Industrial IT 800xA System - 800xA for Melody ... - AoteWell

IndustrialIT 800xA - System 800xA for Melody System Version 4.1

Configuration

IndustrialIT 800xA - System 800xA for Melody System Version 4.1

Configuration

NOTICE The information in this document is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document. In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB be liable for incidental or consequential damages arising from use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. This product meets the requirements specified in EMC Directive 89/336/EEC and in Low Voltage Directive 72/23/EEC. Copyright © 2003-2005 by ABB. All rights reserved. Release: Document number:

May 2005 3BDD011741R4101

TRADEMARKS Registrations and trademarks used in this document include: Windows

Registered trademark of Microsoft Corporation.

ActiveX

Registered trademark of Microsoft Corporation.

PostScript

Registered trademark of Adobe Systems Inc.

Acrobat Reader

Registered trademark of Adobe Systems Inc.

Industrial IT

Trademark of ABB.

TABLE OF CONTENTS About This Book General ............................................................................................................................17 Use of Warning, Caution, Information, and Tip ..............................................................17 Document Conventions ...................................................................................................18 Related Documentation ...................................................................................................19

Section 1 - Introduction Intended User...................................................................................................................21 Functional Description ....................................................................................................21 IndustrialIT Melody System Structure.................................................................22 IndustrialIT Melody Entities ................................................................................23 IndustrialIT Melody Context and Structure .........................................................24 Supported Operating Systems ..............................................................................27 Engineering ..........................................................................................................27 Base Configuration...............................................................................................28 Topology .............................................................................................................28 Engineering Settings ............................................................................................29 System Definition.................................................................................................29 Alarm and Event System......................................................................................29 Time Synchronization ..........................................................................................29 Backup and Restore..............................................................................................29 Automation Classes Configuration ......................................................................29 Special Functions .................................................................................................29 Technical Data......................................................................................................30 Quality Definition ................................................................................................30 Base Configuration Overview ..............................................................................30

3BDD011741R4101

5

Table of Contents

Section 2 - Base Configuration Install DHCP Server........................................................................................................ 31 Modify Etc/host File ....................................................................................................... 32 Create Base Topology ..................................................................................................... 32 Object List View .................................................................................................. 33 Tabs

............................................................................................................ 33

Body

............................................................................................................ 33

Footer

............................................................................................................ 33

Design Life Cycle Options .................................................................................. 35 How to Edit Objects............................................................................................. 36 Adding Connectivity Server to the System.......................................................... 37 Adding Event Concentrator to the System........................................................... 41 Adding Coupling Modules of Type CCO 30, CMC 70 and PM 875................... 44 Deleting Units or Areas ....................................................................................... 48 Common Object Properties.................................................................................. 49 Settings ............................................................................................................................ 52 Configuration Server............................................................................................ 53 Options

............................................................................................................ 53

Audit Trail............................................................................................................ 59 Synchronizing Engineering Data .................................................................................... 61 Configurator Admin............................................................................................. 61 Auto Configurator ................................................................................................ 64 OPC Data Source Definition ........................................................................................... 66 Tag Importer .................................................................................................................... 69

Section 3 - Topology Operator Network Redundancy ........................................................................... 74 Boundary Conditions for HW Planning............................................................... 74 Topology Planning Software ........................................................................................... 75 Control Structure................................................................................. 75 Functional Structure............................................................................ 76 Base Topology Configuration ......................................................................................... 78

6

3BDD011741R4101

Table of Contents

Creating a new Operator User ..............................................................................78 Affinity

.............................................................................................................82

Control Structure Import ......................................................................................89

Section 4 - Engineering Workflow Bulk Data Management ...................................................................................................93 Import/Export ..................................................................................................................95 Alarms and Events...........................................................................................................96 Object Life Cycle ............................................................................................................97 Operating Parameters ......................................................................................................97

Section 5 - System Definition System Definition Object ..............................................................................................100 Configurable Text ..........................................................................................................101 Indexed Text Tab ................................................................................................101 Event Comment.................................................................................103 Text Selector Text..............................................................................103 Engineering Unit Descriptor .............................................................103 Logic State Descriptor.......................................................................105 Alarm Priority Text ...........................................................................105 Melody System Events......................................................................106 Substitutable Text Tab ........................................................................................107 Quality Text Tab ............................................................................................................108 Management Tab ...........................................................................................................110 Project History Tab ........................................................................................................110

Section 6 - Alarm and Event System Alarm and Event Service Provider ................................................................................111 Melody 800xA Process Portal Process Events...................................................114 Melody 800xA Process Portal System Events ...................................................118 Melody Message System ...............................................................................................119 Melody Message Transport and Buffering.........................................................120 Melody Process Messages..................................................................................122

3BDD011741R4101

7

Table of Contents

System and Process Interface Messages ............................................................ 124 Alarm & Event System Definitions and Overview ....................................................... 125 Alarms and Events ............................................................................................. 126 Event Point......................................................................................................... 126 Event Distribution System ................................................................................. 127 Event Concentrators........................................................................................... 127 Local Event Concentrator ................................................................. 127 Client Event Concentrator................................................................. 128 Event Classifications.......................................................................................... 128 Event Categories ................................................................................................ 128 Event Point Definition................................................................................................... 129 Event Point Attributes........................................................................................ 129 Behavioral Attributes ......................................................................................... 133 Informational Attributes..................................................................................... 134 Event Point State Attributes............................................................................... 136 Dual Event Point Behavior ................................................................................ 138 Non Dual Event Point Behavior......................................................................... 138 Redundancy................................................................................................................... 138 Message Generation.......................................................................... 139 Message synchronization .................................................................. 140 Severity, OPC Severity and Device Priority.................................................................. 140 OPC Severity...................................................................................................... 140 Client Severity.................................................................................................... 140 Device Severity (Melody Priorities) .................................................................. 141

Section 7 - Time Synchronization Operation Overview........................................................................................... 143 Time Adjustment................................................................................................ 145 800xA Process Portal Time Server Configuration............................................. 146 800xA Process Portal Time Server Handler Configuration ............................... 147 Windows Time Synchronization Service (W32Time) ....................................... 148 Master Clock Configuration in Melody ............................................................. 149 Configuration of Melody Server as Time Master .............................................. 150

8

3BDD011741R4101

Table of Contents

Deleting all Services that are not Time Master ..................................................152 Melody TimeSync Daemon installation.............................................................153 DHCP Configuration for Time Synchronization................................................154 Checking the Configuration with Melody Analyser ..........................................155 Checking the Master Time Daemon with TsyncCTRL Tool .............................155 Multiple Network Adaptors configuration specifics ..........................................156 Multiple Network Adaptors Binding example ...................................................159 Time Synchronization Options...........................................................................160 Melody Server SYSLOG Time Synchronization Diagnostic.............................161

Section 8 - Backup and Restore Access............................................................................................................................163 Function .........................................................................................................................164 Backup Industrial IT Melody Composer .......................................................................164 Backup ConfigServer.....................................................................................................164 Restore ConfigServer.....................................................................................................166

Section 9 - Melody Automation Classes MelodyAnalog – Analog monitoring.............................................................................170 Configuration .....................................................................................................170 Composer function block and signal definitions...............................170 Event typical ....................................................................................174 Automation class................................................................................................175 Structure

....................................................................................175

Calculated atoms ...............................................................................178 MelodyAnMon – Analog monitoring ............................................................................179 Configuration .....................................................................................................179 Composer function block and signal definitions...............................179 Event typical ....................................................................................181 Automation class................................................................................................185 Structure

....................................................................................185

Control

....................................................................................189

Calculated atoms ...............................................................................190

3BDD011741R4101

9

Table of Contents

Melody AnOut – Analog output ................................................................................... 191 Configuration ..................................................................................................... 191 Composer function block and signal definitions .............................. 191 Event typical .................................................................................... 192 Automation class................................................................................................ 196 Structure

.................................................................................... 196

Control

.................................................................................... 198

Melody APID controller ............................................................................................... 200 Configuration ..................................................................................................... 200 Composer function block and signal definitions .............................. 200 Event typical .................................................................................... 203 Automation class................................................................................................ 213 Structure

.................................................................................... 213

Control

.................................................................................... 223

Calculated atoms............................................................................... 225 MelodyBFlagx – Block flag.......................................................................................... 227 Configuration ..................................................................................................... 227 Composer function block and signal definitions .............................. 227 Event typical .................................................................................... 229 Automation class................................................................................................ 232 Structure

.................................................................................... 232

Control

.................................................................................... 236

Calculated atoms............................................................................... 237 MelodyBinary – Binary................................................................................................. 238 Configuration ..................................................................................................... 238 Composer function block and signal definitions .............................. 238 Event typical .................................................................................... 240 Automation class................................................................................................ 241 Structure

.................................................................................... 241

Calculated atoms............................................................................... 242 Melody CLCx controller ............................................................................................... 243 Configuration ..................................................................................................... 244

10

3BDD011741R4101

Table of Contents

Composer function block and signal definitions...............................244 MelodyCLC automation class...........................................................246 MelodyCLCD automation class........................................................247 MelodyCLCM automation class .......................................................248 Event typical ....................................................................................249 Automation class................................................................................................253 Structure

....................................................................................253

Control

....................................................................................264

Calculated atoms ...............................................................................265 MelodyCOA – Change over automatic .........................................................................270 Configuration .....................................................................................................270 Composer function block and signal definitions...............................271 Event typical ....................................................................................272 Automation class................................................................................................275 Structure

....................................................................................275

Control

....................................................................................278

MelodyCount – Counter ................................................................................................280 Configuration .....................................................................................................280 Composer function block and signal definitions...............................280 Automation class................................................................................................282 Structure

....................................................................................282

Calculated atoms ...............................................................................284 MelodyDos – Dosing circuit .........................................................................................285 Configuration .....................................................................................................285 Composer function block and signal definitions...............................285 Event typical ....................................................................................288 Automation class................................................................................................293 Structure

....................................................................................293

Control

....................................................................................298

Calculated atoms ...............................................................................299 MelodyIDF – Individual control....................................................................................300 Configuration .....................................................................................................300

3BDD011741R4101

11

Table of Contents

Composer function block and signal definitions .............................. 301 Event typical .................................................................................... 302 Automation class................................................................................................ 307 Structure

.................................................................................... 307

Control

.................................................................................... 311

Calculated atoms............................................................................... 312 MelodyOPA – Binary memory...................................................................................... 314 Configuration ..................................................................................................... 314 Composer function block and signal definitions .............................. 314 Event typical .................................................................................... 316 Automation class................................................................................................ 320 Structure

.................................................................................... 320

Control

.................................................................................... 323

Calculated atoms............................................................................... 324 MelodySel – Preselection.............................................................................................. 325 Configuration ..................................................................................................... 325 Composer function block and signal definitions .............................. 326 Event typical .................................................................................... 327 Automation class................................................................................................ 330 Structure

.................................................................................... 330

Control

.................................................................................... 333

Melody SFC – Sequence control................................................................................... 334 Configuration ..................................................................................................... 334 Composer function block and signal definitions .............................. 335 Event typical .................................................................................... 337 Automation class................................................................................................ 342 Structure

.................................................................................... 342

Control

.................................................................................... 352

Calculated atoms............................................................................... 353 MelodySFlagx – Single flag.......................................................................................... 355 Configuration ..................................................................................................... 355 Composer function block and signal definitions .............................. 355

12

3BDD011741R4101

Table of Contents

Event typical ....................................................................................357 Automation class................................................................................................357 Structure

....................................................................................357

Control

....................................................................................359

Calculated atoms ...............................................................................359 MelodySwClock – Calendar and timing function .........................................................360 Configuration .....................................................................................................360 Composer function block and signal definitions...............................360 Event typical ....................................................................................361 Automation class................................................................................................363 Structure

....................................................................................363

Control

....................................................................................365

Calculated atoms ...............................................................................366 MelodyTCount – Time and pulse counter ......................................................................................368 Configuration .....................................................................................................368 Composer function block and signal definitions...............................369 Event typical ....................................................................................370 Automation class................................................................................................372 Structure

....................................................................................372

Control

....................................................................................375

Calculated atoms ...............................................................................375 MelodyTotal – Quantity value acquisition..................................................................................377 Configuration .....................................................................................................377 Composer function block and signal definitions...............................377 Event typical ....................................................................................379 Automation class................................................................................................381 Structure

....................................................................................381

Control

....................................................................................384

Calculated atoms ...............................................................................385

Section 10 - Special Functions

3BDD011741R4101

13

Table of Contents

Sequence Control (SFC) ............................................................................................... 387 IDF Viewer .................................................................................................................... 389 Data Exchange to AC 800M ......................................................................................... 392 Additional Connection to OperateIT B or Maestro UX................................................ 394 Fieldbus Support ........................................................................................................... 394 Security ......................................................................................................................... 395 Batch Support................................................................................................................ 396 Information Manger ...................................................................................................... 396

Appendix A - Technical Data Sizing Data (800xA for Melody) ....................................................................... 397 Sizing Data (Melody)......................................................................................... 398 Performance ....................................................................................................... 398 Hardware Preconditions..................................................................................... 399 Melody Connectivity Server ............................................................. 399 Melody Config Server....................................................................... 399 Supported Operating Systems............................................................................ 400 Supported Composer Version ............................................................................ 400

Appendix B - Quality Definition Description .................................................................................................................... 401 Indicators....................................................................................................................... 401 OPC Quality Definition................................................................................................. 401 800xA for Melody Quality Definition .......................................................................... 403 Tag.Property Quality for Process Properties ................................................................. 404 Tag.Property Quality for Computed Properties............................................................. 404 Tag.Property Quality for Configuration Data................................................................ 404 Tag.Property Quality for Event Point Related Properties ............................................. 405 Tag Quality .................................................................................................................... 405 Properties .......................................................................................................... 405

14

Quality

.................................................................................... 405

Bad

.................................................................................... 405

Suspended

.................................................................................... 406

3BDD011741R4101

Table of Contents

800xA for Melody Quality Information.............................................................406 OPC Quality Flags.........................................................................................................407 Quality Bits ........................................................................................................408 Substatus Bits .....................................................................................................408 Limit Bits ...........................................................................................................410 OPCHDA Quality...............................................................................................411

Appendix C - Base Configuration Overview Configuration Overview Part I ......................................................................................414 Configuration Overview Part II .....................................................................................415

Appendix D - Hints, Handlings and Workarounds Starting a redundant pair of Connectivity Server ..........................................................417 Hints on Partitioning......................................................................................................418 Partitioning of a Melody Connectivity Server ...................................................418 Partitioning of a Melody Config Server .............................................................418

3BDD011741R4101

15

Table of Contents

16

3BDD011741R4101

About This Book General Use this section as a guide to the conventions and terminology used throughout this book.

Use of Warning, Caution, Information, and Tip This publication includes Warning, Caution, and Information where appropriate to point out safety related or other important information. It also includes Tip to point out useful hints to the reader. The corresponding symbols should be interpreted as follows: Electrical warning icon indicates the presence of a hazard which could result in electrical shock. Warning icon indicates the presence of a hazard which could result in personal injury. Caution icon indicates important information or warning related to the concept discussed in the text. It might indicate the presence of a hazard which could result in corruption of software or damage to equipment/property. Information icon alerts the reader to pertinent facts and conditions.

Tip icon indicates advice on, for example, how to design your project or how to use a certain function

3BDD011741R4101

17

Document Conventions

About This Book

Although Warning hazards are related to personal injury, and Caution hazards are associated with equipment or property damage, it should be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process performance leading to personal injury or death. Therefore, comply fully with all Warning and Caution notices.

Document Conventions The following conventions are used for the presentation of material: •

The words in names of screen elements (for example, the title in the title bar of a window, the label for a field of a dialog box) are initially capitalized.

•

Capital letters are used for the name of a keyboard key if it is labeled on the keyboard. For example, press the ENTER key.

•

Lowercase letters are used for the name of a keyboard key that is not labeled on the keyboard. For example, the space bar, comma key, and so on.

•

Press CTRL+C indicates that you must hold down the CTRL key while pressing the C key (to copy a selected object in this case).

•

Press ESC E C indicates that you press and release each key in sequence (to copy a selected object in this case).

•

The names of push and toggle buttons are boldfaced. For example, select OK.

•

The names of menus and menu items are boldfaced. For example, the File menu.

•

–

The following convention is used for menu operations: MenuName > MenuItem > CascadedMenuItem. For example: select File > New > Type.

–

The Start menu name always refers to the Start menu on the Windows ® Task Bar.

System prompts/messages are shown in the Courier font, and user responses/input are in the boldfaced Courier font. For example, if you enter a value out of range, the following message is displayed: Entered value is not valid. The value must be 0 to 30.

18

3BDD011741R4101

About This Book

Related Documentation

Related Documentation The following is a listing of documentation related to the Configuration part of the Industrial IT 800xA for Melody software application. Category 800xA for Melody as part of IIT 800xA System

Title

Description

Industrial IT 800xA - System, 800xA for Melody Operation (Utility)

3BDD011742R4001

Industrial IT 800xA - System, 800xA for Melody Operation (Process Industry)

3BDD011778R4001

IIT 800xA Industrial IT 800xA - System, Installation System in Industrial IT 800xA - System, Post Installation Setup general Industrial IT 800xA - System, Topology Designer Industrial IT 800xA - Operations, Operator Workplace -

3BSE034678R4001 3BUA000156R4001 3BDS011225R4001 3BSE030322R4001

Configuration

misc.

Industrial IT, 800xA - System, Basic Operation

3BSE036903R4001

Industrial IT, 800xA - System, Extended Operation

3BSE036904R4001

Industrial IT 800xA - System, Configuration

3BDS011222R4001

Industrial IT 800xA - System, Automation System Network, Design and Configuration

3BSE034463R4001

CMC 70 Controller

TI 30/72-2326 EN

Symphony Analyser (Diagnostic Tool)

TI 30/72-8062 EN

SFC-Editor

TI 30/72-8014 EN

FDT-Field Device Tool for Composer

TI 30/72-8023 EN

Hardware, Software and Backup

TI 30/72-8001 EN

Importing and exporting project data

TI 30/72-8010 EN

3BDD011741R4101

19

Related Documentation

20

About This Book

3BDD011741R4101

Section 1 Introduction Overview 800xA for Melody is an integrated part of the IndustrialIT System 800xA. It communicates through Connector/Adapter OPC ® DA and standard AE interfaces. This instruction describes the configuration requirements to use the 800xA for Melody system specific functions through IndustrialIT System 800xA.

Intended User This instruction is intended for use by personnel responsible for configuring 800xA for Melody to operate as part of IndustrialIT System 800xA. This instruction assumes the configuration engineer or technician is familiar with Windows 2000 / Windows 2003, Microsoft ® Internet Explorer, and the installed IndustrialIT Melody control system including the Composer for Melody configuration.

Functional Description The 800xA for Melody component connects the ControlIT Melody and 800xA Process Portal to an IndustrialIT 800xA distributed process management and control system. Using a series of integrated IndustrialIT 800xA Melody control units, the system allows monitoring and control of process variables such as flow rate, temperature, and pressure according to a control configuration that the engineer or technician defines. A Melody control unit is a controller and its I/O devices connected for communication on control network. 800xA for Melody operates in the Windows 2000 / Windows 2003 environment on personal computer hardware. Using interactive process graphics, the operator can monitor and control all Analog loops and Digital devices interfaced to the network via Melody control units. 800xA for Melody also provides maintenance personnel

3BDD011741R4101

21

IndustrialIT Melody System Structure

Section 1 Introduction

with the capability to globally monitor the operating status of any system component on the network, and to diagnose component failures from any workstation.

IndustrialIT Melody System Structure The following figure gives an overview about IndustrialIT System 800xA - Melody:

Figure 1. IndustrialIT System 800xA Melody Overview

Multi function modules of type CMC 50 or CMC 60 use the CCO 30 coupling module for the connection to the 800xA Process Portal via 800xA for Melody.

22

3BDD011741R4101


IndustrialIT Melody Entities

IndustrialIT Melody Entities IndustrialIT System 800xA - Melody consists of the entities as shown in the following figure:

Figure 2. IndustrialIT System 800xA Melody Entities To enable the connectivity of the operator workplaces to the ControlIT Melody system part a Connectivity Server is needed. The Melody Connectivity is a standard connectivity server using the OPC connectivity to 800xA Process Portal. The Melody object types are needed to allow the creation of Melody objects and corresponding aspects. The object type encapsulates the knowledge on how to extract Melody information and how to operate e.g. Melody controllers. In order to enable life cycle support and automatic management of Melody objects and their aspects some Aspect Systems are needed. The object types and the life cycle related Aspect Systems are the major part of the so-called Melody System Extension. Because Melody covers different markets, different industries or even different customers different sets of faceplates or graphics are available at ABB market

3BDD011741R4101

23

IndustrialIT Melody Context and Structure


divisions. Therefore 800xA for Melody does not provide a set of faceplates and graphic symbols by default. For detailed information about the different sets of faceplates or graphics please contact sour local ABB supplier or your ABB project partner.

IndustrialIT Melody Context and Structure 800xA for Melody basically consists of five main parts: •

Melody Connectivity Server

Communicates with Melody Controllers and provides real-time data access between 800xA Process Portal and Melody Control network via OPC DA/AE interfaces. •

Config Server

Configures the Melody OPC Servers, stores the configuration data and manages configuration data life cycle. •

Configuration Management

Seamlessly integrates the Melody Connectivity into the IndustrialIT framework by uploading the configured tags into the Aspect Directory. •

Melody Object Types

Provides Object types for Melody Tag objects with pre-configured Control Connection Aspects •

Faceplates/Symbols

Enriches the Melody Object Types with graphical faceplates for operation of the Melody functions and with symbols for building process graphics displays. Faceplates and symbols are not integrated part of 800xA for Melody.

24

3BDD011741R4101



Figure 3. 800xA for Melody: Context and Structure The system components shown in Figure 3 have the following relations: 1.

Melody object types are imported into 800xA Process Portal during installation of the 800xA for Melody system extension. This does not include faceplates and symbols.

2.

On the Config Server runs a “Tag Importer” process that automatically updates the configuration database when the Melody Composer performs downloads of code with operations contents. The data is transferred using a special text file format.

3.

The Configuration Management runs a service (Auto-Configurator) hosted by the IndustrialIT System 800xA. This service monitors the configuration

3BDD011741R4101

25



database for changes. The Auto-Configurator communicates with the Config Server.

26

4.

The Configuration Management automatically creates/updates/deletes Tag objects and arranges them in the Control Structure as well as in the Functional Structure.

5.

Melody Connectivity Server is configured via DCOM (SQL-serverreplication).

6.

800xA Process Portal has real-time data access to Melody via the Melody OPC server, which provides standard OPC/DA and OPC/AE interfaces.

7.

The Melody OPC server communicates with the Melody units (CMC 70, PM875, CCO 30) via Ethernet.

3BDD011741R4101


Supported Operating Systems

Supported Operating Systems The following figure shows supported operating system variety:

Figure 4. 800xA for Melody: Supported Operating System Environment

Engineering The engineering workflow always starts in IndustrialIT Melody Composer and ends up in 800xA Process Portal and the control system. Composer supports bulk data actions and import of data reflecting the basic engineering like tag imports, signal lists, channel assignments and management of typicals to create instances of function charts by list based engineering. Engineering activities in IndustrialIT System 800xA colliding with Melody business rules will be rejected. The lifecycle of a IndustrialIT Melody object starts and ends in Composer. Aspects hosted by other than Melody Aspect Systems might extend Melody objects.

3BDD011741R4101

27

Base Configuration


When commissioning functionality planned in Composer the 800xA system relevant information will be generated by Composer and automatically uploaded into the IndustrialIT System 800xA core. Versioning of data is done according to the Melody life cycle model.

Figure 5. Basic IndustrialIT 800xA Melody Engineering Workflow

Base Configuration This section describes the basic configuration steps that are necessary after having finished the installation before starting to realize plant specific configuration settings.

Topology Hardware topology as well as software topology has to be planned and commissioned based on basic rules. The description of these rules affiliated to 800xA for Melody are part of this section.

28

3BDD011741R4101


Engineering Settings

Engineering Settings This section provides an overview of the basic system engineering when using 800xA for Melody.

System Definition System definition features such as security properties are defined in the system definition object.

Alarm and Event System The 800xA for Melody system provides services to define event conditions and client applications.

Time Synchronization 800xA for Melody provides the function of passing through the system time synchronization. The required settings are described in this section.

Backup and Restore The 800xA for Melody Backup or Restore feature allows the user to manually initiate a backup or restore that supports either the full backup or full restore of the SQL 800xA for Melody configuration contained in its SQL database.

Automation Classes Configuration The automation classes are the function diagrams for the automation functions in IndustrialIT System 800xA Melody. There will be a more detailed description of the automation classes in this section.

Special Functions This section describes functionality that is closely related to the 800xA for Melody system part but not or only partly integrated in the Connectivity itself.

3BDD011741R4101

29

Technical Data


Technical Data This appendix lists in tables technical data necessary for basic sizing and planning of IndustrialIT System 800xA Melody.

Quality Definition The purpose of this appendix is to describe the tag.property qualities in Melody Connect.

Base Configuration Overview This appendix shows the workflow during installation and base configuration of IndustrialIT System 800xA for Melody.

30

3BDD011741R4101

Section 2 Base Configuration Introduction After installation of the 800xA for Melody software according to the IndustrialIT 800xA System Installation Guide it is required to execute the following steps to finish the base configuration: 1.

Install DHCP Server (refer to Install DHCP Server on page 31)

2.

Modify etc/host file. (refer to Modify Etc/host File on page 32)

3.

Create Base Topology (using the Object List Tool; refer to Create Base Topology on page 32)

4.

Adjust Settings (refer to Settings on page 52)

5.

Synchronize Engineering Data (Start Configurator Admin or Start Auto Configurator) (refer to Synchronizing Engineering Data on page 61)

6.

Adjust OPC Data Source Definition (refer to OPC Data Source Definition on page 66)

7.

Adjust OPC Alarm and Events (refer to Section 6, Alarm and Event System)

8.

Set Time Synchronization (refer to Section 7, Time Synchronization)

9.

Start Tag Importer. (refer to Tag Importer on page 69)

10. Set Affinity (refer to Section 3, Topology)

Install DHCP Server The Melody Gateway CCO 30, CMC 70 or PM 875 gets its IP-address for communication with Operate IT from a DHCP-Server. This computer should be every time available. To support the availability the DHCP-Server should be

3BDD011741R4101

31

Modify Etc/host File

Section 2 Base Configuration

installed on PC´s which are installed as Windows 2000 or Windows 2003 Server nodes for 800xA Process Portal. Every time a CCO 30, CMC 70 or PM 875 starts after RESET or supply voltage interruption the CCO 30, CMC 70 or PM 875 requested the DHCP-Server for its IPAddress. If the DHCP-Server is not available the CCO 30, CMC 70 or PM 875 starts after a time-out of 5 minutes with its old IP-address. IP address reservations for coupling modules must be available.

Modify Etc/host File The entry of the EPC and the IP-address of the CCO 30, CMC 70 or PM 875 must be inserted into the file \windows\system32\drivers\etc\host on the Melody Connectivity Server nodes (e.g. 10.0.1.20 EP001A09). The assignment of the IP addresses to the CCO 30 / CMC 70 / PM 875 modules is also part of the CSE_conf file that is required for the normal operation of Composer and the Melody Analyser. If available the information can be taken over to the etc/host file.

Create Base Topology After installation of the 800xA for Melody software it is required to add the following components to the system: •

Connectivity Server (primary and backup)

•

Event Concentrator (local and client)

•

CCO 30 / CMC 70 / PM 875 modules (primary and backup)

For editing the object list go to: Start > All Programs > ABB Industrial IT 800xA > 800xA for Melody > Diagnostics > ObjectList The Configuration is also possible from the TagConfig Aspect in the Control Structure inside the Workplace.

32

3BDD011741R4101


Object List View

Object List View All Object List views have the same general appearance and behavior. The views are divided into three common areas: • Tabs. • Body. • Footer.

Tabs The tabs presented in a view depend on the type of object selected for Melody. Melody data that is common to multiple object types is presented in the same way to help make Melody tasks easier and to improve efficiency. The General and Version tabs are included for every object type.

Body The body area contains all of the configurable properties of the selected tab. The fields are only editable in the Design Life Cycle version of an object, when the user has Melody access rights, and after the user has locked the object for editing.

Footer The footer area shows general object information; contains controls to change the life cycle; and contains controls to edit, submit, and cancel changes (). Different buttons are available in the footer depending on the life cycle of the object as shown in Figure 6. Life Cycle

The Life Cycle field shows the life cycle of the object. This is a display only field. Locked By

The Locked By: field shows the name of the user that has locked the object for editing. If the object is not locked this field will be blank.

3BDD011741R4101

33

Footer


C H A N G E TO RU N

CO PY FOR D E S IG N

C H A N G E TO R E LE A S E

H E LP

