Advant Configuration

IndustrialIT
800xA - System
800xA for Advant Master
System Version 4.1
Configuration
IndustrialIT
800xA - System
System Version 4.1
Configuration
NOTICE
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB. ABB assumes no responsibility for any errors that
may appear in this document.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party nor used
for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.
Copyright 2003-2005 by ABB.
All rights reserved.
Release:
Document number:
June 2005
3BSE030340R4101
TRADEMARKS
All rights to trademarks reside with their respective owners.
TABLE OF CONTENTS
About This Book
General ............................................................................................................................11
Intended User...................................................................................................................11
How to Use this Instruction..................................................................................11
Use of Warning, Caution, Information, and Tip Icons ....................................................13
Document Conventions ...................................................................................................14
Terminology.....................................................................................................................15
Related Documentation ...................................................................................................20
Section 1 - Introduction
Product Overview ............................................................................................................23
Product Scope.......................................................................................................23
What You Can Do with 800xA for Advant Master ..............................................24
Prerequisites and Requirements ......................................................................................24
Section 2 - Configuration
Before You Start ..............................................................................................................25
Controller Documentation ...............................................................................................25
Getting Started.................................................................................................................27
Configuration of clock synchronization settings .............................................................29
AC 400 Series Controller as Clock Master ..........................................................29
800xA for Advant Master Connectivity server as Clock Master .........................31
No Synchronization..............................................................................................33
RTA Board Configuration................................................................................................34
Setting Up the RTA Board....................................................................................34
Configure Alarm and Event Lists ....................................................................................34
3BSE030340R4101
Table of Contents
Process Object Lock........................................................................................................ 36

Process Object Sensitive Hot Keys ................................................................................. 37
Predefined Hot Keys ............................................................................................ 37
The Verb Map Aspect .......................................................................................... 39
AC400 Operator Workplace ............................................................................................ 40
Tools in AC 400 Operator Workplace.................................................................. 40
Recommended Workplace Settings ..................................................................... 41
Min and Max Dialog ....................................................................................................... 42
Min and Max Dialog According to Security ....................................................... 42
Section 3 - Engineering
Using the MB 300 Uploader Aspect ............................................................................... 45
Using the From Controller Tab to Upload ........................................................... 46
Using the From FCB Tab to Upload .................................................................... 48
Building the Control Structure On-line........................................................................... 49
Building the Control Structure Offline............................................................................ 53
Building a Control Structure for Test and Demo Purposes............................................. 57
Section 4 - Alarm and Event

Audible Alarm................................................................................................................. 59
Alarm Hiding .................................................................................................................. 59
Defining Event Treatments Using RTA Board Configuration ........................................ 59
Defining Event Treatment for Process and System Objects ........................................... 60
Default Alarm and Event Settings ....................................................................... 60
Defining Event Treatment.................................................................................... 61
Defining event filter on node level .................................................................................. 70
Section 5 - Time Tagged Data (TTD) Configuration

Creating Time Tagged Data (TTD) Logs ........................................................................ 71
The TTD Source Aspect ...................................................................................... 73
The Log Template Aspect.................................................................................... 73
TTD Node Configuration Aspect......................................................................... 76
The Log Configuration Aspect ............................................................................ 82
3BSE030340R4101
Table of Contents
Working with TTD logs .......................................................................................84
Section 6 - Quick List Configuration

Quick List User Interface ................................................................................................97
Configure the Quick List .................................................................................................98
Configuration Examples ................................................................................................103
Section 7 - National Language Support Configuration

Event Treat According to NLS...........................................................................107
Section 8 - Data transfer via OPC DA

OPC Read Operations....................................................................................................119
OPC Write Operations...................................................................................................120
Section 9 - Display Converter

Getting Started...............................................................................................................122
Considerations ...............................................................................................................122
Display Conversion .......................................................................................................122
Add Display Converter as Add-ins to your Graphics Builder............................122
Create New Graphic Elements to Replace the Previously Created AdvaCommand
Graphic Elements ..............................................................................123
Customize your Configuration Files ..................................................................123
Convert and Import your AdvaCommand Graphic Displays .............................129
Edit your Converted Graphic Display ................................................................132
Test and Deploy your Graphic Display ..............................................................133
Limitations of the Display Converter ............................................................................134
Section 10 - System Administration

Hardware Indicators ......................................................................................................135
System Diagnostics .......................................................................................................135
Fault Finding and User Repair ...........................................................................135
System Status .....................................................................................................135
System Alarms ...................................................................................................150
Backup/Restore Procedures...........................................................................................152
3BSE030340R4101
Table of Contents
Backup
.......................................................................................................... 152
Restore
.......................................................................................................... 153
Appendix A - Event Treat Elements

Introduction ................................................................................................................... 157
The Event Treat Database Element ............................................................................... 159
Appendix B - Event Texts

Analog Input Signal AI ................................................................................................. 171
Analog Output Signal AO ............................................................................................. 172
Digital Input Signal DI.................................................................................................. 173
Digital Output Signal DO.............................................................................................. 174
Sequence SEQ ............................................................................................................... 174
Process Controller PIDCON ......................................................................................... 177
Process Controller PIDCONA....................................................................................... 179
Manual Station MANSTN ............................................................................................ 181
Ratio Station RATIOSTN ............................................................................................. 182
User Defined Controller GENCON .............................................................................. 183
Binary Object GENBIN ................................................................................................ 185
User Defined Object GENUSD..................................................................................... 188
Motor Control MOTCON ............................................................................................. 191
Valve Control VALVECON .......................................................................................... 194
Group Start GROUP...................................................................................................... 197
Group Alarm GRPALARM........................................................................................... 199
Motor Control MOTCONI ............................................................................................ 200
Standard Alarm Text from MOTCON PC element............................................ 202
Standard Warning Texts from MCU .................................................................. 204
Standard Alarm Text from MCU ....................................................................... 207
Standard Event Text from MCU ........................................................................ 209
Event Treatment in Operator Station ................................................................. 210
Engineered Drive, DRICONE ....................................................................................... 211
Standard Drive, DRICONS ........................................................................................... 233
3BSE030340R4101
Table of Contents
Appendix C - Messages
Fatal, Error, Warning and Info Messages ......................................................................243
Fatal Messages ...................................................................................................244
Error Messages...................................................................................................245
Warning Messages..............................................................................................248
Appendix D - System Alarm List

Advant Master System Alarms ..........................................................................252
Appendix E - Control Aspects

RTA Board Control Aspect............................................................................................255
RTA Board Control Tab......................................................................................257
RTA Board - Network and Node Configuration Tab..........................................259
RTA Board Configuration Tab ...........................................................................260
Control Connection Aspect (CCA) ...............................................................................261
The CCA Property view .....................................................................................261
CCA Property Info .............................................................................................262
CCA - Additional info........................................................................................264
CCA MasterBus 300 ..........................................................................................264
Appendix F - OPC Properties

OPC object type properties............................................................................................267
INDEX
3BSE030340R4101
Table of Contents
10
3BSE030340R4101
About This Book

General
This book describes 800xA for Advant Master. The 800xA for Advant Master
product is used for connecting the workplaces to a Masterbus 300 control network
with connected AC 400 Controller Series, including MasterPiece 200/1.
Intended User
The information in this instruction is intended for:
The Engineer that sets up the control system functionality (including defining
displays, writing the control programs, etc.)
The System administrator that sets up the control system configuration
The intended user must have experience with process control systems and
Microsoft Windows operating systems. In general, Microsoft Windows
functions are not described in this instruction.
In addition, you should be logged in as an Application Engineer or System Engineer
(on the workplaces) to be allowed to perform some of the procedures that are
described in this book.
There are a number of users guides for the Operator Workplace product.
See Related Documentation on page 20 for a complete list of references.
How to Use this Instruction

This section is a quick guideline to help you find what you are looking for in this
instruction.
3BSE030340R4101
11
How to Use this Instruction
About This Book
Where to Start
Read Product Overview on page 23, to learn more about 800xA for Advant Master.
Read IndustrialIT 800xA, System, Introduction and Installation if you want to start
installing the product.
Start reading Getting Started on page 27 if you want to start to setup the
configuration.
Read Section 10, System Administrationto learn how to trace a problem in the
control system.
Start reading Appendix A, Event Treat Elements, if you want to setup the handling
of process events.
Read Appendix B, Event Textsfor a detailed description of how to setup the texts for
the process events. Start reading Section 9, Display Converterfor a detailed
description of how to define and setup the displays for presenting process data from
the AC 400 controllers.
How to Install 800xA for Advant Master
The 800xA for Advant Master is installed as a system extension to the workplace
software. See IndustrialIT 800xA, System, Introduction and Installation for
instructions on how to install the 800xA for Advant Master software.
Configuration of 800xA for Advant Master
The configuration of 800xA for Advant Master is described in Section 2,

Configuration This section also includes examples of how to setup 800xA for
Advant Master applications.
Maintenance and Administrative Procedures
Section 10, System Administrationdescribes error messages that are applicable to

the 800xA for Advant Master.
This section also describes the configuration of 800xA for Advant Master. Refer to
the IndustrialIT 800xA, System, Administration and Security for information on
system administration procedures such as:
12
managing users (creating new users, setting up passwords, and configuration of

user preferences)
3BSE030340R4101
About This Book
Use of Warning, Caution, Information, and Tip Icons
guidelines for adapting the connection to the used controllers
On-Line Help
Comprehensive on-line help is available for the software. Access to the complete
help files is available via the menu bar.
Use of Warning, Caution, Information, and Tip Icons

This publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:
Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.
Warning icon indicates the presence of a hazard which could result in personal
injury.
Caution icon indicates important information or warning related to the concept
discussed in the text. It might indicate the presence of a hazard which could result
in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function.
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.
3BSE030340R4101
13
Document Conventions
About This Book
Document Conventions
The following conventions are used for the presentation of material:
The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
Press ESC E C indicates that you press and release each key in sequence (to
copy a selected object in this case).
The names of push and toggle buttons are boldfaced. For example, click OK.
The names of menus and menu items are boldfaced. For example, the File
menu.
The following convention is used for menu operations: MenuName >

MenuItem > CascadedMenuItem. For example: select File > New > Type.
The Start menu name always refers to the Start menu on the Windows
Task Bar.
System prompts/messages are shown in the Courier font, and user

responses/input are in the boldfaced Courier font. For example, if you enter a
value out of range, the following message is displayed:
Entered value is not valid. The value must be 0 to 30.
You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.

sequence name
14
3BSE030340R4101
About This Book
Terminology
Terminology
The list contains terms and abbreviations that are unique to ABB or have a usage or
definition that is different from standard industry usage.
Table 1. Terminology
Term
Description
ActiveX
Microsoft standard for user interface components, based

on definition of software interfaces.
Aspect
An aspect is a description of some properties of a real

world entity. The properties described could be
mechanical layout, how the object is controlled, a live
video image, name of the object etc.
Aspect Category
A specialization of an aspect type. For example, the

aspect type Graphic Display includes the categories
Overview, Group and Object Display.
Aspect Object Type
An Aspect Object type defines certain characteristics

that are shared between several Aspect Object
instances, such as a basic set of common aspects. This
makes it possible to create and efficiently re-use
standardized solutions to frequently recurring problems.
For example, rather than building an Aspect Object from
scratch for every valve in a plant, you can define a set of
valve types, and then create all valve objects as
instances of these types.
Aspect Objects
A computer representation of a real world entity like a

pump, a valve, an order or a virtual object like a service.
This computer representation is implemented by the
800xA System. An Aspect Object works like an
information container for its aspects.
Aspect Server
A server that runs the central functions of the Aspect

Object architecture, such as Aspect Directory, Structure
and Name Server, Cross Referencing, File Set
Distribution, etc.
3BSE030340R4101
15
Terminology
About This Book
Term
16
Description
Aspect System
A software system, which implements one or several

aspect types by providing one or several aspect system
objects.
Composite Aspect
Object Type
A composite Aspect Object type describes a set of

Aspect Objects organized in a structure, with a parent
object and one or several child objects. The children in a
composite object type are called formal instances,
because they inherit from object types defined
elsewhere in the Object Type Structure, but they are not
actual instances. When a composite object is
instantiated actual instances are created for these child
objects.
OCS Integration
Product
connectivity components, up-loader, supporting aspect

systems (e.g for the configuration), and graphical
elements, faceplates, Aspect Object Types, etc., bundled
together to provide the integration of a certain type of
devices into the IndustrialIT 800xA System.
Connectivity Server
A server that provides access to controllers and other

sources for real-time data, historical data, and alarm and
event data. A Connectivity Server runs services related
to OPC/DA, OPC/AE, OPC/HDA.
Control Builder A
The configuration tool for Advant Master Controller.

Control Builder A consists of Application Builder, Bus
Configuration Builder, Function Chart Builder and the
option On-Line Builder.
Faceplate
A faceplate is an aspect that provides a graphical

representation of a certain aspect object, with
presentation of certain properties related to the object,
and mechanism for operator interaction such as on/off,
increase/decrease, etc. Aspect Object types often
include several faceplate aspects, providing different
presentation and interaction possibilities.
3BSE030340R4101
About This Book
Terminology
Term
Description
Function Chart Builder
Part of the configuration tool Control Builder A.
Graphic Display
A graphic display is an aspect that provides a visual

presentation. It consists of static graphics representing
for example tanks, pipes etc., and graphic elements that
present dynamic information. Graphic displays are often
used to present the state of a process or a part of a
process, but are useful in any context where dynamic
graphical information is needed.
Hot Key
Key combination that perform a specific function.
IndustrialIT
ABBs vision for enterprise automation.
IndustrialIT 800xA
System
A computer system that implements the IndustrialIT

vision.
Node
A computer communicating on a network e.g. the

Internet, Plant, Control or IO network. Each node
typically has a unique node address with a format
depending on the network it is connected to.
OPC/DA
An application programming interface defined by the

standardization group OPC Foundation. The standard
defines how to access large amounts of real-time data
between applications. The OPC standard interface is
used between automation/control applications, field
systems/devices and business/office application.
Permission
A permission groups a set of operations that require the

same authority. For each operation defined for an
aspect, the aspect category specifies the permission
needed to use that interface.
3BSE030340R4101
17
Terminology
About This Book
Term
Description
Plant Explorer
An application that is used to create, delete and organize

Aspect Objects and Aspects within the 800xA System.
The plant explorer organizes the Aspect Objects in
structures according to functionality, location etc. You
can also use it to browse and search the structures of
the plant.
Process Object
A process concept/equipment e.g. valve, motor,

conveyor or tank.
Property
A data field on an aspect of an Aspect Object that can be

accessed through OPC using the standard Aspect
Object reference syntax.
A data field on an ActiveX control accessible from the
Visual Basic editor.
Security
Server
18
Security controls a users authority to perform different

operations on Aspect Objects, depending on several
parameters:
The users credentials, as provided by Windows
The node where the user is logged in. This makes it

possible to give a user different authority depending
on where he/she is located, e.g. close to the
process equipment, in a control room, or at home
accessing the system through Internet.
The operation the user wants to perform the

operation on.
A node that runs one or several Afw Services.

It is the part of the software that supply data to a
subscriber.
3BSE030340R4101
About This Book
Terminology
Term
Description
Structure
A hierarchical tree organization of Aspect Objects.

Each structure is used to define a certain kind of relation
between Aspect Object. The functional structure defines
how a function can be divided into sub functions, the
location structure defines how different objects are
located within each other.
The control structure defines how functions are executed
by tasks, controllers etc. An Aspect Object can be
located in several structures, for example both in a
functional structure and in a location structure.
System Application
A software component, based on the Aspect Object

architecture, which provides functionality. System
applications cooperate according to rules defined be the
Aspect Object architecture. They are normally bundled
into the system products or system extensions. System
applications are implemented as client applications or
services. To participate in Aspect Object operations,
an application must present itself as one (or several)
aspect system.
When there is no risk for confusion with user application,
the term application may be used instead of system
application.
System Extension
A system Extension consists of one or more applications

that are bundled as an extension to one or several
existing System Product(s). A System extension can
only be installed if (one of) the corresponding System
Product(s) has been installed previously.
Uploader
An upload is used to import a configuration from devices,

to load and build a set of Aspect Objects from
information present in the devices.
3BSE030340R4101
19
Related Documentation
About This Book
Term
Description
User application
A configuration of software and hardware components

that applies to a specific problem, e.g. a specific process
control problem. A user application consists of a set of
simple and composite Aspect Object instances, with
parameter values and other configuration data for the
aspects, e.g control logic, graphics, alarm and event
specifications, reports etc.
View
An Aspect can have several ways to be presented

depending on the task performed, like viewing or
configuration. Each presentation form is called a view.
Workplace
1. User interactive functions that are combined for a

particular use, e.g, Operator Workplace.
2. A node that runs one or several workplace
applications.
Table 2. Related Documentation
Category
Installation
20
Title
Description
IndustrialIT 800xA System Installation
This book describes the installation

procedure for 800xA System and 800xA
for Advant Master.
IndustrialIT 800xA System Post

Installation
This book describes the post installation

procedure for 800xA System and 800xA
for Advant Master.
3BSE030340R4101
About This Book
Table 2. Related Documentation

Category
Configuration
Operation
Title
Description
IndustrialIT 800xA System

Extended Graphic Library
This book describes the library of

optional graphic elements for
AC 400 Series controllers objects.

Graphic Library
This book describes all the graphic

elements and faceplates for AC 400
Series controllers specific object types.

Operator Workplace Configuration
This book describes how to set up an

Operator Workplace.

Administration and Security
This book describes user handling,

security settings, system backup etc.

Operation
This book describes how to operate

800xA for Advant Master.
3BSE030340R4101
21
22
About This Book
3BSE030340R4101
Section 1 Introduction
Product Overview
The Operator Workplace software is a product for process monitoring and control.
The generic design makes it possible to use the Operator Workplace together with
many different types of Process Control Systems, both systems provided by ABB as
well as systems provided by other suppliers.
This book describes 800xA for Advant Master. It is a software product that enables
you to integrate an Operator Workplace to a system of AC 400 controllers (Master
version), in a MasterBus 300 network, and extends the total functionality of the
System utilizing the best of the AC 400 controller system.
Product Scope
800xA for Advant Master is a product which together with the Operator Workplace
gives you the following features:
A connection to the control system through a dedicated communication board the RTA board (Real-Time Accelerator board).
Tools to build your Operator Workplace Control Structure on-line from

the AC 400 controllers or off-line from the AC 400 Engineering tools
databases.
The possibility to customize the event and alarm reporting and presentation
with just a few configuration actions.
To use the AC 400 TTD historical logs as data source to Operator Workplace
Historian, but also tools to configure new TTD logs in the controllers.
Powerful maintenance and supervision of the Advant Master Control system

itself using the System Status, System Alarms and RTA Board Control
functions.
3BSE030340R4101
23
What You Can Do with 800xA for Advant Master
Section 1 Introduction
What You Can Do with 800xA for Advant Master

This list is an example of the engineering that you can do with
800xA for Advant Master.
Configure the connection of the workplace to the MasterBus 300 control

network.
Convert the displays and display elements from older versions of

ABB Operator stations.
Setup the workplace for handling the process data that is defined in
the database of the AC 400 controllers. You do not need to define the database
again, it is read from the controllers over the network.
Setup the event handling for the process events that are reported from
the AC 400 controllers.
Define and activate the logging of process data, including presentation of

the stored data logs.
Collect and present System status for the entire control system, including
the AC 400 controllers and the MB 300 control network.
Prerequisites and Requirements

The general hardware and software requirements for the Operator Workplace
product are described in the IndustrialIT 800xA System, Introduction and
Installation.
24
3BSE030340R4101
Section 2 Configuration
Before You Start
Make sure that you have access to either of the following:
The Connectivity Server is connected to the AC 400 controllers (the

MasterBus 300 control network).
The database instances from the Function Chart Builder (AC 400 Controller
Engineering tools).
You should have at least briefly read IndustrialIT 800xA, System, Operator
Workplace Configuration, before going into the details in this book.
You must be logged in as an Application Engineer or System Engineer to be able to
perform the configuration work described in this section.
The Application Engineer or System Engineer has to be a member of the MS
Windows Power Users group or the Administrators group to be able to
perform the configurations.
Controller Documentation
The AC 400 controller documentation covering all manuals needed for
configuration, operation or maintenance of AC 450 or AC 410 controllers are
included in 800xA for Advant Master. The manuals are available in the following
ways:
3BSE030340R4101
Via object type specific bookmarks available as aspects in the Control

Structure on the uploaded Advant Master objects. The manuals can also be
opened via the context menu on Advant Master objects in the System Status
viewer. See Figure 1 below.
25
Controller Documentation
Figure 1. Bookmark on I/O
26
The complete collection of AC 400 manuals can be found on the AC 400

Documentation object in the Object type structure. The manuals that do not
have a related object type in 800xA for Advant Master can only be opened via
the AC 400 Documentation object. See Figure 2 below.
3BSE030340R4101
Getting Started
Figure 2. AC 400 Documentation Object
Getting Started
There are normally two different scenarios for the configuration work on an
800xA for Advant Master system:
1.
3BSE030340R4101
You have an existing system that is in operation. The engineering of

the controllers is already made. The controllers are already up and running.
27
Getting Started
2.
You are building up a new system or at least partly a new system.

It is an advantage to be able to start the engineering of the Operator Workplace
applications in parallel with the engineering of the controllers.
You perform the following steps for the two scenarios:

The Steps for an Existing Plant
1.
Setup the parameters for the RTA Board (network and node address, time
synchronization, Character Conversion).
You can choose No Conversion (English), Swedish or German when configuring
the RTA Board.
2.
Build the Control Structure.
3.
Retrieve (upload) the information about the Process and System objects.
4.
Modify (if required) the Alarm and Event default settings.
5.
Retrieve (synchronize) the TTD (Time Tagged Data) logs in the controller and
the corresponding log hierarchies above them.
6.
Perform an RTA board backup.
The Steps for the New System
1.
28
Build the Controller Application

a.
Create and configure Process and System objects
b.
Define Log groups (TTD)
c.
Write your AMPL applications
2.
Setup the parameters for the RTA Board (network and node address, time
synchronization).
3.
Download the applications to the controllers, using Function Chart Builder.
4.
Build the Control Structure (Retrieve the information about the Process
and system objects).
5.
Modify (if required) the Alarm and Event default setting.
3BSE030340R4101
6.
Configuration of clock synchronization settings
Configure the TTD logs in the controller and the corresponding log hierarchies
above them.
The Engineering of the controllers and the various steps to perform is not described
in this book. Please read the corresponding Users Guides.

This document describes two possible configuration settings for time
synchronization with MB300 network.
AC 400 Series controller as Clock Master, in a configuration with MB300.
800xA for Advant Master Connectivity Server As Clock Master, in a

configuration with AC 400 Series controllers on MB300 and AC 800M
controllers on a TCP/IP network.
A thorough description of synchronization strategies and overall configuration is

provided in Industrial IT 800xA System - Automation System Network - Design and
Configuration.
AC 400 Series Controller as Clock Master

When you have MB300 as the only control network in your configuration, it is
recommended to use an AC 400 Series controller as clock master. The described
configuration will receive time synchronization from the MB300 network and
distribute it to other Operator Workplace nodes (e.g Aspect Servers, Clients) in the
system. Manual time settings (e.g from client nodes) or local time shifts in the
system are propagated to the RTA Board and the MB300 network.
The following settings are used for this configuration:
Windows Registry Settings
REVERSED_SYNC_MODE = 0
No changes of the default configuration values are required

RTA Board Settings
CLK_MAST = 0
LOC_TIME = 2
3BSE030340R4101
29
CLK_SEND = 1
No changes of the default configuration values are required
Time Server Master Settings
To distribute the time received from the MB300 network to other Operator
Workplace nodes (e.g Aspect Servers, Clients) in the system, you have to configure
the time service in the dedicated Connectivity Server as time server master.
This is done in the following way.
1.
Go to the Service Structure and select Time Service.
2.
Select Basic, Service Group.
3.
Select the Service Group Definition aspect.
Figure 3. Service Structure
30
3BSE030340R4101
800xA for Advant Master Connectivity server as Clock Master
4.
Select the Configuration tab in the aspect window.
5.
Place the Provider, selected to be master, first in the list. The providers below
will automatically be configured as standby.
All Time Synchronization services should be enabled.

This description is valid for a system configuration with AC 400 Series controllers
on MB300 and AC 800M controllers on a TCP/IP network. The described
configuration will synchronize all nodes on the MB300 network from the RTA
Board in the configured CS.
Windows registry settings
For the configuration using 800xA for Advant Master Connectivity server as clock
master, change the synchronization direction between the Connectivity Server and
the RTA Board. This is done by changing a parameter in the registry.
It is always a risk to change values in the Windows registry edit. Be sure you
have a backup for safety reasons, so the computer can be restored if something
goes wrong.
1.
Go to the Start menu, select Run and enter regedit. The registry is opened.
2.
Open the KEY:

HKEY_LOCAL_MACHINE\SOFTWARE\ABB\AFW\SystemModules\
AfwTimeServerAdaptor\1.0-0\Private
3.
Change the parameter REVERSED_SYNC_MODE from 0 to 1.
RTA Board settings
1.
Expand the Control Structure in the Plant Explorer, and select the RTA Board
object.
2.
Select the RTA Board Control aspect in the aspect list.
3.
Select the RTA Board Configuration tab and click the RTA Board Config
button.
This is done locally in the Connectivity Server with a RTA Board.
3BSE030340R4101
31
Figure 4. RTA Board Control Aspect

In the RTA Board Configuration window, enter mdb CLOCK_SYNCH.
32
3BSE030340R4101
No Synchronization
Change the CLK_MAST parameter to 0 as described in window,

see Figure 5.
Figure 5. CLOCK_SYNCH DB Element

4.
Close the window.
5.
Select RTA Board Backup.
6.
You have to Stop and then Start the RTA Board, to activate the changes.
This is done by selecting the RTA Board Control tab in the RTA Board
Control aspect.
No Synchronization
If you for some reason (mixed systems) do not want any synchronization between
the RTA Board (MB 300 network) and the Connectivity Server, you can set the
parameter SYNC_INTERVAL to a negative value in the registry (same key as
above, -1 put in FFFFFFFF).
3BSE030340R4101
33
RTA Board Configuration

Setting Up the RTA Board
The configuration settings for the RTA Board include configuration of:
Network and node number on the MasterBus 300 Control Network
Time synchronization setting for RTA / PC clock synchronization
Character Conversion
The network and node numbers must be setup before the Operator Workplace
node can communicate with the control network.
The RTA Board configuration view (Network and Node configuration) will also
come up during the configuration of the system. The view is included when you
run the Configuration wizard.
Setup Network and Node Number
Use Configuration Wizard in order to setup network and node number. Please see
IndustrialIT 800xA System, Post Installation Setup.
Configure Alarm and Event Lists

Available Lists
There are four Advant Master specific alarm and event lists.
34
AC400 Alarm Line. It is used in the alarm line in the AC 400 Operator
Workplace, and shows the three latest unacknowledged process alarms.
AC400 Alarm List. It shows all process alarms.
AC400 Event List. It shows all process events.
AC400 System Alarm List. It shows all Advant Master and 800xA system
alarms.
3BSE030340R4101
Configure Alarm and Event Lists
To access a list:
1.
Select the Workplace Structure.
2.
Select the object AC400 Operator Workplace, see Figure 6.
3.
Select relevant aspect, for example, AC400 Alarm List.
Figure 6. Available Alarm and Event Lists

Default Configurations
The relevant default alarm and event configurations can be found in the Library
Structure as part of the object MB300 Default Configurations, see Figure 7.
Figure 7. Default Alarm and Event Configurations

Available are:
MB300 Default Alarm Line. It is used to configure the AC400 Alarm Line.
MB300 Default Alarm List. It is used to configure the AC400 Alarm List.
MB300 Default Event List. It is used to configure the AC400 Event List.
MB300 Default Logger Config. It is used by the Alarm Logger function to log
alarms or events on a printer.
3BSE030340R4101
35
Process Object Lock
MB300 Default System Alarm List. It is used to configure the AC400 System
Alarm List.
For more information on how to configure alarm and event lists, refer to the
IndustrialIT 800xA, System, Operator Workplace Configuration.
Process Object Lock

It is possible to lock a process object via the lock button in the Faceplate to exclude
other operators from operation on the specific object. The lock is released when the
Faceplate is closed, the lock button is clicked or else after a specific time-out period
of inactivity. It is however not required to lock an object before starting to operate it.
The autolock function can be used if the desired behavior is that the object is
automatically locked at Faceplate call-up. This function can be enabled on a user via
the User Profile aspect Graphics Profile Values in the User Structure (see Figure 8).
See IndustrialIT System, Operator Workplace Configuration for details on how to
configure User Profile aspects.
Figure 8. Autolock Enabled in an Graphics Profile Values Aspect
36
3BSE030340R4101
Process Object Sensitive Hot Keys

The Hot Keys Aspect is located in the workplace structure.
You use the Hot Keys Aspect System to configure Hot Keys. It enables
configuration of key combinations that perform specific functions, such as opening
an aspect view or activating a verb.
The hot keys operations is done on highlighted objects.
Predefined Hot Keys

The following set of Hot Keys are predefined in the product:
Table 3. Predefined Hot Keys 1

Object Type
Acknowledge
On/Start/
Off/Stop
Open/True Close/False
Man
CTRL+
SHIFT+
CTRL+
SHIFT+
CTRL+
SHIFT+
CTRL+
SHIFT+
AI
AO
DI
DO
PIDCONA
PIDCON
MANSTN
RATIONSTN
MOTCON
VALVECON
GROUP
3BSE030340R4101
37
Table 3. Predefined Hot Keys 1 (Continued)

Object Type
Acknowledge
On/Start/
Off/Stop
Open/True Close/False
Man
SEQUENCE
GENBIN
GENCON
GENUSD
DATB
TEXT_DATA
DRICONE
DRICONS
MOTCON_I
Table 4. Predefined Hot Keys 2

Object Type
Auto
E1
E2
Small
Increase
Small
Decrease
CTRL+ CTRL+ CTRL+ CTRL+

SHIFT+ SHIFT+ SHIFT+ SHIFT+
CTRL+
SHIFT+
AI
AO
DI
38
DO
PIDCONA
PIDCON
3BSE030340R4101
Table 4. Predefined Hot Keys 2 (Continued)

Object Type
Auto
MANSTN
RATIONSTN
MOTCON
VALVECON
GROUP
SEQUENCE
GENBIN
GENCON
GENUSD
E1
E2
Small
Increase
Small
Decrease
DATB
TEXT_DATA
DRICONE
DRICONS
MOTCON_I
The Verb Map Aspect

The Verb Map aspect extends the support provided by the Hot Keys aspect.
It provides a cross connection, which makes it easier to apply the Hot Key support
for highlighted and selected objects. It makes it also easier for different connected
OCS systems to apply the same hot keys for their objects.
Objects with the Verb Map aspect can be part of a hot key scheme using the selected
and highlighted concepts.
For more information about the Verb Map Aspect see IndustrialIT 800xA, System,
Operator Workplace Configuration.
3BSE030340R4101
39
AC400 Operator Workplace
AC400 Operator Workplace

Tools in AC 400 Operator Workplace
The following chapters describe the added/changed functionality/tools in the
AC 400 Operator Workplace. Please see IndustrialIT 800xA, System, Operator
Workplace Configuration for a description of generic Operator Workplace
functionality.
AC 400 Lines
All Process Alarms
External Alarms
Show Help Date and Time
All Process Events System Event List
Aspect Menu
System Status
Close all Overlaps
System Alarms
Figure 9. AC 400 Specific Tools
40
AC 400 Alarm Lines

