advant configuration
Post on 02-Jun-2018
248 Views
Preview:
TRANSCRIPT
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 1/280
IndustrialIT
800xA - System
800xA for Advant MasterSystem Version 4.1
Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 2/280
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 3/280
Configuration
IndustrialIT
800xA - System
800xA for Advant MasterSystem Version 4.1
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 4/280
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 hard-
ware described in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission from ABB, and the contents thereof must not be imparted to a third party nor usedfor 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: June 2005
Document number: 3BSE030340R4101
TRADEMARKS
All rights to trademarks reside with their respective owners.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 5/280
3BSE030340R4101 5
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.....................................................................................................................15Related 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.............................................................29AC 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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 6/280
Table of Contents
6 3BSE030340R4101
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 ....................................................................................................... 42Min 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....................................................................48Building 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 .................................................................................................................. 59Defining 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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 7/280
Table of Contents
3BSE030340R4101 7
3BSE030340R4101 7
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 ConfigurationEvent Treat According to NLS...........................................................................107
Section 8 - Data transfer via OPC DA
OPC Read Operations....................................................................................................119
OPC Write Operations...................................................................................................120
Section 9 - Display ConverterGetting 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 AdvaCommandGraphic 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 AdministrationHardware Indicators ......................................................................................................135
System Diagnostics .......................................................................................................135
Fault Finding and User Repair ...........................................................................135
System Status .....................................................................................................135
System Alarms ...................................................................................................150
Backup/Restore Procedures...........................................................................................152
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 8/280
Table of Contents
8 3BSE030340R4101
Backup ..........................................................................................................152
Restore ..........................................................................................................153
Appendix A - Event Treat Elements
Introduction...................................................................................................................157
The Event Treat Database Element...............................................................................159
Appendix B - Event TextsAnalog 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 ............................................................................................. 191Valve 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 .................................................................. 204Standard 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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 9/280
Table of Contents
3BSE030340R4101 9
3BSE030340R4101 9
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 PropertiesOPC object type properties............................................................................................267
INDEX
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 10/280
Table of Contents
10 3BSE030340R4101
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 11/280
3BSE030340R4101 11
About This Book
GeneralThis book describes 800xA for Advant Master. The 800xA for Advant Masterproduct is used for connecting the workplaces to a Masterbus 300 control networkwith 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 definingdisplays, 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 Windowsfunctions 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 aredescribed in this book.
There are a number of user’s 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 thisinstruction.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 12/280
How to Use this Instruction About This Book
12 3BSE030340R4101
Where to Start
Read Product Overview on page 23, to learn more about 800xA for Advant Master.Read Industrial IT 800xA, System, Introduction and Installation if you want to startinstalling the product.Start reading Getting Started on page 27 if you want to start to setup theconfiguration.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 handlingof process events.
Read Appendix B, Event Textsfor a detailed description of how to setup the texts forthe process events. Start reading Section 9, Display Converterfor a detaileddescription of how to define and setup the displays for presenting process data fromthe AC 400 controllers.
How to Install 800xA for Advant Master
The 800xA for Advant Master is installed as a system extension to the workplacesoftware. See Industrial IT 800xA, System, Introduction and Installation forinstructions on how to install the 800xA for Advant Master software.
Configuration of 800xA for Advant MasterThe configuration of 800xA for Advant Master is described in Section 2,Configuration This section also includes examples of how to setup 800xA forAdvant Master applications.
Maintenance and Administrative Procedures
Section 10, System Administrationdescribes error messages that are applicable tothe 800xA for Advant Master.
This section also describes the configuration of 800xA for Advant Master. Refer tothe Industrial IT 800xA, System, Administration and Security for information onsystem administration procedures such as:
• managing users (creating new users, setting up passwords, and configuration of
user preferences)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 13/280
About This Book Use of Warning, Caution, Information, and Tip Icons
3BSE030340R4101 13
• guidelines for adapting the connection to the used controllers
On-Line Help
Comprehensive on-line help is available for the software. Access to the completehelp files is available via the menu bar.
Use of Warning, Caution, Information, and Tip IconsThis publication includes Warning, Caution, and Information where appropriateto point out safety related or other important information. It also includes Tip topoint out useful hints to the reader. The corresponding symbols should beinterpreted as follows:
Although Warning hazards are related to personal injury, and Caution hazards areassociated with equipment or property damage, it should be understood thatoperation of damaged equipment could, under certain operational conditions, resultin degraded process performance leading to personal injury or death. Therefore,comply fully with all Warning and Caution notices.
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 personalinjury.
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 resultin 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.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 14/280
Document Conventions About This Book
14 3BSE030340R4101
Document ConventionsThe following conventions are used for the presentation of material:
• The words in names of screen elements (for example, the title in the title bar ofa 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 thekeyboard. For example, press the ENTER key.
• Lowercase letters are used for the name of a keyboard key that is not labeled onthe keyboard. For example, the space bar, comma key, and so on.
• Press CTRL+C indicates that you must hold down the CTRL key whilepressing 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 (tocopy 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 WindowsTask Bar.
• System prompts/messages are shown in the Courier font, and userresponses/input are in the boldfaced Courier font. For example, if you enter avalue 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 asfollows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 15/280
About This Book Terminology
3BSE030340R4101 15
TerminologyThe list contains terms and abbreviations that are unique to ABB or have a usage ordefinition that is different from standard industry usage.
Table 1. Terminology
Term Description
ActiveX Microsoft standard for user interface components, basedon definition of software interfaces.
Aspect An aspect is a description of some properties of a realworld entity. The properties described could bemechanical layout, how the object is controlled, a livevideo image, name of the object etc.
Aspect Category A specialization of an aspect type. For example, theaspect type Graphic Display includes the categoriesOverview, Group and Object Display.
Aspect Object Type An Aspect Object type defines certain characteristicsthat are shared between several Aspect Objectinstances, such as a basic set of common aspects. Thismakes it possible to create and efficiently re-use
standardized solutions to frequently recurring problems.For example, rather than building an Aspect Object fromscratch for every valve in a plant, you can define a set ofvalve types, and then create all valve objects asinstances of these types.
Aspect Objects A computer representation of a real world entity like apump, a valve, an order or a virtual object like a service.This computer representation is implemented by the800xA System. An Aspect Object works like aninformation container for it’s aspects.
Aspect Server A server that runs the central functions of the AspectObject architecture, such as Aspect Directory, Structureand Name Server, Cross Referencing, File SetDistribution, etc.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 16/280
Terminology About This Book
16 3BSE030340R4101
Aspect System A software system, which implements one or severalaspect types by providing one or several aspect systemobjects.
Composite Aspect
Object Type
A composite Aspect Object type describes a set of
Aspect Objects organized in a structure, with a parentobject and one or several child objects. The children in acomposite object type are called formal instances,because they inherit from object types definedelsewhere in the Object Type Structure, but they are notactual instances. When a composite object isinstantiated actual instances are created for these childobjects.
OCS IntegrationProduct
connectivity components, up-loader, supporting aspectsystems (e.g for the configuration), and graphicalelements, faceplates, Aspect Object Types, etc., bundledtogether to provide the integration of a certain type ofdevices 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 andevent data. A Connectivity Server runs services relatedto OPC/DA, OPC/AE, OPC/HDA.
Control Builder A The configuration tool for Advant Master Controller.Control Builder A consists of Application Builder, BusConfiguration Builder, Function Chart Builder and theoption On-Line Builder.
Faceplate A faceplate is an aspect that provides a graphicalrepresentation of a certain aspect object, withpresentation of certain properties related to the object,and mechanism for operator interaction such as on/off,increase/decrease, etc. Aspect Object types ofteninclude several faceplate aspects, providing differentpresentation and interaction possibilities.
Table 1. Terminology
Term Description
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 17/280
About This Book Terminology
3BSE030340R4101 17
Function Chart Builder Part of the configuration tool Control Builder A.
Graphic Display A graphic display is an aspect that provides a visualpresentation. It consists of static graphics representingfor example tanks, pipes etc., and graphic elements that
present dynamic information. Graphic displays are oftenused to present the state of a process or a part of aprocess, but are useful in any context where dynamicgraphical information is needed.
Hot Key Key combination that perform a specific function.
IndustrialIT ABB’s vision for enterprise automation.
IndustrialIT 800xASystem
A computer system that implements the IndustrialITvision.
Node A computer communicating on a network e.g. theInternet, Plant, Control or IO network. Each nodetypically has a unique node address with a formatdepending on the network it is connected to.
OPC/DA An application programming interface defined by the
standardization group OPC Foundation. The standarddefines how to access large amounts of real-time databetween applications. The OPC standard interface isused between automation/control applications, fieldsystems/devices and business/office application.
Permission A permission groups a set of operations that require thesame authority. For each operation defined for an
aspect, the aspect category specifies the permissionneeded to use that interface.
Table 1. Terminology
Term Description
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 18/280
Terminology About This Book
18 3BSE030340R4101
Plant Explorer An application that is used to create, delete and organizeAspect Objects and Aspects within the 800xA System.The plant explorer organizes the Aspect Objects instructures according to functionality, location etc. Youcan also use it to browse and search the structures ofthe 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 beaccessed through OPC using the standard AspectObject reference syntax.
A data field on an ActiveX control accessible from theVisual Basic editor.
Security Security controls a user’s authority to perform differentoperations on Aspect Objects, depending on severalparameters:
• The user’s credentials, as provided by Windows
• The node where the user is logged in. This makes it
possible to give a user different authority dependingon where he/she is located, e.g. close to theprocess equipment, in a control room, or at homeaccessing the system through Internet.
• The operation the user wants to perform theoperation on.
Server A node that runs one or several Afw Services.It is the part of the software that supply data to asubscriber.
Table 1. Terminology
Term Description
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 19/280
About This Book Terminology
3BSE030340R4101 19
Structure A hierarchical tree organization of Aspect Objects.Each structure is used to define a certain kind of relationbetween Aspect Object. The functional structure defineshow a function can be divided into sub functions, thelocation structure defines how different objects are
located within each other.The control structure defines how functions are executedby tasks, controllers etc. An Aspect Object can belocated in several structures, for example both in afunctional structure and in a location structure.
System Application A software component, based on the Aspect Objectarchitecture, which provides functionality. System
applications cooperate according to rules defined be theAspect Object architecture. They are normally bundledinto the system products or system extensions. Systemapplications are implemented as client applications orservices. 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 applicationsthat are bundled as an extension to one or severalexisting System Product(s). A System extension canonly be installed if (one of) the corresponding SystemProduct(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 frominformation present in the devices.
Table 1. Terminology
Term Description
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 20/280
Related Documentation About This Book
20 3BSE030340R4101
Related Documentation
User application A configuration of software and hardware componentsthat applies to a specific problem, e.g. a specific processcontrol problem. A user application consists of a set ofsimple and composite Aspect Object instances, withparameter values and other configuration data for the
aspects, e.g control logic, graphics, alarm and eventspecifications, reports etc.
View An Aspect can have several ways to be presenteddepending on the task performed, like viewing orconfiguration. 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 workplaceapplications.
Table 2. Related Documentation
Category Title Description
Installation IndustrialIT 800xA System Installation This book describes the installationprocedure for 800xA System and 800xAfor Advant Master.
IndustrialIT 800xA System Post
Installation
This book describes the post installation
procedure for 800xA System and 800xAfor Advant Master.
Table 1. Terminology
Term Description
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 21/280
About This Book Related Documentation
3BSE030340R4101 21
Configuration IndustrialIT 800xA System800xA for Advant MasterExtended Graphic Library
This book describes the library ofoptional graphic elements forAC 400 Series controllers objects.
IndustrialIT 800xA System
800xA for Advant MasterGraphic Library
This book describes all the graphic
elements and faceplates for AC 400Series controllers specific object types.
IndustrialIT 800xA SystemOperator Workplace Configuration
This book describes how to set up anOperator Workplace.
IndustrialIT 800xA SystemAdministration and Security
This book describes user handling,security settings, system backup etc.
Operation IndustrialIT
800xA System800xA for Advant MasterOperation
This book describes how to operate800xA for Advant Master.
Table 2. Related Documentation
Category Title Description
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 22/280
Related Documentation About This Book
22 3BSE030340R4101
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 23/280
3BSE030340R4101 23
Section 1 Introduction
Product OverviewThe Operator Workplace software is a product for process monitoring and control.The generic design makes it possible to use the Operator Workplace together withmany different types of Process Control Systems, both systems provided by ABB aswell 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 (Masterversion), in a MasterBus 300 network, and extends the total functionality of theSystem utilizing the best of the AC 400 controller system.
Product Scope
800xA for Advant Master is a product which together with the Operator Workplacegives 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 fromthe AC 400 controllers or off-line from the AC 400 Engineering toolsdatabases.
• The possibility to customize the event and alarm reporting and presentationwith just a few configuration actions.
• To use the AC 400 TTD historical logs as data source to Operator WorkplaceHistorian, but also tools to configure new TTD logs in the controllers.
• Powerful maintenance and supervision of the Advant Master Control systemitself using the System Status, System Alarms and RTA Board Controlfunctions.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 24/280
What You Can Do with 800xA for Advant Master Section 1 Introduction
24 3BSE030340R4101
What You Can Do with 800xA for Advant Master
This list is an example of the engineering that you can do with800xA for Advant Master.
• Configure the connection of the workplace to the MasterBus 300 controlnetwork.
• Convert the displays and display elements from older versions ofABB Operator stations.
• Setup the workplace for handling the process data that is defined inthe database of the AC 400 controllers. You do not need to define the databaseagain, it is read from the controllers over the network.
• Setup the event handling for the process events that are reported fromthe AC 400 controllers.
• Define and activate the logging of process data, including presentation ofthe stored data logs.
• Collect and present System status for the entire control system, includingthe AC 400 controllers and the MB 300 control network.
Prerequisites and Requirements
The general hardware and software requirements for the Operator Workplaceproduct are described in the Industrial IT 800xA System, Introduction and
Installation.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 25/280
3BSE030340R4101 25
Section 2 Configuration
Before You StartMake sure that you have access to either of the following:
• The Connectivity Server is connected to the AC 400 controllers (theMasterBus 300 control network).
• The database instances from the Function Chart Builder (AC 400 ControllerEngineering tools).
You should have at least briefly read Industrial IT 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 toperform the configuration work described in this section.
Controller Documentation
The AC 400 controller documentation covering all manuals needed for
configuration, operation or maintenance of AC 450 or AC 410 controllers areincluded in 800xA for Advant Master. The manuals are available in the followingways:
• Via object type specific bookmarks available as aspects in the ControlStructure on the uploaded Advant Master objects. The manuals can also beopened via the context menu on Advant Master objects in the System Statusviewer. See Figure 1 below.
The Application Engineer or System Engineer has to be a member of the MSWindows “Power Users” group or the “Administrators” group to be able toperform the configurations.
C t ll D t ti S ti 2 C fi ti
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 26/280
Controller Documentation Section 2 Configuration
26 3BSE030340R4101
• The complete collection of AC 400 manuals can be found on the AC 400Documentation object in the Object type structure. The manuals that do nothave a related object type in 800xA for Advant Master can only be opened viathe AC 400 Documentation object. See Figure 2 below.
Figure 1. Bookmark on I/O
Section 2 Configuration Getting Started
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 27/280
Section 2 Configuration Getting Started
3BSE030340R4101 27
Getting Started
There are normally two different scenarios for the configuration work on an800xA for Advant Master system:
1. You have an existing system that is in operation. The engineering ofthe controllers is already made. The controllers are already up and running.
Figure 2. AC 400 Documentation Object
Getting Started Section 2 Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 28/280
Getting Started Section 2 Configuration
28 3BSE030340R4101
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 Workplaceapplications 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).
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. 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 Processand system objects).
5. Modify (if required) the Alarm and Event default setting.
You can choose No Conversion (English), Swedish or German when configuringthe RTA Board.
Section 2 Configuration Configuration of clock synchronization settings
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 29/280
Section 2 Configuration Configuration of clock synchronization settings
3BSE030340R4101 29
6. 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 describedin this book. Please read the corresponding User´s Guides.
Configuration of clock synchronization settings
This document describes two possible configuration settings for timesynchronization 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 aconfiguration with AC 400 Series controllers on MB300 and AC 800Mcontrollers on a TCP/IP network.
A thorough description of synchronization strategies and overall configuration isprovided 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 isrecommended to use an AC 400 Series controller as clock master. The describedconfiguration will receive time synchronization from the MB300 network anddistribute it to other Operator Workplace nodes (e.g Aspect Servers, Clients) in thesystem. Manual time settings (e.g from client nodes) or local time shifts in thesystem 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
Configuration of clock synchronization settings Section 2 Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 30/280
g y g g
30 3BSE030340R4101
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 configurethe 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
Section 2 Configuration 800xA for Advant Master Connectivity server as Clock Master
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 31/280
3BSE030340R4101 31
4. Select the Configuration tab in the aspect window.
5. Place the Provider, selected to be master, first in the list. The providers belowwill automatically be configured as standby.
800xA for Advant Master Connectivity server as Clock Master
This description is valid for a system configuration with AC 400 Series controllerson MB300 and AC 800M controllers on a TCP/IP network. The describedconfiguration will synchronize all nodes on the MB300 network from the RTABoard in the configured CS.
Windows registry settings
For the configuration using 800xA for Advant Master Connectivity server as clockmaster, change the synchronization direction between the Connectivity Server andthe RTA Board. This is done by changing a parameter in the registry.
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 Boardobject.
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.
All Time Synchronization services should be enabled.
It is always a risk to change values in the Windows registry edit. Be sure youhave a backup for safety reasons, so the computer can be restored if somethinggoes wrong.
This is done locally in the Connectivity Server with a RTA Board.
800xA for Advant Master Connectivity server as Clock Master Section 2 Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 32/280
32 3BSE030340R4101
In the RTA Board Configuration window, enter mdb CLOCK_SYNCH.
Figure 4. RTA Board Control Aspect
Section 2 Configuration No Synchronization
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 33/280
3BSE030340R4101 33
Change the “CLK_MAST” parameter to “0” as described in window,
see Figure 5.
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 BoardControl aspect.
No Synchronization
If you for some reason (mixed systems) do not want any synchronization betweenthe RTA Board (MB 300 network) and the Connectivity Server, you can set theparameter SYNC_INTERVAL to a negative value in the registry (same key asabove, -1 put in FFFFFFFF).
Figure 5. CLOCK_SYNCH DB Element
RTA Board Configuration Section 2 Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 34/280
34 3BSE030340R4101
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
Setup Network and Node Number
Use Configuration Wizard in order to setup network and node number. Please see Industrial IT 800xA System, Post Installation Setup.
Configure Alarm and Event Lists
Available Lists
There are four Advant Master specific alarm and event lists.
• AC400 Alarm Line. It is used in the alarm line in the AC 400 OperatorWorkplace, 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 systemalarms.
The network and node numbers must be setup before the Operator Workplacenode can communicate with the control network.
The RTA Board configuration view (Network and Node configuration) will alsocome up during the configuration of the system. The view is included when yourun the Configuration wizard.
Section 2 Configuration Configure Alarm and Event Lists
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 35/280
3BSE030340R4101 35
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.
Default ConfigurationsThe relevant default alarm and event configurations can be found in the LibraryStructure as part of the object MB300 Default Configurations, see Figure 7.
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 logalarms or events on a printer.
Figure 6. Available Alarm and Event Lists
Figure 7. Default Alarm and Event Configurations
Process Object Lock Section 2 Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 36/280
36 3BSE030340R4101
• MB300 Default System Alarm List. It is used to configure the AC400 System
Alarm List.
Process Object Lock
It is possible to lock a process object via the lock button in the Faceplate to excludeother operators from operation on the specific object. The lock is released when theFaceplate is closed, the lock button is clicked or else after a specific time-out periodof 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 isautomatically locked at Faceplate call-up. This function can be enabled on a user viathe User Profile aspect Graphics Profile Values in the User Structure (see Figure 8).
See Industrial IT System, Operator Workplace Configuration for details on how toconfigure User Profile aspects.
For more information on how to configure alarm and event lists, refer to the Industrial IT 800xA, System, Operator Workplace Configuration.
Figure 8. Autolock Enabled in an Graphics Profile Values Aspect
Section 2 Configuration Process Object Sensitive Hot Keys
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 37/280
3BSE030340R4101 37
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 enablesconfiguration of key combinations that perform specific functions, such as openingan 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/Open/True
Off/StopClose/False
Man
CTRL+
SHIFT+
Q
CTRL+
SHIFT+
1
CTRL+
SHIFT+
0
CTRL+
SHIFT+
Y
AI X
AO X X
DI X X X
DO X X X X
PIDCONA X X
PIDCON X X
MANSTN X X
RATIONSTN X X
MOTCON X X X X
VALVECON X X X X
GROUP X X X X
Process Object Sensitive Hot Keys Section 2 Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 38/280
38 3BSE030340R4101
SEQUENCE X X X X
GENBIN X X X X
GENCON X X
GENUSD X X
DATB X X
TEXT_DATA X X X X
DRICONE X X X X
DRICONS X X X X
MOTCON_I X X X X
Table 4. Predefined Hot Keys 2
Object Type Auto E1 E2 Small
Increase
Small
Decrease
CTRL+
SHIFT+
U
CTRL+
SHIFT+
O
CTRL+
SHIFT+
P
CTRL+
SHIFT+
K
CTRL+
SHIFT+
H
AI
AO X X X
DI
DO X
PIDCONA X X X X X
PIDCON X X X X X
Table 3. Predefined Hot Keys 1 (Continued)
Object Type Acknowledge On/Start/
Open/True
Off/Stop
Close/False Man
Section 2 Configuration Process Object Sensitive Hot Keys
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 39/280
3BSE030340R4101 39
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 supportfor highlighted and selected objects. It makes it also easier for different connectedOCS 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 selectedand highlighted concepts.
For more information about the Verb Map Aspect see Industrial IT 800xA, System,
Operator Workplace Configuration.
MANSTN X X X
RATIONSTN X X X X
MOTCON X
VALVECON X
GROUP X
SEQUENCE X
GENBIN X
GENCON X X X X X
GENUSD X X X
DATB
TEXT_DATA X
DRICONE X
DRICONS X
MOTCON_I X
Table 4. Predefined Hot Keys 2 (Continued)
Object Type Auto E1 E2 Small
Increase
Small
Decrease
AC400 Operator Workplace Section 2 Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 40/280
40 3BSE030340R4101
AC400 Operator Workplace
Tools in AC 400 Operator Workplace
The following chapters describe the added/changed functionality/tools in theAC 400 Operator Workplace. Please see Industrial IT 800xA, System, Operator
Workplace Configuration for a description of generic Operator Workplacefunctionality.
• AC 400 Alarm LinesThis area shows the three latest unacknowledged process alarms in the system.
• All Process AlarmsClick this button to view a list of all process alarms.
• All Process EventShows a list of all process events and Advant Master system events.
• System AlarmsClick the button to view a list of all Advant Master system alarms.
• System Event List
Figure 9. AC 400 Specific Tools
All Process Alarms
All Process Events
System Alarms
System Event ListSystem Status
External Alarms
Aspect Menu
Close all Overlaps
Date and TimeShow Help
AC 400 Lines
Section 2 Configuration Recommended Workplace Settings
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 41/280
3BSE030340R4101 41
• System Status
Shows System Status for all control networks and controllers included in thesystem.
• External AlarmsWhen you click the button the status for all External Alarms configured in thesystem, will be shown. For more information about External Alarms,read Industrial IT 800xA, System, Operator Workplace Configuration.
• Close all OverlapsUse this button to close all overlaps (pop-up windows).
• Show HelpClick the Show Help button to view the On-line Help.
• Date & TimeBoth 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 thisdocument. It is possible to customize the AC 400 Operator Workplace.For details about workplace settings Industrial IT 800xA, System, Operator
Workplace Configuration.
Min and Max Dialog Section 2 Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 42/280
42 3BSE030340R4101
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 thecontrol connection for each of the Advant Master objects types have been defined torequire either tune or operate permission. This together with the correspondingsystem 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 operationsavailable for a single user or a group of users.
When the user does not possess the permissions required for an operation thebuttons in the faceplate will be dimmed. Number fields will not be open for inputetc.
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 totune, e.g. set alarm limits or blocking parameters.For more information about Security settings, please read the Industrial IT 800xA,
System, Administration and Security.
Section 2 Configuration Min and Max Dialog
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 43/280
3BSE030340R4101 43
Figure 10. Min and Max Dialog
Min and Max Dialog Section 2 Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 44/280
44 3BSE030340R4101
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 45/280
3BSE030340R4101 45
Section 3 Engineering
Using the MB 300 Uploader AspectThe MB300 Uploader aspect is placed in the Control Structure. It is possible tomake 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 atime.
Figure 11. Upload - Control Structure
Network Level
Node/ControllerLevel
Section 3 Engineering
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 46/280
46 3BSE030340R4101
The MB 300 Uploader aspect has two tabs:
• The From Controller tab that contains functions to read the informationdirectly from the controllers (via the MB 300 network), refer toUsing the From Controller Tab to Upload on page 46.
• The From FCB tab that contains functions to read the information from asource 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 fromthe AC 400 controller to the Operator Workplace.
Adding or Removing Object Types to Upload
Click Add or Remove to modify the list with object types that you want to includein the Upload. If you leave the list blank, all object types are included (this is thedefault).
Figure 12. MB 300 Uploader, From Controller
Section 3 Engineering
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 47/280
3BSE030340R4101 47
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 tracingand simulation, and should not be modified. They should only be modified on directrequest from the supplier.
Starting the Upload
Click on Start Upload when you are ready for the upload. The window in the lowerpart 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.
Using the From FCB Tab to Upload Section 3 Engineering
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 48/280
48 3BSE030340R4101
Using the From FCB Tab to Upload
This aspect makes it possible to request an upload of object data based oninformation from the Function Chart Builder Engineering tool.
Adding or Removing Object Types to Upload
Click Add or Remove to modify the list with object types that you want to includein the Upload. If you leave the list blank, all object types are included (this is thedefault).
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.
Figure 13. MB 300 Uploader, From FCB
Section 3 Engineering Building the Control Structure On-line
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 49/280
3BSE030340R4101 49
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 engineeringsoftware FCB (Function Chart Builder). You have to fill in the name of theFCB Database File (ODB file) to retrieve information from. This choicerequires that FCB is installed at the same node.
• Uncheck the Create Uploader Source File checkbox and check BuildControl Structure checkbox to build the Control Structure from a previouslycreated Uploader Source File (OCD file). You have to enter the name of theUploader Source File. This choice does not require that FCB is installed at thesame node. See Building the Control Structure On-line. [Ändra till sidnr-ref]
• Check Create Uploader Source File and uncheck Build Control Structure tocreate a Uploader Source file based on the information from the engineering
software FCB (Function Chart Builder). You have to fill in the name of theFCB Database File (ODB file) to retrieve information from, and the name ofthe Uploader Source File (OCD file) to create. This option does not update orcreate the Control Structure. Can be used to produce the OCD file for other800xA systems using the same controllers. This choice requires that FCB isinstalled at the same node.
Starting the Upload
Click on the Start Upload button when you are ready for the upload. The windowin 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.
Building the Control Structure On-line
The Control Structure is based on the controllers in your Advant Master System.To build the structure, do as follows:
Building the Control Structure On-line Section 3 Engineering
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 50/280
50 3BSE030340R4101
• Use the Configuration Wizard to create an RTA Board object
• Add each AC 400 controller to the structure using the correct node object typeas template and enter the correct network and node number.
• For each AC 400 controller, run the Upload procedure (as described on the nextpages) to populate the whole structure of I/O boards and Process and Systemobjects. 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 inName and Description converted to 8-bit. This to prevent incorrect naming, forexample “H\G NIV]” instead of “HÖG 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 processgraphics 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 andcreates the corresponding objects and aspects in the Control Structure.
The following steps describe how to create the complete Control Structure, for oneController Node starting from an empty Control Structure.
1. Go to the Control Structure.
2. Add the Controller object. Request creation of a new object and select aController type that corresponds to the controller you are adding.
Section 3 Engineering Building the Control Structure On-line
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 51/280
3BSE030340R4101 51
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 probablynot be included in the name). See Figure 14.
Figure 14. Creating a Controller Object Type
Building the Control Structure On-line Section 3 Engineering
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 52/280
52 3BSE030340R4101
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:
For a controller with many objects of certain types it may be wise to read atleast the most populated object types one by one and then read the others insequence.
Check the Create Uploader Source File and the Build Control Structure
check boxes. (These check boxes are only unchecked during fault tracing, andshall 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.
4. Uploading can take some time. When complete, use Plant Explorer to browsethe structure and verify that everything is in place as expected.
5. Start building applications based on these objects, see the Industrial IT 800xA,
System, Operator Workplace Configuration.
Figure 15. The MB 300 Uploader aspect
Section 3 Engineering Building the Control Structure Offline
B ildi th C t l St t Offli
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 53/280
3BSE030340R4101 53
Building the Control Structure Offline
The Control Structure can also be built using the output from the ControllerEngineering tool FCB. This has some advantages for a new site:
• You can create the Control Structure step by step as the Controller Engineeringproceeds and thereby extend your Operator Workplace applications stepwise.
• You can work off-line from the controllers (without connection to the controlnetwork), 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 inUsing the From FCB Tab to Upload on page 48:
• Use the FCB 6.0 MB 300 Uploader option or a later version on the EngineeringPC. Create source files for each controller and copy them to your AdvantMaster Server.
• Run the MB 300 Uploader aspect for each controller using the source files asinput. You can populate one controller at a time or one or a couple of objecttypes at a time.
• When the controller is available on the network, you can retrieve some ofthe 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 completeControl Structure for the AC 450 Controller (node address 31,18) starting with anempty Control Structure. We assume that you have already installed the MB 300Uploader option on the PC where you have the engineering software running.Refer to the Function Chart Builder User’s Guide for a detailed description on howto 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 menuand select Advant > Engineering > Utilities > MB 300 Uploader option onthe Engineering PC.
Building the Control Structure Offline Section 3 Engineering
3 Th f ll i di l b
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 54/280
54 3BSE030340R4101
3. The following dialog box appears:
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 inthe Object Types to upload list. You move object types between the lists byselecting 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 Workplaceserver. 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.
Figure 16. FCB Upload
Section 3 Engineering Building the Control Structure Offline
Now we can go over to the Operator Workplace server machine Log in as a
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 55/280
3BSE030340R4101 55
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 tutorialin 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.
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 sourcefile Load-file-31-18.ocd. Select Start Upload, see Figure 18.
Figure 17. Selecting the Object Type AC 450
Building the Control Structure Offline Section 3 Engineering
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 56/280
56 3BSE030340R4101
This step can be split up into several parts, as it is possible to work with oneobject type at a time. If you know that you have only added or modified objectsof type AI in the engineering database, then other object types do not have to beuploaded.
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 applicationsbased on these objects, see also the Industrial IT 800xA, System, Operator
Workplace Configuration.
7. Before you can go on-line with your system, you need to make an additionalupload session, directly toward the controllers. The reason is that some of thephysical addresses in the controllers are not available in the FCB files.
However, you have saved considerable time by using the time-lag betweenController Engineering and the time the controllers are installed and up andrunning.
8. Select the From Controller tab and click Start Upload. This will upload allobject data from the controller.
Figure 18. Creating the Control Structure for Node 31, 18
Section 3 Engineering Building a Control Structure for Test and Demo Purposes
Building a Control Structure for Test and Demo Purposes
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 57/280
3BSE030340R4101 57
Building a Control Structure for Test and Demo Purposes
It may sometimes be an advantage to be able to test or demonstrate yourapplications in a simulated Control Structure.
You can build a Control Structure with simulated values through the followingsteps:
1. Select the Control Structure in Plant Explorer.
2. Build a structure that includes the process and system objects that you want tosimulate.
3. Add the Property Signal Generator aspect to each object (process and system
objects) that you want simulated data from.
Note that the graphic presentation of object data, in the shape of faceplates ordisplay elements, does not work directly with simulated values from the PropertySignal Generator. You must define supervision and presentation properties toinput “simulated live data” into the presentation of faceplates or display elements.
Figure 19. Add Aspect Property Signal Generator
Building a Control Structure for Test and Demo Purposes Section 3 Engineering
4. Set up the configuration of the Signal Generator aspect to generate data for the
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 58/280
58 3BSE030340R4101
p g g p gspecific attributes. This set up includes specifying variable data style - Sinwave, Ramp, Random, Static Value etc. You specify the set up for each objectattribute.
5. Build your applications to work with this Control Structure with simulatedattributes.
6. Test your applications (demo applications, test applications).
7. Save the controller node objects in the Control Structure for future use byexporting each node separately, one by one. Start the Import/Export tool viaStart > All Programs > ABB Industrial IT 800xA > System > Import
Export. Use drag and drop when exporting the objects from thePlant Explorer to the Import/Export tool.
Figure 20. Setup for Property Signal Generator
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 59/280
3BSE030340R4101 59
Section 4 Alarm and Event
Audible Alarm
In order to be able to receive audible alarms, the audible event treatment propertymust 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. Pleasesee the 800xA System Operator Workplace Configuration for more information.
The 800xA for Advant Master faceplates are preconfigured to indicate hiding. Thealarm control button indicates this.
Defining Event Treatments Using RTA BoardConfiguration
You define the Event treatment by configuring data base elements on the RTABoard. After setting up the database on the RTA Board, you shall save the databaseconfiguration. See Appendix A, Event Treat Elements to get a detailed descriptionof the data base elements that you can configure. Appendix B, Event Texts containsa detailed description how to setup the event text elements.
When you have setup the event treatment, you shall save the RTA database. Look inRTA Board Configuration Tab on page 260 for guidance how to save the RTAdatabase.
Defining Event Treatment for Process and System Objects Section 4 Alarm and Event
Defining Event Treatment for Process and System Objects
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 60/280
60 3BSE030340R4101
g y j
Default Alarm and Event Settings
After installing the 800xA for Advant Master, you will find five (5) Default Alarmand Event aspect objects in the Library Structure, with default settings related toMasterBus 300 and Advant Controller 400 Series. See Figure 21 below. Referencethese when you need an alarm or event object.
They are predefined to meet your needs.
How to change the default settings is described in Industrial IT 800xA, System,
Operator Workplace Configuration.
Figure 21. Predefined Default Alarm and Event Aspect Objects for
MB 300
Section 4 Alarm and Event Defining Event Treatment
Defining Event Treatment
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 61/280
3BSE030340R4101 61
The Event Treatment for Advant Master objects are defined during the engineeringphase of the controller. When you build the Objects in the controller you assignvalues to special parameters that are important for the event handling. Theseparameters are mentioned in many “Advant OCS documents” under the collectivedesignation “Event-Treat-pointers”. They are used, for example, to determinewhether a change of status is to be handled as an alarm or an event. It is alsopossible 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 areallocated 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 pointerERR_TR. Passages of limits Low and High (L1 and H1) are another group with apointer 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 manycases this selection is satisfactory and permits you to start the system without furtheradjustment.
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 cannotbe 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.
Defining Event Treatment Section 4 Alarm and Event
Example 1: Standard Event Text
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 62/280
62 3BSE030340R4101
Figure 22 shows the alarm handling with a Standard event text for a DI signal.
Figure 22. Linkage Between Data Base Elements
S2
12345678
EVENT2
S3
Controller
Operator station
147252711
DI1.2
M2IN10000
1256
NAME VALUEACT ERRBLOCKED UPDATEDINVTESTEDERR CTRL
Digital Input(8.2)
210403839
14232022213637
CONVEYOR21000
1100022
18891716
DESCR DISTURBNORM TR MAN ENTRAL DELAY SELECTEDPROC SEC RP F BLKCLASS AL UNACK
NORM POSRP F CTLAL BLKPR BLKAL P BLKERR TRVALUE TR
E3 Group Alarm
AUDIBLEAL PRIOAL TOBLKAL FRBLKPERSISTBTEXT TOBTEXT FRBTEXTCOMB
Event Treat(25.2)
Event Texts
Property Texts
Section 4 Alarm and Event Defining Event Treatment
ERR_TR and VALUE_TR are pointers to elements in the Event Treat data base inthe operator station In this example both ERR TR and VALUE TR point at
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 63/280
3BSE030340R4101 63
the operator station. In this example, both ERR_TR and VALUE_TR point atEVENT2.
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 alarmAL_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 statusTEXTCOMB 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 andmeasurement 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.
Defining Event Treatment Section 4 Alarm and Event
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 64/280
64 3BSE030340R4101
Figure 23. Data Base Element Analog Input
1212435479
X1108
434452
59(3).109
K54010L100000.10V01S00.1%1000.0
19362223
AI1.1
Analog Input(6.16)
25427
5755562834404748373938
53
59.7959.80
OIL LEVEL0100000000000
4
020
3525
493326
59.74
59.7059.7559.7159.7659.7259.7759.7359.78
1
950.00850.00150.0150.01.0
29
30
31
32
NAME VALUEACT OVERFLOWBLOCKED ERRUNIT UPDATEDRANGEMAXRANGEMINCONV PARLIN CODESCANTFILTER PDEADBOVF CTRLTESTEDERR CTRLERR VAL
EN H2
HI LIM2 VALUE>H2EN H1HI LIM1 VALUE>H1EN L1LO LIM1 VALUE<L1EN L2LO LIM2 VALUE<L2HYST
DESCRDEC DISTURBNORM TR MAN ENTR
AL DELAYPROC SECCLASSH2 R FCLH1 R FCLL1 R FCLL2 R FCLER R FCL RP F BLKAL BLK AL UNACKPR BLK SELECTEDAL P BLKERR TR- -- -- -- -- -- --LIM 1 TRLIM 2 TR
E4 Group Alarm
Section 4 Alarm and Event Defining Event Treatment
As presented in Appendix A, Event Treat Elements, EVENT4 has the followingproperties:
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 65/280
3BSE030340R4101 65
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 itsnormal 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 baseon 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.
Defining Event Treatment Section 4 Alarm and Event
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 66/280
66 3BSE030340R4101
4. Click on the Start Config button. This will startup the On-line Builder toolwhich is used for the configuration of the RTA Board.
5. MDB EVENT20 and press <CR>. The data base element is displayed on thescreen.
6. Enter the values as shown in Figure 25.
Figure 24. RTA Board Configuration
Section 4 Alarm and Event Defining Event Treatment
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 67/280
3BSE030340R4101 67
The properties in the first part of EVENT20 are the same as for EVENT4 thatERR_TR points at. Another TEXTCOMB is used as property and event textsshall be user defined and not standard.
When you define the event and property texts, take note that the events arelinked to predefined lines in the segment Event Texts and Property Texts. Theselines 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 followingtable:
Figure 25. Changes in the Data Base Element EVENT20
Table 5. Standard Texts for the Pointer LIM_2_TR
Event PointerStandard
property text
Line
no
Standard
Event text
Line
noUpper limit H2 exceeded LIM_2_TR Limit H2 1 Alarm 1
Upper limit H2 re-entered LIM_2_TR Limit H2 1 Normal 3
Lower limit L2 exceeded LIM_2_TR Limit L2 2 Alarm 2
Lower limit L2 re-entered LIM_2_TR Limit L2 2 Normal 4
S2
123456
78
EVENT20
Event Treat(25.20)
12NOYESNONONO5
S3
AUDIBLEAL PRIOAL TOBLKAL FRBLKPERSISTBTEXT TOB
TEXT FRBTEXTCOMB
Event Texts
Property Texts
Defining Event Treatment Section 4 Alarm and Event
The property texts Limit H2 on line 1 and Limit L2 on line 2 shall be changedto Full and Empty. The standard event text Alarm on line 1 and 2 shall be
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 68/280
68 3BSE030340R4101
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 beentered in EVENT20.
7. Expand Event Text, and enter the text in accordance to the following:
Figure 26. Population of Segment S2 in the Event Treat Element
950 l50 l Normal Normal
S1
S3
EVENT20
Event Treat(25.20)
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)
Base part
Property Texts
EV1EV2EV3EV4EV5
EV6EV7EV8EV9EV10EV11EV12EV13EV14EV15EV16
Section 4 Alarm and Event Defining Event Treatment
8. Expand Property Texts, and enter the text according to the following:
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 69/280
3BSE030340R4101 69
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.
Figure 27. Population of Segment S3 in the Event Treat Element
FullEmpty
S1
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)
EVENT20
Event Treat(25.20)
S2
PRTE1PRTE2
PRTE3PRTE4PRTE5PRTE6PRTE7PRTE8PRTE9PRTE10PRTE11PRTE12PRTE13
PRTE14PRTE15PRTE16
Base part
Event Texts
Defining event filter on node level Section 4 Alarm and Event
Defining event filter on node level
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 70/280
70 3BSE030340R4101
It is possible to filter alarm and events to be sent from selected controllers on aMB300 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 includedinto 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:
1. Start the RTA board configuration from the RTA Board Control aspect.
2. Create one instance of the data base element NODE_DESCR for eachcontroller 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 thenetworks.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 boardconfiguration session and start a RTA Board Backup (also from the RTA BoardControl aspect).
5. Restart the RTA board from the RTA Board Control aspect.
6. Now the configuration is completed for this connectivity server. In caseredundancy is configured for this you need to repeat the configuration on theredundant connectivity server.
7. Restart the concerned controllers to make the changes take effect.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 71/280
Creating Time Tagged Data (TTD) Logs Section 5 Time Tagged Data (TTD) Configuration
A log also contains information about the data source.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 72/280
72 3BSE030340R4101
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 log’s sequence number within the log groupis called log index. The log group keeps the important parameters, storage intervaland 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 arespecific 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 theLog Template aspect.
Figure 29. Information About the Data Source
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 fastersample time than 9s.
Always use 9s sample time for the primary log when a sample time faster than 2min 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 networkand controllers in such a way that the operator interface may get slow, or evenstops working properly.
t1v1
t2v2
tnvn
Log
SourceInfo
DataSource
Section 5 Time Tagged Data (TTD) Configuration The TTD Source Aspect
The TTD Source Aspect
The Configuration Wizard creates this aspect when adding an RTA boardTh d fi h i f TTD C fi S d TTD D
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 73/280
3BSE030340R4101 73
The Configuration Wizard creates this aspect when adding an RTA board.The aspect defines the service groups for TTD Config Source and TTD DataSource. TTD Source is placed on the MB300 Network object and does normally notneed to be changed.
The Log Template AspectA Log Template is a re-usable template representing one log group. If you modifyan existing Log Template, the changes will affect existing logs that have beencreated using that Log Template.You define the Log template via the Log Templateaspect.
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 eachTTD log Group on the corresponding AC 400 Series Controller object.
You can also create a new Log Template aspect manually by adding a new HistoryLog Template object in the Library Structure. This method requires knowledge ofhow the TTD log groups are configured in the controller.
Figure 30. TTD Source Aspect
The Log Template Aspect Section 5 Time Tagged Data (TTD) Configuration
The aspect has two tabs:
• The Log Definition tab
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 74/280
74 3BSE030340R4101
• 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 withoutstoring anything by clicking Cancel.
You save the Log template definition by clicking the Apply button. On-line help isavailable by clicking the Help button.
Log Definition Tab
Figure 31. Log Template - Log Definition Tab
Section 5 Time Tagged Data (TTD) Configuration The Log Template Aspect
Log Name
Enter the log name in this field We recommend that you include the following partsin the name:
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 75/280
3BSE030340R4101 75
Enter the log name in this field. We recommend that you include the following partsin 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
TTD Log Storage Interval
This is the storage interval for the TTD log in the controller. Select the log storageinterval for the TTD log in the drop-down menu.
Figure 32. Log Template - TTD Data Collection Tab
TTD Node Configuration Aspect Section 5 Time Tagged Data (TTD) Configuration
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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 76/280
76 3BSE030340R4101
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 theentry field.
History Log Value Count
This is the storage size (number of stored values) in the history server. The defaultsize of the History log is double the size of the TTD log. If you want to change theHistory log size, you enter the number of stored values in the History log in theValue Count field. The Capacity (in time) is automatically calculated and presentedto the right of the entry field.
TTD Node Configuration Aspect
TTD Node Configuration is an aspect of the AC 400 Series Controller object inControl Structure. It has three different views:
• 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.
The TTD log storage interval and the TTD log value count must match aLog Group in the controller.
Section 5 Time Tagged Data (TTD) Configuration TTD Node Configuration Aspect
Main View
The main view of the TTD Node Configuration aspect presents the TTD logs in thecontroller.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 77/280
3BSE030340R4101 77
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 thecontroller is required.
Figure 33. TTD Node Configuration, Main View
TTD Node Configuration Aspect Section 5 Time Tagged Data (TTD) Configuration
Log
TTD log name (defined in the Log Template aspect that represents the Log Group)that the object property is included in.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 78/280
78 3BSE030340R4101
j p p y
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 inthe left window:
• 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).
Figure 34. TTD Node Configuration: Controller View, Log Groups
Section 5 Time Tagged Data (TTD) Configuration TTD Node Configuration Aspect
The second layout of the Controller View, showing the details for a selectedLog Group has the following columns in the right window, see Figure 35.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 79/280
3BSE030340R4101 79
• 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 alwaysbe Mom for primary logs.
• Source - Source shows if the log is primary or hierarchical. Only primary logsare 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.
Figure 35. TTD Node Configuration: Controller View,
Details About one Log Group
TTD Node Configuration Aspect Section 5 Time Tagged Data (TTD) Configuration
Synchronize View
The Synchronize view of the TTD Node Configuration aspect has the followingfunctionality:
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 80/280
80 3BSE030340R4101
• 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 Configurationaspects.
Click Upload and wait.The progress is presented in the text window, see Figure 36.
Figure 36. Upload of TTD Logs
Section 5 Time Tagged Data (TTD) Configuration TTD Node Configuration Aspect
The result of a completed Upload is as follows:
• A Log Template aspect for each type of TTD Log Group is created on thecorresponding AC450 and AC410 Controller object.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 81/280
3BSE030340R4101 81
• A Log Configuration aspect is created on each logged object. It has the primarylog being a TTD log configured according to the information read from thecontroller and with an extension into a corresponding hierarchical log twice aslarge as the primary log. To extend it, change the corresponding Log templateand it will affect all logs belonging to that Log Template.
• The hierarchical logs are disregarded.
Download of new log configurations into the Controller
To download and activate new TTD logs you can use the synchronization view ofthe TTD Node Configuration aspect. Click Download to the right and wait.The Match Existing dialog box appears, see Figure 37.
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 thedownloaded log to. Click No when a new log will be created in the controller foreach configured un-mapped log.
You can also do Download for an individual log from the Log configurationaspect on the process object, see The Log Configuration Aspect on page 82.
Figure 37. Match Existing
The Log Configuration Aspect Section 5 Time Tagged Data (TTD) Configuration
The progress is logged in the text window, see Figure 38.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 82/280
82 3BSE030340R4101
When the download is finished, you can check the result in the log on the screen butyou can also bring up the Main View to check specific logs.
The Log Configuration Aspect
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:
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 andselects 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 andselect the TTD Data Collection tab.
Figure 38. Downloading the new TTD logs
Section 5 Time Tagged Data (TTD) Configuration The Log Configuration Aspect
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.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 83/280
3BSE030340R4101 83
In the Presentation tab you can define some attributes for trend display such asengineering 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 Configurationaspects for all objects included in the logs.
Figure 39. Log Configuration Aspect
Working with TTD logs Section 5 Time Tagged Data (TTD) Configuration
Working with TTD logs
We have now discussed each configuration aspect. In this section you will find threeexamples of how to make the configuration. The assumption is that you have aControl Structure for an AC 400 controller and that the controller has configured
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 84/280
84 3BSE030340R4101
Control Structure for an AC 400 controller and that the controller has configuredTTD 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 newTTD logs by creating Log Templates for them.
3. The third example utilizes the Log templates when you create new logs anddownload them to the controllers.
The recommended method to configure the History Aspect System if thecontroller already is configured by terms of TTD groups and logs is however toperform Upload. This is done from the Synchronize View of the TTD NodeConfiguration aspect of the controller objects. This action creates all necessary
objects and aspects.
Section 5 Time Tagged Data (TTD) Configuration Working with TTD logs
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.S l t th TTD N d C fi ti t
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 85/280
3BSE030340R4101 85
Select the TTD Node Configuration aspect.
3. Select the Controller View. See Figure 40.
To the left you see a list with the existing Log Groups, and to the right a storageinterval (Interval) and storage size (Capacity) for each Log Group. If you select oneof the groups you can see the existing logs in that group to the right, see alsoFigure 41.
Figure 40. TTD Node Configuration: Controller View, Log Groups
Working with TTD logs Section 5 Time Tagged Data (TTD) Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 86/280
86 3BSE030340R4101
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 anda storage size of 2 hours (240 values). We already know (from example 1) that asuitable TTD log group exists in this controller and there are at least one free indexin the group. The TTD log shall be stored and extended in the History ConfigurationAspect System to a storage capacity of 4 hours.
Furthermore, a hierarchical log shall be created within the History ConfigurationAspect System which aggregates the primary information into an average, stored
with 1 minutes interval over 1 day (1440 values) aggregated as average.1. Select the Library Structure in Plant Explorer.
2. Create a new object of the History Log Template type. Give it a proper Nameand Description. Let the name reflect to the TTD log template and the storageinterval and size. It makes it easier to select a log template during log creation
Figure 41. TTD Node Configuration: Controller View, details about
one Log Group
Section 5 Time Tagged Data (TTD) Configuration Working with TTD logs
It is recommended to save the log template in the Library Structure,History Log Template Object Type.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 87/280
3BSE030340R4101 87
3. An aspect of the category Log Template is created by default. Select it in thepreview window or as a pop-up (double click on it).
Figure 42. Creating the Log Template Object
Working with TTD logs Section 5 Time Tagged Data (TTD) Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 88/280
88 3BSE030340R4101
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 43. Log Template Aspect
Figure 44. Create New Log of TTD type
Section 5 Time Tagged Data (TTD) Configuration Working with TTD logs
5. Select TTD in the Data Source drop-down menu. In the Log Type area, selectthe Direct radio button. Click OK to save the settings.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 89/280
3BSE030340R4101 89
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 hourscapacity), see Figure 46.
Figure 45. Creating TTD Log Templates
Working with TTD logs Section 5 Time Tagged Data (TTD) Configuration
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).
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 90/280
90 3BSE030340R4101
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.
Figure 46. Log Configuration - TTD Data collection
Section 5 Time Tagged Data (TTD) Configuration Working with TTD logs
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 91/280
3BSE030340R4101 91
10. Enter the following for the hierarchical log and save it:
– Log name: SecTTD_1m_24h
– Log type: Hierarchical
Figure 47. Creating the Hierarchical Log
Working with TTD logs Section 5 Time Tagged Data (TTD) Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 92/280
92 3BSE030340R4101
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.
Figure 48. Hierarchical Log, Filling in Capacity
Section 5 Time Tagged Data (TTD) Configuration Working with TTD logs
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.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 93/280
3BSE030340R4101 93
3. Select the process object. Add the Log Configuration aspect. Give it a properName and Description and save it.
4. Select the aspect and then - in the preview area - select the object and clickAdd Property Log.
5. Select VALUE in the Property list and theTTD_LogTemplate_30s_24h:Log Template in the Template drop-downmenu. Click OK.
Figure 49. New Property Log Dialog
Working with TTD logs Section 5 Time Tagged Data (TTD) Configuration
6. The preview area now looks like Figure 50.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 94/280
94 3BSE030340R4101
Figure 50. Log Configuration - presentation
Section 5 Time Tagged Data (TTD) Configuration Working with TTD logs
7. Go to the Presentation tab and enter the following. Save it by clicking Apply.
– Engineering Units: KPa
– Normal Maximum: 200
– Normal Minimum: 0
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 95/280
3BSE030340R4101 95
– 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 NodeConfiguration aspect in the aspect list.
10. Select the Synchronize view and click Download. Select No in the MatchExisting dialog box that appears. Study the results on the screen as thedownload proceeds:
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 canbring up the Main view and study all TTD logs.See TTD Node Configuration Aspect on page 76.
Figure 51. Downloading new TTD Log Definitions
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 96/280
Section 6 Quick List Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 97/280
3BSE030340R4101 97
Quick List User Interface
Figure 52 shows the Quick List configuration view. Detailed information about thedifferent parts and how to configure and operate the Quick List, is described in thefollowing sections.
Figure 52. Configuration View - Quick List
Configure the Quick List Section 6 Quick List Configuration
Configure the Quick List
The Quick List aspect can be pre-configured with search criteria. For example, oneaspect 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 isopened and the result is presented in the Quick list main view.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 98/280
98 3BSE030340R4101
How to Configure the Quick List Aspect
The Quick List aspect is created and handled as other aspects in the
Operator Workplace.
The following tutorial will guide you through the different steps in configuring theQuick List.
If the Quick List aspect is created on an object in a structure other than theControl Stucture, you must add a Quick List Data Source aspect to the object. Inthe configuration view of the Quick List Data Source aspect you choose provider,see Figure 53.
Figure 53. Quick List Data Source Aspect
Section 6 Quick List Configuration Configure the Quick List
1. In the Plant Explorer, create a new Quick List aspect on an object. The mainview with an empty list is shown as in Figure 54.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 99/280
3BSE030340R4101 99
2. As this aspect is new it does not hold any configuration data (i.e no searchcriteria 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.
Figure 54. Quick List Main View
Configure the Quick List Section 6 Quick List Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 100/280
100 3BSE030340R4101
4. Now, configure a simple search criteria. Suppose that you want to know whichDigital 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 withgreen color (Red colored are not common, and are not possible to select in theProperties area). See Figure 56.
7. Click on the property for error state (ERR) in the Properties area and the textERR 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 theProperty2 text field (press CR).
Figure 55. Quick List Config View
Section 6 Quick List Configuration Configure the Quick List
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.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 101/280
3BSE030340R4101 101
Figure 56. Quick List Configuration example.
If you use the property ‘’STATUS_DO /’’ you have to write a value that is ahexadecimal. For example: ‘’/H:5’’
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 102/280
Section 6 Quick List Configuration Configuration Examples
Configuration Examples
Example 1
List all Analog Inputs (AI) of process section 2 in the nodes 5,6, and 7, which hasthe string “Temp” in position 7-10 in the name and are in a state of alarm and haveth l i bl k d
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 103/280
3BSE030340R4101 103
the alarm processing blocked.
1. Click the check box for the AI in the Object Type List. The properties of AIwhich 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 questionmarks 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 ofalarm, the flag DISTURB (disturbance) is set high. Specify the conditions youwant 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. Enterthis property in the Property2 text field by clicking on the label AL_BLK inthe property list and add ‘1’ to the Property2 text field.
7. Now all the necessary parameters of the list are defined and the search criteriacan now be activated. Click the Apply button to save the configuration data.
Configuration Examples Section 6 Quick List Configuration
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 havebeen 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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 104/280
104 3BSE030340R4101
A checked box signifies an active parameter. The accessible properties ofMOTCON appear in the list of available properties. Select the Node1 text fieldand 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 fieldand enter the value 9.
3. Move the cursor to the Section1 text field and enter the value ‘3’. Move thecursor to the Class1 text field and enter the value 1. Move the cursor to theClass2 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 theseindications.
5. See the description of MOTCON in AdvaCommand User Interface ReferenceManual. The block item is defined as Property 1. In this way, an OR conditionis created.On the other hand, if the three indications IND2_01, IND2_02 and IND2_03were 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 isto have the value H’E, which corresponds to the three indications. Specify theproperty like this.
– Move the cursor to the list with available properties and click on the label‘IND2_MOTCON’. The text ‘IND2_MOTCON //’ will be copied to thefirst free text field for Property 1 - Property 4 and the input focus will bemoved to the actual text field. Add the value HE to the text fields.
6. 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 LOCALmode, two message lines appear on the list. This type of block itemcondition generates a message line for every high bit thatcorresponds to the actual value in the data base.
Section 7 National Language SupportConfiguration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 105/280
3BSE030340R4101 105
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 inWindows. The target language must also be set in Regional Settings in WindowsExplorer and in Visual Basics.
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 Industrial IT 800xA System, Operator Workplace Configuration.
Alarm and Event Texts
Alarm and Event texts are translated in the controller according to Advant MasterNational Language Support. Languages that can be used are English, German andSwedish.
The figure below (Figure 58), displays how to select language.
Application engineering can be performed directly in the local language, but theresulting application data will not be reusable in other languages. To ensure that itis possible to translate the application data, all engineering shall be made with
Regional Options in Windows set to English (United States).
Select language before starting the translation. Otherwise, the text will be lost.
Section 7 National Language Support Configuration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 106/280
106 3BSE030340R4101
Character Conversion
When connecting to controllers using national characters this setting will convertthe 7-bit representation to the correct 8-bit. The conversion applies to objectproperties: NAME, DESCRIPTION and UNIT.
• English (No Conversion): Characters ‘[‘,’\’,’]’,’{‘,’|’,’}’,’~’ will not bechanged.
• Swedish: Characters ‘[‘,’\’,’]’,’{‘,’|’,’}’,’~’ areconverted to‘Ä’,’Ö’,’Å’,’ä’,’ö’,’å’,’~’.
Figure 58. Select Language in Advant Master NLS
Section 7 National Language Support Configuration
• German: Characters ‘[‘,’\’,’]’,’{‘,’|’,’}’,’~’ are converted to‘Ä’,’Ö’,’Ü’,’ä’,’ö’,’ü’,‘β’.
The change of character conversion will also load a number of predefined files toEVENT_TREAT, TEXT, CLOCK_SYNCH etc.
It is strongly recommended that this setting is done before commencing theengineering and then not be changed.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 107/280
3BSE030340R4101 107
Event Treat According to NLS
Process Alarm and Process Event texts
A process alarm or process event is presented by its name, description, property textand event text in a list. The translation to local language of the property and eventtext are described in this section.
The property and event texts can be either user defined or standard. The userdefined property and event texts are stored in database elements of typeEVENT_TREAT. The standard property and event texts are store in the databaseconcept 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 inEVENT8 - EVENT14, EVENT16 - EVENT18.
The property and event text for the user defined event handling are stored inEVENT20 - 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.
Since the Online Builder is not an option to the Operator Workplace, you needthe Engineering Studio to do the translation.
Section 7 National Language Support Configuration
4. 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 IndustrialIT\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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 108/280
108 3BSE030340R4101
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 namedEVENTxx.BA.
5. Edit the source code files by opening the file in the text editor, choose File >
Open...
6. Save the changes and exit from the text editor by selecting File > Save > Exit
Figure 59. Event Text
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 109/280
Section 7 National Language Support Configuration
Below is an extract of the dump. The dump starts with some headlines which mustnot 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 notbe changed. 5 is the number of characters in the property or event text. Thereafterfollows the text to be translated. The text and the number of characters can bechanged using the text editor.
• ][ A 201
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 110/280
110 3BSE030340R4101
• ][ A 201SRCE:STANDARD.LDMidas Data Base Logical DumpCopyright ASEA--------------58 Selective dump of logfile 31 created 2002-04-18 14:07:2040 Dump of standard property and event text5 \*+-/0 31 0 FFFFFFFF 50 2 0 20 0 FFFFFFFF 1
0 3 0 20 0 FFFFFFFF 10 5 0 20 0 TFFFFFFF 10 6 0 40 0 FFFFFFFF 10 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
Section 7 National Language Support Configuration
][ 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 notlonger 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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 111/280
3BSE030340R4101 111
• 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.
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
Figure 60. Standard Text
Section 7 National Language Support Configuration
Answer the questions as follows:
– 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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 112/280
112 3BSE030340R4101
ENTER RECORD SELECT LOAD (Y/N/ /Q) N
– LOAD START AT RECORD (<recnr>//Q) = 2
– Try again. (Y/N/Q) = N
7. Take a backup of the RTA Board by clicking the RTA Board Backup button.
System Alarm texts
An event in the System Alarm List has the following layout:
The text row includes the following:
• 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.
Figure 61. System Alarm List
Section 7 National Language Support Configuration
Translation to a national language must be made by using the database source codefacilities for dumping and loading the TEXT concept against the Windowsenvironment.
Make a logical dump as follows:
1. Open the RTA Board Configuration window.
2. Go to the Control Structure > Network > Node and RTA Board object.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 113/280
3BSE030340R4101 113
3. Select the RTA Board Control aspect and the RTA Board Configuration tab.
4. Click on the RTA Board Config button.5. Enter in RTA Board Configuration window
– DUDB SRCE:TEXT for example DUDB SRCE:TEXTENG. Max lengthof 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
Section 7 National Language Support Configuration
The dump is stored in directory \Program Files\ABB IndustrialIT\AC400CI\AdvantBase\Data\RTA\Nodes\SRCE. The created file name is <filename>.LD.
Below is an extract of the dump. The dump starts with some headlines which mustnot 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@
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 114/280
114 3BSE030340R4101
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/OST@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 numberof characters and the pointer in bold can be changed using the text editor.
][ A 201SRCE:TEXT.LDMidas Data Base Logical Dump
Copyright ASEA--------------58 Selective dump of logfile 31 created 2002-04-18 14:07:2012 Dump of LF315 \*+-/0 31 0 FFFFFFFF 30 3 0 20 0 FFFFFFFF 1
0 5 0 20 0 TFFFFFFF 10 6 0 40 0 FFFFFFFF 1
][ 280 48 10 0 0 0 0 0 0 12 29 0 4948 PROC I/O ST@3A2@-board errorNet @1A3@ Node @2A3@][ 281 50 10 0 0 0 0 0 0 12 31 0 51
Section 7 National Language Support Configuration
50 PROC I/O ST@3A2@-board workingNet @1A3@ Node @2A3@][ 282 59 10 0 0 0 0 0 0 11 40 0 6059 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 5958 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@
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 115/280
3BSE030340R4101 115
................and so on...........................
There may be parameters in the text. The parameter is replaced in runtime by itsactual 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 theSystem Part Description text. Corresponding values for 16 bit characters (forexample chinese) are 6 characters for the System Part Text and 14 characters for theSystem Part Description text.
Section 7 National Language Support Configuration
6. Edit the dump file by opening the file in the text editor, choose File > Open...
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 116/280
116 3BSE030340R4101
7. Save the changes and exit from the text editor by selecting File > Save > Exit
Load the dump file.
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.
4. Select the RTA Board Configuration tab and click on the RTA Board Config
button.
5. Enter in RTA Board Configuration window
– LODB SRCE:XXX where XXX is the name of the dump.
Figure 62. System Alarm Text
Section 7 National Language Support Configuration
Answer the questions as follows:
– TARGET IS NOT IN CONFIGURATION MODE! PROCEED? (Y/N/Q)= Y
– LOAD MODE (L/L*/I/I*/P/P*/S/S*/Q) = I
Max number of characters for the name is 8 and the characters must be capitals.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 117/280
3BSE030340R4101 117
– 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
6. Take a backup of the RTA Board by clicking the RTA Board Backup button.
Operator Messages
Use the following steps to translate the Advant Master Operator Messages
1. Go to the Library Structure.
Section 7 National Language Support Configuration
2. Open System Messages > Messages, see the figure below.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 118/280
118 3BSE030340R4101
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 Industrial IT 800xA, System, Operator Workplace Configuration.
Figure 63. Operator Messages
Section 8 Data transfer via OPC DA
800xA for Advant Master supports data subscriptions and write operations towards
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 119/280
3BSE030340R4101 119
800xA for Advant Master supports data subscriptions and write operations towardsprocess objects via the OPC DA interface in 800xA OPC Client connection.
However the following AC 400 and MP200/1 controller limitations andrecommendations need to be considered to avoid system overload. For detailedinformation about the 800xA OPC DA interface see Industrial IT 800xA, System
Configuration.
OPC Read Operations
Cyclic subscriptions are only supported on process objects for the subscriptiontimes 1, 3 and 9 seconds and not for all properties. If other rates or properties areselected the RTA board will emulate this by sending repeated demand requests tothe controller which causes much higher load than the cyclic subscriptions. Forperformance reasons faster sample times than 9 seconds should be avoided whenpossible. The properties that support cyclic subscriptions are listed in Appendix F,OPC Properties.
OPC Write Operations Section 8 Data transfer via OPC DA
An overview of the different subscription types supported by the AC 400 andMP200/1 controllers are described below:
• Demand. One data request from the RTA board results in one reply from thecontroller.
• Cyclic. One data request from the RTA board results in a continuous stream ofcyclic updates from the controller. Supported cyclic rates: 1, 3 and 9 seconds.
• Event driven. One data request from the RTA board results in a continuousf d i d f h ll
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 120/280
120 3BSE030340R4101
stream of event driven updates from the controller.
OPC Write Operations
It is only supported to perform OPC write operations towards DAT objects. Thereare no hard limitations on the number of write operations that can be executed.
Section 9 Display Converter
In order to facilitate a smooth and easy migration from AdvaCommand (both Unix
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 121/280
3BSE030340R4101 121
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 fromAdvaCommand of the IndustrialIT products. It is installed together with the 800xAfor Advant Master Extension. The user interface of the display conversion tool isaccessed from theAdd-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 ActiveXControls. All standard display elements in AdvaCommand are made as ActiveXbased graphic elements in System 800xA. A map file, which maps theAdvaCommand standard display element to an ActiveX based graphic element, isavailable as part of the conversion tool. User defined display elements inAdvaCommand need to be created as ActiveX Controls in System 800xA andentered into the map file. This is done once. This map file is re-used for allconversions 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 showdynamic 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 notdo that but answer Yes on the question, about saving the display, you will get an
application error.
Getting Started Section 9 Display Converter
Getting Started
This appendix describes the major steps in display conversion:
1. Create new graphic elements to replace your own AdvaCommand graphicelements.
2. Customize your configuration files.
3. Edit your converted graphic display.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 122/280
122 3BSE030340R4101
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 theprocess 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 inthe old system, may require that they are aspects of objects with similarfunctionality 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 theAdd-In Manager, which is accessible from the Add-Ins menu. To add or remove theDisplay Converter:
1. From the Graphic Builder’s Add-Ins menu, select Add-In Manager.
Section 9 Display Converter Create New Graphic Elements to Replace the Previously Created
2. Select the Display Converter, mark or un-mark the Loaded/Unloaded andLoad 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 CreatedAdvaCommand Graphic Elements
Before you convert your AdvaCommand graphic display, you may want to create anew graphic element or process dialog to replace your own AdvaCommand graphic
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 123/280
3BSE030340R4101 123
g p p g p y g pelement. Once you have created the graphic elements, you add and map those to
the graphic elements configuration file. Then you can convert the appropriateAdvaCommand graphic element to the new one.
Refer to the Industrial IT 800xA, Engineering, Graphics for information on how tocreate 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 pairbased. 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 cansubstitute the default settings by adding your own configuration files (could bestored in any directory). You can restore the original configuration file by removingthe 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 isrecommended that you decide on one set of configuration files to use throughoutyour system to preserve consistency.
Customize your Configuration Files Section 9 Display Converter
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 colorconversions.
{
OSCOLOR: {0}
RED: {0}
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 124/280
124 3BSE030340R4101
GREEN: {0}
BLUE: {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 onthe 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 colorname of Operator Workplace. The logical color specification will overrule the RGBspecification.
The Colors.cnf file installed with the Display Converter contain mapping of thestandard OS palette (colordef.dat).
Fonts.cnf
In the AdvaCommand fonts are specified with a short font specification consistingof two letters FA-FN and two digits 10-60 in step of 10. These font specificationsare connected to real X fonts through a definition file.
Section 9 Display Converter Customize your Configuration Files
The font definition file is placed in the directory:
/products/data/standard/OS/config/
and have the name fontdef.dat.
-adobe-courier-bold-r-normal--11-80-100-100-p-60-iso8859-1
foundry weight set width points
verticalresolution average width
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 125/280
3BSE030340R4101 125
The first line specifies that font number 11 shall be a courier font.The fontspecification is the standard X font specification described above. The second line isused by process graphics and the display builder. FM says that this is font FM, 10:12specifies 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 acomma separated list of fonts. The specification should be on one line, or as in theexample below that uses a line continuation character as the last character on theline.
The example above specifies two fonts for the default raster 11 font inSherrill-Lubinski, one used for languages using iso8859-1 encoding and one usedfor languages using iso8859-5 encoding.
The Fonts.cnf configuration file contains mapping of font names and numbers intoWindows Font info. Like the color.cnf the file contain record entries, each entrydescribing 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 sixdifferent 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 Advantstation is mapped into the font.cnf file.
font family slant pixels horizontal
resolutionspacing character set
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 */
Customize your Configuration Files Section 9 Display Converter
This example shows a snip of code from the fontdef.dat file. The code describesthe Courier face name where the style is bold. The X equivalent is (not samefacename/style):
The mapping in the font.cnf file will look like:..
..
{
TYPE: {FONT}
FONT: {FA10}
{1}
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 126/280
126 3BSE030340R4101
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 ofthe standard OS fonts.
Changing the default fonts example:
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 tothe new one.
Section 9 Display Converter Customize your Configuration Files
If your system does not have the colors or fonts you used to convert theAdvant Master graphic display, the conversion tool selects the closest matchingcolor 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 toOperator Workplace. Following is an example of the mapping for DATPD01.{
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 127/280
3BSE030340R4101 127
{
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: {}
Customize your Configuration Files Section 9 Display Converter
OUTPUTTO: {ctl}
}
SIMPLE: {
FROM:{Font}TO:{Font}
TYPE: {Font}
DEFAULT: {}
OUTPUTTO: {ctl}
}
SIMPLE: {
FROM {C diti C l }
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 128/280
128 3BSE030340R4101
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 displayelement. Example on how to get specification for your new graphic element:
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.
Section 9 Display Converter 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. Relationshipbetween VB units and SL units are XVB=XSL*144.11255 andYVB=YSL*142.3321.
Convert and Import your AdvaCommand Graphic Displays
1. Select object in Plant Explorer.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 129/280
3BSE030340R4101 129
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 Builder’s 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 (SourceDirectory).
Convert and Import your AdvaCommand Graphic Displays Section 9 Display Converter
7. All conversion errors such as unrecognized graphic primitive, graphic element,faceplate, graphic link or syntax error will be displayed in a dialog box andlisted in a text file.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 130/280
130 3BSE030340R4101
The layout of the Display Converter is shown in Figure 64. The dialog consists of:
• 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 theBrowse push-button next to the edit field will popup a standard File Opendialog (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.
Figure 64. Display Conversion Dialog
Section 9 Display Converter Convert and Import your AdvaCommand Graphic Displays
• 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/Informationmessages in the log is also set.
• Convert
Activating the Convert button will convert the selected displays and place theconverted files in the destination directory. The log field (and the log file ifenabled) will show the status of the conversion
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 131/280
3BSE030340R4101 131
Figure 65. Display Open Dialog
Edit your Converted Graphic Display Section 9 Display Converter
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 132/280
132 3BSE030340R4101
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 Diror C:\My MOD Configuration Dir.
• Logfile
The Logfile specifies the filename and path of the logfile. Activating theBrowse 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 GraphicsDir\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. Manipulate graphic elements.
Figure 66. Config dialog
Section 9 Display Converter 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 Industrial
IT
800xA, Engineering, Graphics.
4. The display conversion is proportionate to a graphic display without Dynamicfunction keys. If you have included Dynamic function keys in the conversionyou need to resize the graphic display in Y position and move the Dynamicfunction keys to the bottom.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 133/280
3BSE030340R4101 133
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 OperatorWorkplace native graphic aspect. You use the same tools to test, save, and deploythe graphic display as if you had built it directly in the Graphics Builder - refer tothe Industrial IT 800xA, Engineering, Graphics.
Figure 67. Graphics Builder
Limitations of the Display Converter Section 9 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:• Graphic display or external application references in Dynamic function keys
may not be fully resolved. The graphic display or external application namewill be converted from the graphic link but the object that owns that aspect maybe unknown or nonexistent.
• Three dimensional graphic primitives not using static graphic element will be
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 134/280
134 3BSE030340R4101
converted into Graphics Builder maintaining the multiple spline compositionof the graphic primitives. In the System the same effect can be accomplishedby using a simple three dimensional shading to the whole primitive (andremoving the multiple splines.) This will result in improved performance. Butthe user will have to do this manually. It is strongly recommended that you dothis optimization.
Section 10 System Administration
Hardware Indicators
The RTA Board has no hardware indicators on the board.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 135/280
3BSE030340R4101 135
System Diagnostics
The AC 400 Controllers produce a number of event and alarm messages to informyou about errors concerning the Advant System system and not with the processitself.
You can find a System Alarm List aspect on the network. The System Alarm Listaspect 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 withinthe 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 resultfrom the control system internal supervision programs. The System Status isavailable for the Network, the Operator Workplace node, and the Controller node.
System Diagnostics Section 10 System Administration
System Status Viewer
The System Status Viewer shows status of different parts of the system. Systemstatus information can be available for both software processes and hardwaredevices. The System Status Viewer aspect can be located on different levels in allstructures. All status information in the System Status Viewer is updateddynamically when a change of status occurs.
Find Child ErrorShow Details Refresh Alarm and Events
Help ButtonView Mode Button
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 136/280
136 3BSE030340R4101
A description of the different tools and columns in the System Status Vieweroverview, are described below.
Figure 68. System Status Viewer - an Overview
If you have several controllers it may cause a delay of the data update.
Next Error
Previous Error
Propagated
Show all Errors
Section 10 System Administration System Diagnostics
Tools in the Application Bar
Use the Next and Previous arrows in the upper left part of the figure, to get theprevious or next status.
To find out where the source of the status is, click the Find Child Error button, seeFigure 68. It is possible to make all objects with errors or warnings visible byclicking the Show all Errors button.
By default the Status Viewer displays the objects in a tree view. In the list view youcan sort the objects by different columns. To change between list view and tree view,select the View Mode button.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 137/280
3BSE030340R4101 137
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. Objectsthat do not provide system status information will not have an icon in the column.There are three possible status results: OK, Warning or Error.
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 bothError and Warning, then Error will be shown as propagated status.
Figure 69. The Status column
System Diagnostics Section 10 System Administration
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 foreach object.
An x in the Details column indicates that there is more detailed informationavailable 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
h S S Vi
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 138/280
138 3BSE030340R4101
the System Status Viewer aspect.
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.
Figure 70. System Status for the Network
Section 10 System Administration System Diagnostics
System Status - Operator Workplace Node
The System Status for the Operator Workplace node itself is presented if you selectthe Operator Workplace node, and the System Status View aspect in the ControlStructure. See Figure 71.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 139/280
3BSE030340R4101 139
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 errorcan be found, such as disk full or similar, the service error should be reported to thesupplier, see Fault Finding and User Repair on page 135.
Figure 71. System Status View for Operator Workplace Node
System Diagnostics Section 10 System Administration
System Status - MB 300 Control Network
The System Status for a MB 300 control network is presented if you select theControl Structure, the MB 300 Network Board object , and the System Status Vieweraspect.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 140/280
140 3BSE030340R4101
When an RTA Board object is marked with a cross in the Details column, double-click in the column to show the Advant Master Connectivity Server Communication
Display.
Figure 72. System Status View for MB 300 Network Object
The display is also shown in the Advant Master CS Communication aspect of theMB300 RTA board object in the Control Structure.
Section 10 System Administration System Diagnostics
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 141/280
3BSE030340R4101 141
The display lists the communication status for each node the RTA Board cancommunicate with. The columns are:
• Node. It shows the node number.
• Primary and Secondary. They show the node communication status, and arefurther described in Table 6.
• Name. It shows the node name. The name originates from the node object inthe 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.
Figure 73. Advant Master Connectivity Server Communication Display
For single network - only one column is shown.
System Diagnostics Section 10 System Administration
Table 6. Node Connectivity Status
Primary
Column
Secondary
ColumnMB 300 Description
Communication is OK.
Communication error for an redundant MB300network.
Communication error for an redundant MB300network.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 142/280
142 3BSE030340R4101
In the top-right corner of the display, the status for the RTA Board Location isshown, see Figure 74.
e
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
Figure 74. Status Indication
Section 10 System Administration System Diagnostics
An error indicates that there is no communication with the RTA board, while awarning indicates a problem with the communication. If the status indicationshows 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.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 143/280
3BSE030340R4101 143
2. In the displayed aspect tab, click Stop and wait for the RTA Board to stop(check status).
3. Click on the Start button.
Figure 75. Context menu
System Diagnostics Section 10 System Administration
System Status - Controller Node
The System Status for a Controller node is presented if you select the ControlStructure, the Controller node, and the System Status Viewer aspect. In the examplebelow (Figure 76), the AC 450 Controller (Node 4) has a problem with an Analoginput board no. 2.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 144/280
144 3BSE030340R4101
The next step in your fault finding is to study the system alarm list for the failingController, see System Alarms on page 150.
When an object is marked with a cross in the Details column, double-click in thecolumn, and then select Local Devices, to show the Local Devices graphic displayfor the controller node.
Figure 76. System Status View for Controller node
This function isn’t supported for MP 200/1 controllers.
Section 10 System Administration System Diagnostics
10
2
1
15
6
14
117 8 9
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 145/280
3BSE030340R4101 145
Figure 77. AC 400 Local Devices Display
3
17
16
1312
5
4
5
System Diagnostics Section 10 System Administration
No DescriptionDefault
PresentationCondition
1 Controller powersupply header
Grey
1.1 24V supply indication Green filled OK
Red crossed Error
1.2 24 supply name Grey OK
Red Error
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 146/280
146 3BSE030340R4101
2.1 Regulator indication Green filled OK
Red crossed Error
2.2 Regulator name Grey OK
Red Error
3.1 Battery voltageindication
Green filled OK
Red crossed Error
3.2 Battery voltage name Grey OK
Red Error
3.3 Battery backupsupply indication
Green filled OK
Red crossed Error
3.4 Battery backupsupply name
Grey OK
Red Error
4 I/O power supplyheader
Grey
4.1 I/O 24V supplyindication
Green filled OK
Section 10 System Administration System Diagnostics
Red crossed Error4.2 I/O 24V supply name Grey OK
Red Error
5.1 I/O regulatorindication
Green filled OK
Red crossed Error
5.2 I/O regulator name Grey OK
No DescriptionDefault
PresentationCondition
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 147/280
3BSE030340R4101 147
Red Error
6 Controller header Grey
6.1 Processor moduleindication
Green filled OK
Green empty Standby
Yellow crossed Warning
Red crossed Error
6.2 Processor modulename
Grey OK
Grey Standby
Grey Warning
Red Error
7.1 Program cardindication
Green filled OK
Yellow crossed Warning
Red crossed Error
7.2 Program card name Grey OK
System Diagnostics Section 10 System Administration
Grey WarningRed Error
8.1 Free pgm card &M500 indication
Green filled OK
Yellow crossed Warning
Red crossed Error
8.2 Free pgm card & Grey OK
No DescriptionDefault
PresentationCondition
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 148/280
148 3BSE030340R4101
M500 name
Grey Warning
Red Error
9 Subrack fan header Grey
9.1 Fan indication Green filled OK
Red crossed Error
9.2 Fan name Grey OK
Red Error
10.1 I/O fan indication Green filled OK
Red crossed Error
I/O fan name Grey OK
Red Error
11 S100 I/O busextension header
Grey
11.1 S100 I/O busextension indication
Green filled OK
Red crossed Error
Section 10 System Administration System Diagnostics
11.2 S100 I/O busextension name Grey OK
Red Error
12 Additional header Grey
12.1 User definedsupervision
indication
Green filled OK
Red crossed Error
No DescriptionDefault
PresentationCondition
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 149/280
3BSE030340R4101 149
12.2 User definedsupervision name
Grey OK
Red Error
13.1 PC triggered
supervisionindication
Green filled OK
Red crossed Error
13.2 PC triggeredsupervision name
Grey OK
Red crossed Error
14 Terminal header Grey
14.1 Terminal indication Green filled OK
Red crossed Error
14.2 Terminal name Grey OK
Red Error
15 Printer header Grey
15.1 Printer indication Green filled OK
Red crossed Error
System Alarms Section 10 System Administration
15.2 Printer name Grey OKRed Error
16 Externalcommunication
Grey
16.1 XCom indication Green filled OK
Red crossed Error
16.2 XCom name Grey OK
No DescriptionDefault
PresentationCondition
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 150/280
150 3BSE030340R4101
System Alarms
The System Alarms provide valuable information for fault tracing. Default you havea System Alarm aspect on the Network object and on the Controller object(s) inyour Control Structure. You should use them as they will give you an overview listfor all the system alarms in your system. To create your own System Alarm aspects,
follow the instructions below: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 Defaultaspect MB 300 System Alarms.
4. Save.
Red Error
17.1 RSCom indication Green filled OK
Red crossed Error
17.2 RSCom Grey OK
Section 10 System Administration System Alarms
An example of a typical System Alarm List is presented in Figure 78.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 151/280
3BSE030340R4101 151
When you have located the Controller where the problem resides, bring up theSystem Alarm List on that Controller object (Control Structure). This gives you adedicated system alarm list for that Controller helping you to close in on theproblem. The System Alarms are in plain text and should help you to continue with
your fault tracing.
Figure 78. System Alarm List for the Complete Network
Backup/Restore Procedures Section 10 System Administration
Backup/Restore Procedures
General backup procedures are described in Industrial IT 800xA, System,
Administration & Security.
Backup
Backup the following as described below:
• RTA Board Configuration
• Network Configuration Settings
• Time Server Setting
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 152/280
152 3BSE030340R4101
RTA Board Configuration
You use the RTA Board Control aspect to save changes to the configuration of theRTA board. Use Plant Explorer to locate the Control Structure, the OperatorWorkplace 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 toconfiguration 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. Ifthere are no errors, the new configuration has been saved (and will automatically beloaded to the RTA Board at startup).
The RTA board configuration files are locally stored on the computer with the RTAboard. If you want to export the files for backup or for importing to another machinewith an RTA board, you can do as follows:¨
Path: \Program Files\ABB Industrial IT\Operate IT\AC 400 Connect\AdvantBase\Data\RTA\Init
Please observe that if you have a backup of a whole Control Structure and wantto import it, you have to Add a Provider under the Adapter Data SourceDefinition Structure aspect, in the Control Structure.
Section 10 System Administration Restore
Save these three files on a safe location, such as a CD or other server.
• \DATHR1.CD
• \DATHR2.CD• \DATHR3.CD
Network Configuration Settings
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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 153/280
3BSE030340R4101 153
2. Select the RTA Board Control aspect, and then the Network/NodeConfiguration tab.
3. Relevant settings are the values of:
– Network Number 1
– Network Number 2– Node Number
4. Write down these settings and store the information on a safe location, such asa CD or other server.
Time Server Setting
Backup the time server setting by writing the setting down and storing thisinformation on a safe location, such as a CD or other server.
Relevant setting is the value of the registry parameter REVERSED_SYNC_MODEdescribed in 800xA for Advant Master Connectivity server as Clock Master on page31. The parameter has a value of either 0 or 1.
RestoreWhen you make a restore, you first have to make a general 800xA restore asdescribed in Industrial IT 800xA, System, Administration & Security.
Restore Section 10 System Administration
RTA Board Configuration
To restore the configuration for an RTA Board, copy the three files you saved duringbackup from the safe location to the folder \..\Program Files\ABB Industrial
IT\Operate IT\AC 400 Connect\ AdvantBase\Data\RTA\Init. (If prompted, answerYes to replace existing files).
Network Configuration SettingsTo restore the network configuration settings, setup network and node numbers
sing the settings o rote do n d ring the back p Ho to set p net ork and
Before you restore these three files you have to make sure that the system towhich you restore to, is running on the same “Character conversion language” asthe machine from where you took the dump.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 154/280
154 3BSE030340R4101
using the settings you wrote down during the backup. How to setup network andnode numbers is described in Setup Network and Node Number on page 34.
Time Server Settings
To restore the time server setting, change the registry parameterREVERSED_SYNC_MODE to the value you wrote down during the backup. Howto change the parameter is described in 800xA for Advant Master Connectivityserver 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 communicationwith the RTA Board) and the RTA Board status.
Section 10 System Administration Restore
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 155/280
3BSE030340R4101 155
Figure 79. RTA Configuration
Restore Section 10 System Administration
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 156/280
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 OperatorWorkplaces and functionality you can study the alarm and event information invarious formats The presentation of an Alarm or Event generated in
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 157/280
3BSE030340R4101 157
various formats. The presentation of an Alarm or Event generated inan AC 400 Controller is made according to the specified event treatment.
Figure 80. Alarm and event handling
MOTOR 2Conveyor 2Control mode AControl status TOInterlocking status..... .
Ev_Tr 1 EVENT10
Ev_Tr 2 EVENT12
Event Treat
Process
Object
EVENT 10
Audible alarm 1Alarm priority 2Alarm To Block NOAlarm Fr Block YES
.
.Textcomb 5
or IMS object
Operator IT Workplace
Controller
....
Appendix A Event Treat Elements
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 isdescribed.
Each Process and System object contains at least one pointer to the Event Treat database. 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.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 158/280
158 3BSE030340R4101
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).
Appendix A Event Treat Elements The Event Treat Database Element
The Event Treat Database Element
The contents of the Event Treat data base, and ways to vary the event handling, aredescribed below:
12345
EVENT20
Event Treat(25.20)
04YESYESNO
21
4
5 3
AUDIBLEAL PRIOAL TOBLKAL FRBLKPERSISTB
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 159/280
3BSE030340R4101 159
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).
Figure 81. Data Base Element for Event Handling
S2
678
NONO0
S3
67
TEXT TOBTEXT FRBTEXTCOMB
Event Texts
Property Texts
The Event Treat Database Element Appendix A Event Treat Elements
The properties in the EVENT element are described below:
AUDIBLE
AUDIBLE makes it possible for you to activate an audible signal on the OperatorWorkplace Server. The condition for an audible alarm is that:
• you have defined an audible alarm for that priority (see the configuration ofpriority 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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 160/280
160 3BSE030340R4101
Alarm Priority defines the Alarm priority in the presentation. Read the Industrial IT
800xA, System, Operator Workplace Configuration.for information about how toconfigure text color and font, sound effects etc. The priority you define in the EventTreat elements are converted to a corresponding OPC Severity according to the
following:
Table 8. Mapping Event Treatment Alarm Priority to OPC Severity
Priority OPC Severity
1 875
2 750
3 625
4 500
5 375
6 250
7 125
Appendix A Event Treat Elements The Event Treat Database Element
AL_TOBLK - Alarm To Block
Blocks alarm handling of a supervised alarm signal/flag when it makes a 0 -> 1transition. 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 -> 0transition. Since most alarm signals/flags are active high, and since alarm handlingon return to normal makes little sense, AL_FRBLK should normally be set = Y
(Yes).
PERSISTB - Persistent Alarm Block
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 161/280
3BSE030340R4101 161
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 persistentalarms from the Alarm List after acknowledgment, even if the alarm situationpersists. 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/eventchanges from 0 ->1.
TEXT_FRBLK - Text From Block
Flag that blocks generation of text in lists and printouts when the alarm/eventchanges from 1 -> 0.
The Event Treat Database Element Appendix A Event Treat Elements
TEXTCOMB - Text Combination code
Integer to select if standard or User defined property text and event text shall beused.
Property text:8 characters
Event text + Step no:8+3 characters
Value + unit:
11 characters
(exceptTEXTCOMB=16and 17)
Event text:11 characters
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 162/280
162 3BSE030340R4101
Figure 82. Maximum number of characters for the property and event texts
Appendix A Event Treat Elements The Event Treat Database Element
Table 9. Formats for Property and Event Texts
TEXT COMBination
codeProperty text Event text
0 Standard Standard
1 User defined
2 Standard Value + unit
3 Standard User defined
4 User defined Standard
5 U d fi d U d fi d
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 163/280
3BSE030340R4101 163
5 User defined User defined
16 User defined (1)
(1) Suitable for long property texts (up to 20 characters).
Standard
17 User defined (1) User defined
18 (2)
(2) Specially adapted for the function unit Sequence (SEQ).
Standard Standard + Step no
19 (2) Standard User defined + Step no
20 (2) User defined Standard + Step no
21 (2) User defined User defined + Step no
24 (3)
(3) Similar to TEXTCOMB=2, but only events caused by a process event will be
entered in the list.
Standard Value + unit
Description can NOT be displayed if long Property texts are used (TEXTCOMB16 and 17).
The Event Treat Database Element Appendix A Event Treat Elements
As mentioned earlier, EVENT20 - EVENT300 can accommodate your own eventtexts as an alternative to the standard texts in the system. You can enter these byexpanding segment S2.
S1
EVENT20
Event Treat(25.20)
9(1)9(2)9(3)
9(4)9(5)9(6)9(7)9(8)9(9)
1
Base part
EV1EV2EV3
EV4EV5EV6EV7EV8EV9
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 164/280
164 3BSE030340R4101
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 userdefined event text that you put the text into the correct line number.
You enter the user defined property texts in EVENT20 - EVENT300 by expandingsegment S3.
Figure 83. Segment S2 in Event Treat
S3
9(9)9(10)9(11)9(12)9(13)9(14)9(15)9(16)
Property Texts
EV9EV10EV11EV12EV13EV14EV15EV16
Appendix A Event Treat Elements The Event Treat Database Element
S1
10(1)10(2)10(3)10(4)10(5)
10(6)10(7)10(8)10(9)10(10)10(11)
PRTE1PRTE2PRTE3PRTE4PRTE5
PRTE6PRTE7PRTE8PRTE9PRTE10PRTE11
EVENT20
Event Treat (25.20)
Base part
Event TextsS2
1
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 165/280
3BSE030340R4101 165
The relative line numbers for 16 property texts. Each text has a maximum length of20 characters.
The coupling between the event and the line number is the same as it is for the eventtexts. For this reason, you must put the different texts on the correct lines.Appendix B, Event Texts, describes the events that generate different line numberpointers.
Figure 84. Segment S3 in Event Treat
TEXTCOMB decides max number of characters to be presented in the lists.
10(11)10(12)10(13)10(14)10(15)10(16)
PRTE11PRTE12PRTE13PRTE14PRTE15PRTE16
The Event Treat Database Element Appendix A Event Treat Elements
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.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 166/280
166 3BSE030340R4101
g p p
EVENT301 Reserved for other applications.
PropertyEVENT
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
AUDIBLE 0 1 0 1 0 1 0 1 0 1 1 0 0 0 0 1 0 1
AL_PRIO 4 2 4 2 4 2 2 2 4 2 2 4 4 4 4 2 3 2
AL_TOBLK Y N Y N Y N N N Y N N Y Y Y N N Y N
AL_FRBLK Y Y Y Y Y Y Y Y Y Y Y Y Y Y N Y Y Y
PERSISTB Y N Y N Y N Y N Y N N Y Y Y N N Y N
TEXT_TOB N N N N N N Y N N N N N N N N N N N
TEXT_FRB N N N N N N Y N N N N N N Y N N N N
TEXTCOMB 0 0 24 24 18 18 0 5 5 5 5 5 5 5 0 5 17 17
Appendix A Event Treat Elements The Event Treat Database Element
Table 11. Recommended Usage of the EVENT Elements
EVENT Number Usage
EVENT1, EVENT2 Are suitable for binary process signals and objects, forexample DI, DO, GENBIN.
EVENT3, EVENT4 Are suitable for analog process signals and objects, forexample 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, RATIOSTNand MANSTN to obtain an unacknowledged alarm indicated
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 167/280
3BSE030340R4101 167
and MANSTN to obtain an unacknowledged alarm indicatedin 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 theAMPL element EVENT in the Controller.
EVENT15 Is specially adapted for the Status List and contains texts forobjects 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).
The Event Treat Database Element Appendix A Event Treat Elements
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 168/280
168 3BSE030340R4101
Appendix B Event Texts
The events defined for the various signal/object types are described in the tablesbelow with the following layout:
2 3 4 5 61
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 169/280
3BSE030340R4101 169
1. Description of the event.
2. Pointer to data base elements in Event Treat. All pointers for each signal/objecttype and the recommended values for standard event handling are described inthe manuals Functional Units, Part 1 to Functional Units, Part 9.
3. Standard property text that describes the event (applies to EVENT1-EVENT18). 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).
Figure 85. Event Text Table Layout
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
Upper limit H2exceeded
LIM_2_TR Limit H2 1 Alarm 1
Appendix B Event Texts
5. Standard event text that describes the state of the event, alarm-normal,blocked-deblocked, etc. If EVENT20-EVENT300 are chosen, you can definethe appropriate text yourself.
6. Line number in the EVENT database elements where your own text should beplaced (applies to EVENT20- EVENT300). The line number is the same forstandard event texts (applies to EVENT1- EVENT18).
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 170/280
170 3BSE030340R4101
Appendix B Event Texts Analog Input Signal AI
Analog Input Signal AI
Events Event Treatpointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
Upper limit H2 exceeded LIM_2_TR Limit H2 1 Alarm 1
Upper limit H2 re-entered LIM_2_TR Limit H2 1 Normal 3
Upper limit H1 exceeded LIM_1_TR Limit H1 1 Alarm 1
Upper limit H1 re-entered LIM_1_TR Limit H1 1 Normal 3
Lower limit L1 exceeded LIM_1_TR Limit L1 2 Alarm 2
Lower limit L1 re-entered LIM_1_TR Limit L1 2 Normal 4
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 171/280
3BSE030340R4101 171
Lower limit L2 exceeded LIM_2_TR Limit L2 2 Alarm 2
Lower limit L2 re-entered LIM_2_TR Limit L2 2 Normal 4
Measured value entered LIM_1_TR Value 4 ValueChg 8
H2-value entered LIM_2_TR Limit H2 1 ValueChg 5
H1-value entered LIM_1_TR Limit H1 1 ValueChg 6
L1-value entered LIM_1_TR Limit L1 2 ValueChg 7
L2-value entered LIM_2_TR Limit L2 2 ValueChg 6
Signal error On ERR_TR Sig.Err 1 Alarm 1
Signal error Off ERR_TR Sig.Err 1 Normal 2
Blocking of event handling ERR_TR Alarm 2 Blocked 3
Deblocking of eventhandling
ERR_TR Alarm 2 Deblocked 4
Blocking of printout ERR_TR Printout 3 Blocked 3
Deblocking of printout ERR_TR Printout 3 Deblocked 4
Analog Output Signal AO Appendix B Event Texts
Analog Output Signal AO
Blocking of DB-update ERR_TR Update 4 Blocked 3
Deblocking of DB-update ERR_TR Update 4 Deblocked 4
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
Manual control mode ERR TR Manual 3 On 5
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 172/280
172 3BSE030340R4101
Manual control mode ERR_TR Manual 3 On 5
Auto control mode ERR_TR Auto 3 On 4
Block output signal againstprocess ERR_TR Output sign 6 Blocked 6
Deblock output signalagainst process
ERR_TR Output sign 6 Deblocked 7
Measured value entered ERR_TR Output sign 2 ValueChg 3
Max limit value entered ERR_TR Max limit 7 ValueChg 3
Min limit value entered ERR_TR Min limit 8 ValueChg 3
Appendix B Event Texts Digital Input Signal DI
Digital Input Signal DI
Events Event Treatpointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
Abnormal position On VALUE_TR Value 1 Alarm 1
Normal position On VALUE_TR Value 1 Normal 2
Abnormal value entered VALUE_TR Value 3 ValueChg 5
Normal value entered VALUE_TR Value 3 ValueChg 6
Signal error On ERR_TR Sig.Err 1 Alarm 1
Signal error Off ERR_TR Sig.Err 1 Normal 2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 173/280
3BSE030340R4101 173
Blocking of event handling ERR_TR Alarm 2 Blocked 3
Deblocking of event handling ERR_TR Alarm 2 Deblocked 4
Blocking of printout ERR_TR Printout 3 Blocked 3
Deblocking of printout ERR_TR Printout 3 Deblocked 4
Blocking of data base update ERR_TR Update 4 Blocked 3
Deblocking of data baseupdate
ERR_TR Update 4 Deblocked 4
Digital Output Signal DO Appendix B Event Texts
Digital Output Signal DO
Events Event Treatpointer
Property text Event text
Standard
text
Line No in
Event
Treat
Standard
text
Line No in
Event
Treat
Order On ERR_TR Output sign 2 On 3
Order Off ERR_TR Output sign 2 Off 4
Manual control mode ERR_TR Manual 3 On 6
Auto control mode ERR_TR Auto 3 Off 5
Blocking of output signalagainst process
ERR_TR Output sign 6 Blocked 7
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 174/280
174 3BSE030340R4101
Sequence SEQ
Deblocking of output signalagainst process
ERR_TR Output sign 6 Deblocked 8
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
Change the step POS_TREAT StepChg 1 ValueChg 1
Step number for jumpentered
POS_TREAT Jumpmode
2 Enter 2
Number of turns entered POS_TREAT Turn no 3 Enter 2
Interval time entered POS_TREAT IntervT 4 Enter 2
Indication Active On IND_TREAT Active 1 On 1
Indication Active Off IND_TREAT Active 1 Off 2
Indication Last Step On IND_TREAT Last Step 2 On 3
Appendix B Event Texts Sequence SEQ
Indication Last Step Off IND_TREAT Last Step 2 Off 4
Indication Auto control modeOn
IND_TREAT Auto Ind 3 On 5
Indication Manual controlmode On
IND_TREAT Man Ind 4 On 5
Indication step Hold On IND_TREAT Hold Ind 5 On 5Indication Unconditionalcontrol mode On
IND_TREAT UncondInd
6 On 5
Indication Next step On IND_TREAT Next 7 On 5
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 175/280
3BSE030340R4101 175
Position error On FAULT_TR Jump error 1 Alarm 1
Position error Off FAULT_TR Jump error 1 Normal 2
Sequence error On FAULT_TR SeqAlarm 3 Alarm 1
Sequence error Off FAULT_TR SeqAlarm 3 Normal 2
Step error On FAULT_TR StepAlarm 4 Alarm 1
Step error Off FAULT_TR StepAlarm 4 Normal 2
Blocking of event handling forposition change
FAULT_TR PosAlarm 7 Blocked 3
Deblocking of event handlingfor position change
FAULT_TR PosAlarm 7 Deblocked 4
Blocking of printout forposition change
FAULT_TR PosPrint 11 Blocked 3
Deblocking of printout forposition change
FAULT_TR PosPrint 11 Deblocked 4
Blocking of event handling fordisturbance
FAULT_TR Disturb 5 Blocked 3
Sequence SEQ Appendix B Event Texts
Deblocking of event handlingfor disturbance
FAULT_TR Disturb 5 Deblocked 4
Blocking of printout fordisturbance
FAULT_TR DistPrint 9 Blocked 3
Deblocking of printout fordisturbance
FAULT_TR DistPrint 9 Deblocked 4
Blocking of event handling fortype error
FAULT_TR TEAlarm 6 Blocked 3
Deblocking of event handlingfor type error
FAULT_TR TEAlarm 6 Deblocked 4
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 176/280
176 3BSE030340R4101
yp
Blocking of printout for typeerror
FAULT_TR TEPrint 10 Blocked 3
Deblocking of printout fortype error
FAULT_TR TEPrint 10 Deblocked 4
Blocking of event handling forind. changes
FAULT_TR IndAlarm 8 Blocked 3
Deblocking of event handlingfor ind. changes
FAULT_TR IndAlarm 8 Deblocked 4
Blocking of printout for ind.changes
FAULT_TR IndPrint 12 Blocked 3
Deblocking of printout for ind.changes
FAULT_TR IndPrint 12 Deblocked 4
Blocking of operator order FAULT_TR OprOrder 13 Blocked 3
Deblocking of operator order FAULT_TR OprOrder 13 Deblocked 4
Appendix B Event Texts Process Controller PIDCON
Process Controller PIDCON
Events Event Treatpointer
Property text Event text
Standard
text
Line No in
Event
Treat
Standard
text
Line No in
Event
Treat
Lower limit L1 for measuredvalue exceeded
H1L1_TR MV<L1 1 <Value>
<Unit>
1
Lower limit L1 for measured
value re-entered
H1L1_TR MV<L1 1 <Value>
<Unit>
2
Upper limit H1 for measuredvalue exceeded
H1L1_TR MV>H1 2 <Value>
<Unit>
1
Upper limit H1 for measured H1L1 TR MV>H1 2 <Value> 2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 177/280
3BSE030340R4101 177
Upper limit H1 for measuredvalue re-entered
H1L1_TR MV>H1 2 <Value>
<Unit>
2
Lower limit (1) for deviationexceeded
H1L1_TR DEV<L 3 <Value><Unit>
1
Lower limit (1) for deviationre-entered
H1L1_TR DEV<L 3 <Value>
<Unit>
2
Upper limit (1) for deviationexceeded
H1L1_TR DEV>H 4 <Value>
<Unit>
1
Upper limit (1) for deviationre-entered
H1L1_TR DEV>H 4 <Value>
<Unit>
2
Lower limit L2 for measuredvalue exceeded
H2L2_TR MV<L2 1 <Value>
<Unit>
1
Lower limit L2 for measuredvalue re-entered
H2L2_TR MV<L2 1 <Value>
<Unit>
2
Upper limit H2 for measuredvalue exceeded
H2L2_TR MV>H2 2 <Value>
<Unit>
1
Process Controller PIDCON Appendix B Event Texts
Upper limit H2 for measuredvalue re-entered
H2L2_TR MV>H2 2 <Value>
<Unit>
2
PC-gate LOCALFL decidescontrol mode
MODE_TR LOCAL !! 1 On 1
PC-gate MANFL decides
control mode
MODE_TR MAN !! 2 On 1
PC-gate AUTOFL decidescontrol mode
MODE_TR AUTO !! 3 On 1
PC-gate E1 decides control MODE_TR E1 !! 4 On 1
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event
Treat
Standard
text
Line No in
Event
Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 178/280
178 3BSE030340R4101
gmode
PC-gate E2 decides control
mode
MODE_TR E2 !! 5 On 1
PC-gate E3 decides controlmode
MODE_TR E3 !! 6 On 1
AI-error On ERR_TR AISign Err 1 Alarm 1
AI-error Off ERR_TR AISign Err 1 Normal 2
Appendix B Event Texts Process Controller PIDCONA
Process Controller PIDCONA
Lower limit L1 for measured
value exceeded
H1L1_TR MV<L1 1 <Value>
<Unit>
1
Lower limit L1 for measuredvalue re-entered
H1L1_TR MV<L1 1 <Value>
<Unit>
2
Upper limit H1 for measuredvalue exceeded
H1L1_TR MV>H1 2 <Value>
<Unit>
1
Upper limit H1 for measuredvalue re-entered
H1L1_TR MV>H1 2 <Value>
<Unit>
2
Lower limit (1) for deviationexceeded
H1L1_TR DEV<L 3 <Value>
<Unit>
1
L li it (1) f d i ti H1L1 TR DEV L 3 V l 2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 179/280
3BSE030340R4101 179
Lower limit (1) for deviationre-entered
H1L1_TR DEV<L 3 <Value>
<Unit>
2
Upper limit (1) for deviationexceeded
H1L1_TR DEV>H 4 <Value>
<Unit>
1
Upper limit (1) for deviationre-entered
H1L1_TR DEV>H 4 <Value>
<Unit>
2
Lower limit L2 for measuredvalue exceeded
H2L2_TR MV<L2 1 <Value>
<Unit>
1
Lower limit L2 for measuredvalue re-entered
H2L2_TR MV<L2 1 <Value>
<Unit>
2
Upper limit H2 for measuredvalue exceeded
H2L2_TR MV>H2 2 <Value>
<Unit>
1
Upper limit H2 for measured
value re-entered
H2L2_TR MV>H2 2 <Value>
<Unit>
2
PC-gate LOCALFL decidescontrol mode
MODE_TR LOCAL !! 1 On 1
Process Controller PIDCONA Appendix B Event Texts
PC-gate MANFL decidescontrol mode
MODE_TR MAN !! 2 On 1
PC-gate AUTOFL decides
control mode
MODE_TR AUTO !! 3 On 1
PC-gate E1 decides controlmode
MODE_TR E1 !! 4 On 1
PC-gate E2 decides controlmode
MODE_TR E2 !! 5 On 1
PC-gate E3 decides control
mode
MODE_TR E3 !! 6 On 1
AI-error On ERR_TR AISign Err 1 Alarm 1
AI-error Off ERR_TR AISign Err 1 Normal 2
Autotuning aborted ADAP_TR AT Abort 1 Alarm 1
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 180/280
180 3BSE030340R4101
g _
Autotuning aborted ADAP_TR AT Abort 1 Normal 2
Autotuning failed ADAP_TR AT Fail 2 Alarm 1
Autotuning failed ADAP_TR AT Fail 2 Normal 2
Autotuning. Question tooperator
ADAP_TR AT Quest 3 Decision 3
Autotuning. Question tooperator answered
ADAP_TR AT Quest 3 Answered 4
There is an invalid samplerate
ADAP_TR TS Fault 4 Alarm 1
There is an invalid samplerate
ADAP_TR TS Fault 4 Normal 2
Adaptation failed ADAP_TR Ad Fail 5 Alarm 1
Adaptation failed ADAP_TR Ad Fail 5 Normal 2
Appendix B Event Texts Manual Station MANSTN
Manual Station MANSTN
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
Lower limit L1 for measuredvalue exceeded
H1L1_TR MV<L1 1 <Value>
<Unit>
1
Lower limit L1 for measuredvalue re-entered
H1L1_TR MV<L1 1 <Value>
<Unit>
2
Upper limit H1 for measuredvalue exceeded
H1L1_TR MV>H1 2 <Value>
<Unit>
1
Upper limit H1 for measuredvalue re-entered
H1L1_TR MV>H1 2 <Value>
<Unit>
2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 181/280
3BSE030340R4101 181
Lower limit L2 for measured
value exceeded
H2L2_TR MV<L2 1 <Value>
<Unit>
1
Lower limit L2 for measuredvalue re-entered
H2L2_TR MV<L2 1 <Value>
<Unit>
2
Upper limit H2 for measuredvalue exceeded
H2L2_TR MV>H2 2 <Value>
<Unit>
1
Upper limit H2 for measuredvalue re-entered
H2L2_TR MV>H2 2 <Value>
<Unit>
2
AI-error On ERR_TR AISign Err 1 Alarm 1
AI-error Off ERR_TR AISign Err 1 Normal 2
Ratio Station RATIOSTN Appendix B Event Texts
Ratio Station RATIOSTN
EventsEvent Treat
pointer
Property text Event text
Standardtext
Line No inEvent Treat
Standardtext
Line No inEvent Treat
Lower limit L1 for measuredvalue exceeded
H1L1_TR MV<L1 1 <Value>
<Unit>
1
Lower limit L1 for measuredvalue re-entered
H1L1_TR MV<L1 1 <Value>
<Unit>
2
Upper limit H1 for measuredvalue exceeded
H1L1_TR MV>H1 2 <Value>
<Unit>
1
Upper limit H1 for measuredvalue re-entered
H1L1_TR MV>H1 2 <Value>
<Unit>
2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 182/280
182 3BSE030340R4101
Lower limit L2 for measured
value exceeded
H2L2_TR MV<L2 1 <Value>
<Unit>
1
Lower limit L2 for measuredvalue re-entered
H2L2_TR MV<L2 1 <Value>
<Unit>
2
Upper limit H2 for measuredvalue exceeded
H2L2_TR MV>H2 2 <Value>
<Unit>
1
Upper limit H2 for measuredvalue re-entered
H2L2_TR MV>H2 2 <Value>
<Unit>
2
AI-error On ERR_TR AISign Err 1 Alarm 1
AI-error Off ERR_TR AISign Err 1 Normal 2
Appendix B Event Texts User Defined Controller GENCON
User Defined Controller GENCON
EventsEvent Treat
pointer
Property text Event text
Standardtext
Line No inEvent Treat
Standardtext
Line No inEvent Treat
AI-error On AL_TR AISign Err 1 Alarm 1
AI-error Off AL_TR AISign Err 1 Normal 2
Limit for control deviationexceeded
AL_TR Big Dev 4 Alarm 1
Limit for control deviation re-entered
AL_TR Big Dev 4 Normal 2
Upper limit H2 for measuredvalue exceeded
AL_TR MV>H2 5 Alarm 1
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 183/280
3BSE030340R4101 183
Upper limit H2 for measuredvalue re-entered
AL_TR MV>H2 5 Normal 2
Upper limit H1 for measuredvalue exceeded
AL_TR MV>H1 6 Alarm 1
Upper limit H1 for measuredvalue re-entered
AL_TR MV>H1 6 Normal 2
Lower limit L1 for measuredvalue exceeded
AL_TR MV<L1 7 Alarm 1
Lower limit L1 for measuredvalue re-entered
AL_TR MV<L1 7 Normal 2
Lower limit L2 for measuredvalue exceeded
AL_TR MV<L2 8 Alarm 1
Lower limit L2 for measuredvalue re-entered
AL_TR MV<L2 8 Normal 2
Max limit for output sign On LIM_TR SpMaxLim 1 On 1
Max limit for output sign Off LIM_TR SpMaxLim 1 Off 2
Min limit for output sign On LIM_TR SpMinLim 2 On 1
User Defined Controller GENCON Appendix B Event Texts
Min limit for output sign Off LIM_TR SpMinLim 2 Off 2
Max limit for output sign On LIM_TR OpMaxLim 3 On 1
Max limit for output sign Off LIM_TR OpMaxLim 3 Off 2
Min limit for output sign On LIM_TR OpMinLim 4 On 1
Min limit for output sign Off LIM_TR OpMinLim 4 Off 2
Op. mode Balance On IND_TR Balance 1 On 1
Op. mode Balance Off IND_TR Balance 1 Off 2
Op. mode Manual Forced On IND_TR ManFrced 2 On 1
Op mode Manual Forced Off IND TR ManFrced 2 Off 2
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 184/280
184 3BSE030340R4101
Op. mode Manual Forced Off IND_TR ManFrced 2 Off 2
Op. mode Manual On IND_TR Manual 3 On 1
Op. mode Manual Off IND_TR Manual 3 Off 2
Op. mode Auto On IND_TR Auto 4 On 1
Op. mode Auto Off IND_TR Auto 4 Off 2
Op. mode E1 On IND_TR E1 5 On 1
Op. mode E1 Off IND_TR E1 5 Off 2
Op. mode E2 On IND_TR E2 6 On 1
Op. mode E2 Off IND_TR E2 6 Off 2
Controller output On IND_TR Controller 9 On 1
Controller output Off IND_TR Controller 9 Off 2
Controller On Binary control IND_TR BinCtrl 10 On 1
Controller Off Binary control IND_TR BinCtrl 10 Off 2
Appendix B Event Texts Binary Object GENBIN
Binary Object GENBIN
EventsEvent Treat
pointer
Property text Event text
Standardtext
Line No inEvent Treat
Standardtext
Line No inEvent Treat
Signal error On AL_TR SignErr 1 Alarm 1
Signal error Off AL_TR SignErr 1 Normal 2
Feedback error On AL_TR FBErr 2 Alarm 1
Feedback error Off AL_TR FBErr 2 Normal 2
Upper limit H2 for measuredvalue exceeded
AL_TR MV>H2 5 Alarm 1
Upper limit H2 for measuredvalue re-entered
AL_TR MV>H2 5 Normal 2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 185/280
3BSE030340R4101 185
Upper limit H1 for measured
value exceeded
AL_TR MV>H1 6 Alarm 1
Upper limit H1 for measuredre-entered
AL_TR MV>H1 6 Normal 2
Lower limit L1 for measuredvalue exceeded
AL_TR MV<L1 7 Alarm 1
Lower limit L1 for measured
value re-entered
AL_TR MV<L1 7 Normal 2
Lower limit L2 for measuredvalue exceeded
AL_TR MV<L2 8 Alarm 1
Lower limit L2 for measuredvalue re-entered
AL_TR MV<L2 8 Normal 2
Op. mode Interlock
INTMODE On
INTL_TR ModeIntl 1 On 1
Op. mode InterlockINTMODE Off
INTL_TR ModeIntl 1 Off 2
Binary Object GENBIN Appendix B Event Texts
Process Interlock INTPROCOn
INTL_TR ProcIntl 2 On 1
Process Interlock INTPROCOff
INTL_TR ProcIntl 2 Off 2
Switchgear InterlockINTSWGR On
INTL_TR SwgrIntl 3 On 1
Switchgear InterlockINTSWGR Off
INTL_TR SwgrIntl 3 Off 2
Emergency Stop InterlockINTEMTP On
INTL_TR EmTrpInt 4 On 1
Emergency Stop Interlock INTL TR EmTrpInt 4 Off 2
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 186/280
186 3BSE030340R4101
Emergency Stop InterlockINTEMTP Off
INTL_TR EmTrpInt 4 Off 2
Op. mode Central On IND_TR Central 1 On 1
Op. mode Central Off IND_TR Central 1 Off 2
Op. mode Local On IND_TR Local 2 On 1
Op. mode Local Off IND_TR Local 2 Off 2
Op. mode Remote On IND_TR Remote 3 On 1
Op. mode Remote Off IND_TR Remote 3 Off 2
Op. mode Manual On IND_TR Manual 5 On 1
Op. mode Manual Off IND_TR Manual 5 Off 2
Op. mode Auto On IND_TR Auto 4 On 1
Op. mode Auto Off IND_TR Auto 4 Off 2
Op. mode Blocked On IND_TR CtrlBlk 6 On 1
Op. mode Blocked Off IND_TR CtrlBlk 6 Off 2
Op. mode Standby On IND_TR Standby 7 On 1
Appendix B Event Texts Binary Object GENBIN
Op. mode Standby Off IND_TR Standby 7 Off 2
ON-indication On IND_TR On/Open 9 On 1
ON-indication Off IND_TR On/Open 9 Off 2
Indication changing On IND_TR PosChnge 10 On 1
Indication changing Off IND_TR PosChnge 10 Off 2
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 187/280
3BSE030340R4101 187
User Defined Object GENUSD Appendix B Event Texts
User Defined Object GENUSD
Events Event Treatpointer
Property text Event text
Standard
text
Line No inEvent
Treat
Standard
text
Line No inEvent
Treat
Alarm ALQ1 On AL_TR Quality 1 1 Alarm 1
Alarm ALQ1 Off AL_TR Quality 1 1 Normal 2
Alarm ALQ2 On AL_TR Quality 2 2 Alarm 1
Alarm ALQ2 Off AL_TR Quality 2 2 Normal 2
Alarm ALF1 On AL_TR Fault 1 3 Alarm 1
Alarm ALF1 Off AL_TR Fault 1 3 Normal 2
Alarm ALF2 On AL_TR Fault 2 4 Alarm 1
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 188/280
188 3BSE030340R4101
Alarm ALF2 Off AL_TR Fault 2 4 Normal 2
Alarm ALF3 On AL_TR Fault 3 5 Alarm 1
Alarm ALF3 Off AL_TR Fault 3 5 Normal 2
Alarm ALF4 On AL_TR Fault 4 6 Alarm 1
Alarm ALF4 Off AL_TR Fault 4 6 Normal 2
Alarm ALF5 On AL_TR Fault 5 7 Alarm 1
Alarm ALF5 Off AL_TR Fault 5 7 Normal 2
Alarm ALF6 On AL_TR Fault 6 8 Alarm 1
Alarm ALF6 Off AL_TR Fault 6 8 Normal 2
Interlock INTLU1 On INTL_TR Interl 1 1 On 1
Interlock INTLU1 Off INTL_TR Interl 1 1 Off 2Interlock INTLU2 On INTL_TR Interl 2 2 On 1
Interlock INTLU2 Off INTL_TR Interl 2 2 Off 2
Appendix B Event Texts User Defined Object GENUSD
Interlock INTLU3 On INTL_TR Interl 3 3 On 1
Interlock INTLU3 Off INTL_TR Interl 3 3 Off 2
Interlock INTLU4 On INTL_TR Interl 4 4 On 1
Interlock INTLU4 Off INTL_TR Interl 4 4 Off 2
Interlock INTLU5 On INTL_TR Interl 5 5 On 1
Interlock INTLU5 Off INTL_TR Interl 5 5 Off 2
Interlock INTLU6 On INTL_TR Interl 6 6 On 1
Interlock INTLU6 Off INTL_TR Interl 6 6 Off 2
O d M1 M1 O IND TR O P 1 1 O 1
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event
Treat
Standard
text
Line No in
Event
Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 189/280
3BSE030340R4101 189
Op. mode M1 M1 On IND_TR OperPos1 1 On 1
Op. mode M1 M1 Off IND_TR OperPos1 1 Off 2
Op. mode M2 M2 On IND_TR OperPos2 2 On 1
Op. mode M2 M2 Off IND_TR OperPos2 2 Off 2
Op. mode M3 M3 On IND_TR OperPos3 3 On 1
Op. mode M3 M3 Off IND_TR OperPos3 3 Off 2
Op. mode Manual On MAN IND_TR Manual 5 On 1
Op. mode Manual Off MAN IND_TR Manual 5 Off 2
Op. mode Auto On AUTO IND_TR Auto 4 On 1
Op. mode Auto Off AUTO IND_TR Auto 4 Off 2
Op. mode Blocked On BLK IND_TR CtrlBlk 6 On 1
Op. mode Blocked Off BLK IND_TR CtrlBlk 6 Off 2
Op. mode Standby On STBY IND_TR Standby 7 On 1
Op. mode Standby Off STBY IND_TR Standby 7 Off 2
User Defined Object GENUSD Appendix B Event Texts
Indication IND1 On IND_TR Indic.1 9 On 1
Indication IND1 Off IND_TR Indic.1 9 Off 2
Indication IND2 On IND_TR Indic.2 10 On 1
Indication IND2 Off IND_TR Indic.2 10 Off 2
Indication IND3 On IND_TR Indic.3 11 On 1
Indication IND3 Off IND_TR Indic.3 11 Off 2
Indication IND4 On IND_TR Indic.4 12 On 1
Indication IND4 Off IND_TR Indic.4 12 Off 2
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event
Treat
Standard
text
Line No in
Event
Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 190/280
190 3BSE030340R4101
Appendix B Event Texts Motor Control MOTCON
Motor Control MOTCON
EventsEvent Treat
pointer
Property text Event text
Standardtext
Line No inEvent Treat
Standardtext
Line No inEvent Treat
Control voltage absent I1_TR ControlV 1 Alarm 1
Control voltage restored I1_TR ControlV 1 Normal 2
Bimetal relay has tripped I1_TR BimetalR 2 Alarm 1
Bimetal relay triggered I1_TR BimetalR 2 Normal 2Local Stop I1_TR LStop 3 Alarm 1
Local Stop ended I1_TR LStop 3 Normal 2
Safety Monitor tripped I1_TR SafeMon 4 Alarm 1
Safety Monitor triggered I1_TR SafeMon 4 Normal 2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 191/280
3BSE030340R4101 191
y gg _
Main contactor Error I1_TR MainCErr 5 Alarm 1
Main contactor Erroracknowledged
I1_TR MainCErr 5 Normal 2
Monitor Low tripped I1_TR MonLow 6 Alarm 1
Monitor Low restored I1_TR MonLow 6 Normal 2
Monitor High tripped I1_TR MonHigh 7 Alarm 1
Monitor High restored I1_TR MonHigh 7 Normal 2
Position A reached I1_TR Pos A 8 Alarm 1
Position A left I1_TR Pos A 8 Normal 2
Current limit 100 % exceeded I1_TR HighCurr 11 Alarm 1
Current limit 100 % re-entered I1_TR HighCurr 11 Normal 2
Position B reached I1_TR Pos B 12 Alarm 1
Position B left I1_TR Pos B 12 Normal 2
Motor Control MOTCON Appendix B Event Texts
Control mode Local On I2_TR Local 2 On 1
Control mode Local Off I2_TR Local 2 Off 2
Control mode Test On I2_TR Test 3 On 1
Control mode Test Off I2_TR Test 3 Off 2
Control mode Standby On I2_TR Standby 4 On 1
Control mode Standby Off I2_TR Standby 4 Off 2
Control mode Sequence On I2_TR Sequence 5 On 1
Control mode Sequence Off I2_TR Sequence 5 Off 2
Op. mode Auto On I2_TR Auto 6 On 1
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 192/280
192 3BSE030340R4101
Op. mode Auto Off I2_TR Auto 6 Off 2
Interlock IC1 On I2_TR CInterl1 9 On 1
Interlock IC1 Off I2_TR CInterl1 9 Off 2
Interlock IC2 On I2_TR CInterl2 10 On 1
Interlock IC2 Off I2_TR CInterl2 10 Off 2
Interlock IB1 On I2_TR BInterl1 13 On 1
Interlock IB1 Off I2_TR BInterl1 13 Off 2
Interlock IB2 On I2_TR BInterl2 14 On 1
Interlock IB2 Off I2_TR BInterl2 14 Off 2
Interlock IB3 On I2_TR BInterl3 11 On 1
Interlock IB3 Off I2_TR BInterl3 11 Off 2
Interlock IB4 On I2_TR BInterl4 12 On 1
Interlock IB4 Off I2_TR BInterl4 12 Off 2
Appendix B Event Texts Motor Control MOTCON
Interlock IA On I2_TR AInterl 15 Off 1
Interlock IA Off I2_TR AInterl 15 Off 2
Control mode Local ORD_TR Local 1 Order 1
Control mode Test ORD_TR Test 2 Order 1
Control mode Standby ORD_TR Standby 3 Order 1
Control mode Central ORD_TR Central 4 Order 1
Control mode Sequence ORD_TR Sequence 13 Order 1
Op. mode Auto ORD_TR Auto 5 Order 1
Op. mode Manual ORD_TR Manual 6 Order 1
Bl ki f IB1 d IB3 ORD TR Blk BI 7 O d 1
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 193/280
3BSE030340R4101 193
Blocking of IB1 and IB3
Interlock
ORD_TR Blk.BI 7 Order 1
Deblocking of IB1 and IB3Interlock
ORD_TR Norm.BI 8 Order 1
Order Forward ORD_TR Forward 9 Order 1
Order Reverse ORD_TR Reverse 10 Order 1
Order Start ORD_TR Start 11 Order 1Order Stop ORD_TR Stop 12 Order 1
Valve Control VALVECON Appendix B Event Texts
Valve Control VALVECON
Events
Event Treat
pointer
Property text Event text
Standardtext
Line No inEvent Treat
Standardtext
Line No inEvent Treat
User defined Fault 1 coming I1_TR F1 1 Alarm 1
User defined Fault 1 passing I1_TR F1 1 Normal 2
User defined Fault 2 coming I1_TR F2 2 Alarm 1
User defined Fault 2 passing I1_TR F2 2 Normal 2Position error open coming I1_TR PosErrO 3 Alarm 1
Position error open passing I1_TR PosErrO 3 Normal 2
Position error closed coming I1_TR PosErrC 4 Alarm 1
Position error closed passing I1_TR PosErrC 4 Normal 2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 194/280
194 3BSE030340R4101
Valve in open position I1_TR Pos O 8 Alarm 1
Valve changes from openposition
I1_TR Pos O 8 Normal 2
Valve in closed position I1_TR Pos C 12 Alarm 1
Valve changes from closedposition
I1_TR Pos C 12 Normal 2
Valve in intermediate position I1_TR IntPos 16 Alarm 1
Valve not in intermediateposition
I1_TR IntPos 16 Normal 2
Control mode Local On I2_TR Local 2 On 1
Control mode Local Off I2_TR Local 2 Off 2
Control mode Test On I2_TR Test 3 On 1
Control mode Test Off I2_TR Test 3 Off 2
Control mode Standby On I2_TR Standby 4 On 1
Appendix B Event Texts Valve Control VALVECON
Control mode Standby Off I2_TR Standby 4 Off 2
Control mode Sequence On I2_TR Sequence 5 On 1
Control mode Sequence Off I2_TR Sequence 5 Off 2
Op. mode Auto On I2_TR Auto 6 On 1
Op. mode Auto Off I2_TR Auto 6 Off 2
Interlock IC1 On I2_TR CInterl1 9 On 1
Interlock IC1 Off I2_TR CInterl1 9 Off 2
Interlock IC2 On I2_TR CInterl2 10 On 1
Interlock IC2 Off I2_TR CInterl2 10 Off 2
Interlock IB1 On I2 TR BInterl1 11 On 1
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 195/280
3BSE030340R4101 195
Interlock IB1 On I2_TR BInterl1 11 On 1
Interlock IB1 Off I2_TR BInterl1 11 Off 2
Interlock IB2 On I2_TR BInterl2 12 On 1
Interlock IB2 Off I2_TR BInterl2 12 Off 2
Interlock IB3 On I2_TR BInterl3 13 On 1
Interlock IB3 Off I2_TR BInterl3 13 Off 2
Interlock IB4 On I2_TR BInterl4 14 On 1
Interlock IB4 Off I2_TR BInterl4 14 Off 2
Interlock IA On I2_TR AInterl 15 On 1
Interlock IA Off I2_TR AInterl 15 Off 2
Op. mode Local ORD_TR Local 1 Order 1
Op. mode Test ORD_TR Test 2 Order 1
Control mode Standby ORD_TR Standby 3 Order 1
Valve Control VALVECON Appendix B Event Texts
Control mode Central ORD_TR Central 4 Order 1
Control mode Sequence ORD_TR Sequence 11 Order 1
Op. mode Auto ORD_TR Auto 5 Order 1
Op. mode Manual ORD_TR Manual 6 Order 1
Blocking of IB1 and IB3
Interlock
ORD_TR Blk.BI 7 Order 1
Deblocking of IB1 and IB3Interlock
ORD_TR Norm.BI 8 Order 1
Order Open ORD_TR Open 9 Order 1
Order Close ORD_TR Close 10 Order 1
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 196/280
196 3BSE030340R4101
Appendix B Event Texts Group Start GROUP
Group Start GROUP
Events
Event Treat
pointer
Property text Event text
Standardtext
Line No inEvent Treat
Standardtext
Line No inEvent Treat
Timeout sequence I1_TR Timeout G 1 Alarm 1
Timeout sequenceacknowledged
I1_TR Timeout G 1 Normal 2
Timeout step I1_TR Timeout S 2 Alarm 1
Timeout step acknowledged I1_TR Timeout S 2 Normal 2
User defined Fault 3 coming I1_TR Fault 3 3 Alarm 1
User defined Fault 3 passing I1_TR Fault 3 3 Normal 2
User defined Fault 4 coming I1_TR Fault 4 4 Alarm 1
User defined Fault 4 passing I1 TR Fault 4 4 Normal 2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 197/280
3BSE030340R4101 197
User defined Fault 4 passing I1_TR Fault 4 4 Normal 2
User defined Fault 5 coming I1_TR Fault 5 5 Alarm 1
User defined Fault 5 passing I1_TR Fault 5 5 Normal 2
Position A reached I1_TR Pos A 8 Alarm 1
Position A left I1_TR Pos A 8 Normal 2
Position B reached I1_TR Pos B 12 Alarm 1
Position B left I1_TR Pos B 12 Normal 2
Control mode Local On I2_TR Local 2 On 1
Control mode Local Off I2_TR Local 2 Off 2
Control mode Test On I2_TR Test 3 On 1
Control mode Test Off I2_TR Test 3 Off 2
Control mode Standby On I2_TR Standby 4 On 1
Control mode Standby Of I2_TR Standby 4 Off 2f
Group Start GROUP Appendix B Event Texts
Control mode Sequence On I2_TR Sequence 5 On 1
Control mode Sequence Off I2_TR Sequence 5 Off 2
Op. mode Auto On I2_TR Auto 6 On 1
Op. mode Auto Off I2_TR Auto 6 Off 2
Interlock IC1 On I2_TR CInterl1 9 On 1
Interlock IC1 Off I2_TR CInterl1 9 Off 2
Interlock IC2 On I2_TR CInterl2 10 On 1
Interlock IC2 Off I2_TR CInterl2 10 Off 2
Interlock IB1 On I2_TR BInterl1 13 On 1
Interlock IB1 Off I2_TR BInterl1 13 Off 2
EventsEvent Treat
pointer
Property text Event text
Standard
text
Line No in
Event Treat
Standard
text
Line No in
Event Treat
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 198/280
198 3BSE030340R4101
Interlock IB2 On I2_TR BInterl2 14 On 1
Interlock IB2 Off I2_TR BInterl2 14 Off 2
Interlock IB3 On I2_TR BInterl3 11 On 1
Interlock IB3 Off I2_TR BInterl3 11 Off 2
Interlock IB4 On I2_TR BInterl4 12 On 1
Interlock IB4 Off I2_TR BInterl4 12 Off 2
Interlock IA On I2_TR AInterl 15 On 1
Interlock IA Off I2_TR AInterl 15 Off 2
Appendix B Event Texts Group Alarm GRPALARM
Group Alarm GRPALARM
Events
Event Treat
pointer
Property text Event text
Standardtext
Line No inEvent Treat
Standardtext
Line No inEvent Treat
Abnormal position Off DISTR_TR Disturb 1 Alarm 1
Abnormal position On DISTR_TR Disturb 1 Normal 2
Blocking of event handling DISTR_TR Alarm 2 Blocked 3
Deblocking of event handling DISTR_TR Alarm 2 Deblocked 4Blocking of printout DISTR_TR Printout 3 Blocked 3
Deblocking of printout DISTR_TR Printout 3 Deblocked 4
Blocking master On PREV_TR Blk Master 1 On 1
Blocking master Off PREV_TR Blk Master 1 Off 2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 199/280
3BSE030340R4101 199
First error On PREV_TR First Err 2 On 1First error Off PREV_TR First Err 2 Off 2
Prevent event handling On PREV_TR Event 3 Blocked 3
Prevent event handling Off PREV_TR Event 3 Deblocked 4
Blocking of the membersevent handling
PREV_TR MembAlarm
4 Blocked 3
Deblocking of the membersevent handling
PREV_TR MembAlarm
4 Deblocked 4
Blocking of the membersevent printout
PREV_TR MembPrint 5 Blocked 3
Deblocking of the membersevent printout
PREV_TR MembPrint 5 Deblocked 4
Motor Control MOTCONI Appendix B Event Texts
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 byoperator. 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 ascommunication error. Most events and alarms are however generated and timestamped in the Motor Control Unit itself, for best possible time resolution, and sentvia the LONWORKS network to the Controller.
Figure 86 below shows the principles for how the events are translated andassociated to proper texts in the Operator Station.
Advant Controller 410/450 Operator Station
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 200/280
200 3BSE030340R4101
Figure 86. Event handling from LON W ORKS Network to Operator station in principles
MMCXx
EVENT346..352
Event &Alarm
handlingUserControl
AL_BLK
I1_TR
I2_TRIND1IND2
I1_EVBLK
I2_EVBLKLON Device
EV_BLK
LONEVTRx
ALOBJx
LONDEVxLonWorks Network
MOTCON
PC-Program
Alarm list
Event list
Event Treat
Texts
CI572
Appendix B Event Texts Motor Control MOTCONI
In principle, the following processing is done in the Controller for every eventmessage received from the MCU via network variable 2040:
• The LONDEV data base element that represents the sending device (MCU) isrecognized.
• The LONDEV data base element points out three objects, of type MMCX. Oneobject for warnings (ALOBJ1), one for alarms (ALOBJ2) and one forevents(ALOBJ3). Each MMCX object can deal with up to 32 differentwarning/alarm/event indications. The event message is then forwarded to eachalarm object.
• The MMCX object in it’s turn forwards all state transitions to the Operator
stations for presentation according to defined treatment and texts defined byterminals I1_TR or I2_TR. The treatment is divided in groups represented bydata base element Event Treat. For each group different handling can beselected 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 couldbe done either from the operators dialog affecting all alarms and events from eachMCU. Separate alarms could be blocked by the bit masks I1_EVBLK and
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 201/280
3BSE030340R4101 201
p yI2_EVBLK in MMCX data base element. The terminal EV_BLK in LONDEV database element could also be used to block events received from each MCU.
The translation of events and alarms for MOTCONI is described below. They aredivided 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
Standard Alarm Text from MOTCON PC element Appendix B Event Texts
See Table E-1 for network variable bindnings that has to be done to correctly receiveevents and alarms from MCU.
Table 12. Network Variable bindings needed for event and alarm handling from MCU
Description SNVTCI572 MCU
NV-Index NV-Name NV-Index NV-Name
Clock Warning, broadcast from
CI572 before the clocksynchronization message
0 2042 nvoClockWrng 8 nviClockWrng
Clock synchronizationbroadcast message. The send
interval is defined byLONCHAN database element
0 2041 nvoClock 7 nviClock
Alarm Report message with
warnings, alarms, events andtime stamp
0 2040 nviAlarmReport 51 nvoAlarmReport
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 202/280
202 3BSE030340R4101
Standard Alarm Text from MOTCON PC element
Table 13. Alarms reported from MOTCON PC element, translated via data base element
EVENT352
Description
IND bit
in
MMCX
Property textEvent
Text
Communication error IND1_00 CommErr Warning
Normal
Over load IND1_01 Overload Warning
Normal
Local Stop IND1_02 LStop Warning
Normal
Appendix B Event Texts Standard Alarm Text from MOTCON PC element
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
Table 13. Alarms reported from MOTCON PC element, translated via data base element EVENT352
(Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 203/280
3BSE030340R4101 203
Standard Warning Texts from MCU Appendix B Event Texts
Standard Warning Texts from MCU
Table 14. Warnings reported from MCU, translated via data base element EVENT346 or
EVENT347
DescriptionIND bit
in MMCX
Event
Treat
element
Property textEvent
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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 204/280
204 3BSE030340R4101
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
Appendix B Event Texts Standard Warning Texts from MCU
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
Table 14. Warnings reported from MCU, translated via data base element EVENT346 or EVENT347
(Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 205/280
3BSE030340R4101 205
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
Standard Warning Texts from MCU Appendix B Event Texts
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
Table 14. Warnings reported from MCU, translated via data base element EVENT346 or EVENT347
(Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 206/280
206 3BSE030340R4101
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
Appendix B Event Texts Standard Alarm Text from MCU
Standard Alarm Text from MCU
Table 15. Alarms reported from MCU, translated via data base element EVENT348 or EVENT349
DescriptionIND bit
in MMCX
Event
Treat
element
Property textEvent
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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 207/280
3BSE030340R4101 207
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
Standard Alarm Text from MCU Appendix B Event Texts
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
St t li it ti t i IND2 00 EVENT349 St tLi W i
Table 15. Alarms reported from MCU, translated via data base element EVENT348 or EVENT349
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 208/280
208 3BSE030340R4101
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
Appendix B Event Texts 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
Table 15. Alarms reported from MCU, translated via data base element EVENT348 or EVENT349
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 209/280
3BSE030340R4101 209
Standard Event Text from MCU
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
Table 16. Events reported from MCU, translated via data base element EVENT350 or EVENT351
DescriptionIND bit
in MMCX
Event
Treat
element
Property textEvent
Text
Event Treatment in Operator Station Appendix B Event Texts
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
Table 16. Events reported from MCU, translated via data base element EVENT350 or EVENT351
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 210/280
210 3BSE030340R4101
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 databaseelement. The table below describes the predefined settings for different Event Treatelements for MOTCONI.
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
Table 17. Predefined Event treatment for MOTCONI
TerminalIndex of EVENT treatment data base element
352 346 347 348 349 350 351
AUDIBLE 1 1 1 1 1 0 0
Appendix B Event Texts Engineered Drive, DRICONE
Engineered Drive, DRICONE
This section describes the principles for events and alarms, the standard event textsfor DRICONE main data base element and DRICONE fault and alarm data baseelements. The section contains also a layout of the Event Treat configuration for
DRICONE.
AL_PRIO 2 3 3 2 2 4 4
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
5 5 5 5 5 5 5
Table 17. Predefined Event treatment for MOTCONI
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 211/280
3BSE030340R4101 211
Figure 86 shows diagrammatically the relation between indications and theparameters which can be used to block event handling for certain indications andpoints out a required handling in the operator’s station.
Engineered Drive, DRICONE Appendix B Event Texts
The possibilities of the operator to block event printouts and alarms are shown underthe heading ‘Event and alarm blocking’ below.
I1_EVBLK
IND 1
I1_TR
Y
X
Advant Controller 410/450
PC element MMC-IND
Fault in DriveLimitWarning from Drive
•••
Parameters
Data base element
Blockingof
requiredevents
Event treatpointer
Advant Station 500 Series
Event Treat
X
Defines
- Event/Alarm- Acoustic alarm- Layout of texts- Std. texts
etc.
Operator Station
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 212/280
212 3BSE030340R4101
The events are divided into groups. One pointer is allocated to each group whichmeans that the individual events of the group are, in several respects, handled in thesame way in Advant Station 500 Series Operator Station. For each group differenthandling can be selected for status changes 0-->1 and 1-->0 respectively. The textswhich are written out in different lists are individual for each event. The groupdivision - which events are associated with the pointer - is given in ‘Eventdescription with standard texts’ below. This also specifies which event handling isobtained as default and which alternative standard function.
Figure 87. Event Handling Principles
Appendix B Event Texts Engineered Drive, DRICONE
Table 18. Event Text for Main MMCX Data Base Element, EVENT Treat element 334 - 335
Signal Events EventTreat
pointer
Property text Event Text
Standard text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_01 Out of window I1_TR Speed OutsideWindow
2 Alarm 1
IND1_01 Within window I1_TR Speed Outside
Window
2 Normal 2
IND1_02 Emergency stop I1_TR Emergency Stop Fault 3 Alarm 1
IND1_02 No Emergencystop
I1_TR Emergency Stop Fault 3 Normal 2
IND1_04 Run disabled I1_TR Run Disabled 5 Alarm 1
IND1_04 Run enabled I1_TR Run Disabled 5 Normal 2
IND1 06 First start not I1 TR First start not done 7 Alarm 1
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 213/280
3BSE030340R4101 213
IND1_06 First start not
done
I1_TR First start not done 7 Alarm 1
IND1_06 First start done I1_TR First start not done 7 Normal 2
IND1_07 Alarm from drive I1_TR Alarm from drive 8 Alarm 1
IND1_07 No alarm I1_TR Alarm from drive 8 Normal 2
IND1_08 Start inhibition I1_TR False Start Inhibit 9 Alarm 1
IND1_08 No start inhibition I1_TR False Start Inhibit 9 Normal 2
IND1_09 Limit exceeded I1_TR Limit 10 Alarm 1
IND1_09 No Limit I1_TR Limit 10 Normal 2
IND1_11 Fault from drive I1_TR Fault in Drive 12 Alarm 1
IND1_11 No fault I1_TR Fault in Drive 12 Normal 2
IND1_12 Communicationfault
I1_TR Communication Error 13 Alarm 1
Engineered Drive, DRICONE Appendix B Event Texts
IND1_12 Communicationfault
I1_TR Communication Error 13 Normal 2
IND2_00 In service readyto switch on I2_TR In service 1 On 1
IND2_00 Not in service I2_TR In service 1 Off 2
IND2_01 Drive ready tostart
I2_TR Ready to Start 2 On 1
IND2_01 Drive is not ready
to start
I2_TR Ready to Start 2 Off 2
IND2_02 Running with
selectedreference
I2_TR Run 3 On 1
IND2_02 Stopped I2_TR Run 3 Off 2
IND2_03 Motor is
magnetized
I2_TR Motor Magnetized 4 On 1
IND2_03 Motor is not I2_TR Motor Magnetized 4 Off 2
Table 18. Event Text for Main MMCX Data Base Element, EVENT Treat element 334 - 335
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 214/280
214 3BSE030340R4101
magnetized
IND2_04 OFF 2 I2_TR Emergency 5 On 5
IND2_04 No OFF 2 I2_TR Emergency 5 Off 6
IND2_05 OFF 3 I2_TR Emergency stop 6 On 5
IND2_05 No OFF 3 I2_TR Emergency stop 6 Off 6
IND2_06 Switch on is
inhibited
I2_TR Inhibit Switch On 7 Yes 3
IND2_06 Switch on is not
inhibited
I2_TR Inhibit Switch On 7 No 4
IND2_07 Drive runs at
setpoint
I2_TR At Setpoint 8 On 1
IND2_07 Drive is not atsetpoint
I2_TR At Setpoint 8 Off 2
Appendix B Event Texts Engineered Drive, DRICONE
IND2_08 C-Interlock I2_TR C-Interlock 9 On 1
IND2_08 C-Interlock I2_TR C-Interlock 9 Off 2
IND2_09 Drive runsremotely
controlled
I2_TR Remote 10 On 1
IND2_09 Drive runs locallycontrolled
I2_TR Remote 10 Off 2
IND2_10 B-Interlock 1 I2_TR B-Interlock 1 11 On 1
IND2_10 B-Interlock 1 I2_TR B-Interlock 1 11 Off 2
IND2_11 B-Interlock 2 I2_TR B-Interlock 2 12 On 1
IND2_11 B-Interlock 2 I2_TR B-Interlock 2 12 Off 2
IND2_12 B-Interlock 3 I2_TR B-Interlock 3 13 On 1
IND2_12 B-Interlock 3 I2_TR B-Interlock 3 13 Off 2
IND2_13 B-Interlock 4 I2_TR B-Interlock 4 14 On 1
Table 18. Event Text for Main MMCX Data Base Element, EVENT Treat element 334 - 335
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 215/280
3BSE030340R4101 215
IND2_13 B-Interlock 4 I2_TR B-Interlock 4 14 Off 2
IND2_14 A-Interlock I2_TR A-Interlock 15 On 1
IND2_14 A-Interlock I2_TR A-Interlock 15 Off 2
IND2_15 Override interlock I2_TR Override Interlock 16 On 1
IND2_15 Don’t overrideinterlock
I2_TR Override Interlock 16 Off 2
Engineered Drive, DRICONE Appendix B Event Texts
Table 19. Event Text for Fault MMCX Data Base Element ACS type of Drive, EVENT Treat element
336 - 337
Signal EventsEvent
Treat
pointer
Property text Event Text
Standard text
Line No
in EventTreat
Stand
ardtext
Line No
in EventTreat
IND1_0
0
Short circuit I1_TR Short Circuit 1 Fault 1
IND1_00
Short circuit I1_TR Short Circuit 1 Normal 2
IND1_01
Over current I1_TR Over Current 2 Fault 1
IND1_0
1
Over current I1_TR Over Current 2 Normal 2
IND1_02
DC over voltage fault I1_TR DC Over Voltage 3 Fault 1
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 216/280
216 3BSE030340R4101
IND1_02
No DC over voltagefault
I1_TR DC Over Voltage 3 Normal 2
IND1_0
3
Power plate over
temperature fault
I1_TR Over Temp Pow
Plate
4 Fault 1
IND1_03 No power plate overtemperature fault I1_TR Over Temp PowPlate 4 Normal 2
IND1_04
Earth fault I1_TR Earth Fault 5 Fault 1
IND1_04
No earth fault I1_TR Earth Fault 5 Normal 2
IND1_0
5
Motor over temperature
fault
I1_TR Over Temp Motor 6 Fault 1
IND1_0
5
No motor over
temperature fault
I1_TR Over Temp Motor 6 Normal 2
Appendix B Event Texts Engineered Drive, DRICONE
IND1_0
6
Motor over load fault I1_TR Over Load Motor 7 Fault 1
IND1_0
6
No motor over load
fault
I1_TR Over Load Motor 7 Normal 2
IND1_07
System fault I1_TR System Fault 8 Fault 1
IND1_0
7
No system fault I1_TR System Fault 8 Normal 2
IND1_0
8
Under load fault I1_TR Under Load 9 Fault 1
IND1_0
8
No under load fault I1_TR Under Load 9 Normal 2
IND1_0
9
Over speed fault I1_TR Over Speed 10 Fault 1
IND1_09
No over speed fault I1_TR Over Speed 10 Normal 2
Table 19. Event Text for Fault MMCX Data Base Element ACS type of Drive, EVENT Treat element
336 - 337 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 217/280
3BSE030340R4101 217
IND1_10
Supply Section fault I1_TR Supply Section 11 Fault 1
IND1_10
No Supply Section fault I1_TR Supply Section 11 Normal 2
IND1_11
Master/Follower fault I1_TR Master/Follower 12 Fault 1
IND1_1
1
No Master/Follower
fault
I1_TR Master/Follower 12 Normal 2
IND1_12
Short circuit INT1 I1_TR Short circuit INT1 13 Fault 1
IND1_12 No Short circuit INT1 I1_TR Short Circuit Int1 13 Normal 2
IND1_13
Short circuit INT2 I1_TR Short Circuit Int2 14 Fault 1
Engineered Drive, DRICONE Appendix B Event Texts
IND1_1
3
No Short circuit INT2 I1_TR Short Circuit Int2 14 Normal 2
IND1_1
4
Short circuit INT3 I1_TR Short Circuit Int3 15 Fault 1
IND1_14
No Short circuit INT3 I1_TR Short Circuit Int3 15 Normal 2
IND1_1
5
Short circuit INT4 I1_TR Short Circuit Int4 16 Fault 1
IND1_1
5
No Short circuit INT4 I1_TR Short Circuit Int4 16 Normal 2
IND2_0
0
Supply section fault I2_TR Supply Section 1 Fault 1
IND2_0
0
No supply section fault I2_TR Supply Section 1 Normal 2
IND2_02
DC under voltage I2_TR DC Under Voltage 3 Fault 1
Table 19. Event Text for Fault MMCX Data Base Element ACS type of Drive, EVENT Treat element
336 - 337 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 218/280
218 3BSE030340R4101
IND2_02
No DC under voltage I2_TR DC Under Voltage 3 Normal 2
IND2_04
Run disabled I2_TR Run Disabled 5 Fault 1
IND2_04
Run enabled I2_TR Run Disabled 5 Normal 2
IND2_0
5
Encoder fault I2_TR Speed Encoder 6 Fault 1
IND2_05
No encoder fault I2_TR Speed Encoder 6 Normal 2
IND2_06
I/O link fault channel 1 I2_TR I/O Link channel 1 7 Fault 1
IND2_06
No I/O link faultchannel 1
I2_TR I/O Link channel 1 7 Normal 2
Appendix B Event Texts Engineered Drive, DRICONE
IND2_0
7
Cabinett
overtemperature
I2_TR Cabinett overtemp 8 Fault 1
IND2_0
7
No Cabinett
overtemperature
I2_TR Cabinett overtemp 8 Normal 2
IND2_09
Over svitchingfrequency
I2_TR Over Switching 10 Fault 1
IND2_0
9
No over switching
frequency
I2_TR Over Switching 10 Normal 2
IND2_1
1
PPCC link fault I2_TR PPCC Link 12 Fault 1
IND2_1
1
No PPCC link fault I2_TR PPCC Link 12 Normal 2
IND2_1
2
Communication fault
Channel 0
I2_TR Communication
Ch 0
13 Fault 1
IND2_12
No Communicationfault Channel 0
I2_TR CommunicationCh 0
13 Normal 2
Table 19. Event Text for Fault MMCX Data Base Element ACS type of Drive, EVENT Treat element
336 - 337 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 219/280
3BSE030340R4101 219
IND2_13
Pannel loss I2_TR Pannel loss 14 Fault 1
IND2_13
No pannel loss I2_TR Pannel loss 14 Normal 2
IND2_14
Motor stalled I2_TR Motor Stalled 15 Fault 1
IND2_1
4
No motor stalled I2_TR Motor Stalled 15 Normal 2
IND2_15
Motor phase missing I2_TR Motor PhaseMissing
16 Fault 1
IND2_15
No motor phasemissing
I2_TR Motor PhaseMissing
16 Normal 2
Engineered Drive, DRICONE Appendix B Event Texts
Table 20. Event Text for Alarm MMCX Data Base Element ACS type of Drive, EVENT Treat element
338 - 339
Signal EventsEvent
Treat
pointer
Property text Event Text
Standard text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_00
Prevent unexpectedstart
I1_TR Prevent Start 1 Alarm 1
IND1_00
No preventation ofunexpected start
I1_TR Prevent Start 1 Normal 2
IND1_0
1
Emergency stop I1_TR Emergency Stop 2 Alarm 1
IND1_01
Emergency stop I1_TR Emergency Stop 2 Normal 2
IND1_02
Measured motor tempalarm
I1_TR Meas. MotorTemp
3 Alarm 1
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 220/280
220 3BSE030340R4101
IND1_02
Measured motor tempalarm
I1_TR Meas. MotorTemp
3 Normal 2
IND1_0
3
Over temperature
alarm of the thermal
model
I1_TR Motor Overload 4 Alarm 1
IND1_03
No over temperaturealarm of the thermal
model
I1_TR Motor Overload 4 Normal 2
IND1_04
Power plate overtemperature alarm
I1_TR Temp Power Plate 5 Alarm 1
IND1_0
4
No power plate over
temperature alarm
I1_TR Temp Power Plate 5 Normal 2
IND1_05
Pulse encoder alarm I1_TR Pulse Encoder 6 Alarm 1
Appendix B Event Texts Engineered Drive, DRICONE
IND1_0
5
No Pulse encoder
alarm
I1_TR Pulse Encoder 6 Normal 2
IND1_0
7
Standard digital I/O
alarm
I1_TR Standard Digital
I/O
8 Alarm 1
IND1_07
No Standard digital I/Oalarm
I1_TR Standard DigitalI/O
8 Normal 2
IND1_0
8
Standard analogue I/O
alarm
I1_TR Standard Analog
I/O
9 Alarm 1
IND1_0
8
No Standard analogue
I/O alarm
I1_TR Standard Analog
I/O
9 Normal 2
IND1_0
9
External digital I/O
alarm
I1_TR Ext. Digital I/O 10 Alarm 1
IND1_0
9
No External digital I/O
alarm
I1_TR Ext. Digital I/O 10 Normal 2
IND1_10
External analogue I/Oalarm
I1_TR Ext. Analog I/O 11 Alarm 1
Table 20. Event Text for Alarm MMCX Data Base Element ACS type of Drive, EVENT Treat element
338 - 339 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 221/280
3BSE030340R4101 221
IND1_10
No External analogueI/O alarm
I1_TR Ext. Analog I/O 11 Normal 2
IND1_11
Master - Followeralarm
I1_TR Master - Followalarm
12 Alarm 1
IND1_11
Master - Followeralarm
I1_TR Master - Followalarm
12 Normal 2
IND1_1
2
Communication alarm
Channel 0
I1_TR Comm. Channel 0 13 Alarm 1
IND1_12
Communication alarmChannel 0
I1_TR Comm. Channel 0 13 Normal 2
IND1_14
Earth fault alarm I1_TR Earth fault 15 Alarm 1
IND1_14
No Earth fault alarm I1_TR Earth fault 15 Normal 2
Engineered Drive, DRICONE Appendix B Event Texts
IND2_0
0
Power failure I2_TR Power Failure 1 Alarm 1
IND2_0
0
No power failure I2_TR Power Failure 1 Normal 2
IND2_01
Under load alarm I2_TR Under Load 2 Alarm 1
IND2_0
1
No under load alarm I2_TR Under Load 2 Normal 2
IND2_02
Identity run I2_TR Identity run 3 Alarm 1
IND2_0
2
No Identity run I2_TR Identity run 3 Normal 2
IND2_0
3
DC under voltage
alarm
I2_TR DC Under Voltage 5 Alarm 1
IND2_03
No DC under voltagealarm
I2_TR DC Under Voltage 5 Normal 2
Table 20. Event Text for Alarm MMCX Data Base Element ACS type of Drive, EVENT Treat element
338 - 339 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 222/280
222 3BSE030340R4101
IND2_04
DC over voltage alarm I2_TR DC Over Voltage 5 Alarm 1
IND2_04
No DC over voltagealarm
I2_TR DC Over Voltage 5 Normal 2
IND2_05
Over current alarm I2_TR Over Current 6 Alarm 1
IND2_0
5
No over current alarm I2_TR Over Current 6 Normal 2
IND2_06
Over frequency alarm I2_TR Over Frequency 7 Alarm 1
IND2_06
No over frequencyalarm
I2_TR Over Frequency 7 Normal 2
IND2_07
Power failure file I2_TR Power Failure file 8 Alarm 1
Appendix B Event Texts Engineered Drive, DRICONE
IND2_0
7
No power failure file I2_TR Power Failure file 8 Normal 2
IND2_0
8
Power down file I2_TR Power Down file 8 Alarm 1
IND2_07
No power down file I2_TR Power Down file 8 Normal 2
IND2_0
8
Motor stalled alarm I2_TR Stall 9 Alarm 1
IND2_08
No motor stalled alarm I2_TR Stall 9 Normal 2
IND2_0
9
Supply phase I2_TR Supply Phase 10 Alarm 1
IND2_0
9
No supply phase
missing
I2_TR Supply Phase 10 Normal 2
IND2_10
Timeout channel 0 I2_TR DDCS TimeoutCh0
11 Alarm 1
IND2 1 N ti t h l 0 I2 TR DDCS Ti t 11 N l 2
Table 20. Event Text for Alarm MMCX Data Base Element ACS type of Drive, EVENT Treat element
338 - 339 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 223/280
3BSE030340R4101 223
IND2_10
No timeout channel 0 I2_TR DDCS TimeoutCh0
11 Normal 2
IND2_13
Pannel loss I2_TR Pannel loss 14 Alarm 1
IND2_13 No pannel loss I2_TR Pannel loss 14 Normal 2
Engineered Drive, DRICONE Appendix B Event Texts
Table 21. Event Text for Main MMCX Data Base Element DCS type of Drive, EVENT Treat element
340 - 341
Signal EventsEvent
Treat
pointer
Property text Event Text
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 8 Alarm 1
IND1_07 No alarm I1_TR Alarm from drive 8 Normal 2
IND1_11 Fault from drive I1_TR Fault in Drive 12 Alarm 1
IND1_11 No fault I1_TR Fault in Drive 12 Normal 2
IND1_12 Communication fault I1_TR Communication
Error
13 Alarm 1
IND1_12 Communication fault I1_TR CommunicationError
13 Normal 2
IND2_00 In service ready toswitch on
I2_TR In service 1 On 1
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 224/280
224 3BSE030340R4101
IND2_00 Not in service I2_TR In service 1 Off 2
IND2_01 Drive ready to start I2_TR Ready to Start 2 On 1
IND2_01 Drive is not ready to
start
I2_TR Ready to Start 2 Off 2
IND2_02 Running with selected
reference
I2_TR Run 3 On 1
IND2_02 Stopped I2_TR Run 3 Off 2
IND2_08 C-Interlock I2_TR C-Interlock 9 On 1
IND2_08 C-Interlock I2_TR C-Interlock 9 Off 2
IND2_10 B-Interlock 1 I2_TR B-Interlock 1 11 On 1
IND2_10 B-Interlock 1 I2_TR B-Interlock 1 11 Off 2
Appendix B Event Texts Engineered Drive, DRICONE
IND2_11 B-Interlock 2 I2_TR B-Interlock 2 12 On 1
IND2_11 B-Interlock 2 I2_TR B-Interlock 2 12 Off 2IND2_12 B-Interlock 3 I2_TR B-Interlock 3 13 On 1
IND2_12 B-Interlock 3 I2_TR B-Interlock 3 13 Off 2
IND2_13 B-Interlock 4 I2_TR B-Interlock 4 14 On 1
IND2_13 B-Interlock 4 I2_TR B-Interlock 4 14 Off 2
IND2_14 A-Interlock I2_TR A-Interlock 15 On 1
IND2_14 A-Interlock I2_TR A-Interlock 15 Off 2
IND2_15 Override interlock I2_TR Override Interlock 16 On 1
IND2_15 Don’t override interlock I2_TR Override Interlock 16 Off 2
Table 22. Event Text for Fault MMCX Data Base Element DCS type of Drive, EVENT Treat element
342 - 343
Table 21. Event Text for Main MMCX Data Base Element DCS type of Drive, EVENT Treat element
340 - 341 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 225/280
3BSE030340R4101 225
Signal EventsEvent
Treat
pointer
Property text Event Text
Standard text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_0
0
Auxiliary under voltage I1_TR Auxil.
Undervoltage
1 Fault 1
IND1_00
Auxiliary under voltage I1_TR Auxil.Undervoltage
1 Normal 2
IND1_01
Over current I1_TR Over Current 2 Fault 1
IND1_01
No Over current I1_TR Over Current 2 Normal 2
Engineered Drive, DRICONE Appendix B Event Texts
IND1_0
2
Armature over voltage
fault
I1_TR Armature Overvolt. 3 Fault 1
IND1_0
2
No Armature over
voltage fault
I1_TR Armature Overvolt. 3 Normal 2
IND1_03
Converter overtemperature fault
I1_TR Overtemp Conv. 4 Fault 1
IND1_0
3
No converter over
temperature fault
I1_TR Overtemp Conv. 4 Normal 2
IND1_04
Earth fault I1_TR Earth fault 5 Fault 1
IND1_0
4
No earth fault I1_TR Earth fault 5 Normal 2
IND1_0
5
Motor 1 over
temperature fault
I1_TR Motor 1 overtemp 6 Fault 1
IND1_05
No over temperaturefault motor 1
I1_TR Motor 1 overtemp 6 Normal 2
IND1 0 Motor 1 over load fault I1 TR Motor 1 overload 7 Fault 1
Table 22. Event Text for Fault MMCX Data Base Element DCS type of Drive, EVENT Treat element
342 - 343 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 226/280
226 3BSE030340R4101
IND1_06
Motor 1 over load fault I1_TR Motor 1 overload 7 Fault 1
IND1_06
No over load faultmotor 1
I1_TR Motor 1 overload 7 Normal 2
IND1_07 I/O-board not found I1_TR I/O-board notfound 8 Fault 1
IND1_0
7
I/O-board found I1_TR I/O-board not
foundt
8 Normal 2
IND1_08
Motor 2 overtemperature fault
I1_TR Motor 2 overtemp 9 Fault 1
IND1_08
No over temperaturefault motor 2
I1_TR Motor 2 overtemp 9 Normal 2
IND1_09
Motor 2 over load fault I1_TR Motor 2 overload 10 Fault 1
Appendix B Event Texts Engineered Drive, DRICONE
IND1_0
9
No over load fault
motor 2
I1_TR Motor 2 overload 10 Normal 2
IND1_1
1
Main supply under
voltage
I1_TR Mains
undervoltage
12 Alarm 1
IND1_11
No main supply undervoltage
I1_TR Mainsundervoltage
12 Normal 2
IND1_1
2
Main supply over
voltage
I1_TR Mains overvoltage 13 Fault 1
IND1_12
No main supply overvoltage
I1_TR Mains overvoltage 13 Normal 2
IND1_1
3
Not synchronized I1_TR Synchronism 14 Fault 1
IND1_1
3
Synchronized I1_TR Synchronism 14 Normal 2
IND1_14
Field exciter 1 overcurrent
I1_TR Fld ex 1overcurrent
15 Fault 1
IND1_1 No over current field I1_TR Fld ex 1 15 Normal 2
Table 22. Event Text for Fault MMCX Data Base Element DCS type of Drive, EVENT Treat element
342 - 343 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 227/280
3BSE030340R4101 227
_4 exciter 1
_overcurrent
IND1_15
Field exciter 1communication fault
I1_TR Fld ex 1commerror
16 Fault 1
IND1_15 No communicationfault field exciter 1 I1_TR Fld ex 1commerror 16 Normal 2
IND2_0
0
Armature current ripple I2_TR Arm current ripple 1 Fault 1
IND2_00
No armature currentripple
I2_TR Arm current ripple 1 Normal 2
IND2_01
Field exciter 2 overcurrent
I1_TR Fld ex 2overcurrent
2 Fault 1
IND2_01
No over current fieldexciter 2
I1_TR Fld ex 2overcurrent
2 Normal 2
Engineered Drive, DRICONE Appendix B Event Texts
IND2_0
2
Field exciter 2
communication fault
I1_TR Fld ex 2
commerror
3 Fault 1
IND2_0
2
No communication
fault field exciter 2
I1_TR Fld ex 2
commerror
3 Normal 2
IND2_03
Phase sequence fault I2_TR Phase sequence 4 Fault 1
IND2_0
3
No phase sequence
fault
I2_TR Phase sequence 4 Normal 2
IND2_04
No field acknowledge I2_TR Field acknowledge 5 Fault 1
IND2_0
4
Field acknowledge I2_TR Field acknowledge 5 Normal 2
IND2_0
5
Measured speed fault I2_TR Speed measured 6 Fault 1
IND2_05
No measured speedfault
I2_TR Speed measured 6 Normal 2
IND2_0 No external fan I2_TR Ext. Fan 7 Fault 1
Table 22. Event Text for Fault MMCX Data Base Element DCS type of Drive, EVENT Treat element
342 - 343 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 228/280
228 3BSE030340R4101
6 acknowledge acknowledge
IND2_06
External fanacknowledge
I2_TR Ext. Fanacknowledge
7 Normal 2
IND2_07 No main contactoracknowledge I2_TR Main cont ack 8 Fault 1
IND2_0
7
Main contactor
acknowledge
I2_TR Main cont ack 8 Normal 2
IND2_08
Type coding fault I2_TR Type coding 9 Fault 1
IND2_0
8
No type coding fault I2_TR Type coding 9 Normal 2
IND2_09
Parameter backup fault I2_TR Par backup 10 Fault 1
Appendix B Event Texts Engineered Drive, DRICONE
IND2_0
9
No parameter backup
fault
I2_TR Par backup 10 Normal 2
IND2_1
0
No central fan
acknowledge
I2_TR C Fan ack 11 Fault 1
IND2_10
Central fanacknowledge
I2_TR C Fan ack 11 Normal 2
IND2_1
1
DDCS ch. 0
communication fault
I2_TR DDCS Comm. Ch
0.
12 Fault 1
IND2_11
No DDCS ch. 0communication faultr
I2_TR DDCS Comm. Ch0.
12 Normal 2
IND2_1
2
Field exciter 1 fault I1_TR Fld ex 1 13 Fault 1
IND2_1
2
Field exciter 1 ok I1_TR Fld ex 1 13 Normal 2
IND2_13
Field exciter 2 fault I1_TR Fld ex 2 14 Fault 1
IND2_1 Field exciter 2 ok I1_TR Fld ex 2 14 Normal 2
Table 22. Event Text for Fault MMCX Data Base Element DCS type of Drive, EVENT Treat element
342 - 343 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 229/280
3BSE030340R4101 229
3
IND2_14
Motor stalled I2_TR Motor stalled 15 Fault 1
IND2_14 No motor stall I2_TR Motor stalled 15 Normal 2
IND2_1
5
Motor over speed I2_TR Motor overspeed 16 Fault 1
IND2_15
No motor over speed I2_TR Motor overspeed 16 Normal 2
Engineered Drive, DRICONE Appendix B Event Texts
Table 23. Event Text for Alarm MMCX Data Base Element DCS type of Drive, EVENT Treat element
344 - 345
Signal EventsEvent
Treat
pointer
Property text Event Text
Standard text
Line No
in Event
Treat
Standar
d text
Line
No in
Event
Treat
IND1_00
Prevent unexpected start I1_TR Prevent Start 1 Alarm 1
IND1_0
0
No preventation of
unexpected start
I1_TR Prevent Start 1 Normal 2
IND1_01
Emergency stop I1_TR Emergency Stop 2 Alarm 1
IND1_01
Emergency stop I1_TR Emergency Stop 2 Normal 2
IND1_0
2
Motor 1 over temperature
alarm
I1_TR Motor 1 Temp 3 Alarm 1
IND1 0 No over temperature I1 TR Motor 1 Temp 3 Normal 2
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 230/280
230 3BSE030340R4101
IND1_02
No over temperaturealarm motor 1
I1_TR Motor 1 Temp 3 Normal 2
IND1_0
3
Motor 1 over load alarm I1_TR Motor 1 Overload 4 Alarm 1
IND1_0
3
No over load alarmmotor
1
I1_TR Motor 1 Overload 4 Normal 2
IND1_0
4
Converter over
temperature alarm
I1_TR Conv. Overtemp 5 Alarm 1
IND1_0
4
No converter over
temperature alarm
I1_TR Conv. Overtemp 5 Normal 2
IND1_05
Register Blocked alarm I1_TR Register Blocked 6 Alarm 1
Appendix B Event Texts Engineered Drive, DRICONE
IND1_0
5
No Register Blocked
alarm
I1_TR Register Blocked 6 Normal 2
IND1_0
7
RAM backup alarm I1_TR RAM backup 8 Alarm 1
IND1_07
No RAM backup alarm I1_TR RAM backup 8 Normal 2
IND1_0
8
Motor 2 over temperature
alarm
I1_TR Motor 2 Temp 9 Alarm 1
IND1_08
No over temperaturealarm motor 2
I1_TR Motor 2 Temp 9 Normal 2
IND1_0
9
Motor 2 over load alarm I1_TR Motor 2 Overload 10 Alarm 1
IND1_0
9
No over load alarmmotor
2
I1_TR Motor 2 Overload 10 Normal 2
IND1_10
Main supply undervoltage
I1_TR Mainsundervoltage
11 Alarm 1
IND1_10
No main supply undervoltage
I1_TR Mainsundervoltage
11 Normal 2
Table 23. Event Text for Alarm MMCX Data Base Element DCS type of Drive, EVENT Treat element
344 - 345 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 231/280
3BSE030340R4101 231
0 voltage undervoltage
IND1_12
Converter Fan alarm I1_TR Converter Fan 13 Alarm 1
IND1_12 No Converter Fan alarm I1_TR Converter Fan 13 Normal 2
IND1_1
3
Armature current
deviation alarm
I1_TR Armature current
dev.
14 Alarm 1
IND1_13
No armature currentdeviation alarm
I1_TR Armature currentdev.
14 Normal 2
IND1_1
5
External fan
acknowledge alarm
I2_TR External Fan 16 Alarm 1
IND1_15
No external fanacknowledge alarm
I2_TR External Fan 16 Normal 2
Engineered Drive, DRICONE Appendix B Event Texts
IND2_0
0
Pannel loss alarm I2_TR Pannel loss 1 Alarm 1
IND2_0
0
No pannel loss alarm I2_TR Pannel loss 1 Normal 2
IND2_01
Type code changedalarm
I2_TR Type codechanged
2 Alarm 1
IND2_0
1
No type code changed
alarm
I2_TR Type code
changed
2 Normal 2
IND2_02
Init values read, S2 alarm I2_TR Init values read,S2
3 Alarm 1
IND2_0
2
No init values read, S2
alarm
I2_TR Init values read,
S2
3 Normal 2
IND2_0
3
Parameter set 2 missing
alarm
I2_TR Param set 2
missing
4 Alarm 1
IND2_03
Parameter set 2 notmissing
I2_TR Param set 2missing
4 Normal 2
IND2_04
Backup not allowedalarm
I2_TR Backup notallowed
5 Alarm 1
Table 23. Event Text for Alarm MMCX Data Base Element DCS type of Drive, EVENT Treat element
344 - 345 (Continued)
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 232/280
232 3BSE030340R4101
4 alarm allowed
IND2_04
Backup allowed I2_TR Backup notallowed
5 Normal 2
IND2_05
Write backup alarm I2_TR Write backup 6 Alarm 1
IND2_0
5
No write backup alarm I2_TR Write backup 6 Normal 2
Appendix B Event Texts Standard Drive, DRICONS
The Event Treat data base element in the Advant Station 500 Series of OperatorStation has a predefined configuration shown in Table 24.
Standard Drive, DRICONS
Table 24. Predefined Event Treat for DRICONE
Property EVENT
334 335 336 337 338 339 340 341 342 343 344 345
AUDIBLE 1 0 1 1 1 1 1 0 1 1 1 1
AL_PRIO 2 4 2 2 2 2 2 4 2 2 2 2
AL_TOBLK 0 1 0 0 0 0 0 1 0 0 0 0
AL_FRBLK 1 1 1 1 1 1 1 1 1 1 1 1
PERSISTB 0 1 0 0 0 0 0 1 0 0 0 0
TEXT_TOB 0 0 0 0 0 0 0 0 0 0 0 0
TEXT_FRB 0 0 0 0 0 0 0 0 0 0 0 0
TEXTCOM
B
17 17 17 17 17 17 17 17 17 17 17 17
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 233/280
3BSE030340R4101 233
This section describes the principles for events and alarms, the standard event textsfor DRICONS main data base element and DRICONS help data base element. Thesection contains also a layout of the Event Treat configuration for DRICONS.
Figure 86 shows diagrammatically the relation between indications and theparameters which can be used to block event handling for certain indications andpoints out a required handling in the operator’s station.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 234/280
Appendix B Event Texts Standard Drive, DRICONS
Table 25. Event text for main MMCX data base element, EVENT Treat element 330 - 331
Signal Events EventTreat
pointer
Property text Event Text
Standard text
Line No
in Event
Treat
Stand
ard
text
Line No
in Event
Treat
IND1_09 Limit exceeded I1_TR Limit 10 Alarm 1
IND1_09 No Limit I1_TR Limit 10 Normal 2
IND1_10 Warning fromdrive
I1_TR Warning from drive 11 Alarm 1
IND1_10 No warning I1_TR Warning from drive 11 Normal 2
IND1_11 Fault from drive I1_TR Fault in drive 12 Alarm 1
IND1_11 No fault I1_TR Fault in drive 12 Normal 2
IND1_12 Communication
error
I1_TR Communication error 13 Alarm 1
IND1_12 Communicationerror
I1_TR Communication error 13 Normal 2
IND2 00 I i d I2 TR I i 1 O 1
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 235/280
3BSE030340R4101 235
IND2_00 In service readyto switch on
I2_TR In service 1 On 1
IND2_00 Not in service I2_TR In service 1 Off 2
IND2_01 Drive enabled tostart
I2_TR Enabled 2 On 1
IND2_01 Drive is notenabled to start
I2_TR Enabled 2 Off 2
IND2_02 Running withselectedreference
I2_TR Run 3 On 1
IND2_02 Stopped I2_TR Run 3 Off 2
Standard Drive, DRICONS Appendix B Event Texts
IND2_04(1)
No OFF 2 I2_TR Emergency 5 Off 5
IND2_04
(1)
OFF 2 I2_TR Emergency 5 On 6
IND2_05(1)
No OFF 3 I2_TR Emergency stop 6 Off 5
IND2_05(1)
OFF 3 I2_TR Emergency stop 6 On 6
IND2_06(1)
Switch on is
inhibited
I2_TR Inhibit switch on 7 Yes 3
IND2_06(1)
Switch on is notinhibited
I2_TR Inhibit switch on 7 No 4
IND2_07 Drive runs atsetpoint
I2_TR At setpoint 8 On 1
IND2_07 Drive is not at
setpoint
I2_TR At setpoint 8 Off 2
IND2_08 C-Interlock I2_TR C-Interlock 9 On 1
IND2_08 C-Interlock I2_TR C-Interlock 9 Off 2
Table 25. Event text for main MMCX data base element, EVENT Treat element 330 - 331
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 236/280
236 3BSE030340R4101
IND2_09 Drive runs
remotelycontrolled
I2_TR Remote 10 On 1
IND2_09 Drive runs locallycontrolled
I2_TR Remote 10 Off 2
IND2_10 B-Interlock 1 I2_TR B-Interlock 1 11 On 1
IND2_10 B-Interlock 1 I2_TR B-Interlock 1 11 Off 2
IND2_11 B-Interlock 2 I2_TR B-Interlock 2 12 On 1
IND2_11 B-Interlock 2 I2_TR B-Interlock 2 12 Off 2
IND2_12 B-Interlock 3 I2_TR B-Interlock 3 13 On 1
IND2_12 B-Interlock 3 I2_TR B-Interlock 3 13 Off 2
Appendix B Event Texts Standard Drive, DRICONS
IND2_13 B-Interlock 4 I2_TR B-Interlock 4 14 On 1
IND2_13 B-Interlock 4 I2_TR B-Interlock 4 14 Off 2
IND2_14 A-Interlock I2_TR A-Interlock 15 On 1
IND2_14 A-Interlock I2_TR A-Interlock 15 Off 2
IND2_15 Override interlock I2_TR Override interlock 16 On 1
IND2_15 Don’t overrideinterlock
I2_TR Override interlock 16 Off 2
(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
Signal EventsEvent
Treat
pointer
Property text Event Text
Standard text
Line No
in EventTreat
Stand
ardtext
Line No
in EventTreat
IND1_0
0
Short circuit I1_TR Short circuit 1 Fault 1
Table 25. Event text for main MMCX data base element, EVENT Treat element 330 - 331
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 237/280
3BSE030340R4101 237
IND1_0
0
Short circuit I1_TR Short circuit 1 Normal 2
IND1_01
Over current I1_TR Over current 2 Fault 1
IND1_0
1
Over current I1_TR Over current 2 Normal 2
IND1_02
DC over voltage fault I1_TR DC over voltage 3 Fault 1
IND1_02 No DC over voltagefault I1_TR DC over voltage 3 Normal 2
IND1_0
3
Power plate over
temperature fault
I1_TR Over temp pow
plate
4 Fault 1
Standard Drive, DRICONS Appendix B Event Texts
IND1_03
No power plate overtemperature fault
I1_TR Over temp powplate
4 Normal 2
IND1_0
4
Earth fault I1_TR Earth fault 5 Fault 1
IND1_04
No earth fault I1_TR Earth fault 5 Normal 2
IND1_0
5
Motor over
temperature fault
I1_TR Over temp motor 6 Fault 1
IND1_0
5
No motor over
temperature fault
I1_TR Over temp motor 6 Normal 2
IND1_06
Motor over load fault I1_TR Over load motor 7 Fault 1
IND1_06
No motor over loadfault
I1_TR Over load motor 7 Normal 2
IND1_07
System fault I1_TR System fault 8 Fault 1
IND1_0
7
No system fault I1_TR System fault 8 Normal 2
IND1_0 Under load fault I1_TR Under load 9 Fault 1
Table 26. Event text for help MMCX data base element, EVENT Treat element 332 - 333
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 238/280
238 3BSE030340R4101
8
IND1_08
No under load fault I1_TR Under load 9 Normal 2
IND1_09
Over speed fault I1_TR Over speed 10 Fault 1
IND1_09
No over speed fault I1_TR Over speed 10 Normal 2
IND1_1
0
Supply Section fault I1_TR Supply Section 11 Fault 1
IND1_1
0
No Supply Section fault I1_TR Supply Section 11 Normal 2
Appendix B Event Texts Standard Drive, DRICONS
IND1_11
Master/Follower fault I1_TR Master/Follower 12 Fault 1
IND1_1
1
No Master/Follower
fault
I1_TR Master/Follower 12 Normal 2
IND1_12
Short circuit INT1 I1_TR Short circuit INT1 13 Fault 1
IND1_1
2
No Short circuit INT1 I1_TR Short circuit INT1 13 Normal 2
IND1_1
3
Short circuit INT2 I1_TR Short circuit INT2 14 Fault 1
IND1_13
No Short circuit INT2 I1_TR Short circuit INT2 14 Normal 2
IND1_14
Short circuit INT3 I1_TR Short circuit INT3 15 Fault 1
IND1_14
No Short circuit INT3 I1_TR Short circuit INT3 15 Normal 2
IND1_1
5
Short circuit INT4 I1_TR Short circuit INT4 16 Fault 1
IND1_1 No Short circuit INT4 I1_TR Short circuit INT4 16 Normal 2
Table 26. Event text for help MMCX data base element, EVENT Treat element 332 - 333
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 239/280
3BSE030340R4101 239
5
IND2_00
Prevent unexpectedstart
I2_TR Prevent start 1 Alarm 1
IND2_00
No preventation ofunexpected start
I2_TR Prevent start 1 Normal 2
IND2_01
Emergency stop I2_TR Emergency stop 2 Alarm 1
IND2_0
1
Emergency stop I2_TR Emergency stop 2 Normal 2
IND2_0
2
Measured motor temp
alarm
I2_TR Meas. motor temp 3 Alarm 1
Standard Drive, DRICONS Appendix B Event Texts
IND2_02
Measured motor tempalarm
I2_TR Meas. motor temp 3 Normal 2
IND2_0
3
Over temperature
alarm of the thermalmodel
I2_TR Motor overload 4 Alarm 1
IND2_03
No over temperaturealarm of the thermal
model
I2_TR Motor overload 4 Normal 2
IND2_0
4
Power plate over
temperature alarm
I2_TR Temp power plate 5 Alarm 1
IND2_0
4
No power plate over
temperature alarm
I2_TR Temp power plate 5 Normal 2
IND2_05
Pulse encoder alarm I2_TR Pulse encoder 6 Alarm 1
IND2_0
5
No Pulse encoder
alarm
I2_TR Pulse encoder 6 Normal 2
IND2_07
Standard digital I/Oalarm
I2_TR Standard DigitalI/O
8 Alarm 1
IND2_0
7
No Standard digital I/O
alarm
I2_TR Standard Digital
I/O
8 Normal 2
Table 26. Event text for help MMCX data base element, EVENT Treat element 332 - 333
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 240/280
240 3BSE030340R4101
IND2_0
8
Standard analogue I/O
alarm
I2_TR Standard Analog
I/O
9 Alarm 1
IND2_08
No Standard analogueI/O alarm
I2_TR Standard AnalogI/O
9 Normal 2
IND2_09
External digital I/Oalarm
I2_TR Ext. Digital I/O 10 Alarm 1
IND2_09
No External digital I/Oalarm
I2_TR Ext. Digital I/O 10 Normal 2
IND2_10
External analogue I/Oalarm
I2_TR Ext. Analog I/O 11 Alarm 1
Appendix B Event Texts Standard Drive, DRICONS
The Event Treat data base element in the Advant Station 500 Series of OperatorStation has a predefined configuration shown in Table 24.
IND2_10
No External analogueI/O alarm
I2_TR Ext. Analog I/O 11 Normal 2
IND2_1
1
Master - Follower
alarm
I2_TR Master - Follow
alarm
12 Alarm 1
IND2_11
Master - Followeralarm
I2_TR Master - Followalarm
12 Normal 2
IND2_1
4
Earth fault alarm I2_TR Earth fault 15 Alarm 1
IND2_1
4
No Earth fault alarm I2_TR Earth fault 15 Normal 2
Table 27. Predefined Event Treat for DRICONS
Property EVENT
330 331 332 333
AUDIBLE 1 0 1 1
AL_PRIO 2 4 2 2
Table 26. Event text for help MMCX data base element, EVENT Treat element 332 - 333
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 241/280
3BSE030340R4101 241
AL_TOBLK 0 1 0 0
AL_FRBLK 1 1 1 1
PERSISTB 0 1 0 0
TEXT_TOB 0 0 0 0
TEXT_FRB 0 0 0 0
TEXTCOMB 17 17 17 17
Standard Drive, DRICONS Appendix B Event Texts
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 242/280
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 byunmark the check box in the Config dialog (Figure 66).
Fatal, Error and Warning messages are all in the form:
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 243/280
3BSE030340R4101 243
<nnnn>-<s>-<text>
• 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
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 thepath are correct
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 244/280
244 3BSE030340R4101
Appendix C Messages Error Messages
Error Messages
Table 29 shows the Error numbers and texts
Table 29. Error Messages
Number Text Reason
2001 Syntax error in input file <path\filename> The syntax in the specified file is incorrect,correct
2002 Error-2002-OSCOLOR not found The specified token was not found in theconfiguration file, correct
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>
The specified file can not be accessed,check access rights
2008 Error-2008-Negative value not allowed
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 245/280
3BSE030340R4101 245
Error Messages Appendix C Messages
2009 Error-2009-FONT not found The specified token was not found in the
configuration file, correct2010 Error-2010-FONTNAME not found
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 E 2023 FROM t f d
Table 29. Error Messages (Continued)
Number Text Reason
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 246/280
246 3BSE030340R4101
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
Appendix C Messages Error Messages
2032 Error-2032-No Registry (CLSID) found
for <progid>
The CLSID token was not found in the
configuration file, correct2033 Error-2033-Cannot instantiate object for
<progid>Instantiation of the specified object failed,check that the object is correct installed
2034 Error-2034-Failed to doPersistStreamInit for <progid>
The specified object does not implementthe 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 inthe input (*.g) file
2037 Error-2037-Expected at least <number>parameters, got <number>
2038 Instance <object> not found in input file
<path\filename>
No entry for the specified object is found in
the configuration file(s).
Table 29. Error Messages (Continued)
Number Text Reason
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 247/280
3BSE030340R4101 247
Warning Messages Appendix C Messages
Warning Messages
Table 30 shows the Warning numbers and texts
Table 30. Warning Messages
Number Text Reason
1001 Warning-1001-No center found for the threepoints: <point>,<point>, <point>,<point>
1002 Warning-1002-No Configuration file for<object>
No configuration file found for the object,Create and include
1003 Warning-1003-No Configuration file for<object>
1004 Warning-1004-No Configuration file for<object>
1005 Warning-1005-Cannot create OLE font for<object>
Internal error when creating thespecified font
1006 Warning-1006-Cannot set property<property> for <object>
An objects property could not be set.Check the configuration file for thatobject
1007 Warning-1007-Invalid Command/Attribute,[Number,Type] = [<number>,<type>]
Internal error when accessing the object
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 248/280
248 3BSE030340R4101
1008 Warning-1008-Unknown Command =<command>
The command is unknown
1009 Warning-1009-<attrib>=<value> alreadydefined with <attrib>=<value>, ignoring newdefinition: <value>
An entry in the configuration files aredouble defined. Second definition will beignored
1010 Warning-1010-<attrib>=<value> alreadydefined with <attrib>=<value>, ignoring newdefinition: <value>
1011 Warning-1011-<attrib>=<value> alreadydefined with <attrib>=<value>, ignoring newdefinition: <value>
Appendix C Messages Warning Messages
1012 Warning-1012-Include File <path/filename>
already read
A circular reference in the include files.
Check and correct the #includestatements
1013 Warning-1013-Failed to create stream A stream could not be created/read
1014 Warning-1014-Failed to save stream
1015 Warning-1015-Failed to set seek pointer Failed to manipulate the binary outputfile
1016 Warning-1016-Failed to get global handle
1017 Warning-1017-Failed to set persist data
1018 Warning-1018-No vbcolor defined foroscolor=<color>
The specified color is not specified in theconfiguration files. Correct.
Table 30. Warning Messages (Continued)
Number Text Reason
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 249/280
3BSE030340R4101 249
Warning Messages Appendix C Messages
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 250/280
250 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 alarmsin your system. An example of a typical System Alarm List is presented in
Figure 89.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 251/280
3BSE030340R4101 251
The different columns in the System Alarm list are:
• Event Time
• Condition
• Object Name
• Message Description
Figure 89. System Alarm List
Appendix D System Alarm List
When you have located the Controller where the problem resides, bring up theSystem Alarm List on that Controller object (Control Structure). This gives you adedicated system alarm list for that Controller helping you to close in on theproblem. The System Alarms are in plain text and should help you to continue withyour fault tracing.
Advant Master System Alarms
The most important system alarms in 800xA for Advant Master are described in thetable 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 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 thecontroller(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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 252/280
252 3BSE030340R4101
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
available through this Connectivity
Server Node.
Appendix D System Alarm List
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
available through this ConnectivityServer 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 lostcontact with the RTA board.
This indicates that no data from the
controller(s) will be available through
this Connectivity Server Node.
RTA Board startup failed This indicates that no data from the
controller(s) will be available through
this Connectivity Server Node.
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
Message Description Extended Description
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 253/280
3BSE030340R4101 253
For more information about Operator Workplace System Alarms see Industrial IT
800xA, System, Operator Workplace Configuration.
g y
unless the address is set on the RTA
Board.
Appendix D System Alarm List
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 254/280
254 3BSE030340R4101
Appendix E Control Aspects
RTA Board Control Aspect
The RTA - Real-Time Accelerator Board - is an intelligent communication board forconnection to the MasterBus 300 network on which the AC 400 Controllerscommunicate. The RTA Board Control aspect makes it possible to perform somemaintenance and fault tracing work on the board.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 255/280
3BSE030340R4101 255
Appendix E Control Aspects
The RTA Board aspect is located on the RTA Board object under the network objectin the Control Structure. See Figure 90 for a fast location of the RTA Board controlobject and its aspects.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 256/280
256 3BSE030340R4101
Select the RTA Board Control aspect using any of the possible techniques for aspectselection.
The aspect has three tabs:
• 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.
Figure 90. Locating the RTA Board Control Aspect
Appendix E Control Aspects RTA Board Control Tab
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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 257/280
3BSE030340R4101 257
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 startsthe RTA Board in Operational mode.
Stop
Stops the RTA Board. A warning message, see Figure 92, will pop-up and must beacknowledged before the stop command is executed.
RTA Board Control Tab Appendix E Control Aspects
Get Status
Requests the current status from the RTA Board, and presents the result in thewindow. (Status is also updated cyclically).
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 controlthe process during the time the RTA Board is stopped.
Table 31. RTA Board Status
Status text:
RTA Board....Comment
Running Normal state. Everything OK
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 258/280
258 3BSE030340R4101
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, networkaddress not set
Network and Node must be set before the RTA canbe started
Appendix E Control Aspects RTA Board - Network and Node Configuration Tab
RTA Board - Network and Node Configuration Tab
You use this tab to change the network and node addresses on the MB 300/AC 400network.
Start failed There are a number of potential possible causes:One of the files required for boot does not exist orThe 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 havetried to find the cause repeatedly, a reinstallation isadvised. If reinstallation fails, the RTA Board couldbe out of order.
Stop failed Bootstrapper file not found, see Start failed
Table 31. RTA Board Status (Continued)
Status text:
RTA Board....Comment
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 259/280
3BSE030340R4101 259
Figure 93. RTA Set Network and Node
RTA Board Configuration Tab Appendix E Control Aspects
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.
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 mustrestart the RTA Board to get the new network/node address to take effect (see
You must be very careful when setting up network and node numbers. If you gettwo nodes with identical addresses, the entire network communication could bedisturbed with unpredictable consequences. Changing network and node
numbers should normally only be necessary when the control network isrearranged.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 260/280
260 3BSE030340R4101
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 andsetup the configuration for the RTA Board.The window contains the following:
Appendix E Control Aspects Control Connection Aspect (CCA)
RTA Board Config
Starts the On-line Builder tool that is used for configuration of the database on theRTA Board.
Control Connection Aspect (CCA)There is a CCA for all Process and system objects. The CCA:s can be useful to traceproblems specific for a certain object or for the presentation of an object. The CCAhas four views, here is a short description of the views and how you can use them inyour trouble shooting.
The CCA Property viewThe CCA Property view, see Figure 94, gives you a list of all the attributes, theirdata 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.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 261/280
3BSE030340R4101 261
Use this view to verify the attribute values of an object, how they are configured andthe current attribute values to compare with other presentations of it. If you suspect
Figure 94. The CCA Property View
CCA Property Info Appendix E Control Aspects
an error in a node, an I/O board or a transducer, you can use the CCA:s to narrow inon the problem by verifying which objects that are available over the network andwhich are not - and what their status attributes tell you.
CCA Property InfoThe Property Info view presents all details about the selected property. An exampleof a Property Info view is found in Figure 95.
The CCA Property view gives you a complete list of attributes, their names, datatype, access.
A “-” before the update rate value enables “on event” updating, of the values inbetween the cyclic updates according to AC 400 Event handling. If you locallychange the update rate in a graphic display, “ - “ must be included if you want the“on event” updating to be activated.
The Property Info view includes the possibility to set the definitions for theProperty values. To define property value handling and to set these values could
severely affect the control of the industrial process, including loosing control ofthe process. This functionality is only included for testing and fault tracing, andshould not be used during normal operation.
Do not change any Property values unless you are fully aware of all theconsequences.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 262/280
262 3BSE030340R4101
Appendix E Control Aspects CCA Property Info
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.
Figure 95. CCA - Property Information
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 263/280
3BSE030340R4101 263
• 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.
CCA - Additional info Appendix E Control Aspects
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 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 thediscrete points in trend curves: Stepped (value is constant between points) orInterpolated (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 presentationmode in Trace presentations: Stepped or Interpolated, see Industrial IT 800xA,
System Operator Workplace Configuration for more information
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 controlof the industrial process, including loosing control of the process.This functionality is only included for testing fault tracing, and should not beused during normal operation.
Do not change any Additional Info values unless you are fully aware of all theconsequences.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 264/280
264 3BSE030340R4101
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:
• The MasterBus 300 address: Network number, Node number, Logical file
number, Logical record number, Reference type.• The ID number of each attribute.
Appendix E Control Aspects CCA MasterBus 300
You can enter Network and Node number in this view. These are the only valuesthat you should modify. This information is mainly intended for fault tracing and thesupplier’s maintenance work.
You shall never modify or change the LF, LR, or RefType values. This willcause several functions to stop working.
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 265/280
3BSE030340R4101 265
CCA MasterBus 300 Appendix E Control Aspects
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 266/280
266 3BSE030340R4101
Appendix F OPC Properties
OPC object type properties
The following table lists process objects and the properties that supports cyclicsubscriptions.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
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 267/280
3BSE030340R4101 267
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
Appendix F OPC 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,B10_VAL, B11_VAL, B12_VAL, B13_VAL, B14_VAL, B15_VAL,B16_VAL, B17_VAL, B18_VAL, B19_VAL, B20_VAL, B21_VAL,B22_VAL, B23_VAL, B24_VAL, B25_VAL, B26_VAL, B27_VAL,B28_VAL, B29_VAL, B30_VAL, B31_VAL, I_VAL, IL_VAL,
Table 32. Properties supporting cyclical subscriptions via OPC (Continued)
Object Type Properties
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 268/280
268 3BSE030340R4101
R_VAL, VALUE
Appendix F OPC Properties
DRICONE, DRICONS,GROUP, MOTCON,
MOTCONI, VALVECON
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_IND1_07, AU_IND1_08, AU_IND1_09, AU_IND1_10,AU_IND1_11, AU_IND1_12, AU_IND1_13, AU_IND1_14,AU_IND1_15, AU_IND2_00, AU_IND2_01, AU_IND2_02,AU_IND2_03, AU_IND2_04, AU_IND2_05, AU_IND2_06,AU_IND2_07, AU_IND2_08, AU_IND2_09, AU_IND2_10,AU_IND2_11, AU_IND2_12, AU_IND2_13, AU_IND2_14,AU_IND2_15, IND1, IND1_00, IND1_01, IND1_02, IND1_03,IND1_04, IND1_05, IND1_06, IND1_07, IND1_08, IND1_09,IND1_10, IND1_11, IND1_12, IND1_13, IND1_14, IND1_15,IND2, IND2_00, IND2_01, IND2_02, IND2_03, IND2_04,IND2_05, IND2_06, IND2_07, IND2_08, IND2_09, IND2_10,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_05, INTWA_06, INTWA_07, INTWA_08, INTWA_09,INTWA_10, INTWA_11, INTWA_12, INTWA_13, INTWA_14,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,
Table 32. Properties supporting cyclical subscriptions via OPC (Continued)
Object Type Properties
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 269/280
3BSE030340R4101 269
INTWB_14, INTWB_15
Appendix F OPC 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_08, PC_ST_09, PC_ST_10, PC_ST_11, PC_ST_12,PC_ST_13, PC_ST_14, PC_ST_15, PC_ST_16, PC_ST_17,PC_ST_18, PC_ST_19, PC_ST_20, PC_ST_21, PC_ST_22,PC_ST_23, PC_ST_24, PC_ST_25, PC_ST_26, PC_ST_27,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),
Table 32. Properties supporting cyclical subscriptions via OPC (Continued)
Object Type Properties
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 270/280
270 3BSE030340R4101
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,
Appendix F OPC Properties
PIDCON 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_BELOW_L1 (TS_MV<L1), TS_MV_ABOVE_H1(TS_MV>H1), TS_DEV_BELOW_L (TS_DEV<L),TS_DEV_ABOVE_H (TS_DEV>H), TS_MV_BELOW_L2(TS_MV<L2), TS_MV_ABOVE_H2 (TS_MV>H2),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)
Table 32. Properties supporting cyclical subscriptions via OPC (Continued)
Object Type Properties
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 271/280
3BSE030340R4101 271
REPEAT_F1_FAIL_CTRL, AU_MV_BELOW_L2 (AU_MV<L2),AU_MV_ABOVE_H2 (AU_MV>H2), ALARM_F2_BLK,ALARM_F2_PERIOD_BLK, PRINT_F2_BLK,REPEAT_F2_FAIL_CTRL, STATUS_1, STATUS_2, STATUS_3,STATUS_4
Appendix F OPC Properties
PIDCONA 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
Table 32. Properties supporting cyclical subscriptions via OPC (Continued)
Object Type Properties
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 272/280
272 3BSE030340R4101
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,
Appendix F OPC Properties
PIDCONA (cont.) ALARM_F1_PERIOD_BLK, PRINT_F1_BLK,REPEAT_F1_FAIL_CTRL,AU_MV_BELOW_L2,
AU_MV_ABOVE_H2, ALARM_F2_BLK,ALARM_F2_PERIOD_BLK, PRINT_F2_BLK,REPEAT_F2_FAIL_CTRL, ALARM_F4_BLK,ALARM_F4_PERIOD_BLK, PRINT_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<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, SPARE_TS_05,TS DCM ERROR TS PC BLK TS SERVUC TS HW ERR
Table 32. Properties supporting cyclical subscriptions via OPC (Continued)
Object Type Properties
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 273/280
3BSE030340R4101 273
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_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
Appendix F OPC 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
Table 32. Properties supporting cyclical subscriptions via OPC (Continued)
Object Type Properties
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 274/280
274 3BSE030340R4101
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
Numerics800xA for Advant Master Product 23
Functionality 24Hardware and Software requirements 24Product features 23
800xA for Advant MasterProductProduct overview 23
AAlarm and Event List 34
BBackup and Restore 152Building Control structure
Create FCB source file 53Demo structure 57Off-line from FCB source file 53Test structure 57
CClock Master
800xA for Advant Master 31
AC 400 Series Controller 29
Property information 262Property view 261
DDisplay conversion
Colors.cnf file 124Converter limitations 134
Customize configuration files 123Deploy graphic display 133Dynamic.cnf file 127Edit converted display 132Fonts.cnf file 124Import Master displays 129Replace Master graphic elements 123Test graphic display 133
Display converterAdd-in to Graphics Builder 122Considerations 122Error messages 245Fatal messages 244Getting started 122Introduction 121
Warning messages 248
INDEX
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 275/280
3BSE030340R4101 275
AC 400 Series Controller 29Configuration 25, 105, 119
Before you start 25Examples 103Existing plant 28Getting started 27New system 28Quick List 98
Control Connection Aspect 261Additional information 264MasterBus 300 264
Warning messages 248
EEVENT elements 166Event text 107
Analog Input signal AI 171Analog Output signal AO 172Binary object GENBIN 185
Digital Input signal DI 173Digital Output signal DO 174Group alarm GRPALARM 199
Index
Group start GROUP 197Manual station MANSTN 181Motor Control MOTCON 191Process Controller PIDCON 177Process Controller PIDCONA 179Ratio station RATIOSTN 182
Sequence SEQ 174Standard event text 62User defined controller GENCON 183User defined object GENUSD 188User-defined alarm and event text 63Valve control VALVECON 194
EVENT TREAT 160Event treat 169
EVENT TREAT propertiesAL_FRBLK 161AL_PRIO 160AL_TOBLK 161AUDIBLE 160PERSISTB 161TEXT_FRBLK 161TEXT_TOBLK 161TEXTCOMB 162
Event treatment 60Overview 157, 255Standard event text 61 to 62User defined alarm text 63User defined event text 63
EVENT_TREAT 107 to 108
F
MMB300 Upload
Upload from AC400 controller 46, 48
PProperty text 107
RRTA Board - Get status 257RTA Board configuration 34
Character Conversion 50Network and Node numbers 34Save configuration 260
Setup Network and Node 259Start On-Line Builder 260Start/Stop of RTA 257
SSimulated process data
Export control structure 58Property signal generator 57
System Alarms 150Alarm list for Controllers 151, 252Alarm list for network 151, 251Create and Setup 150
System Error Messages 135System Status
Controller node 144Network 138Operator Workplace Node 139
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 276/280
276 3BSE030340R4101
FFault Tracing 135
HHardware indicators 135Hot Keys in 800xA for Advant Master 37
LLog index 72
Operator Workplace Node 139
TTEXT 107, 109TTD Logs 69
Create log template 86Create TTD log in a controller 93
Log templateLog definition 74Node configuration, controller details 79
Index
Node configuration, Download tocontroller 81
Node configuration, Main view 76Node configuration, Upload from
controller 80Setup in IndustrialIT 800xA System 84
View TTD log in a controller 85
UUploading
MB300 45
W
Where to start 12
XX font 125
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 277/280
3BSE030340R4101 277
Index
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 278/280
278 3BSE030340R4101
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 279/280
8/10/2019 Advant Configuration
http://slidepdf.com/reader/full/advant-configuration 280/280
3BSE030340R4101. Printed in Sweden June 2005Copyright © 2003–2005 by ABB. All Rights Reserved ® Registered Trademark of ABB.™ Trademark of ABB.
Automation Technology Products
Mannheim, Germany
www.abb.de/processautomation
email:marketing.control-products@de.abb.com
Automation Technology Products
Västerås, Sweden
www.abb.com/processautomation
email: processautomation@se.abb.com
Automation Technology Products
Wickliffe, Ohio, USA
www.abb.com/processautomation
email: industrialitsolutions@us.abb.com
http://www.abb.com/control
top related