D E LE T E T H IS V E R S IO N

C H A N G E TO O U T O F S E RV IC E

S U B M IT CHANGES

E D IT O B JE C T

CANCEL CHANGES T 050 33A

Figure 6. Life Cycles Validate Against

The Validate Against: shows the current method of validation. Objects in the Design Life Cycle present user selectable validation options. Objects in the release and Running Life Cycles show release and running validation respectively. Life Cycle

The life cycle buttons change the object to a desired life cycle. These buttons will be displayed or hidden based on the current life cycle and the user access rights. Delete Version

Deletes this version from the Melody Server. Copy for Design

Copies this object and creates a new object in design mode. The new object retains all of the configured properties of the original except for the ID. Submit Changes

Only visible when the object is being edited. It submits changes to the Melody Server.

34

3BDD011741R4101


Design Life Cycle Options

Edit Object

Locks the object and allows editing its definitions. This button is only enabled if the user has access rights, the object is not currently locked, and the object is in the Design Life Cycle. Cancel Changes

Only visible when the object is being edited. It cancels any changes without updating the Melody Server and unlocks the object.

Design Life Cycle Options Three different views are possible when an object is in the Design Life Cycle: unlocked, locked by current user, and locked by other user. The object becomes locked so only one user can edit it at a time. Clicking the edit object button () changes the view to the locked by user view. Any other users that call up the same object for viewing will see the locked by other user view. Unlocked

When an object in the Design Life Cycle is first called up, it is unlocked (unless it has already been locked by another user). Any user with access rights can edit the object. The body of the view contains view only fields. The life cycle of the object can be changed to release, run, or out of service when unlocked. Clicking a life cycle change button causes the Server to attempt to change the object to the selected life cycle. This involves obtaining a lock, performing a validation, and if successful, moving the object into the new life cycle. Locked by Current User

For an object in the Design Life Cycle, the Server attempts to obtain a lock when the edit object button is clicked. Once the lock has been obtained, the view changes to the locked by user view, which updates the Locked By: field and changes the fields within the body of the view from view only to editable. The life cycle of the object can be changed to release, run, or out of service when unlocked.

3BDD011741R4101

35

How to Edit Objects


Locked by Other User

For an object in the Design Life Cycle, the object is called up in the locked by other user view when another user is currently editing the object. In this case, the Locked By field will show the name of the user currently editing the object and the fields within the body of the view are view only. The locked by user is not updated automatically but only on interaction with the Melody Server. Release Life Cycle

In the Release Life Cycle, the user can view the object or change its life cycle. The Locked By: field is not visible. The validate against field is fixed to release. Running Life Cycle

In this life cycle, the user can view the object or change its life cycle. The Locked By: field is not visible. The validate against field is fixed to run.

How to Edit Objects Edit Mode

An object must be locked for editing before any changes to the Melody can be made. Only objects in the Design Life Cycle can be edited. Melody access right is required to edit an object. The object cannot be locked by another user to edit. To edit an object:

36

1.

Open the aspect view of the desired object using one of the Open options from the aspect view.

2.

Verify that the object is in the Design Life Cycle and is not locked by another user.

3.

Click the edit object button ().

3BDD011741R4101


Adding Connectivity Server to the System

Saving Changes

After changes have been made to an object they need to be submitted to the Connectivity Server. During the submission they are also validated according to their life cycle. To save changes to the Connectivity Server: 1.

Make the desired changes to the object.

2.

Change the Validation Against: field if applicable and desired.

3.

Click the submit changes button (). This also automatically clears the edit lock.

Canceling Changes

Click the cancel changes button () to cancel all changes made during an edit session. This also automatically clears the edit lock.

Adding Connectivity Server to the System For editing the object list go to: Start > (All) Programs > ABB Industrial IT 800xA > 800xA for Melody > Diagnostics > ObjectList

The Connectivity Servers must be first in the order of additions to the system.

3BDD011741R4101

37



Define all Melody Connectivity Server and the backup Connectivity Server:

MCBT009A

Figure 7. Adding new Connectivity Server (Example)

38

1.

Select Template in the Life Cycle field

2.

Select MelServer as template

3BDD011741R4101


3.


Select New in the context menu (right mouse click to open the menu).

MCBT011A

Figure 8. Creating new Node Object (Example) 4.

Fill in Network identification When entering the server path of a redundant pair of Connectivity Server it is necessary tho extend the path with the group name of the redundant pair of Connectivity Server.

The group name combines primary and backup Connectivity Server.

3BDD011741R4101

39



Table 1. Informational Attributes Attribute

Description

Config

Property

DESC1

Description of the event point. If no description is configured for the specific event point the description of the tag will be used instead.

Yes

Yes

EPSCAT

Category the event point belongs to. Defining event categories supports identification of closely related event points of one source. Event points with the same event category will be considered by a client application as closely related.

No

Yes

SIG0

Defines the logic state descriptor for the zero state of the event point. Usually this attribute is defined through configuration.

Yes

Yes

SIG1

Defines the logic state descriptor for the one state of the event Yes point. Usually this attribute is defined through configuration.

Yes

PRI0

Priority defined for the inactive state of the event point.

Yes

Yes

PRI1

Priority defined for the active state of the event point.

Yes

Yes

COM0

Event comment for inactive event point.

Yes

Yes

COM1

Event comment for active event point.

Yes

Yes

ALMEN

Event point represents an alarm (abnormal condition).

Yes

Yes

NOTES: 1. Only if the event point is defined as part of the tag.

40

3BDD011741R4101


Adding Event Concentrator to the System

MCBT014B

Figure 9. Assigning Node Object and Server Path (Example)

Adding Event Concentrator to the System For editing the object list go to: Start > (All) Programs > ABB Industrial IT 800xA > 800xA for Melody > Diagnostics > ObjectList Define all ClientEvent Concentrators and all LocalEvent Concentrators.

MCBT007A

Figure 10. Adding new Event Concentrator (Example)

3BDD011741R4101

41



When entering the server path for Event Concentrators of a redundant pair of Connectivity Server it is necessary tho extend the path with the group name of the redundant pair of Connectivity Server. Table 2. Informational Attributes Attribute 1

Description

Config

Property

DESC


Yes

Yes

EPSCAT


No

Yes

SIG0


Yes

Yes

SIG1


Yes

PRI0


Yes

Yes

PRI1


Yes

Yes

COM0


Yes

Yes

COM1


Yes

Yes

ALMEN


Yes

Yes

NOTES: 1. Only if the event point is defined as part of the tag.

42

3BDD011741R4101



The group name combines primary and backup Connectivity Server.

MCBT008B

Figure 11. Assigning Node Object and Server Path (Example)

3BDD011741R4101

43

Adding Coupling Modules of Type CCO 30, CMC 70 and PM 875


Adding Coupling Modules of Type CCO 30, CMC 70 and PM 875 After installation of the 800xA for Melody software it is required to add the Melody Coupling Modules to the system. When extending the system by new coupling modules observe the correct order: 1.

Create the module in the object list.

2.

Extend the system in Composer (incl. release and commissioning)

For editing the object list go to: Start > (All) Programs > ABB Industrial IT 800xA > 800xA for Melody > Diagnostics > ObjectList Select new (right mouse click):

MCBT002B

Figure 12. Adding new CCO to Object List In the General Tab the module name and description has to be entered. As Name for the coupling module the module place position is mandatory! Backup modules

44

3BDD011741R4101



of a redundant pair must not be entered in the General Tab. For entering backup modules refer to the CCO Tab.

MCBT003B

Figure 13. Naming new Coupling Module

3BDD011741R4101

45



In the Tag Tab the belonging server has to be selected.

MCBT004B

Figure 14. Naming the belonging Server The CCO Tab is only for entering the mounting place position of redundant modules (backup modules) while the primary module has to be entered in the

46

3BDD011741R4101



General Tab. For single, non redundant modules the Redundant module text box remains empty.

MCBT005B

Figure 15. Naming the Redundant Module The Version Tab lists automatically all versioned modifications. The Version Tab is not intended for any entries. After having done all settings and after having saved these settings, the life cycle has to be set to Running.

3BDD011741R4101

47

Deleting Units or Areas


MCBT006B

Figure 16. Setting the Module in Running

Deleting Units or Areas To delete a unit (area) in the system: •

Remove all entries under the unit (area) in Composer.

•

Delete the empty unit (area) in Composer

•

Select the Connect Configuration aspect

•

Delete the unit (area) via ObjectList.

The deletion of the unit (area) will automatically actualized to the system by the Tag Importer. The context sensitive delete option in the Control Structure can not be used to directly delete a unit (area).

48

3BDD011741R4101


Common Object Properties

Common Object Properties All 800xA for Melody objects have some common object properties. These common properties identify the object and relate the objects to each other in the object hierarchy. The common properties are configured in the general, aspects, version, and tag tabs of the object view.

General Tab The General tab contains the following sections (Table 3): • Identification. • Template. • Advanced. Table 3. General Tab Fields Field 1

Description

Identification Type

Selected during object creation. The type field cannot be changed except to delete the object and create a new object of the desired type. The behavior and the properties of an object are mainly dependent on the object type.

Name

Used to identify an object at the user interface level. Internally the name is linked with a unique ID. References to objects are stored by using the unique ID only. If the name of an object that another object references is changed, the reference will stay the same. At the browser level the most recent name will be used to present an object. Object names must be unique. The field accepts from up to 32 characters.

Description

Defines more detailed information about an object. It displays in several views (faceplates). The field accepts from up to 64 characters.

Template Based On

Template this object was derived from. It is filled in automatically and is for information purpose only. Refer to See Template for more information.

Advanced

3BDD011741R4101

49



Table 3. General Tab Fields (Continued) Field 1

Description

User Text

Allows language specific text to be associated with the version of the object.

User Index 2

Provides a method to index objects using some other indexing scheme.

NOTES: 1. Refer to See Naming Conventions and Guidelines for a description of the legal character set for names. 2. This field is currently used by Operate IT conversion tools to map the original object in Operate IT to a new object in 800xA for Melody.

Identification

The identification section shows the information that identifies the object to the user throughout the 800xA for Melody system. Template

The templates section provides information about the template the object was created from. Advanced

Click the advanced arrow to expose the user text and the user index fields.

Version Tab The Version tab is used to add and view comments about the object. The Comment field is used to enter a user defined comment related to the specific version of the object. Comments can be added independent of the life cycle the object is in. The object does not have to be in edit mode to add a comment. The design engineer, as well as the person putting the object into operation, can make comments. Security does not apply to this feature. Every life cycle change and submit will automatically create a version entry containing the user name, time, and action performed.

50

3BDD011741R4101



To enter a comment: 1.

Type a comment in the field provided.

2.

Click Add Now. This adds the comment to the list that appears at the bottom of the window. Version, User, Date, and Life Cycle are automatically filled in.

The area below the comment entry field provides a list of the version information for the object in a table form. Table 4 describes the columns in the information section. Table 4. Version Tab Columns Field

Description

Get Version

Shows the version number of the object when the comment was added. This field is filled in automatically.

User

Shows the name of the user who entered the comment. This field is filled in automatically.

Date

Shows the time of the comment. This field is filled in automatically.

Life Cycle

Shows the life cycle the object was in when the comment was added. This field is filled in automatically.

Comments

Shows the comment.

3BDD011741R4101

51

Settings


Settings For access to the System Settings enter the Control Structure, select the system and select the Settings aspect.

MCTP006B

Figure 17. System Settings Aspect

52

3BDD011741R4101


Configuration Server

Configuration Server Domain Name and Database Name are provided by the system as defined before. It is possible to modify the Database Name but it is recommended to keep the default name. As Machine Name the belonging Config Server has to be selected. Selecting the Test button shows if a connection to the database is currently established.

Options Disconnected Tags and Synchronize to Functional Structure:

As default the setting for Disconnected Tags is delete and the Synchronize Functional Structure option is selected. If the Delete option is selected and if an object is deleted in Composer then all Aspects of the deleted object will also be deleted. This is also the case of variant exchange in Composer. If the Add to Functional Structure option is selected, then a directory can be selected where to store disconnected tags. The Aspects of the tags can be retrieved from this directory. Faceplate Mapping:

Melody tag object types may have multiple faceplates. One type of faceplate shall be defined as default depending on the configuration of the tag object in Composer. Each Melody tag object type in the operator workplace with more than one faceplate may have one additional aspect named: "Faceplate Mapping". The addition of the Faceplate Mapping Aspect is the precondition for using the Faceplate Mapping option.

3BDD011741R4101

53

Options


The Faceplate Mapping aspect is a basic property aspect that can be added to the object type.

MCBT421A

Figure 18. Adding the Faceplate Mapping Aspect

54

3BDD011741R4101


Options

The "Faceplate Mapping" table (accessible via the Faceplate Mapping aspect see Figure 19) assigns faceplate names visible in 800xA Operations to internal 800xA for Melody faceplate names.

MCBT423A

Figure 19. Example for a Faceplate Mapping Table

If the Faceplate Mapping option is checked then 800xA for Melody automatically updates the default faceplate settings in the operator workplace when it recognizes a configuration, which requires another faceplate. The TagImporter service component reads the faceplate name created by Composer and translates it into an 800xA for Melody faceplate. If the Faceplate Mapping option is not checked then there is only one single type of faceplate that will always be used even if more types of faceplates are available as aspects.

3BDD011741R4101

55

Options


Usage of specific Faceplates The usage of specific faceplates for single tags is possible. These specific faceplates have to be handled as individual exceptions to the standard faceplates that have been assigned by faceplate mapping. To avoid overriding of the specific faceplates by the standard faceplates at each start of the Operations code generation it is necessary to protect the specific faceplates. To protect a specific Faceplate from overriding: •

Select the Faceplate mapping aspect for the tag.

•

Right mouse click to open Properties.

•

Select the Aspect Details tab.

•

Click Add.

•

Select No Faceplate Mapping and click OK.(see Figure 20)

•

Click Apply.

MCBT422A

Figure 20. Avoiding Overriding of Specific Faceplates

56

3BDD011741R4101


Options

History Log Configuration:

Melody Composer provides standard archive typicals with predefined configurations for history logging. Archive typicals are assigned to individual process signals within Composer. The assignment can be done by placing the archive template symbol to the signal line in the function plan or by a configurations dialog (accessible from signal origin symbol in the function plan) 800xA for Melody provides also a library with log templates. Each log template corresponds to a Composer archive template. If the History Log Configuration is checked then 800xA for Melody creates a “History Log Aspect” as soon as signals for archiving are available. Signals will then automatically be entered as ’to be archived’ and 800xA assigns the log template to the corresponding typical in Composer. Adding further specific typicals in Composer and 800xA Process Portal is always possible. In that case the template naming in Composer (Archive typical) and in 800xA Process Portal (History log template) have to be synchronized. Identical template naming is the precondition for the log transfer from Composer to 800xA Process Portal. The synchronization of further log information within the Composer mask (“Processing for an archive typical”, see Figure 21) for the archive typical is useful for documentation purposes but not necessary for the log transfer. The log behavior is defined by the log template settings in 800xA Process Portal. The standard workflow begins with the usage of archive typicals in Composer function plans and continues with the automatically transfer of the archive information to 800xA Process Portal.

If the History Log Configuration is not checked then a manually log configuration of 800xA Process Portal is required.

3BDD011741R4101

57

Options


Using external archive The functionality External archive that can be set in Composer (see Figure 21) will not be active to 800xA Process Portal. All Composer typicals will only transfer information to short-term archive.

MCBT419A

Figure 21. Archive Template Configuration in Composer

58

3BDD011741R4101


Audit Trail

To enable the long-term archive functionality in 800xA Process Portal it is necessary to extend the template by a hierarchical archive in the library structure (See Figure).

MCBT420A

Figure 22. Log Template Definition in 800xA Process Portal For detailed information about the archive configuration refer to the 800xA Information Management, Configuration (3BUF001092).

Audit Trail The Configuration Manager of 800xA for Melody is able to create audit trail events for configuration changes like creation, modification and deletion of tag objects. Use the following steps for enabling system audit trail: 1.

Check both Audit Trail check boxes.

2.

Click Apply.

3BDD011741R4101

59

Audit Trail


Auto-Configurator User Account: Enter the user account. If the Auto-Configurator User Account text field is empty all information about audit trail events won’t be archived even if the boxes for Audit Trail are checked.

The user account must not be the service account.

For further Audit Trail settings refer to Industrial IT 800xA - System, Configuration (3BDS011222).

60

3BDD011741R4101


Synchronizing Engineering Data

Synchronizing Engineering Data Introduction Configurator Admin and Auto Configurator basically perform the same task to synchronize the Aspect Server data with the data of Composer for Melody. All configuration changes related to the Melody controllers, tags and the OPC configuration are made in the Composer. As a result the Melody aspect objects represent the actual state of the controller configuration in both the control structure as well as the functional structure.

Configurator Admin The Configurator Admin manually initiates synchronization between Composer and the Aspect Server. In addition the Auto Configurator the Configurator Admin allows to analyze all differences between the 800xA for Melody Config Server and 800xA Process Portal.

It is recommended to use the Auto configurator as standard functionality for the synchronization between Composer and the Aspect Directory. The use of the Configurator Admin should be limited to rare, specific actions.

3BDD011741R4101

61

Configurator Admin


To run the Configurator Admin enter the Control Structure of the Connectivity Server, select the system and then select the Configurator Admin Aspect.

MCBT416A

Figure 23. Configurator Admin Aspect

62

1.

Click Analyze.

2.

Click Apply.

3BDD011741R4101


Configurator Admin

The options button offers the possibilities to analyze differences between the ConfigServer and the Aspect Directory or to show tag objects.

MCBT424A

Figure 24. Configurator Admin Aspect Options When selecting the Analyze Differences option the Objects and Structure will always be analyzed. All other items have to be explicitly checked to perform the analyze. If the result of the difference analysis are differences between the ConfigServer and the Aspect Directory then the differences are listed in the table of the Configurator Admin Aspect. To synchronize Aspect Directory data with the ConfigServer data: Click Apply in the Configurator Admin Aspect. When selecting the Search Tag Objects option the disconnected tags are listed. Disconnected tags are those tags, that are not part of the Control Structure but only part of the Functional Structure. To check also if there are naming conflicts: Check Duplicate Tags. For disconnected tags or duplicated tags the synchronizing functionality (Apply button) is not available.

3BDD011741R4101

63

Auto Configurator


Auto Configurator It is possible to apply changes to the Melody Controller and Config Server even if the Aspect Server is temporarily unavailable. After restart of the Aspect Server, 800xA for Melody recognizes outstanding changes and automatically performs a complete synchronization. Due to run time advantages it is recommended to use the Auto Configurator as standard for synchronization between Composer and the Aspect Server! To run the Auto Configurator enter the Control Structure, select the system and then select the SAC Data Source Aspect. Click Create... and enter the desired Service Group Name.

MCAC002A

Figure 25. Selecting the SAC Data Source Aspect

64

3BDD011741R4101


Auto Configurator

As node select the primary aspect server

MCAC001A

Figure 26. Selecting the Service Group Click OK. Click Add.

After the start the Auto-Configurator analyzes the data base wether full synchronization is necessary or not.. After the auto-configuration service has been started the progress can be followed up by the following messages sent as event for information: • Melody/AC870P auto-configuration service started full sync. • Melody/AC870P auto-configuration service finished full sync. Note: for very large-scaled systems full sync process may last up to 90 min. • Melody/AC870P auto-configuration service is ready for synchronization. Note: if the Auto Configurator clearly detects all changes then it synchronizes only these changes and the first two messages referring full sync will not be sent but only the last one.

3BDD011741R4101

65

OPC Data Source Definition


OPC Data Source Definition The OPC Data Source Definition Aspect provides the possibility to adjust the OPC data access (OPC DA) settings that are necessary to run the data transfer.

MCAC004A

Figure 27. OPC Data Source Definition Aspect

To create a new Service Group: 1.

Select the Connectivity Tab

2.

Enter the name for a new Service Group in the Service Group text box. The Data Key provided by the system must not be modified.

66

3BDD011741R4101


3.


Click New.

MCBT017A

Figure 28. Assigning Connectivity Servers to a new Service Group 4.

Click Add... .

5.

Select the Melody Connectivity Servers to be member of the newly created group. Redundant Connectivity Servers must be members of the same service group.

6.

Click OK

Via the Modify button it is possible to edit a service group after first definition. Via the View button it is possible to view a service group after first definition. The result of the OPC Data Source Definition are newly created objects in the Service Structure

3BDD011741R4101

67



MCBT018A

Figure 29. Result of the OPC Data Source Definition

68

3BDD011741R4101


Tag Importer

Tag Importer The task of the Melody Tag Importer is the upload of configuration data from Composer for Melody to the 800xA for Melody Config Server. Use the following step to run the Tag Importer for an automatic Composer upload: 1.

Create a new directory: c:\Melody\bin\jobs on the Config Server.

2.

Share the newly created Melody directory.

3.

On the Composer Server, map a network drive “o:\” to the shared “Melody” drive on the Config Server node.

4.

To start the Tag Importer go to the Melody Config Server:

Start > All Programs > ABB Industrial IT 800xA> 800xA for Melody > Configuration > Tag Importer To have an easy access to a manual upload it is useful to place the Tag Importer on the desktop. The source file is located under: \Program files\ABB Industrial IT\Configuration\MelConverter.exe

3BDD011741R4101

69

Tag Importer


In case of a large amount (> 1000) of configuration changes (modification and/or creation of new tags) the synchronization mechanism between data base and Connectivity Server slows down. It is possible to minimize the effect of this slowdown by performing the following steps: 1. Stop Tag Importer 2. Disable Online Changes Control Structure > Connect Configuration Aspect > Management Tab > Deselect “Synchronize data after each object update” 3. Start Tag Importer 4. Execute configuration changes 5. Stop Tag Importer 6. Enable Online Changes Control Structure > Connect Configuration Aspect > Management Tab > Select “Synchronize data after each object update”. 7. When prompted for the type of restart (see Figure 30): a. Check Restart the affected server(s)... b. Check Restart Servers Manually c. Click OK d. In case of redundant Connectivity Servers restart the first and wait until this Connectivity Server is up again before restarting the second. 8. After the system operation has been normalized start Tag Importer.

70

3BDD011741R4101


Tag Importer

MCBT426A

Figure 30. Restart Options

3BDD011741R4101

71

Tag Importer

72


3BDD011741R4101

Section 3 Topology Topology Planning Hardware Control Network Redundancy 800xA for Melody supports server redundancy and network redundancy. The Melody control network is a standard industrial Ethernet network using standard components. Typically the redundant Melody Control Network is a ring and one cut does not affect system availability. The principle is shown in Figure 31:

MCTP003A

Figure 31. Example for a Redundant Network Structure

3BDD011741R4101

73

Operator Network Redundancy

Section 3 Topology

Applying this solution one failure does not cause a shutdown because the Melody components might be redundant and the connectivity server might be redundant as well. The Control Ethernet Network is redundant, if the solution shortly described is applied and cutting the network at one point is compensated.

For detailed information about network configuration including RNRP settings refer to IIT 800xA - System, Automation System Network Configuration (3BSE034463)

Operator Network Redundancy The Operator Network will be realized according to the IndustrialIT 800xA system guidelines. A redundant Operator Network is realized by using the Redundant Network Routing Protocol (RNRP). RNRP is an ABB protocol for handling redundancy functions and routing between nodes in a control network. The protocol is designed for rapid detection of network failure and instant switching to an alternative path.

Boundary Conditions for HW Planning The Melody Connectivity Server has to be a dedicated server. Other software components than those necessary to run the Melody Connectivity server are not allowed to be installed on the Connectivity Server computer.

74

3BDD011741R4101

Section 3 Topology

Topology Planning Software

Topology Planning Software Overview

MCTP001B

Figure 32. System Software Structures edited by 800xA for Melody Control Structure

Melody controller objects are placed in the Control Structure under a Melody operations Network object. This object contains several aspects required for synchronization with the configuration server. These will store the node and configuration server name for communication with the configuration server. Each operations network object is related to a particular Melody Connectivity Server. The Melody System and Config Server objects are unique and represent the entire automation system. The Auto Configurator Aspect (automatic uploader) is running on a server node (e.g. aspect directory node) – the node can be configured in the SAC Aspect of the Melody System object. The Data Source aspect of each Melody operations network object points to the Connectivity Server node providing the OPC data for this network.

3BDD011741R4101

75


Section 3 Topology

Below the CMC/CCO objects the tags will be grouped based on their object types. This simplifies the navigation to a certain tag and avoids very large object branches on one level.

MCTP004A

Figure 33. Example for a Control Structure Functional Structure

Melody tag objects are inserted into the Functional Structure during the Auto Configuration or after the starting the Configurator Admin. The Functional Structure is intended for easier navigation to process automation functions in a function oriented way. Functional units and plant areas can be configured and assigned to process points (tags) in Composer and are automatically published as

76

3BDD011741R4101

Section 3 Topology


Aspect objects by 800xA for Melody. It is possible to create additional higher level unit objects or area objects created by 800xA for Melody in tree structures.

MCTP005A

Figure 34. Example of a Functional Structure

3BDD011741R4101

77

Base Topology Configuration

Section 3 Topology

Base Topology Configuration Deleting Nodes Use the following steps for deleting nodes if necessary: 1.

select the node in the object list environment

2.

set the node Out of Service

3.

delete the node.

Creating a new Operator User To create a new operator user select the User Structure as shown in the following Figure 35:

MCUS001A

Figure 35. User Structure as Start Point for Creating a new Operator User

78

1.

Select the Operators, User Group in the User Structure.

2.

Right mouse click to enter the menu.

3BDD011741R4101

Section 3 Topology

Creating a new Operator User

3.

Select New Object.

4.

Select User in the Common Tab.

5.

Enter the operator user name as shown in the following Figure 36:

MCUS002A

Figure 36. Entering User Name for new User 6.

Click Next.

7.

Select the domain/machine.

For details about creating a new Operator User refer to Industrial IT 800xA System, Configuration (3BDS011222) and Industrial IT; 800xA - System; Engineering Workplace; Topology Designer (3BDS011225).

3BDD011741R4101

79


Section 3 Topology

Select the new user

MCUS003A

Figure 37. Selecting the User

80

8.

Select the new user

9.

Click Create.

3BDD011741R4101

Section 3 Topology


The following figure shows the new user within the user group.

MCUS004A

Figure 38. New User as new Member of the User Group

3BDD011741R4101

81

Affinity

Section 3 Topology

Affinity In case of redundant Connectivity Servers it is recommended to practice load balancing, i.e. to split the data transfer to the different operator workstations on both Connectivity Servers (primary and backup). To do this balancing by help of the Affinity Aspect: 1.

Enter the Admin Structure and select Inventory Object > Affinity, Aspect Type

MCAF006A

Figure 39. Affinity Definition 2.

82

Select new object via right mouse click

3BDD011741R4101

Section 3 Topology

3.

Affinity

In the New Object window select Affinity and enter the Name as shown in Figure 40

MCAF007A

Figure 40. Defining Affinity Name 4.

3BDD011741R4101

Click Create.

83

Affinity

Section 3 Topology

5.

Select the Configuration Tab.

MCAF008A

Figure 41. Affinity Definition Aspect 6.

84

Select Add under the Selection Group/Node box on the left to ad the operator workplaces.

3BDD011741R4101

Section 3 Topology

7.

Affinity

Select an odd numbered operator workplace and select Add right to the Select server group/node box for adding belonging connectivity server as shown in Figure 42:

MCAF009A

Figure 42. Adding Connectivity Servers to an odd numbered Operator Workplace

In case of redundant Connectivity Servers the operator workplace gets its OPC data from the first Connectivity Server, that is listed in the right box. It is recommended to assign the odd numbered operator workplaces in the default order and to change the order of redundant Connectivity Servers. By this means the connection to the odd numbered operator workplaces is done by the primary connectivity servers and the connection to the even numbered operator workplaces is done by the backup connectivity servers.

3BDD011741R4101

85

Affinity

Section 3 Topology

8.

Select an even numbered operator workplace and select Add right to the Select server group/node box for adding belonging connectivity server as shown in Figure 43:

MCAF010A

Figure 43. Adding Connectivity Servers to an even numbered Operator Workplace 9.

86

To change the sequence of access Click up or down.

3BDD011741R4101

Section 3 Topology

Affinity

10. Select the Affinity Summary Tab to verify the created affinity.

MCAF003A

Figure 44. Affinity Definition Aspect - Affinity Summary Tab

For non redundant Connectivity Servers, their appearance in the connectivity server sequence is optional.

3BDD011741R4101

87

Affinity

Section 3 Topology

11. To activate the affinity select the Service Structure > OpcDA_Connector, Service > Service Definition aspect and select as Affinity the former defined Affinity name.

MCAF004A

Figure 45. Affinity Definition Aspect - Configuration Tab 12. Click Apply.

For alarms and events the affinity settings may be done but due to the exclusive connection via primary Connectivity Server a balancing effect will not come into effect.