This area shows the three latest unacknowledged process alarms in the system.
All Process Alarms

Click this button to view a list of all process alarms.
All Process Event

Shows a list of all process events and Advant Master system events.
System Alarms
Click the button to view a list of all Advant Master system alarms.
System Event List
3BSE030340R4101
Recommended Workplace Settings
System Status
Shows System Status for all control networks and controllers included in the
system.
External Alarms
When you click the button the status for all External Alarms configured in the
system, will be shown. For more information about External Alarms,
read IndustrialIT 800xA, System, Operator Workplace Configuration.
Close all Overlaps

Use this button to close all overlaps (pop-up windows).
Show Help
Click the Show Help button to view the On-line Help.
Date & Time

Both date and time are shown according to the Windows date and time settings.
Recommended Workplace Settings

Your AC 400 Operator Workplace interface can differ from the figures in this
document. It is possible to customize the AC 400 Operator Workplace.
For details about workplace settings IndustrialIT 800xA, System, Operator
Workplace Configuration.
3BSE030340R4101
41
Min and Max Dialog
Min and Max Dialog

Min and Max Dialog According to Security
In order to reflect min and max dialog of the AS500OS all writable properties in the
control connection for each of the Advant Master objects types have been defined to
require either tune or operate permission. This together with the corresponding
system security definition will allow the operators to operate the min dialog but not
the max dialog properties.
The introduction of min/max dialog does not hide any information from the user;
instead it will give the system configurator the means to restrict the operations
available for a single user or a group of users.
When the user does not possess the permissions required for an operation the
buttons in the faceplate will be dimmed. Number fields will not be open for input
etc.
The most common is that an operator is permitted to operate, e.g. enter values.
If you have more permissions (as an Application Engineer) you may be allowed to
tune, e.g. set alarm limits or blocking parameters.
For more information about Security settings, please read the IndustrialIT 800xA,
System, Administration and Security.
42
3BSE030340R4101
Min and Max Dialog
Figure 10. Min and Max Dialog
3BSE030340R4101
43
Min and Max Dialog
44
3BSE030340R4101
Section 3 Engineering
Using the MB 300 Uploader Aspect
The MB300 Uploader aspect is placed in the Control Structure. It is possible to
make an upload on network level or on node/controller level. See Figure 11.
If making an upload on network level all nodes below are uploaded, one node at a
time.
Network Level
Node/Controller
Level
Figure 11. Upload - Control Structure
3BSE030340R4101
45
The MB 300 Uploader aspect has two tabs:
The From Controller tab that contains functions to read the information
directly from the controllers (via the MB 300 network), refer to
Using the From Controller Tab to Upload on page 46.
The From FCB tab that contains functions to read the information from a
source file. The source file is created with the Function Chart Builder (FCB)
engineering tool. Refer to Using the From FCB Tab to Upload on page 48.
Using the From Controller Tab to Upload

This aspect makes it possible to request an upload of object data from
the AC 400 controller to the Operator Workplace.
Figure 12. MB 300 Uploader, From Controller

Adding or Removing Object Types to Upload
Click Add or Remove to modify the list with object types that you want to include
in the Upload. If you leave the list blank, all object types are included (this is the
default).
46
3BSE030340R4101
The following object types are valid for Upload:
All object types located in MB 300 Process Objects group.
Bus and Station object types under Advant Fieldbus 100, Lonbus and Profibus.
S400 MasterFieldbus object type.

Create Uploader from Source File and Build Control Structure
These check boxes should always be marked. They are only used for fault tracing
and simulation, and should not be modified. They should only be modified on direct
request from the supplier.
Starting the Upload
Click on Start Upload when you are ready for the upload. The window in the lower
part of the aspect view presents messages describing the progress, see Figure 12.
Stop the Upload
Click on Stop Upload if you want to interrupt the upload.

Uploading may take time depending on application and controller type.
3BSE030340R4101
47
Using the From FCB Tab to Upload
Using the From FCB Tab to Upload

This aspect makes it possible to request an upload of object data based on
information from the Function Chart Builder Engineering tool.
Figure 13. MB 300 Uploader, From FCB

Adding or Removing Object Types to Upload
Click Add or Remove to modify the list with object types that you want to include
in the Upload. If you leave the list blank, all object types are included (this is the
default).
The following object types are valid for Upload:
48
All object types located in MB 300 Process Objects group.
Bus and Station object types under Advant Fieldbus 100, Lonbus and Profibus.
S400 MasterFieldbus object type.
3BSE030340R4101
Building the Control Structure On-line
Selecting Type of Upload
You can select three types of upload from this view.
Check the Create Uploader Source File and Build Control Structure check
boxes to build the Control Structure based on information from the engineering
software FCB (Function Chart Builder). You have to fill in the name of the
FCB Database File (ODB file) to retrieve information from. This choice
requires that FCB is installed at the same node.
Uncheck the Create Uploader Source File checkbox and check Build
Control Structure checkbox to build the Control Structure from a previously
created Uploader Source File (OCD file). You have to enter the name of the
Uploader Source File. This choice does not require that FCB is installed at the
same node. See Building the Control Structure On-line. [ndra till sidnr-ref]
Check Create Uploader Source File and uncheck Build Control Structure to
create a Uploader Source file based on the information from the engineering
software FCB (Function Chart Builder). You have to fill in the name of the
FCB Database File (ODB file) to retrieve information from, and the name of
the Uploader Source File (OCD file) to create. This option does not update or
create the Control Structure. Can be used to produce the OCD file for other
800xA systems using the same controllers. This choice requires that FCB is
installed at the same node.
Starting the Upload
Click on the Start Upload button when you are ready for the upload. The window
in the lower part of the aspect view presents messages describing the progress,
see Figure 13.
Stopping the Upload
Click on the Stop Upload button when you want to interrupt the upload.

The Control Structure is based on the controllers in your Advant Master System.
To build the structure, do as follows:
3BSE030340R4101
49
Use the Configuration Wizard to create an RTA Board object
Add each AC 400 controller to the structure using the correct node object type
as template and enter the correct network and node number.
For each AC 400 controller, run the Upload procedure (as described on the next
pages) to populate the whole structure of I/O boards and Process and System
objects. Run the MB 300 Uploader aspect for each controller.
Before starting the upload procedure it is recommended to select character

conversion on the RTA Board. Character conversion must have 7-bit ASCII in
Name and Description converted to 8-bit. This to prevent incorrect naming, for
example H\G NIV] instead of HG NIV in a Swedish system.
If character conversion is changed after the upload and a new upload is done,
object identity might change, for example links from trends and process
graphics can be lost as well as event treatment element settings.
You can populate one controller at a time or one or a couple of object types at a
time. The MB 300 Uploader reads all information it requires from the controller and
creates the corresponding objects and aspects in the Control Structure.
The following steps describe how to create the complete Control Structure, for one
Controller Node starting from an empty Control Structure.
50
1.
Go to the Control Structure.
2.
Add the Controller object. Request creation of a new object and select a
Controller type that corresponds to the controller you are adding.
3BSE030340R4101
It is recommended to include Network number or at least Node number in the

name. (If you have a redundant network, the network number should probably
not be included in the name). See Figure 14.
Figure 14. Creating a Controller Object Type
3BSE030340R4101
51
3.
Now you are ready to read all the information about the Control Structure and
the Process and System objects. Bring up the MB 300 Uploader aspect:
Figure 15. The MB 300 Uploader aspect

For a controller with many objects of certain types it may be wise to read at
least the most populated object types one by one and then read the others in
sequence.
Check the Create Uploader Source File and the Build Control Structure
check boxes. (These check boxes are only unchecked during fault tracing, and
shall always be checked during normal operation.)
In this case it will read all information and create the whole structure in one
sequence. Click the Start Upload button to do so.
52
4.
Uploading can take some time. When complete, use Plant Explorer to browse
the structure and verify that everything is in place as expected.
5.
Start building applications based on these objects, see the IndustrialIT 800xA,
System, Operator Workplace Configuration.
3BSE030340R4101
Building the Control Structure Offline

The Control Structure can also be built using the output from the Controller
Engineering tool FCB. This has some advantages for a new site:
You can create the Control Structure step by step as the Controller Engineering
proceeds and thereby extend your Operator Workplace applications stepwise.
You can work off-line from the controllers (without connection to the control
network), also in a site geographically separated from where the Controller
Engineering is made.
The work will now involve a few more steps compared to the On-line example in
Using the From FCB Tab to Upload on page 48:
Use the FCB 6.0 MB 300 Uploader option or a later version on the Engineering
PC. Create source files for each controller and copy them to your Advant
Master Server.
Run the MB 300 Uploader aspect for each controller using the source files as
input. You can populate one controller at a time or one or a couple of object
types at a time.
When the controller is available on the network, you can retrieve some of
the addresses, that are only available in the controller, to the Control Structure.
Run the MB 300 Uploader directly towards the controller. This is not required
until you are about to go on-line.
The following step by step tutorial describes how to create the complete
Control Structure for the AC 450 Controller (node address 31,18) starting with an
empty Control Structure. We assume that you have already installed the MB 300
Uploader option on the PC where you have the engineering software running.
Refer to the Function Chart Builder Users Guide for a detailed description on how
to build the controller objects.
1.
Build the Controller objects with the Function Chart Builder engineering tool.
2.
Use FCB 6.0 MB 300 Uploader option or a later version. Go to the Start menu
and select Advant > Engineering > Utilities > MB 300 Uploader option on
the Engineering PC.
3BSE030340R4101
53
3.
The following dialog box appears:
Figure 16. FCB Upload
54
4.
Enter the name of the file that should be created (the Uploader Source File).
Set the name to Load-file-31-18.ocd.
5.
Make sure only the object types that you want to upload are shown in
the Object Types to upload list. You move object types between the lists by
selecting them and using the arrow buttons.
6.
Start the upload process by clicking the Start FcbUpload button.
7.
Make the source file you just created accessible from the Operator Workplace
server. There are several ways to make the file accessible.
Copy the file to a shared disk that is available from the server.
Copy the file to a floppy disk.
3BSE030340R4101
Now we can go over to the Operator Workplace server machine. Log in as a

System Engineer and do as follows:
1.
Select the Control Structure in Plant Explorer. (We assume that you have
created the Network and Server objects already. If you have not, see the tutorial
in Creating Time Tagged Data (TTD) Logs on page 71.)
2.
Open the context menu on Network object and select New Object.
3.
Select the AC 450 Controller Object Type, enter the Node name, and click
Create.
Figure 17. Selecting the Object Type AC 450

4.
From the Controller 31, 18 object, select the MB 300 Uploader aspect,
and select the From FCB tab.
5.
Uncheck the Create Uploader Source File check box. Now you can edit
the Uploader Source File text field. Enter the name of the transported source
file Load-file-31-18.ocd. Select Start Upload, see Figure 18.
3BSE030340R4101
55
Figure 18. Creating the Control Structure for Node 31, 18

This step can be split up into several parts, as it is possible to work with one
object type at a time. If you know that you have only added or modified objects
of type AI in the engineering database, then other object types do not have to be
uploaded.
6.
Now that the Uploader step is done, the Control Structure is updated with
the objects included in the FCB source file. You can start building applications
based on these objects, see also the IndustrialIT 800xA, System, Operator
Workplace Configuration.
7.
Before you can go on-line with your system, you need to make an additional
upload session, directly toward the controllers. The reason is that some of the
physical addresses in the controllers are not available in the FCB files.
However, you have saved considerable time by using the time-lag between
Controller Engineering and the time the controllers are installed and up and
running.
8.
56
Select the From Controller tab and click Start Upload. This will upload all
object data from the controller.
3BSE030340R4101
Building a Control Structure for Test and Demo Purposes

It may sometimes be an advantage to be able to test or demonstrate your
applications in a simulated Control Structure.
Note that the graphic presentation of object data, in the shape of faceplates or
display elements, does not work directly with simulated values from the Property
Signal Generator. You must define supervision and presentation properties to
input simulated live data into the presentation of faceplates or display elements.
You can build a Control Structure with simulated values through the following
steps:
1.
Select the Control Structure in Plant Explorer.
2.
Build a structure that includes the process and system objects that you want to
simulate.
3.
Add the Property Signal Generator aspect to each object (process and system
objects) that you want simulated data from.
Figure 19. Add Aspect Property Signal Generator
3BSE030340R4101
57
4.
Set up the configuration of the Signal Generator aspect to generate data for the
specific attributes. This set up includes specifying variable data style - Sin
wave, Ramp, Random, Static Value etc. You specify the set up for each object
attribute.
Figure 20. Setup for Property Signal Generator
58
5.
Build your applications to work with this Control Structure with simulated
attributes.
6.
Test your applications (demo applications, test applications).
7.
Save the controller node objects in the Control Structure for future use by
exporting each node separately, one by one. Start the Import/Export tool via
Start > All Programs > ABB Industrial IT 800xA > System > Import
Export. Use drag and drop when exporting the objects from the
Plant Explorer to the Import/Export tool.
3BSE030340R4101
Section 4 Alarm and Event

Audible Alarm
In order to be able to receive audible alarms, the audible event treatment property
must be set.
Alarm Hiding
The 800xA for Advant Master supports hiding of alarms. The hiding function
supports hiding of all alarms for an object. Specific values can not be hidden. Please
see the 800xA System Operator Workplace Configuration for more information.
The 800xA for Advant Master faceplates are preconfigured to indicate hiding. The
alarm control button indicates this.
Defining Event Treatments Using RTA Board

Configuration
You define the Event treatment by configuring data base elements on the RTA
Board. After setting up the database on the RTA Board, you shall save the database
configuration. See Appendix A, Event Treat Elements to get a detailed description
of the data base elements that you can configure. Appendix B, Event Texts contains
a detailed description how to setup the event text elements.
When you have setup the event treatment, you shall save the RTA database. Look in
RTA Board Configuration Tab on page 260 for guidance how to save the RTA
database.
3BSE030340R4101
59
Defining Event Treatment for Process and System Objects
Defining Event Treatment for Process and System Objects

Default Alarm and Event Settings
After installing the 800xA for Advant Master, you will find five (5) Default Alarm
and Event aspect objects in the Library Structure, with default settings related to
MasterBus 300 and Advant Controller 400 Series. See Figure 21 below. Reference
these when you need an alarm or event object.
They are predefined to meet your needs.
Figure 21. Predefined Default Alarm and Event Aspect Objects for
MB 300
How to change the default settings is described in IndustrialIT 800xA, System,
60
3BSE030340R4101
Defining Event Treatment

The Event Treatment for Advant Master objects are defined during the engineering
phase of the controller. When you build the Objects in the controller you assign
values to special parameters that are important for the event handling. These
parameters are mentioned in many Advant OCS documents under the collective
designation Event-Treat-pointers. They are used, for example, to determine
whether a change of status is to be handled as an alarm or an event. It is also
possible to determine color priority and whether an acoustic signal is to be activated,
separate handling of changes 0 to 1 and 1 to 0 etc.
Different types of events in an aspect object are assembled in groups, which are
allocated a pointer, with which you determines the event handling of the group.
For example, signal errors in an analog input are collected in a group with a pointer
ERR_TR. Passages of limits Low and High (L1 and H1) are another group with a
pointer LIM1_TR. A third group of passages of limits Low low and High high
(L2 and H2) have a pointer LIM2_TR. The event handling, within a group, is the
same in principle, but each individual event has its own text in the presentations.
Each pointer has been allocated a default value on delivery (a norm value). In many
cases this selection is satisfactory and permits you to start the system without further
adjustment.
Figure 22 shows the Event Treat pointers for a digital input.
The pointers are given a number, which points out a standard alarm and event
handling description (on the RTA Board in the Connectivity Server).
The Event Treat pointers 1-18 are, with standard handling, ready for use and cannot
be changed. Event Treat pointers 20-300 can be used by the user, without restriction,
to adapt the event handling to the requirements of the process concerned.
Standard pointers adapted to the individual Object types are given in Appendix A,
Event Treat Elements.
3BSE030340R4101
61
Example 1: Standard Event Text
Figure 22 shows the alarm handling with a Standard event text for a DI signal.
Controller
DI1.2
Digital Input
Operator station
(8.2)
M2IN
1
0
0
0
0
1
4
7
25
27
11
NAME
ACT
BLOCKED
INV
TESTED
ERR CTRL
VALUE
ERR
UPDATED
12
5
6
CONVEYOR2
1
0
0
0
1
1
0
0
0
2
2
2
10
40
38
39
14
23
20
22
21
36
37
DESCR
NORM TR
AL DELAY
PROC SEC
CLASS
NORM POS
RP F CTL
AL BLK
PR BLK
AL P BLK
ERR TR
VALUE TR
DISTURB
MAN ENTR
SELECTED
RP F BLK
AL UNACK
18
8
9
17
16
E3
Group Alarm
EVENT2
Event Treat
1
2
3
4
5
6
7
8
(25.2)
AUDIBLE
AL PRIO
AL TOBLK
AL FRBLK
PERSISTB
TEXT TOB
TEXT FRB
TEXTCOMB
S2
Event Texts
S3
Property Texts
Figure 22. Linkage Between Data Base Elements
62
3BSE030340R4101
ERR_TR and VALUE_TR are pointers to elements in the Event Treat data base in
the operator station. In this example, both ERR_TR and VALUE_TR point at
EVENT2.
The data base element EVENT2 has the following properties, see also Appendix A,
Event Treat Elements:
AUDIBLE
1 = audible alarm
AL_PRIO
2 = Priority 2
AL_TOBLK
N = acknowledgment required at alarm
AL_FRBLK
Y = blocking of acknowledgment when the alarm returns to its

normal status
PERSISTB
N = remaining alarm persists in the list despite acknowledgment
TEXT_TOB
N = printout with alarm
TEXT_FRB
N = printout when the alarm returns to the normal status
TEXTCOMB 0 = standard property and standard event texts

Appendix B, Event Texts contains the standard texts for alarms and events for DI.
Example 2: User Defined Alarm and Event Text
Following information has been built for the AI signal during the engineering phase
of the controller. The signal has the name K540, the description OIL LEVEL and
measurement range 0 - 1000 liters with alarm limits at 50 and 950 liters.
EN_H2 and EN_L2 are set to 1 to enable alarm handling
ERR_TR points at EVENT4.
LIM_1_TR is set to 0, that is no event handling.
LIM_2_TR points at EVENT20.
The values are shown in Figure 23.
3BSE030340R4101
63
AI1.1
Analog Input
K540
1
0
L
1000
0
0.10V
0
1S
0
0.1%
1
0
0
0.0
1
950.0
0
850.0
0
150.0
1
50.0
1.0
OIL LEVEL
0
1
0
0
0
0
0
0
0
0
0
0
0
4
0
20
1
21
24
3
5
4
7
9
X1
10
8
43
44
52
59(3).109
59.74
59.70
59.75
59.71
59.76
59.72
59.77
59.73
59.78
2
54
27
57
55
56
28
34
40
47
48
37
39
38
53
59.79
59.80
E4
NAME
ACT
BLOCKED
UNIT
RANGEMAX
RANGEMIN
CONV PAR
LIN CODE
SCANT
FILTER P
DEADB
OVF CTRL
TESTED
ERR CTRL
ERR VAL
EN H2
HI LIM2
EN H1
HI LIM1
EN L1
LO LIM1
EN L2
LO LIM2
HYST
(6.16)
VALUE
OVERFLOW
ERR
UPDATED
19
36
22
23
VALUE>H2
29
VALUE>H1
30
VALUE<L1
31
VALUE<L2
32
DESCR
DEC
DISTURB
NORM TR
MAN ENTR
AL DELAY
PROC SEC
CLASS
H2 R FCL
H1 R FCL
L1 R FCL
L2 R FCL
ER R FCL
RP F BLK
AL BLK
AL UNACK
PR BLK
SELECTED
AL P BLK
ERR TR
- -- -- -- -- -- -LIM 1 TR
LIM 2 TR
35
25
49
33
26
Group Alarm
Figure 23. Data Base Element Analog Input
64
3BSE030340R4101
As presented in Appendix A, Event Treat Elements, EVENT4 has the following

properties:
AUDIBLE
1 = audible alarm
AL_PRIO
2 = Priority 2
AL_TOBLK
N = acknowledgment required at alarm
AL_FRBLK
Y = no acknowledgment required when the alarm returns to its

normal status
PERSISTB
N = remaining alarm persists in the list despite acknowledgment
TEXT_TOB
N = printout with alarm
TEXT_FRB
N = printout when the alarm returns to the normal status
TEXTCOMB 24 = standard property text

No pointers are set for H1 and L1. EN_H1 and EN_L1 are set to 0 since no warning
limits (H1 and L1) are set in the controller.
LIM _2_TR points at a data base element, EVENT20, in the Event Treat data base
on the RTA Board.
Define the alarm and event text for EVENT20.
1.
Select the Control Structure in Plant Explorer.
2.
Select the Network, Node, and then the RTA Board object.
3.
Select the RTA Board Control aspect and when it is started, select the RTA
Board Configuration tab.
3BSE030340R4101
65
Figure 24. RTA Board Configuration

4.
Click on the Start Config button. This will startup the On-line Builder tool
which is used for the configuration of the RTA Board.
5.
MDB EVENT20 and press <CR>. The data base element is displayed on the
screen.
6.
66
Enter the values as shown in Figure 25.
3BSE030340R4101
EVENT20
Event Treat
1
2
NO
YES
NO
NO
NO
5
1
2
3
4
5
6
7
8
(25.20)
AUDIBLE
AL PRIO
AL TOBLK
AL FRBLK
PERSISTB
TEXT TOB
TEXT FRB
TEXTCOMB
S2
Event Texts
S3
Property Texts
Figure 25. Changes in the Data Base Element EVENT20

The properties in the first part of EVENT20 are the same as for EVENT4 that
ERR_TR points at. Another TEXTCOMB is used as property and event texts
shall be user defined and not standard.
When you define the event and property texts, take note that the events are
linked to predefined lines in the segment Event Texts and Property Texts. These
lines are listed in the table for standard event texts for AI
(see Appendix B, Event Texts).
Since only the LIM_2_TR pointer is of interest, it is selected in the following
table:
Table 5. Standard Texts for the Pointer LIM_2_TR
Event
Pointer
Standard
Line
property text no
Standard
Event text
Line
no
Upper limit H2 exceeded LIM_2_TR
Limit H2
Alarm
Upper limit H2 re-entered LIM_2_TR
Limit H2
Normal
Lower limit L2 exceeded
LIM_2_TR
Limit L2
Alarm
Lower limit L2 re-entered LIM_2_TR
Limit L2
Normal
3BSE030340R4101
67
The property texts Limit H2 on line 1 and Limit L2 on line 2 shall be changed
to Full and Empty. The standard event text Alarm on line 1 and 2 shall be
changed to 950 l and 50 l (liters), respectively.
The standard event texts on line 3 and 4 shall be the same. These texts shall be
entered in EVENT20.
7.
Expand Event Text, and enter the text in accordance to the following:
EVENT20
Event Treat
S1
950 l
50 l
Normal
Normal
9(1)
9(2)
9(3)
9(4)
9(5)
9(6)
9(7)
9(8)
9(9)
9(10)
9(11)
9(12)
9(13)
9(14)
9(15)
9(16)
S3
(25.20)
Base part
EV1
EV2
EV3
EV4
EV5
EV6
EV7
EV8
EV9
EV10
EV11
EV12
EV13
EV14
EV15
EV16
Property Texts
Figure 26. Population of Segment S2 in the Event Treat Element
68
3BSE030340R4101
8.
Expand Property Texts, and enter the text according to the following:
EVENT20
Event Treat
Full
Empty
S1
Base part
S2
Event Texts
10(1)
10(2)
10(3)
10(4)
10(5)
10(6)
10(7)
10(8)
10(9)
10(10)
10(11)
10(12)
10(13)
10(14)
10(15)
10(16)
(25.20)
PRTE1
PRTE2
PRTE3
PRTE4
PRTE5
PRTE6
PRTE7
PRTE8
PRTE9
PRTE10
PRTE11
PRTE12
PRTE13
PRTE14
PRTE15
PRTE16
Figure 27. Population of Segment S3 in the Event Treat Element

9.
Save the RTA Board configuration according to the following steps:

a.
Go to the Control Structure, Network, Node, and RTA Board object.
b.
Select the RTA Board Control aspect and the RTA Board Configuration
tab.
c.
Click the Save Config button.
The configuration for the event handling for the AI signal is now complete.
3BSE030340R4101
69
Defining event filter on node level
Defining event filter on node level

It is possible to filter alarm and events to be sent from selected controllers on a
MB300 network to certain connectivity servers. This can be useful when;
Multiple connectivity servers are connected to the same MB300 network.
Only a selection of controllers connected to a MB300 network are included

into a 800xA system.
Instruction how to configure Event filter on Node level.

This function is configured on the RTA board in the connectivity servers.
Follow the steps below:
70
1.
Start the RTA board configuration from the RTA Board Control aspect.
2.
Create one instance of the data base element NODE_DESCR for each
controller node you want to prevent from sending events to this RTA board.
Command: CRDB NODE_DESCR.
3.
The following terminals should be defined:

NETW_NO Network number. For redundant networks, specify one of the
networks.
NODE_NO Node number for the controller node to be filtered.
EVENT 1 = Filter is active.
4.
When all NODE_DESCR elements are defined, terminate the RTA board
configuration session and start a RTA Board Backup (also from the RTA Board
Control aspect).
5.
Restart the RTA board from the RTA Board Control aspect.
6.
Now the configuration is completed for this connectivity server. In case

redundancy is configured for this you need to repeat the configuration on the
redundant connectivity server.
7.
Restart the concerned controllers to make the changes take effect.
3BSE030340R4101
Section 5 Time Tagged Data (TTD)

Configuration
The configuration of TTD is based on the History Configuration Aspect System
which is an integrated part of IndustrialIT 800xA System. This chapter describes
mainly the Aspect Categories for TTD. The History Configuration Aspect System
user interfaces in general are described in detail in the IndustrialIT 800xA System,
Creating Time Tagged Data (TTD) Logs

The AC 400 Series Controllers have a Historical logging feature called
Time Tagged Data (TTD). The framework for this, called log groups, must be
defined during the Controller Engineering phase. Adding logs to the log groups can
then be made from the workplace.
Before going into the details on how to create the TTD logs in the controllers,
here is a short description of some of the terms and functionality of the
AC 400 TTD logs:
A log is a collection of time stamped (tagged) data.
t1
v1
t2
v2
tn
vn
tx = time x
vx = value at time x
Log
Figure 28. A Collection of Time Stamped (tagged) Data

The process or system object from which the data originates is called the data
source.
3BSE030340R4101
71
Creating Time Tagged Data (TTD) Logs
Section 5 Time Tagged Data (TTD) Configuration
A log also contains information about the data source.

Data
Source
Source
Info
t1
v1
t2
v2
tn
vn
Log
Figure 29. Information About the Data Source

A log is always part of a log group, one log group in TTD can manage up to 127
logs. There are up to 15 log groups. The logs sequence number within the log group
is called log index. The log group keeps the important parameters, storage interval
and storage size (in controller documentation storage size is called log period)
common to all logs in the log group.
The following History Configuration Aspect System user interfaces, which are
specific for 800xA for Advant Master, are described below:
The TTD Source Aspect
The Log Template aspect, the TTD log tab
The TTD Node Configuration aspect, three views
The Log Configuration aspect, the TTD log tab is the same view as the
Log Template aspect.
History Primary Logging should preferably be done by using TTD as data source.
TTD causes much less impact on the system than OPC logging on a cyclic rate.
If a process object is used directly as data source, it is not supported to have faster
sample time than 9s.
Always use 9s sample time for the primary log when a sample time faster than 2
min are wanted. Sample times from 2 min and upwards can be used in primary
OPC logs without causing load problems in the system.
Too heavy History logging may cause unnecessary load in the control network
and controllers in such a way that the operator interface may get slow, or even
stops working properly.
72
3BSE030340R4101

The Configuration Wizard creates this aspect when adding an RTA board.
The aspect defines the service groups for TTD Config Source and TTD Data
Source. TTD Source is placed on the MB300 Network object and does normally not
need to be changed.
Figure 30. TTD Source Aspect
The Log Template Aspect

A Log Template is a re-usable template representing one log group. If you modify
an existing Log Template, the changes will affect existing logs that have been
created using that Log Template.You define the Log template via the Log Template
aspect.
To create this aspect you preferably invoke an upload from the Synchronize View
on TTD Node Configuration aspect. This creates a Log Template aspect for each
TTD log Group on the corresponding AC 400 Series Controller object.
You can also create a new Log Template aspect manually by adding a new History
Log Template object in the Library Structure. This method requires knowledge of
how the TTD log groups are configured in the controller.
3BSE030340R4101
73
The aspect has two tabs:
The Log Definition tab
The TTD Data Collection tab
Property log Template area
You select the log to define in the Property log Template area on the left side.
You can add new Log templates by clicking the Add button and delete
Log templates by clicking Delete. You quit the Log template definition without
storing anything by clicking Cancel.
You save the Log template definition by clicking the Apply button. On-line help is
available by clicking the Help button.
Log Definition Tab
Figure 31. Log Template - Log Definition Tab
74
3BSE030340R4101
Log Name
Enter the log name in this field. We recommend that you include the following parts
in the name:
TTD for TTD logs
the storage interval for the log (30s)
the total log capacity (2h) in the log template name.
This makes it easier to find the correct log template.

Log Type
Log type is set to Direct for primary logs, and Hierarchical for hierarchical logs.
The Log type and Source definitions are defined when you create the log template.
TTD Data Collection Tab
Figure 32. Log Template - TTD Data Collection Tab

TTD Log Storage Interval
This is the storage interval for the TTD log in the controller. Select the log storage
interval for the TTD log in the drop-down menu.
3BSE030340R4101
75
TTD Node Configuration Aspect
TTD Log Value Count
This is the storage size (number of stored values) in the TTD log in the controller.
The Capacity (in time) is automatically calculated and presented to the right of the
entry field.
The TTD log storage interval and the TTD log value count must match a
Log Group in the controller.
History Log Value Count
This is the storage size (number of stored values) in the history server. The default
size of the History log is double the size of the TTD log. If you want to change the
History log size, you enter the number of stored values in the History log in the
Value Count field. The Capacity (in time) is automatically calculated and presented
to the right of the entry field.

TTD Node Configuration is an aspect of the AC 400 Series Controller object in
Control Structure. It has three different views:
76
Main View - presents the TTD logs in the controller
Controller View - presents the structure of the Log Groups
Synchronize View - used for upload and download of TTD configurations.
3BSE030340R4101
Main View
The main view of the TTD Node Configuration aspect presents the TTD logs in the
controller.
Figure 33. TTD Node Configuration, Main View

Object
Name of the object that has a property included in a TTD log.

Property
Object property that is included in the TTD log.

Enabled
Indicates if the TTD log is enabled or disabled in the History server.