88

3BDD011741R4101

Section 3 Topology

Control Structure Import

Control Structure Import To get messages from Melody modules other than coupling modules it is required to make them known to the system. To achieve this: 1.

Enter the Composer System Overview

2.

Select the project (left mouse)

3.

Select the middle mouse button

4.

Select Export -> Control Structure as shown in the following Figure 46.

MCTP008A

Figure 46. Export Control Structure

The directory on the Config Server must be the same name like the directory for Operations Code Generation in Composer. The directory name in Composer can be seen in the Project Setup -> Operations Tab -> Working Directory.

3BDD011741R4101

89


Section 3 Topology

In case of successful Control Structure Export the control structure information for the relevant Melody coupling modules is copied to the ocs directory on the Melody Config Sever.

MCTP010B

Figure 47. Control Structure Export Result To extend the Control Structure: 1.

90

Select the desired Melody coupling module in the Control Structure

3BDD011741R4101

Section 3 Topology

2.


Select the Control Structure Import Aspect as shown in Figure 48

MCTP011B

Figure 48. Control Structure Import Aspect - Standard Tab 3.

Select the Advanced tab. (refer to Figure 48)

4.

Select the OCS Filename for belonging to the desired Melody coupling module (same mounting place position, e.g. ep001g09)

For entering the file name it is not necessary to map a network drive. Because both computers are assigned to the same domain it is sufficient to enter the network path as shown in Figure 48.

3BDD011741R4101

91


5.

Section 3 Topology

Select the Standard tab as shown in Figure 49

MCTP012A

Figure 49. Control Structure Import Aspect - Advanced Tab 6.

Click Start.

After a topology modification the Control Structure Import has to be done again for the affected coupling modules.

92

3BDD011741R4101

Section 4 Engineering Workflow Engineering Overview The engineering workflow always starts in IndustrialIT Melody Composer and ends up in 800xA Process Portal and the control system part. Composer supports bulk data actions and import of data reflecting the basic engineering like tag imports, signal lists, channel assignments and management of typicals to create instances of function charts by list based engineering. Engineering activities in 800xA Process Portal colliding with Melody business rules in means of consistency and integrity will be rejected. The lifecycle of a Melody object starts and ends in Composer. Aspects hosted by other than Melody Aspect Systems might extend Melody objects. When commissioning functionality that has been planned in Composer the 800xA Process Portal relevant information will be generated by Composer and automatically uploaded into 800xA Process Portal. Versioning of data is done according to the Melody life cycle model.

Bulk Data Management IndustrialIT Melody Composer provides a lot of bulk data processing with powerful business rules to save engineering effort in the project. The Composer project database comprises •

Function Block library representing explicit and implicit operation functionality

•

Alarm/Event Typicals

3BDD011741R4101_DRAFT

93

Bulk Data Management

Section 4 Engineering Workflow

Typically each project sets up templates representing the standard solutions for the specific project. These templates are mainly designed by ABB project engineers and approved by customers. Using the list based engineering support of Composer the real function chart instances get automatically derived from the templates. Using this approach all information relevant for faceplates, archive and control application events and alarms will be generated by the operations code generation (“Operations Generation”) during release and commissioning in Composer.

MCES001A

Figure 50. Operations Configuration as Part of Functional Planning (Example)

94

3BDD011741R4101


Import/Export

Import/Export From a functional point of view Industrial IT Melody Composer provides the import/export functionality. 800xA for Melody uploads imported data to 800xA Process Portal by using e.g. the Auto-Configurator. Composer supports features to enable import / export of engineering data. Composer allows the import of basic engineering like tag list, signal list, process media information, I/O channel assignment lists etc. as well as it allows export / import of complete functional arrangements. The functional arrangement may comprise function charts, functional areas described by a complete set of function charts, complete automation stations and more. All the import and export in Composer is realized by applying the life cycle management and its business rule to enforce data consistency.

For detailed information about Composer Import/Export functionality refer to Technical Information 30/72-8010 “Importing and exporting project data”

3BDD011741R4101

95

Alarms and Events


Alarms and Events Alarm/Event typicals are predefined in the Industrial IT Melody Composer project library. By adding an Alarm/Event typical to a signal in the function chart, this signal is marked to fire an alarm/event when becoming true.

MCSG002A

Figure 51. Alarm and Event Typical in Industrial IT Melody Composer System messages are inherent part of the control system software and not part of project engineering. Process application related messages have to be designed during project engineering. Event and alarming typicals are predefined in Composer. By assigning these event and alarm typicals to a signal on a function chart Composer performs the code generation for the control system as well as for the Connectivity Server.

96

3BDD011741R4101


Object Life Cycle

Object Life Cycle The configuration system allows making configuration changes in a way that the changes do not immediately take effect in the system. This provides the ability to make changes in preparation for future use and allows for distributed plant engineering and commissioning. Additionally, it provides a roll-back function that can be used to go back to a former version in case the latest changes lead to undesired behavior. These capabilities are provided through life cycle management features. Life cycle management allows configuration data for an object to exist in multiple versions where each version is in a different life cycle. The life cycles are: • Design. (Planning) • Release. • Running. An object version in the design or Release Life Cycle is not effective in the system. These life cycles are for configuration data being prepared for later use. Objects in the design or Release Life Cycle are offline versions. An object version in the Running Life Cycle is currently effective in the system. Objects in the Running Life Cycle are online versions.

Operating Parameters All parameters operated via the 800xA Operator Workplace are written down to the Melody system. The Melody objects provide the information which data are accessible by an operator in the connectivity aspects assigned to the Melody object type definitions contained in the Melody system extension. Parameter adjusted by the operators are downloaded into the Melody system and made persistent in the controller but not automatically included into the Composer project database. At certain points in time the current settings are automatically

3BDD011741R4101

97

Operating Parameters


reloaded by Composer into the project engineering database as new default settings. This allows planning of revisions based on the approved plant settings.

MCSG003A

Figure 52. Operating Parameters

98

3BDD011741R4101

Section 5 System Definition Introduction This section describes system definition features defined in the system definition object. Select the Connect Configuration Aspect for the system, selected in the control structure.

MCSD001A

Figure 53. Connect Configuration Aspect

3BDD011741R4101

99

System Definition Object

Section 5 System Definition

System Definition Object Even though 800xA for Melody configuration data is maintained and organized in objects, there is data that does not belong to a single object, but affects the entire system. This data is maintained in a system definition object. The system definition object defines the following for the entire system: • System protocol. • System text. • Quality indicators. • Project history. The system definition object is not subject to life cycle management. All changes to information in this object are directed to the runtime system. Only one system definition object can be configured in the project. Table 5 describes the system definition object properties. Table 5. System Definition Object Properties Properties

100

Description

Common

Has the same common object properties (General and Version) as other objects.

Indexed Text

Refer to Indexed Text Tab on page 101.

Substitutable Text

Refer to Substitutable Text Tab on page 107.

Quality Text

Refer to Quality Text Tab on page 108.

Management

Refer to Management Tab on page 110

Project History

Refer to Project History Tab on page 110.

3BDD011741R4101


Configurable Text

Configurable Text Some system text is maintained in the system definition object. This text is used in the configuration of other objects. The objects refer to this text in their definitions. The advantage of maintaining them centrally is that if changes are required they can be done and will be applied to all referring objects. Also, translation to other languages can be done in one place instead of in every object in the project. Configurable Text includes Indexed Text and Substitutable Text. These text items appear in displays as informative text, engineering units, logic state descriptors, and error indications. System text configuration is performed in two different tabs of the system definition object: • Indexed text. • Substitutable text.

Indexed Text Tab There are several types of Indexed Text. Objects refer to this text using index numbers. The Indexed Text tab of the system definition object allows selecting each type for definition (Figure 54). The Indexed Text includes: • Event Comment. • Text Selector Text. • Engineering Unit Descriptor. • Logic State Descriptor. • Alarm Priority Text. • Melody System Events. Besides the various types of Indexed Text, the text list is also organized according to Server type. This lowers the needed resources for the different Servers. Objects in a certain Server can only refer to text specific to its Server type and also the Common Server type. Each text type selection calls up a different table with an ’Index’, ’Sub-System’, and ’Text’ column. Beside the selection box is a set of buttons to scroll through the table. Click the outer buttons to scroll to the beginning or end of the table. The other buttons scroll through each table entry. The text field (1 of 15 in Figure 54) beside these controls shows the record number that currently has cursor focus and the total number of records in the table.

3BDD011741R4101

101

Indexed Text Tab


MCSD002A

Figure 54. Indexed Text Tab The fields at the bottom of the window are available for all of the text types. This area is used to edit and add user defined text. Only text indexes that are not locked can be edited. To add a text index: 1.

Click on the Add Text button. An empty text index is added at the bottom of the table.

2.

Enter the index number in the provided field. This index number must be unique to the selected Server type.

102

3.

Select a Server type. The selection of a Server type assigns the index to that Server type. This allows multiple text entries for the same index for each type of Server. Selecting Common makes it available to all Server types.

4.

Enter the text that is to be associated with the index number.

5.

Click the Submit Changes button to save the information to the Configuration Server.

3BDD011741R4101


Indexed Text Tab

Event Comment

An event comment is associated with an event point. An event comment can be assigned to every event point of a tag. Each tag type has different possible event points depending on the tag type. All event comments have an assigned index number. The index number allows using a single comment with several event points. In this way, a comment does not have to be redefined for each tag. Enter an event comment index number for each alarm condition of a tag during its configuration to associate a comment with a condition. Text Selector Text

Each text message has a unique index number assigned to it. The message can be a maximum of 80 characters long. Although there are no predefined messages, message 0 is always blank to allow displays to show no message. Engineering Unit Descriptor

Engineering unit descriptors (EUD) relate to analog signals in the control system. They describe the unit of measurement (kg/h, bar, Nm3/h, kW) for the analog signal. A list of common engineering units is provided by Composer. Theoretically, an unlimited number of engineering unit descriptors can be defined in the database.

3BDD011741R4101

103

Indexed Text Tab


Figure 55 lists as an example engineering unit descriptors and their index numbers provided by Composer.

MCSD008A

Figure 55. Engineering Unit Descriptors (Example) The Melody Connectivity Server sends an EUD index number along with the process value to identify the unit associated with the value. This index number is then cross referenced with the database list of descriptors. Since the controller reports the EUD index number, all devices on a common communication network should use the same EUD list.

104

3BDD011741R4101


Indexed Text Tab

Logic State Descriptor

Logic state descriptors (LSD) describe logic states for Digital signals. These descriptors show the current logic state (on or off, zero or one, run or stop, closed or open) of a device. A descriptor follows a tag throughout all 800xA for Melody functions after being defined for a tag. A list of common logic state descriptors is provided. Theoretically, an unlimited number of logic state descriptors can be defined in the database; although, zero through 15 are fixed. Table 6 lists the fixed logic state descriptors and their index numbers. Table 6. Logic State Descriptors Index

Descriptor

Index

Descriptor

0

ZERO

8

LOW

1

ONE

9

HIGH

2

ON

10

EMPTY

3

OFF

11

FULL

4

NO

12

RUN

5

YES

13

STOP

6

CLOSED

14

TRIP

7

OPEN

15

(Blank)

Alarm Priority Text

An alarm priority can be represented by text. There are 17 alarm priorities. Each priority can be assigned different priority text including both active and normal state events. The alarm priorities are shown in Table 7. Only the default alarm priorities are available. No others can be added.

3BDD011741R4101

105

Indexed Text Tab


Table 7. Alarm Priorities Priority

Descriptor

Priority

Descriptor

0

Priority Error!

9

WARNING

1

DIRE

10

warning

2

dire

11

ADVISE

3

CRUCIAL

12

advise

4

crucial

13

NOTIFY

5

CRITICAL

14

notify

6

critical

15

INFORM

7

ALERT

16

inform

8

alert

—

—

Melody System Events

The Melody System Events tab lists all available texts for system messages and process interface messages including the individual message priority. The priority can be modified in the text box after selecting the message.

106

3BDD011741R4101


Substitutable Text Tab

MCSD009A

Figure 56. Melody System Events

Substitutable Text Tab The Substitutable Text tab of the system definition object contains a list of system text items (Figure 57). The default entries can be modified.

MCSD003A

Figure 57. Substitutable Text Tab To edit a text entry:

3BDD011741R4101

107

Quality Text Tab


1.

Click the item to be edited. This displays a table at the bottom of the window that has four columns: Value, Text, Default Text, and Description.

2.

Enter the desired text in the text field. The default text remains in the Default Text column so that the field can be easily returned to default if desired.

3.

Click the Submit Changes button to save the new information.

Quality Text Tab The Quality Text tab of the system definition object configures the OPC quality state indicators and the 800xA for Melody increasing and decreasing indicators (Figure 58). A quality indicator is shown in displays to indicate the quality of the tag and property providing values. The increasing and decreasing indicators are used to indicate that a value is increasing, decreasing, or remaining constant. The tab shows the current indicator and the default character. To change an indicator: 1.

108

Enter the desired character in the Symbol field. The default character remains in the Default column so that the field can be easily returned to default if desired.

3BDD011741R4101


Quality Text Tab

MCSD004A

Figure 58. Quality Text Tab 2.

Click the Submit Changes button to save the new information. Changes to the quality text require a node restart to take affect.

3BDD011741R4101

109

Management Tab


Management Tab The management tab offers the possibility to enable the data synchronization immediately after each object update without system reboot (Figure 60). If the check box is checked then the synchronization works immediately. If the check box is unchecked then the synchronization can be done later after checking the same check box.

MCSD005A

Figure 59. Management Tab To enable data synchronization after each object update set the checkbox and answer the prompted question: “Enable data synchronization after each object update?“ with yes.

Project History Tab The project history tab shows an audit of all the changes made to the configuration (Figure 60).

MCSD007A

Figure 60. Project History Tab

110

3BDD011741R4101

Section 6 Alarm and Event System Introduction The 800xA for Melody event system is based on a Client/Server architecture. 800xA for Melody provides services to define event conditions and client applications. The system provides facilities to distribute the events to interested clients. This section gives an overview over the alarm and event system. It describes the system structure and also the configuration of event client applications.

Alarm and Event Service Provider Refer also to the 800xA System Alarm & Event Users Configuration instruction for more information. Enabling the Operator Alarm and Event page requires to add the Melody OPC alarm server program ID to a Service Group under the EventCollector category in the Service Structure. In case of redundant Melody Connectivity Servers both Connectivity Servers must have the same EventCollector Group. (E.g.: MELSTT011 and MELSTT012 are redundant Melody Connectivity Servers in the Basic_MELSTT011_012 Service Group, see Figure 61.) To configure the Alarm & Event Service Provider, use the following steps: 1.

Open a Plant Explorer Workplace.

2.

Use the Structure Selector to open the Service Structure.

3.

Use the Object Browser to navigate to: Service Structure > Services > EventCollector, Service

3BDD011741R4101

111

Alarm and Event Service Provider

Section 6 Alarm and Event System

4.

Select the Basis, Service Group object containing the Melody Service Provider (Melody Connectivity Server).

5.

Rename the Service Group to a suitable name (e.g.: from Basic to Basic_Server Group...)

6.

In case of redundant Connectivity Servers drag and drop the Service Providers into the same Service Group.

7.

Select the Special Configuration tab in the Service Group Definition aspect.

8.

Select Maestro/OPC EventServer(InProc) option in the Alarm Server configuration field.

9.

Select the Melody Alarms option in the Collection Definition configuration filed if it not already selected.

10. Click Apply.

112

3BDD011741R4101


Alarm and Event Service Provider

11. Delete the remaining empty Basic Service Group(s).

MCAE004B

Figure 61. Connecting Melody AE Server with 800xA Process Portal

3BDD011741R4101

113

Melody 800xA Process Portal Process Events


Melody 800xA Process Portal Process Events Table 8. Example of (Condition) Process Event FIC002 Attribute Name

Data

Vendor Melody

Ack State Event Time

03-07-28 10:17:42:282

Object Name

FIC 0002

Description

Saw tooth with offset

X

State

>Max 1

X

Condition

XH01

Type

PE

Object Description


X

Message Description Comment ViolatedLimit

75.98

X

EngUnit

1/s

X

Next table shows all possible Attributes with 800xA Process Portal Alarm Pages and Melody. Table 9. Possible Attributes with 800xA Process Portal Alarm Pages and Melody AttributeExample Data

Example Data (Process Event)

Vendor Melody

Ack State

114

Enable State

Enabled

Event Time

03-07-28 10:19:44:282

Ack Time

xxxxxxxxxx

3BDD011741R4101



Table 9. Possible Attributes with 800xA Process Portal Alarm Pages and Melody AttributeExample Data


Object Name

FIC 0002

Description


Vendor Melody

X

State>Max1X ConditionXH01 Sub Condition Current Value Priority Level

1

Priority

1000

Type

PEX

Object Description


Category

Limit Events

X

Component Message Description Comment Actor Auto Disabled Severity

1000

Section Class Blocked Repetitive Uncertain Time Tag

3BDD011741R4101

115





Vendor Melody

Audible Alarm Printout Blocked Guid

3377186754

Campaign ID Batch ID Lot ID Unit ID Recipe Path ViolatedLimit

75.98

AckHighTime

0

AckLowTime

0

ActiveTime

X

ActiveTimePrecision

3

X

Alarm

FALSE

X

Area

AREA52

X

Dual

FALSE

X

EngUnit

l/s

X

Equipment

MiscEquipment

X

EventTimePrecision

7

X

GroupID

BDD64658-AD38-4A7F-AE7A46C6FD225B0D

X

InactiveTime InactiveTimePrecision

116

X

X 3

X

3BDD011741R4101





Vendor Melody

Inhibited

FALSE

ObjectID

33550F6A-C5E3-4D6D-9641-D72C22C9B4EA X

PageAckEnabled

FALSE

X

ResponseType

0

X

ServerID

8E783BE9-469C-4B52-BD9A-E07E37FB1326

X

TimeInvalid

FALSE

X

TypeID

1

X

Unit

FU001

X

3BDD011741R4101

X

117

Melody 800xA Process Portal System Events


Melody 800xA Process Portal System Events The following Table shows important Event Information that will be generated with Melody System Messages. These are events of type dynamic Event Point. System messages (system failures) are shown in the 800xA Process Portal Alarm Page as acknowledgeable Alarms. All Melody System events coming from the controller module are handled as alarms. The system events are always active, i.e. an inactive state does not exit. Table 10. Melody System Messages Object Name

118

Description

Conditi Priori on ty

Message Description

ep064a09 Measured value(s) not actualized

1708/0

850

EP064A09, 1708

ep064a09 Connection to Profibus failed

9bc/3

1000 EP064A09, 9bc

ep064a09 Redundance take over

2204/0

1000 EP064A09, 2204

ep064a09 Redundancy communication disturbed

2206/0

900

ep064a11 Cnet(C) failure of a unit

911/0

1000 EP064A11, 911

ep064a11 Cnet(SC) failure of a unit

912/0

1000 EP064A11, 912

ep064a09 Redundancy link disturbed

2208/0

900

ep064a09 Profibus: failure of a subscriber

d810/a 00

1000 EP064A09, 0, 10, DP0010

ep064a11 Measured value(s) not actualized

1708/0

850

EP064A09, 2206

EP064A09, 2208

EP064A11, 1708

3BDD011741R4101


Melody Message System

Melody Message System This chapter describes the functionality of Melody Control related to Alarms and Events. A Melody Coupling module can be of module type CCO30, CMC 70 or PM 875. With respect to their definition there are two types of events: •

Events, predefined in Melody Control like system messages and process interface messages.

•

Events, user defined by configuration of the process loop functions like process messages.

On the Melody Coupling Module, process and system messages are generated. All messages are sorted into the message buffer for the transfer to 800xA Process Portal. 800xA for Melody enriches the transferred messages and distributes them to the 800xA Process Portal where they are distributed across the Operator Workplaces. The system messages generated on the Melody Coupling Module are additionally entered in the error memory, and can be read out by means of the diagnostics.

3BDD011741R4101

119

Melody Message Transport and Buffering


The following figure shows the message processing of the Melody Coupling Module in cooperation with 800xA for Melody.

MCAE005A

Figure 62. Melody Message System Overview

Melody Message Transport and Buffering Events provided on the Melody Coupling Module are transmitted as raw messages to a message receiver assigned to the Melody Coupling Module. Message receiver is the Melody Server. The Melody Server is a component that is installed an the Melody Connectivity Server. The transfer of raw messages from the Melody Coupling Module to the message receiver is acknowledged. The raw messages are buffered in the message buffer of the Melody Coupling Module until the acknowledgment is received. The Melody Coupling Module can store up to 4,000 raw messages in its message buffer. The message receiver generates the 800xA Process Portal messages by enriching the events, e.g. by additions that are made to the message text. The messages are distributed to the Operator Workplaces. The Melody Server is configured during commissioning of the Melody Coupling Module from the 800xA for Melody Components.

120

3BDD011741R4101


Melody Message Transport and Buffering

Up to 10 Melody Coupling Modules can be assigned to one Melody Server. The transfer of raw messages from the Melody Coupling Module to the Melody Server is always initiated by the Melody Server. The Melody Server must first set up a message link to the Melody Coupling Module. This is done during startup of the Melody Connectivity Server, respectively the Melody Server. When the connection has been set up, the Melody Coupling Module starts transmitting the raw messages. If there are messages in the message buffer, they are sent immediately. The message transfer rate is based on the speed of acknowledgment of the message receiver. Connectivity Server running with high CPU load can cause the effect that the Melody Server gets no CPU time to compute the Coupling Module messages. In this case the Coupling Module removes less important messages from its own buffer and indicates (Module signaling) this error situation. The Melody Coupling Module supports a maximum of two message receivers simultaneously. Switch-over between single and dual receiver mode is made automatically when the connection is set up to the second message receiver. If two message receivers are active, both must acknowledge receipt of the raw message before it is removed from the message buffer. If one of the message receivers fails, the Melody Coupling Module switches back to "One message receiver active" mode. All events generated and received on the Melody Coupling Modules are stored in the failsafe message buffer until they are successfully transported to the Melody Server. The administration of raw messages in the message buffer is dependent on priority and message category. Each raw message may have a priority of 1 up to 16 and is classified as a process message (type alarm), process interface message, system message or process message (type status). The message categories are in turn stored in the message buffer and administered according to the following priorities: •

Process messages: type alarm (highest priority)

•

Process interface messages

3BDD011741R4101

121

Melody Process Messages


•

System messages

•

Process messages: type status (lowest priority)

Raw messages can be distributed in any order within the message buffer in terms of message category and priority. As a maximum, all 4,000 raw messages may be of the same category and priority. For transport to 800xA Process Portal, the raw messages with highest priority are always read from the message buffer first. If the buffer is full when a new raw message is received, then the priority of the new message is compared with the lowest-priority message in the buffer. If the priority of the new message is higher, then it will overwrite the lowest-priority message in the buffer. Otherwise the new raw message is rejected. In a redundant Melody Coupling Module, the message buffer administration systems ensure consistent data in the active and backup units. The contents of the message buffer are retained even when the module is reset. In case that two Melody Coupling Modules are working as a redundant pair and if the backup unit has been reset, then the backup (passive) unit adjusts to the primary (active) unit. The message buffer is erased during basic initialization.

Melody Process Messages Process messages are generated due to changes of the process variables. If a change has occurred, and if a message criterion is configured for the process variable, the Melody Coupling Module generates a raw message dependent on the associated configuration data. It enters the message into the message buffer for transfer to 800xA Process Portal. On the Melody Coupling Module, message events can be configured for Bool, Packed Bool and Limit Value type signals. Whereas for the types Bool and Limit Value one message criterion is defined, for Packed Bool type signals up to 32 criteria can be configured. For each message criterion, expanded message processing rules can be configured, which characterize the specific messaging behavior of a signal. The following message parameters are administered on the Melody Coupling Module:

122

3BDD011741R4101


Melody Process Messages

Table 11. Message Parameters Message Selector MGEN (Bool)

Meaning Message generation

Remarks Defines whether at least one message is to be generated for the process variable. 0: No message generation 1: Message generation

MTYPE (Integer)

Message type

Defines the message type to be sent. Message type as per P-protocol definition, e.g., binary value message, real value message, P32Bool value message.

MIDX (Integer)

Message index

Defines the message signal for process variables of data type P32Bool. The data type P32Bool contains up to 32 independent message signals which are unambiguously defined system-wide in Melody. For each message signal, a fixed message generation rule is defined on the Melody Coupling Module. The message is usually generated from precisely the specified message signal, but in specific cases, the value information of additional message signals within the P32Bool signal is also taken into account in generating the message.The message index unambiguously identifies the message signal defined in Melody. The message index is evaluated only in the case of signals of data type P32Bool. The value range is defined from 0 to 32767. Signals of the data type not equal to P32Bool have the message index -1.

PRIO (Integer)

Message priority

Defines the priority of the message to be sent. 1: Highest priority 16: Lowest priority

DUAL (Bool)

Message significance Defines whether only incoming or also outgoing messages are to be sent. 0: Only active messages (single) 1: Active and return-to-normal messages (dual)

3BDD011741R4101

123

System and Process Interface Messages


Table 11. Message Parameters Message Selector LOGIC (Bool)

Meaning Message logic

Remarks Defines the direction of the edge change at which the message is to be generated. 0: Positive logic. Message on signal change 0 > 1 1: Negative logic. Message on signal change 1 > 0

AL (Bool) Alarm / Status

Defines whether the message is to be sent as an alarm or status message. 0: Status 1: Alarm

The process messages are only generated with valid measured values. The change check for message generation is always based on the last valid measured value. The time entry for the raw message is based on the time entry of the process variable, i.e. the time at which the signal change was detected. Table 12. Total No. of Configurable Process Messages Coupling module

Max.No. of Process Messages

CMC 70 / PM 875

60,000

CCO 30

22,500

System and Process Interface Messages System messages are generated by the Melody Coupling Module and associated units in Melody and prepared for further transport to 800xA Process Portal. The active Melody Coupling Module enters its own system messages directly into the message buffer. The backup Melody Coupling Module transmits its system messages for onward transfer to the primary (active) unit.

124

3BDD011741R4101


Alarm & Event System Definitions and Overview

Process interface messages are not only generated by the Melody Coupling Module, but also by all associated units in Melody. The units send their process interface messages like their system messages to the active Melody Coupling Module. Supplements to the message text and plant area are appended, and the priority for the system and process interface messages is assigned during message enrichment by 800xA for Melody. The plant area printed out in the message is configurable in 800xA Process Portal with Connect Configuration Aspect and is specific for each Melody Coupling Module.

Alarm & Event System Definitions and Overview Events are generated by Servers in the system. Event concentrators collect the events from the Servers and distribute them between the different nodes and make the event stream accessible for client applications. All client applications can be configured to be sensitive to a group of events defined by an event filter and applied to the event stream in the system. Figure 63 is a functional diagram of the 800xA for Melody event system. OPC A E S E RV E R

EVENT D IS T R IB U T IO N

EVENT STREAM

EVENT STREAM EVENT STREAM

S E RV E R S M A IN TA IN IN G E V E N T P O IN TS A N D G E N E R AT IN G E V E N T S

S E RV E R S M A IN TA IN IN G E V E N T P O IN TS A N D G E N E R AT IN G E V E N T S

S E RV E R S M A IN TA IN IN G E V E N T P O IN TS A N D G E N E R AT IN G E V E N T S T 04 056 B

Figure 63. 800xA for Melody Event System

3BDD011741R4101

125

Alarms and Events


The design and implementation of the alarm and event system is closely related to the OPC definitions for alarms and events. For a clearer understanding, this instruction refers to the OPC terms where appropriate indicating similarities and potential differences.

Alarms and Events An event is the notification of some occurrence that is considered significant. The event can either be related to a specific condition represented by an event point (the transition into high alarm of a tag and the respective return to normal) or non condition related events (an operator action). An event itself has no state and only indicates states or state changes. An event client can subscribe for notifications of specified events. An alarm is considered an event that indicates an abnormal condition. It is a specially classified event. The classification is made through an attribute in the event structure and supports filtering.

Event Point An event point represents a defined condition in the system. The event point generates events at the occurrence of a state change of the defined condition. It maintains its current state in terms of active or inactive, acknowledged or unacknowledged, inhibited or uninhibited, and enabled or disabled. Usually an event point exists as part of a tag in a Connectivity Server of 800xA for Melody. The system also provides the option to maintain transient event points for non tag related events. Since the event point maintains the various states of a condition, only events generated by an event point (as opposed to non event point related events) can be inhibited or disabled. The similar entity in the OPC definition is a condition. Consider the event point implementation of 800xA for Melody similar to the implementation of the abstract OPC condition model.

126

3BDD011741R4101


Event Distribution System

Event Distribution System The event distribution system is responsible for collecting the event streams from all Servers in order to generate an overall event stream. They allow client applications to access all events in the system, even though a client application can only subscribe to a subset of the events defined by a filter. This subset is usually functionally oriented (all events of priority one or all system events) rather than Server oriented. The event subsystem makes sure that the various Servers comprising the system are transparent to the client applications. The user can focus on functional aspects rather than knowing how tags are distributed within the system.

Event Concentrators Event concentrators are specialized servers that collect and distribute alarms and events throughout the system. In order to minimize system and network load, event concentrators work in a hierarchical order. Two categories of event concentrators are supported: • Local event concentrators. • Client event concentrators. Event concentrators subscribe to the event stream of other Servers and provide interfaces for clients to subscribe to the resulting event stream. The OPC definition calls all of them alarm/event management systems or alarm/event management Servers. Buffer Capacity

The Event Concentrator's primary event buffer, for incoming events, is designed to hold approximately 2-minutes of event data. The buffer is allowed to expand up to a size of approximately 60,000 events. Local Event Concentrator

Local event concentrators subscribe to the event streams of all Servers running on the same system node (computer). Local event concentrators collect events generated on the local node and make them available to client event concentrators. A local event concentrator needs to be configured for all nodes in the system that

3BDD011741R4101

127

Event Classifications


host Melody Connectivity Servers. If not, events generated from the respective Servers will not be accessible for clients. Redundancy is handled automatically by the event concentrators; no special configuration is required. Client Event Concentrator

Client event concentrators subscribe to the event streams of all local event concentrators in the system that belong to the same 800xA for Melody domain as they do. A client event concentrator combines the event stream of all local event concentrators into a complete event stream of the system. A client event concentrator needs to be configured for every system node (computer) that runs any event client application. This means that all Melody Connectivity Servers must have a client concentrator configured. Client event concentrators have the ability of using a filter. For 800xA for Melody it is recommended not to use filtering.

Event Classifications Events are separated into two classifications: • Alarm. • Status. Typically alarm events are events that require action to resolve the reason for their generation. An example of an alarm event is a boiler temperature exceeding a limit. Status events do not require action to resolve the reason of their generation. An example of a status event is a motors state changing from on to off. The event is identified as an alarm or a status in the event point configuration.

Event Categories Event categories can be used to condense the event state of a tag. Multiple event points in a tag can belong to the same event category. Event client applications (event pages and alarm bars) can interpret the event categories and only present the most important events to an operator instead of all events. This lowers the event noise to the operator. Some example categories are: • Boolean. • Limit.

128

3BDD011741R4101


• •

Event Point Definition

Deviation. Rate.

Event Point Definition In 800xA for Melody an event point represents a single condition, like the high alarm or high-high alarm of a process tag. Multiple event points of one event source can be closely related. In this case the event points belong to the same event category. This gives client applications the option to detect related events and display them accordingly. The definition of event points is part of the definition of the respective tag.

Event Point Attributes An event point in 800xA for Melody is a specialization of PSigBool. It has all the attributes defined for a Boolean signal. The various attributes can be configuration defined, accessible as properties, and updated in accordance with the state of the condition itself. Table 13 and Table 14 identify the different attributes of an event point and provide descriptions. The configuration column (Config) identifies if the attribute is defined through configuration. The Property column identifies if the

3BDD011741R4101

129

Event Point Attributes


attribute is accessible as an property in case the event point exists as part of a tag instance. Table 13. Event Point Identification Attribute Source

Description Name of the source of the event point. Every event point instance is related to one source. For an event point defined as part of a tag the source is the tag name.

EventPointName Identifies the event point inside the source. The event point name is defined in the class of the tag as the signal name and is not configurable.

Config

Prop erty

Yes

Yes2

Class1

No

The signal name in combination with the sender name uniquely identifies the event point: .. An alias is defined the resulting event point name that is overriding the signal name on an “per instance base”. If an alias is defined the resulting event point name is: . NOTES: 1. The configuration is inherited from the class of the object. 2. Only if the event point is defined as part of the tag.

Melody deals inside of the controller not with Function Block Connector names but with Signal names like XH01 (is called ALIAS Name for the Signal), the Signal is connected to the Function block Connector and has therefore a relation to the signal. The usage of the Alias Signal rather than the Event Point Name is configured as default setting during installation of the Melody Server. The Event Point Name has a fixed definition on the Melody Class of the Melody Function block Type. With Melody it is possible to subscribe a configured Event Point and the attributes with OPC DA. The definition can be seen in the Control Connection Aspect in the Object Type Structure. The Melody configures the ALIAS to this Event Point depending on Composer configuration. The general rule is, if the Alias is configured the Event Point is available in the Melody Server.

130

3BDD011741R4101



The following figure shows the event point definition at a Melody object type (Melody Analog Monitor):

MCAE007A

Figure 64. Control Connection Definition of an Event

X1V1/ALI covers the Alias name on Instance if configured.

3BDD011741R4101

131



The current event point configuration can be displayed via Connect Configuration Aspect:

MCAE008A

Figure 65. Overview of Event Point Configuration EPSCAT: Melody only handles only LL and HH. Table 14. Event Point State Attribute

Config

Prop erty

SIG

Represents the current state of the event point. The SIG property is updated even though the event point is not enabled.

No

Yes

PRI

Current priority of the event point.

No

Yes

Associated value. Returns the current value of the property which is associated to the event point (PV for a high alarm).

Class1

Yes

AREF

132

Description

3BDD011741R4101


Behavioral Attributes

Table 14. Event Point State (Continued) Config

Prop erty

Event point is currently unacknowledged. An event point is set to unacknowledged when it goes into active state and is configured to require acknowledge.

Yes

Yes

SUP

Event generation is currently suppressed by configured condition in the system.

No

Yes

COM

Current event comment. Returns the event comment COM0 No or COM1 dependent on the active state of the event point.

Yes

ALARM

Event point is in alarm: ALARM = ACT AND ALMEN.

No

Yes

UNACK

Current state of the event point represents an No unacknowledged alarm: UNACK = UNACKEP AND ALMEN.

Yes

Attribute

Description

UNACKEP

NOTE: The configuration is inherited from the class of the object.

Certain attributes of an event point can be configured if the event point is defined as part of a tag. Two classes of attributes can be distinguished: • Behavioral. • Informational.

Behavioral Attributes Behavioral attributes impact the behavior of the event point in terms of its state machine and actions processed upon state change. The behavioral attributes are shown in Table 15.

3BDD011741R4101

133

Informational Attributes


Table 15. Behavioral Attributes Attribute

Description

Config

ACKR

Event point requires an acknowledge and will be included Yes in the event page. Only events that have ACKR enabled will be represented in the event status page and event bar.

PACK

Page acknowledge enabled. The event point can be acknowledged through a page acknowledge action. If page acknowledge is not enabled the event point can only be individually acknowledged.

Prop erty Yes

This attribute has currently no effect with OperateIT EN

Event point is enabled. If the event point is enabled it will generate events according to state changes of the event point. (An event point can be enabled by configuration action and operator action).

Yes

Yes

DUAL

Event point generates events on transition into active and Yes inactive state. A non dual event point will only generate an event upon transition into active state.

Yes

Melody Composer Configuration COMP

Not implemented

—

—

Informational Attributes Informational attributes do not impact the behavior of the event point. They serve to qualify events generated by the event point to be interpreted by client applications. The informational attributes are shown in Table 16. The list in Table 16 represents a complete set of possible configuration attributes. The actual attributes are dependent on the implementation of the tag type, some of them are defined by default.

134

3BDD011741R4101


Informational Attributes

Event points that are not part of a tag are defined by the application generating the associated events. The configuration of such event points is up to the application itself. Table 16. Informational Attributes Attribute

Description

Config

Property

ALI

Provides a renaming mechanism for the signal name. It is an instance specific configuration attribute. If defined for a given instance the event point can be alternatively addressed and identified by .

DESC1


Yes

Yes

EPSCAT


No

Yes

SIG0


Yes

Yes

SIG1


Yes

PRI0


Yes

Yes

PRI1


Yes

Yes

COM0


Yes

Yes

COM1


Yes

Yes

ALMEN


Yes

Yes

Note: Active event (PRI0)and inactive event (return to normal event) have the same priority (PRI0 = PRI1). NOTES: 1. Only if the event point is defined as part of the tag.

3BDD011741R4101

135

Event Point State Attributes


Event Point State Attributes Event points have several boolean state attributes. They are: • Acknowledged. • Active. • Enabled. • Suppressed. • Inhibited. Acknowledged An event acknowledgment generates an acknowledge event notification. This notification contains the event point description, the current event point state, and the ID of the operator who made the acknowledgment. Figure 66 describes the event point acknowledgement flow. 800xA for Melody supports three different methods for acknowledging an event: • Tag Acknowledgment. • Event Point Acknowledgment. Tag Acknowledgment All event points existing in the tag instance get acknowledged. Event Point Acknowledgment

136

3BDD011741R4101


Event Point State Attributes

Acknowledge is issued for an individual event point. The current state of the event point is acknowledged.

VA L ID AC K N O W L E D G M E N T

IN AC T IV E , U N AC K E D

BECOM ES IN AC T IV E

E N A B LE D, UNSUPPRESSED IN AC TIV E , AC K E D

BECOM ES AC T IV E

AC T IV E , U N AC K E D

BECOM ES IN AC T IV E

AC T IV E , AC K E D

VA LID AC K N O W L E D G M E N T T 040 58A

Figure 66. Event Point Acknowledgment Flow Active An active event is an event point that is in the condition that defines the event. Events become inactive after the condition that caused the event subsides or returns to normal. Enabled Event points can be enabled and disabled. The enable attribute can be configured with a default value. The event point can be enabled and disabled by a client application. A disabled event point will not generate any events. Inhibited An event point can be inhibited by a defined logic. An event point which is currently inhibited will generate events according to its respective event point state changes. These events will be marked as inhibited, giving a client application the option to filter the events.

3BDD011741R4101

137

Dual Event Point Behavior


800xA for Melody tags generically support inhibiting of event points on a tag level. That means all event points of the tag will be inhibited, although certain tag types can support inhibiting individual event points as a reaction to other conditions.

Dual Event Point Behavior Most of the event points have dual behavior. Dual events generate event notifications for active to inactive and inactive to active state transitions. Refer to Figure 66.

Non Dual Event Point Behavior Non dual event points have slightly different behavior. Non dual event points only generate event notifications for inactive to active transitions. They automatically go inactive when they receive a valid acknowledgment.

Redundancy Event System Redundancy The main objective of event system redundancy is providing a continuous event stream across a fail over.

138

3BDD011741R4101


Redundancy

The following figure gives an overview of the architecture of a redundant Alarm and Event System with Melody.

MCAE006A

Figure 67. Redundant AE System with Event Concentrators Message Generation

Events are generated on both active and inactive servers. Event messages contain a field, which specifies their redundant state. For tags that are found in both the primary and the redundant servers, this field typically contains the active/inactive state of the Connectivity Server that contains them. Exceptions are events that are generated by sources that are not in both servers e.g. events generated by hardware or communication failures. The Local Event Concentrator (LEC) reads both event streams but only forwards active event messages to clients for display. During a fail over, the LEC is responsible for deciding which "inactive" event it received should now be forwarded to the event clients. The Connectivity Server event system has no responsibility for event system redundancy other than to mark each event message with the correct redundancy state.

3BDD011741R4101

139

Severity, OPC Severity and Device Priority


The Connectivity Server will maintain at an event for a minimum amount of time seconds worth of events. The default for this will be 30 seconds but will be modifiable through a registry entry (LookOutTime). Message synchronization

For event system redundancy, duplicate event messages must be generated on the active and inactive servers for tags that are duplicated in the primary and redundant servers. Tags that occur on only one of the servers or events generated through the Event API are not synchronized. The individual servers must insure that duplicate events are generated for tags that are duplicated on redundant servers. Direct synchronization of events will not be done, however all "Puts" will be echoed and servers must use these message to insure that event messages are duplicated.

Severity, OPC Severity and Device Priority The severity value is an indication of the urgency of the sub-condition. This is also commonly called 'priority', especially in relation to process alarms. Values will range from 1 to 1000, with 1 being the lowest severity and 1000 being the highest severity. Typically, a severity of 1 indicates an informal event while a value of 1000 indicates a very important event of dangerous nature. The priority mapping has to be harmonized with Faceplates and Graphics to have the OPC alarms fitted. (texts, priority, colors).

OPC Severity It is expected that few server implementations will support 1000 distinct severity levels. Therefore, server developers are responsible for distributing their severity levels across the 1 - 1000 range in such a manner that clients can assume a linear distribution.

Client Severity Clients can assume a linear distribution.

140

3BDD011741R4101


Device Severity (Melody Priorities)

For example, a client wishing to present five severity levels to a user should be able to do the following mapping: Table 17. Client Severity Mapping Client Severity

OPC Severity

HIGH

801 - 1000

MEDIUM HIGH

601 - 800

MEDIUM

401 - 600

MEDIUM LOW

201 - 400

LOW

1 - 200

Device Severity (Melody Priorities) Melody has 16 Priorities. Priority 1 is the highest and Priority 16 is the lowest Priority. Within the Connectivity the default Mapping to OPC Severities and the 16 Melody priority levels results in to the following global mapping: Table 18. Priority Mapping

3BDD011741R4101

Melody Priority OPC AE Severity

Process Portal Priority

1

1000

938 - 1000

2

900

875 - 937

3

850

812 - 874

4

800

749 - 811

5

700

686 - 748

6

650

623 - 685

7

600

560 - 622

8

500

497 - 559

141

Device Severity (Melody Priorities)


Table 18. Priority Mapping Melody Priority OPC AE Severity

Process Portal Priority

9

450

435 - 496

10

400

373 - 434

11

350

311 - 372

12

300

249 - 310

13

200

187 - 248

14

150

125 - 186

15

100

63 - 124

16

1

1 - 62

The ’0’ Priority is mapped the OPC Severity zero. The consistent mapping for each connectivity server within a system is not checked, i.e. the configured OPC-mapping must be the same for all connectivity servers.

142

3BDD011741R4101

Section 7 Time Synchronization

Operation Overview

Section 7 Time Synchronization Introduction The time synchronization mechanism keeps the time synchronized without doing step changes, which can cause data collection to be inaccurate. The majority of time synchronization activity will be done by components of the 800xA for Melody system part. The only nodes that will have time adjustments carried out by the 800xA Process Portal system part, are nodes that do not have a Melody Connectivity Server running. The 800xA for Melody shall always be time master for the system. The Melody Control module can be connected to a radio controlled clock. For detailed information refer to the modules technical information. 800xA Process Portal Time Server can only be configured for nodes that have 800xA for Melody Servers installed. Ideally, there should be two Time Servers configured, one for each Connectivity Server of a redundant pair. If there isn’t any external time source available then the Time Servers negotiate a time master among themselves and keep the time using the Windows clock.

Operation Overview The time synchronization function is provided through the Time Server service. This service synchronizes the system clocks, distributes time and time zone changes.

3BDD011741R4101

143

Operation Overview


A time adapter allows the 800xA for Melody to be a time source. This will then allow participation in the standard 800xA Process Portal time synchronization.

MCTS008A

Figure 68. Synchronization Direction The Time Service can be used to synchronize the time on the server and client nodes that are defined in a system. This service can also be used to change the current time in the system. The Time Service has two components, a Time Server and a Time Client. Time Server (Service Provider)

The Time Server component is the administrator for the time synchronization. It receives and distributes the time synchronization telegrams to/from other nodes, and it makes the final decision on which telegram to accept and broadcast to the network. The Time Server should be active on the same node as the 800xA for Melody software (Connectivity Server). By default the Time Server is installed on all System Product server nodes.

144

3BDD011741R4101


Time Adjustment

There must be at least one Time Server enabled in the network for the Time Service to be in operation. In the case of redundancy, where more than one node is configured as a Time Server, only one of the nodes will be active (in Service State), the other nodes will be passive (in Standby State). Time Client (Service Handler)

A Time Client is responsible for keeping the date and time in its node updated and synchronized with the global time broadcasted from the Time Server. It is also responsible for allowing or disallowing manual setting of date and time, according to how it is configured. A Time Client resides in all System Product nodes.

Time Adjustment The Melody Connectivity Server gets the time from the control network and sets the time to the Time Synchronization Daemon. The Time Synchronization Daemon then sets the nodes clock on which it is running and synchronizes also all nodes running this Daemon, actually all Connectivity Server for Melody.

If Windows is the time source then the normal Windows clock adjustment dialog is used to set the time but: Time synchronization shall only be done by the Melody control network.

3BDD011741R4101

145

800xA Process Portal Time Server Configuration


800xA Process Portal Time Server Configuration If a Connectivity Server node is added to the system, a Time Server service provider is automatically added to Services > Time, Service > Basic, Service Group. The server provider can be configured via the Service Provider Definition aspect.

MCTS009A

Figure 69. Time Server Service Provider Configuration Any service providers added for nodes that do not have 800xA for Melody server installed and are not connected to the Melody Unit that is the Time Source, must be removed or disabled (otherwise the active Time Server could end up broadcasting a time that differs a lot from the Time Synchronization Daemon time).

146

3BDD011741R4101


800xA Process Portal Time Server Handler Configuration

800xA Process Portal Time Server Handler Configuration All 800xA Process Portal client and server nodes have a TimeServerHandler aspect under the Node Administration Structure under Node Administration > All Nodes, Node Group > , Node.

MCTS010A

Figure 70. Time Server Handler Aspect Configuration

For the configuration settings refer to the following Table 19:

3BDD011741R4101

147

Windows Time Synchronization Service (W32Time)


Table 19. Time Server Handler configuration Dialog element

Description

Allowed To Set Time

Should be unchecked for all nodes, to prevent users from changing the system clock

TimeSync Running

Has to be checked on all Process Portal nodes.

Deviation Limit

For Connectivity Server that act as Time Source the “Deviation Limit” should be remain on the default value of 1000 msec.

Windows Time Synchronization Service (W32Time) Windows supports its own time synchronization service (W32Time). The Industrial IT ’System Time Service’ provides higher synchronization accuracy than the ’Windows Time Synchronization Service’. Furthermore there isn’t any support for time synchronization between the ’Windows Time Synchronization Service’ and the control network! During the installation of 800xA for Melody the Windows Time Synchronization Service “W32Time” will be automatically disabled on the Connectivity Server. The Windows Time Synchronization Service must remain disabled. In case the W32Time Service was unintentionally turned on it can be disabled as follows: 1. On the Windows Domain Server node, go to the Start menu > Control Panel. 2. Select Administrative Tools > Services. 3. Scroll down to Window Time and double-click, this opens a dialog box. 4. Press the Stop button in Service Status field and select Manual in the Startup Type drop-down menu.

148

3BDD011741R4101


Master Clock Configuration in Melody

Master Clock Configuration in Melody The Master Clock Function for the Melody Controller can be activated in the Composer Mask “Specific Process Item Data” belonging to the controller module. Melody uses the UTC Time. For special function blocks (Calendar function and time function blocks) it is necessary to configure ’Day Light Saving Time’ (Summer time). The Melody Controller module can be connected to a radio controlled clock.

MCTS007A

Figure 71. Melody Master Clock Configuration For detailed information refer to the technical information of the controller module. The final configuration of the Melody module has to be checked by using the diagnostic tool Melody Analyser (see Configuration Check with Melody Analyser).

3BDD011741R4101

149

Configuration of Melody Server as Time Master


Configuration of Melody Server as Time Master The Time Synchronization Daemon is installed on each Melody Connectivity Server as service. Either the Melody Server or the redundant Melody Server needs to be configured as Time Master to pick up the time from the Melody module that broadcasts the Melody Time Message. The following modification has to be done in the Windows registry. HKEY_LOCAL_MACHINE\SOFTWARE\ABB\PWC Table 20. Registry Settings for the Melody Time Master Server Primary Connectivity Server

timesync_priority = 10

Redundant Connectivity Server

timesync_priority = 9

MCTS001A

Figure 72. Windows Time Master Registry Settings

150

3BDD011741R4101


Configuration of Melody Server as Time Master

MCTS002A

Figure 73. Editing TimeSync_priority for Primary Connectivity Server After the setting of both (primary and backup) connectivity server timesysnc_priority entries the time synch daemon has to be restarted.

MCTS005A

Figure 74. Time Sync Daemon Restart

3BDD011741R4101

151

Deleting all Services that are not Time Master


Deleting all Services that are not Time Master During installation 800xA Process Portal activates Time Server Groups on all server nodes by default. It is required to delete all Basic, Service Groups and Service Providers of Time Service other than the selected Time Master on the Connectivity Servers. The following Figure 75 shows how to find out the Connectivity Server that works as Time Master.

MCTS017A

Figure 75. Indicating Connectivity Servers Working as Time Master Note: In the example the pair of redundant Connectivity Server MELSTT017 and MELSTT018 are working as Time Master.

152

3BDD011741R4101


Melody TimeSync Daemon installation

Melody TimeSync Daemon installation For Melody Connectivity Servers and for the Melody Config Server the TimeSync Daemon is automatically installed during installation. Computer that neither belong to Melody nor to the 800xA Process Portal but that need a time synchronization (e.g. dedicated Domain Controller) must have a TimeSync Daemon installed or must use the SNTP protocol. To install the TimeSync Daemon PC that neither belongs directly to Melody nor to 800xA Process Portal follow: 1.

Create a new directory on drive c: of the PC that has to be prepared for running the TimeSync Daemon (e.g.: c:\tsync).

2.

Open the directory \Program Files\ABB Industrial IT\Operate IT\Base on a Melody Connectivity Server.

3.

Copy the files nwkdll.dll, tsyncCtrl.exe and tsyncdd.exe to the newly directory on drive c: (e.g.: c:\tsync) of the computer prepared to run the TimeSync Daemon.

4.

Change to the directory containing the copied files (c:\tsync).

5.

Run tsynchdd.exe -install to install the TimeSync Daemon on the computer.

6.

Disable the Windows Time Synchronization Service (W32Time)

For settings referring to the SNTP protocol follow the Industrial IT 800xA Automation System Network, Design and Configuration Guide (3BSE034463).

3BDD011741R4101

153

DHCP Configuration for Time Synchronization


DHCP Configuration for Time Synchronization The Melody CCO / CMC / PM 875 modules get their IP-addresses via DHCP. At least one (preferably a redundant) Melody module has to be configured to broadcast time messages to the Melody Connectivity Server. For that purpose it is necessary to configure the Melody specific DHCP option 161 in the DHCP Server.

MCTS011A

Figure 76. DHCP Configuration for Transmission of Time Synchronization The final configuration of the Melody module has to be checked by using the diagnostic tool Melody Analyser (see “Checking the Configuration with Melody Analyser”).

154

3BDD011741R4101


Checking the Configuration with Melody Analyser

Checking the Configuration with Melody Analyser The final configuration of the Melody module concerning Master clock and time gateway setting has to be checked by using the diagnostic tool Melody Analyser (for details see also Technical Information 30/72-8062).

MCTS012A

Figure 77. Configuration Check with Melody Analyser

Checking the Master Time Daemon with TsyncCTRL Tool The Master Time Daemon service is part of the 800xA for Melody software. The diagnostic tool tsyncCTRL on the Melody Connectivity Server Nodes helps to find the time master. To find the master time daemon enter msite. The master time daemon then shows the node with the daemon running with highest priority. If either the Time Synchronization Daemon is not running or if there is a wrong configuration order of network cards then the program tsyncCTRL indicates an error.

3BDD011741R4101

155

Multiple Network Adaptors configuration specifics


In case the time daemon with priority 10 is not available, then the daemon with highest priority becomes “master time daemon” of the system.

MCTS006B

Figure 78. Time Sync Daemon Restart

Multiple Network Adaptors configuration specifics If multiple network cards shall be used then the card that is binding to an other Time Synchronization Daemon has to be on the first network card. In case of multiple network cards the following applies: - The operations network card must be the first in the binding order. - The Control System network card must not the first network card. You can configure the binding order on most machines by changing the following configuration. Go to the Network and Dial-up Connections in the Settings. On the Advanced Tab select Advanced Settings.

156

3BDD011741R4101



Move the Network Card to the 800xA Process Portal System to top.

MCTS013B

Figure 79. Multiple network card configuration

3BDD011741R4101

157



Reboot the computer and check your configuration with the DOS command “route print”.

MCTS014A

Figure 80. Example for a Route Print Command Output In the last line at Network Destination 255.255.255.255 normally the network adapter IP-Address to the operations network appears. On some DELL computers there can be a problem if the internal NIC is not connected to the operations network. The configuration made in the Network and Dial-up Connections is ignored. In this case the operations network has to be connected to the internal network adapter.

158

3BDD011741R4101


Multiple Network Adaptors Binding example

Multiple Network Adaptors Binding example

MCTS015A

Figure 81. Example for Correct Binding Configuration

3BDD011741R4101

159

Time Synchronization Options


Operations network card is configured to have IP address 172.16.4.1

MCTS016A

Figure 82. Operations Network Card is (correct) Last Entry

Time Synchronization Options The TimeSync Configuration Tool allows to change the Network Interface IP address of the network interface that is responsible for time synchronization

MCTS018A

Figure 83. Time Synchronization Options .Start > All Programs > ABB Industrial IT 800xA > 800xA for Melody > Diagnostics > TimeSync Configuration

160

3BDD011741R4101


Melody Server SYSLOG Time Synchronization Diagnostic

Melody Server SYSLOG Time Synchronization Diagnostic It is recommended to set up the Melody Server SYSLOG to log Time Synch Messages on the Melody Connectivity Server (pair) that works as time master. To provide every time a little diagnostic output for the Melody time synchronization, it is recommended to check the Bit 36: Time synchronization on the EbMelodyServer. The changes can be made using the tool “..\Operate IT\Base\SysLogModify.exe”. The Melody log file “..\Operate IT\Base\syslog.log” contains the data.

Figure 84. Time Synchronization Debug Traces for Melody Server

3BDD011741R4101

161

Melody Server SYSLOG Time Synchronization Diagnostic


Example for WRONG Adapter ORDER (Syslog):

20.03.2003 17:44:12.985 : EB_DB36 CEbMelodyScan::SetConsoleTime 'Call NetAdjSystemTime with -262 seconds' 20.03.2003 17:44:17.993 : EB_DB36 CEbMelodyScan::SetConsoleTime 'NetAdjSystemTime -262 seconds returns not zero' 20.03.2003 17:44:27.977 : EB_DB36 CEbMelodyScan::TimeSyncThread 'Got Time from 172.32.1.10'

Example for CORRECT Adapter ORDER (Syslog):

20.03.2003 17:54:24.821 : EB_DB36 CEbMelodyScan::SetConsoleTime 'called with diff seconds to actual time: -259' 20.03.2003 17:54:24.821 : EB_DB36 CEbMelodyScan::SetConsoleTime 'Library nwkdll.dll loaded' 20.03.2003 17:54:24.821 : EB_DB36 CEbMelodyScan::SetConsoleTime 'Call NetAdjSystemTime with -259 seconds' 20.03.2003 17:54:24.830 : EB_DB36 CEbMelodyScan::SetConsoleTime 'NetAdjSystemTime -259 seconds returns zero'

162

3BDD011741R4101

Section 8 Backup and Restore General The following is a general information about the Melody Configuration Backup and Restore: •

The sessions on screen status entries are appended to a backup or restore log file. The user must manually erase any unwanted entries or Rename/Delete the log file to start a fresh log. The log file is initially created in the Windows 2000 / Windows 2003 accounts temporary directory location. The screen form contains a log file icon that opens the log file in a Notepad application window for viewing, printing, or editing of the log file.

•

Must be run on the Melody ConfigServer while logged in to the Service Account for this product. Recommendations: Typically, run the Backup option after creating a database for the first time. Run the Backup option before doing an upgrade or making significant changes the system configuration. Run the Restore option when the system becomes corrupt or after and upgrade takes place

Access This feature is accessed through Start > (All) Programs > ABB Industrial IT 800xA > 800xA for Melody > Configuration on the ConfigServer node.

3BDD011741R4101

163

Function

Section 8 Backup and Restore

Function The 800xA for Melody Backup or Restore feature allows the user to manually initiate a backup or restore that supports either the full backup or full restore of the SQL 800xA for Melody configuration contained in its SQL database. The backup or restore operation sequences through all steps are required to complete the operation requested. The user backup process consists of the user selecting an aspect system name and file location to contain a standard SQL backup set and initiating the backup for the Melody ConfigServer. This includes the Melody Connectivity Server backup because of the snapshot done in the same procedure. The user restore process consists of the user selecting an existing SQL backup set filename and initiating the restore operation. For support during the ConfigServer backup the Microsoft SQL-Server online help is also available.

Backup Industrial IT Melody Composer The Composer backup and restore procedure is described in the Technical Information TI 30/72-8001-EN “Hardware, Software and Backup”.

Backup ConfigServer The backup has to be stored on a local disk or on a tape connected to the local computer. A backup via network drive is not possible!

During the backup configuration changes must not be performed!

164

3BDD011741R4101