Mapped
Indicates if the TTD log is mapped to a TTD Log Group (in the controller).
This will normally be set to Mapped. Unmapped indicates that a download to the
controller is required.
3BSE030340R4101
77
Log
TTD log name (defined in the Log Template aspect that represents the Log Group)
that the object property is included in.
Controller View
The Controller View of the TTD Node Configuration aspect has two lists:
one overview list with all groups in the controller node, see Figure 34.
one list for a selected Log Group, see Figure 35.
The following columns are presented when you have selected the controller node in
the left window:
Figure 34. TTD Node Configuration: Controller View, Log Groups
78
Log Group No - Log Group number 1 - 15.
Log Group Name - The name of the TTD Log Group.
Interval - The storage interval displayed in suitable time scale.
Capacity - The number of stored data items before they are overwritten
(circular log).
3BSE030340R4101
The second layout of the Controller View, showing the details for a selected
Log Group has the following columns in the right window, see Figure 35.
Figure 35. TTD Node Configuration: Controller View,

Details About one Log Group
Index - Index in the Log Group 1- 127.
Object - The name of the logged object.
Property - The name of the logged object attribute.
Treatment - The logged value could be calculated from the real-time value.
Four calculations (treatments) are available: Mom (momentary), Mean
(average), Max (maximum) and Min (minimum). The treatment should always
be Mom for primary logs.
Source - Source shows if the log is primary or hierarchical. Only primary logs
are handled by history server, hierarchical logs are ignored.
Active - The state of the log - Active or Not active (shown as blank in the list).
The header above the list of logs contains information about Log group address,
the storage interval and capacity.
3BSE030340R4101
79
Synchronize View
The Synchronize view of the TTD Node Configuration aspect has the following
functionality:
Upload of the current TTD groups and logs from the selected controller.
Download of new TTD log configurations into the controller.
Upload of TTD Logs from Controller
To load the existing TTD logs into the History Configuration Aspect System,
you use the synchronization view of the TTD Node Configuration aspect.
The upload process creates all necessary Log Template and Log Configuration
aspects.
Click Upload and wait.The progress is presented in the text window, see Figure 36.
Figure 36. Upload of TTD Logs
80
3BSE030340R4101
The result of a completed Upload is as follows:
A Log Template aspect for each type of TTD Log Group is created on the
corresponding AC450 and AC410 Controller object.
A Log Configuration aspect is created on each logged object. It has the primary
log being a TTD log configured according to the information read from the
controller and with an extension into a corresponding hierarchical log twice as
large as the primary log. To extend it, change the corresponding Log template
and it will affect all logs belonging to that Log Template.
The hierarchical logs are disregarded.
Download of new log configurations into the Controller
You can also do Download for an individual log from the Log configuration
aspect on the process object, see The Log Configuration Aspect on page 82.
To download and activate new TTD logs you can use the synchronization view of
the TTD Node Configuration aspect. Click Download to the right and wait.
The Match Existing dialog box appears, see Figure 37.
Figure 37. Match Existing

Click Yes for logs that have not been mapped to a TTD log in the controller.
The download function will try to find a suitable log in the controller to map the
downloaded log to. Click No when a new log will be created in the controller for
each configured un-mapped log.
3BSE030340R4101
81
The Log Configuration Aspect
The progress is logged in the text window, see Figure 38.
Figure 38. Downloading the new TTD logs

When the download is finished, you can check the result in the log on the screen but
you can also bring up the Main View to check specific logs.

The Log Configuration aspects are placed on the objects that should be logged.
It defines which properties on the object to log, and how to log (by referring to a
Log Template).
To configure Log Configuration, follow the steps below:
82
1.
Add a new Log Configuration Aspect on the desired process object.
2.
Open the aspect.
3.
Select Add Property Log, and you will get the New Property Log dialog box.
4.
Choose the property to log, for example VALUE, from the list of properties and
selects a template in the Template box.
5.
Press OK and then Apply.
6.
In the Logged Properties: area, browse to the newly created TTD log and
select the TTD Data Collection tab.
3BSE030340R4101
7.
Click on the Download button. Now you should see that the Log Group No:
and Log No: fields are updated. The log will be put in the first available slot in
a group matching the storage interval.
Figure 39. Log Configuration Aspect

In the Presentation tab you can define some attributes for trend display such as
engineering units, number of decimals, maximum and minimum presentation range.
The Status tab presents each time stamped data in table form.
You can also create Log Configuration by invoke Upload from the Synchronize
View on TTD Node Configuration aspect. This action creates Log Configuration
aspects for all objects included in the logs.
3BSE030340R4101
83
Working with TTD logs

We have now discussed each configuration aspect. In this section you will find three
examples of how to make the configuration. The assumption is that you have a
Control Structure for an AC 400 controller and that the controller has configured
TTD log Groups with some logs.
1.
The first example shows how to view the current TTD logs in the controller.
2.
The second example shows how you prepare the configuration of new
TTD logs by creating Log Templates for them.
3.
The third example utilizes the Log templates when you create new logs and
download them to the controllers.
The recommended method to configure the History Aspect System if the
controller already is configured by terms of TTD groups and logs is however to
perform Upload. This is done from the Synchronize View of the TTD Node
Configuration aspect of the controller objects. This action creates all necessary
objects and aspects.
84
3BSE030340R4101
Example 1: View the TTD logs in the Controllers
1.
Go to the Control Structure in Plant Explorer.
2.
Click on the object representing the controller you want to work with.
Select the TTD Node Configuration aspect.
3.
Select the Controller View. See Figure 40.
Figure 40. TTD Node Configuration: Controller View, Log Groups

To the left you see a list with the existing Log Groups, and to the right a storage
interval (Interval) and storage size (Capacity) for each Log Group. If you select one
of the groups you can see the existing logs in that group to the right, see also
Figure 41.
3BSE030340R4101
85
Figure 41. TTD Node Configuration: Controller View, details about

one Log Group
Example 2: Create a Log Template for a TTD log
We want to create a log template for a TTD log with storage interval 30 seconds and
a storage size of 2 hours (240 values). We already know (from example 1) that a
suitable TTD log group exists in this controller and there are at least one free index
in the group. The TTD log shall be stored and extended in the History Configuration
Aspect System to a storage capacity of 4 hours.
Furthermore, a hierarchical log shall be created within the History Configuration
Aspect System which aggregates the primary information into an average, stored
with 1 minutes interval over 1 day (1440 values) aggregated as average.
86
1.
Select the Library Structure in Plant Explorer.
2.
Create a new object of the History Log Template type. Give it a proper Name
and Description. Let the name reflect to the TTD log template and the storage
interval and size. It makes it easier to select a log template during log creation
3BSE030340R4101
It is recommended to save the log template in the Library Structure,

History Log Template Object Type.
Figure 42. Creating the Log Template Object

3.
3BSE030340R4101
An aspect of the category Log Template is created by default. Select it in the

preview window or as a pop-up (double click on it).
87
Figure 43. Log Template Aspect

4.
Start creating the new TTD log. Select Property Log and click Add.
See Figure 43. The New Log Template dialog is displayed, see Figure 44.
Figure 44. Create New Log of TTD type
88
3BSE030340R4101
5.
Select TTD in the Data Source drop-down menu. In the Log Type area, select
the Direct radio button. Click OK to save the settings.
Figure 45. Creating TTD Log Templates

6.
Enter the name of the new TTD log (TTD_30s in the example above).
Name the logs according to the type of log (TTD in this case), and the storage
interval (30s). See Figure 45.
7.
Select the TTD Data Collection tab and enter the TTD log storage interval
30 seconds and a storage TTD log value count of 240 values (2 hours
capacity), see Figure 46.
3BSE030340R4101
89
The storage size in History Aspect System is defined by History Log Value
Count. Choose twice the size of the TTD log, in this case 480 values (4 hours
capacity).
Figure 46. Log Configuration - TTD Data collection
90
8.
Save the TTD Data Collection parameters (click Apply) and go back to
the Log Definition tab to enter the definition of one hierarchical log.
9.
Select the TTD_30s log and click the Add button and OK button.
3BSE030340R4101
Figure 47. Creating the Hierarchical Log

10. Enter the following for the hierarchical log and save it:
3BSE030340R4101
Log name: SecTTD_1m_24h
Log type: Hierarchical
91
Figure 48. Hierarchical Log, Filling in Capacity

11. Select the Data Collection tab, enter the following data and click Apply.
Aggregate: Time Average
Exception Deviation = 0
Bad Data Quality Limit = 0
Min Time: 5 minutes
Max Time: 5 minutes
Storage Size (Time): 24 hours
The log template is now finished and ready to use.
92
3BSE030340R4101
Example 3: Create TTD logs from workplace and Download them
1.
Go to the Control Structure in Plant Explorer.
2.
Click on the object representing the controller that you want to work with.
Browse down to the process object that shall be placed in the TTD log.
3.
Select the process object. Add the Log Configuration aspect. Give it a proper
Name and Description and save it.
4.
Select the aspect and then - in the preview area - select the object and click
Add Property Log.
Figure 49. New Property Log Dialog

5.
3BSE030340R4101
Select VALUE in the Property list and the

TTD_LogTemplate_30s_24h:Log Template in the Template drop-down
menu. Click OK.
93
6.
The preview area now looks like Figure 50.
Figure 50. Log Configuration - presentation
94
3BSE030340R4101
7.
Go to the Presentation tab and enter the following. Save it by clicking Apply.
Engineering Units: KPa
Normal Maximum: 200
Normal Minimum: 0
Decimals: 2
Display Mode: Interpolated.
8.
Repeat Step 2 to Step 7 for each log that you want to create.
9.
Now it is time to download all the new logs to the TTD logs in the controller.
Click on the object representing the controller. Select the TTD Node
Configuration aspect in the aspect list.
10. Select the Synchronize view and click Download. Select No in the Match
Existing dialog box that appears. Study the results on the screen as the
download proceeds:
Figure 51. Downloading new TTD Log Definitions

11. If there were no error messages displayed during download, the TTD logs
should now be mapped to a Log Group in the controller and started. You can
bring up the Main view and study all TTD logs.
See TTD Node Configuration Aspect on page 76.
3BSE030340R4101
95
96
3BSE030340R4101
Section 6 Quick List Configuration

Quick List User Interface
Figure 52 shows the Quick List configuration view. Detailed information about the
different parts and how to configure and operate the Quick List, is described in the
following sections.
Figure 52. Configuration View - Quick List
3BSE030340R4101
97
Configure the Quick List

The Quick List aspect can be pre-configured with search criteria. For example, one
aspect can be configured with search criteria for a specific Process Section.
If an aspect is pre-configured, the search will start automatically when the aspect is
opened and the result is presented in the Quick list main view.
How to Configure the Quick List Aspect
The Quick List aspect is created and handled as other aspects in the
Operator Workplace.
If the Quick List aspect is created on an object in a structure other than the
Control Stucture, you must add a Quick List Data Source aspect to the object. In
the configuration view of the Quick List Data Source aspect you choose provider,
see Figure 53.
Figure 53. Quick List Data Source Aspect

The following tutorial will guide you through the different steps in configuring the
Quick List.
98
3BSE030340R4101
1.
In the Plant Explorer, create a new Quick List aspect on an object. The main
view with an empty list is shown as in Figure 54.
Figure 54. Quick List Main View

2.
As this aspect is new it does not hold any configuration data (i.e no search
criteria is defined) and the search is not automatically started. We have to
configure some search criteria first.
3.
Select the config view from the tool bar panel on top of the aspect window.
The configuration view is shown as in Figure 55.
3BSE030340R4101
99
Figure 55. Quick List Config View
100
4.
Now, configure a simple search criteria. Suppose that you want to know which
Digital Input and Digital Output signals that are in an error state (Error flag set)
and alarm state in the nodes with controller node 73 and 74.
5.
Start by checking the check box for DI and DO in the Object Type area.
6.
Those properties that are common for these two object types are shown with
green color (Red colored are not common, and are not possible to select in the
Properties area). See Figure 56.
7.
Click on the property for error state (ERR) in the Properties area and the text
ERR followed by a = appears in the Property1 text field.
8.
Type 1 or TRUE in the Property1 text field.
9.
Click on the AL_UNACK property in the list and type 1 or TRUE to the
Property2 text field (press CR).
3BSE030340R4101
10. Change the text fields Node1 to 73 and Node2 to 74. Click the Apply
button to store the configuration. Now the configuration should look like
Figure 56.
Figure 56. Quick List Configuration example.

If you use the property STATUS_DO / you have to write a value that is a
hexadecimal. For example: /H:5
3BSE030340R4101
101
11. To present the result, just change to the Main view and the search will start
automatically. See Figure 57.
Figure 57. Main View

The search can be stopped by clicking the Cancel button or selecting the config
view again. A text string at the end of the list indicates that the search is completed
on the two nodes. By clicking the Print button, it is possible to send a printout of the
search result to a printer connected to the system. A new search is started by
clicking the Search button.
If the service is down or the RTA board is not properly configured you get the
error message: Connect Fail.
An illegal search option will give the message: Syntax of entered property
match value is illegal.
102
3BSE030340R4101
Configuration Examples
Example 1
List all Analog Inputs (AI) of process section 2 in the nodes 5,6, and 7, which has
the string Temp in position 7-10 in the name and are in a state of alarm and have
the alarm processing blocked.
1.
Click the check box for the AI in the Object Type List. The properties of AI
which are available for searching are displayed in the list view for available
properties.
2.
Position the mouse pointer on the Section1 text field and enter the value 2.
3.
Enter the values 5 to 7 in the Node1 to Node3 text fields.
4.
Select the Object name text field and enter ??????Temp. The six question
marks mean that the first six characters may be any alphanumeric characters.
Move the cursor to another field.
5.
Now use the text field for Property1. When an analog signal is in state of
alarm, the flag DISTURB (disturbance) is set high. Specify the conditions you
want for Property1 - Property4:
Click on the label DISTURB in the list of available properties. The text
DISTURB = is copied to the first free text field. Add the value 1 or
TRUE to the text field.
6.
The alarm blocking property is called AL_BLK and has the number 4. Enter
this property in the Property2 text field by clicking on the label AL_BLK in
the property list and add 1 to the Property2 text field.
7.
Now all the necessary parameters of the list are defined and the search criteria
can now be activated. Click the Apply button to save the configuration data.
3BSE030340R4101
103
Example 2
List all the motors in node 7, 8 and 9, process section 3, class 1 or 2, which are in
any of the following modes: LOCAL, TEST or STAND BY. All motor controls have
been implemented by using the object type MOTCON.
1.
Click on the check box representing MOTCON in the list for object types.
A checked box signifies an active parameter. The accessible properties of
MOTCON appear in the list of available properties. Select the Node1 text field
and enter the value 7. Move cursor to the Node2 text field.
2.
Enter the value 8 in the Node2 text field. Move cursor to the Node3 text field
and enter the value 9.
3.
Move the cursor to the Section1 text field and enter the value 3. Move the
cursor to the Class1 text field and enter the value 1. Move the cursor to the
Class2 text field and enter the value 2.
4.
In order to ascertain whether the motors are in any of the modes, LOCAL,
TEST or STAND BY, look at the block item IND2_MOTCON containing these
indications.
5.
See the description of MOTCON in AdvaCommand User Interface Reference

Manual. The block item is defined as Property 1. In this way, an OR condition
is created.
On the other hand, if the three indications IND2_01, IND2_02 and IND2_03
were specified one by one as Property 1, Property 2 and Property 3, an AND
condition would be specified. In this case, the block item IND2_MOTCON is
to have the value HE, which corresponds to the three indications. Specify the
property like this.
6.
Move the cursor to the list with available properties and click on the label
IND2_MOTCON. The text IND2_MOTCON // will be copied to the
first free text field for Property 1 - Property 4 and the input focus will be
moved to the actual text field. Add the value HE to the text fields.
Click on the Apply button to save the configuration data.

If a single motor is in STAND BY at the same time it is in LOCAL
mode, two message lines appear on the list. This type of block item
condition generates a message line for every high bit that
corresponds to the actual value in the data base.
104
3BSE030340R4101
Section 7 National Language Support

Configuration
The National Language Support (NLS) is used for translation of application data.
It will translate the text to the same language as selected in the Regional Options in
Windows. The target language must also be set in Regional Settings in Windows
Explorer and in Visual Basics.
Application engineering can be performed directly in the local language, but the
resulting application data will not be reusable in other languages. To ensure that it
is possible to translate the application data, all engineering shall be made with
Regional Options in Windows set to English (United States).
Object and Aspect Names and Graphic Aspects
Translation of Object and Aspect name texts as well as Graphic aspects texts,
are made according to the Operator Workplace National Language Support.
See IndustrialIT 800xA System, Operator Workplace Configuration.
Alarm and Event Texts
Alarm and Event texts are translated in the controller according to Advant Master
National Language Support. Languages that can be used are English, German and
Swedish.
Select language before starting the translation. Otherwise, the text will be lost.
The figure below (Figure 58), displays how to select language.
3BSE030340R4101
105
Section 7 National Language Support Configuration
Figure 58. Select Language in Advant Master NLS

Character Conversion
When connecting to controllers using national characters this setting will convert
the 7-bit representation to the correct 8-bit. The conversion applies to object
properties: NAME, DESCRIPTION and UNIT.
106
English (No Conversion): Characters [,\,],{,|,},~ will not be

changed.
Swedish: Characters [,\,],{,|,},~ areconverted to

,,,,,,~.
3BSE030340R4101
German: Characters [,\,],{,|,},~ are converted to

,,,,,,.
The change of character conversion will also load a number of predefined files to
EVENT_TREAT, TEXT, CLOCK_SYNCH etc.
It is strongly recommended that this setting is done before commencing the
engineering and then not be changed.
Event Treat According to NLS

Since the Online Builder is not an option to the Operator Workplace, you need
the Engineering Studio to do the translation.
Process Alarm and Process Event texts
A process alarm or process event is presented by its name, description, property text
and event text in a list. The translation to local language of the property and event
text are described in this section.
The property and event texts can be either user defined or standard. The user
defined property and event texts are stored in database elements of type
EVENT_TREAT. The standard property and event texts are store in the database
concept TEXT. Both are located on the Real Time Accelerator Board (RTA).
User defined property and event text
The user defined property and event texts for standard event handling are stored in
EVENT8 - EVENT14, EVENT16 - EVENT18.
The property and event text for the user defined event handling are stored in
EVENT20 - EVENT300.
1.
Open the RTA Board Configuration window
2.
Go to the Control Structure > Network >Node and RTA Board object.
3.
Select the RTA Board Control aspect and its RTA Board Configuration tab.
3BSE030340R4101
107
4.
5.
Click on the RTA Board Config button.
Dump the source code for the EVENT_TREAT elements to the volume
SRCE: which corresponds to the directory \Program Files\ABB Industrial
IT\AC400CI\AdvantBase\Data\RTA\Nodes\SRCE in the target system.
DUDBS SRCE:EVENT,SEL=EVENT8 >X <CR>

where X is the number of the last EVENT element with defined property
or event text that shall be translated to local language.
The number of created files depends on how many EVENT_TREAT

elements that have been dumped. The created files are named
EVENTxx.BA.
Edit the source code files by opening the file in the text editor, choose File >
Open...
Figure 59. Event Text

6.
108
Save the changes and exit from the text editor by selecting File > Save > Exit
3BSE030340R4101
7.
Load the modified source code files by typing:
8.
TRDBS SRCE:EVENTxx.BA <CR>
Take a backup of the RTA Board by clicking the RTA Board Backup button.
Standard Property and Event Text
Translation to a national language should be made in a logical dump of the TEXT

concept. You must make a logical dump manually as follows:
1.
Open the RTA Board Configuration window.
2.
Go to the Control Structure > Network > Node and RTA Board object.
3.
Select the RTA Board Control aspect and the RTA Board Configuration tab.
4.
5.
Enter in RTA Board Configuration window

DUDB SRCE:<file name> for example DUDB SRCE:STANDARD.
Max length of the file name is 8 characters. Answer the questions as follows:
DUMP FROM LF (<lfnr>[,<dest lfnr>]/Q) = 31
INCLUDE DYNAMIC PROPERTIES (Y/N/Q) = N
INCLUDE STRUCTURE OF DYNAMIC PROPERTIES (Y/N/Q) = N
INCLUDE ACTION PROPERTIES (Y/N/Q) = N
MESSAGE TO LOADER, COMPLETE WITH EMPTY LINE!