Backup ConfigServer

Backup Configuration Use the following procedure to save 800xA for Melody information: 1.

Log in to the 800xA for Melody local service account on the Config Server node.

2.

Use the 800xA for Melody Config backup / restore utility to create a backup of the Melody Config Server database. a.

Select All Programs > ABB Industrial IT 800xA > 800xA for Melody > Configuration > Backup Configuration

b.

Click Connect in the 800xA for Melody Configuration Backup/Restore window.

This initiates the connection to the configuration database using the current Windows 2000 / Windows 2003 account security. This account must have Administrative access to the system and ConfigServer database (800xA for Melody Service account). The file name is auto generated using the ConfigServer name, date and time. Example: ConfigServer_20020521_1034.bak c.

Click Backup.

Clicking on the Status Log icon shows the log file. This text file can be saved.

The Backup button manually initiates the SQL database backup operation. Only one single backup is stored per file. If the backup file already exists it is overwritten! d.

3BDD011741R4101

Click Exit when the backup is complete.

165

Restore ConfigServer


Restore ConfigServer Use the following procedure to restore existing 800xA for Melody ConfigServer information: 1.

Log in to the 800xA for Melody local service account on the ConfigServer node.

2.

Use the 800xA for Melody Config backup / restore utility to restore the Melody Configuration information from a saved backup. a.

Select All Programs > ABB Industrial IT 800xA > 800xA for Melody > Configuration > Restore Configuration

a.

Click Connect in the 800xA for Melody Configuration Backup/Restore window.

The Connect button manually initiates the connection to the configuration database using the current Windows account security. This account must have Administrative access to the system and Configuration Server database (800xA for Melody Service Account). Refer to the MSSQL file folders for the .bak files generated upon successful backup. The last successful backup name is preloaded into the screens Backup/Restore Backup File name field. b.

Enter the name of the 800xA for Melody Config Server database backup file in the Backup File field.

c.

Click Restore.

d.

If prompted that the system version does not match the backup version, click OK.

If the message Services must be stopped, REBOOT system now then restart this application! is displayed, restart the node and repeat Step a through Step e. e.

166

Click Exit when the restore operation is complete.

3BDD011741R4101



After restoring a ConfigServer restart all Connectivity Server sequentially and wait to start the next Connectivity Server until the former Connectivity Server has finished SQL replication. This sequence avoids a high Config Server load and replication time-outs due to parallel replication after a parallel restart of several Connectivity Server.

3BDD011741R4101

167


168


3BDD011741R4101

Section 9 Melody Automation Classes Operator Interface Faceplate

The faceplate is the interface with the operator. In the faceplate, all the information required for process control is displayed in graphical form. The operating elements required for process operation are provided in the faceplate, according to the function. The pre-defined faceplate from the 800xA Process Portal template is assigned as part of code generation in Composer. Certain faceplates are provided as standard for the individual automation class. In addition to these, project-specific faceplates can be available. If required, the faceplate for the entity can subsequently be replaced by another faceplate. To get more information about Faceplate refer to following documents: •

IIT 800xA - System, 800xA for Melody System Version 4.0 - Operation (Utility)

•

IIT 800xA - System, 800xA for Melody System Version 4.0 - Operation (Process Industry)

3BDD011741R4101

169

MelodyAnalog – Analog monitoring

Section 9 Melody Automation Classes

MelodyAnalog – Analog monitoring Features The analog monitoring (MelodyAnalog) automation classes allow a freelyconfigurable analog monitoring function from Melody to be displayed in a data structure in 800xA Process Portal. Analog process variables with the option of MvN selection, up to 8 limit value variables and 4 binary process variables. A selection of pre-configured faceplates is available.

Configuration The MelodyAnalog automation class displays the analog monitoring function from the Melody automation system in a variable structure in 800xA Process Portal. This standard display is configured by connection of the process signals in Composer for Melody. As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the Melody connection components. The configuration data can be tailored to meet the requirements of the operator in the tag configuration screens in 800xA Process Portal. The configuration from Composer is described in the technical information “Commissioning a system”, Technical Information 30/72-8055. Composer function block and signal definitions

The following figures show the function blocks (monitoring blocks) used to display the process variables in 800xA Process Portal. The function block connections on the monitoring block identify signals exchanged between Melody and 800xA Process Portal. The input variables, shown on the left, originate from the automation process. The output variables, shown on the right, originate from 800xA Process Portal or an external control function. To permit the exchange of process signal data between Melody and 800xA Process Portal, the function block connections on the monitoring function block must be connected to the function blocks in Melody.

170

3BDD011741R4101


Configuration

Connection behavior of the function block connections on the monitor block: CSCANA1

CSCANA2

CSCANA3

alw

=

Always Signal is always/must always be connected.

ext

=

External control Signal is only created if the option “Extended code generation” is selected in Composer (application e. g. recipe).

opt

=

Optional Signal is only created if the function block connection in Composer is connected and explicitly opened in alphanumeric format.

3BDD011741R4101

171

Configuration


Connection example for the Melody Analog automation class (data link to 800xA Process Portal using CSCANA1 function block)

The CSCANA1 monitoring block allows one analog signal, eight limit value signals and four binary signals to be combined. Connection example for the Melody Analog automation class (data link to 800xA Process Portal using CSCANA2 function block)

The CSCANA2 monitoring block allows one analog signal, eight limit value signals and four binary signals to be combined. With the assistance of three signal

172

3BDD011741R4101


Configuration

references (RX1 … RX3), functional relationships for process control by the operator can be edited (signpost to another function). Used e. g. for MvN selection. Connection example for the Melody Analog automation class (data link to 800xA Process Portal using CSCANA3 function block)

The CSCANA3 monitoring block allows three analog signals, eight limit value signals and four binary signals to be combined. All limit value signals relate to the analog signal X1. The automation function in 800xA Process Portal is configured using code generation for Operations in Composer. Depending on the monitoring block used and the function block connections, a faceplate tailored to the function is assigned as part of the code generation for Operations.

3BDD011741R4101

173

Configuration


Event typical

The signalling behavior of a function is defined by specifying the behavior of the signal in Composer. The event typical is connected to the process signal. The following configuration data is defined as part of an event typical: •

Priority of the signal (Prio)

•

Generate signal (SGen)

•

Signal as alarm (Al)

•

Signal page acknowledge (PAck)

•

Dual-value signal (Dual)

•

Signal inhibitable (Inhibi) #

•

Signal can be suppressed (Supp) #

•

Signal generation for negative edge change (Logic) #) Information is only evaluated in code generation for Operations.

The status texts are defined for the signal itself.

174

3BDD011741R4101


Automation class

Automation class Structure

The following table describes the structure of the automation class for the Melody Analog analog monitoring function. Atom

Description

OPC data type

Melody data type

Melody Read Write I/O

X1

Real input

Double (w)

Real

I

X

Extended Boolean

I

X

X1/ALARM

Bool

X1/UNACK

Bool

X1V1

Limit signal 1 for X1

Bool

X1X1

Limit value 1 for X1 (actual)

Double (w)

YX11

Limit value 1 for X1

Double (w)

Real

O

X1V2


Bool

Extended Boolean

I

X1X2


Double (w)

YX12


Double (w)

Real

O

X1V3


Bool

Extended Boolean

I

X1X3


Double (w)

YX13


Double (w)

Real

O

X1V4


Bool

Extended Boolean

I

3BDD011741R4101

Write access

X

High limits

X

Computer mode

X

High limits

X

Computer mode

X

High limits

X

Computer mode

X

X

X

175

Automation class

176


Atom

Description

OPC data type

Melody data type


X1X4


Double (w)

YX14

Limit value 4

Double (w)

Real

O

X1V5


Bool

Extended Boolean

I

X1X5


Double (w)

YX15

Limit value 5

Double (w)

Real

O

X1V6


Bool

Extended Boolean

I

X1X6


Double (w)

YX16

Limit value 6

Double (w)

Real

O

X1V7


Bool

Extended Boolean

I

X1X7


Double (w)

YX17

Limit value 7

Double (w)

Real

O

X1V8


Bool

Extended Boolean

I

X1X8


Double (w)

YX18

Limit value 8

Double (w)

Real

RX1

Reference to 1st analog value

Double

ATOMREF

O

Write access

X

High limits

X

Computer mode

X

Low limits

X

Computer mode

X

Low limits

X

Computer mode

X

Low limits

X

Computer mode

X

Low limits

X

Computer mode

X

X

X

X

3BDD011741R4101


Automation class

Atom

Description

OPC data type

Melody data type


RX2

Reference to 2nd Double analog value

ATOMREF

RX3

Reference to 3rd analog value

Double

ATOMREF

RX4

Reference to 4th analog value

Double

ATOMREF

X2

Real input

Double

Real

I

X

X3

Real input

Double

Real

I

X

X4

Real input

Double

Real

I

X

I1

Boolean input

Bool

Extended Boolean

I

X

I2

Boolean input

Bool

Extended Boolean

I

X

I3

Boolean input

Bool

Extended Boolean

I

X

I4

Boolean input

Bool

Extended Boolean

I

X

Write access

Legend for columns: Atom

Atom name

Description

Descriptive information for the atom

OPC data type

800xA Process Portal data type

Melody data type

Melody data type

Melody I/O

800xA Process Portal monitoring block input/output

Read

Atom can be read in 800xA Process Portal.

Write

Atom can be written from 800xA Process Portal. (Control – operator action or external control system)

Write access

Atom requires the access rights specified for write access.

3BDD011741R4101

177

Automation class


Calculated atoms

Calculated atoms are atoms, which are derived from values from other atoms, according to a defined processing standard. The atoms are calculated centrally in Melody Connectivity Server.

178

Atom:

Description:

Processing standard:

.BAD/SIG

Quality of process signals OR (X1/SIG, X2/SIG, X3/SIG, X4/SIG, X1V1/SIG, transmitted X1V2/SIG, X1V3/SIG, X1V4/SIG, X1V5/SIG, X1V6/SIG, X1V7/SIG, X1V8/SIG, I1/SIG, I2/SIG, I3/SIG, I4/SIG)

.ALARM

General function fault, alarm signal pending

OR (X1V1/ALARM, X1V2/ALARM, X1V3/ALARM, X1V4/ALARM, X1V5/ALARM, X1V6/ALARM, X1V7/ALARM, X1V8/ALARM, I1/ALARM, I2/ALARM, I3/ALARM, I4/ALARM)

.UNACK

General function fault, alarm signal pending, error status not yet acknowledged

OR (X1V1/UNACK, X1V2/UNACK, X1V3/UNACK, X1V4/UNACK, X1V5/UNACK, X1V6/UNACK, X1V7/UNACK, X1V8/UNACK, I1/UNACK, I2/UNACK, I3/UNACK, I4/UNACK)

.X1/ALARM

Limit value violation with alarm signal pending

OR (X1V1/ALARM, X1V2/ALARM, X1V3/ALARM, X1V4/ALARM, X1V5/ALARM, X1V6/ALARM, X1V7/ALARM, X1V8/ALARM)

.X1/UNACK Limit value violation with alarm signal pending, error status not yet acknowledged

OR (X1V1/UNACK, X1V2/UNACK, X1V3/UNACK, X1V4/UNACK, X1V5/UNACK, X1V6/UNACK, X1V7/UNACK, X1V8/UNACK)

3BDD011741R4101


MelodyAnMon – Analog monitoring

MelodyAnMon – Analog monitoring Features The analog monitoring (MelodyAnMon) automation class allows the pre-configured analog monitoring function from Melody to be displayed in a data structure in 800xA Process Portal. The pre-configured automation function in Melody has the functions of replacement and alternative value processing, root extraction, linearization, delimitation, transient and limit value checking.

Configuration The MelodyAnMon automation class displays the analog monitoring function from the Melody automation system in a variable structure in 800xA Process Portal. This standard display is configured by connection of the process signals in Composer for Melody. As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the Melody connection components. The configuration data can be tailored to meet the requirements of the operator in the tag configuration screens in 800xA Process Portal. The configuration from Composer is described in the technical information “Commissioning a System", Technical Information 30/72-8055. Composer function block and signal definitions

The figures below show the function blocks for the analog monitoring function in Composer. The function blocks have an integrated monitoring block for the link to 800xA Process Portal. The connections to the Melody function block identify input and output signals in Melody. Data is exchanged between Melody and 800xA Process Portal, through the internal

3BDD011741R4101

179

Configuration


connections of the Melody function block with a monitoring block inside the yellow backed case.

180

ANMONB

ANMONS

ANMONM

ANMONL

3BDD011741R4101


Configuration

Connection behavior of the function block connections on the monitoring block: alw

=

ext

=

opt

=

Always Signal is always/must always be connected. External control Signal is only created if the option “Extended code generation” is selected in Composer (application e. g. recipe). Optional Signal is only created if the function block connection in Composer is connected and explicitly opened in alphanumeric format.

The automation function in 800xA Process Portal is configured using code generation for Operations in Composer. Event typical

The signalling behavior of a function is defined by providing an event typical or specifying the behavior of the signal in Composer. The event typical is connected to a process signal. The following configuration data is defined as part of a event typical: • • • • • • • • • •

Priority of the signal (Prio) Generate signal (SGen) Signal as alarm (Al) Signal page acknowledge (PAck) Dual-value signal (Dual) Signal can be inhibited (Inhib) # Signal can be suppressed (Supp) # Signal generation for negative edge change (logic) Operator profile (PROF) Packed Boolean sub-variant $ #) Information is only evaluated in code generation for Operations. $) Only defined for event typicals for Packed Boolean signals.

3BDD011741R4101

181

Configuration


For the configuration of signalling behavior in Composer, a distinction is made between the event typical for Boolean signals and the event typical for Packed Boolean signals. Event typicals for Boolean signals define the signalling behavior of precisely one binary signal. Event typicals for Packed Boolean signals define the signalling behavior of the individual binary signals packed in the signal (max. 32). For the XSTA function block connection in the MelodyAnMon automation class, the event typicals VAM and VAM2 are defined as standard in Composer. These event typicals refer to a sub-variant, which describes the structure and status texts for the packed Boolean signal.

182

3BDD011741R4101


Configuration

Structure of an event typical using the example of VAM1. The signalling behavior can be adjusted on a project-specific basis. Event typical VAM1 Brief desc.

Name VAM1

PROF 0

VAM1

Explanatory text ANMON XSTA with events

Packed Boolean sub-variant ANMON_1

MIdx

Csel

Prio

110

SUO

10

111

ATO

10

112

AKO

9

113

HVO

10

114

LVO

10

115

TRO

4

189

AHHN

10

190

AHN

10

191

ALN

10

192

ALLN

10

193

AHDN

10

194

ALDN

10

195

AHTN

10

196

ALTN

10

SGen

Al

PAck

Dual

Inhib

Supp

Logic

Status texts

The status texts for the Boolean signals are configured in Composer. The status texts for individual items of binary information within a packed Boolean signal are not configured in Composer. These status texts are shown in the subvariant (e. g. ANMON_1) referred to by the event typical. The sub-variant is stored in the Importer for 800xA Process Portal).

3BDD011741R4101

183

Configuration


Structure of a sub-variant using the example of ANMON_1. The status texts and the alias can be adjusted on a project-specific basis. Table: Alias name and status texts for sub-variant ANMON_1

184

ATOM

Alias

SUS

SUS

Status text 1

Status text 0

SUO

SUO

SV Act

(SV Act)

ATO

ATO

AV Act

(AV Act)

BFO

BFO

AKO

AKO

AccLock

(AccLock)

HVO

HVO

MsgMax

(MsgMax)

LVO

LVO

MsgMin

(MsgMin)

TRO

TRO

MsgTrans

(MsgTrans)

RDO

RDO

AHHN

AHHN

AHH Sup

(AHH Sup)

AHN

AHN

AH Sup

(AH Sup)

ALN

ALN

AL Sup

(AL Sup)

ALLN

ALLN

ALL Sup

(ALL Sup)

AHDN

AHDN

AHD Sup

(AHD Sup)

ALDN

ALDN

ALD Sup

(ALD Sup)

AHTN

AHTN

AHT Sup

(AHT Sup)

ALTN

ALTN

ALT Sup

(ALT Sup)

AHHO

AHHO

AHO

AHO

ALO

ALO

ALLO

ALLO

AHDO

AHDO

ALDO

ALDO

AHTO

AHTO

ALTO

ALTO

3BDD011741R4101


Automation class


The following table describes the structure of the automation class for the MelodyAnMon analog monitoring function. Table: Structure of the MelodyAnMon automation class Atom

Description

OPC data type

Melody data type

Melody Read Writ I/O e

XSTA

Actual value status

Integer

Packed Boolean

I

SUS

Alternative value trigger active

Bool

SUO

Alternative value active

Bool (w)

X

Lock operator access

ATO

Alternative value set

Bool (w)

X


ATOR

Reset alternative value

Bool (w)

X


BFO

Switching impulse filter active

Bool

AKO

Access locked

Bool (w)

X


AKOR

Reset operator access lock

Bool (w)

X


HVO

H limit reached

Bool

LVO

L limit reached

Bool

TRO

Transient violation

Bool

RDO

Characteristic curve reversal

Bool

AHHN

No HH limit

Bool

AHN

No H limit

Bool

ALN

No L limit

Bool

ALLN

No LL limit

Bool

AHDN

No H tolerance

Bool

3BDD011741R4101

Write access

X

185

Automation class

186


ALDN

No L tolerance

Bool

AHTN

No H transient

Bool

ALTN

No L transient

Bool

AHHO

HH limit active

Bool

AHO

H limit active

Bool

ALO

L limit active

Bool

ALLO

LL limit active

Bool

AHDO

H tolerance active

Bool

ALDO

L tolerance active

Bool

AHTO

H transient active

Bool

ALTO

L transient active

Bool

MDO

Operation control word

Integer (w)

Packed Boolean

O

Y

Real output

Double

Real

I

X

X

Y/ALARM

Bool

Y/UNACK

Bool

XRY

Non-linearised value

Double (w)

Real

I

ATV

Alternative value

Double (w)

Real

O

XSUY

Alternative value

Double

Real

I

X

WY

Setpoint

Double (w)

Real

I

X

W

External setpoint

Double (w)

Real

O

AHHY

HH limit signal

Bool

Packed Boolean

I

AHHX

HH limit value (actual) Double (w)

AHHV

HH limit value

Double (w)

Real

O

AHY

HH limit signal

Bool

Packed Boolean

I

AHX

H limit value (actual)

Double (w)

X

Computer mode

X

Setpoint control

X

Computer mode

X

Setpoint control

X

Computer mode

X

High limits priority

X

Computer mode

X

High limits

X

X

3BDD011741R4101


Automation class

AHV

H limit value

Double (w)

Real

O

ALLY

LL limit signal

Bool

Packed Boolean

I

ALLX

LL limit value (actual)

Double (w)

ALLV

LL limit value

Double (w)

Real

O

ALY

L limit signal

Bool

Packed Boolean

I

ALX

L limit value (actual)

Double (w)

ALV

L limit value

Double (w)

Real

O

AHDY

H tolerance signal

Bool

Packed Boolean

I

AHDX

H tolerance value (actual)

Double (w)

AHDV

H tolerance value

Double (w)

Real

O

ALDY

L tolerance signal

Bool

Packed Boolean

I

ALDX

L tolerance value (actual)

Double (w)

ALDV

L tolerance value

Double (w)

Real

O

AHTY

H transient signal

Bool

Packed Boolean

I

AHTX

H transient value (actual)

Double (w)

AHTV

H transient value

Double (w)

Real

O

ALTY

L transient signal

Bool

Packed Boolean

I

ALTX

L transient value (actual)

Double (w)

ALTV

L transient value

Double (w)

3BDD011741R4101

Real

O

X

Computer mode

X

Low limits priority

X

Computer mode

X

Low limits

X

Computer mode

X


X

Computer mode

X

Low limits priority

X

Computer mode

X


X

Computer mode

X

Low limits priority

X

Computer mode

X

X

X

X

X

X

187

Automation class


RX1

Reference to process signal 1

Double

RX2


Double

RX3


Double

RX4


Double

X1

Real input

Double

Real

I

X

X2

Real input

Double

Real

I

X

X3

Real input

Double

Real

I

X

X4

Real input

Double

Real

I

X

I1

Boolean input

Bool

Extended Boolean

I

X

I2

Boolean input

Bool

Extended Boolean

I

X

I3

Boolean input

Bool

Extended Boolean

I

X

I4

Boolean input

Bool

Extended Boolean

I

X

Legend for columns:

188

Atom

Atom name

Description


OPC data type


Melody data type

Melody data type

Melody I/O


Read


Write

Atom can be written from 800xA Process Portal (control – operator action or external control system).

Write access


3BDD011741R4101


Automation class

Control

The operator actions for the ANMON analog monitoring function are converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in Melody. The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in Melody. Table: 800xA Process Portal commands and resulting control code in Melody 800xA Process Melody Effect: Portal: commands control code: AKO/SIG

01800080H

Set general operator input inhibit

AKOR/SIG

01800100H

Reset general operator input inhibit

SUO/SIG

40004000H

Reset the alternative value

ATO/SIG

40034001H

Switch to alternative value

ATOR/SIG

40034002H

Switch from alternative value to input variable X

3BDD011741R4101

189

Automation class


Calculated atoms

Calculated atoms are atoms, which are derived from values from other atoms, according to a defined processing standard. The atoms are calculated centrally in Melody Connectivity Server. Atom:

Description:

.BAD/SIG

Quality of process signals OR (XSTA/SIG, Y/SIG, XRY/SIG, XSUY/SIG, WY/SIG, transmitted AHHY/SIG, AHY/SIG, ALY/SIG, ALLY/SIG, AHDY/SIG, ALDY/SIG, AHTY/SIG, ALTY/SIG, X1/SIG, X2/SIG, X3/SIG, X4/SIG, I1/SIG, I2/SIG, I3/SIG, I4/SIG)

.ALARM


OR (SUO/ALARM, ATO/ALARM, AKO/ALARM, HVO/ALARM, LVO/ALARM, TRO/ALARM, AHHN/ALARM, AHN/ALARM, ALN/ALARM, ALLN/ALARM, AHDN/ALARM, ALDN/ALARM, AHTN/ALARM, ALTN/ALARM, AHHY/ALARM, AHY/ALARM, ALY/ALARM, ALLY/ALARM, AHDY/ALARM, ALDY/ALARM, AHTY/ALARM, ALTY/ALARM, I1/ALARM, I2/ALARM, I3/ALARM, I4/ALARM)

.UNACK


OR (SUO/UNACK, ATO/UNACK, AKO/UNACK, HVO/UNACK, LVO/UNACK, TRO/UNACK, AHHN/UNACK, AHN/UNACK, ALN/UNACK, ALLN/UNACK, AHDN/UNACK, ALDN/UNACK, AHTN/UNACK, ALTN/UNACK, AHHY/UNACK, AHY/UNACK, ALY/UNACK, ALLY/UNACK, AHDY/UNACK, ALDY/UNACK, AHTY/UNACK, ALTY/UNACK, I1/UNACK, I2/UNACK, I3/UNACK, I4/UNACK)

.Y/ALARM


OR (TRO/ALARM, AHHY/ALARM, AHY/ALARM, ALY/ALARM, ALLY/ALARM, AHDY/ALARM, ALDY/ALARM, AHTY/ALARM, ALTY/ALARM)

.Y/UNACK

Limit value violation with alarm signal pending, error status not yet acknowledged

OR (TRO/UNACK, AHHY/UNACK, AHY/UNACK, ALY/UNACK, ALLY/UNACK, AHDY/UNACK, ALDY/UNACK, AHTY/UNACK, ALTY/UNACK)

190


3BDD011741R4101


Melody AnOut – Analog output

Melody AnOut – Analog output Features The analog output (MelodyAnOut) automation class allows the pre-configured analog output function from Melody to be displayed in a data structure in 800xA Process Portal. The pre-configured automation function in Melody has the functions of replacement and alternative value processing, linearization, delimitation, limit value checking. A configured faceplate is available for selection.

Configuration The MelodyAnOut automation class displays the analog monitoring function from the Melody automation system in a variable structure in 800xA Process Portal. This standard display is configured by connection of the process signals in Composer for Melody. As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the Melody connection components. The configuration data can be tailored to meet the requirements of the operator in the tag configuration screens in 800xA Process Portal. The configuration from Composer is described in the technical information “Commissioning a System", Technical Information 30/72-8055.

Composer function block and signal definitions

The figures below show the function blocks for the analog output function in Composer. The function blocks have an integrated monitoring block for the link to 800xA Process Portal. The connections to the Melody function block identify input and output signals in Melody. Data is exchanged between Melody and 800xA Process Portal, through the internal

3BDD011741R4101

191

Configuration


connections of the Melody function block with a monitoring block inside the yellow backed case. YS-00

YL-00

Connection behavior of the function block connections on the monitoring block:

alw

=


ext

=


opt

=


The automation function in 800xA Process Portal is configured using code generation for Operations in Composer. Event typical

The signalling behavior of a function is defined by providing an event typical or specifying the behavior of the signal in Composer. The event typical is connected to a process signal. The following configuration data is defined as part of an event typical,: • Priority of the signal (Prio) • Generate signal (SGen)

192

3BDD011741R4101


• • • • • • • •

Configuration

Signal as alarm (Al) Signal page acknowledge (PAck) Dual-value signal (Dual) Signal can be inhibited (Inhib) # Signal can be suppressed (Supp) # Signal generation for negative edge change (logic) Operator profile (PROF) Packed Boolean sub-variant $ #) Information is only evaluated in code generation for Operations. $) Only defined for event typicals for Packed Boolean signals.

For the configuration of signalling behavior in Composer, a distinction is made between the event typical for Boolean signals and the event typical for Packed Boolean signals. Event typicals for Boolean signals defined the signalling behavior of precisely one binary signal. Event typicals for Packed Boolean signals define the signalling behavior of the individual binary signals packed in the signal (max. 32). For the XSTA function block connection in the MelodyAnOut automation class, the event typicals VYM and VYM2 are defined as standard in Composer. These event typicals refer to a sub-variant, which describes the structure and status texts for the packed Boolean signal.

3BDD011741R4101

193

Configuration


Structure of a event typical using the example of VYM1. The signalling behavior can be adjusted on a project-specific basis. Table: Event typical VYM1

194

Name

Brief desc.

Explanatory text

VYM1

VYM1

Analog output XSTA with events

PROF

Packed Boolean sub-variant

0

ANOUT_1

MIdx

Csel

Prio

110

SUO

10

111

ATO

10

112

AKO

9

113

HVO

8

114

LVO

8

189

AHHN

10

190

AHN

10

191

ALN

10

192

ALLN

10

SGen

Al

PAck

Dual

Inhib

Supp

Logic

3BDD011741R4101


Configuration

Status texts

The status texts for the Boolean signals are configured in Composer. The status texts for individual items of binary information within a packed Boolean signal are not configured in Composer. These status texts are shown in the subvariant (e. g. ANOUT_1) referred to by the event typical. The sub-variant is stored in the Importer for 800xA Process Portal. Structure of a sub-variant using the example of ANOUT_1. The status texts and the alias can be adjusted on a project-specific basis. Table: Alias name and status texts for sub-variant ANOUT_1 Status text 1

Status text 0

SUO

SV Act

(SV Act)

ATO

ATO

AV Act

(AV Act)

BFO

BFO

AKO

AKO

AccLock

(AccLock)

HVO

HVO

MsgMax

(MsgMax)

LVO

LVO

MsgMin

(MsgMin)

RDO

RDO

AHHN

AHHN

AHH Sup

(AHH Sup)

AHN

AHN

AH Sup

(AH Sup)

ALN

ALN

AL Sup

(AL Sup)

ALLN

ALLN

ALL Sup

(ALL Sup)

AHHO

AHHO

AHO

AHO

ALO

ALO

ALLO

ALLO

ATOM

Alias

SUS

SUS

SUO

3BDD011741R4101

195

Automation class



The following table describes the structure of the automation class for the MelodyAnOut analog output function. Table: Structure of the MelodyAnOut automation class

196

Atom

Description

OPC data type

Melody data type

Melody Read I/O

Write

Write access

XSTA

Actual value status

Integer (w)

Packed Boolean

I

SUS


Bool

SUO


Bool (w)

X


ATO

Set alternative value

Bool (w)

X


ATOR


Bool (w)

X


BFO


Bool

AKO

Access locked

Bool (w)

X


AKOR


Bool (w)

X


HVO

H limit reached

Bool

LVO

L limit reached

Bool

RDO


Bool

AHHN

No HH limit

Bool

AHN

No H limit

Bool

ALN

No L limit

Bool

X

3BDD011741R4101


ALLN

Automation class

No LL limit

Bool

AHHO

HH limit active

Bool

AHO

H limit active

Bool

ALO

L limit active

Bool

ALLO

LL limit active

Bool

MDO


Integer (w)

Packed Boolean

O

Y

Real output

Double

Real

I

X

X

Y/ALARM

Bool

Y/UNACK

Bool

XRY


Double (w)

Real

I

ATV

Alternative value

Double (w)

Real

O

XSUY

Alternative value

Double

Real

I

X

AHHY

HH limit signal

Bool

Packed Boolean

I

X

AHHX

HH limit value (actual)

Double (w)

AHHV

HH limit value

Double (w)

Real

O

AHY

HH limit signal

Bool

Packed Boolean

I

AHX


Double (w)

AHV

H limit value

Double (w)

Real

O

ALLY

LL limit signal

Bool

Packed Boolean

I

ALLX


Double (w)

ALLV

LL limit value

Double (w)

Real

O

ALY

L limit signal

Bool

Packed Boolean

I

ALX


Double (w)

3BDD011741R4101

X

Computer mode

X

Setpoint control

X

Computer mode

X


X

Computer mode

X

High limits

X

Computer mode

X

Low limits priority

X

Computer mode

X

Low limits

X

X

X

197

Automation class


ALV

L limit value

Double (w)

Real

O

RX1


ATOMREF

RX2


ATOMREF

RX3


ATOMREF

RX4


ATOMREF

I1

Boolean input

I2

X

Bool

Extended Boolean

I

X

Boolean input

Bool

Extended Boolean

I

X

I3

Boolean input

Bool

Extended Boolean

I

X

I4

Boolean input

Bool

Extended Boolean

I

X

Computer mode


Atom name

Description


OPC data type


Melody data type

Melody data type

Melody I/O


Read


Write


Write access


Control

The operator actions for the ANOUT analog output function are converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in Melody. The meaning of the individual items of information in the

198

3BDD011741R4101


Automation class

operator action can be found in the associated function block descriptions in Melody. Table: 800xA Process Portal commands and resulting control code in Melody

3BDD011741R4101

Operate IT Process Portal commands

Melody control code

Effect:

AKO/SIG

01800080H


AKOR/SIG

01800100H


SUO/SIG

40004000H


ATO/SIG

40034001H


ATOR/SIG

40034002H


199

Melody APID controller


Melody APID controller Features The controller (MelodyAPID) automation class allows the pre-configured PID controller function from Melody to be displayed in a data structure in 800xA Process Portal. The pre-configured automation function in Melody has an operating mode memory, as well as X/W/Y handling and a timer function. A configured faceplate is available for selection.

Configuration The MelodyAnAPID automation class displays the controller function from the Melody automation system in a variable structure in 800xA Process Portal. This standard display is configured by connection of the process signals in Composer for Melody. As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the Melody connection components. The configuration data can be tailored to meet the requirements of the operator in the tag configuration screens in 800xA Process Portal. The configuration from Composer is described in the technical information “commissioning a System", Technical Information 30/72-8055. Composer function block and signal definitions

The figures below show the function blocks for the controller function in Composer. The function blocks have an integrated monitoring block for the link to 800xA Process Portal. The connections to the Melody function block identify input and output signals in Melody. Data is exchanged between Melody and 800xA Process Portal, through the internal

200

3BDD011741R4101


Configuration

connections of the Melody function block with a monitoring block inside the yellow backed case. APIDS-00

3BDD011741R4101

APIDM-00

201

Configuration


APIDL-00

202

3BDD011741R4101


Configuration


=


ext

=


opt

=


The automation function in 800xA Process Portal is configured using code generation for Operations in Composer.

Event typical

The signalling behavior of a function is defined by providing an event typical or specifying the behavior of the signal in Composer. The event typical is connected to a process signal. The following configuration data is defined as part of an event typical: • Priority of the signal (Prio) • Generate signal (SGen) • Signal as alarm (Al) • Signal page acknowledge (PAck) • Dual-value signal (Dual) • Signal can be inhibited (Inhib) # • Signal can be suppressed (Supp) # • Signal generation for negative edge change (logic) • Operator profile (PROF) • Packed Boolean sub-variant $ #) Information is only evaluated in code generation for Operations. $) Only defined for event typicals for Packed Boolean signals.

3BDD011741R4101

203

Configuration


For the configuration of signalling behavior in Composer, a distinction is made between the event typical for Boolean signals and the event typical for Packed Boolean signals. Event typicals for Boolean signals define the signalling behavior of precisely one binary signal. Event typicals for Packed Boolean signals define the signalling behavior of the individual binary signals packed in the signal (max. 32). The controller APID provides its current status in the form of 4 packed Boolean telegrams. As a result, different event typicals can be used for each individual status telegram. The following are defined as standard for the function block connection for the MelodyAPID automation class in Composer: • XSTA event typical VCX1 and VCX2 • YSTA event typical VCY1 and VCY2 • WSTA event typical VCW1 and VCW2 • TSTA event typical VCT1 and VCT2 These event typicals refer to a sub-variant, which describes the structure and status texts for the packed Boolean signal. Structure of event typical using the examples of VCX1, VCY1, VCW1 and VCT1. The signalling behavior can be adjusted on a project-specific basis.

204

3BDD011741R4101


Configuration

Table: Event typical VCX1 Name

Brief desc.

Explanatory text

VCX1

VCX1

APID controller XSTA with events

PROF


0

APID_1

MIdx

Csel

Prio

110

SUO

10

111

ATO

10

112

AKO

5

113

HVO

10

114

LVO

10

115

TRO

4

189

AHHN

10

190

AHN

10

191

ALN

10

192

ALLN

10

193

AHDN

10

194

ALDN

10

195

AHTN

10

196

ALTN

10

SGen

Al

PAck

Dual

Inhib

Supp

Logic

Inhib

Supp

Logic

Table: Event typical VCY1 Name

Brief desc.

Explanatory text

VCY1

VCY1

APID controller YSTA with events

PROF


0

APID_3

MIdx

Csel

Prio

140

AKO

9

141

LKO

9

142

MAN

9

143

AUT

9

3BDD011741R4101

SGen

Al

PAck

Dual

205

Configuration

206


144

COMP

9

145

DDC

9

146

LOCO

9

147

MIO

9

148

AIO

9

149

CIO

9

150

YFSO

2

151

YHO

10

152

YHE

10

153

YLO

12

154

YLE

12

155

YRE

12

156

YNO

11

157

YNVO

11

158

YNHO

11

159

YN+O

11

160

YN-O

11

161

YBNO

11

162

YHNO

11

163

YLNO

11

164

YRNO

11

3BDD011741R4101


Configuration

Table: Event typical VCW1 Name

Brief desc.

VCW1

VCW1

Explanatory text

APID controller WSTA with events

PROF


0

APID_2

MIdx

Csel

Prio

116

INT

9

117

EXT

9

118

IIO

9

119

EIO

9

120

WTO

10

121

SPC

9

122

CAS

9

123

AUTI

9

124

WKHO

10

125

WKLO

10

126

WHO

10

127

WHE

10

128

WLO

12

129

WLE

12

130

WRE

12

131

WNO

11

132

WNVO

11

133

WNHO

11

134

WN+O

11

135

WN-O

11

136

WBNO

11

137

WHNO

11

138

WLNO

11

139

WRNO

11

3BDD011741R4101

SGen

Al

PAck

Dual

Inhib

Supp

Logic

207

Configuration


Table: Event typical VCT1 Name

Brief desc.

Explanatory text

VCT1

VCT1

PROF


0

APID_4

MIdx

Csel

Prio

165

TFNO

11

166

KCNO

11

167

PNO

11

168

IN+O

11

169

IN-O

11

170

DN+O

11

171

DN-O

11

172

ARNO

11

173

DPNO

11

174

DINO

11

175

DDNO

11

APID controller TSTA with events

SGen

Al

PAck

Dual

Inhib

Supp

Logic

Status texts

The status texts for the Boolean signals are configured in Composer. The status texts for individual items of binary information within a packed Boolean signal are not configured in Composer. These status texts are shown in the subvariant (e. g. APID_1) referred to by the event typical. The sub-variant is stored in the Importer for 800xA Process Portal). Structure of a sub-variant using the examples of APID_1, APID_2, APID_3 and APID_4. The status texts and the alias can be adjusted on a project-specific basis.

208

3BDD011741R4101


Configuration

Table: Alias name and status texts for sub-variant APID_1 ATOM

Alias

Status text 1

Status text 0

SUS

SUS

SUO

SUO

Sv Act

(Sv Act)

ATO

ATO

AV Act

(AV Act)

BFO

BFO

AKO

AKO

AccLock

(AccLock)

HVO

HVO

MsgMax

(MsgMax)

LVO

LVO

MsgMin

(MsgMin)

TRO

TRO

MsgTrans

(MsgTrans)

RDO

RDO

AHHN

AHHN

AHH Sup

(AHH Sup)

AHN

AHN

AH Sup

(AH Sup)

ALN

ALN

AL Sup

(AL Sup)

ALLN

ALLN

ALL Sup

(ALL Sup)

AHDN

AHDN

AHD Sup

(AHD Sup)

ALDN

ALDN

ALD Sup

(ALD Sup)

AHTN

AHTN

AHT Sup

(AHT Sup)

ALTN

ALTN

ALT Sup

(ALT Sup)

AHHO

AHHO

AHO

AHO

ALO

ALO

ALLO

ALLO

AHDO

AHDO

ALDO

ALDO

AHTO

AHTO

ALTO

ALTO

3BDD011741R4101

209

Configuration


Table: Alias name and status texts for sub-variant APID_2

210

ATOM

Alias

Status text 1

Status text 0

INT

INT

OM INT S

(OM INT S)

EXT

EXT

OM EXT M

(OM EXT M)

IIO

IIO

LockI S

(LockI S)

EIO

EIO

LockE M

(LockE M)

WEFO

WEFO

ONEWWI

ONEWWI

WTXO

WTXO

WBO

WBO

WTO

WTO

WN Act

(WN Act)

INTW

INTW

EXTW

EXTW

SPC

SPC

SPC Act

(SPC Act)

CAS

CAS

CAS Act

(CAS Act)

AUTI

AUTI

AUT Intv

(AUT Intv)

WKHO

WKHO

W V HMsg

(W V HMsg)

WKLO

WKLO

W V LMsg

(W V LMsg)

WHO

WHO

W MaxMsg

(W MaxMsg)

WHE

WHE

WLimHRdy

(WLimHRdy)

WLO

WLO

W MinMsg

(W MinMsg)

WLE

WLE

WLimLRdy

(WLimLRdy)

WRO

WRO

WRE

WRE

W GL Rdy

(W GL Rdy)

WSVO

WSVO

WNO

WNO

W IntvAct

(W IntvAct)

WNVO

WNVO

W SWextM

(W SWextM)

WNHO

WNHO

W HLVAct

(W HLVAct)

WN+O

WN+O

LockW+Act

(LockW+Act)

WN-O

WN-O

LockW-Act

(LockW-Act)

WBNO

WBNO

WLimStpA

(WLimStpA)

WHNO

WHNO

WLimHStA

(WLimHStA)

WLNO

WLNO

WLimLStA

(WLimLStA)

WRNO

WRNO

W GL StA

(W GL StA)

3BDD011741R4101


Configuration

Table: Alias name and status texts for sub-variant APID_3 ATOM

Alias

Status text 1

Status text 0

YAKO

YAKO

AccLock

(AccLock)

LKO

LKO

LckOMSw M

(LckOMSw M)

MAN

MAN

Manual

(Manual)

AUT

AUT

Automatic

(Automatic)

COMP

COMP

OM COM W

(OM COM W)

DDC

DDC

OM DDC

(OM DDC)

SPCC

SPCC

LOCO

LOCO

Loc Msg

(Loc Msg)

MIO

MIO

LockM M

(LockM M)

AIO

AIO

LockA M

(LockA M)

CIO

CIO

LockC M

(LockC M)

OVO

OVO

YFSO

YFSO

PSO Act

(PSO Act)

TFA

TFA

YBO

YBO

EBO

EBO

YHO

YHO

Y MaxMsg

(Y MaxMsg)

YHE

YHE

YLimHRdy

(YLimHRdy)

YLO

YLO

Y MinMsg

(Y MinMsg)

YLE

YLE

YLimLRdy

(YLimLRdy)

YRO

YRO

YRE

YRE

Y GL Rdy

(Y GL Rdy)

YSVO

YSVO

YNO

YNO

Y IntAct

(Y IntAct)

YNVO

YNVO

Y SWextM

(Y SWextM)

YNHO

YNHO

Y HaltMsg

(Y HaltMsg)

YN+O

YN+O

DLck +Act

(DLck +Act)

YN-O

YN-O

DLck -Act

(DLck -Act)

YBNO

YBNO

YLimStpA

(YLimStpA)

YHNO

YHNO

YLimHStA

(YLimHStA)

YLNO

YLNO

YLimLStA

(YLimLStA)

YRNO

YRNO

Y GL StA

(Y GL StA)

3BDD011741R4101

211

Configuration


Table: Alias name and status texts for sub-variant APID_4

212

ATOM

Alias

ARHA

ARHA

Status text 1

Status text 0

ARLA

ARLA

ARVA

ARVA

ARHN

ARHN

ARLN

ARLN

ARVN

ARVN

ARH

ARH

ARL

ARL

THVO

THVO

TLVO

TLVO

YOTO

YOTO

DVPO

DVPO

DVIO

DVIO

DVDO

DVDO

TBO

TBO

TFNO KCNO

TFNO

Intv TF

(Intv TF)

KCNO

SOK KP M

(SOK KP M)

PNO

PNO

P SO Act

(P SO Act)

IN+O

IN+O

ISwOff+M

(ISwOff+M)

IN-O

IN-O

ISwOff-M

(ISwOff-M)

DN+O

DN+O

DSwOff+M

(DSwOff+M)

DN-O

DN-O

DSwOff-M

(DSwOff-M)

ARNO

ARNO

I-Endp A

(I-Endp A)

DPNO

DPNO

LckTz PM

(LckTz PM)

DINO

DINO

LckTz IM

(LckTz IM)

DDNO

DDNO

LckTz DM

(LckTz DM)

3BDD011741R4101


Automation class


The following table describes the structure of the automation class for the MelodyAPID controller function. Table: Structure of the MelodyAPID automation class Atom

Description

OPC data type

Melody data type

Melody Read I/O

Write

Write access

XSTA

Actual value status

Integer (w)

Packed Boolean

I

X

WSTA

Setpoint status

Integer (w)

Packed Boolean

I

X

YSTA

control variable status

Integer (w)

Packed Boolean

I

X

TSTA

Timer function status

Integer (w)

Packed Boolean

I

X

SUS


Bool

SUO


Bool (w)

X


ATO

Alternative value set

Bool (w)

X


ATOR


BoolW

X


BFO


Bool

AKO

Access locked

Bool (w)

X


AKOR


BoolW

X


HVO

H limit reached

Bool

LVO

L limit reached

Bool

TRO

Transient violation

Bool

3BDD011741R4101

213

Automation class

RDO

214



Bool

AHHN

No HH limit

Bool

AHN

No H limit

Bool

ALN

No L limit

Bool

ALLN

No LL limit

Bool

AHDN

No H tolerance

Bool

ALDN

No L tolerance

Bool

AHTN

No H transient

Bool

ALTN

No L transient

Bool

AHHO

HH limit active

Bool

AHO

H limit active

Bool

ALO

L limit active

Bool

ALLO

LL limit active

Bool

AHDO

H tolerance active

Bool

ALDO

L tolerance active

Bool

AHTO

H transient active

Bool

ALTO

L transient active

Bool

INT

INT operating mode

Bool (w)

X

Operator mode

EXT

EXT operating mode

Bool (w)

X

Operator mode

IIO

INT locked

Bool

EIO

EXT locked

Bool

WEFO

Wext switching Bool impulse filter active

ONEWWI

New value from operator

Bool

WTXO

Adjustment to X active

Bool

WBO

Adjustment require- Bool ment from W

WTO

Adjustment active

Bool

INTW

INT active

Bool

EXTW

EXT active

Bool

SPC

SPC operating mode

Bool

3BDD011741R4101


Automation class

CAS

Yaut and Wext (cascade) operating mode

Bool (w)

X

Operator mode

AUTI

Yaut and Wext operating mode

Bool (w)

X

Operator mode

WKHO

H limit ratio

Bool

WKLO

L limit ratio

Bool

WHO

H limit active

Bool

WHE

Release H limit

Bool

WLO

L limit active

Bool

WLE

Release L limit

Bool

WRO

Gradient limit active Bool

WRE

Gradient limit released

Bool

WSVO


Bool

WNO

Control action

Bool

WNVO

Setpoint control active

Bool

WNHO

Keep last value active

Bool

WN+O

Stop direction +

Bool

WN-O

Stop direction –

Bool

WBNO

No limit for W

Bool

WHNO

No H limit

Bool

WLNO

No L limit

Bool

WRNO

No gradient limit

Bool

CMD1

Activate command

BoolW

X

Operator action priority

CMD0

De-activate command

BoolW

X

Operator action priority

YAKO

Auxiliary variable gain

Bool

LKO

Switching locked mode

Bool

MAN

Manual

Bool (w)

X

Operator mode

3BDD011741R4101

215

Automation class

216


AUT

Automatic

Bool (w)

X

Operator mode

COMP

Computer waiting

Bool (w)

X

Operator mode

DDC

DDC operating mode

Bool

SPCC

SPC operating mode

Bool

LOCO

Local action

Bool

LKOS

Operating mode S/O lock

BoolW

X

Lock operator mode

LKOR

Operating mode S/O release

BoolW

X

Lock operator mode

X

Computer mode

MIO

MAN locked

Bool

AIO

AUT locked

Bool

CIO

DDC locked

Bool

OVO

Override active

Bool

YFSO

Compulsory disconnection

Bool (w)

TFA

Timer function active

Bool

YBO

Adjustment requirement for Y

Bool

EBO

Syn. requirement, external

Bool

YHO

H limit active

Bool

YHE

Release H limit

Bool

YLO

L limit active

Bool

YLE

Release L limit

Bool

YRO

Gradient limit active Bool

YRE

Release gradient limit

Bool

YSVO


Bool

YNO

Control action

Bool

YNVO

External alternative Bool Y value active

YNHO

Keep last Y value

Bool

3BDD011741R4101


YN+O

Stop direction +

Automation class

Bool

YN-O

Stop direction –

Bool

YBNO

No limit for Y

Bool

YHNO

No H limit

Bool

YLNO

No L limit

Bool

YRNO

No gradient limit

Bool

ARHA

Timer function dyn. Bool H limit active

ARLA

Timer function dyn. Bool L limit active

ARVA

Timer function dyn. Bool limit active

ARHN

Timer function dyn. Bool H limit new

ARLN

Timer function dyn. Bool L limit new

ARVN

Timer function dyn. Bool limit new

ARH

Timer function dyn. Bool H limit

ARL

Timer function dyn. Bool L limit

THVO

Bool

TLVO

Bool

YOTO

Operating point adjustment

Bool

DVPO

No deviation of P component

Bool

DVIO

No deviation of I component

Bool

DVDO

No deviation of D component

Bool

TBO

Hard synchronisation

Bool

TFNO

Timer function active

Bool

KCNO

No Kp compensation

Bool

PNO

P component disconnected

Bool

3BDD011741R4101

217

Automation class


IN+O

I component + disconnected

Bool

IN-O

I component – disconnected

Bool

DN+O

D component + disconnected

Bool

DN-O

D component – disconnected

Bool

ARNO

I behavior at end position

Bool

DPNO

P component neutral zone off

Bool

DINO

I component neutral zone off

Bool

DDNO

D component neutral zone off

Bool

MDO


Integer (w)

Packed Boolean

O

XRY


Double (w)

Real

I

X

XAY

Current process value

Double

Real

I

X

Real

O

XAY/ALARM

Computer mode

X

Setpoint control

X

Computer mode

X


X

Computer mode

X

High limits

X

Computer mode

Bool

XAY/UNACK

218

X

Bool

ATV

Alternative value

Double (w)

XSUY

Alternative value

Double

Real

I

X

AHHY

HH limit signal

Bool

Extended Boolean

I

X

AHHX

HH limit value (actual)

Double (w)

AHHV

HH limit value

Double (w)

Real

O

AHY

HH limit signal

Bool

Extended Boolean

I

AHX


Double (w)

AHV

H limit value

Double (w)

Real

O

ALLY

LL limit signal

Bool

Extended Boolean

I

X

X

3BDD011741R4101


Automation class

ALLX


Double (w)

ALLV

LL limit value

Double (w)

Real

O

ALY

L limit signal

Bool

Extended Boolean

I

ALX


Double (w)

ALV

L limit value

Double (w)

Real

O

AHDY

H tolerance signal

Bool

Extended Boolean

I

AHDX

HD limit value (actual)

Double (w)

AHDV

H tolerance value

Double (w)

Real

O

ALDY

L tolerance signal

Bool

Extended Boolean

I

ALDX

LD limit value (actual)

Double (w)

ALDV

L tolerance value

Double (w)

Real

O

AHTY

H transient signal

Bool

Extended Boolean

I

AHTX

HT limit value (actual)

Double (w)

AHTV

H transient value

Double (w)

Real

O

ALTY

L transient signal

Bool

Extended Boolean

I

ALTX

LT limit value (actual)

Double (w)

ALTV

L transient value

Double (w)

Real

Low limits priority

X

Computer mode

X

Low limits

X

Computer mode

X


X

Computer mode

X

Low limits priority

X

Computer mode

X


X

Computer mode

X

Low limits priority

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

X

X

X

X

O

WAY

Current setpoint

Double

Real

I

X

WHY

Current H limit

Double (w)

Real

I

X

WHV

H limit value

Double (w)

Real

O

WLY

Current L limit

Double (w)

Real

I

3BDD011741R4101

X

X

219

Automation class


WLV

L limit value

Double (w)

Real

O

WOY

Current operator setpoint

Double (w)

Real

I

WOV

Operator setpoint

Double (w)

Real

O

WIY

Internal setpoint Wint

Double

Real

I

X

WNY

Current setpoint control

Double

Real

I

X

WCAY

Current offset for Wext

Double

Real

I

X

WCY

Setpoint offset Wext

Double (w)

Real

I

X

WCV

Setpoint offset Wext

Double (w)

Real

O

WEY

Evaluated setpoint Wext

Double

Real

I

X

WKAY

Current Wext ratio

Double

Real

I

X

WKY

Ratio factor for Wext

Double (w)

Real

I

X

WKV

Ratio factor for Wext

Double (w)

Real

O

WKFY

Evaluated ratio for Wext.

Double

Real

I

X

YAY

Current controller output

Double (w)

Real

I

X

Real

O

YAY/ALARM

220

Computer mode

X

Setpoint control

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Setpoint control

X

Computer mode

Bool

YAY/UNACK YOV

X

X

Bool Operator control variable

Double (w)

YHY

Current H limit

Double (w)

Real

I

X

Tuning

YHV

H limit value

Double (w)

Real

O

X

Computer mode

YLY

Current L limit

Double (w)

Real

I

X

Tuning

YLV

L limit value

Double (w)

Real

O

X

Computer mode

YIY

Internal position value Yint

Double

Real

I

TYOY

Operating point

Double (w)

Real

I

X

Setpoint control

3BDD011741R4101


TYOV

Operating point

Automation class

Double (w)

Real

O

DEVY

Control deviation

Double

Real

I

X

ARBY

End position of ARW range

Double (w)

Real

I

X

ARB

End position of ARW range

Double (w)

Real

O

KPY

Proportional gain

Double (w)

Real

I

KP

Proportional gain

Double (w)

Real

O

VDY

Derivative action gain

Double (w)

Real

I

VD

Derivative action gain

Double (w)

Real

O

VD+Y

Derivative action gain +

Double (w)

Real

I

VD+

Derivative action gain + (setpoint)

Double (w)

Real

O

VD-Y

Derivative action gain –

Double (w)

Real

I

VD-

Derivative action gain – (setpoint)

Double (w)

Real

O

WR+Y

Gradient limit value Duration (w) +

Short duration

I

WRT+

Gradient limit value Duration (w) + (setpoint)

Short duration

O

WR-Y

Gradient limit value –

Duration (w)

Short duration

I

WRT-

Gradient limit value – (setpoint)

Duration (w)

Short duration

O

YR+Y

Gradient limit value Duration (w) +

Short duration

I

YRT+

Gradient limit value Duration (w) + (setpoint)

Short duration

O

YR-Y

Gradient limit value –

Duration (w)

Short duration

I

YRT-

Gradient limit value – (setpoint)

Duration (w)

Short duration

O

TIY

Integration time

Duration (w)

Short duration

I

TI

Integration time

Duration (w)

Short duration

O

3BDD011741R4101

X

X

X

X

X

X

X

X

X

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

221

Automation class

222


TI+Y

Integration time +

Duration (w)

Short duration

I

TI+

Integration time + (setpoint)

Duration (w)

Short duration

O

TI-Y

Integration time –

Duration (w)

Short duration

I

TI-

Integration time – (setpoint)

Duration (w)

Short duration

O

TDY

Recovery time

Duration (w)

Short duration

I

TD

Recovery time

Duration (w)

Short duration

O

TD+Y

Recovery time +

Duration (w)

Short duration

I

TD+

Recovery time + (setpoint)

Duration (w)

Short duration

O

TD-Y

Recovery time –

Duration (w)

Short duration

I

TD-

Recovery time – (setpoint)

Duration (w)

Short duration

COMV

Computer value

Integer (w)

DBY

Neutral zone value

DBV

Neutral zone value

YNY

X

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

X

Computer mode

X

Tuning

O

X

Computer mode

Packed Boolean

O

X

Computer mode

Double (w)

Real

I

X

Tuning

Double (w)

Real

O

X

Computer mode

External alternative Double Y value

Real

I

X

RX1

Reference to 1st process signal

ATOMREF

ATOMREF

RX2

Reference to 2nd process signal

ATOMREF

ATOMREF

RX3

Reference to 3rd process signal

ATOMREF

ATOMREF

RX4

Reference to 4th process signal

ATOMREF

ATOMREF

X1

Real input

Double

Real

I

X

X2

Real input

Double

Real

I

X

X3

Real input

Double

Real

I

X

X4

Real input

Double

Real

I

X

I1

Boolean input

Bool

Extended Boolean

I

X

X

X

X

X

X

3BDD011741R4101


Automation class

I2

Boolean input

Bool

Extended Boolean

I

X

I3

Boolean input

Bool

Extended Boolean

I

X

I4

Boolean input

Bool

Extended Boolean

I

X

CR1

Telegram 1 criteria

Integer

Packed Boolean

I

X

CR2

Telegram 2 criteria

Integer

Packed Boolean

I

X

CR3

Telegram 3 criteria

Integerl

Packed Boolean

I

X


Atom name

Description


OPC data type


Melody data type

Melody data type

Melody I/O


Read


Write


Write access


Control

The operator actions for the APID controller function are converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in Melody. The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in Melody.

3BDD011741R4101

223

Automation class


Table: 800xA Process Portal commands and resulting control code in Melody

224

Operate IT Process Portal: commands

Melody control code

Effect:

AKO/SIG

01800080H


AKOR/SIG

01800100H


SUO/SIG

40004000H


ATO/SIG

40034001H


ATOR/SIG

40034002H


INT/SIG

00600020H

“Internal” setpoint

EXT/SIG

00600040H

“External” setpoint

CAS/SIG

007c0048H

Cascade operating mode

COMP/SIG

001c0010H

Computer operating mode

MAN/SIG

081c0804H

Manual operating mode

AUT/SIG

007c0028H

Automatic internal operating mode

LKOS/SIG

06000200H

Set operating mode lock

LKOR/SIG

06000400H

Reset operating mode lock

YFSO/SIG

08000800H

Reset forced manual state

CMD0/SIG

30001000H

control variable 0 %

CMD1/SIG

30002000H

control variable 100 %

3BDD011741R4101


Automation class

Calculated atoms


Description:


.BAD/SIG

Quality of process signals transmitted

OR (XSTA/SIG, YSTA/SIG, WSTA/SIG, TSTA/SIG, XRY/SIG, XAY/SIG, XSUY/SIG, AHHY/SIG, AHY/SIG, ALY/SIG, ALLY/SIG, AHDY/SIG, ALDY/SIG, AHTY/SIG, ALTY/SIG, WAY/SIG, WHY/SIG, WLY/SIG, WOY/SIG, WIY/SIG, WNY/SIG, WCAY/SIG, WCY/SIG, WEY/SIG, WKAY/SIG, WKY/SIG, WKFY/SIG, YAY/SIG, YHY/SIG, YLY/SIG, YIY/SIG, TYOY/SIG, DEVY/SIG, ARBY/SIG, KPY/SIG, VDY/SIG, VD+Y/SIG, VD-Y/SIG, WR+Y/SIG, WR-Y/SIG, YR+Y/SIG, YR-Y/SIG, TIY/SIG, TI+Y/SIG, TI-Y/SIG, TDY/SIG, TD+Y/SIG, TD-Y/SIG, DBY/SIG, YNY/SIG, X1/SIG, X2/SIG, X3/SIG, X4/SIG, I1/SIG, I2/SIG, I3/SIG, I4/SIG)