MESSAGE = Dump of standard property and event text
DUMP START AT RECORD (<recnr>//*/Q) = 2
DUMP STOP AT RECORD (<recnr>//*/Q) = 278
ENTER PROPERTY SELECTION DIALOG (Y/N/Q) = N
The dump is stored in directory \Program Files\ABB Industrial

IT\AC400CI\AdvantBase\Data\RTA\Nodes\SRCE. The created file name is <file
name>.LD.
3BSE030340R4101
109
Below is an extract of the dump. The dump starts with some headlines which must
not be changed. The text to be translated starts with line
][ 2 0 0 0 5 Value 0 where 2 is the record number, 0 0 0 are pointers which shall not
be changed. 5 is the number of characters in the property or event text. Thereafter
follows the text to be translated. The text and the number of characters can be
changed using the text editor.
][ A 201
SRCE:STANDARD.LD
Midas Data Base Logical Dump
Copyright ASEA
-------------58 Selective dump of logfile 31 created 2002-04-18 14:07:20
40 Dump of standard property and event text
5 \*+-/
0 31 0 FFFFFFFF 5
0 2 0 20 0 FFFFFFFF 1
0 3 0 20 0 FFFFFFFF 1
0 5 0 20 0 TFFFFFFF 1
0 6 0 40 0 FFFFFFFF 1
0 7 0 40 0 FFFFFFFF 1
][ 2 0 0 0 5 Value 0
][ 3 0 0 0 7 Sig.Err 0
][ 4 0 0 0 6 Lim H2 0
][ 5 0 0 0 6 Lim H1 0
][ 6 0 0 0 6 Lim L1 0
][ 7 0 0 0 6 Lim L2 0
][ 8 0 0 0 5 Value 0
][ 9 0 0 0 8 Printout 0
][ 10 0 0 0 5 Alarm 0
][ 11 0 0 0 6 Update 0
][ 12 0 0 0 8 Disturb. 0
][ 13 0 0 0 7 Opening 0
][ 14 0 0 0 7 Closing 0
110
3BSE030340R4101
][ 15 0 0 0 8 NotClose 0
][ 16 0 0 0 8 Not Open 0
............and so on.........
The dump contains all records from 2 to 278. However some of the texts are not
longer used and no translation is necessary. The records to be translated are:
record no 2 - 132, 150 - 221, 232 - 233, 238 - 239 and 261 - 278
Edit the dump file by opening the file in the text editor, choose File > Open...
The file is found in directory \Program Files\ABB Industrial
IT\AC400CI\AdvantBase\Data\RTA\Nodes\SRCE.
Figure 60. Standard Text

6.
Save the changes and exit from the text editor by choose File > Save > Exit
The new dump must be loaded into the target system:

LODB SRCE:<file name> for example LODB SRCE:STANDARD
3BSE030340R4101
111
Answer the questions as follows:
7.
TARGET IS NOT IN CONFIGURATION MODE! PROCEED? (Y/N/Q)

=Y
LOAD MODE (L/L*/I/I*/P/P*/S/S*/Q) = I
RECEIVER LF = 31
ENTER RECORD SELECT LOAD (Y/N/*/Q) = N
LOAD START AT RECORD (<recnr>//Q) = 2
Try again. (Y/N/Q) = N
System Alarm texts
An event in the System Alarm List has the following layout:
Figure 61. System Alarm List

The text row includes the following:
112
Date and time of the event.
System Part text which is a description of in which subsystem the error

occurred.
System Part Description which gives the operator more details about the event.
Net and node.
3BSE030340R4101
Translation to a national language must be made by using the database source code
facilities for dumping and loading the TEXT concept against the Windows
environment.
Make a logical dump as follows:
1.
2.
3.
Select the RTA Board Control aspect and the RTA Board Configuration tab.
4.
5.
3BSE030340R4101
DUDB SRCE:TEXT for example DUDB SRCE:TEXTENG. Max length

of the file name is 8 characters. Answer the questions as follows:
DUMP FROM LF (<lfnr>[,<dest lfnr>]/Q) = 31
INCLUDE DYNAMIC PROPERTIES (Y/N/Q) = N
INCLUDE STRUCTURE OF DYNAMIC PROPERTIES (Y/N/Q) = N
INCLUDE ACTION PROPERTIES (Y/N/Q) = N
MESSAGE TO LOADER, COMPLETE WITH EMPTY LINE!

MESSAGE = Dump of LF31
DUMP START AT RECORD (<recnr>//*/Q) = 280
DUMP STOP AT RECORD (<recnr>//*/Q) = <CR>
ENTER PROPERTY SELECTION DIALOG (Y/N/Q) = Y
2 PROPERTY 2 N
3 PROPERTY 3 Y
5 PROPERTY 5 Y
6 PROPERTY 6 Y
7 PROPERTY 7 N
113
The dump is stored in directory \Program Files\ABB Industrial

IT\AC400CI\AdvantBase\Data\RTA\Nodes\SRCE. The created file name is <file
name>.LD.
Below is an extract of the dump. The dump starts with some headlines which must
not be changed. The text to be translated starts with follow lines:
][ 280 48 10 0 0 0 0 0 0 12 29 0 49
48 PROC I/O ST@3A2@-board errorNet @1A3@ Node @2A3@
280 is the record number.
48 is the number of characters in the text.
10 0 0 0 0 0 0 are pointers which shall not be changed.
12 is a pointer, points to the character after the System Part (PROC I/O ST + 1)
29 is a pointer, points to the character after the System Part Description (PROC I/O
ST@3A2@-board error + 1).
0 is a pointer which shall not be changed.
49 is a pointer, points to the character after the Net and Node part (PROC I/O
ST@3A2@-board errorNet @1A3@ Node @2A3@ + 1)
Thereafter follows the pointer 48 and the text to be translated. The text, the number
of characters and the pointer in bold can be changed using the text editor.
][ A 201
SRCE:TEXT.LD
Midas Data Base Logical Dump
Copyright ASEA
-------------58 Selective dump of logfile 31 created 2002-04-18 14:07:20
12 Dump of LF31
5 \*+-/
0 31 0 FFFFFFFF 3
0 3 0 20 0 FFFFFFFF 1
0 5 0 20 0 TFFFFFFF 1
0 6 0 40 0 FFFFFFFF 1
][ 280 48 10 0 0 0 0 0 0 12 29 0 49
48 PROC I/O ST@3A2@-board errorNet @1A3@ Node @2A3@
][ 281 50 10 0 0 0 0 0 0 12 31 0 51
114
3BSE030340R4101
50 PROC I/O ST@3A2@-board workingNet @1A3@ Node @2A3@

][ 282 59 10 0 0 0 0 0 0 11 40 0 60
59 REM I/O STError in bus @1I1@ node @2I2@Net @1A3@ Node @2A3@
][ 283 58 10 0 0 0 0 0 0 11 39 0 59
58 REM I/O STBus @1I1@ node @2I2@ workingNet @1A3@ Node @2A3@
][ 284 31 10 0 0 0 0 0 0 7 12 0 32 31 DEV STErrorNet @1A3@ Node @2A3@
][ 285 42 10 0 0 0 0 0 0 7 23 0 43 42 DEV STDevice not readyNet @1A3@ Node
@2A3@
................and so on...........................
There may be parameters in the text. The parameter is replaced in runtime by its
actual value for example net number. A parameter starts and ends with the sign
@. The parameters must be written in the same way as in the original version
(for example @1A3@).
There is a limitation of characters in the text fields. The limit is 12 characters for 8
bit characters for the System Part Text and 28 characters for 8 bit characters for the
System Part Description text. Corresponding values for 16 bit characters (for
example chinese) are 6 characters for the System Part Text and 14 characters for the
System Part Description text.
3BSE030340R4101
115
6.
Edit the dump file by opening the file in the text editor, choose File > Open...
Figure 62. System Alarm Text

7.
Save the changes and exit from the text editor by selecting File > Save > Exit
Load the dump file.

1.
2.
3.
Select the RTA Board Control aspect.
4.
Select the RTA Board Configuration tab and click on the RTA Board Config
button.
5.
116
LODB SRCE:XXX where XXX is the name of the dump.
3BSE030340R4101
Max number of characters for the name is 8 and the characters must be capitals.
Answer the questions as follows:
6.
TARGET IS NOT IN CONFIGURATION MODE! PROCEED? (Y/N/Q)

=Y
LOAD MODE (L/L*/I/I*/P/P*/S/S*/Q) = I
RECEIVER LF = 31
ENTER RECORD SELECT LOAD (Y/N/*/Q) = N
LOAD START AT RECORD (<recnr>//Q) = 280
ENTER PROPERTY CHANGE DIALOG (Y/N/Q) = N
Operator Messages
Use the following steps to translate the Advant Master Operator Messages
1.
3BSE030340R4101
Go to the Library Structure.
117
2.
Open System Messages > Messages, see the figure below.
Figure 63. Operator Messages
118
3.
Drag and drop the AdvDsMasterAdaptor into the Import/Export application.
4.
Follow the instructions from step 3 in the section about Extracting Data,
in IndustrialIT 800xA, System, Operator Workplace Configuration.
3BSE030340R4101
Section 8 Data transfer via OPC DA

800xA for Advant Master supports data subscriptions and write operations towards
process objects via the OPC DA interface in 800xA OPC Client connection.
However the following AC 400 and MP200/1 controller limitations and
recommendations need to be considered to avoid system overload. For detailed
information about the 800xA OPC DA interface see IndustrialIT 800xA, System
Configuration.
OPC Read Operations

Cyclic subscriptions are only supported on process objects for the subscription
times 1, 3 and 9 seconds and not for all properties. If other rates or properties are
selected the RTA board will emulate this by sending repeated demand requests to
the controller which causes much higher load than the cyclic subscriptions. For
performance reasons faster sample times than 9 seconds should be avoided when
possible. The properties that support cyclic subscriptions are listed in Appendix F,
OPC Properties.
3BSE030340R4101
119
OPC Write Operations
Section 8 Data transfer via OPC DA
An overview of the different subscription types supported by the AC 400 and

MP200/1 controllers are described below:
Demand. One data request from the RTA board results in one reply from the
controller.
Cyclic. One data request from the RTA board results in a continuous stream of
cyclic updates from the controller. Supported cyclic rates: 1, 3 and 9 seconds.
Event driven. One data request from the RTA board results in a continuous
stream of event driven updates from the controller.
OPC Write Operations

It is only supported to perform OPC write operations towards DAT objects. There
are no hard limitations on the number of write operations that can be executed.
120
3BSE030340R4101
Section 9 Display Converter

In order to facilitate a smooth and easy migration from AdvaCommand (both Unix
and NT) a display conversion tool is available as a plug-in to the Graphics Builder.
The display conversion tool is used to convert graphic displays from
AdvaCommand of the IndustrialIT products. It is installed together with the 800xA
for Advant Master Extension. The user interface of the display conversion tool is
accessed from the
Add-Ins menu in Graphics Builder.
The display builder package in AdvaCommand is based on a Sherrill-Lubinski
graphic package and the graphics builder in System 800xA is based on ActiveX
Controls. All standard display elements in AdvaCommand are made as ActiveX
based graphic elements in System 800xA. A map file, which maps the
AdvaCommand standard display element to an ActiveX based graphic element, is
available as part of the conversion tool. User defined display elements in
AdvaCommand need to be created as ActiveX Controls in System 800xA and
entered into the map file. This is done once. This map file is re-used for all
conversions of displays to System 800xA.
The display conversion tool does also handle the conversion of static graphic.
If System 800xA is connected to the process, the displays will directly show
dynamic data after a display deployment.
If you have used the AdvaCommand Display Conversion tool in the Graphic
Builder, you have to close it before exit from the Graphic Builder. If you do not
do that but answer Yes on the question, about saving the display, you will get an
application error.
3BSE030340R4101
121
Getting Started
Getting Started
This appendix describes the major steps in display conversion:
1.
Create new graphic elements to replace your own AdvaCommand graphic

elements.
2.
Customize your configuration files.
3.
Edit your converted graphic display.
4.
Test your graphic display.
5.
Deploy or just save your graphic display.
Considerations
Uploading of process objects. Use the MB 300 Upload tool to upload the
process objects from the controllers to the systems Control Structure.
Move the AdvaCommand graphic displays to your hard disk.
To be able to run the Display Converter you must have the Graphics Builder
installed in your workplace.
AdvaCommand graphic displays that were related to special functionality in

the old system, may require that they are aspects of objects with similar
functionality in the System.
Display Conversion
This section gives you a description of the Display Converter.
Add Display Converter as Add-ins to your Graphics Builder

You can add or remove the Display Converter to your Graphics Builder by using the
Add-In Manager, which is accessible from the Add-Ins menu. To add or remove the
Display Converter:
1.
122
From the Graphic Builders Add-Ins menu, select Add-In Manager.
3BSE030340R4101
Create New Graphic Elements to Replace the Previously Created
2.
Select the Display Converter, mark or un-mark the Loaded/Unloaded and

Load on Startup from the Load Behavior section.
3.
When you are finished making your selections, click OK.
Create New Graphic Elements to Replace the Previously Created

AdvaCommand Graphic Elements
Before you convert your AdvaCommand graphic display, you may want to create a
new graphic element or process dialog to replace your own AdvaCommand graphic
element. Once you have created the graphic elements, you add and map those to
the graphic elements configuration file. Then you can convert the appropriate
AdvaCommand graphic element to the new one.
Refer to the IndustrialIT 800xA, Engineering, Graphics for information on how to
create your own graphic elements and process dialogs.
Customize your Configuration Files

The default settings for Display Converter are stored in the configuration files.
All configuration files are plain ASCII files which can be edited by any text editor
(Notepad, Wordpad,.). The content of the configuration files is token-value pair
based. Specific examples follows.
The following configuration files are installed with the Display Converter:
Colors.cnf
Fonts.cnf
Dynamic.cnf
To provide greater flexibility when using these configuration files, you can
substitute the default settings by adding your own configuration files (could be
stored in any directory). You can restore the original configuration file by removing
the corresponding custom configuration file. You can create multiple configuration
files of each type, but you can use only one configuration file at one time. It is
recommended that you decide on one set of configuration files to use throughout
your system to preserve consistency.
3BSE030340R4101
123
Colors.cnf
The Colors.cnf configuration file contains mapping of AdvaCommand color

numbers into RGB values or logical color names. The file contain record entries,
each entry describing one color conversion. Following example shows 3 color
conversions.
{
OSCOLOR:
RED:
GREEN:
BLUE:
{0}
{0}
{0}
{0}
}
{
OSCOLOR: {1}
RED:
{16}
GREEN:
{12}
BLUE:
{11}
}
// Color mapping for the Alarm color
{
OSCOLOR: {127}
LOGICAL: {Alarm}
}
The number which specifies the OSCOLOR is the color index in the colordef.dat on
the Advant operator station, where the RED, GREEN and BLUE is the RGB value
of Operator Workplace. If the LOGICAL is specified it is used as the logical color
name of Operator Workplace. The logical color specification will overrule the RGB
specification.
The Colors.cnf file installed with the Display Converter contain mapping of the
standard OS palette (colordef.dat).
Fonts.cnf
In the AdvaCommand fonts are specified with a short font specification consisting
of two letters FA-FN and two digits 10-60 in step of 10. These font specifications
are connected to real X fonts through a definition file.
124
3BSE030340R4101
The font definition file is placed in the directory:

/products/data/standard/OS/config/
and have the name fontdef.dat.
foundry
weight
set width
points
vertical
resolution
average width
-adobe-courier-bold-r-normal--11-80-100-100-p-60-iso8859-1
font family
slant
pixels
horizontal
resolution
spacing
character set
The first line specifies that font number 11 shall be a courier font.The font
specification is the standard X font specification described above. The second line is
used by process graphics and the display builder. FM says that this is font FM, 10:12
specifies that pixel size 12 shall be used for FM10. The last font name string is only
shown in the display builder.
It is also possible to add a font set used for more than one language by adding a
comma separated list of fonts. The specification should be on one line, or as in the
example below that uses a line continuation character as the last character on the
line.
The example above specifies two fonts for the default raster 11 font in
Sherrill-Lubinski, one used for languages using iso8859-1 encoding and one used
for languages using iso8859-5 encoding.
The Fonts.cnf configuration file contains mapping of font names and numbers into
Windows Font info. Like the color.cnf the file contain record entries, each entry
describing one font conversion. 12 entries describe the 3 font faces in the four styles,
Normal, Bold, Italic and Bold-Italic. These 12 font faces/styles can appear in six
different sizes. Another 72 entries maps the Advant font name (e.g.FA10) to a
number (0-11) and a size. Following example shows how a font from the Advant
station is mapped into the font.cnf file.
default raster 11 -adobe-courier-bold-r-normal--*-*-*-*-*-*-iso8859-1
/* FM 10:12 20:14 30:17 40:18 50:24 60:34 Courier-bold-r */
3BSE030340R4101
125
This example shows a snip of code from the fontdef.dat file. The code describes
the Courier face name where the style is bold. The X equivalent is (not same
facename/style):
The mapping in the font.cnf file will look like:
..
..
{
TYPE: {FONT}
FONT: {FA10}
FONTNUMBER: {1}
RELSIZE: {0.703125}
}
..
..
{
TYPE:{FONTDESC}
FONTNUMBER:{1}
FONTNAME:{Courier}
SIZE:{17}
WEIGHT:{400}
CHARSET:{0}
ITALIC:{0}
UNDERLINE:{0}
STRIKETHROUGH:{0}
}
..
..
The Fonts.cnf file installed with the Display Converter contain mapping of
the standard OS fonts.
Changing the default fonts example:
126
1.
Make a copy of font configuration file and save it in your directory.
2.
Open a text editor such as Wordpad.
3.
Add or substitute any default font with a new font.
4.
Map with the appropriate font in your AdvaCommand graphic display to

the new one.
3BSE030340R4101
If your system does not have the colors or fonts you used to convert the
Advant Master graphic display, the conversion tool selects the closest matching
color or font on the system. One way to avoid font problems is to install necessary
fonts in your system. Check among the fonts available in your system.
Dynamic.cnf
The dynamic.cnf describes the mapping of display elements from Advant to

Operator Workplace. Following is an example of the mapping for DATPD01.
{
ELEMENTNAME: {DATPD01}
CONTROLNAME:{DATPG01}
PROGID:{DATPG01Proj.DATPG01}
LIBNAME:{DATPG01Proj}
REFERENCE:{"{89D92A21-E694-11D2-9261-0060084F2C5B}#5.0#0";
"{15E46AF2-5E6C-11D3-867A-0060B02958BA}.ocx"}
WIDTH:{4.8}
HEIGHT:{1.5}
FIXPOINT_X:{0.0}
FIXPOINT_Y:{0.0}
PROPERTIES: {
SIMPLE: {
FROM:{Update}
TO:{Update}
TYPE: {}
DEFAULT: {9s}
OUTPUTTO: {ctl}
}
SIMPLE: {
FROM:{ObjectName}
TO:{Tagname}
TYPE: {}
DEFAULT: {}
OUTPUTTO: {ctl}
}
SIMPLE: {
FROM:{FrameColor}
TO:{FrameColor}
TYPE: {Color}
DEFAULT: {}
3BSE030340R4101
127
OUTPUTTO: {ctl}
}
SIMPLE: {
FROM:{Font}
TO:{Font}
TYPE: {Font}
DEFAULT: {}
OUTPUTTO: {ctl}
}
SIMPLE: {
FROM:{ConditionCycle}
TO:{ConditionCycle}
TYPE: {}
DEFAULT: {}
OUTPUTTO: {ctl}
}
SIMPLE: {
FROM:{ConditionEvent}
TO:{ConditionEvent}
TYPE: {}
DEFAULT: {}
OUTPUTTO: {ctl}
}
SIMPLE: {
FROM:{FrameWidth}
TO:{FrameWidth}
TYPE: {}
DEFAULT: {}
OUTPUTTO: {ctl}
}
The mapping of DATPG01 reflects the DATPD01.de definition of the SL display

element. Example on how to get specification for your new graphic element:
128
1.
Create new VB project of Standard EXE type.
2.
Insert your new graphic element.
3.
Save project.
4.
Open the .fm file with a text editor.
5.
Copy Object entry to Reference in Dynamic.cnf.
3BSE030340R4101
Convert and Import your AdvaCommand Graphic Displays
6.
Copy progid entry to PROGID in Dynamic.cnf.
7.
The first part of PROGID is the Libname and the extension is the Controlname.
8.
Width, Height, Fixpoint_X and Fixpoint_Y are in SL units. Relationship

between VB units and SL units are XVB=XSL*144.11255 and
YVB=YSL*142.3321.

1.
Select object in Plant Explorer.
2.
Add the Graphic Display aspect and click Create.
3.
Select the aspect and click on the Edit button to open Graphic Builder.
4.
From the Graphics Builders Add-Ins menu, select Display Converter.

The dialog shown in Figure 64 appears.
5.
Select the AdvaCommand graphic display(s) you want to convert.
6.
Browse to the directory where the configuration files are stored (Source
Directory).
3BSE030340R4101
129
7.
All conversion errors such as unrecognized graphic primitive, graphic element,

faceplate, graphic link or syntax error will be displayed in a dialog box and
listed in a text file.
Figure 64. Display Conversion Dialog

The layout of the Display Converter is shown in Figure 64. The dialog consists of:
130
Source Directory
The Source Directory specifies where the graphic files to convert are stored.
Activating the Browse button next to the edit field will popup a dialog
(Figure 65) for selecting directory.
Displays
The Displays define the name(s) of the display(s) to convert. Activating the
Browse push-button next to the edit field will popup a standard File Open
dialog (Figure 65).
Log to file
Enabling this check box will save all log information to the selected log file.
Log information will always be appended to the log file. Default is un-checked.
3BSE030340R4101
Config
Activating the Config push-button will popup the config dialog (Figure 66).
From the Config dialog the path to the configuration files and the log files can
be specified. In the config dialog enabling/suppression of Warning/Information
messages in the log is also set.
Convert
Activating the Convert button will convert the selected displays and place the
converted files in the destination directory. The log field (and the log file if
enabled) will show the status of the conversion
Figure 65. Display Open Dialog
3BSE030340R4101
131
Edit your Converted Graphic Display
Figure 66. Config dialog

The layout of the Config dialog is shown in Figure 66. The dialog consists of:
Configuration Directory
The Configuration Directory specifies where the configuration files resides.
Activating the Browse button next to the edit field will popup a dialog
(Figure 66) for selecting directory. Default is C:\My Master Configuration Dir
or C:\My MOD Configuration Dir.
Logfile
The Logfile specifies the filename and path of the logfile. Activating the
Browse push-button next to the edit field will popup a standard file open dialog
(Figure 65) for selecting filename. Default is C:\My New Process Graphics
Dir\log.txt
Log Warnings
Marking this check box will display warnings in the log. Default is checked.
Log Infos
Marking this checkbox will display informations in the log. Informations are
very descriptive and will produce a large log quickly. Default is un-checked.
Edit your Converted Graphic Display

Check the conversion error text file and:
1.
132
Manipulate graphic elements.
3BSE030340R4101
Test and Deploy your Graphic Display
2.
Insert graphic elements.
3.
You can change or add expressions to properties. For complete information on

using the expression language, see On-line Help or IndustrialIT 800xA,
Engineering, Graphics.
4.
The display conversion is proportionate to a graphic display without Dynamic

function keys. If you have included Dynamic function keys in the conversion
you need to resize the graphic display in Y position and move the Dynamic
function keys to the bottom.
Figure 67. Graphics Builder
Test and Deploy your Graphic Display

Once you have converted your graphic display and got it into the Graphics Builder,
you can work with the graphic display in the same way as you do with an Operator
Workplace native graphic aspect. You use the same tools to test, save, and deploy
the graphic display as if you had built it directly in the Graphics Builder - refer to
the IndustrialIT 800xA, Engineering, Graphics.
3BSE030340R4101
133
Limitations of the Display Converter
Limitations of the Display Converter

It may not be possible for the conversion tool to make a 100% conversion to the
Operator Workplace format. The converter has the following known limitations:
134
Graphic display or external application references in Dynamic function keys

may not be fully resolved. The graphic display or external application name
will be converted from the graphic link but the object that owns that aspect may
be unknown or nonexistent.
Three dimensional graphic primitives not using static graphic element will be
converted into Graphics Builder maintaining the multiple spline composition
of the graphic primitives. In the System the same effect can be accomplished
by using a simple three dimensional shading to the whole primitive (and
removing the multiple splines.) This will result in improved performance. But
the user will have to do this manually. It is strongly recommended that you do
this optimization.
3BSE030340R4101
Section 10 System Administration

Hardware Indicators
The RTA Board has no hardware indicators on the board.
System Diagnostics
The AC 400 Controllers produce a number of event and alarm messages to inform
you about errors concerning the Advant System system and not with the process
itself.
You can find a System Alarm List aspect on the network. The System Alarm List
aspect enables you to see all system alarms for the AC 400 Controller system.
The System Alarms are presented in plain text.
Fault Finding and User Repair

Here are some hints on how to identify the cause of malfunctions within
the Advant Master System. It could be difficult to decide whether the problem you
see is a problem within the process, or a problem within the Advant System system.
There are some tools you can use for your trouble shooting:
System Status aspects
System Alarm List aspects
RTA Board aspects
Communication aspects
System Status
The System Status presents the status of the control system. It presents the result
from the control system internal supervision programs. The System Status is
available for the Network, the Operator Workplace node, and the Controller node.
3BSE030340R4101
135
System Diagnostics
System Status Viewer
The System Status Viewer shows status of different parts of the system. System
status information can be available for both software processes and hardware
devices. The System Status Viewer aspect can be located on different levels in all
structures. All status information in the System Status Viewer is updated
dynamically when a change of status occurs.
Show Details
Refresh Alarm and Events
Find Child Error
View Mode Button
Help Button
Previous Error
Show all Errors
Next Error
Propagated
Figure 68. System Status Viewer - an Overview

A description of the different tools and columns in the System Status Viewer
overview, are described below.
If you have several controllers it may cause a delay of the data update.
136
3BSE030340R4101
System Diagnostics
Tools in the Application Bar
Use the Next and Previous arrows in the upper left part of the figure, to get the
previous or next status.
To find out where the source of the status is, click the Find Child Error button, see
Figure 68. It is possible to make all objects with errors or warnings visible by
clicking the Show all Errors button.
By default the Status Viewer displays the objects in a tree view. In the list view you
can sort the objects by different columns. To change between list view and tree view,
select the View Mode button.
Click the Help button to view the Online Help for System Status.
Columns
In the Status column an icon is displayed presenting status for an object. Objects
that do not provide system status information will not have an icon in the column.
There are three possible status results: OK, Warning or Error.
Figure 69. The Status column

The background color of the Propagated Status will either be red (Error) or yellow
(Warning). In some cases there might be objects in the collapsed branch with both
Error and Warning, then Error will be shown as propagated status.
3BSE030340R4101
137
System Diagnostics
The Time column shows the time for the last error or warning.
The Description column shows a description of the latest error or warning status for
each object.
An x in the Details column indicates that there is more detailed information
available about the status. To show it, double-click in the column.
System Status - Network
As a start you should have a look at the System Status for the entire network.
Go to the Control Structure in Plant Explorer, select the Network object, and then
the System Status Viewer aspect.
Figure 70. System Status for the Network

In this case you can see that there is something wrong with the AC 450 Controller.
The next action should be to study the System Status for this controller.
138
3BSE030340R4101
System Diagnostics
System Status - Operator Workplace Node
The System Status for the Operator Workplace node itself is presented if you select
the Operator Workplace node, and the System Status View aspect in the Control
Structure. See Figure 71.
Figure 71. System Status View for Operator Workplace Node

To continue identifying the source of the error, study the system messages,
especially those that have been sent from the faulting service. If no obvious error
can be found, such as disk full or similar, the service error should be reported to the
supplier, see Fault Finding and User Repair on page 135.
3BSE030340R4101
139
System Diagnostics
System Status - MB 300 Control Network
The System Status for a MB 300 control network is presented if you select the
Control Structure, the MB 300 Network Board object, and the System Status Viewer
aspect.
Figure 72. System Status View for MB 300 Network Object

When an RTA Board object is marked with a cross in the Details column, doubleclick in the column to show the Advant Master Connectivity Server Communication
Display.
The display is also shown in the Advant Master CS Communication aspect of the
MB300 RTA board object in the Control Structure.
140
3BSE030340R4101
System Diagnostics
Figure 73. Advant Master Connectivity Server Communication Display

The display lists the communication status for each node the RTA Board can
communicate with. The columns are:
Node. It shows the node number.
Primary and Secondary. They show the node communication status, and are
further described in Table 6.
Name. It shows the node name. The name originates from the node object in
the control structure. If the node object is missing, then the name is missing.
Type. It shows the node type, and are further described in Table 7.
For single network - only one column is shown.
3BSE030340R4101
141
System Diagnostics
Table 6. Node Connectivity Status

Primary
Column
Secondary
Column
MB 300 Description
Communication is OK.
Communication error for an redundant MB300
network.
Communication error for an redundant MB300
network.
MB 300 communication error.
Table 7. Node Type

Type Column
Node Description
RTA
AC 400 Connectivity Server
AC
AC 400 Controller
MP
MP 200 Controller
OS
AdvaCommand Operator Station
IMS
Information Management System
MG
Master Gate
In the top-right corner of the display, the status for the RTA Board Location is
shown, see Figure 74.
Figure 74. Status Indication
142
3BSE030340R4101
System Diagnostics
An error
indicates that there is no communication with the RTA board, while a
warning
indicates a problem with the communication. If the status indication
shows a warning or an error, restarting the RTA board may solve the problem. To
restart the RTA board:
1.
Right-click the status indication, and select RTA Board Control.
Figure 75. Context menu

2.
In the displayed aspect tab, click Stop and wait for the RTA Board to stop
(check status).
3.
Click on the Start button.
3BSE030340R4101
143
System Diagnostics
System Status - Controller Node
The System Status for a Controller node is presented if you select the Control
Structure, the Controller node, and the System Status Viewer aspect. In the example
below (Figure 76), the AC 450 Controller (Node 4) has a problem with an Analog
input board no. 2.
Figure 76. System Status View for Controller node

The next step in your fault finding is to study the system alarm list for the failing
Controller, see System Alarms on page 150.
When an object is marked with a cross in the Details column, double-click in the
column, and then select Local Devices, to show the Local Devices graphic display
for the controller node.
This function isnt supported for MP 200/1 controllers.
144
3BSE030340R4101
System Diagnostics
10
11
14
1
2
15
3
16
17
4
5
12
13
Figure 77. AC 400 Local Devices Display
3BSE030340R4101
145
System Diagnostics
No
Description
Default
Presentation
Controller power
supply header
1.1
24V supply indication Green filled
1.2
2.1
2.2
3.1
3.2
3.3
3.4
146
24 supply name
Regulator indication
Regulator name
Battery voltage
indication
Grey
Battery backup
supply name
OK
Red crossed
Error
Grey
OK
Red
Error
Green filled
OK
Red crossed
Error
Grey
OK
Red
Error
Green filled
OK
Red crossed
Error
Battery voltage name Grey
Battery backup
supply indication
Condition
OK
Red
Error
Green filled
OK
Red crossed
Error
Grey
OK
Red
Error
I/O power supply

header
Grey
4.1
I/O 24V supply

indication
Green filled
OK
3BSE030340R4101
No
Description
System Diagnostics
Default
Presentation
Red crossed
4.2
5.1
5.2
I/O 24V supply name Grey
I/O regulator
indication
I/O regulator name
Condition
Error
OK
Red
Error
Green filled
OK
Red crossed
Error
Grey
OK
Red
Error
Controller header
Grey
6.1
Processor module
indication
Green filled
OK
Green empty
Standby
Yellow crossed
Warning
Red crossed
Error
Grey
OK
Grey
Standby
Grey
Warning
Red
Error
Green filled
OK
Yellow crossed
Warning
Red crossed
Error
Grey
OK
6.2
7.1
7.2
3BSE030340R4101
Processor module
name
Program card
indication
Program card name
147
System Diagnostics
No
8.1
8.2
Description
Free pgm card &

M500 indication
Free pgm card &

M500 name
Condition
Grey
Warning
Red
Error
Green filled
OK
Yellow crossed
Warning
Red crossed
Error
Grey
OK
Grey
Warning
Red
Error
Subrack fan header
Grey
9.1
Fan indication
Green filled
OK
Red crossed
Error
Grey
OK
Red
Error
Green filled
OK
Red crossed
Error
Grey
OK
Red
Error
9.2
10.1
Fan name
I/O fan indication
I/O fan name
148
Default
Presentation
11
S100 I/O bus

extension header
Grey
11.1
S100 I/O bus

extension indication
Green filled
OK
Red crossed
Error
3BSE030340R4101
No
11.2
Description
S100 I/O bus
extension name
System Diagnostics
Default
Presentation
Condition
Grey
OK
Red
Error
12
Additional header
Grey
12.1
User defined
supervision
indication
Green filled
OK
Red crossed
Error
Grey
OK
Red
Error
Green filled
OK
Red crossed
Error
Grey
OK
Red crossed
Error
12.2
13.1
13.2
User defined
supervision name
PC triggered
supervision
indication
PC triggered
supervision name
14
Terminal header
Grey
14.1
Terminal indication
Green filled
OK
Red crossed
Error
Grey
OK
Red
Error
14.2
Terminal name
15
Printer header
Grey
15.1
Printer indication
Green filled
OK
Red crossed
Error
3BSE030340R4101
149
System Alarms
No
15.2
Description
Printer name
Default
Presentation
Condition
Grey
OK
Red
Error
16
External
communication
Grey
16.1
XCom indication
Green filled
OK
Red crossed
Error
Grey
OK
Red
Error
Green filled
OK
Red crossed
Error
Grey
OK
16.2
XCom name
17.1
RSCom indication
17.2
RSCom
System Alarms
The System Alarms provide valuable information for fault tracing. Default you have
a System Alarm aspect on the Network object and on the Controller object(s) in
your Control Structure. You should use them as they will give you an overview list
for all the system alarms in your system. To create your own System Alarm aspects,
follow the instructions below:
150
1.
Go to the Control Structure in Plant Explorer. Select the object on which you
want to create the aspect.
2.
Create an Alarm and Event List aspect and name it System Alarms.
3.
Select the System Alarms aspect, go to the Config view and select the Default
aspect MB 300 System Alarms.
4.
Save.
3BSE030340R4101
System Alarms
An example of a typical System Alarm List is presented in Figure 78.
Figure 78. System Alarm List for the Complete Network

When you have located the Controller where the problem resides, bring up the
System Alarm List on that Controller object (Control Structure). This gives you a
dedicated system alarm list for that Controller helping you to close in on the
problem. The System Alarms are in plain text and should help you to continue with
your fault tracing.
3BSE030340R4101
151
Backup/Restore Procedures
Backup/Restore Procedures
General backup procedures are described in IndustrialIT 800xA, System,
Administration & Security.
Backup
Backup the following as described below:
Network Configuration Settings
Time Server Setting
You use the RTA Board Control aspect to save changes to the configuration of the
RTA board. Use Plant Explorer to locate the Control Structure, the Operator
Workplace Server object, the RTA Board object, select the RTA Board Control
aspect, and then the RTA Board Control tab.
This view contains a RTA Board backup button. When you have made changes to
configuration data on the RTA Board, you shall save the new configuration (if not,
the changes will be lost after the next restart of the PC). Click on the RTA Board
backup button and check the log messages that are presented in the text window. If
there are no errors, the new configuration has been saved (and will automatically be
loaded to the RTA Board at startup).
Please observe that if you have a backup of a whole Control Structure and want
to import it, you have to Add a Provider under the Adapter Data Source
Definition Structure aspect, in the Control Structure.
The RTA board configuration files are locally stored on the computer with the RTA
board. If you want to export the files for backup or for importing to another machine
with an RTA board, you can do as follows:
Path: \Program Files\ABB Industrial IT\Operate IT\AC 400 Connect\
AdvantBase\Data\RTA\Init
152
3BSE030340R4101
Restore
Save these three files on a safe location, such as a CD or other server.
\DATHR1.CD
\DATHR2.CD
\DATHR3.CD
To backup the network configuration settings for an RTA Board:

1.
Select the Control Structure, a Server node object, and then an RTA Board
object.
2.
Select the RTA Board Control aspect, and then the Network/Node
Configuration tab.
3.
Relevant settings are the values of:
4.
Network Number 1
Network Number 2
Node Number
Write down these settings and store the information on a safe location, such as
a CD or other server.
Time Server Setting
Backup the time server setting by writing the setting down and storing this
information on a safe location, such as a CD or other server.
Relevant setting is the value of the registry parameter REVERSED_SYNC_MODE
described in 800xA for Advant Master Connectivity server as Clock Master on page
31. The parameter has a value of either 0 or 1.
Restore
When you make a restore, you first have to make a general 800xA restore as
described in IndustrialIT 800xA, System, Administration & Security.
3BSE030340R4101
153
Restore
To restore the configuration for an RTA Board, copy the three files you saved during
backup from the safe location to the folder \..\Program Files\ABB Industrial
IT\Operate IT\AC 400 Connect\ AdvantBase\Data\RTA\Init. (If prompted, answer
Yes to replace existing files).
Before you restore these three files you have to make sure that the system to
which you restore to, is running on the same Character conversion language as
the machine from where you took the dump.
To restore the network configuration settings, setup network and node numbers
using the settings you wrote down during the backup. How to setup network and
node numbers is described in Setup Network and Node Number on page 34.
Time Server Settings
To restore the time server setting, change the registry parameter

REVERSED_SYNC_MODE to the value you wrote down during the backup. How
to change the parameter is described in 800xA for Advant Master Connectivity
server as Clock Master on page 31.
RTA Board Backup
Saves the RTA Board configuration. The saved configuration will be loaded on the
RTA Board after the board is started.
The window also contains a progress log (information about the communication
with the RTA Board) and the RTA Board status.
154
3BSE030340R4101
Restore
Figure 79. RTA Configuration
3BSE030340R4101
155
Restore
156
3BSE030340R4101
Appendix A Event Treat Elements

Introduction
When an event occurs it is analyzed in the Controller. As a result of that an
information package is sent to the Operator Workplace server. Using your Operator
Workplaces and functionality you can study the alarm and event information in
various formats. The presentation of an Alarm or Event generated in
an AC 400 Controller is made according to the specified event treatment.
OperatorIT Workplace
EVENT 10
Audible alarm
Alarm priority
Alarm To Block
Alarm Fr Block
.
.
Textcomb
1
2
NO
YES
5
Event
Treat
Controller
Process
Object
or IMS
object
MOTOR 2
Conveyor 2
Control mode
A
Control status
TO
Interlocking status
.....
.
Ev_Tr 1
EVENT10
Ev_Tr 2
EVENT12
....
Figure 80. Alarm and event handling
3BSE030340R4101
157
The alarm and event message includes:
NAME of the object, for example MOTOR 2.
DESCRIPTION of the object, for example Conveyor 2.
A set of status flags for the internal control.
Pointers to elements (EVENT) in the Event Treat data base, where the event is
described.
Each Process and System object contains at least one pointer to the Event Treat data
base. A digital input. DI for example, contains two Event Treat pointers, ERR_TR
(Error Treat) and VALUE_TR (Value Treat).
ERR_TR is used for internal signal errors when the ERR flag changes status.
VALUE_TR is used for process events and process alarms when the signal value
(VALUE) changes status, possibly together with the process error flag
(DISTURBANCE).
158
3BSE030340R4101
The Event Treat Database Element

The contents of the Event Treat data base, and ways to vary the event handling, are
described below:
1
EVENT20
Event Treat
1
2
3
4
5
6
7
8
0
4
YES
YES
NO
NO
NO
0
(25.20)
AUDIBLE
AL PRIO
AL TOBLK
AL FRBLK
PERSISTB
TEXT TOB
TEXT FRB
TEXTCOMB
S2
Event Texts
S3
Property Texts
Figure 81. Data Base Element for Event Handling

1.
Name and element number in the Event Treat data base.
2.
Logic file number and element number.
3.
Properties whose values can be changed.
4.
Property numbers.
5.
Start values applied.
6.
Segment S2 containing User defined event texts for use instead of the standard
system texts (applies only to EVENT20 - EVENT300).
7.
Segment S3 containing User defined property texts for use instead of the
standard system texts (applies only to EVENT20 - EVENT300).
3BSE030340R4101
159
The properties in the EVENT element are described below:

AUDIBLE
AUDIBLE makes it possible for you to activate an audible signal on the Operator
Workplace Server. The condition for an audible alarm is that:
you have defined an audible alarm for that priority (see the configuration of
priority for the alarm list in Operator Workplace Alarms)
you have set AUDIBLE > 0 for the Process or system object
the Process or system object is in an alarm state
AL_PRIO
Alarm Priority defines the Alarm priority in the presentation. Read the IndustrialIT
800xA, System, Operator Workplace Configuration.for information about how to
configure text color and font, sound effects etc. The priority you define in the Event
Treat elements are converted to a corresponding OPC Severity according to the
following:
Table 8. Mapping Event Treatment Alarm Priority to OPC Severity
160
Priority
OPC Severity
875
750
625
500
375
250
125
3BSE030340R4101
AL_TOBLK - Alarm To Block
Blocks alarm handling of a supervised alarm signal/flag when it makes a 0 -> 1

transition. Since most alarm signals/flags are active high, AL_TOBLK should be set
= N (No) to invoke alarm handling for 0 -> 1 transitions and = Y (Yes) to disable it.
AL_FRBLK - Alarm From Block
Blocks alarm handling of a supervised alarm signal/flag when it makes a 1 -> 0

transition. Since most alarm signals/flags are active high, and since alarm handling
on return to normal makes little sense, AL_FRBLK should normally be set = Y
(Yes).
PERSISTB - Persistent Alarm Block
Should be set = N (No) when alarm handling either way is required and = Y (yes)
when it is not. With PERSISTB =Y, it is possible to block, that is remove persistent
alarms from the Alarm List after acknowledgment, even if the alarm situation
persists. Normally, that is with PERSISTB = N, an alarm is only removed from the
Alarm List when the alarm is acknowledged and disappears.
TEXT_TOBLK - Text To Block
Flag that blocks generation of text in lists and printouts when the alarm/event
changes from 0 ->1.
TEXT_FRBLK - Text From Block
Flag that blocks generation of text in lists and printouts when the alarm/event
changes from 1 -> 0.
3BSE030340R4101
161
TEXTCOMB - Text Combination code
Integer to select if standard or User defined property text and event text shall be
used.
Event text:
11 characters
Property text:
8 characters
(except
TEXTCOMB=16
and 17)
Event text + Step no:

8+3 characters
Value + unit:
11 characters
Figure 82. Maximum number of characters for the property and event texts
162
3BSE030340R4101
Table 9. Formats for Property and Event Texts

TEXT COMBination
code
0
Property text
Standard
Event text
Standard
User defined
Standard
Value + unit
Standard
User defined
User defined
Standard
User defined
User defined
16
User defined (1) Standard
17
User defined (1) User defined
18 (2)
Standard
Standard
19 (2)
Standard
User defined + Step no
20 (2)
User defined
Standard
21 (2)
User defined
User defined + Step no
24
(3)
Standard
+ Step no
+ Step no
Value + unit
(1) Suitable for long property texts (up to 20 characters).

(2) Specially adapted for the function unit Sequence (SEQ).
(3) Similar to TEXTCOMB=2, but only events caused by a process event will be
entered in the list.
Description can NOT be displayed if long Property texts are used (TEXTCOMB
16 and 17).
3BSE030340R4101
163
As mentioned earlier, EVENT20 - EVENT300 can accommodate your own event

texts as an alternative to the standard texts in the system. You can enter these by
expanding segment S2.
1
EVENT20
Event Treat
S1
9(1)
9(2)
9(3)
9(4)
9(5)
9(6)
9(7)
9(8)
9(9)
9(10)
9(11)
9(12)
9(13)
9(14)
9(15)
9(16)
S3
(25.20)
Base part
EV1
EV2
EV3
EV4
EV5
EV6
EV7
EV8
EV9
EV10
EV11
EV12
EV13
EV14
EV15
EV16
Property Texts
Figure 83. Segment S2 in Event Treat

Line numbers for 16 event texts. Each text can have a maximum of 11 characters.
Each event points out a certain line number. It is important when you use a user
defined event text that you put the text into the correct line number.
You enter the user defined property texts in EVENT20 - EVENT300 by expanding
segment S3.
164
3BSE030340R4101
EVENT20
Event Treat
S1
Base part
S2
Event Texts
10(1)
10(2)
10(3)
10(4)
10(5)
10(6)
10(7)
10(8)
10(9)
10(10)
10(11)
10(12)
10(13)
10(14)
10(15)
10(16)
(25.20)
PRTE1
PRTE2
PRTE3
PRTE4
PRTE5
PRTE6
PRTE7
PRTE8
PRTE9
PRTE10
PRTE11
PRTE12
PRTE13
PRTE14
PRTE15
PRTE16
Figure 84. Segment S3 in Event Treat

The relative line numbers for 16 property texts. Each text has a maximum length of
20 characters.
TEXTCOMB decides max number of characters to be presented in the lists.
The coupling between the event and the line number is the same as it is for the event
texts. For this reason, you must put the different texts on the correct lines.
Appendix B, Event Texts, describes the events that generate different line number
pointers.
3BSE030340R4101
165
There are 300 EVENT elements available, as described below:

Table 10. Event Elements
EVENT1-18
Predefined for standard event handling (see Table 8).

You are not allowed to change these
EVENT19
Reserved for future extensions of the standard handling.

You are not allowed to change it.
EVENT20-94
Available for user defined event handling.

You can change all properties.
EVENT95-100
Reserved for Batch applications.
EVENT101-300
Available for user defined event handling.

You can change all properties.
EVENT301
Reserved for other applications.
EVENT
Property
1
10 11 12 13 14 15 16 17 18
AUDIBLE
AL_PRIO
AL_TOBLK
AL_FRBLK
PERSISTB
TEXT_TOB
TEXT_FRB
TEXTCOMB
24 24 18 18
17 17
166
3BSE030340R4101
Table 11. Recommended Usage of the EVENT Elements

EVENT Number
Usage
EVENT1, EVENT2 Are suitable for binary process signals and objects, for
example DI, DO, GENBIN.
EVENT3, EVENT4 Are suitable for analog process signals and objects, for
example AI, AO, GENCON and PIDCON.
EVENT5, EVENT6 Are specially adapted for SEQUENCE. EVENT1,EVENT3
and EVENT5 block all alarm handling whereas EVENT2,
EVENT4 and EVENT6 permit alarm handling.
EVENT7
Is suitable for use as DIST_TREAT for PIDCON, RATIOSTN

and MANSTN to obtain an unacknowledged alarm indicated
in the process Alarm List. No text is created.
EVENT8
Is specially adapted for use as I1_TR for GROUP.
EVENT9
Is specially adapted for use as I2_TR for GROUP.
EVENT10
Is specially adapted for use as I1_TR for MOTCON.
EVENT11
Is specially adapted for use as I1_TR for VALVECON.
EVENT12
Is specially adapted for use as I2_TR for MOTCON.
EVENT13
Is specially adapted for use as I2_TR for VALVECON.
EVENT14
Is specially adapted for use for texts generated from the

AMPL element EVENT in the Controller.
EVENT15
Is specially adapted for the Status List and contains texts for
objects in normal conditions.
EVENT16
Is specially adapted for use as ADAP_TR for PIDCONA.
EVENT17
Is specially adapted for SPC (Statistical Process Control).
EVENT18
Is specially adapted for SPC (Statistical Process Control).
3BSE030340R4101
167
168
3BSE030340R4101
Appendix B Event Texts

The events defined for the various signal/object types are described in the tables
below with the following layout:
Events
Event Treat
pointer
Property text
Upper limit H2
exceeded
LIM_2_TR
Standard
text
Limit H2
Line No in
Event Treat
1
6
Event text
Standard
text
Alarm
Line No in
Event Treat
1
Figure 85. Event Text Table Layout

1.
Description of the event.
2.
Pointer to data base elements in Event Treat. All pointers for each signal/object
type and the recommended values for standard event handling are described in
the manuals Functional Units, Part 1 to Functional Units, Part 9.
3.
Standard property text that describes the event (applies to EVENT1EVENT18). EVENT20- EVENT300 have user-defined texts.
4.
Line number in the EVENT data base elements where your own text should be
placed (applies to EVENT20- EVENT300).
3BSE030340R4101
169
170
5.
Standard event text that describes the state of the event, alarm-normal,
blocked-deblocked, etc. If EVENT20-EVENT300 are chosen, you can define
the appropriate text yourself.
6.
Line number in the EVENT database elements where your own text should be
placed (applies to EVENT20- EVENT300). The line number is the same for
standard event texts (applies to EVENT1- EVENT18).
3BSE030340R4101
Analog Input Signal AI
Analog Input Signal AI

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Upper limit H2 exceeded
LIM_2_TR
Limit H2
Alarm
Upper limit H2 re-entered
LIM_2_TR
Limit H2
Normal
Upper limit H1 exceeded
LIM_1_TR
Limit H1
Alarm
Upper limit H1 re-entered
LIM_1_TR
Limit H1
Normal
LIM_1_TR
Limit L1
Alarm
Lower limit L1 re-entered
LIM_1_TR
Limit L1
Normal
LIM_2_TR
Limit L2
Alarm
Lower limit L2 re-entered
LIM_2_TR
Limit L2
Normal
Measured value entered
LIM_1_TR
Value
ValueChg
H2-value entered
LIM_2_TR
Limit H2
ValueChg
H1-value entered
LIM_1_TR
Limit H1
ValueChg
L1-value entered
LIM_1_TR
Limit L1
ValueChg
L2-value entered
LIM_2_TR
Limit L2
ValueChg
Signal error On
ERR_TR
Sig.Err
Alarm
Signal error Off
ERR_TR
Sig.Err
Normal
Blocking of event handling
ERR_TR
Alarm
Blocked
Deblocking of event
handling
ERR_TR
Alarm
Deblocked
Blocking of printout
ERR_TR
Printout
Blocked
Deblocking of printout
ERR_TR
Printout
Deblocked
3BSE030340R4101
171
Analog Output Signal AO
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Blocking of DB-update
ERR_TR
Update
Blocked
Deblocking of DB-update
ERR_TR
Update
Deblocked
Analog Output Signal AO

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Manual control mode
ERR_TR
Manual
On
Auto control mode
ERR_TR
Auto
On
Block output signal against ERR_TR

process
Output sign
Blocked
Deblock output signal

against process
ERR_TR
Output sign
Deblocked
Measured value entered
ERR_TR
Output sign
ValueChg
Max limit value entered
ERR_TR
Max limit
ValueChg
Min limit value entered
ERR_TR
Min limit
ValueChg
172
3BSE030340R4101
Digital Input Signal DI
Digital Input Signal DI

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Abnormal position On
VALUE_TR Value
Alarm
Normal position On
VALUE_TR Value
Normal
Abnormal value entered
VALUE_TR Value
ValueChg
Normal value entered
VALUE_TR Value
ValueChg
Signal error On
ERR_TR
Sig.Err
Alarm
Signal error Off
ERR_TR
Sig.Err
Normal
ERR_TR
Alarm
Blocked
Deblocking of event handling
ERR_TR
Alarm
Deblocked
ERR_TR
Printout
Blocked
ERR_TR
Printout
Deblocked
Blocking of data base update
ERR_TR
Update
Blocked
Deblocking of data base

update
ERR_TR
Update
Deblocked
3BSE030340R4101
173
Digital Output Signal DO
Digital Output Signal DO

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event
Treat
Event text
Standard
text
Line No in
Event
Treat
Order On
ERR_TR
Output sign 2
On
Order Off
ERR_TR
Output sign 2
Off
Manual control mode
ERR_TR
Manual
On
Auto control mode
ERR_TR
Auto
Off
Blocking of output signal

against process
ERR_TR
Output sign 6
Blocked
Deblocking of output signal

against process
ERR_TR
Output sign 6
Deblocked
Sequence SEQ
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Change the step
POS_TREAT StepChg
ValueChg
Step number for jump

entered
POS_TREAT Jump
mode
Enter
Number of turns entered
POS_TREAT Turn no
Enter
Interval time entered
POS_TREAT IntervT
Enter
Indication Active On
IND_TREAT
Active
On
Indication Active Off
IND_TREAT
Active
Off
Indication Last Step On
IND_TREAT
Last Step
On
174
3BSE030340R4101
Sequence SEQ
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Indication Last Step Off
IND_TREAT
Last Step
Off
Indication Auto control mode

On
IND_TREAT
Auto Ind
On
Indication Manual control

mode On
IND_TREAT
Man Ind
On
Indication step Hold On
IND_TREAT
Hold Ind
On
Indication Unconditional
control mode On
IND_TREAT
Uncond
Ind
On
Indication Next step On
IND_TREAT
Next
On
Position error On
FAULT_TR
Jump error 1
Alarm
Position error Off
FAULT_TR
Jump error 1
Normal
Sequence error On
FAULT_TR
SeqAlarm
Alarm
Sequence error Off
FAULT_TR
SeqAlarm
Normal
Step error On
FAULT_TR
StepAlarm 4
Alarm
Step error Off
FAULT_TR
StepAlarm 4
Normal
Blocking of event handling for FAULT_TR

position change
PosAlarm
Blocked
Deblocking of event handling FAULT_TR

for position change
PosAlarm
Deblocked
Blocking of printout for

position change
FAULT_TR
PosPrint
11
Blocked
Deblocking of printout for

position change
FAULT_TR
PosPrint
11
Deblocked
Disturb
Blocked

disturbance
3BSE030340R4101
175
Sequence SEQ
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat

for disturbance
Disturb
Deblocked
Blocking of printout for

disturbance
FAULT_TR
DistPrint
Blocked

disturbance
FAULT_TR
DistPrint
Deblocked

type error
TEAlarm
Blocked

for type error
TEAlarm
Deblocked
Blocking of printout for type

error
FAULT_TR
TEPrint
10
Blocked

type error
FAULT_TR
TEPrint
10
Deblocked

ind. changes
IndAlarm
Blocked

for ind. changes
IndAlarm
Deblocked
Blocking of printout for ind.

changes
FAULT_TR
IndPrint
12
Blocked
Deblocking of printout for ind. FAULT_TR

changes
IndPrint
12
Deblocked
Blocking of operator order
FAULT_TR
OprOrder
13
Blocked
Deblocking of operator order
FAULT_TR
OprOrder
13
Deblocked
176
3BSE030340R4101
Process Controller PIDCON

Property text
Events
Event Treat
pointer
Lower limit L1 for measured

value exceeded
H1L1_TR

value re-entered
H1L1_TR
Upper limit H1 for measured

value exceeded
H1L1_TR

value re-entered
H1L1_TR
Lower limit (1) for deviation

exceeded
H1L1_TR

re-entered
H1L1_TR
Upper limit (1) for deviation

exceeded
H1L1_TR

re-entered
H1L1_TR

value exceeded
H2L2_TR

value re-entered
H2L2_TR

value exceeded
H2L2_TR
3BSE030340R4101
Standard
text
MV<L1
Line No in
Event
Treat
1
Event text
Standard
text
<Value>
Line No in
Event
Treat
1
<Unit>
MV<L1
<Value>
<Unit>
MV>H1
<Value>
<Unit>
MV>H1
<Value>
<Unit>
DEV<L
<Value>
<Unit>
DEV<L
<Value>
<Unit>
DEV>H
<Value>
<Unit>
DEV>H
<Value>
<Unit>
MV<L2
<Value>
<Unit>
MV<L2
<Value>
<Unit>
MV>H2
<Value>
<Unit>
177
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event
Treat
Standard
text
<Value>
Line No in
Event
Treat
Upper limit H2 for measured H2L2_TR

value re-entered
MV>H2
PC-gate LOCALFL decides

control mode
MODE_TR
LOCAL !!
On
PC-gate MANFL decides

control mode
MODE_TR
MAN !!
On
PC-gate AUTOFL decides

control mode
MODE_TR
AUTO !!
On
PC-gate E1 decides control

mode
MODE_TR
E1 !!
On

mode
MODE_TR
E2 !!
On

mode
MODE_TR
E3 !!
On
AI-error On
ERR_TR
AISign Err
Alarm
AI-error Off
ERR_TR
AISign Err
Normal
178
Event text
<Unit>
3BSE030340R4101
Process Controller PIDCONA

value exceeded
H1L1_TR

value re-entered
H1L1_TR

value exceeded
H1L1_TR

value re-entered
H1L1_TR

exceeded
H1L1_TR

re-entered
H1L1_TR

exceeded
H1L1_TR

re-entered
H1L1_TR

value exceeded
H2L2_TR

value re-entered
H2L2_TR

value exceeded
H2L2_TR

value re-entered
H2L2_TR
PC-gate LOCALFL decides

control mode
MODE_TR
3BSE030340R4101
MV<L1
<Value>
<Unit>
MV<L1
<Value>
<Unit>
MV>H1
<Value>
<Unit>
MV>H1
<Value>
<Unit>
DEV<L
<Value>
<Unit>
DEV<L
<Value>
<Unit>
DEV>H
<Value>
<Unit>
DEV>H
<Value>
<Unit>
MV<L2
<Value>
<Unit>
MV<L2
<Value>
<Unit>
MV>H2
<Value>
<Unit>
MV>H2
<Value>
<Unit>
LOCAL !!
On
179
PC-gate MANFL decides

control mode
MODE_TR
MAN !!
On
PC-gate AUTOFL decides

control mode
MODE_TR
AUTO !!
On

mode
MODE_TR
E1 !!
On

mode
MODE_TR
E2 !!
On

mode
MODE_TR
E3 !!
On
AI-error On
ERR_TR
AISign Err
Alarm
AI-error Off
ERR_TR
AISign Err
Normal
Autotuning aborted
ADAP_TR
AT Abort
Alarm
Autotuning aborted
ADAP_TR
AT Abort
Normal
Autotuning failed
ADAP_TR
AT Fail
Alarm
Autotuning failed
ADAP_TR
AT Fail
Normal
Autotuning. Question to
operator
ADAP_TR
AT Quest
Decision
Autotuning. Question to
operator answered
ADAP_TR
AT Quest
Answered
There is an invalid sample

rate
ADAP_TR
TS Fault
Alarm
There is an invalid sample

rate
ADAP_TR
TS Fault
Normal
Adaptation failed
ADAP_TR
Ad Fail
Alarm
Adaptation failed
ADAP_TR
Ad Fail
Normal
180
3BSE030340R4101
Manual Station MANSTN
Manual Station MANSTN

Property text
Events
Event Treat
pointer
Standard
text
Standard
text
<Value>
Line No in
Event Treat

value exceeded
H1L1_TR

value re-entered
H1L1_TR

value exceeded
H1L1_TR

value re-entered
H1L1_TR

value exceeded
H2L2_TR

value re-entered
H2L2_TR

value exceeded
H2L2_TR

value re-entered
H2L2_TR
AI-error On
ERR_TR
AISign Err
Alarm
AI-error Off
ERR_TR
AISign Err
Normal
3BSE030340R4101
MV<L1
Line No in
Event Treat
Event text
<Unit>
MV<L1
<Value>
<Unit>
MV>H1
<Value>
<Unit>
MV>H1
<Value>
<Unit>
MV<L2
<Value>
<Unit>
MV<L2
<Value>
<Unit>
MV>H2
<Value>
<Unit>
MV>H2
<Value>
<Unit>
181
Ratio Station RATIOSTN
Ratio Station RATIOSTN

Property text
Events
Event Treat
pointer
Standard
text
Standard
text
<Value>
Line No in
Event Treat

value exceeded
H1L1_TR

value re-entered
H1L1_TR

value exceeded
H1L1_TR

value re-entered
H1L1_TR

value exceeded
H2L2_TR

value re-entered
H2L2_TR

value exceeded
H2L2_TR

value re-entered
H2L2_TR
AI-error On
ERR_TR
AISign Err
Alarm
AI-error Off
ERR_TR
AISign Err
Normal
182
MV<L1
Line No in
Event Treat
Event text
<Unit>
MV<L1
<Value>
<Unit>
MV>H1
<Value>
<Unit>
MV>H1
<Value>
<Unit>
MV<L2
<Value>
<Unit>
MV<L2
<Value>
<Unit>
MV>H2
<Value>
<Unit>
MV>H2
<Value>
<Unit>
3BSE030340R4101
User Defined Controller GENCON

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
AI-error On
AL_TR
AISign Err
Alarm
AI-error Off
AL_TR
AISign Err
Normal
Limit for control deviation

exceeded
AL_TR
Big Dev
Alarm
Limit for control deviation reentered
AL_TR
Big Dev
Normal

value exceeded
AL_TR
MV>H2
Alarm

value re-entered
AL_TR
MV>H2
Normal

value exceeded
AL_TR
MV>H1
Alarm

value re-entered
AL_TR
MV>H1
Normal

value exceeded
AL_TR
MV<L1
Alarm

value re-entered
AL_TR
MV<L1
Normal

value exceeded
AL_TR
MV<L2
Alarm

value re-entered
AL_TR
MV<L2
Normal
Max limit for output sign On
LIM_TR
SpMaxLim
On
Max limit for output sign Off
LIM_TR
SpMaxLim
Off
Min limit for output sign On
LIM_TR
SpMinLim
On
3BSE030340R4101
183
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Min limit for output sign Off
LIM_TR
SpMinLim
Off
Max limit for output sign On
LIM_TR
OpMaxLim
On
Max limit for output sign Off
LIM_TR
OpMaxLim
Off
Min limit for output sign On
LIM_TR
OpMinLim
On
Min limit for output sign Off
LIM_TR
OpMinLim
Off
Op. mode Balance On
IND_TR
Balance
On
Op. mode Balance Off
IND_TR
Balance
Off
Op. mode Manual Forced On IND_TR
ManFrced
On
Op. mode Manual Forced Off IND_TR
ManFrced
Off
Op. mode Manual On
IND_TR
Manual
On
Op. mode Manual Off
IND_TR
Manual
Off
Op. mode Auto On
IND_TR
Auto
On
Op. mode Auto Off
IND_TR
Auto
Off
Op. mode E1 On
IND_TR
E1
On
Op. mode E1 Off
IND_TR
E1
Off
Op. mode E2 On
IND_TR
E2
On
Op. mode E2 Off
IND_TR
E2
Off
Controller output On
IND_TR
Controller
On
Controller output Off
IND_TR
Controller
Off
Controller On Binary control
IND_TR
BinCtrl
10
On
Controller Off Binary control
IND_TR
BinCtrl
10
Off
184
3BSE030340R4101
Binary Object GENBIN

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Signal error On
AL_TR
SignErr
Alarm
Signal error Off
AL_TR
SignErr
Normal
Feedback error On
AL_TR
FBErr
Alarm
Feedback error Off
AL_TR
FBErr
Normal

value exceeded
AL_TR
MV>H2
Alarm

value re-entered
AL_TR
MV>H2
Normal

value exceeded
AL_TR
MV>H1
Alarm

re-entered
AL_TR
MV>H1
Normal

value exceeded
AL_TR
MV<L1
Alarm

value re-entered
AL_TR
MV<L1
Normal

value exceeded
AL_TR
MV<L2
Alarm

value re-entered
AL_TR
MV<L2
Normal
Op. mode Interlock

INTMODE On
INTL_TR
ModeIntl
On
Op. mode Interlock

INTMODE Off
INTL_TR
ModeIntl
Off
3BSE030340R4101
185
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Process Interlock INTPROC

On
INTL_TR
ProcIntl
On
Process Interlock INTPROC

Off
INTL_TR
ProcIntl
Off
Switchgear Interlock
INTSWGR On
INTL_TR
SwgrIntl
On
Switchgear Interlock
INTSWGR Off
INTL_TR
SwgrIntl
Off
Emergency Stop Interlock

INTEMTP On
INTL_TR
EmTrpInt
On
Emergency Stop Interlock

INTEMTP Off
INTL_TR
EmTrpInt
Off
Op. mode Central On
IND_TR
Central
On
Op. mode Central Off
IND_TR
Central
Off
Op. mode Local On
IND_TR
Local
On
Op. mode Local Off
IND_TR
Local
Off
Op. mode Remote On
IND_TR
Remote
On
Op. mode Remote Off
IND_TR
Remote
Off
Op. mode Manual On
IND_TR
Manual
On
Op. mode Manual Off
IND_TR
Manual
Off
Op. mode Auto On
IND_TR
Auto
On
Op. mode Auto Off
IND_TR
Auto
Off
Op. mode Blocked On
IND_TR
CtrlBlk
On
Op. mode Blocked Off
IND_TR
CtrlBlk
Off
Op. mode Standby On
IND_TR
Standby
On
186
3BSE030340R4101
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Op. mode Standby Off
IND_TR
Standby
Off
ON-indication On
IND_TR
On/Open
On
ON-indication Off
IND_TR
On/Open
Off
Indication changing On
IND_TR
PosChnge
10
On
Indication changing Off
IND_TR
PosChnge
10
Off
3BSE030340R4101
187
User Defined Object GENUSD

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event
Treat
Event text
Standard
text
Line No in
Event
Treat
Alarm ALQ1 On
AL_TR
Quality 1
Alarm
Alarm ALQ1 Off
AL_TR
Quality 1
Normal
Alarm ALQ2 On
AL_TR
Quality 2
Alarm
Alarm ALQ2 Off
AL_TR
Quality 2
Normal
Alarm ALF1 On
AL_TR
Fault 1
Alarm
Alarm ALF1 Off
AL_TR
Fault 1
Normal
Alarm ALF2 On
AL_TR
Fault 2
Alarm
Alarm ALF2 Off
AL_TR
Fault 2
Normal
Alarm ALF3 On
AL_TR
Fault 3
Alarm
Alarm ALF3 Off
AL_TR
Fault 3
Normal
Alarm ALF4 On
AL_TR
Fault 4
Alarm
Alarm ALF4 Off
AL_TR
Fault 4
Normal
Alarm ALF5 On
AL_TR
Fault 5
Alarm
Alarm ALF5 Off
AL_TR
Fault 5
Normal
Alarm ALF6 On
AL_TR
Fault 6
Alarm
Alarm ALF6 Off
AL_TR
Fault 6
Normal
Interlock INTLU1 On
INTL_TR
Interl 1
On
Interlock INTLU1 Off
INTL_TR
Interl 1
Off
Interlock INTLU2 On
INTL_TR
Interl 2
On
INTL_TR
Interl 2
Off
188
3BSE030340R4101
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event
Treat
Event text
Standard
text
Line No in
Event
Treat
Interlock INTLU3 On
INTL_TR
Interl 3
On
INTL_TR
Interl 3
Off
Interlock INTLU4 On
INTL_TR
Interl 4
On
INTL_TR
Interl 4
Off
Interlock INTLU5 On
INTL_TR
Interl 5
On
INTL_TR
Interl 5
Off
Interlock INTLU6 On
INTL_TR
Interl 6
On
INTL_TR
Interl 6
Off
Op. mode M1 M1 On
IND_TR
OperPos1
On
Op. mode M1 M1 Off
IND_TR
OperPos1
Off
Op. mode M2 M2 On
IND_TR
OperPos2
On
Op. mode M2 M2 Off
IND_TR
OperPos2
Off
Op. mode M3 M3 On
IND_TR
OperPos3
On
Op. mode M3 M3 Off
IND_TR
OperPos3
Off
Op. mode Manual On MAN
IND_TR
Manual
On
Op. mode Manual Off MAN
IND_TR
Manual
Off
Op. mode Auto On AUTO
IND_TR
Auto
On
Op. mode Auto Off AUTO
IND_TR
Auto
Off
Op. mode Blocked On BLK
IND_TR
CtrlBlk
On
Op. mode Blocked Off BLK
IND_TR
CtrlBlk
Off
Op. mode Standby On STBY
IND_TR
Standby
On
Op. mode Standby Off STBY
IND_TR
Standby
Off
3BSE030340R4101
189
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event
Treat
Event text
Standard
text
Line No in
Event
Treat
Indication IND1 On
IND_TR
Indic.1
On
Indication IND1 Off
IND_TR
Indic.1
Off
Indication IND2 On
IND_TR
Indic.2
10
On
Indication IND2 Off
IND_TR
Indic.2
10
Off
Indication IND3 On
IND_TR
Indic.3
11
On
Indication IND3 Off
IND_TR
Indic.3
11
Off
Indication IND4 On
IND_TR
Indic.4
12
On
Indication IND4 Off
IND_TR
Indic.4
12
Off
190
3BSE030340R4101
Motor Control MOTCON

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Control voltage absent
I1_TR
ControlV
Alarm
Control voltage restored
I1_TR
ControlV
Normal
Bimetal relay has tripped
I1_TR
BimetalR
Alarm
Bimetal relay triggered
I1_TR
BimetalR
Normal
Local Stop
I1_TR
LStop
Alarm
Local Stop ended
I1_TR
LStop
Normal
Safety Monitor tripped
I1_TR
SafeMon
Alarm
Safety Monitor triggered
I1_TR
SafeMon
Normal
Main contactor Error
I1_TR
MainCErr
Alarm
Main contactor Error

acknowledged
I1_TR
MainCErr
Normal
Monitor Low tripped
I1_TR
MonLow
Alarm
Monitor Low restored
I1_TR
MonLow
Normal
Monitor High tripped
I1_TR
MonHigh
Alarm
Monitor High restored
I1_TR
MonHigh
Normal
Position A reached
I1_TR
Pos A
Alarm
Position A left
I1_TR
Pos A
Normal
Current limit 100 % exceeded I1_TR
HighCurr
11
Alarm
Current limit 100 % reentered
I1_TR
HighCurr
11
Normal
Position B reached
I1_TR
Pos B
12
Alarm
Position B left
I1_TR
Pos B
12
Normal
3BSE030340R4101
191
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Control mode Local On
I2_TR
Local
On
Control mode Local Off
I2_TR
Local
Off
Control mode Test On
I2_TR
Test
On
Control mode Test Off
I2_TR
Test
Off
Control mode Standby On
I2_TR
Standby
On
Control mode Standby Off
I2_TR
Standby
Off
Control mode Sequence On
I2_TR
Sequence
On
Control mode Sequence Off
I2_TR
Sequence
Off
Op. mode Auto On
I2_TR
Auto
On
Op. mode Auto Off
I2_TR
Auto
Off
Interlock IC1 On
I2_TR
CInterl1
On
Interlock IC1 Off
I2_TR
CInterl1
Off
Interlock IC2 On
I2_TR
CInterl2
10
On
Interlock IC2 Off
I2_TR
CInterl2
10
Off
Interlock IB1 On
I2_TR
BInterl1
13
On
Interlock IB1 Off
I2_TR
BInterl1
13
Off
Interlock IB2 On
I2_TR
BInterl2
14
On
Interlock IB2 Off
I2_TR
BInterl2
14
Off
Interlock IB3 On
I2_TR
BInterl3
11
On
Interlock IB3 Off
I2_TR
BInterl3
11
Off
Interlock IB4 On
I2_TR
BInterl4
12
On
Interlock IB4 Off
I2_TR
BInterl4
12
Off
192
3BSE030340R4101
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Interlock IA On
I2_TR
AInterl
15
Off
Interlock IA Off
I2_TR
AInterl
15
Off
Control mode Local
ORD_TR
Local
Order
Control mode Test
ORD_TR
Test
Order
Control mode Standby
ORD_TR
Standby
Order
Control mode Central
ORD_TR
Central
Order
Control mode Sequence
ORD_TR
Sequence
13
Order
Op. mode Auto
ORD_TR
Auto
Order
Op. mode Manual
ORD_TR
Manual
Order
Blocking of IB1 and IB3

Interlock
ORD_TR
Blk.BI
Order
Deblocking of IB1 and IB3

Interlock
ORD_TR
Norm.BI
Order
Order Forward
ORD_TR
Forward
Order
Order Reverse
ORD_TR
Reverse
10
Order
Order Start
ORD_TR
Start
11
Order
Order Stop
ORD_TR
Stop
12
Order
3BSE030340R4101
193
Valve Control VALVECON

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
User defined Fault 1 coming
I1_TR
F1
Alarm
User defined Fault 1 passing
I1_TR
F1
Normal
I1_TR
F2
Alarm
I1_TR
F2
Normal
Position error open coming
I1_TR
PosErrO
Alarm
Position error open passing
I1_TR
PosErrO
Normal
Position error closed coming
I1_TR
PosErrC
Alarm
Position error closed passing
I1_TR
PosErrC
Normal
Valve in open position
I1_TR
Pos O
Alarm
Valve changes from open

position
I1_TR
Pos O
Normal
Valve in closed position
I1_TR
Pos C
12
Alarm
Valve changes from closed

position
I1_TR
Pos C
12
Normal
Valve in intermediate position I1_TR
IntPos
16
Alarm
Valve not in intermediate

position
I1_TR
IntPos
16
Normal
I2_TR
Local
On
I2_TR
Local
Off
I2_TR
Test
On
I2_TR
Test
Off
I2_TR
Standby
On
194
3BSE030340R4101
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Control mode Standby Off
I2_TR
Standby
Off
I2_TR
Sequence
On
I2_TR
Sequence
Off
Op. mode Auto On
I2_TR
Auto
On
Op. mode Auto Off
I2_TR
Auto
Off
Interlock IC1 On
I2_TR
CInterl1
On
Interlock IC1 Off
I2_TR
CInterl1
Off
Interlock IC2 On
I2_TR
CInterl2
10
On
Interlock IC2 Off
I2_TR
CInterl2
10
Off
Interlock IB1 On
I2_TR
BInterl1
11
On
Interlock IB1 Off
I2_TR
BInterl1
11
Off
Interlock IB2 On
I2_TR
BInterl2
12
On
Interlock IB2 Off
I2_TR
BInterl2
12
Off
Interlock IB3 On
I2_TR
BInterl3
13
On
Interlock IB3 Off
I2_TR
BInterl3
13
Off
Interlock IB4 On
I2_TR
BInterl4
14
On
Interlock IB4 Off
I2_TR
BInterl4
14
Off
Interlock IA On
I2_TR
AInterl
15
On
Interlock IA Off
I2_TR
AInterl
15
Off
Op. mode Local
ORD_TR
Local
Order
Op. mode Test
ORD_TR
Test
Order
Control mode Standby
ORD_TR
Standby
Order
3BSE030340R4101
195
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Control mode Central
ORD_TR
Central
Order
Control mode Sequence
ORD_TR
Sequence
11
Order
Op. mode Auto
ORD_TR
Auto
Order
Op. mode Manual
ORD_TR
Manual
Order
Blocking of IB1 and IB3

Interlock
ORD_TR
Blk.BI
Order
Deblocking of IB1 and IB3

Interlock
ORD_TR
Norm.BI
Order
Order Open
ORD_TR
Open
Order
Order Close
ORD_TR
Close
10
Order
196
3BSE030340R4101
Group Start GROUP
Group Start GROUP

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Timeout sequence
I1_TR
Timeout G
Alarm
Timeout sequence
acknowledged
I1_TR
Timeout G
Normal
Timeout step
I1_TR
Timeout S
Alarm
Timeout step acknowledged
I1_TR
Timeout S
Normal
I1_TR
Fault 3
Alarm
I1_TR
Fault 3
Normal
I1_TR
Fault 4
Alarm
I1_TR
Fault 4
Normal
I1_TR
Fault 5
Alarm
I1_TR
Fault 5
Normal
Position A reached
I1_TR
Pos A
Alarm
Position A left
I1_TR
Pos A
Normal
Position B reached
I1_TR
Pos B
12
Alarm
Position B left
I1_TR
Pos B
12
Normal
I2_TR
Local
On
I2_TR
Local
Off
I2_TR
Test
On
I2_TR
Test
Off
I2_TR
Standby
On
Control mode Standby Of
I2_TR
Standby
Off
2f
3BSE030340R4101
197
Group Start GROUP
Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
I2_TR
Sequence
On
I2_TR
Sequence
Off
Op. mode Auto On
I2_TR
Auto
On
Op. mode Auto Off
I2_TR
Auto
Off
Interlock IC1 On
I2_TR
CInterl1
On
Interlock IC1 Off
I2_TR
CInterl1
Off
Interlock IC2 On
I2_TR
CInterl2
10
On
Interlock IC2 Off
I2_TR
CInterl2
10
Off
Interlock IB1 On
I2_TR
BInterl1
13
On
Interlock IB1 Off
I2_TR
BInterl1
13
Off
Interlock IB2 On
I2_TR
BInterl2
14
On
Interlock IB2 Off
I2_TR
BInterl2
14
Off
Interlock IB3 On
I2_TR
BInterl3
11
On
Interlock IB3 Off
I2_TR
BInterl3
11
Off
Interlock IB4 On
I2_TR
BInterl4
12
On
Interlock IB4 Off
I2_TR
BInterl4
12
Off
Interlock IA On
I2_TR
AInterl
15
On
Interlock IA Off
I2_TR
AInterl
15
Off
198
3BSE030340R4101
Group Alarm GRPALARM
Group Alarm GRPALARM

Property text
Events
Event Treat
pointer
Standard
text
Line No in
Event Treat
Event text
Standard
text
Line No in
Event Treat
Abnormal position Off
DISTR_TR
Disturb
Alarm
Abnormal position On
DISTR_TR
Disturb
Normal
DISTR_TR
Alarm
Blocked
Deblocking of event handling
DISTR_TR
Alarm
Deblocked
DISTR_TR
Printout
Blocked
DISTR_TR
Printout
Deblocked
Blocking master On
PREV_TR
Blk Master
On
Blocking master Off
PREV_TR
Blk Master
Off
First error On
PREV_TR
First Err
On
First error Off
PREV_TR
First Err
Off
Prevent event handling On
PREV_TR
Event
Blocked
Prevent event handling Off
PREV_TR
Event
Deblocked
Blocking of the members

event handling
PREV_TR
MembAlar
m
Blocked
Deblocking of the members

event handling
PREV_TR
MembAlar
m
Deblocked
Blocking of the members

event printout
PREV_TR
MembPrint
Blocked
Deblocking of the members

event printout
PREV_TR
MembPrint
Deblocked
3BSE030340R4101
199
Motor Control MOTCONI

Alarms and events in this context are divided in three groups:
Warnings, alarms from the Motor Controller Unit (MCU) which does not trip
the motor. Acknowledge by operator. Color: Yellow
Alarms, alarms from the MCU which trips the motor. Acknowledge by
operator. Color: Red.
Events, appears only in the event list. Not able to acknowledge. Color: Green.
Some alarms are reported from the PC element MOTCON directly, such as
communication error. Most events and alarms are however generated and time
stamped in the Motor Control Unit itself, for best possible time resolution, and sent
via the LONWORKS network to the Controller.
Figure 86 below shows the principles for how the events are translated and
associated to proper texts in the Operator Station.
Advant Controller 410/450
Operator Station
PC-Program
MOTCON
MMCXx
UserControl
LonWorks Network
CI572
LONDEVx
LON Device
EV_BLK
LONEVTRx
ALOBJx
Event &
Alarm
handling
AL_BLK
I1_EVBLK
I2_EVBLK
I1_TR
I2_TR
IND1
IND2
Alar m list
Event list
EVENT346..352
Event Treat
Texts
Figure 86. Event handling from LONWORKS Network to Operator station in principles
200
3BSE030340R4101
In principle, the following processing is done in the Controller for every event
message received from the MCU via network variable 2040:
The LONDEV data base element that represents the sending device (MCU) is
recognized.
The LONDEV data base element points out three objects, of type MMCX. One
object for warnings (ALOBJ1), one for alarms (ALOBJ2) and one for
events(ALOBJ3). Each MMCX object can deal with up to 32 different
warning/alarm/event indications. The event message is then forwarded to each
alarm object.
The MMCX object in its turn forwards all state transitions to the Operator
stations for presentation according to defined treatment and texts defined by
terminals I1_TR or I2_TR. The treatment is divided in groups represented by
data base element Event Treat. For each group different handling can be
selected for status changes 0 to 1 and 1 to 0 respectively see Table E-6.
It is possible to block the update of events and alarms in different manners. It could
be done either from the operators dialog affecting all alarms and events from each
MCU. Separate alarms could be blocked by the bit masks I1_EVBLK and
I2_EVBLK in MMCX data base element. The terminal EV_BLK in LONDEV data
base element could also be used to block events received from each MCU.
The translation of events and alarms for MOTCONI is described below. They are
divided into four groups. For each group one data base element MMCX is needed.
The groups are:
Alarm from MOTCON PC element
Warnings directly from MCU
Alarm directly from MCU
Events directly from MCU
3BSE030340R4101
201
Standard Alarm Text from MOTCON PC element
See Table E-1 for network variable bindnings that has to be done to correctly receive
events and alarms from MCU.
Table 12. Network Variable bindings needed for event and alarm handling from MCU
CI572
Description
MCU
SNVT
NV-Index
NV-Name
NV-Index
NV-Name
Clock Warning, broadcast from

CI572 before the clock
synchronization message
2042
nvoClockWrng
nviClockWrng
Clock synchronization
broadcast message. The send
interval is defined by
LONCHAN database element
2041
nvoClock
nviClock
Alarm Report message with

warnings, alarms, events and
time stamp
2040
nviAlarmReport
51
nvoAlarmReport

Table 13. Alarms reported from MOTCON PC element, translated via data base element
EVENT352
Description
IND bit
in
MMCX
Property text
Event
Text
Communication error
IND1_00
CommErr
Warning
Normal
Over load
IND1_01
Overload
Warning
Normal
Local Stop
IND1_02
LStop
Warning
Normal
202
3BSE030340R4101
Table 13. Alarms reported from MOTCON PC element, translated via data base element EVENT352
(Continued)
Emergency stop
IND1_03
EStop
Warning
Normal
Main contactor error
IND1_04
MainCErr
Warning
Normal
Monitor low
IND1_05
MonLow
Warning
Normal
Monitor high
IND1_06
MonHigh
Warning
Normal
3BSE030340R4101
203
Standard Warning Texts from MCU
Table 14. Warnings reported from MCU, translated via data base element EVENT346 or
EVENT347
Description
IND bit
in MMCX
Event
Treat
element
Property text
Event
Text
Thermal Overload
IND1_00
EVENT346
ThermOL
Warning
Normal
Phase Loss L1
IND1_01
EVENT346
PhLossL1
Warning
Normal
Phase Loss L2
IND1_02
EVENT346
PhLossL2
Warning
Normal
Phase Loss L3
IND1_03
EVENT346
PhLossL3
Warning
Normal
Under load
IND1_04
EVENT346
UndLoad
Warning
Normal
No load
IND1_05
EVENT346
NoLoad
Warning
Normal
Stall
IND1_06
EVENT346
Stall
Warning
Normal
Feedback CFA
IND1_07
EVENT346
FeedbCFA
Warning
Normal
Feedback CFB
IND1_08
EVENT346
FeedbCFB
Warning
Normal
204
3BSE030340R4101
Table 14. Warnings reported from MCU, translated via data base element EVENT346 or EVENT347
(Continued)
Feedback CFC
IND1_09
EVENT346
FeedbCFC
Warning
Normal
Earth Fault
IND1_10
EVENT346
EarthFlt
Warning
Normal
Unbalance
IND1_11
EVENT346
UnBalanc
Warning
Normal
U/L Cosphi
IND1_12
EVENT346
Cosphi
Warning
Normal
Rotation
IND1_13
EVENT346
Rotation
Warning
Normal
PTC temperature
IND1_14
EVENT346
PTCtemp
Warning
Normal
Under Voltage
IND1_15
EVENT346
UnderVlt
Warning
Normal
Start limitation
IND2_00
EVENT347
StartLim
Warning
Normal
Autoreclosuer
IND2_01
EVENT347
AutoRecl
Warning
Normal
Device temperature
IND2_02
EVENT347
Dev temp
Warning
Normal
O/L
IND2_03
EVENT347
Overload
Warning
Normal
Maintenance A
IND2_04
EVENT347
MaintenA
Warning
Normal
3BSE030340R4101
205
Table 14. Warnings reported from MCU, translated via data base element EVENT346 or EVENT347
(Continued)
Maintenance B
IND2_05
EVENT347
MaintenB
Warning
Normal
Maintenance C
IND2_06
EVENT347
MaintenC
Warning
Normal
Maintenance hour run
IND2_07
EVENT347
MaintMot
Warning
Normal
Fail-safe activated
IND2_08
EVENT347
FailSafe
Warning
Normal
No external memory
IND2_09
EVENT347
NoExtROM
Warning
Normal
ROM write fail
IND2_10
EVENT347
ROMWrFai
Warning
Normal
ROM read fail
IND2_11
EVENT347
ROMRdFai
Warning
Normal
Drawer location
IND2_12
EVENT347
DrawLoc
Warning
Normal
PTC short circuit
IND2_13
EVENT347
PTCshort
Warning
Normal
PTC open circuit
IND2_14
EVENT347
PTCopen
Warning
Normal
Startup inhibit
IND2_15
EVENT347
StrtInhb
Warning
Normal
206
3BSE030340R4101
Standard Alarm Text from MCU

Table 15. Alarms reported from MCU, translated via data base element EVENT348 or EVENT349
Description
IND bit
in MMCX
Event
Treat
element
Property text
Event
Text
Thermal Overload trip
IND1_00
EVENT348
ThermOL
Warning
Normal
Phase Loss trip L1
IND1_01
EVENT348
PhLossL1
Warning
Normal
Phase Loss trip L2
IND1_02
EVENT348
PhLossL2
Warning
Normal
Phase Loss trip L3
IND1_03
EVENT348
PhLossL3
Warning
Normal
Under load trip
IND1_04
EVENT348
UndLoad
Warning
Normal
No load trip
IND1_05
EVENT348
NoLoad
Warning
Normal
Stall trip
IND1_06
EVENT348
Stall
Warning
Normal
Feedback trip CFA
IND1_07
EVENT348
FeedbCFA
Warning
Normal
Feedback trip CFB
IND1_08
EVENT348
FeedbCFB
Warning
Normal
Feedback trip CFC
IND1_09
EVENT348
FeedbCFC
Warning
Normal
3BSE030340R4101
207
Earth fault trip
IND1_10
EVENT348
EarthFlt
Warning
Normal
Unbalance trip
IND1_11
EVENT348
UnBalanc
Warning
Normal
U/L Cosphi trip
IND1_12
EVENT348
Cosphi
Warning
Normal
Rotation trip
IND1_13
EVENT348
Rotation
Warning
Normal
PTC temperature trip
IND1_14
EVENT348
PTCtemp
Warning
Normal
Under Voltage trip
IND1_15
EVENT348
UnderVlt
Warning
Normal
Start limitation trip
IND2_00
EVENT349
StartLim
Warning
Normal
PTC short circuit trip
IND2_01
EVENT349
PTCshort
Warning
Normal
PTC open circuit trip
IND2_02
EVENT349
PTCopen
Warning
Normal
Torque trip
IND2_03
EVENT349
TorqTrip
Warning
Normal
Parametering failure
IND2_04
EVENT349
ParamFail
Warning
Normal
External trip
IND2_05
EVENT349
ExtTrip
Warning
Normal
208
3BSE030340R4101
Standard Event Text from MCU
Test mode failure trip
IND2_06
EVENT349
TestTrip
Warning
Normal
EM stop activated
IND2_07
EVENT349
EMstop
Warning
Normal
Internal fault trip
IND2_08
EVENT349
InterFlt
Warning
Normal
External trip command
IND2_09
EVENT349
ExTrpCmd
Warning
Normal
Main switch OFF
IND2_10
EVENT349
MainSwOf
Warning
Normal
spare
IND2_11
EVENT349
spare
Warning
Normal
MCB trip
IND2_12
EVENT349
MCBtrip
Warning
Normal
Motor still running
IND2_13
EVENT349
MotIsRun
Warning
Normal
Start Interlock trip
IND2_14
EVENT349
StrtIntl
Warning
Normal
Standard Event Text from MCU
Table 16. Events reported from MCU, translated via data base element EVENT350 or EVENT351
Description
3BSE030340R4101
IND bit
in MMCX
Event
Treat
element
Property text
Event
Text
209
Event Treatment in Operator Station
Table 16. Events reported from MCU, translated via data base element EVENT350 or EVENT351
TOL reset level reached
IND1_00
EVENT350
TolResLv
McuEvent
Motor started 1
IND1_01
EVENT350
MotStrt1
McuEvent
Motor started 2
IND1_02
EVENT350
MotStrt2
McuEvent
Motor stopped
IND1_03
EVENT350
MotorStp
McuEvent
Control mode local
IND1_04
EVENT350
Local
McuEvent
Main switch in Test-position
IND1_05
EVENT350
TestPos
McuEvent
Trip reset
IND1_06
EVENT350
TripRes
McuEvent
Device set to off-line
IND1_07
EVENT350
Off-line
McuEvent
Motor started CW by RCU-switch
IND1_08
EVENT350
RcuStrt1
McuEvent
Motor stopped by RCU-switch
IND1_09
EVENT350
RcuStop
McuEvent
Motor started CCW by RCU-switch
IND1_10
EVENT350
RcuStrt2
McuEvent
Trip bypass activated
IND1_11
EVENT350
TrpBypas
McuEvent
Motor stopped by limit position 1
IND1_12
EVENT350
StopLim1
McuEvent
Motor stopped by limit position 2
IND1_13
EVENT350
StopLim2
McuEvent
Start interlock alarm
IND2_01
EVENT351
StrtIntl
McuEvent
Event Treatment in Operator Station

The treatment of events and alarms in Operator Station (such as color of event line,
audible alarm or not, text line appearance) is defined in the EVENT Treat database
element. The table below describes the predefined settings for different Event Treat
elements for MOTCONI.
Table 17. Predefined Event treatment for MOTCONI
Index of EVENT treatment data base element
Terminal
AUDIBLE
210
352
346
347
348
349
350
351
3BSE030340R4101
Engineered Drive, DRICONE
Table 17. Predefined Event treatment for MOTCONI

AL_PRIO
AL_TOBLK
No
No
No
No
No
Yes
Yes
AL_FRBLK
Yes
Yes
Yes
Yes
Yes
Yes
Yes
PERSISTB
No
No
No
No
No
Yes
Yes
TEXT_TOB
No
No
No
No
No
No
No
TEXT_FRB
No
No
No
No
No
Yes
Yes
TEXTCOM
B

This section describes the principles for events and alarms, the standard event texts
for DRICONE main data base element and DRICONE fault and alarm data base
elements. The section contains also a layout of the Event Treat configuration for
DRICONE.
Figure 86 shows diagrammatically the relation between indications and the
parameters which can be used to block event handling for certain indications and
points out a required handling in the operators station.
3BSE030340R4101
211
The possibilities of the operator to block event printouts and alarms are shown under
the heading Event and alarm blocking below.
Advant Station 500 Series
Operator Station
Parameters
Data base element
PC element MMC-IND
Fault in Drive
Limit
Warning from Drive
I1_EVBLK
IND 1
I1_TR
Blocking
of
required
events
Event Treat
Event treat
pointer
Defines
- Event/Alarm
- Acoustic alarm
- Layout of texts
- Std. texts
etc.
Figure 87. Event Handling Principles

The events are divided into groups. One pointer is allocated to each group which
means that the individual events of the group are, in several respects, handled in the
same way in Advant Station 500 Series Operator Station. For each group different
handling can be selected for status changes 0-->1 and 1-->0 respectively. The texts
which are written out in different lists are individual for each event. The group
division - which events are associated with the pointer - is given in Event
description with standard texts below. This also specifies which event handling is
obtained as default and which alternative standard function.
212
3BSE030340R4101
Table 18. Event Text for Main MMCX Data Base Element, EVENT Treat element 334 - 335
Property text
Signal
Events
Event
Treat
pointer
Standard text
Event Text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_01
Out of window
I1_TR
Speed Outside
Window
Alarm
IND1_01
Within window
I1_TR
Speed Outside
Window
Normal
IND1_02
Emergency stop
I1_TR
Emergency Stop Fault
Alarm
IND1_02
No Emergency
stop
I1_TR
Emergency Stop Fault
Normal
IND1_04
Run disabled
I1_TR
Run Disabled
Alarm
IND1_04
Run enabled
I1_TR
Run Disabled
Normal
IND1_06
First start not

done
I1_TR
First start not done
Alarm
IND1_06
First start done
I1_TR
First start not done
Normal
IND1_07
Alarm from drive
I1_TR
Alarm from drive
Alarm
IND1_07
No alarm
I1_TR
Alarm from drive
Normal
IND1_08
Start inhibition
I1_TR
False Start Inhibit
Alarm
IND1_08
No start inhibition
I1_TR
False Start Inhibit
Normal
IND1_09
Limit exceeded
I1_TR
Limit
10
Alarm
IND1_09
No Limit
I1_TR
Limit
10
Normal
IND1_11
Fault from drive
I1_TR
Fault in Drive
12
Alarm
IND1_11
No fault
I1_TR
Fault in Drive
12
Normal
IND1_12
Communication
fault
I1_TR
Communication Error
13
Alarm
3BSE030340R4101
213
IND1_12
Communication
fault
I1_TR
Communication Error
13
Normal
IND2_00
In service ready
to switch on
I2_TR
In service
On
IND2_00
Not in service
I2_TR
In service
Off
IND2_01
Drive ready to
start
I2_TR
Ready to Start
On
IND2_01
Drive is not ready

to start
I2_TR
Ready to Start
Off
IND2_02
Running with
selected
reference
I2_TR
Run
On
IND2_02
Stopped
I2_TR
Run
Off
IND2_03
Motor is
magnetized
I2_TR
Motor Magnetized
On
IND2_03
Motor is not
magnetized
I2_TR
Motor Magnetized
Off
IND2_04
OFF 2
I2_TR
Emergency
On
IND2_04
No OFF 2
I2_TR
Emergency
Off
IND2_05
OFF 3
I2_TR
Emergency stop
On
IND2_05
No OFF 3
I2_TR
Emergency stop
Off
IND2_06
Switch on is
inhibited
I2_TR
Inhibit Switch On
Yes
IND2_06
Switch on is not
inhibited
I2_TR
Inhibit Switch On
No
IND2_07
Drive runs at
setpoint
I2_TR
At Setpoint
On
IND2_07
Drive is not at
setpoint
I2_TR
At Setpoint
Off
214
3BSE030340R4101
IND2_08
C-Interlock
I2_TR
C-Interlock
On
IND2_08
C-Interlock
I2_TR
C-Interlock
Off
IND2_09
Drive runs
remotely
controlled
I2_TR
Remote
10
On
IND2_09
Drive runs locally

controlled
I2_TR
Remote
10
Off
IND2_10
B-Interlock 1
I2_TR
B-Interlock 1
11
On
IND2_10
B-Interlock 1
I2_TR
B-Interlock 1
11
Off
IND2_11
B-Interlock 2
I2_TR
B-Interlock 2
12
On
IND2_11
B-Interlock 2
I2_TR
B-Interlock 2
12
Off
IND2_12
B-Interlock 3
I2_TR
B-Interlock 3
13
On
IND2_12
B-Interlock 3
I2_TR
B-Interlock 3
13
Off
IND2_13
B-Interlock 4
I2_TR
B-Interlock 4
14
On
IND2_13
B-Interlock 4
I2_TR
B-Interlock 4
14
Off
IND2_14
A-Interlock
I2_TR
A-Interlock
15
On
IND2_14
A-Interlock
I2_TR
A-Interlock
15
Off
IND2_15
Override interlock
I2_TR
Override Interlock
16
On
IND2_15
Dont override
interlock
I2_TR
Override Interlock
16
Off
3BSE030340R4101
215
Table 19. Event Text for Fault MMCX Data Base Element ACS type of Drive, EVENT Treat element
336 - 337
Property text
Signal
Events
Event Text
Event
Treat
pointer
Standard text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_0
0
Short circuit
I1_TR
Short Circuit
Fault
IND1_0
0
Short circuit
I1_TR
Short Circuit
Normal
IND1_0
1
Over current
I1_TR
Over Current
Fault
IND1_0
1
Over current
I1_TR
Over Current
Normal
IND1_0
2
DC over voltage fault
I1_TR
DC Over Voltage
Fault
IND1_0
2
No DC over voltage
fault
I1_TR
DC Over Voltage
Normal
IND1_0
3
Power plate over

temperature fault
I1_TR
Over Temp Pow

Plate
Fault
IND1_0
3
No power plate over

temperature fault
I1_TR
Over Temp Pow

Plate
Normal
IND1_0
4
Earth fault
I1_TR
Earth Fault
Fault
IND1_0
4
No earth fault
I1_TR
Earth Fault
Normal
IND1_0
5
Motor over temperature

fault
I1_TR
Over Temp Motor
Fault
IND1_0
5
No motor over
temperature fault
I1_TR
Over Temp Motor
Normal
216
3BSE030340R4101
336 - 337 (Continued)
IND1_0
6
Motor over load fault
I1_TR
Over Load Motor
Fault
IND1_0
6
No motor over load

fault
I1_TR
Over Load Motor
Normal
IND1_0
7
System fault
I1_TR
System Fault
Fault
IND1_0
7
No system fault
I1_TR
System Fault
Normal
IND1_0
8
Under load fault
I1_TR
Under Load
Fault
IND1_0
8
No under load fault
I1_TR
Under Load
Normal
IND1_0
9
Over speed fault
I1_TR
Over Speed
10
Fault
IND1_0
9
No over speed fault
I1_TR
Over Speed
10
Normal
IND1_1
0
Supply Section fault
I1_TR
Supply Section
11
Fault
IND1_1
0
No Supply Section fault
I1_TR
Supply Section
11
Normal
IND1_1
1
Master/Follower fault
I1_TR
Master/Follower
12
Fault
IND1_1
1
No Master/Follower
fault
I1_TR
Master/Follower
12
Normal
IND1_1
2
Short circuit INT1
I1_TR
Short circuit INT1
13
Fault
IND1_1
2
No Short circuit INT1
I1_TR
Short Circuit Int1
13
Normal
IND1_1
3
Short circuit INT2
I1_TR
Short Circuit Int2
14
Fault
3BSE030340R4101
217
IND1_1
3
I1_TR
Short Circuit Int2
14
Normal
IND1_1
4
Short circuit INT3
I1_TR
Short Circuit Int3
15
Fault
IND1_1
4
I1_TR
Short Circuit Int3
15
Normal
IND1_1
5
Short circuit INT4
I1_TR
Short Circuit Int4
16
Fault
IND1_1
5
I1_TR
Short Circuit Int4
16
Normal
IND2_0
0
Supply section fault
I2_TR
Supply Section
Fault
IND2_0
0
No supply section fault
I2_TR
Supply Section
Normal
IND2_0
2
DC under voltage
I2_TR
DC Under Voltage
Fault
IND2_0
2
No DC under voltage
I2_TR
DC Under Voltage
Normal
IND2_0
4
Run disabled
I2_TR
Run Disabled
Fault
IND2_0
4
Run enabled
I2_TR
Run Disabled
Normal
IND2_0
5
Encoder fault
I2_TR
Speed Encoder
Fault
IND2_0
5
No encoder fault
I2_TR
Speed Encoder
Normal
IND2_0
6
I/O link fault channel 1
I2_TR
I/O Link channel 1
Fault
IND2_0
6
No I/O link fault

channel 1
I2_TR
I/O Link channel 1
Normal
218
3BSE030340R4101
IND2_0
7
Cabinett
overtemperature
I2_TR
Cabinett overtemp
Fault
IND2_0
7
No Cabinett
overtemperature
I2_TR
Cabinett overtemp
Normal
IND2_0
9
Over svitching
frequency
I2_TR
Over Switching
10
Fault
IND2_0
9
No over switching
frequency
I2_TR
Over Switching
10
Normal
IND2_1
1
PPCC link fault
I2_TR
PPCC Link
12
Fault
IND2_1
1
No PPCC link fault
I2_TR
PPCC Link
12
Normal
IND2_1
2
Communication fault
Channel 0
I2_TR
Communication
Ch 0
13
Fault
IND2_1
2
No Communication
fault Channel 0
I2_TR
Communication
Ch 0
13
Normal
IND2_1
3
Pannel loss
I2_TR
Pannel loss
14
Fault
IND2_1
3
No pannel loss
I2_TR
Pannel loss
14
Normal
IND2_1
4
Motor stalled
I2_TR
Motor Stalled
15
Fault
IND2_1
4
No motor stalled
I2_TR
Motor Stalled
15
Normal
IND2_1
5
Motor phase missing
I2_TR
Motor Phase
Missing
16
Fault
IND2_1
5
No motor phase
missing
I2_TR
Motor Phase
Missing
16
Normal
3BSE030340R4101
219
Table 20. Event Text for Alarm MMCX Data Base Element ACS type of Drive, EVENT Treat element
338 - 339
Property text
Signal
Events
Event Text
Event
Treat
pointer
Standard text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_0
0
Prevent unexpected
start
I1_TR
Prevent Start
Alarm
IND1_0
0
No preventation of
unexpected start
I1_TR
Prevent Start
Normal
IND1_0
1
Emergency stop
I1_TR
Emergency Stop
Alarm
IND1_0
1
Emergency stop
I1_TR
Emergency Stop
Normal
IND1_0
2
Measured motor temp

alarm
I1_TR
Meas. Motor
Temp
Alarm
IND1_0
2
Measured motor temp

alarm
I1_TR
Meas. Motor
Temp
Normal
IND1_0
3
Over temperature
alarm of the thermal
model
I1_TR
Motor Overload
Alarm
IND1_0
3
No over temperature
model
I1_TR
Motor Overload
Normal
IND1_0
4
Power plate over

temperature alarm
I1_TR
Temp Power Plate
Alarm
IND1_0
4
No power plate over

temperature alarm
I1_TR
Temp Power Plate
Normal
IND1_0
5
Pulse encoder alarm
I1_TR
Pulse Encoder
Alarm
220
3BSE030340R4101
IND1_0
5
No Pulse encoder
alarm
I1_TR
Pulse Encoder
Normal
IND1_0
7
Standard digital I/O

alarm
I1_TR
Standard Digital
I/O
Alarm
IND1_0
7
No Standard digital I/O

alarm
I1_TR
Standard Digital
I/O
Normal
IND1_0
8
Standard analogue I/O

alarm
I1_TR
Standard Analog
I/O
Alarm
IND1_0
8
No Standard analogue
I/O alarm
I1_TR
Standard Analog
I/O
Normal
IND1_0
9
External digital I/O

alarm
I1_TR
Ext. Digital I/O
10
Alarm
IND1_0
9
No External digital I/O

alarm
I1_TR
Ext. Digital I/O
10
Normal
IND1_1
0
External analogue I/O

alarm
I1_TR
Ext. Analog I/O
11
Alarm
IND1_1
0
No External analogue
I/O alarm
I1_TR
Ext. Analog I/O
11
Normal
IND1_1
1
Master - Follower
alarm
I1_TR
Master - Follow
alarm
12
Alarm
IND1_1
1
Master - Follower
alarm
I1_TR
Master - Follow
alarm
12
Normal
IND1_1
2
Communication alarm
Channel 0
I1_TR
Comm. Channel 0
13
Alarm
IND1_1
2
Communication alarm
Channel 0
I1_TR
Comm. Channel 0
13
Normal
IND1_1
4
Earth fault alarm
I1_TR
Earth fault
15
Alarm
IND1_1
4
No Earth fault alarm
I1_TR
Earth fault
15
Normal
3BSE030340R4101
221
IND2_0
0
Power failure
I2_TR
Power Failure
Alarm
IND2_0
0
No power failure
I2_TR
Power Failure
Normal
IND2_0
1
Under load alarm
I2_TR
Under Load
Alarm
IND2_0
1
No under load alarm
I2_TR
Under Load
Normal
IND2_0
2
Identity run
I2_TR
Identity run
Alarm
IND2_0
2
No Identity run
I2_TR
Identity run
Normal
IND2_0
3
DC under voltage
alarm
I2_TR
DC Under Voltage
Alarm
IND2_0
3
No DC under voltage
alarm
I2_TR
DC Under Voltage
Normal
IND2_0
4
DC over voltage alarm
I2_TR
DC Over Voltage
Alarm
IND2_0
4
No DC over voltage
alarm
I2_TR
DC Over Voltage
Normal
IND2_0
5
Over current alarm
I2_TR
Over Current
Alarm
IND2_0
5
No over current alarm
I2_TR
Over Current
Normal
IND2_0
6
Over frequency alarm
I2_TR
Over Frequency
Alarm
IND2_0
6
No over frequency
alarm
I2_TR
Over Frequency
Normal
IND2_0
7
Power failure file
I2_TR
Power Failure file
Alarm
222
3BSE030340R4101
IND2_0
7
No power failure file
I2_TR
Power Failure file
Normal
IND2_0
8
Power down file
I2_TR
Power Down file
Alarm
IND2_0
7
No power down file
I2_TR
Power Down file
Normal
IND2_0
8
Motor stalled alarm
I2_TR
Stall
Alarm
IND2_0
8
No motor stalled alarm
I2_TR
Stall
Normal
IND2_0
9
Supply phase
I2_TR
Supply Phase
10
Alarm
IND2_0
9
No supply phase
missing
I2_TR
Supply Phase
10
Normal
IND2_1
0
Timeout channel 0
I2_TR
DDCS Timeout
Ch0
11
Alarm
IND2_1
0
No timeout channel 0
I2_TR
DDCS Timeout
Ch0
11
Normal
IND2_1
3
Pannel loss
I2_TR
Pannel loss
14
Alarm
IND2_1
3
No pannel loss
I2_TR
Pannel loss
14
Normal
3BSE030340R4101
223
Table 21. Event Text for Main MMCX Data Base Element DCS type of Drive, EVENT Treat element
340 - 341
Property text
Signal
Events
Event Text
Event
Treat
pointer
Standard text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_07
Alarm from drive
I1_TR
Alarm from drive
Alarm
IND1_07
No alarm
I1_TR
Alarm from drive
Normal
IND1_11
Fault from drive
I1_TR
Fault in Drive
12
Alarm
IND1_11
No fault
I1_TR
Fault in Drive
12
Normal
IND1_12
Communication fault
I1_TR
Communication
Error
13
Alarm
IND1_12
Communication fault
I1_TR
Communication
Error
13
Normal
IND2_00
In service ready to
switch on
I2_TR
In service
On
IND2_00
Not in service
I2_TR
In service
Off
IND2_01
Drive ready to start
I2_TR
Ready to Start
On
IND2_01
Drive is not ready to

start
I2_TR
Ready to Start
Off
IND2_02
Running with selected

reference
I2_TR
Run
On
IND2_02
Stopped
I2_TR
Run
Off
IND2_08
C-Interlock
I2_TR
C-Interlock
On
IND2_08
C-Interlock
I2_TR
C-Interlock
Off
IND2_10
B-Interlock 1
I2_TR
B-Interlock 1
11
On
IND2_10
B-Interlock 1
I2_TR
B-Interlock 1
11
Off
224
3BSE030340R4101
Table 21. Event Text for Main MMCX Data Base Element DCS type of Drive, EVENT Treat element
IND2_11
B-Interlock 2
I2_TR
B-Interlock 2
12
On
IND2_11
B-Interlock 2
I2_TR
B-Interlock 2
12
Off
IND2_12
B-Interlock 3
I2_TR
B-Interlock 3
13
On
IND2_12
B-Interlock 3
I2_TR
B-Interlock 3
13
Off
IND2_13
B-Interlock 4
I2_TR
B-Interlock 4
14
On
IND2_13
B-Interlock 4
I2_TR
B-Interlock 4
14
Off
IND2_14
A-Interlock
I2_TR
A-Interlock
15
On
IND2_14
A-Interlock
I2_TR
A-Interlock
15
Off
IND2_15
Override interlock
I2_TR
Override Interlock
16
On
IND2_15
Dont override interlock
I2_TR
Override Interlock
16
Off
Table 22. Event Text for Fault MMCX Data Base Element DCS type of Drive, EVENT Treat element
342 - 343
Property text
Signal
Events
Event
Treat
pointer
Standard text
Event Text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_0
0
Auxiliary under voltage
I1_TR
Auxil.
Undervoltage
Fault
IND1_0
0
Auxiliary under voltage
I1_TR
Auxil.
Undervoltage
Normal
IND1_0
1
Over current
I1_TR
Over Current
Fault
IND1_0
1
No Over current
I1_TR
Over Current
Normal
3BSE030340R4101
225
IND1_0
2
Armature over voltage

fault
I1_TR
Armature Overvolt.
Fault
IND1_0
2
No Armature over
voltage fault
I1_TR
Armature Overvolt.
Normal
IND1_0
3
Converter over
temperature fault
I1_TR
Overtemp Conv.
Fault
IND1_0
3
No converter over
temperature fault
I1_TR
Overtemp Conv.
Normal
IND1_0
4
Earth fault
I1_TR
Earth fault
Fault
IND1_0
4
No earth fault
I1_TR
Earth fault
Normal
IND1_0
5
Motor 1 over
temperature fault
I1_TR
Motor 1 overtemp
Fault
IND1_0
5
No over temperature
fault motor 1
I1_TR
Motor 1 overtemp
Normal
IND1_0
6
Motor 1 over load fault
I1_TR
Motor 1 overload
Fault
IND1_0
6
No over load fault

motor 1
I1_TR
Motor 1 overload
Normal
IND1_0
7
I/O-board not found
I1_TR
I/O-board not
found
Fault
IND1_0
7
I/O-board found
I1_TR
I/O-board not
foundt
Normal
IND1_0
8
Motor 2 over
temperature fault
I1_TR
Motor 2 overtemp
Fault
IND1_0
8
No over temperature
fault motor 2
I1_TR
Motor 2 overtemp
Normal
IND1_0
9
Motor 2 over load fault
I1_TR
Motor 2 overload
10
Fault
226
3BSE030340R4101
IND1_0
9
No over load fault

motor 2
I1_TR
Motor 2 overload
10
Normal
IND1_1
1
Main supply under

voltage
I1_TR
Mains
undervoltage
12
Alarm
IND1_1
1
No main supply under

voltage
I1_TR
Mains
undervoltage
12
Normal
IND1_1
2
Main supply over

voltage
I1_TR
Mains overvoltage
13
Fault
IND1_1
2
No main supply over

voltage
I1_TR
Mains overvoltage
13
Normal
IND1_1
3
Not synchronized
I1_TR
Synchronism
14
Fault
IND1_1
3
Synchronized
I1_TR
Synchronism
14
Normal
IND1_1
4
Field exciter 1 over

current
I1_TR
Fld ex 1
overcurrent
15
Fault
IND1_1
4
No over current field

exciter 1
I1_TR
Fld ex 1
overcurrent
15
Normal
IND1_1
5
Field exciter 1
communication fault
I1_TR
Fld ex 1
commerror
16
Fault
IND1_1
5
No communication
fault field exciter 1
I1_TR
Fld ex 1
commerror
16
Normal
IND2_0
0
Armature current ripple
I2_TR
Arm current ripple
Fault
IND2_0
0
No armature current
ripple
I2_TR
Arm current ripple
Normal
IND2_0
1
Field exciter 2 over

current
I1_TR
Fld ex 2
overcurrent
Fault
IND2_0
1
No over current field

exciter 2
I1_TR
Fld ex 2
overcurrent
Normal
3BSE030340R4101
227
IND2_0
2
Field exciter 2
communication fault
I1_TR
Fld ex 2
commerror
Fault
IND2_0
2
No communication
fault field exciter 2
I1_TR
Fld ex 2
commerror
Normal
IND2_0
3
Phase sequence fault
I2_TR
Phase sequence
Fault
IND2_0
3
No phase sequence
fault
I2_TR
Phase sequence
Normal
IND2_0
4
No field acknowledge
I2_TR
Field acknowledge
Fault
IND2_0
4
Field acknowledge
I2_TR
Field acknowledge
Normal
IND2_0
5
Measured speed fault
I2_TR
Speed measured
Fault
IND2_0
5
No measured speed
fault
I2_TR
Speed measured
Normal
IND2_0
6
No external fan
acknowledge
I2_TR
Ext. Fan
acknowledge
Fault
IND2_0
6
External fan
acknowledge
I2_TR
Ext. Fan
acknowledge
Normal
IND2_0
7
No main contactor
acknowledge
I2_TR
Main cont ack
Fault
IND2_0
7
Main contactor
acknowledge
I2_TR
Main cont ack
Normal
IND2_0
8
Type coding fault
I2_TR
Type coding
Fault
IND2_0
8
No type coding fault
I2_TR
Type coding
Normal
IND2_0
9
Parameter backup fault
I2_TR
Par backup
10
Fault
228
3BSE030340R4101
IND2_0
9
No parameter backup
fault
I2_TR
Par backup
10
Normal
IND2_1
0
No central fan
acknowledge
I2_TR
C Fan ack
11
Fault
IND2_1
0
Central fan
acknowledge
I2_TR
C Fan ack
11
Normal
IND2_1
1
DDCS ch. 0
communication fault
I2_TR
DDCS Comm. Ch
0.
12
Fault
IND2_1
1
No DDCS ch. 0
communication faultr
I2_TR
DDCS Comm. Ch
0.
12
Normal
IND2_1
2
Field exciter 1 fault
I1_TR
Fld ex 1
13
Fault
IND2_1
2
Field exciter 1 ok
I1_TR
Fld ex 1
13
Normal
IND2_1
3
Field exciter 2 fault
I1_TR
Fld ex 2
14
Fault
IND2_1
3
Field exciter 2 ok
I1_TR
Fld ex 2
14
Normal
IND2_1
4
Motor stalled
I2_TR
Motor stalled
15
Fault
IND2_1
4
No motor stall
I2_TR
Motor stalled
15
Normal
IND2_1
5
Motor over speed
I2_TR
Motor overspeed
16
Fault
IND2_1
5
No motor over speed
I2_TR
Motor overspeed
16
Normal
3BSE030340R4101
229
Table 23. Event Text for Alarm MMCX Data Base Element DCS type of Drive, EVENT Treat element
344 - 345
Property text
Signal
Events
Event
Treat
pointer
Event Text
Standard text
Line No
in Event
Treat
Standar
d text
Line
No in
Event
Treat
IND1_0
0
Prevent unexpected start
I1_TR
Prevent Start
Alarm
IND1_0
0
No preventation of
unexpected start
I1_TR
Prevent Start
Normal
IND1_0
1
Emergency stop
I1_TR
Emergency Stop
Alarm
IND1_0
1
Emergency stop
I1_TR
Emergency Stop
Normal
IND1_0
2
Motor 1 over temperature

alarm
I1_TR
Motor 1 Temp
Alarm
IND1_0
2
No over temperature
alarm motor 1
I1_TR
Motor 1 Temp
Normal
IND1_0
3
Motor 1 over load alarm
I1_TR
Motor 1 Overload
Alarm
IND1_0
3
No over load alarmmotor

1
I1_TR
Motor 1 Overload
Normal
IND1_0
4
Converter over
temperature alarm
I1_TR
Conv. Overtemp
Alarm
IND1_0
4
No converter over
temperature alarm
I1_TR
Conv. Overtemp
Normal
IND1_0
5
Register Blocked alarm
I1_TR
Register Blocked
Alarm
230
3BSE030340R4101
IND1_0
5
No Register Blocked
alarm
I1_TR
Register Blocked
Normal
IND1_0
7
RAM backup alarm
I1_TR
RAM backup
Alarm
IND1_0
7
No RAM backup alarm
I1_TR
RAM backup
Normal
IND1_0
8
Motor 2 over temperature

alarm
I1_TR
Motor 2 Temp
Alarm
IND1_0
8
No over temperature
alarm motor 2
I1_TR
Motor 2 Temp
Normal
IND1_0
9
Motor 2 over load alarm
I1_TR
Motor 2 Overload
10
Alarm
IND1_0
9
No over load alarmmotor

2
I1_TR
Motor 2 Overload
10
Normal
IND1_1
0
Main supply under

voltage
I1_TR
Mains
undervoltage
11
Alarm
IND1_1
0
No main supply under

voltage
I1_TR
Mains
undervoltage
11
Normal
IND1_1
2
Converter Fan alarm
I1_TR
Converter Fan
13
Alarm
IND1_1
2
No Converter Fan alarm
I1_TR
Converter Fan
13
Normal
IND1_1
3
Armature current
deviation alarm
I1_TR
Armature current
dev.
14
Alarm
IND1_1
3
No armature current
deviation alarm
I1_TR
Armature current
dev.
14
Normal
IND1_1
5
External fan
acknowledge alarm
I2_TR
External Fan
16
Alarm
IND1_1
5
No external fan
acknowledge alarm
I2_TR
External Fan
16
Normal
3BSE030340R4101
231
IND2_0
0
Pannel loss alarm
I2_TR
Pannel loss
Alarm
IND2_0
0
No pannel loss alarm
I2_TR
Pannel loss
Normal
IND2_0
1
Type code changed

alarm
I2_TR
Type code
changed
Alarm
IND2_0
1
No type code changed

alarm
I2_TR
Type code
changed
Normal
IND2_0
2
Init values read, S2 alarm
I2_TR
Init values read,

S2
Alarm
IND2_0
2
No init values read, S2

alarm
I2_TR
Init values read,

S2
Normal
IND2_0
3
Parameter set 2 missing

alarm
I2_TR
Param set 2
missing
Alarm
IND2_0
3
Parameter set 2 not

missing
I2_TR
Param set 2
missing
Normal
IND2_0
4
Backup not allowed

alarm
I2_TR
Backup not
allowed
Alarm
IND2_0
4
Backup allowed
I2_TR
Backup not
allowed
Normal
IND2_0
5
Write backup alarm
I2_TR
Write backup
Alarm
IND2_0
5
No write backup alarm
I2_TR
Write backup
Normal
232
3BSE030340R4101
Standard Drive, DRICONS
The Event Treat data base element in the Advant Station 500 Series of Operator
Station has a predefined configuration shown in Table 24.
Table 24. Predefined Event Treat for DRICONE
EVENT
Property
334
335
336
337
338
339
340
341
342
343
344
345
AUDIBLE
AL_PRIO
AL_TOBLK
AL_FRBLK
PERSISTB
TEXT_TOB
TEXT_FRB
TEXTCOM
B
17
17
17
17
17
17
17
17
17
17
17
17

This section describes the principles for events and alarms, the standard event texts
for DRICONS main data base element and DRICONS help data base element. The
section contains also a layout of the Event Treat configuration for DRICONS.
Figure 86 shows diagrammatically the relation between indications and the
parameters which can be used to block event handling for certain indications and
points out a required handling in the operators station.
3BSE030340R4101
233
The possibilities of the operator to block event printouts and alarms are shown under
the heading Event and alarm blocking below.
Advant Station 500 Series
Operator Station
Parameters
Data base element
PC element MMC-IND
Fault in Drive
Limit
Warning from Drive
I1_EVBLK
IND 1
I1_TR
Blocking
of
required
events
Event Treat
Event treat
pointer
Defines
- Event/Alarm
- Acoustic alarm
- Layout of texts
- Std. texts
etc.
Figure 88. Event handling principles

The events are divided into groups. One pointer is allocated to each group which
means that the individual events of the group are, in several respects, handled in the
same way in Advant Station 500 Series Operator Station. For each group different
handling can be selected for status changes 0-->1 and 1-->0 respectively. The texts
which are written out in different lists are individual for each event. The group
division - which events are associated with the pointer - is given in Event
description with standard texts below. This also specifies which event handling is
obtained as default and which alternative standard function.
234
3BSE030340R4101
Table 25. Event text for main MMCX data base element, EVENT Treat element 330 - 331
Property text
Signal
Events
Event Text
Event
Treat
pointer
Standard text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_09
Limit exceeded
I1_TR
Limit
10
Alarm
IND1_09
No Limit
I1_TR
Limit
10
Normal
IND1_10
Warning from
drive
I1_TR
Warning from drive
11
Alarm
IND1_10
No warning
I1_TR
Warning from drive
11
Normal
IND1_11
Fault from drive
I1_TR
Fault in drive
12
Alarm
IND1_11
No fault
I1_TR
Fault in drive
12
Normal
IND1_12
Communication
error
I1_TR
Communication error
13
Alarm
IND1_12
Communication
error
I1_TR
Communication error
13
Normal
IND2_00
In service ready
to switch on
I2_TR
In service
On
IND2_00
Not in service
I2_TR
In service
Off
IND2_01
Drive enabled to
start
I2_TR
Enabled
On
IND2_01
Drive is not
enabled to start
I2_TR
Enabled
Off
IND2_02
Running with
selected
reference
I2_TR
Run
On
IND2_02
Stopped
I2_TR
Run
Off
3BSE030340R4101
235
IND2_04
No OFF 2
I2_TR
Emergency
Off
OFF 2
I2_TR
Emergency
On
No OFF 3
I2_TR
Emergency stop
Off
OFF 3
I2_TR
Emergency stop
On
Switch on is
inhibited
I2_TR
Inhibit switch on
Yes
Switch on is not
inhibited
I2_TR
Inhibit switch on
No
IND2_07
Drive runs at
setpoint
I2_TR
At setpoint
On
IND2_07
Drive is not at
setpoint
I2_TR
At setpoint
Off
IND2_08
C-Interlock
I2_TR
C-Interlock
On
IND2_08
C-Interlock
I2_TR
C-Interlock
Off
IND2_09
Drive runs
remotely
controlled
I2_TR
Remote
10
On
IND2_09
Drive runs locally

controlled
I2_TR
Remote
10
Off
IND2_10
B-Interlock 1
I2_TR
B-Interlock 1
11
On
IND2_10
B-Interlock 1
I2_TR
B-Interlock 1
11
Off
IND2_11
B-Interlock 2
I2_TR
B-Interlock 2
12
On
IND2_11
B-Interlock 2
I2_TR
B-Interlock 2
12
Off
IND2_12
B-Interlock 3
I2_TR
B-Interlock 3
13
On
IND2_12
B-Interlock 3
I2_TR
B-Interlock 3
13
Off
(1)
IND2_04
(1)
IND2_05
(1)
IND2_05
(1)
IND2_06
(1)
IND2_06
(1)
236
3BSE030340R4101
IND2_13
B-Interlock 4
I2_TR
B-Interlock 4
14
On
IND2_13
B-Interlock 4
I2_TR
B-Interlock 4
14
Off
IND2_14
A-Interlock
I2_TR
A-Interlock
15
On
IND2_14
A-Interlock
I2_TR
A-Interlock
15
Off
IND2_15
Override interlock
I2_TR
Override interlock
16
On
IND2_15
Dont override
interlock
I2_TR
Override interlock
16
Off
(1) IND2_04 - IND2_06 are only valid if a Drive with software version 5.0 is used.
Table 26. Event text for help MMCX data base element, EVENT Treat element 332 - 333
Property text
Signal
Events
Event Text
Event
Treat
pointer
Standard text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_0
0
Short circuit
I1_TR
Short circuit
Fault
IND1_0
0
Short circuit
I1_TR
Short circuit
Normal
IND1_0
1
Over current
I1_TR
Over current
Fault
IND1_0
1
Over current
I1_TR
Over current
Normal
IND1_0
2
DC over voltage fault
I1_TR
DC over voltage
Fault
IND1_0
2
No DC over voltage
fault
I1_TR
DC over voltage
Normal
IND1_0
3
Power plate over

temperature fault
I1_TR
Over temp pow

plate
Fault
3BSE030340R4101
237
IND1_0
3
No power plate over

temperature fault
I1_TR
Over temp pow

plate
Normal
IND1_0
4
Earth fault
I1_TR
Earth fault
Fault
IND1_0
4
No earth fault
I1_TR
Earth fault
Normal
IND1_0
5
Motor over
temperature fault
I1_TR
Over temp motor
Fault
IND1_0
5
No motor over
temperature fault
I1_TR
Over temp motor
Normal
IND1_0
6
Motor over load fault
I1_TR
Over load motor
Fault
IND1_0
6
No motor over load

fault
I1_TR
Over load motor
Normal
IND1_0
7
System fault
I1_TR
System fault
Fault
IND1_0
7
No system fault
I1_TR
System fault
Normal
IND1_0
8
Under load fault
I1_TR
Under load
Fault
IND1_0
8
No under load fault
I1_TR
Under load
Normal
IND1_0
9
Over speed fault
I1_TR
Over speed
10
Fault
IND1_0
9
No over speed fault
I1_TR
Over speed
10
Normal
IND1_1
0
Supply Section fault
I1_TR
Supply Section
11
Fault
IND1_1
0
No Supply Section fault
I1_TR
Supply Section
11
Normal
238
3BSE030340R4101
IND1_1
1
Master/Follower fault
I1_TR
Master/Follower
12
Fault
IND1_1
1
No Master/Follower
fault
I1_TR
Master/Follower
12
Normal
IND1_1
2
Short circuit INT1
I1_TR
Short circuit INT1
13
Fault
IND1_1
2
I1_TR
Short circuit INT1
13
Normal
IND1_1
3
Short circuit INT2
I1_TR
Short circuit INT2
14
Fault
IND1_1
3
I1_TR
Short circuit INT2
14
Normal
IND1_1
4
Short circuit INT3
I1_TR
Short circuit INT3
15
Fault
IND1_1
4
I1_TR
Short circuit INT3
15
Normal
IND1_1
5
Short circuit INT4
I1_TR
Short circuit INT4
16
Fault
IND1_1
5
I1_TR
Short circuit INT4
16
Normal
IND2_0
0
Prevent unexpected
start
I2_TR
Prevent start
Alarm
IND2_0
0
No preventation of
unexpected start
I2_TR
Prevent start
Normal
IND2_0
1
Emergency stop
I2_TR
Emergency stop
Alarm
IND2_0
1
Emergency stop
I2_TR
Emergency stop
Normal
IND2_0
2
Measured motor temp

alarm
I2_TR
Meas. motor temp
Alarm
3BSE030340R4101
239
IND2_0
2
Measured motor temp

alarm
I2_TR
Meas. motor temp
Normal
IND2_0
3
Over temperature
model
I2_TR
Motor overload
Alarm
IND2_0
3
No over temperature
model
I2_TR
Motor overload
Normal
IND2_0
4
Power plate over

temperature alarm
I2_TR
Temp power plate
Alarm
IND2_0
4
No power plate over

temperature alarm
I2_TR
Temp power plate
Normal
IND2_0
5
Pulse encoder alarm
I2_TR
Pulse encoder
Alarm
IND2_0
5
No Pulse encoder
alarm
I2_TR
Pulse encoder
Normal
IND2_0
7
Standard digital I/O

alarm
I2_TR
Standard Digital
I/O
Alarm
IND2_0
7
No Standard digital I/O

alarm
I2_TR
Standard Digital
I/O
Normal
IND2_0
8
Standard analogue I/O

alarm
I2_TR
Standard Analog
I/O
Alarm
IND2_0
8
No Standard analogue
I/O alarm
I2_TR
Standard Analog
I/O
Normal
IND2_0
9
External digital I/O

alarm
I2_TR
Ext. Digital I/O
10
Alarm
IND2_0
9
No External digital I/O

alarm
I2_TR
Ext. Digital I/O
10
Normal
IND2_1
0
External analogue I/O

alarm
I2_TR
Ext. Analog I/O
11
Alarm
240
3BSE030340R4101
IND2_1
0
No External analogue
I/O alarm
I2_TR
Ext. Analog I/O
11
Normal
IND2_1
1
Master - Follower
alarm
I2_TR
Master - Follow
alarm
12
Alarm
IND2_1
1
Master - Follower
alarm
I2_TR
Master - Follow
alarm
12
Normal
IND2_1
4
Earth fault alarm
I2_TR
Earth fault
15
Alarm
IND2_1
4
No Earth fault alarm
I2_TR
Earth fault
15
Normal
The Event Treat data base element in the Advant Station 500 Series of Operator
Station has a predefined configuration shown in Table 24.
Table 27. Predefined Event Treat for DRICONS
EVENT
Property
330
331
332
333
AUDIBLE
AL_PRIO
AL_TOBLK
AL_FRBLK
PERSISTB
TEXT_TOB
TEXT_FRB
TEXTCOMB
17
17
17
17
3BSE030340R4101
241
242
3BSE030340R4101
Appendix C Messages
Fatal, Error, Warning and Info Messages
Messages are grouped into Fatal, Error, Warning and Info messages.
Fatal - Fatals will stop conversion immediately and produce no output files.
Error - Errors will continue conversion but produce no output files.
Warning - Warnings will continue conversion and produce output files.

Warnings can be suppressed by unmark the check box in the Config dialog
(Figure 66)
Info - Infos are informations about the ongoing conversion.

Information messages are not described here. Infos are mainly for the
situations where the user want to have an exact overview of the conversion.
Enabling Infos will produce lots of text in the log. Infos can be suppressed by
unmark the check box in the Config dialog (Figure 66).
Fatal, Error and Warning messages are all in the form:

<nnnn>-<s>-<text>
3BSE030340R4101
nnnn, The Fatal/Error/Warning number.
Warnings, 1001 - 1999
Errors, 2001 - 2999
Fatals, 3001 - 3999
s, The Severity code
F, Fatal
E, Error
W, Warning
243
Fatal Messages
Appendix C Messages
text, Plain text describing the message
Information messages have the format:

I-<text>
text, Plain text describing the message
Fatal Messages
Table 28 shows the Fatal numbers and texts
Table 28. Fatal Messages
Number
Text
Reason
3001
Fatal-3001-System error
System error, Try rebooting the PC
3002
Fatal-3002-Cannot open this file:

<path\filename>
A crucial file was not found, check that the

path are correct
244
3BSE030340R4101
Appendix C Messages
Error Messages
Error Messages
Table 29 shows the Error numbers and texts
Table 29. Error Messages
Number
Text
2001
Syntax error in input file <path\filename> The syntax in the specified file is incorrect,
correct
2002
Error-2002-OSCOLOR not found
2003
Error-2003-RED not found
2004
Error-2004-GREEN not found
2005
Error-2005-BLUE not found
2006
Error-2006-TYPE not found
2007
Error-2007-Error accessing file:

<path\filename>
2008
Error-2008-Negative value not allowed
3BSE030340R4101
Reason
The specified token was not found in the

configuration file, correct
The specified file can not be accessed,

check access rights
245
Error Messages
Appendix C Messages
Table 29. Error Messages (Continued)

Number
Text
Reason
2009
Error-2009-FONT not found
2010
Error-2010-FONTNAME not found
The specified token was not found in the

2011
Error-2011-FONTNUMBER not found
2012
Error-2012-RELSIZE not found
2013
Error-2013-SIZE not found
2014
Error-2014-CHARSET not found
2015
Error-2015-ELEMENTNAME not found
2016
Error-2016-CONTROLNAME not found
2017
Error-2017-LIBNAME not found
2018
Error-2018-PROGID not found
2019
Error-2019-WIDTH not found
2020
Error-2020-HEIGHT not found
2021
Error-2021-FIXPOINT not found
2022
Error-2022-PROPERTIES not found
2023
Error-2023-FROM not found
2024
Error-2024-TO not found
2025
Error-2025-ADAPTOR not found
2026
Error-2026-OUTPUTTO not found
2027
Error-2027-NAME not found
2028
Error-2028-PROGID not found
2029
Error-2029-REFERENCE not found
2030
Error-2030-STATIC not found
2031
Error-2031-LIBNAME not found
246
3BSE030340R4101
Appendix C Messages
Error Messages
Table 29. Error Messages (Continued)

Number
Text
Reason
2032
Error-2032-No Registry (CLSID) found

for <progid>
The CLSID token was not found in the

2033
Error-2033-Cannot instantiate object for Instantiation of the specified object failed,

<progid>
check that the object is correct installed
2034
Error-2034-Failed to do
PersistStreamInit for <progid>
The specified object does not implement

the specified interface correct.
2035
Error-2035-Failed to do
PersistStreamInit->InitNew
The specified method of the interface failed
2036
Error-2036-Expected <number>
parameters, got <number>
Wrong number of parameters, mismatch in

the input (*.g) file
2037
Error-2037-Expected at least <number>

parameters, got <number>
2038
Instance <object> not found in input file

<path\filename>
3BSE030340R4101
No entry for the specified object is found in

the configuration file(s).
247
Warning Messages
Appendix C Messages
Warning Messages
Table 30 shows the Warning numbers and texts
Table 30. Warning Messages
Number
Text
1001
Warning-1001-No center found for the three

points: <point>,<point>, <point>,<point>
1002
Warning-1002-No Configuration file for

<object>
1003

<object>
1004

<object>
1005
Warning-1005-Cannot create OLE font for

<object>
Internal error when creating the

specified font
1006
Warning-1006-Cannot set property

<property> for <object>
An objects property could not be set.

Check the configuration file for that
object
1007
Warning-1007-Invalid Command/Attribute,
[Number,Type] = [<number>,<type>]
Internal error when accessing the object
1008
Warning-1008-Unknown Command =
<command>
The command is unknown
1009
Warning-1009-<attrib>=<value> already
An entry in the configuration files are
defined with <attrib>=<value>, ignoring new double defined. Second definition will be
ignored
definition: <value>
1010
defined with <attrib>=<value>, ignoring new
definition: <value>
1011
defined with <attrib>=<value>, ignoring new
definition: <value>
248
Reason
No configuration file found for the object,

Create and include
3BSE030340R4101
Appendix C Messages
Warning Messages
Table 30. Warning Messages (Continued)

Number
Text
1012
Warning-1012-Include File <path/filename> A circular reference in the include files.

already read
Check and correct the #include
statements
1013
Warning-1013-Failed to create stream
1014
Warning-1014-Failed to save stream
1015
Warning-1015-Failed to set seek pointer
1016
Warning-1016-Failed to get global handle
1017
Warning-1017-Failed to set persist data
1018
Warning-1018-No vbcolor defined for

oscolor=<color>
3BSE030340R4101
Reason
A stream could not be created/read
Failed to manipulate the binary output

file
The specified color is not specified in the

configuration files. Correct.
249
Warning Messages
250
Appendix C Messages
3BSE030340R4101
Appendix D System Alarm List

System Alarms provide valuable information for fault tracing of the control system,
which includes 800xA for Advant Master, Advant and Operator Workplace.
You should use them as they will give you an overview list of all the system alarms
in your system. An example of a typical System Alarm List is presented in
Figure 89.
Figure 89. System Alarm List

The different columns in the System Alarm list are:
Event Time
Condition
Object Name
Message Description
3BSE030340R4101
251
When you have located the Controller where the problem resides, bring up the
System Alarm List on that Controller object (Control Structure). This gives you a
dedicated system alarm list for that Controller helping you to close in on the
problem. The System Alarms are in plain text and should help you to continue with
your fault tracing.
Advant Master System Alarms

The most important system alarms in 800xA for Advant Master are described in the
table below.
The Message Description column lists short descriptions of system events.

Text within % signs is replaced with the current data at run-time.
The Extended Description column explains system events further.

Message Description
252
Extended Description
Failed to create RTA Management

Handler
The 800xA for Advant Master data

service failed to connect to the RTA
board Server.
This indicates that no data from the
controller(s) will be available through
this Connectivity Server Node.
Failed to initialize
Could not start the 800xA for Advant

Master data service due to severe
problems in the system. This indicates
that no data from the controller(s) will be
available through this Connectivity
Server Node.
No nodes available on MB300 network
No contact with the controller(s) on the

MB300 network. This indicates that no
data from the controller(s) will be
Server Node.
3BSE030340R4101
Message Description
Extended Description
No nodes available om MB300 network
No contact with the controller(s) on the

MB300 network. This indicates that no
data from the controller(s) will be
Server Node.
Failed to send data to client
The 800xA for AC 400 TTD Server has

lost contact with a History Server.
This indicates that no history data from
the controller(s) will be logged from this
Connectivity Server Node.
RTA Board failed (stall)
The RTA Management Server has lost

contact with the RTA board.
RTA Board startup failed

RTA Board startup failed (Network

address not set)
This indicates that the Node and

network address has not been
configured on the RTA Board. No data
from the controller(s) will be available
through this Connectivity Server Node
unless the address is set on the RTA
Board.
For more information about Operator Workplace System Alarms see IndustrialIT
800xA, System, Operator Workplace Configuration.
3BSE030340R4101
253
254
3BSE030340R4101
Appendix E Control Aspects

RTA Board Control Aspect
The RTA - Real-Time Accelerator Board - is an intelligent communication board for
connection to the MasterBus 300 network on which the AC 400 Controllers
communicate. The RTA Board Control aspect makes it possible to perform some
maintenance and fault tracing work on the board.
3BSE030340R4101
255
The RTA Board aspect is located on the RTA Board object under the network object
in the Control Structure. See Figure 90 for a fast location of the RTA Board control
object and its aspects.
Figure 90. Locating the RTA Board Control Aspect

Select the RTA Board Control aspect using any of the possible techniques for aspect
selection.
The aspect has three tabs:
256
RTA Board Control, see RTA Board Control Tab on page 257.
Network / Node Configuration, see RTA Board - Network and Node

Configuration Tab on page 259.
RTA Board Configuration - see RTA Board Configuration Tab on page 260 for
details on how to use it for configuration.
3BSE030340R4101
RTA Board Control Tab

This tab is useful for the following purposes:
You can request the current status of the board
You can Start and Stop the RTA Board (for example after changing the network
address or if it has halted).
Figure 91. RTA Board Control

The aspect view contains a Progress log, the Current Status and the following
buttons:
Start
Loads the RTA Board load image and the previously saved configuration and starts
the RTA Board in Operational mode.
Stop
Stops the RTA Board. A warning message, see Figure 92, will pop-up and must be
acknowledged before the stop command is executed.
3BSE030340R4101
257
Figure 92. Confirming the Stop of the RTA Board

If you stop the RTA Board, the Operator Workplace server does no longer collect
any data from the AC 400 Controllers, and can not be used to monitor or control
the process during the time the RTA Board is stopped.
Get Status
Requests the current status from the RTA Board, and presents the result in the
window. (Status is also updated cyclically).
Table 31. RTA Board Status
Status text:
RTA Board....
258
Comment
Running
Normal state. Everything OK
Stopped
Manually stopped. No run-time data is available.
Start-up in progress
The start-up is progressing, please wait
Stop in progress
The stopping is progressing, please wait
Start failed, network

address not set
Network and Node must be set before the RTA can

be started
3BSE030340R4101
RTA Board - Network and Node Configuration Tab
Table 31. RTA Board Status (Continued)

Status text:
RTA Board....
Start failed
Comment
There are a number of potential possible causes:
One of the files required for boot does not exist or
The path to the file is incorrect.
If start fails, the cause will be displayed in the
Progress log list in RTA Board Control. If you have
tried to find the cause repeatedly, a reinstallation is
advised. If reinstallation fails, the RTA Board could
be out of order.
Stop failed
Bootstrapper file not found, see Start failed
RTA Board - Network and Node Configuration Tab

You use this tab to change the network and node addresses on the MB 300/AC 400
network.
Figure 93. RTA Set Network and Node
3BSE030340R4101
259
RTA Board Configuration Tab
The window contains the following:

Network Number 1
Network address (network number) for the normal MB 300 network.

Network number range: 11-19, 21-29, 31-39,...81-89, 91-99, 126-127.
Network Number 2
Network address (network number) for the redundant MB 300 network.

Redundant network number range: 0, 11-19, 21-29, 31-39,...81-89, 91-99, 126-127.
Redundant network number 0 indicates no redundant network.
Node Number
Node address (node number) for this node. Node number range: 1-99.
You must be very careful when setting up network and node numbers. If you get
two nodes with identical addresses, the entire network communication could be
disturbed with unpredictable consequences. Changing network and node
numbers should normally only be necessary when the control network is
rearranged.
Use the buttons in the figure as follows:
Click Cancel to interrupt the input.
Click Apply to set the new network address (network/node number). You must
restart the RTA Board to get the new network/node address to take effect (see
RTA Board Control Tab on page 257).
Click Help to get information about this window.
RTA Board Configuration Tab

Use the RTA Board Configuration tab to start the On-line Builder program and
setup the configuration for the RTA Board.The window contains the following:
260
3BSE030340R4101
Control Connection Aspect (CCA)
RTA Board Config
Starts the On-line Builder tool that is used for configuration of the database on the
RTA Board.
Control Connection Aspect (CCA)

There is a CCA for all Process and system objects. The CCA:s can be useful to trace
problems specific for a certain object or for the presentation of an object. The CCA
has four views, here is a short description of the views and how you can use them in
your trouble shooting.
The CCA Property view

The CCA Property view, see Figure 94, gives you a list of all the attributes, their
data format and how they can be accessed. If you mark the Subscribe for live data
check box, you will also get the current value of all attributes updated cyclically.
Figure 94. The CCA Property View

Use this view to verify the attribute values of an object, how they are configured and
the current attribute values to compare with other presentations of it. If you suspect
3BSE030340R4101
261
CCA Property Info
an error in a node, an I/O board or a transducer, you can use the CCA:s to narrow in
on the problem by verifying which objects that are available over the network and
which are not - and what their status attributes tell you.
The CCA Property view gives you a complete list of attributes, their names, data
type, access.
A - before the update rate value enables on event updating, of the values in
between the cyclic updates according to AC 400 Event handling. If you locally
change the update rate in a graphic display, - must be included if you want the
on event updating to be activated.
CCA Property Info

The Property Info view presents all details about the selected property. An example
of a Property Info view is found in Figure 95.
The Property Info view includes the possibility to set the definitions for the
Property values. To define property value handling and to set these values could
severely affect the control of the industrial process, including loosing control of
the process. This functionality is only included for testing and fault tracing, and
should not be used during normal operation.
Do not change any Property values unless you are fully aware of all the
consequences.
262
3BSE030340R4101
CCA Property Info
Figure 95. CCA - Property Information

The following Property values are presented and could be changed:
Type - Type of value (boolean, integer, float, etc.).
Name - The name of the property.
Update Rate - The update rate for this property (in ms).
Description - Describes the relation between the property and the object.
R/W - Flag that indicates if the property is Readable and/or Writable.
Operations - Defines the Read and Write operations for the property.
Flags - Indicates how the property is updated: Real time (hard real-time),
Runtime (soft real-time), Additional info (no real-time update), or Other.
The Property values are changed when you click on the Set button.
3BSE030340R4101
263
CCA - Additional info
CCA - Additional info

The Additional Info tab presents details on property specific information.
The example in Figure 95 presents information about an analog value.
The Additional Info view includes the possibility to set definitions for the values.
To define value handling and to set these values could severely affect the control
of the industrial process, including loosing control of the process.
This functionality is only included for testing fault tracing, and should not be
used during normal operation.
Do not change any Additional Info values unless you are fully aware of all the
consequences.
The following Additional info values are presented and could be changed:
Normal Maximum - Maximum range value (for an analog value).
Normal Minimum - Minimum range value (for an analog value).
Engineering Unit - Engineering unit for this property.
No of Decimals - This value should be presented with this number of decimals.
Presentation Mode - Defines if this value should be presented between the

discrete points in trend curves: Stepped (value is constant between points) or
Interpolated (value is linear between points).
The Additional Info values are changed when you click on the Set button.
The Presentation Mode makes it possible for you to select the default presentation
mode in Trace presentations: Stepped or Interpolated, see IndustrialIT 800xA,
System, Operator Workplace Configuration for more information.
CCA MasterBus 300

The MB 300 tab presents detailed address information about the MB 300 object.
The following information is available for each object:
264
The MasterBus 300 address: Network number, Node number, Logical file
number, Logical record number, Reference type.
The ID number of each attribute.
3BSE030340R4101
CCA MasterBus 300
You can enter Network and Node number in this view. These are the only values
that you should modify. This information is mainly intended for fault tracing and the
suppliers maintenance work.
You shall never modify or change the LF, LR, or RefType values. This will
cause several functions to stop working.
3BSE030340R4101
265
CCA MasterBus 300
266
3BSE030340R4101
Appendix F OPC Properties

OPC object type properties
The following table lists process objects and the properties that supports cyclic
subscriptions.The cyclic subscription times are 1, 3 and 9 seconds.
See OPC Read Operations for more information.
Table 32. Properties supporting cyclical subscriptions via OPC

Object Type
Properties
AI
VALUE, SIGNAL_STATUS, IMPLEMENTED, ERROR,

UPDATED, UPD_BLK, MAN_ENTRY, SELECTED,
NORMAL_OBJ_TREAT, H2_R_FCL, ABOVE_HI_LIM2,
ABOVE_HI_LIM1, BELOW_LO_LIM1, BELOW_LO_LIM2,
ALARM_UNACK, H1_R_FCL, DISTURBANCE, OVERFLOW,
ALARM_BLK, ALARM_PERIOD_BLK, PRINT_BLK, L1_R_FCL,
LINKED, RELINK, NOERR_AT_OVF, TESTED, ACC_ERR,
OLD_LOCK, L2_R_FCL, ER_R_FCL, RP_F_BLK, AI_ACTION,
AI_RETRY, ERR_CTRL, NO_OF_DEC
AO
VALUE, SIGNAL_STATUS, IMPLEMENTED, ERROR,

AO_SPARE_2, OUTP_BLK, AO_SPARE_4, SELECTED,
NORMAL_OBJ_TREAT, MAN_MODE, ON_MAX_LIM,
AO_SPARE_9, AO_SPARE_10, ON_MIN_LIM,
ALARM_UNACK, AO_SPARE_13, AO_SPARE_14,
AO_SPARE_15, ALARM_BLK, ALARM_PERIOD_BLK,
PRINT_BLK, OUTP_RESTART, OLD_LOCK, USE_MAX_LIM,
USE_MIN_LIM, TESTED, AO_SPARE_24, USER_DEF_1,
LINKED, USER_DEF_2, USER_DEF_3, USER_DEF_4,
USER_DEF_5, OSP_CTRL, NO_OF_DEC
3BSE030340R4101
267
Table 32. Properties supporting cyclical subscriptions via OPC (Continued)

Object Type
Properties
DI
SIGNAL_STATUS, IMPLEMENTED, ERROR, UPDATED,

UPD_BLK, MAN_ENTRY, SELECTED, NORMAL_OBJ_TREAT,
ERR_CTRL, VALUE, SEC_VALUE, NORM_POSN,
SEC_NORM_POSN, ALARM_UNACK, REPEAT_FAIL_BLK,
DISTURBANCE, CALC_VALUE, ALARM_BLK,
ALARM_PERIOD_BLK, PRINT_BLK, REPEAT_FAIL_CTRL,
OLD_LOCK, INVERTED, DUAL_IND, TESTED, DI_SPARE_24,
V9_CONTROL, LINKED, DI_RETRY, DIC_IND_RED,
DI_ACTION, DIC_IND_YELLOW, DIC_IND_GREEN
DO
SIGNAL_STATUS, IMPLEMENTED, ERROR, DO_SPARE_2,

OUTP_BLK, DO_SPARE_4, SELECTED,
NORMAL_OBJ_TREAT, MAN_MODE, VALUE, DO_SPARE_9,
START_VALUE, DO_SPARE_11, ALARM_UNACK,
DO_SPARE_13, DO_SPARE_14, USER_DEF_1, ALARM_BLK,
ALARM_PERIOD_BLK, PRINT_BLK, OUTP_RESTART,
OLD_LOCK, INVERTED, OSP_VAL, TESTED, ORDER_TO,
ORDER_FROM, LINKED, USER_DEF_2, USER_DEF_3,
USER_DEF_4, USER_DEF_5, OSP_CTRL
DAT
VALID, VAL_TYPE, B0_VAL, B1_VAL, B2_VAL, B3_VAL,

B4_VAL, B5_VAL, B6_VAL, B7_VAL, B8_VAL, B9_VAL,
B28_VAL, B29_VAL, B30_VAL, B31_VAL, I_VAL, IL_VAL,
R_VAL, VALUE
268
3BSE030340R4101

Object Type
DRICONE, DRICONS,
GROUP, MOTCON,
MOTCONI, VALVECON
3BSE030340R4101
Properties
IMPLEMENTED, ALARM_BLK, ALARM_PERIOD_BLK,
PRINT_BLK, IND1_DIST, IND2_DIST, SELECTED, AU_IND,
ALARM_UNACK, AU_IND1_00, AU_IND1_01, AU_IND1_02,
AU_IND1_03, AU_IND1_04, AU_IND1_05, AU_IND1_06,
AU_IND2_15, IND1, IND1_00, IND1_01, IND1_02, IND1_03,
IND1_04, IND1_05, IND1_06, IND1_07, IND1_08, IND1_09,
IND2, IND2_00, IND2_01, IND2_02, IND2_03, IND2_04,
IND2_11, IND2_12, IND2_13, IND2_14, IND2_15, REAL_RES,
INTL_RES, ACT_PRES_TEXT, BOOL_A, BOOL_B, BOOL_C,
BOOL_D, BOOL_E, BOOL_F, BOOL_G, BOOL_H, INTW_A,
INTW_B, REAL_A, REAL_B, REAL_C, REAL_D, REAL_E,
INTWA_00, INTWA_01, INTWA_02, INTWA_03, INTWA_04,
INTWA_15, INTWB_00, INTWB_01, INTWB_02, INTWB_03,
INTWB_04, INTWB_05, INTWB_06, INTWB_07, INTWB_08,
INTWB_09, INTWB_10, INTWB_11, INTWB_12, INTWB_13,
INTWB_14, INTWB_15
269

Object Type
Properties
GENBIN, GENCON,
GENUSD
IMPLEMENTED, ALARM_BLK, ALARM_PERIOD_BLK,

PRINT_BLK, REPEAT_FAIL_BLK, EVENT_BLK, SELECTED,
MORD_EV_BLK, ALARM_UNACK, AU_ST_00, AU_ST_01,
AU_ST_02, AU_ST_03, AU_ST_04, AU_ST_05, AU_ST_06,
AU_ST_07, PC_STATUS, PC_ST_00, PC_ST_01, PC_ST_02,
PC_ST_03, PC_ST_04, PC_ST_05, PC_ST_06, PC_ST_07,
PC_ST_28, PC_ST_29, PC_ST_30, PC_ST_31, MV, MV_INTL,
SP, OP, H2, L2, STATUS_1, STATUS_2
MANSTN
STATUS, IMPLEMENTED, F1_ACTION, RUNNING,

ACTUATOR, MVDIR, SELECTED, F2_ACTION, TESTED,
PANEL_CTRL, SPARE_STATUS_09, SPARE_STATUS_10,
REMOTE, CENTRAL, LOCAL, SERVICE_UNIT, MMI_MAN,
MMI_E1, OUT_EQ_LL (OUT=LL), OUT_EQ_HL (OUT=HL),
MAN, E1, MV, OUTREF, OUT, TS, POUT, TS_MV_BELOW_L1
(TS_MV<L1), TS_MV_ABOVE_H1 (TS_MV>H1),
TS_MV_BELOW_L2 (TS_MV<L2), TS_MV_ABOVE_H2
(TS_MV>H2), TS_AI_ERROR, TS_AO_ERROR,
MNO_OF_DEC, PONO_OF_DEC, PRES1, ALARM_UNACK,
DIST, AU_MV_BELOW_L1 (AU_MV<L1), AU_MV_ABOVE_H1
(AU_MV>H1), ALARM_F1_BLK, ALARM_F1_PERIOD_BLK,
PRINT_F1_BLK, AU_MV_BELOW_L2 (AU_MV<L2),
AU_MV_ABOVE_H2 (AU_MV>H2), ALARM_F2_BLK,
ALARM_F2_PERIOD_BLK, PRINT_F2_BLK, STATUS_1,
STATUS_2, STATUS_3, STATUS_4,
270
3BSE030340R4101

Object Type
PIDCON
3BSE030340R4101
Properties
IMPLEMENTED, F1_ACTION, RUNNING, ACTUATOR, MVDIR,
SELECTED, F2_ACTION, TESTED, PANEL_CTRL,
ON_OFF_CTRL, F4_ACTION, REMOTE, CENTRAL, LOCAL,
SERVICE_UNIT, MMI_MANF, MMI_MAN, MMI_AUTO,
MMI_INT_BLK, MMI_DER_BLK, MMI_E1, MMI_E2, MMI_E3,
OUT_EQ_LL (OUT=LL), OUT_EQ_HL (OUT=HL), SP_EQ_LL
(SP=LL), SP_EQ_HL (SP=HL), BAL, MAN, AUTO, E1, E2, E3,
LOCAL_OUT, CLAMP_OUT, EXT_OUT_LIMIT,
EXT_GAIN_ENBL, EXT_TI_ENBL, EXT_TD_ENBL,
EXT_TF_ENBL, EXT_INT_BLK, EXT_DER_BLK,
SPARE_PARAM5_15, MV, AUTOSP, WSP, DEVIATION, OUT,
TS, MAN_OUT, SPARE_PARAM6_01, POUT,
(TS_MV>H1), TS_DEV_BELOW_L (TS_DEV<L),
TS_DEV_ABOVE_H (TS_DEV>H), TS_MV_BELOW_L2
TS_LOCAL_FL, TS_MAN_FL, TS_AUTO_FL, TS_E1_FL,
TS_E2_FL, TS_E3_FL, TS_AI_ERROR, TS_AO_ERROR,
TS_DCM_ERROR, TS_PC_BLK, TS_SERVUC, TS_HW_ERR,
MNO_OF_DEC, EXT_OUT_LL, EXT_OUT_HL, EXT_GAIN,
EXT_TI, EXT_TD, EXT_TF, PRES1, PRES2, ALARM_UNACK,
REPEAT_FAIL_BLK, DIST, AU_MV_BELOW_L1 (AU_MV<L1),
AU_MV_ABOVE_H1 (AU_MV>H1), AU_DEV_BELOW_L
(AU_DEV<L), AU_DEV_ABOVE_H (AU_DEV>H),
ALARM_F1_BLK, ALARM_F1_PERIOD_BLK, PRINT_F1_BLK,
REPEAT_F1_FAIL_CTRL, AU_MV_BELOW_L2 (AU_MV<L2),
ALARM_F2_PERIOD_BLK, PRINT_F2_BLK,
REPEAT_F2_FAIL_CTRL, STATUS_1, STATUS_2, STATUS_3,
STATUS_4
271

Object Type
PIDCONA
272
Properties
IMPLEMENTED, ACTUATOR, MVDIR, SELECTED, MANPREF,
SHOW_ACT, SHOW_SCHED, AUTOSP_TRACKING,
STATUS_SPARE01, MMI_MANF, MMI_MAN, MMI_AUTO,
PARAM11_SPARE01, PARAM11_SPARE02, MMI_E1, MMI_E2,
MMI_E3, OUT_EQ_LL, OUT_EQ_HL, SP_EQ_LL, SP_EQ_HL,
PARAM13, BAL, MAN, AUTO, E1, E2, E3, LOCAL_OUT,
CLAMP_OUT, EXT_OUT_LIMIT, BADSN,
OUTSIDE_START_ZONE, AT_TIMEOUT_FLAG,
VERIFY_UNCERTAIN, AT_INDICATOR, AD_INDICATOR,
ATENABLE, GSENABLE, MV_NONFILTERED, AUTOSP, WSP,
DEVIATION, OUT, MV_AAFILTERED, EXTREF1, EXTREF2,
EXTREF3, EXT_OUT_LL, EXT_OUT_HL, ACTPOS,
TS_MV_BELOW_L1, TS_MV_ABOVE_H1,
TS_DEV_BELOW_L, TS_DEV_ABOVE_H,
TS_MV_BELOW_L2, TS_MV_ABOVE_H2, TS_LOCAL_FL,
TS_MAN_FL, TS_AUTO_FL, TS_E1_FL, TS_E2_FL,
TS_E3_FL, TS_AI_ERROR, TS_AT_PC_ABORTED,
TS_AT_FAILED, TS_AT_ALERT, TS_INV_TSAMP,
TS_ADAP_FAIL, TS_AT_SPARE01, TS_AT_SPARE02,
TS_AT_SPARE03, AT_PHASE, AT_COUNTER,
AT_START_ZONE, CURRENT_ZONE, SAVED_PAR_MAN_AD,
CONTR_PAR_MAN_AD, Z1_MAN_AD_OBT_PAR,
Z2_MAN_AD_OBT_PAR, Z3_MAN_AD_OBT_PAR,
Z4_MAN_AD_OBT_PAR, Z5_MAN_AD_OBT_PAR,
SAVED_GAIN, SAVED_TI, SAVED_TD, SAVED_BETA,
SAVED_TS, SAVED_DOM_FREQ, SCHEDIN, ZLIM12, ZLIM23,
ZLIM34, ZLIM45, TRIM_REP, PARAM16_SPARE01,
START_TUNE, CONT_TUNE, SAVE_REQUEST,
RESTORE_REQUEST, ADAPENBL, FREQ_UNLIMITED,
VERIFY_REQUEST, RETRIEVE, RETRIEVEALLOWED,
PARAM17_SPARE01, PARAM17_SPARE02,
PARAM17_SPARE03, MNO_OF_DEC, ONO_OF_DEC,
ALARM_UNACK, DIST, AU_MV_BELOW_L1 ,
AU_MV_ABOVE_H1, AU_DEV_BELOW_L,
AU_DEV_ABOVE_H, ALARM_F1_BLK,
3BSE030340R4101

Object Type
Properties
PIDCONA (cont.)
REPEAT_F1_FAIL_CTRL,AU_MV_BELOW_L2,
AU_MV_ABOVE_H2, ALARM_F2_BLK,
REPEAT_F2_FAIL_CTRL, ALARM_F4_BLK,
REPEAT_F4_FAIL_CTRL, AU_AT_PC_ABORTED,
AU_AT_FAILED, AU_AT_ALERT, AU_INV_TSAMP,
AU_ADAP_FAIL, AU_AT_SPARE01, AU_AT_SPARE02,
AU_AT_STATUS_1, STATUS_2, STATUS_3, STATUS_4,
STATUS_5, SPARE03
RATIOSTN
STATUS, IMPLEMENTED, F1_ACTION, RUNNING,

SPARE_STATUS_03, SPARE_STATUS_04, SELECTED,
F2_ACTION, TESTED, PANEL_CTRL, SPARE_STATUS_09,
SPARE_STATUS_10, MMI_RATIOREF, MMI_MAN_OUT,
MMI_BIAS, MMI_OUT_LL, MMI_OUT_HL,
SPARE_PARAM2_01, MMI_MAN, MMI_AUTO, MMI_E1,
OUT_EQ_LL (OUT=LL), OUT_EQ_HL (OUT=HL),
RATIO_EQ_LL (RATIO=LL), RATIO_EQ_HL (RATIO=HL),
TRACK_EQ_1 (TRACK=1), MAN, AUTO, E1, EXT_BIAS_ENBL,
EXT_OUT_LIMIT, SPARE_PARAM5_06, MV, RATIOREF,
WRATIO, OUT, MAN_OUT, TS, POUT, TS_MV_BELOW_L1
(TS_MV>H2), TS_AI_ERROR, SPARE_TS_05,
TS_DCM_ERROR, TS_PC_BLK, TS_SERVUC, TS_HW_ERR,
MNO_OF_DEC, RNO_OF_DEC, PONO_OF_DEC,
EXT_OUT_LL, EXT_OUT_HL, ALARM_UNACK,
REPEAT_FAIL_BLK, DIST, AU_MV_BELOW_L1 (AU_MV<L1),
AU_MV_BELOW_L2 (AU_MV<L2), AU_MV_ABOVE_H2
(AU_MV>H2), ALARM_F2_BLK, ALARM_F2_PERIOD_BLK,
PRINT_F2_BLK, STATUS_1, STATUS_2, STATUS_3, STATUS_4
3BSE030340R4101
273

Object Type
Properties
SEQ
STATUS, IMPLEMENTED, SEQ_RFS, SEQ_COMPLETE,

BLOCKED, SPARE_04, SELECTED, SPARE_06, TESTED,
REMOTE, CENTRAL, LOCAL, SERVICE_UNIT, POSN, SEQTD,
SEQTE, STEPTD, STEPTE, JPOSN_OUTP, ACT_TURN,
INTERV_TIME_EL, AUTOM, MANM, HOLDM, UNCONDM,
RUN, END, NEXT, IND_SPARE_07, PT_ALARM_BLK,
PT_SPARE_01, PT_PRINT_BLK, SI_ALARM_BLK,
SI_SPARE_01, SI_PRINT_BLK, DI1_ALARM_BLK,
DI1_ALARM_PERIOD_BLK, DI1_PRINT_BLK,
DI1_REPEAT_FAIL_CTRL, DI1_SECOND_FAIL_BLK,
DI1_SPARE_05, DI1_SPARE_06, DI1_SPARE_07,
DI2_SPARE_00, DI2_SPARE_01, DI2_SPARE_02,
DI2_SPARE_03, DI2_ALARM_UNACK,
DI2_REPEAT_FAIL_BLK, DI2_DIST, DI2_SPARE_07,
TS_SPARE_00, TS_POSN_F, TS_SERVUC, TS_SEQAL,
TS_STEPAL, ALARM_UNACK, AU_SPARE_00, AU_POSN_F,
AU_SERVUC, AU_SEQAL, AU_STEPAL, TF_ALARM_BLK,
TF_ALARM_PERIOD_BLK, TF_PRINT_BLK,
TF_REPEAT_FAIL_CTRL, TF_ALARM_PERIOD_BL2,
TF_SPARE_05, TF_SPARE_06, TF_SPARE_07, STEPSTAT,
CONDSTA1, CONDSTA2, CONDSTA3, CONDSTA4,
CONDSTA5, CONDSTA6, CONDSTA7, CONDSTA8, ACTSTA1,
ACTSTA2, ACTSTA3, ACTSTA4, ALLACT, BLANKINF,
LOAD_DB, NEXTCOND, JCSTA1, JCSTA2, JCSTA3, JCSTA4,
INFVAL, NEXTSTEP, STATUS_1, STATUS_2, STATUS_3,
TEXT
INT_LONG, REAL, DISPMAX, DISPMIN, NO_OF_DEC,

STATUS, VALID, SELECTED, MAN, BOOLEAN, COLOUR1,
COLOUR2, BLANKT, BLANKB, BLANKR, BLANKIL, B1_VAL,
B2_VAL, B3_VAL, B4_VAL, SPARE_B1, SPARE_B2, TEXT
274
3BSE030340R4101
INDEX
Numerics
800xA for Advant Master Product 23
Functionality 24
Hardware and Software requirements 24
Product features 23
800xA for Advant MasterProduct
Product overview 23
A
Alarm and Event List 34
B
Backup and Restore 152
Building Control structure
Create FCB source file 53
Demo structure 57
Off-line from FCB source file 53
Test structure 57
C
Clock Master
800xA for Advant Master 31
AC 400 Series Controller 29
Configuration 25, 105, 119
Before you start 25
Examples 103
Existing plant 28
Getting started 27
New system 28
Quick List 98
Control Connection Aspect 261
Additional information 264
MasterBus 300 264
3BSE030340R4101
Property information 262

Property view 261
D
Display conversion
Colors.cnf file 124
Converter limitations 134
Customize configuration files 123
Deploy graphic display 133
Dynamic.cnf file 127
Edit converted display 132
Fonts.cnf file 124
Import Master displays 129
Replace Master graphic elements 123
Test graphic display 133
Display converter
Add-in to Graphics Builder 122
Considerations 122
Error messages 245
Fatal messages 244
Getting started 122
Introduction 121
Warning messages 248
E
EVENT elements 166
Event text 107
Analog Input signal AI 171
Analog Output signal AO 172
Binary object GENBIN 185
Digital Input signal DI 173
Digital Output signal DO 174
Group alarm GRPALARM 199
275
Index
Group start GROUP 197

Manual station MANSTN 181
Motor Control MOTCON 191
Process Controller PIDCON 177
Process Controller PIDCONA 179
Ratio station RATIOSTN 182
Sequence SEQ 174
Standard event text 62
User defined controller GENCON 183
User defined object GENUSD 188
User-defined alarm and event text 63
Valve control VALVECON 194
EVENT TREAT 160
Event treat 169
EVENT TREAT properties
AL_FRBLK 161
AL_PRIO 160
AL_TOBLK 161
AUDIBLE 160
PERSISTB 161
TEXT_FRBLK 161
TEXT_TOBLK 161
TEXTCOMB 162
Event treatment 60
Overview 157, 255
Standard event text 61 to 62
User defined alarm text 63
User defined event text 63
EVENT_TREAT 107 to 108
F
Fault Tracing 135
Hardware indicators 135

Hot Keys in 800xA for Advant Master 37
276
P
Property text 107
R
RTA Board - Get status 257
RTA Board configuration 34
Character Conversion 50
Network and Node numbers 34
Save configuration 260
Setup Network and Node 259
Start On-Line Builder 260
Start/Stop of RTA 257
S
Simulated process data
Export control structure 58
Property signal generator 57
System Alarms 150
Alarm list for Controllers 151, 252
Alarm list for network 151, 251
Create and Setup 150
System Error Messages 135
System Status
Controller node 144
Network 138
Operator Workplace Node 139
T
H
Log index 72
M
MB300 Upload
Upload from AC400 controller 46, 48
TEXT 107, 109

TTD Logs 69
Create log template 86
Create TTD log in a controller 93
Log template
Log definition 74
Node configuration, controller details 79
3BSE030340R4101
Index
Node configuration, Download to

controller 81
Node configuration, Main view 76
Node configuration, Upload from
controller 80
Setup in IndustrialIT 800xA System 84
View TTD log in a controller 85
U
Uploading
MB300 45
W
Where to start 12
X
X font 125
3BSE030340R4101
277
Index
278
3BSE030340R4101
3BSE030340R4101. Printed in Sweden June 2005

Copyright 20032005 by ABB. All Rights Reserved
Registered Trademark of ABB.
Trademark of ABB.
http://www.abb.com/control
Automation Technology Products
Vsters, Sweden
www.abb.com/processautomation
email: processautomation@se.abb.com

Wickliffe, Ohio, USA
www.abb.com/processautomation
email: industrialitsolutions@us.abb.com

Mannheim, Germany
www.abb.de/processautomation
email:marketing.control-products@de.abb.com

Advant Configuration

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Advant Configuration

Caricato da

Copyright:

Formati disponibili

IndustrialIT

Process Object Lock........................................................................................................ 36

Section 4 - Alarm and Event

Section 5 - Time Tagged Data (TTD) Configuration

Working with TTD logs .......................................................................................84

Section 6 - Quick List Configuration

Section 7 - National Language Support Configuration

Section 8 - Data transfer via OPC DA

Section 9 - Display Converter

Section 10 - System Administration

Appendix A - Event Treat Elements

Appendix B - Event Texts

Appendix D - System Alarm List

Appendix E - Control Aspects

Appendix F - OPC Properties

About This Book

The System administrator that sets up the control system configuration

How to Use this Instruction

How to Use this Instruction

About This Book

The configuration of 800xA for Advant Master is described in Section 2,

Section 10, System Administrationdescribes error messages that are applicable to

managing users (creating new users, setting up passwords, and configuration of

About This Book

Use of Warning, Caution, Information, and Tip Icons

guidelines for adapting the connection to the used controllers

Use of Warning, Caution, Information, and Tip Icons

About This Book

The following convention is used for menu operations: MenuName >

System prompts/messages are shown in the Courier font, and user

Variables are shown using lowercase letters.

About This Book

Microsoft standard for user interface components, based

An aspect is a description of some properties of a real

A specialization of an aspect type. For example, the

Aspect Object Type

An Aspect Object type defines certain characteristics

A computer representation of a real world entity like a

A server that runs the central functions of the Aspect

About This Book

A software system, which implements one or several

A composite Aspect Object type describes a set of

connectivity components, up-loader, supporting aspect

A server that provides access to controllers and other

The configuration tool for Advant Master Controller.

A faceplate is an aspect that provides a graphical

About This Book

Function Chart Builder

Part of the configuration tool Control Builder A.

A graphic display is an aspect that provides a visual

Key combination that perform a specific function.

ABBs vision for enterprise automation.

A computer system that implements the IndustrialIT

A computer communicating on a network e.g. the

An application programming interface defined by the

A permission groups a set of operations that require the

About This Book

An application that is used to create, delete and organize

A process concept/equipment e.g. valve, motor,

A data field on an aspect of an Aspect Object that can be

Security controls a users authority to perform different

The users credentials, as provided by Windows

The node where the user is logged in. This makes it

The operation the user wants to perform the