.ALARM


OR (SUO/ALARM, ATO/ALARM, AKO/ALARM, HVO/ALARM, LVO/ALARM, TRO/ALARM, AHHN/ALARM, AHN/ALARM, ALN/ALARM, ALLN/ALARM, AHDN/ALARM, ALDN/ALARM, AHTN/ALARM, ALTN/ALARM, INT/ALARM, EXT/ALARM, IIO/ALARM, EIO/ALARM, WTO/ALARM, SPC/ALARM, CAS/ALARM, AUTI/ALARM, WKHO/ALARM, WKLO/ALARM, WHO/ALARM, WHE/ALARM, WLO/ALARM, WLE/ALARM, WRE/ALARM, WNO/ALARM, WNVO/ALARM, WNHO/ALARM, WN+O/ALARM, WN-O/ALARM, WBNO/ALARM, WHNO/ALARM, WLNO/ALARM, WRNO/ALARM, YAKO/ALARM, LKO/ALARM, AUT/ALARM, MAN/ALARM, COMP/ALARM, DDC/ALARM, LOCO/ALARM, MIO/ALARM, AIO/ALARM, CIO/ALARM, YFSO/ALARM, YHO/ALARM, YHE/ALARM, YLO/ALARM, YLE/ALARM, YRE/ALARM, YNO/ALARM, YNVO/ALARM, YNHO/ALARM, YN+O/ALARM, YN-O/ALARM, YBNO/ALARM, YHNO/ALARM, YLNO/ALARM, YRNO/ALARM, TFNO/ALARM, KCNO/ALARM, PNO/ALARM, IN+O/ALARM, IN-O/ALARM, DN+O/ALARM, DN-O/ALARM, ARNO/ALARM, DPNO/ALARM, DINO/ALARM, DDNO/ALARM, AHHY/ALARM, AHY/ALARM, ALY/ALARM, ALLY/ALARM, AHDY/ALARM, ALDY/ALARM, AHTY/ALARM, ALTY/ALARM, I1/ALARM, I2/ALARM, I3/ALARM, I4/ALARM)

3BDD011741R4101

225

Automation class


.UNACK


OR (SUO/UNACK, ATO/UNACK, AKO/UNACK, HVO/UNACK, LVO/UNACK, TRO/UNACK, AHHN/UNACK, AHN/UNACK, ALN/UNACK, ALLN/UNACK, AHDN/UNACK, ALDN/UNACK, AHTN/UNACK, ALTN/UNACK, INT/UNACK, EXT/UNACK, IIO/UNACK, EIO/UNACK, WTO/UNACK, SPC/UNACK, CAS/UNACK, AUTI/UNACK, WKHO/UNACK, WKLO/UNACK, WHO/UNACK, WHE/UNACK, WLO/UNACK, WLE/UNACK, WRE/UNACK, WNO/UNACK, WNVO/UNACK, WNHO/UNACK, WN+O/UNACK, WN-O/UNACK, WBNO/UNACK, WHNO/UNACK, WLNO/UNACK, WRNO/UNACK, YAKO/UNACK, LKO/UNACK, AUT/UNACK, MAN/UNACK, COMP/UNACK, DDC/UNACK, LOCO/UNACK, MIO/UNACK, AIO/UNACK, CIO/UNACK, YFSO/UNACK, YHO/UNACK, YHE/UNACK, YLO/UNACK, YLE/UNACK, YRE/UNACK, YNO/UNACK, YNVO/UNACK, YNHO/UNACK, YN+O/UNACK, YN-O/UNACK, YBNO/UNACK, YHNO/UNACK, YLNO/UNACK, YRNO/UNACK, TFNO/UNACK, KCNO/UNACK, PNO/UNACK, IN+O/UNACK, IN-O/UNACK, DN+O/UNACK, DN-O/UNACK, ARNO/UNACK, DPNO/UNACK, DINO/UNACK, DDNO/UNACK, AHHY/UNACK, AHY/UNACK, ALY/UNACK, ALLY/UNACK, AHDY/UNACK, ALDY/UNACK, AHTY/UNACK, ALTY/UNACK, I1/UNACK, I2/UNACK, I3/UNACK, I4/UNACK)

.XAY/ALARM


OR (TRO/ALARM, AHHY/ALARM, AHY/ALARM, ALY/ALARM, ALLY/ALARM, AHDY/ALARM, ALDY/ALARM, AHTY/ALARM, ALTY/ALARM)

.XAY/UNACK

Limit value violation with alarm signal pending, error status not yet acknowledged

OR (TRO/UNACK, AHHY/UNACK, AHY/UNACK, ALY/UNACK, ALLY/UNACK, AHDY/UNACK, ALDY/UNACK, AHTY/UNACK, ALTY/UNACK)

.YAY/ALARM

Compulsory disconnection with alarm signal pending

YFSO/ALARM

.YAY/UNACK

Compulsory disconnection with alarm signal pending, error status not yet acknowledged

YFSO/UNACK

226

3BDD011741R4101


MelodyBFlagx – Block flag

MelodyBFlagx – Block flag Features The block flag (MelodyBFlagx) automation class allows an operator controllable time and data memory from Melody to be displayed in a data structure in 800xA Process Portal. The time and data memory can display up to 30 variables of a particular data type. The Bflag automation classes are provided for all the data types available in Melody (Real, Integer, Duration, Boolean, Clock and Packed Boolean). A configured faceplate for each data type is available for selection.

Configuration The MelodyBFlagx automation classes display the operator controllable time and data memory from the Melody automation system in a variable structure in 800xA Process Portal. This standard display is configured by connection of the process signals in Composer for Melody. As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the Melody connection components. The configuration data can be tailored to meet the requirements of the operator in the tag configuration screens in 800xA Process Portal. The configuration from Composer is described in the technical information “commissioning a System", Technical Information 30/72-8055. Composer function block and signal definitions

The figures below show the function blocks for the operator controllable memory blocks in Composer. All function blocks have an integrated monitoring block for the link to 800xA Process Portal. The connections to the Melody function block identify input and output signals in Melody. Data is exchanged between Melody and 800xA Process Portal, through the internal

3BDD011741R4101

227

Configuration


connections of the Melody function block with a monitoring block inside the yellow backed case. Boolean BFlag

Clock BFlag

Duration BFlag

Integer BFlag

Long duration BFlag

Packed BFlag Boolean

Real BFlag

Connection behavior of the function block connections on the function block: alw

=

Tabelle 0-1. Always Signal is always/must always be connected.

ext

=


opt

=



228

3BDD011741R4101


Configuration

Event typical

The signalling behavior of a function is defined by providing an event typical or specifying the behavior of the signal in Composer. The event typical is connected to a process signal. The following configuration data is defined as part of an event typical: • Priority of the signal (Prio) • Generate signal (SGen) • Signal as alarm (Al) • Signal page acknowledge (PAck) • Dual-value signal (Dual) • Signal can be inhibited (Inhib) # • Signal can be suppressed (Supp) # • Signal generation for negative edge change (logic) • Operator profile (PROF) • Packed Boolean sub-variant $ #) Information is only evaluated in code generation for Operations. $) Only defined for event typicals for Packed Boolean signals.

For the configuration of signalling behavior in Composer, a distinction is made between the event typical for Boolean signals and the event typical for Packed Boolean signals. Event typicals for Boolean signals defined the signalling behavior of precisely one binary signal. Event typicals for Packed Boolean signals define the signalling behavior of the individual binary signals packed in the signal (max. 32). For the STA function block connection in the MelodyBFlagDFx automation class, the event typicals V1FL1 and V1FL2 are defined as standard in Composer. These event typicals refer to a sub-variant, which describes the structure and status texts for the packed Boolean signal. Structure of a event typical using the example of V1FL1. The signalling behavior can be adjusted on a project-specific basis.

3BDD011741R4101

229

Configuration


Table: Event typical V1FL1 Name

Brief desc.

Explanatory text

V1FL1

V1FL1

BFLAG STA with events

PROF Packed Boolean sub-variant 0

BFLAG_1

MIdx

Csel

Prio

140

AKO

9

SGen

Al

PAck

Dual

Inhib

Supp

Logic

Status texts

The status texts for the Boolean signals are configured in Composer. The status texts for individual items of binary information within a packed Boolean signal are not configured in Composer. These status texts are shown in the subvariant (e. g. BFLAG_1) referred to by the event typical. The sub-variant is stored in the Importer for 800xA Process Portal). Structure of a sub-variant using the example of BFLAG_1. The status texts and the alias can be adjusted on a project-specific basis.

230

3BDD011741R4101


Configuration

Table: Alias name and status texts for sub-variant BFLAG_1 ATOM

Alias

Status text 1

Status text 0

AKO

AKO

AccLock

(AccLock)

AKO1

AKO1

AKO2

AKO2

AKO3

AKO3

AKO4

AKO4

AKO5

AKO5

AKO6

AKO6

AKO7

AKO7

AKO8

AKO8

AKO9

AKO9

AKO10

AKO10

AKO11

AKO11

AKO12

AKO12

AKO13

AKO13

AKO14

AKO14

AKO15

AKO15

AKO16

AKO16

AKO17

AKO17

AKO18

AKO18

AKO19

AKO19

AKO20

AKO20

AKO21

AKO21

AKO22

AKO22

AKO23

AKO23

AKO24

AKO24

AKO25

AKO25

AKO26

AKO26

AKO27

AKO27

AKO28

AKO28

AKO29

AKO29

AKO30

AKO30

O1

O1

3BDD011741R4101

231

Automation class



The following table describes the structure of the automation class for the Boolean block flag BFLAGB. The structure of the other automation classes only varies in terms of the atom name and the data types. Class

Atom name

Description

Operate IT data type

Melody data type

MelodyBFlagB

I1..I30

Boolean input

PSigBool

Boolean

O1..O30

Boolean output

XC1..XC30

Clock input

PSigTime

Clock

YC1..YC30

Clock output

XD1..XD30

Duration input

PSigDuration

Duration

YD1..YD30

Duration output

XI1..XI30

Integer input

PSigInt

Integer

YI1..YI30

Integer output

XL1..XL30

Long duration input

PSigDuration

Long duration

YL1..YL30

Long duration output

IP1..IP30

Packed Boolean input

PSigPBool

Packed Boolean

OP1..OP30

Packed Boolean output

X1..X30

Real input

PSigReal

Real

Y1..Y30

Real output

MelodyBFlagC

MelodyBFlagD

MelodyBFlagI

MelodyBFlagL

MelodyBFlagP

MelodyBFlagR

232

3BDD011741R4101


Automation class

Table: Structure of the MelodyBFlagB automation class Atom

Description

OPC data type Melody Melody Read data type I/O

STA

Status

Integer (w)

AKO

Access locked

Bool (w)

X

X


AKOR


Bool (w)

X

X


O1S

Set memory 1

Bool (w)

X

X

Operator action

O1R

Reset memory 1

Bool (w)

X

X

Operator action

MDO


Integer (w)

Packed Boolean

O

X

Computer mode

O1

Boolean output

Bool (w)

Boolean

I

X

Operator ActionNormal

I1

Boolean input

Bool (w)

Boolean

O

X

Computer mode

O2

Boolean output

Bool (w)

Boolean

I

I2

Boolean input

Bool (w)

Boolean

O

O3

Boolean output

Bool (w)

Boolean

I

I3

Boolean input

Bool (w)

Boolean

O

O4

Boolean output

Bool (w)

Boolean

I

I4

Boolean input

Bool (w)

Boolean

O

O5

Boolean output

Bool (w)

Boolean

I

I5

Boolean input

Bool (w)

Boolean

O

O6

Boolean output

Bool (w)

Boolean

I

I6

Boolean input

Bool (w)

Boolean

O

O7

Boolean output

Bool (w)

Boolean

I

I7

Boolean input

Bool (w)

Boolean

O

O8

Boolean output

Bool (w)

Boolean

I

I8

Boolean input

Bool (w)

Boolean

O

O9

Boolean output

Bool (w)

Boolean

I

3BDD011741R4101

Packed Boolean

I

Write Write access

X

X

X

X

X

X

X

X

X

X

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

233

Automation class

I9

234


Boolean input

Bool (w)

Boolean

O

O10

Boolean output

Bool (w)

Boolean

I

I10

Boolean input

Bool (w)

Boolean

O

O11

Boolean output

Bool (w)

Boolean

I

I11

Boolean input

Bool (w)

Boolean

O

O12

Boolean output

Bool (w)

Boolean

I

I12

Boolean input

Bool (w)

Boolean

O

O13

Boolean output

Bool (w)

Boolean

I

I13

Boolean input

Bool (w)

Boolean

O

O14

Boolean output

Bool (w)

Boolean

I

I14

Boolean input

Bool (w)

Boolean

O

O15

Boolean output

Bool (w)

Boolean

I

I15

Boolean input

Bool (w)

Boolean

O

O16

Boolean output

Bool (w)

Boolean

I

I16

Boolean input

Bool (w)

Boolean

O

O17

Boolean output

Bool (w)

Boolean

I

I17

Boolean input

Bool (w)

Boolean

O

O18

Boolean output

Bool (w)

Boolean

I

I18

Boolean input

Bool (w)

Boolean

O

O19

Boolean output

Bool (w)

Boolean

I

I19

Boolean input

Bool (w)

Boolean

O

O20

Boolean output

Bool (w)

Boolean

I

I20

Boolean input

Bool (w)

Boolean

O

O21

Boolean output

Bool (w)

Boolean

I

I21

Boolean input

Bool (w)

Boolean

O

O22

Boolean output

Bool (w)

Boolean

I

X

X

X

X

X

X

X

X

X

X

X

X

X

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

3BDD011741R4101


Automation class

I22

Boolean input

Bool (w)

Boolean

O

O23

Boolean output

Bool (w)

Boolean

I

I23

Boolean input

Bool (w)

Boolean

O

O24

Boolean output

Bool (w)

Boolean

I

I24

Boolean input

Bool (w)

Boolean

O

O25

Boolean output

Bool (w)

Boolean

I

I25

Boolean input

Bool (w)

Boolean

O

O26

Boolean output

Bool (w)

Boolean

I

I26

Boolean input

Bool (w)

Boolean

O

O27

Boolean output

Bool (w)

Boolean

I

I27

Boolean input

Bool (w)

Boolean

O

O28

Boolean output

Bool (w)

Boolean

I

I28

Boolean input

Bool (w)

Boolean

O

O29

Boolean output

Bool (w)

Boolean

I

I29

Boolean input

Bool (w)

Boolean

O

O30

Boolean output

Bool (w)

Boolean

I

I30

Boolean input

Bool (w)

Boolean

O

X X

X

X

X

X

X

X

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode

X

Operator action

X

Computer mode


Atom name

Description


OPC data type


Melody data type

Melody data type

Melody I/O


Read


Write


Write access


3BDD011741R4101

235

Automation class


Control

The operator actions on the status of the BFlagx automation classes (“STA” connection) is converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in Melody. The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in Melody. Table: 800xA Process Portal commands and resulting control code in Melody Commands Operate IT Process Portal:

Melody control Effect: code

AKO/SIG

01800080H


AKOR/SIG

01800100H


O1S/SIG

30001000H

Set memory 1 commands

O1R/SIG

30001000H

Reset memory 1 commands

All operator actions for the time and data memories [1 … 30] are sent directly to the time and data memory’s conductive connection. The connections are differentiated with regard to the operator actions by an operator or external control system.

236

3BDD011741R4101


Automation class

Calculated atoms


Description:


.BAD/SIG


BFALGB: OR (STA/SIG, O1/SIG, O2/SIG, … On/SIG, …, O30/SIG) BFLAGC: OR (STA/SIG, YC1/SIG, YC2/SIG, … YCn/SIG, …, YC30/SIG) BFLAGD: OR (STA/SIG, YD1/SIG, YD2/SIG, … YDn/SIG, …, YD30/SIG) BFLAGI: OR (STA/SIG, YI1/SIG, YI2/SIG, … YIn/SIG, …, YI30/SIG) BFLAGL: OR (STA/SIG, YL1/SIG, YL2/SIG, … YLn/SIG, …, YL30/SIG) BFLAGP: OR (STA/SIG, OP1/SIG, OP2/SIG, … OPn/SIG, …, OP30/SIG) BFLAGR: OR (STA/SIG, Y1/SIG, Y2/SIG, … Yn/SIG, …, Y30/SIG)

.ALARM


BFLAGB: OR (O1/ALARM, O2/ALARM, …, On/ALARM, …, O30/ALARM)

.UNACK

BFLAGB: General function fault, alarm signal pending, error status not OR (OP1/UNACK, OP2/UNACK, …, OPn/UNACK, …, OP30/UNACK) yet acknowledged

3BDD011741R4101

237

MelodyBinary – Binary


MelodyBinary – Binary Features The binary (MelodyBinary) automation class allows binary process variables from Melody to be displayed in a data structure in 800xA Process Portal.

Configuration The MelodyBinary automation class displays binary process variables from the Melody automation system in a variable structure in 800xA Process Portal. This standard display is configured by connection of the process signals in Composer for Melody. As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the Melody connection components. The configuration data can be tailored to meet the requirements of the operator in the tag configuration screens in 800xA Process Portal. The configuration from Composer is described in the technical information “commissioning a System", Technical Information 30/72-8055. Composer function block and signal definitions

The following figures show the function blocks (monitoring blocks) used to display the process variables in 800xA Process Portal.

238

3BDD011741R4101


Configuration

The block connections on the monitor block identify signals exchanged between Melody and 800xA Process Portal. All variables originate from the automation process and are displayed on the left of the function block. CSCBIN3-00

CSCBIN6-00

CSCBIN13-00

Connection behavior of the function block connections on the function block: alw

=


ext

=


opt

=



Fig.: Connection example for the MelodyBinary automation class (data link to 800xA Process Portal)

3BDD011741R4101

239

Configuration


Event typical

The signalling behavior of a function is defined by specifying the behavior of the signal in Composer. The event typical is connected to the process signal. The following configuration data is defined as part of an event typical: • Priority of the signal (Prio) • Generate signal (SGen) • Signal as alarm (Al) • Signal page acknowledge (PAck) • Dual-value signal (Dual) • Signal can be inhibited (Inhib) # • Signal can be suppressed (Supp) # • Signal generation for negative edge change (Logic) #) Information is only evaluated in code generation for Operations.

The status texts are defined for the signal itself.

240

3BDD011741R4101


Automation class


The following table describes the structure of the MelodyBinary automation class. Atom

Description

OPC data type

Melody data type

Melody I/O

Read

I1

Boolean input

Bool

Boolean

I

X

I2

Boolean input

Bool

Boolean

I

X

I3

Boolean input

Bool

Boolean

I

X

I4

Boolean input

Bool

Boolean

I

X

I5

Boolean input

Bool

Boolean

I

X

I6

Boolean input

Bool

Boolean

I

X

I7

Boolean input

Bool

Boolean

I

X

I8

Boolean input

Bool

Boolean

I

X

I9

Boolean input

Bool

Boolean

I

X

I10

Boolean input

Bool

Boolean

I

X

I11

Boolean input

Bool

Boolean

I

X

I12

Boolean input

Bool

Boolean

I

X

I13

Boolean input

Bool

Boolean

I

X

Write Write access


Atom name

Description


OPC data type


Melody data type

Melody data type

Melody I/O


Read


Write

Atom can be written from 800xA Process Portal (operator action or external control system).

Write access


3BDD011741R4101

241

Automation class


Calculated atoms


Description:

.BAD/SIG Quality of process signals transmitted

242

Processing standard: OR (I1/SIG, I2/SIG, I3/SIG, I4/SIG, I5/SIG, I6/SIG, I7/SIG, I8/SIG, I9/SIG, I10/SIG, I11/SIG, I12/SIG, I13/SIG)

.ALARM

General function fault, alarm OR (I1/ALARM, I2/ALARM, signal pending I3/ALARM, I4/ALARM, I5/ALARM, I6/ALARM, I7/ALARM, I8/ALARM, I9/ALARM, I10/ALARM, I11/ALARM, I12/ALARM, I13/ALARM)

.UNACK

General function fault, alarm OR (I1/UNACK, I2/UNACK, signal pending, error status I3/UNACK, I4/UNACK, I5/UNACK, I6/UNACK, not yet acknowledged I7/UNACK, I8/UNACK, I9/UNACK, I10/UNACK, I11/UNACK, I12/UNACK, I13/UNACK)

3BDD011741R4101


Melody CLCx controller

Melody CLCx controller Features

The controller (MelodyCLC, MelodyCLCD and MelodyCLCM) automation classes allow pre-configured controller functions with and without a drive function in Melody to be displayed in a data structure in 800xA Process Portal. The holding controller modules can be optionally assigned to Y/W/K memories. A selection of pre-configured faceplates is available, depending on the connection of the controller modules.

3BDD011741R4101

243

Configuration


Configuration The MelodyCLCx automation classes display the controller function from the Melody automation system in a variable structure in 800xA Process Portal. This standard display is configured by connection of the process signals in Composer for Melody. As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the Melody connection components. The configuration data can be tailored to meet the requirements of the operator in the tag configuration screens in 800xA Process Portal. The configuration from Composer is described in the technical information “commissioning a System", Technical Information 30/72-8055. Composer function block and signal definitions

The following figures show function blocks (monitoring blocks) used to display the process variables in 800xA Process Portal. The block connections on the monitoring block identify signals exchanged between Melody and 800xA Process Portal. The input variables, shown on the left, originate from the automation process. The output variables, shown on the right, originate from 800xA Process Portal or an external control function. To permit the exchange of process signals between Melody and 800xA Process Portal, the function block connections on the monitor function block must be connected to the function blocks for the controller function in Melody.

244

3BDD011741R4101


OPCLC-00

Configuration

OPCLCD-00

OPCLCM-00

3BDD011741R4101

245

Configuration


Connection behavior of the function block connections on the monitoring block:

alw

=


ext

=


opt

=


The automation function in 800xA Process Portal is configured using code generation for Operations in Composer. MelodyCLC automation class

The MelodyCLC automation class allows three operator controllable memories, five analog signals and four binary signals to be combined. The input variables (left) originate from the automation process, while the output variables (right) originate from 800xA Process Portal or an external control function. The MelodyCLC automation class will only function in combination with the MelodyCLCD automation class. The MelodyCLC class uses the TOP connection to refer to a tag, whose display sections are recorded in a MelodyCLCD class.

246

3BDD011741R4101


Configuration

Fig.: Connection example for the MelodyCLC automation class (data link to 800xA Process Portal)

MelodyCLCD automation class

The MelodyCLCD automation class allows one operator controllable memory to be combined with two limit value signals, four reference signals and four binary signals. The input variables (left) originate from the automation process, while the output variables (right) originate from 800xA Process Portal or an external control function. Using four signal references (RX1, …, RX3, RCLC), functional relationships for process control can be edited by the operator (signpost to another function). The MelodyCLCD class uses the RCLC connection to refer to a tag, whose display sections are recorded in a MelodyCLCD automation class. In this way, process

3BDD011741R4101

247

Configuration


variables from both automation classes can be accessed in the data display (e. g. faceplate). Fig.: Connection example for the MelodyCLCD automation class (data link to 800xA Process Portal)

MelodyCLCM automation class

The MelodyCLCM automation class allows three operator controllable memories, of which the first can have two limit values, five analog signals and four binary signals to be combined.

248

3BDD011741R4101


Configuration

Fig.: Connection example for the MelodyCLCM automation class (data link to 800xA Process Portal)

Event typical

The signalling behavior of a function is defined by providing an event typical or specifying the behavior of the signal in Composer. The event typical is connected to a process signal. The following configuration data is defined as part of an event typical: • Priority of the signal (Prio) • Generate signal (SGen) • Signal as alarm (Al) • Signal page acknowledge (PAck) • Dual-value signal (Dual) • Signal can be inhibited (Inhib) # • Signal can be suppressed (Supp) #

3BDD011741R4101

249

Configuration


• • •

Signal generation for negative edge change (logic) Operator profile (PROF) Packed Boolean sub-variant $ #) Information is only evaluated in code generation for Operations. $) Only defined for event typicals for Packed Boolean signals.

For the configuration of signalling behavior in Composer, a distinction is made between the event typical for Boolean signals and the event typical for Packed Boolean signals. Event typicals for Boolean signals defined the signalling behavior of precisely one binary signal. Event typicals for Packed Boolean signals define the signalling behavior of the individual binary signals packed in the signal (max. 32). Standard event typicals are stored in Composer for the MelodyCLC, MelodyCLCD and MelodyCLCM automation classes. These event typicals refer to a sub-variant, which describes the structure and status texts for the packed Boolean signal. Automation class

Memory

Function block connection

Event typical name

MelodyCLC

Memory 1

IST1

MC1

Memory 2

IST2

MC2

Memory 3

IST3

MC3

MelodyCLCD

Memory 1

IST1

MP1

MelodyCLCM

Memory 1

IST1

MF1

Memory 2

IST2

MF2

Memory 3

IST3

MF3

Structure of a event typical using the example of MP1. The signalling behavior can be adjusted on a project-specific basis.

250

3BDD011741R4101


Configuration

Table: Event typical MP1 Name MP1 PROF

Brief desc.

Explanatory text

MP1

Variable speed drive


160

CLC_1

MIdx

Csel

Prio

0

E1

5

1

E0

5

2

BLK1

5

3

BLK0

5

6

R1

5

7

R0

5

8

P1

5

9

P0

5

10

OL1

5

11

OL0

5

30

PCF

5

29

EER

5

31

TEST

5

32

ERI

5

33

LI

5

35

MAN

5

36

AUT

5

37

LOCK

5

38

INHI

5

49

OPL

5

51

ER

5

46

DAUT

5

45

DMAN

5

43

MANS

5

44

AUTS

5

3BDD011741R4101

SGen

Al

PAck

Dual

Inhib

Supp

Logic

251

Configuration


Status texts

The status texts for the Boolean signals are configured in Composer. The status texts for individual items of binary information within a packed Boolean signal are not configured in Composer. These status texts are shown in the subvariant (e. g. CLC_1) referred to by the event typical. The sub-variant is stored in the Importer for 800xA Process Portal). Structure of a sub-variant using the example of CLC_1. The status texts and the alias can be adjusted on a project-specific basis. Table: Alias name and status texts for sub-variant CLC_1

252

ATOM

Alias

Status text 1

Status text 0

E1

XC01_1

100 %

(100 %)

E0

XC02_1

0%

(0 %)

BLK1

XM01_1

Torque +

(Torque +)

BLK0

XM02_1

Torque -

(Torque -)

R1

XC48_1

RelAuto +

(RelAuto +)

R0

XC49_1

RelAuto -

(RelAuto -)

P1

XC31_1

Protect +

(Protect +)

P0

XC32_1

Protect -

(Protect -)

OL1

XC21_1

SeqInterv+

(SeqInterv+)

OL0

XC22_1

SeqInterv-

(SeqInterv-)

PCF

XM47_1

PosCktDist

(PosCktDist)

EER

XM41_1

ExtDist

(ExtDist)

TEST

XC09_1

Test

(Test)

ERI

XM43_1

ERI

(ERI)

LI

XM57_1

LocInterv

(LocInterv)

MAN

XC03_1

Manual

(Manuell)

AUT

XC04_1

Automatic

(Automatic)

3BDD011741R4101


Automation class

LOCK

XM16_1

Lock

(Lock)

INHI

XM17_1

Inhibit

(Inhibit)

OPL

XC19_1

OperLock

(OperLock)

DAUT

XM44_1

DistAuto

(DistAuto)

DMAN

XM45_1

DistMan

(DistMan)

MANS

XC26_1

ManStatic

(ManStatic)

AUTS

XC25_1

AutStatic

(AutStatic)

OPHP

XM18_1

HighPrioOp

(HighPrioOp)

AUT1

XC27_1

RelAuto +

(RelAuto +)

AUT0

XC28_1

RelAuto -

(RelAuto -)

E1N

XC51_1

N 100%

(N 100%)

E0N

XC52_1

N 0%

(N 0%)

CMDAC


The following table describes the structure of the automation class for MelodyCLC individual control. Table: Structure of the MelodyCLC and MelodyCLCM automation classes Atom

Description

OPC data type

Melody Melody Read Write Write data type I/O access

IST1

Memory 1 status

Integer

Packed Boolean

I

X

IST2

Memory 2 status

Integer

Packed Boolean

I

X

IST3

Memory 3 status

Integer

Packed Boolean

I

X

E1_1

End position 1 SP1

Bool

3BDD011741R4101

X

253

Automation class


E1N_1

End position not 1 SP1

Bool

X

E0_1

End position 0 SP1

Bool

X

E0N_1


Bool

X

BLK1_1

Blockade 1 SP1

Bool

X

BLK0_1

Blockade 0 SP1

Bool

X

AUT1_1

Release Automatic+ SP1

Bool

X

CMD+_1

Activate command + SP1

Bool (w)

AUT0_1

Release AutomaticSP1

Bool

CMD-_1

Activate commandSP1

Bool (w)

MAN_1

Manual SP1

Bool (w)

OMN_1

Manual control SP1

Bool (w)

AUT_1

Automatic SP1

Bool (w)

OAU_1

Automatic control SP1 Bool (w)

LOCK_1

Lock SP1

Bool (w)

X

R1_1

Release 1 SP1

Bool

X

R0_1

Release 0 SP1

Bool

X

P1_1

Protective action 1 SP1

Bool

X

P0_1


Bool

X

ERI_1

Fault action SP1

Bool

X

ER_1

Fault SP1

CMDAC_1 Command acknowledgement SP1

254

X

Operator action

X

Operator action

X

Operator mode

X

Computer mode

X

Operator mode

X

Computer mode

X

Lock operator mode

X

X Extended O Boolean X Extended O Boolean

Bool

X

Bool

X

3BDD011741R4101


Automation class

OPL_1

Lock operation SP1

Bool (w)

X

OPHP_1

Higher priority operation SP1

Bool

X

EER_1

External fault SP1

Bool

X

TEST_1

Test position SP1

Bool

X

IC1_1

Control system 1 SP1 Bool

X

OC11

Command unit 1 On SP1

IC0_1


OC01

Command unit 1 Off

Bool (w)

INHI_1

Inhibit SP1

Bool

OIN1

Command inhibit SP1 Bool (w)

PCF_1

Positioning circuit fault Bool SP1

X

DAUT_1

Automatic fault SP1

Bool

X

DMAN_1

Manual fault SP1

Bool

X

MANS_1

Manual control SP1

Bool

X

AUTS_1

Automatic control SP1 Bool

X

LI_1

Local action SP1

Bool

X

ACK_1

Acknowledgement SP1

Bool (w)

A1

control variable (Y) SP1

Double (w)

A1/ALARM

Bool (w)

Extended O Boolean


X

Computer mode

X

Computer mode

X

Computer mode

X

Acknowledge

X

Setpoint control

X

Computer mode

X

High limits


Real

I

O

X

Bool

A1/UNACK

Bool

YA1

Setpoint A1 SP1

Double (w)

Real

A1V1

Limit signal 1 for A1 SP1

Bool

Extended I Boolean

A1X1

Limit value 1 for A1 (actual) SP1

Double (w)

3BDD011741R4101

X

X

255

Automation class

256


YA11

Specified limit value A1V1

Double (w)

Real

O

X

Computer mode

A1V2


Bool

Extended I Boolean

A1X2


Double (w)

Real

X

Low limits

YA12

Specified limit value A1V2 SP1

Double (w)

Real

O

X

Computer mode

OOP1

Nominal word SP1

IntegerW

Packed Boolean

O

X

Computer mode

E1_2

End position 1 SP2

Bool

X

E1N_2


Bool

X

E0_2

End position 0 SP2

Bool

X

E0N_2


Bool

X

BLK1_2

Blockade 1 SP2

Bool

X

BLK0_2

Blockade 0 SP2

Bool

X

AUT1_2


Bool

X

CMD+_2


Bool (w)

X

Operator action

AUT0_2


Bool

CMD-_2

Activate commandSP2

Bool (w)

X

Operator action

MAN_2

Manual SP2

Bool (w)

X

Operator mode

OMN2

Manual control SP2

Bool (w)

X

Computer mode

AUT_2

Automatic SP2

Bool (w)

X

Operator mode

OAU2


X

Computer mode

LOCK_2

Lock SP2

Bool (w)

X

X

Lock operator mode

R1_2

Release 1 SP2

Bool

X

X

X


3BDD011741R4101


Automation class

R0_2

Release 0 SP2

Bool

X

P1_2


Bool

X

P0_2


Bool

X

ERI_2

Fault action SP2

Bool

X

ER_2

Fault SP2

Bool

X


Bool

X

OPL_2

Lock operation SP2

Bool (w)

X

OPHP_2


Bool

X

EER_2

External fault SP2

Bool

X

TEST_2

Test position SP2

Bool

X

IC1_2


X

OC12


IC0_2


OC02

Command unit 1 Off

Bool (w)

INHI_2

Inhibit SP2

Bool

OIN2


PCF_2


X

DAUT_2

Automatic fault SP2

Bool

X

DMAN_2

Manual fault SP2

Bool

X

MANS_2

Manual control SP2

Bool

X

AUT1_2


X

LI_2

Local action SP2

Bool

X

ACK_2

Acknowledgement SP2

Bool (w)

3BDD011741R4101

Bool (w)

Extended O Boolean

X


X

Computer mode

X

Computer mode

X

Computer mode

X

Acknowledge


257

Automation class

A2

258



Double (w)

A2/ALARM

Bool

A2/UNACK

Bool Double (w)

Real

I

Real Packed Boolean

X

X

Setpoint control

O

X

Computer mode

O

X

Computer mode

X

Operator action

X

Operator action

X

Operator mode

X

Computer mode

X

Operator mode

X

Computer mode

X

Lock operator mode

YA2

Setpoint A1 SP2

OOP2

Operator setpoint SP2 IntegerW

E1_3

End position 1 SP3

Bool

X

E1N_3


Bool

X

E0_3

End position 0 SP3

Bool

X

E0N_3


Bool

X

BLK1_3

Blockade 1 SP3

Bool

X

BLK0_3

Blockade 0 SP3

Bool

X

AUT1_3


Bool

X

CMD+_3


Bool (w)

AUT0_3


Bool

CMD-_3

Activate commandSP3

Bool (w)

MAN_3

Manual SP3

Bool (w)

OMN3

Manual control SP3

Bool (w)

AUT_3

Automatic SP3

Bool (w)

OAU3


LOCK_3

Lock SP3

Bool (w)

X

R1_3

Release 1 SP3

Bool

X

R0_3

Release 0 SP3

Bool

X

X


3BDD011741R4101


Automation class

P1_3


Bool

X

P0_3


Bool

X

ERI_3

Fault action SP3

Bool

X

ER_3

Fault SP3

Bool

X


Bool

X

OPL_3

Lock operation SP3

Bool (w)

X

OPHP_3


Bool

X

EER_3

External fault SP3

Bool

X

TEST_3

Test position SP3

Bool

X

IC1_3


X

OC13


IC0_3


OC03

Command unit 1 Off

Bool (w)

INHI_3

Inhibit SP3

Bool

OIN3


PCF_3


X

DAUT_3

Automatic fault SP3

Bool

X

DMAN_3

Manual fault SP3

Bool

X

MANS_3

Manual control SP3

Bool

X

Bool (w)

Extended O Boolean


X

Computer mode

X

Computer mode

X

Computer mode

X

Acknowle dge

X

Setpoint control


AUTS_3


X

LI_3

Local action SP3

Bool

X

ACK_3

Acknowledgement SP3

Bool (w)

A3


Double (w)

3BDD011741R4101

X

Real

I

X

259

Automation class


A3/ALARM

Bool

A3/UNACK

Bool

YA3

Setpoint A1 SP3

Double (w)

Real

O

X

Computer mode

OOP3

Operator setpoint SP3 IntegerW

Packed Boolean

O

X

Computer mode

RX1

Reference signal 1

ATOMREF

X

RX2

Reference signal 2

ATOMREF

X

RX3

Reference signal 3

ATOMREF

X

RX4

Reference signal 4

ATOMREF

X

X1

Real input

Double

X2

Real input

Double

Real

I

X

X3

Real input

Double

Real

I

X

X4

Real input

Double

Real

I

X

X5

Real input

Double

Real

I

X

I1

Boolean input

Bool

Extended I Boolean

X

I2

Boolean input

Bool

Extended I Boolean

X

I3

Boolean input

Bool

Extended I Boolean

X

I4

Boolean input

Bool

Extended I Boolean

X

CR1

Criteria telegram 1

Integer

Packed Boolean

I

X

CR2

Criteria telegram 2

Integer

Packed Boolean

I

X

CR3

Criteria telegram 3

Integer

Packed Boolean

I

X

TOP

Object reference

SymRef

Real

I

X

Table: Structure of the MelodyCLCD automation class

260

3BDD011741R4101


Automation class

Atom

Description

Operate IT data type

Melody Melody Read Write Write data type I/O access

IST1

Memory 1 status

Integer

Packed Boolean

E1_1

End position 1 SP1

Bool

X

E1N_1

End position not 1 SP1 Bool

X

E0_1

End position 0 SP1

X

E0N_1

End position not 0 SP1 Bool

X

BLK1_1

Blockade 1 SP1

Bool

X

BLK0_1

Blockade 0 SP1

Bool

X

AUT1_1


Bool

X

CMD+_1


Bool (w)

AUT0_1


Bool

CMD-_1

Activate commandSP1

Bool (w)

MAN_1

Manual SP1

Bool (w)

OMN

Manual control SP1

Bool (w)

AUT_1

Automatic SP1

Bool (w)

OAU

Automatic control SP1

Bool (w)

LOCK_1

Lock SP1

Bool (w)

X

R1_1

Release 1 SP1

Bool

X

R0_1

Release 0 SP1

Bool

X

P1_1

Protective action 1 SP1 Bool

X

P0_1

Protective action 0 SP1 Bool

X

ERI_1

Fault action SP1

Bool

X

ER_1

Fault SP1

Bool

X

3BDD011741R4101

I

Bool

X

X

Operator action

X

Operator action

X

Operator mode

X

Compute r mode

X

Operator mode

X

Compute r mode

X

Lock operator mode

X


261

Automation class

262


CMDAC_1 Command Bool acknowledgement SP1

X

OPL_1

Lock operation SP1

Bool (w)

X

OPHP_1


Bool

X

EER_1

External fault SP1

Bool

X

TEST_1

Test position SP1

Bool

X

IC1_1

Control system 1 SP1

Bool

OC1


Bool (w)

IC0_1

Control system 0 SP1

Bool

OC0

Command unit 1 Off

Bool (w)

Inhibit SP1

Bool

Command inhibit SP1

Bool (w)

PCF_1

Positioning circuit fault SP1

Bool

X

DAUT_1

Automatic fault SP1

Bool

X

DMAN_1

Manual fault SP1

Bool

X

MANS_1

Manual control SP1

Bool

X

AUTS_1

Automatic control SP1

Bool

X

LI_1

Local action SP1

Bool

X

ACK_1

Acknowledgement SP1 Bool (w)

A1


Bool

A1/UNACK

Bool

X

Compute r mode

X

Compute r mode

X

Compute r mode

X

Acknowledge

X

Setpoint control

X

Compute r mode

X Extended O Boolean

OIN

A1/ALARM



INHI_1

Double (w)

X


Real

I

O

YA1

Setpoint A1 SP1

Double (w)

Real

A1V1


Bool

Extended I Boolean

X

X

3BDD011741R4101


Automation class

A1X1


Double (w)

X

High limits

YA11

Specified limit value A1V1

Double (w)

Real

X

Compute r mode

A1V2


Bool

Extended I Boolean

A1X2


Double (w)

Real

X

Low limits

YA12

Specified limit value A1V2 SP1

Double (w)

Real

O

X

Compute r mode

OOP

Nominal word SP1

IntegerW

Packed Boolean

O

X

Compute r mode

RX1

Reference signal 1

ATOMREF

X

RX2

Reference signal 2

ATOMREF

X

RX3

Reference signal 3

ATOMREF

X

O X

RX4

Reference signal 4

ATOMREF

X1

Real input

Double

Real

I

X

X2

Real input

Double

Real

I

X

X3

Real input

Double

Real

I

X

X4

Real input

Double

Real

I

X

I1

Boolean input

Bool

Extended I Boolean

X

I2

Boolean input

Bool

Extended I Boolean

X

I3

Boolean input

Bool

Extended I Boolean

X

I4

Boolean input

Bool

Extended I Boolean

X

CR1

Criteria telegram 1

Integer

Packed Boolean

I

X

CR2

Criteria telegram 2

Integer

Packed Boolean

I

X

CR3

Criteria telegram 3

Integer

Packed Boolean

I

X

RCLC

Object reference

SymRef

3BDD011741R4101

X

263

Automation class



Atom name

Description Operate

IT


data type


Melody data type

Melody data type

Melody I/O


Read


Write


Write access


Control

The operator actions for the controller function are converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in Melody. The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in Melody. Table: 800xA Process Portal commands and resulting control code in Melody

264

Memory:

800xA Process Melody control Effect: Portal: commands code

Y memory

ACK/SIG

00000805H

Acknowledge error memory

OPL/SIG

0000080bH

Set/reset general operator input inhibit

MAN/SIG

00000813H

Switch the operating mode to “Manual”

AUT/SIG

00000823H

Switch operating mode to “Automatic”

LOCK/SIG

00000843H

Lock operating mode switching – “Lock”

CMD+/SIG

00000883H

Incremental adjustment

CMD-/SIG

00000903H

Decremental adjustment

3BDD011741R4101


W memory

K memory

Automation class

ACK/SIG

00000405H


OPL/SIG

0000040bH


MAN/SIG

00000413H


AUT/SIG

00000423H


LOCK/SIG

00000443H


CMD+/SIG

00000483H


CMD-/SIG

00000503H


ACK/SIG

00000c05H


OPL/SIG

00000c0bH


MAN/SIG

00000c13H


AUT/SIG

00000c23H


LOCK/SIG

00000c43H


CMD+/SIG

00000c83H


CMD-/SIG

00000d03H


Calculated atoms

Calculated atoms are atoms, which are derived from values from other atoms, according to a defined processing standard. The atoms are calculated centrally in Melody Connectivity Server. Calculation standard for MelodyCLC and Melody CLCM automation classes

3BDD011741R4101

265

Automation class


Atom:

Description:


.BAD/SIG


OR (IST1/SIG, A1/SIG, A1V1/SIG, A1V2/SIG, IST2/SIG, A2/SIG, IST3/SIG, A3/SIG, X1/SIG, X2/SIG, X3/SIG, X4/SIG, X5/SIG, I1/SIG, I2/SIG, I3/SIG, I4/SIG)

.ALARM


OR (E1_1/ALARM, E0_1/ALARM, BLK1_1/ALARM, BLK0_1/ALARM, MAN_1/ALARM, AUT_1/ALARM, LOCK_1/ALARM, R1_1/ALARM, R0_1/ALARM, P1_1/ALARM, P0_1/ALARM, ERI_1/ALARM, ER_1/ALARM, OPL_1/ALARM, OPHP_1/ALARM, EER_1/ALARM, TEST_1/ALARM, IC1_1/ALARM, IC0_1/ALARM, INHI_1/ALARM, PCF_1/ALARM, DAUT_1/ALARM, DMAN_1/ALARM, MANS_1/ALARM, AUTS_1/ALARM, LI_1/ALARM, E1_2/ALARM, E0_2/ALARM, BLK1_2/ALARM, BLK0_2/ALARM, MAN_2/ALARM, AUT_2/ALARM, LOCK_2/ALARM, R1_2/ALARM, R0_2/ALARM, P1_2/ALARM, P0_2/ALARM, ERI_2/ALARM, ER_2/ALARM, OPL_2/ALARM, OPHP_2/ALARM, EER_2/ALARM, TEST_2/ALARM, IC1_2/ALARM, IC0_2/ALARM, INHI_2/ALARM, PCF_2/ALARM, DAUT_2/ALARM, DMAN_2/ALARM, MANS_2/ALARM, AUTS_2/ALARM, LI_2/ALARM, E1_3/ALARM, E0_3/ALARM, BLK1_3/ALARM, BLK0_3/ALARM, MAN_3/ALARM, AUT_3/ALARM, LOCK_3/ALARM, R1_3/ALARM, R0_3/ALARM, P1_3/ALARM, P0_3/ALARM, ERI_3/ALARM, ER_3/ALARM, OPL_3/ALARM, OPHP_3/ALARM, EER_3/ALARM, TEST_3/ALARM, IC1_3/ALARM, IC0_3/ALARM, INHI_3/ALARM, PCF_3/ALARM, DAUT_3/ALARM, DMAN_3/ALARM, MANS_3/ALARM, AUTS_3/ALARM, LI_3/ALARM, A1V1/ALARM, A1V2/ALARM, I1/ALARM, I2/ALARM, I3/ALARM, I4/ALARM)

266

3BDD011741R4101


Automation class

OR (E1_1/UNACK, E0_1/UNACK, BLK1_1/UNACK, BLK0_1/UNACK, MAN_1/UNACK, AUT_1/UNACK, LOCK_1/UNACK, R1_1/UNACK, R0_1/UNACK, P1_1/UNACK, P0_1/UNACK, ERI_1/UNACK, ER_1/UNACK, OPL_1/UNACK, OPHP_1/UNACK, EER_1/UNACK, TEST_1/UNACK, IC1_1/UNACK, IC0_1/UNACK, INHI_1/UNACK, PCF_1/UNACK, DAUT_1/UNACK, DMAN_1/UNACK, MANS_1/UNACK, AUTS_1/UNACK, LI_1/UNACK, E1_2/UNACK, E0_2/UNACK, BLK1_2/UNACK, BLK0_2/UNACK, MAN_2/UNACK, AUT_2/UNACK, LOCK_2/UNACK, R1_2/UNACK, R0_2/UNACK, P1_2/UNACK, P0_2/UNACK, ERI_2/UNACK, ER_2/UNACK, OPL_2/UNACK, OPHP_2/UNACK, EER_2/UNACK, TEST_2/UNACK, IC1_2/UNACK, IC0_2/UNACK, INHI_2/UNACK, PCF_2/UNACK, DAUT_2/UNACK, DMAN_2/UNACK, MANS_2/UNACK, AUTS_2/UNACK, LI_2/UNACK, E1_3/UNACK, E0_3/UNACK, BLK1_3/UNACK, BLK0_3/UNACK, MAN_3/UNACK, AUT_3/UNACK, LOCK_3/UNACK, R1_3/UNACK, R0_3/UNACK, P1_3/UNACK, P0_3/UNACK, ERI_3/UNACK, ER_3/UNACK, OPL_3/UNACK, OPHP_3/UNACK, EER_3/UNACK, TEST_3/UNACK, IC1_3/UNACK, IC0_3/UNACK, INHI_3/UNACK, PCF_3/UNACK, DAUT_3/UNACK, DMAN_3/UNACK, MANS_3/UNACK, AUTS_3/UNACK, LI_3/UNACK, A1V1/UNACK, A1V2/UNACK, I1/UNACK, I2/UNACK, I3/UNACK, I4/UNACK)

.UNACK


.A1/ALARM

OR (ER_1/ALARM, EER_1/ALARM, BLK0_1/ALARM, Function fault, alarm signal BLK1_1/ALARM, PCF_1/ALARM, DAUT_1/ALARM, pending (ER||EER||RF0||BLK0||BLK1||P DMAN_1/ALARM, A1V1/ALARM, A1V2/ALARM) CF||DAUT||DMAN||A1V1||A1V2)

.A1/UNACK

OR (ER_1/UNACK, EER_1/UNACK, BLK0_1/UNACK, Function fault, alarm signal BLK1_1/UNACK, PCF_1/UNACK, DAUT_1/UNACK, pending, error status not yet DMAN_1/UNACK, A1V1/UNACK, A1V2/UNACK) acknowledged (ER||EER||RF0||BLK0||BLK1||P CF||DAUT||DMAN||A1V1||A1V2)

.A2/ALARM

Function fault, alarm signal pending (ER||EER||RF0||BLK0||BLK1||P CF||DAUT||DMAN)

OR (ER_2/ALARM, EER_2/ALARM, BLK0_2/ALARM, BLK1_2/ALARM, PCF_2/ALARM, DAUT_2/ALARM, DMAN_2/ALARM)

.A2/UNACK

Function fault, alarm signal pending, error status not yet acknowledged (ER||EER||RF0||BLK0||BLK1||P CF||DAUT||DMAN)

OR (ER_2/UNACK, EER_2/UNACK, BLK0_2/UNACK, BLK1_2/UNACK, PCF_2/UNACK, DAUT_2/UNACK, DMAN_2/UNACK)

3BDD011741R4101

267

Automation class


.A3/ALARM

Function fault, alarm signal pending (ER||EER||RF0||BLK0||BLK1||P CF||DAUT||DMAN)

OR (ER_3/ALARM, EER_3/ALARM, BLK0_3/ALARM, BLK1_3/ALARM, PCF_3/ALARM, DAUT_3/ALARM, DMAN_3/ALARM)

.A3/UNACK

Function fault, alarm signal pending, error status not yet acknowledged (ER||EER||RF0||BLK0||BLK1||P CF||DAUT||DMAN)

OR (ER_3/UNACK, EER_3/UNACK, BLK0_3/UNACK, BLK1_3/UNACK, PCF_3/UNACK, DAUT_3/UNACK, DMAN_3/UNACK)

268

3BDD011741R4101


Automation class

Calculation standard for MelodyCLCD automation class Atom:

Description:


.BAD/SIG


OR (IST1/SIG, A1/SIG, A1V1/SIG, A1V2/SIG, IST2/SIG, A2/SIG, IST3/SIG, A3/SIG, X1/SIG, X2/SIG, X3/SIG, X4/SIG, X5/SIG, I1/SIG, I2/SIG, I3/SIG, I4/SIG)

.ALARM


OR (E1_1/ALARM, E0_1/ALARM, BLK1_1/ALARM, BLK0_1/ALARM, MAN_1/ALARM, AUT_1/ALARM, LOCK_1/ALARM, R1_1/ALARM, R0_1/ALARM, P1_1/ALARM, P0_1/ALARM, ERI_1/ALARM, ER_1/ALARM, OPL_1/ALARM, OPHP_1/ALARM, EER_1/ALARM, TEST_1/ALARM, IC1_1/ALARM, IC0_1/ALARM, INHI_1/ALARM, PCF_1/ALARM, DAUT_1/ALARM, DMAN_1/ALARM, MANS_1/ALARM, AUTS_1/ALARM, LI/ALARM, A1V1/ALARM, A1V2/ALARM, I1/ALARM, I2/ALARM, I3/ALARM, I4/ALARM)

.UNACK


OR (E1_1/UNACK, E0_1/UNACK, BLK1_1/UNACK, BLK0_1/UNACK, MAN_1/UNACK, AUT_1/UNACK, LOCK_1/UNACK, R1_1/UNACK, R0_1/UNACK, P1_1/UNACK, P0_1/UNACK, ERI_1/UNACK, ER_1/UNACK, OPL_1/UNACK, OPHP_1/UNACK, EER_1/UNACK, TEST_1/UNACK, IC1_1/UNACK, IC0_1/UNACK, INHI_1/UNACK, PCF_1/UNACK, DAUT_1/UNACK, DMAN_1/UNACK, MANS_1/UNACK, AUTS_1/UNACK, LI/UNACK, A1V1/UNACK, A1V2/UNACK, I1/UNACK, I2/UNACK, I3/UNACK, I4/UNACK)

.A1/ALARM

OR (ER_1/ALARM, EER_1/ALARM, BLK0_1/ALARM, Function fault, alarm signal BLK1_1/ALARM, PCF_1/ALARM, DAUT_1/ALARM, pending (ER||EER||RF0||BLK0||BLK1||PC DMAN_1/ALARM, A1V1/ALARM, A1V2/ALARM) F||DAUT||DMAN||A1V1||A1V2)

.A1/UNACK

OR (ER_1/UNACK, EER_1/UNACK, BLK0_1/UNACK, Function fault, alarm signal BLK1_1/UNACK, PCF_1/UNACK, DAUT_1/UNACK, pending, error status not yet DMAN_1/UNACK, A1V1/UNACK, A1V2/UNACK) acknowledged (ER||EER||RF0||BLK0||BLK1||PC F||DAUT||DMAN||A1V1||A1V2)

3BDD011741R4101

269

MelodyCOA – Change over automatic


MelodyCOA – Change over automatic Features

The change over automatic (MelodyCOA) automation class allows pre-configured automatic reversing from Melody to be displayed in a data structure in 800xA Process Portal. The change over automatic is used to control between 2 and 6 individual control functions. It has an operating mode memory and monitors the status of the subscribers to be controlled. Each subscriber has a priority for control. According to this priority, the subscriber is connected or disconnected. A selection of pre-configured faceplates are available.

Configuration The MelodyCOA automation class displays the change over automatic from the Melody automation system in a variable structure in 800xA Process Portal. This standard display is configured by connection of the process signals in Composer for Melody. As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the Melody connection components. The configuration data can be tailored to meet the requirements of the operator in the tag configuration screens in 800xA Process Portal.

270

3BDD011741R4101


Configuration

The configuration from Composer is described in the technical information “commissioning a System", Technical Information 30/72-8055. Composer function block and signal definitions

The following figures show the change over automatic function block as a processing function in Composer, as well as its associated monitoring block with the interface to Composer and 800xA Process Portal. Fig.: Melody function block

Fig.: Monitoring block – interface to Composer and Operate IT

The connections to the Melody function block identify input and output signals in Melody. Data must be exchanged between Melody and 800xA Process Portal with an external connection between the CA-nn function block and the CA-00 monitoring block.

The block connections on the monitoring block identify signals exchanged between Melody and 800xA Process Portal. The input variables, shown on the left, originate from the automation process. The output variables, shown on the right, originate from 800xA Process Portal or an external control function. To permit the exchange of process signals between Melody and 800xA Process Portal, the function block connections on the monitoring block must be connected to the function blocks for the binary memory in Melody.


=


ext

=


opt

=


3BDD011741R4101

271

Configuration


Fig.: Connection example for the MelodyCOA automation class (data link to 800xA Process Portal)


Event typical

The signalling behavior of a function is defined by providing an event typical or specifying the behavior of the signal in Composer. The event typical is connected to a process signal. The following configuration data is defined as part of an event typical: • Priority of the signal (Prio) • Generate signal (SGen) • Signal as alarm (Al) • Signal page acknowledge (PAck) • Dual-value signal (Dual) • Signal can be inhibited (Inhib) # • Signal can be suppressed (Supp) #

272

3BDD011741R4101


• • •

Configuration

Signal generation for negative edge change (logic) Operator profile (PROF) Packed Boolean sub-variants $ #) Information is only evaluated in code generation for Operations. $) Only defined for event typicals for Packed Boolean signals.

For the configuration of signalling behavior in Composer, a distinction is made between the event typical for Boolean signals and the event typical for Packed Boolean signals. Event typicals for Boolean signals defined the signalling behavior of precisely one binary signal. Event typicals for Packed Boolean signals define the signalling behavior of the individual binary signals packed in the signal (max. 32). For the STA function block connection in the MelodyCOA automation class, the event typicals MU1, MU2, MU3 and MU4 are defined as standard in Composer. These event typicals refer to a sub-variant, which describes the structure and status texts for the packed Boolean signal. Structure of a event typical using the example of MU1. The signalling behavior can be adjusted on a project-specific basis. Table: Event typical MU1 Name

Brief desc.

Explanatory text

MU1

MU1

change over automatic

PROF


160

COA_1

MIdx

Csel

Prio

52

PU1

5

53

PU2

5

54

PU3

5

55

PU4

5

3BDD011741R4101

SGen

Al

PAck

Dual

Inhib

Supp

Logic

273

Configuration


56

PU5

5

57

PU6

5

58

PU7

5

59

PU8

5

10

OL1

5

11

OL0

5

60

SGRA

3

61

SLEA

3

62

PUOFF

3

35

MAN

5

36

AUT

5

37

LOCK

5

38

INHI

5

49

OPL

5

51

ER

5

Status texts

The status texts for the Boolean signals are configured in Composer. The status texts for individual items of binary information within a packed Boolean signal are not configured in Composer. These status texts are shown in the subvariant (e. g. COA_1) referred to by the event typical. The sub-variant is stored in the Importer for 800xA Process Portal). Structure of a sub-variant using the example of COA_1. The status texts and the alias can be adjusted on a project-specific basis.

274

3BDD011741R4101


Automation class

Table: Alias name and status texts for sub-variant COA_1 ATOM

Alias

Status text 1

Status text 0

PU1

XA83

1

(1)

PU2

XA84

2

(2)

PU3

XA85

3

(3)

PU4

XA86

4

(4)

PU5

XA87

5

(5)

PU6

XA88

6

(6)

PU7

XA89

7

(7)

PU8

XA90

8

(8)

MAN

XA04

Manual

(Manual)

AUT

XA03

Automatic

(Automatic)

LOCK

XM16

Lock

(Lock)

ER

XM46

Disturbed

(Disturbed)

OPL

XM19

OperLock

(OperLock)

OPHP

XM18

HighPrioOp

(HighPrioOp)

PUOFF

XA65

PrioAggOff

(PrioAggOff)

OL1

XA21

SeqInterv1

(SeqInterv1)

OL0

XA22

SeqInterv0

(SeqInterv0)

INHI

XM17

Inhibit

(Inhibit)

SGRA

XA66

SP>ActVal

(SP>ActVal)

SLEA

XA64

SP