system 800xa for ac 870p/melody - abb ltd€¦ · · 2017-03-01power and productivity for a...

Power and productivity

for a better worldTM

System 800xA for AC 870P/MelodyConfiguration

System Version 6.0

System 800xA for AC 870P/MelodyConfiguration

System Version 6.0

NOTICEThis document contains information about one or more ABB products and may include a descriptionof or a reference to one or more standards that may be generally relevant to the ABB products. Thepresence of any such description of a standard or reference to a standard is not a representation thatall of the ABB products referenced in this document support all of the features of the described or ref-erenced standard. In order to determine the specific features supported by a particular ABB product,the reader should consult the product specifications for the particular ABB product.

ABB may have one or more patents or pending patent applications protecting the intellectual propertyin the ABB products described in this document.

The information in this document is subject to change without notice and should not be construed asa commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document.

Products described or referenced in this document are designed to be connected, and to communicateinformation and data via a secure network. It is the sole responsibility of the system/product owner toprovide and continuously ensure a secure connection between the product and the system networkand/or any other networks that may be connected.

The system/product owners must establish and maintain appropriate measures, including, but not lim-ited to, the installation of firewalls, application of authentication measures, encryption of data, installa-tion of antivirus programs, and so on, to protect the system, its products and networks, against securitybreaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or information.

ABB verifies the function of released products and updates. However system/product owners are ulti-mately responsible to ensure that any system update (including but not limited to code changes, con-figuration file changes, third-party software updates or patches, hardware change out, and so on) iscompatible with the security measures implemented. The system/product owners must verify that thesystem and associated products function as expected in the environment they are deployed.

In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of anynature or kind arising from the use of this document, nor shall ABB be liable for incidental or conse-quential 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 fromABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized pur-pose.

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 require-ments specified in EMC Directive 2004/108/EC and in Low Voltage Directive 2006/95/EC.

TRADEMARKSAll rights to copyrights, registered trademarks, and trademarks reside with their respective owners.

Copyright © 2003-2016 by ABB. All rights reserved.

Release: September 2016Document number: 3BDD011741-600 A

3BDD011741-600 A 5

Table of Contents

About This User ManualGeneral ............................................................................................................................13

User Manual Conventions ...............................................................................................13

Warning, Caution, Information, and Tip Icons ....................................................13

Terminology.....................................................................................................................14

Released User Manuals and Release Notes.....................................................................14

Section 1 - IntroductionIntended User...................................................................................................................17

IndustrialIT AC 870P / Melody System Structure................................................18

IndustrialIT AC 870P / Melody Entities ...............................................................19

IndustrialIT AC 870P / Melody Context and Structure ........................................20

Supported Operating Systems ..............................................................................22

Engineering ..........................................................................................................23

Base Configuration...............................................................................................24

Topology .............................................................................................................24

Engineering Settings ............................................................................................24

System Definition.................................................................................................25

Alarm and Event System......................................................................................25

Time Synchronization ..........................................................................................25

Backup and Restore..............................................................................................25

Automation Classes Configuration ......................................................................25

Special Functions .................................................................................................25

Technical Data......................................................................................................25

Quality Definition ................................................................................................26

Base Configuration Overview ..............................................................................26

6 3BDD011741-600 A

Section 2 - Base ConfigurationInstall DHCP Server........................................................................................................ 28

Modify Etc/host File ....................................................................................................... 28

Internet Explorer Security Settings ................................................................................. 29

Internet Explorer Language Settings............................................................................... 29

Create Base Topology ..................................................................................................... 29

Object List View .................................................................................................. 30

Tabs ............................................................................................................ 30

Body ............................................................................................................ 30

Footer ............................................................................................................ 30

Design Life Cycle Options .................................................................................. 32

How to Edit Objects............................................................................................. 33

Adding Connectivity Server to the System.......................................................... 34

Adding Event Concentrator to the System........................................................... 39

Adding Coupling Modules of Type CCO30, CMC70, PM875, PM876 and PM87741

Deleting Units or Areas ....................................................................................... 45

Common Object Properties.................................................................................. 46

Configuring Melody Executive Service .......................................................................... 48

Configuring Access Rights.............................................................................................. 49

Settings ............................................................................................................................ 52

Configuration Server............................................................................................ 52

Options ............................................................................................................ 53

Audit Trail............................................................................................................ 59

Synchronizing Engineering Data .................................................................................... 60

Configurator Admin............................................................................................. 60

Auto Configurator ................................................................................................ 62

OPC Data Source Definition ........................................................................................... 65

Alarm and Event OPC Provider Setup ............................................................................ 67

Adjust PNSM Configuration........................................................................................... 69

Tag Importer .................................................................................................................... 70

3BDD011741-600 A 7

Section 3 - TopologyOperator Network Redundancy............................................................................74

Boundary Conditions for HW Planning...............................................................74

Topology Planning Software ...........................................................................................75

Base Topology Configuration..........................................................................................78

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

Affinity .............................................................................................................82

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

Section 4 - Engineering WorkflowBulk Data Management ...................................................................................................91

Import/Export ..................................................................................................................93

Alarms and Events...........................................................................................................94

Object Life Cycle ............................................................................................................95

Operating Parameters ......................................................................................................95

Section 5 - System DefinitionSystem Definition Object ................................................................................................97

Configurable Text ............................................................................................................99

Indexed Text Tab ..................................................................................................99

Substitutable Text Tab ........................................................................................105

Quality Text Tab ............................................................................................................106

Management Tab ...........................................................................................................108

Project History Tab........................................................................................................108

Section 6 - Alarm and Event SystemMelody 800xA Process Portal Process Events ..................................................110

Melody 800xA Process Portal System Events ...................................................113

Melody Message System...............................................................................................114

Melody Message Transport and Buffering.........................................................115

Melody Process Messages..................................................................................117

System and Process Interface Messages ............................................................119

Alarm & Event System Definitions and Overview .......................................................120

8 3BDD011741-600 A

Alarms and Events ............................................................................................. 121

Event Point......................................................................................................... 121

Event Distribution System ................................................................................. 122

Event Concentrators........................................................................................... 122

Event Classifications.......................................................................................... 123

Event Categories ................................................................................................ 123

Event Point Definition................................................................................................... 124

Event Point Attributes........................................................................................ 124

Behavioral Attributes ......................................................................................... 128

Informational Attributes..................................................................................... 129

Event Point State Attributes............................................................................... 131

Dual Event Point Behavior ................................................................................ 133

Non Dual Event Point Behavior......................................................................... 133

Redundancy................................................................................................................... 133

Severity, OPC Severity and Device Priority.................................................................. 135

OPC Severity...................................................................................................... 135

Client Severity.................................................................................................... 135

Device Severity (Melody Priorities) .................................................................. 136

Section 7 - Time SynchronizationOperation Overview........................................................................................... 139

Time Adjustment................................................................................................ 141

800xA Process Portal Time Server Configuration............................................. 142

800xA Process Portal Time Server Client Configuration .................................. 143

Windows Time Synchronization Service (W32Time) ....................................... 144

Master Clock Configuration in Melody............................................................. 145

Configuration of Melody Server as Time Master .............................................. 146

Deleting all Services that are not Time Master.................................................. 147

Melody TimeSync Daemon installation ............................................................ 148

DHCP Configuration for Time Synchronization ............................................... 148

Checking the Configuration with AC 870P/Melody Analyzer .......................... 149

Checking the Master Time Daemon with TsyncCTRL Tool ............................. 149

Melody Server SYSLOG Time Synchronization Diagnostic ............................ 150

3BDD011741-600 A 9

Section 8 - Backup and RestoreAccess............................................................................................................................153

Function .........................................................................................................................153

Backup Industrial IT Melody Composer .......................................................................154

Backup ConfigServer.....................................................................................................154

Restore ConfigServer.....................................................................................................155

Section 9 - Melody Automation ClassesFaceplate ...........................................................................................................157

MelodyAnalog – Analog monitoring ............................................................................158

Features ...........................................................................................................158

Configuration .....................................................................................................158

Automation class ................................................................................................162

MelodyAnMon – Analog monitoring............................................................................166

Features ...........................................................................................................166

Configuration .....................................................................................................166


Melody AnOut – Analog output....................................................................................179

Features ...........................................................................................................179

Configuration .....................................................................................................179


Melody APID controller................................................................................................187

Configuration .....................................................................................................187


MelodyBFlagx – Block flag ..........................................................................................217

Configuration .....................................................................................................217


MelodyBinary – Binary .................................................................................................228

Configuration .....................................................................................................228


Melody CLCx controller ...............................................................................................233

Configuration .....................................................................................................234

10 3BDD011741-600 A

Automation class................................................................................................ 244

MelodyCOA – Change over automatic ......................................................................... 264

Configuration ..................................................................................................... 264


MelodyCount – Counter................................................................................................ 274

Configuration ..................................................................................................... 274


MelodyDos – Dosing circuit ......................................................................................... 279

Configuration ..................................................................................................... 279


MelodyIDF – Individual control ................................................................................... 295

Configuration ..................................................................................................... 295


MelodyOPA – Binary memory...................................................................................... 309

Configuration ..................................................................................................... 309


MelodySel – Preselection.............................................................................................. 319

Configuration ..................................................................................................... 320


Melody SFC – Sequence control................................................................................... 329

Features .......................................................................................................... 329

Configuration ..................................................................................................... 329


MelodySFlagx – Single flag.......................................................................................... 351

Configuration ..................................................................................................... 351


MelodySwClock – Calendar and timing function......................................................... 357

Configuration ..................................................................................................... 357


MelodyTCount – Time and pulse counter..................................................................... 365

Configuration ..................................................................................................... 365


3BDD011741-600 A 11

MelodyTotal – Quantity value acquisition ....................................................................374

Configuration .....................................................................................................374


Section 10 - Special FunctionsIDF Viewer ....................................................................................................................386

Data Exchange to AC 800M..........................................................................................389

Additional Connection to OperateIT B or Maestro UX ................................................391

Fieldbus Support............................................................................................................391

Security..........................................................................................................................392

Batch Support ................................................................................................................393

800xA Batch for AC 870P / Melody..................................................................393

Operational Issues ..............................................................................................401

Event Concentrator - Filter out Melody Tracking Events ..................................402

Information Manger.......................................................................................................405

Section 11 - Melody Simulation EventsInstallation .....................................................................................................................407

System Extension ...............................................................................................407

Control Structure ................................................................................................408

Configuration.................................................................................................................409

Simulation Events Settings Aspect ....................................................................409

SAC Data Source Aspect ...................................................................................410

Simulation Event Service ...................................................................................411

Simulation Events ..............................................................................................412

Error and Exception Handling ...........................................................................413

Operations working directory.............................................................................413

Composer Simulation Records ......................................................................................413

Switch on/off Support of Simulation Records ...................................................413

Simulation Regeneration ....................................................................................414

Appendix A - Quality DefinitionDescription ....................................................................................................................417

12 3BDD011741-600 A

Indicators....................................................................................................................... 417

OPC Quality Definition................................................................................................. 418

800xA for AC 870P / Melody Quality Definition......................................................... 419

Tag.Property Quality for Process Properties ................................................................. 420

Tag.Property Quality for Computed Properties............................................................. 420

Tag.Property Quality for Configuration Data................................................................ 421

Tag.Property Quality for Event Point Related Properties ............................................. 421

Tag Quality .................................................................................................................... 421

Properties .......................................................................................................... 422

800xA for AC 870P / Melody Quality Information........................................... 423

OPC Quality Flags ........................................................................................................ 424

Quality Bits ........................................................................................................ 424

Substatus Bits..................................................................................................... 424

Limit Bits .......................................................................................................... 427

OPCHDA Quality .............................................................................................. 427

Appendix B - Hints, Handlings and WorkaroundsStarting a Redundant Pair of Connectivity Server ........................................................ 429

Simultaneously Starting a Configuration and Connectivity Server .............................. 429

Hints on Partitioning ..................................................................................................... 430

Partitioning of a Melody Connectivity Server ................................................... 430

Partitioning of a Melody Config Server............................................................. 430

Illegal Character Set ...................................................................................................... 431

Illegal First and Last Characters.................................................................................... 432

Live Values in Alarm and Event List ............................................................................ 432

Update of PROF dependent settings ............................................................................. 433

Melody tracking events ................................................................................................. 433

Revision HistoryUpdates in Revision Index A......................................................................................... 435

Index

3BDD011741-600 A 13

About This User Manual

General

Use this section as a guide to the conventions and terminology used throughout this user manual.

User Manual ConventionsMicrosoft Windows conventions are normally used for the standard presentation of material when entering text, key sequences, prompts, messages, menu items, screen elements, etc.

Warning, Caution, Information, and Tip Icons

This User Manual 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:

Any security measures described in this User Manual, for example, for user access, password security, network security, firewalls, virus protection, etc., represent possible steps that a user of an 800xA System may want to consider based on a risk assessment for a particular application and installation. This risk assessment, as well as the proper implementation, configuration, installation, operation, administration, and maintenance of all relevant security related equipment, software, and procedures, are the responsibility of the user of the 800xA System.

Electrical warning icon indicates the presence of a hazard that could result in electrical shock.

Terminology About This User Manual

14 3BDD011741-600 A

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, fully comply with all Warning and Caution notices.

TerminologyA complete and comprehensive list of terms is included in System 800xA System Guide Functional Description (3BSE038018*). The listing includes terms and definitions that apply to the 800xA System where the usage is different from commonly accepted industry standard definitions and definitions given in standard dictionaries such as Webster’s Dictionary of Computer Terms.

Released User Manuals and Release NotesA complete list of all User Manuals and Release Notes applicable to System 800xA is provided in System 800xA Released User Documents (3BUA000263*).

System 800xA Released User Manuals and Release Notes (3BUA000263*) is updated each time a document is updated or a new document is released. It is in pdf format and is provided in the following ways:

• Included on the documentation media provided with the system and published to ABB SolutionsBank when released as part of a major or minor release, Service Pack, Feature Pack, or System Revision.

Warning icon indicates the presence of a hazard that 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 that 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

About This User Manual Released User Manuals and Release Notes

3BDD011741-600 A 15

• Published to ABB SolutionsBank when a User Manual or Release Note is updated in between any of the release cycles listed in the first bullet.

A product bulletin is published each time System 800xA Released User Manuals and Release Notes (3BUA000263*) is updated and published to ABB SolutionsBank.

Released User Manuals and Release Notes About This User Manual

16 3BDD011741-600 A

3BDD011741-600 A 17

Section 1 Introduction

800xA for AC 870P / 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 UserThis instruction is intended for use by personnel responsible for configuring 800xA for AC 870P / Melody to operate as part of IndustrialIT System 800xA. This instruction assumes the configuration engineer or technician is familiar with the relevant Workstation Operating System, Microsoft® Internet Explorer, and the installed IndustrialIT AC870P or Melody control system including the Composer for AC 870P / Melody configuration.

For the list of Operating Systems that System 800xA integrates with, refer to System Guide.

Functional DescriptionThe 800xA for AC 870P / Melody component connects the ControlIT AC 870P / Melody and 800xA Process Portal to an IndustrialIT 800xA distributed process management and control system. Using a series of integrated IndustrialIT 800xA AC 870P / 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. An AC 870P or Melody control unit is a controller and its I/O devices connected for communication on control network.

IndustrialIT AC 870P / Melody System Structure Section 1 Introduction

18 3BDD011741-600 A

System 800xA for AC 870P / Melody operates in both Workstation Operating System and Server Operating System 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 AC 870P or Melody control units. 800xA for AC 870P / Melody also provides maintenance personnel 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 AC 870P / Melody System Structure

The following figure gives an overview about IndustrialIT System 800xA for AC 870P / Melody:

Figure 1. IndustrialIT System 800xA AC 870P / Melody Overview

Multi function modules of type CMC50 or CMC60 use the CCO30 coupling module for the connection to the 800xA Process Portal via 800xA for AC 870P / Melody.

Section 1 Introduction IndustrialIT AC 870P / Melody Entities

3BDD011741-600 A 19

IndustrialIT AC 870P / Melody Entities

IndustrialIT System 800xA for AC 870P / Melody consists of the entities as shown in the following figure:

To enable the connectivity of the operator workplaces to the AC 870P or Melody system part a Connectivity Server is needed. The AC 870P / Melody Connectivity is 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 AC870P or Melody information and how to operate e.g. AC870P or 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.

Figure 2. IndustrialIT System 800xA AC 870P / Melody Entities

IndustrialIT AC 870P / Melody Context and Structure Section 1 Introduction

20 3BDD011741-600 A

Because AC 870P / Melody covers different markets, different industries or even different customers different sets of faceplates or graphics are available at ABB market divisions. Therefore 800xA for AC 870P / Melody does not provide a set of faceplates and graphic symbols by default.

IndustrialIT AC 870P / Melody Context and Structure

800xA for AC 870P / Melody basically consists of five main parts:

• Melody Connectivity Server

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

• Config Server

Configures the AC 870P / Melody OPC Servers, stores the configuration data and manages configuration data life cycle.

• Configuration Management

Seamlessly integrates the AC 870P / 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 AC 870P or Melody functions and with symbols for building process graphics displays. Faceplates and symbols are not integrated part of 800xA for Melody.

For detailed information about the different sets of faceplates or graphics please contact your local ABB supplier or your ABB project partner.

Section 1 Introduction IndustrialIT AC 870P / Melody Context and Structure

3BDD011741-600 A 21

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 AC 870P / 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 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 database for changes. The Auto-Configurator communicates with the Config Server.

Figure 3. 800xA for Melody: Context and Structure

Supported Operating Systems Section 1 Introduction

22 3BDD011741-600 A

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-server-replication).

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

7. The AC 870P / Melody OPC server communicates with the AC870P units (PM875) or with the Melody units (CMC70, CCO30) via Ethernet.

Supported Operating Systems

The following figure shows supported operating system variety:

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

Section 1 Introduction Engineering

3BDD011741-600 A 23

Engineering

The engineering workflow always starts in 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 AC 870P / Melody business rules will be rejected. The lifecycle of an AC 870P / Melody object starts and ends in Composer.

Aspects hosted by other than AC 870P / Melody Aspect Systems might extend Melody objects.

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 AC 870P / Melody life cycle model.

Base Configuration Section 1 Introduction

24 3BDD011741-600 A

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 AC 870P / Melody are part of this section.

Engineering Settings

This section provides an overview of the basic system engineering when using 800xA for AC 870P / Melody.

Figure 5. Basic IndustrialIT 800xA AC 870P / Melody Engineering Workflow

Section 1 Introduction System Definition

3BDD011741-600 A 25

System Definition

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

Alarm and Event System

The 800xA for AC 870P / Melody system provides services to define event conditions and client applications.

Time Synchronization

800xA for AC 870P / 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 AC 870P / 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 AC 870P / 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 AC 870P / 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 AC 870P / Melody system part but not or only partly integrated in the Connectivity itself.

Technical Data

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

Quality Definition Section 1 Introduction

26 3BDD011741-600 A

Quality Definition

The purpose of this appendix is to describe the tag.property qualities in 800xA for AC 870P / Melody.

Base Configuration Overview

This appendix shows the workflow during installation and base configuration of IndustrialIT System 800xA for AC 870P / Melody.

3BDD011741-600 A 27

Section 2 Base Configuration

After the installation has completed, a system is created and the system extensions are loaded. The users are required to perform the following steps to complete the base configuration:

1. Install DHCP Server (refer to Install DHCP Server on page 28).

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

3. Adjust the Internet Explorer Settings (refer to Internet Explorer Security Settings on page 29 and Internet Explorer Language Settings on page 29).

4. Create Base Topology (using the Object List Tool; refer to Create Base Topology on page 29)

5. Configure Melody Executive Service for Configuration Server and Connectivity Server (refer to Configuring Melody Executive Service on page 48).

6. Set Configuration Server database access rights (refer to Configuring Access Rights on page 49).

7. Adjust Settings (refer to Settings on page 52).

8. Synchronize Engineering Data (refer to Synchronizing Engineering Data on page 60).

9. OPC Data Source Definition (refer to OPC Data Source Definition on page 65).

10. Alarm and Event OPC Provider Setup (refer to Alarm and Event OPC Provider Setup on page 67).

11. Adjust PNSM Configuration (refer to Adjust PNSM Configuration on page 69).

Install DHCP Server Section 2 Base Configuration

28 3BDD011741-600 A

12. Start Tag Importer. (refer to Tag Importer on page 70).

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

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

Install DHCP ServerThe Melody / AC870P gateways of type CCO30, CMC70, PM875, PM876 or PM877 get their 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 installed on PC´s which are installed on Windows Server nodes for 800xA Process Portal.

Every time a CCO30, CMC70, PM875, PM876 and PM877 starts after RESET or supply voltage interruption the CCO30, CMC70, PM875, PM876 and PM877 requested the DHCP-Server for its IP-Address. If the DHCP-Server is not available the CCO30, CMC70, PM875, PM876 and PM877 starts after a time-out of 5 minutes with its old IP-address.

Modify Etc/host FileThe entry of the EPC and the IP-address of the CCO30, CMC70, PM875, PM876 and PM877 must be inserted into the file \windows\system32\drivers\etc\host on the Melody Connectivity Server nodes (e.g. 10.0.1.20 EP001A09).

Additional Configuration steps are described in the following sections.

IP address reservations for coupling modules must be available.

The assignment of the IP addresses to the CCO30 / CMC70 / PM875/ PM876 /PM877 modules is also part of the CSE_conf file that is required for the normal operation of Composer and the AC 870P / Melody Analyzer. If available the information can be taken over to the etc/host file.

Section 2 Base Configuration Internet Explorer Security Settings

3BDD011741-600 A 29

Internet Explorer Security SettingsIn order to use the web based tools on Melody Configuration Server and the Connectivity Server Nodes (ObjectList, WebBased Server Explorer, Replication Monitor), the Internet Explorer security settings need to be adjusted:

1. Launch Internet Explorer.

2. Select Tools and then click Internet Options to launch the Internet Options dialog box.

3. Select the Security tab and then select Local intranet and click Custom level.

4. Scroll down to the Initialize and script ActiveX controls not marked as safe for scripting entry under ActiveX controls and plug-ins and choose Enable.

5. Click OK to close all the dialog boxes.

Internet Explorer Language SettingsThe prerequisite for the Object List to open is to set the language for Internet Explorer as English (United States) and this language must be on top of all the preferred languages.

To set this: Open Internet Explorer > Tools > Internet Options > Languages > Set Language Preferences.

Create Base TopologyAfter installation of the 800xA for AC 870P / Melody software it is required to add the following components to the system:

• Connectivity Server (primary and backup)

• Event Concentrator (local and client)

• CCO30 / CMC70 / PM875/ PM876/ PM877 modules (primary and backup)

For editing the object list go to:

Start > All Programs > ABB Industrial IT 800xA > 800xA for AC 870P / Melody > Diagnostics > ObjectList

Object List View Section 2 Base Configuration

30 3BDD011741-600 A

The Configuration is also possible from the TagConfig Aspect in the Control Structure inside the Workplace.

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 AC 870P / Melody. AC 870P / Melody data that is common to multiple object types is presented in the same way to help make AC 870P / 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

Section 2 Base Configuration Footer

3BDD011741-600 A 31

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.

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.

Figure 6. Life Cycles

T05033A

H E LP E D ITO B JE C T

S U B M ITC H AN G E S

C A N C E LC H A N G E S

C O P Y FO RD E S IG N

C H AN G E TOR ELE A SE

C H AN G E TOO U T O F S E RV IC E

C H A N G E TORU N

D ELE TE TH ISV E R S IO N

Design Life Cycle Options Section 2 Base Configuration

32 3BDD011741-600 A

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.

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.

Section 2 Base Configuration How to Edit Objects

3BDD011741-600 A 33

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.

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 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:

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

Adding Connectivity Server to the System Section 2 Base Configuration

34 3BDD011741-600 A

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

3. Click the edit object button ().

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 AC 870P / Melody > Diagnostics > ObjectList

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

Section 2 Base Configuration Adding Connectivity Server to the System

3BDD011741-600 A 35

Define System Nodes for all Melody Connectivity Server

1. Select Template in the Life Cycle field

2. Select SystemNode as template

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

Figure 7. Adding new System Node (example)


36 3BDD011741-600 A

4. Fill in Name and Host Name, uncheck Auxiliary Node and check Force a Mirror database to be created.

Figure 8. Assigning Host Name, Replication and Designation

Section 2 Base Configuration Adding Connectivity Server to the System

3BDD011741-600 A 37

Define all Melody Connectivity Server and the backup Connectivity Server:

1. Select Template in the Life Cycle field

2. Select MelServer as template

Figure 9. Adding new Connectivity Server (Example)


38 3BDD011741-600 A

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

4. Fill in Network identification

Figure 10. Creating new Node Object (Example)

When entering the server path of a redundant pair of Connectivity Server it is necessary to extend the path with the group name of the redundant pair of Connectivity Server.

Section 2 Base Configuration Adding Event Concentrator to the System

3BDD011741-600 A 39

The group name combines primary and backup Connectivity Server.

Adding Event Concentrator to the System

For editing the object list go to: Start > (All) Programs > ABB Industrial IT 800xA > 800xA for AC 870P / Melody > Diagnostics > ObjectList

Define all ClientEvent Concentrators and all LocalEvent Concentrators.

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

Figure 12. Adding new Event Concentrator (Example)

Adding Event Concentrator to the System Section 2 Base Configuration

40 3BDD011741-600 A

The group name combines primary and backup Connectivity Server.

When entering the server path for Event Concentrators of a redundant pair of Connectivity Server it is necessary to extend the path with the group name of the redundant pair of Connectivity Server.

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

Section 2 Base Configuration Adding Coupling Modules of Type CCO30, CMC70, PM875, PM876

3BDD011741-600 A 41

Adding Coupling Modules of Type CCO30, CMC70, PM875, PM876 and PM877

After installation of the 800xA for AC 870P / Melody software it is required to add the AC870P or Melody Coupling Modules to the system.

For editing the object list go to:

Start > (All) Programs > ABB Industrial IT 800xA > 800xA for AC 870P / Melody > Diagnostics > ObjectList

Select new (right mouse click):

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

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 (including release and commissioning)

Figure 14. Adding new CCO to Object List

Adding Coupling Modules of Type CCO30, CMC70, PM875, PM876 and PM877 Section 2 Base

42 3BDD011741-600 A

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

Figure 15. Naming new Coupling Module

Section 2 Base Configuration Adding Coupling Modules of Type CCO30, CMC70, PM875, PM876

3BDD011741-600 A 43

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

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

Figure 16. Naming the belonging Server

Adding Coupling Modules of Type CCO30, CMC70, PM875, PM876 and PM877 Section 2 Base

44 3BDD011741-600 A

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

The Version Tab lists automatically all versioned modifications. The Version Tab is not intended for any entries.

Figure 17. Naming the Redundant Module

Section 2 Base Configuration Deleting Units or Areas

3BDD011741-600 A 45

After having done all settings and after having saved these settings, the life cycle has to be set to 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).

Figure 18. Setting the Module in Running

Common Object Properties Section 2 Base Configuration

46 3BDD011741-600 A

Common Object Properties

All 800xA for AC 870P / 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 1):

• Identification.

• Template.

• Advanced.

Table 1. General Tab Fields

Field1 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.

Section 2 Base Configuration Common Object Properties

3BDD011741-600 A 47

Identification

The identification section shows the information that identifies the object to the user throughout the 800xA for AC 870P / 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.

To enter a comment:

Advanced

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

User Index2 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 AC 870P / Melody.

Table 1. General Tab Fields (Continued)

Field1 Description

Configuring Melody Executive Service Section 2 Base Configuration

48 3BDD011741-600 A

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 2 describes the columns in the information section.

Configuring Melody Executive ServiceThe Melody Executive Service is an 800xA System service that controls underlying Melody services running on Melody Configuration Server and Connectivity Servers (it starts and stops Configuration Server database replication and Melody OPC Servers). Once configured, it requires no further user interaction.

1. Open the Plant Explorer Service Structure and select Services and then select Melody Executive and choose Service.

2. Right-click Melody Executive choose Service and then select New Object from context menu.

Table 2. 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.

Log on once with the 800xA Service account on Melody Configuration Server and all the Melody Connectivity Servers.

Section 2 Base Configuration Configuring Access Rights

3BDD011741-600 A 49

3. Select Service Group and enter a name. Select the newly created Service Group in the tree.

4. Select Service Group Definition in the Aspect List Area.

5. Select the Configuration tab in the Preview Area (if not already selected) and then click Add to open the New Service Provider Name dialog box.

6. Enter the Service Provider name and then click OK.

7. Use the Object Browser to select the newly created Melody Executive Service Provider and select Service Provider Definition in the Aspect List Area.

8. Select the Current Node from the node drop-down list box in the Preview Area and then click Apply.

Configuring Access RightsAll System 800xA users require read access to the Configuration server and SQL Server databases for 800xA for AC 870P/Melody. To configure access rights for read access, perform the following steps on the 800xA for AC 870P/Melody Configuration Server. These steps can be repeated on each 800xA for AC 870P/Melody Connectivity Server after it receives a copy of the Configuration Server database (after the Melody Executive Service Provider is configured and started).

The Melody Tag Importer requires write access to the Configuration Server database on the 800xA for AC 870P/Melody Configuration Server node. The following steps can be used in a similar way to configure an Industrial IT administrator as db_datawriter for the Configuration Server database.

1. Start SQL Server Management Studio.

2. Connect to current node\MELODY_INSTANCE.

The steps need to be repeated for the Melody Configuration Server and all Melody Connectivity Servers. Start with the Configuration of the Configuration Server.

Configuring Access Rights Section 2 Base Configuration

50 3BDD011741-600 A

3. Expand the listing to view the Security\Logins in the Microsoft SQL Server Management Studio dialog box (Figure 19).

4. Select Logins and right-click to select New Login from the context menu.

5. Add the Industrial IT user group as the login name in the General page.

Figure 19. Microsoft SQL Server Management Studio Dialog Box

Section 2 Base Configuration Configuring Access Rights

3BDD011741-600 A 51

6. On the User Mapping page, select the db_datareader check box for the ConfigServer and model databases (Figure 20).

7. Click OK.

Figure 20. Selecting db_datareader for the ConfigServer and Model Databases

Settings Section 2 Base Configuration

52 3BDD011741-600 A

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

Configuration Server

Domain Name and Database Name are provided by the system as defined before.

As Machine Name the belonging Configuration Server has to be selected.

Figure 21. System Settings Aspect

It is possible to modify the Database Name but it is recommended to keep the default name.

Section 2 Base Configuration Options

3BDD011741-600 A 53

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.

Options Section 2 Base Configuration

54 3BDD011741-600 A

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

Figure 22. Adding the Faceplate Mapping Aspect


3BDD011741-600 A 55

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

If the Faceplate Mapping option is checked then 800xA for AC 870P / 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 AC 870P / 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.

Figure 23. Example for a Faceplate Mapping Table


56 3BDD011741-600 A

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:

1. Select the Faceplate mapping aspect for the tag.

2. Right mouse click to open Properties.

3. Select the Aspect Details tab.

4. Click Add.

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

6. Click Apply.

Figure 24. Avoiding Overriding of Specific Faceplates


3BDD011741-600 A 57

History Log Configuration:

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 AC 870P / 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 AC 870P / 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.

It is possible to add a Log Configuration aspect manually in 800xA to specific tags. These aspects must be protected from overriding by adding the aspect key Melody No Log Configuration Update.

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

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 25) 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.


58 3BDD011741-600 A

Using external archive

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

Figure 25. Archive Template Configuration in Composer

Section 2 Base Configuration Audit Trail

3BDD011741-600 A 59

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).

For detailed information about the archive configuration refer to the 800xA - Information Management, Configuration (3BUF001092*).

Audit Trail

The Configuration Manager of 800xA for AC 870P / 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.

Figure 26. Log Template Definition in 800xA Process Portal

Synchronizing Engineering Data Section 2 Base Configuration

60 3BDD011741-600 A

2. Click Apply.

Auto-Configurator User Account:

Enter the user account.

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 AC 870P / Melody.

All configuration changes related to the 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 AC 870P / Melody Config Server and 800xA Process Portal.

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*).

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.

Section 2 Base Configuration Configurator Admin

3BDD011741-600 A 61

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

1. Click Analyze.

2. Click Apply.

Figure 27. Configurator Admin Aspect

Auto Configurator Section 2 Base Configuration

62 3BDD011741-600 A

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

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, which 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.

Auto Configurator

It is possible to apply changes to the Controller and Config Server even if the Aspect Server is temporarily unavailable. After restart of the Aspect Server, 800xA for

Figure 28. Configurator Admin Aspect Options

For disconnected tags or duplicated tags the synchronizing functionality (Apply button) is not available.

Section 2 Base Configuration Auto Configurator

3BDD011741-600 A 63

Melody recognizes outstanding changes and automatically performs a complete synchronization.

Before you configure the Auto Configurator it is necessary to log in once with the 800xA service account on the node designated for running the service (ususal the primary 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.

Due to run time advantages it is recommended to use the Auto Configurator as standard for synchronization between Composer and the Aspect Server!

Figure 29. Selecting the SAC Data Source Aspect

Auto Configurator Section 2 Base Configuration

64 3BDD011741-600 A

As node select the primary aspect server

Click OK and then click Apply.

After the start the Auto-Configurator analyzes the data base wether full synchronization is necessary or not.

Figure 30. Selecting the Service Group

After the auto-configuration service has been started the progress can be followed up by the following messages sent as event for information:

- AC 870P / Melody auto-configuration service started full sync.

- AC 870P / Melody auto-configuration service finished full sync.Note: for very large-scaled systems full sync process may last up to 90 min.

- AC 870P / Melody auto-configuration service is ready for synchronization.

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.

The Auto-Configurator is not redundant. If the primary aspect server fails for a longer period of time, the Auto-Configurator service can be assigned to the secondary aspect server. The Auto-Configurator service can be found in Service Structure below the Server Aspect Controller node.

Section 2 Base Configuration OPC Data Source Definition

3BDD011741-600 A 65

OPC Data Source DefinitionThe 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.

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.

Figure 31. OPC Data Source Definition Aspect

The Data Key provided by the system must not be modified.

OPC Data Source Definition Section 2 Base Configuration

66 3BDD011741-600 A

3. Click New.

4. Click Add....

5. Select the Melody Connectivity Servers to be member of the newly created 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.

Figure 32. Assigning Connectivity Servers to a new Service Group

Redundant Connectivity Servers must be members of the same service group.

Section 2 Base Configuration Alarm and Event OPC Provider Setup

3BDD011741-600 A 67

The result of the OPC Data Source Definition are newly created objects in the Service Structure.

Alarm and Event OPC Provider SetupRefer also to the 800xA System Alarm & Event Users Configuration instruction for more information.

This requires the user to add the Melody OPC alarm server program ID to a Service Group under the Event Collector category in the Service Structure.

1. Open a Plant Explorer Workplace.

2. Use the Structure Selector to open the Service Structure.

3. Use the Object Browser to navigate to:Services > Event Collector, Service

Figure 33. Result of the OPC Data Source Definition

Alarm and Event OPC Provider Setup Section 2 Base Configuration

68 3BDD011741-600 A

4. Right-click on EventCollector Service and select New Object from the context menu that appears.

5. Select Service Group.

6. Enter a descriptive name such as Melody EventCollector in the Name field and select Create.

7. Select the Service Group Definition aspect in the Aspect List Area.

8. Select Add in the Preview Area to add a Service Provider for the Connectivity Server and enter a descriptive name such as: Melody_EventCollector_Provider_node,where node is the name of the Connectivity Server node.

9. Select OK.

10. Select Apply in the Service Group Definition aspect.

11. In the Providers list box, double-click the newly created EventCollector Service Provider.

12. The Service Provider Definition aspect should be displayed in the Preview Area. Select the name of the appropriate Connectivity Server from the Node drop-down list box and click Apply.

13. Close the Service Provider Definition dialog.

14. Repeat Step 7 through Step 13 to add and configure an Event Collector Service Provider for the redundant Connectivity Server if one exists.

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

16. Select Maestro/OPC EventServer [InProc] option in the Alarm Server configuration field.

17. Select Melody AE Server option in the Collection Definition configuration field if it is not already selected.

18. In the Source Object Handling field, select Tracking Source Object Interceptor from the Object Handler drop-down list box, select Melody AE Server: Source Object Interceptor Configuration from the Source Configuration drop-down list box and click Apply.

19. Use the Structure Selector to open the Service Structure.

Section 2 Base Configuration Adjust PNSM Configuration

3BDD011741-600 A 69

20. Use the Object Browser to navigate to:Services > Alarm Manager, Basic, Service Group

21. Select the Special Configuration tab in the Preview Area.

22. Disable the Make new alarm entry each time a condition gets active check box and click Apply.

Adjust PNSM ConfigurationThe Melody Connectivity Server nodes need a different PNSM configuration. The Melody specific configuration file can be found on the PSNM program folder SupportFiles and must be copied to:

Deselecting Make new alarm entry each time a condition gets active is a system wide setting. This is only a recommendation for 800xA for Melody. It may conflict with other applications.

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

Tag Importer Section 2 Base Configuration

70 3BDD011741-600 A

..\ABB Industrial IT\Optimize IT\PC, Network and Software Monitoring\bin

On each Melody Connectivity Server node:

1. Make a backup of the existing ABBShadowOPC.exe.config file.

2. Copy the file ABBShadowOPC.exe.config from SupportFiles to the bin folder.

3. If the PNSM service is already running, then restart the node and verify that the KeepAliveApp.exe is not in the list of processes.

Tag ImporterThe task of the Melody Tag Importer is the upload of configuration data from Composer to the 800xA for AC 870P / Melody Config Server.

Use the following step to run the Tag Importer for an automatic Composer upload:

1. Ensure that the Composer project uses the Melody share on the Config Server node as operations working directory

2. Login on Config Server node using an account with the right to write into the Config Server database

3. Start the file: \Program Files\ABB Industrial IT\Configuration\MelConverter.bat

4. The Tag Importer is running automatically as long as the user is logged in

It is also possible to use the Tag Importer for a manuel upload:

1. Login on Config Server node using an account with the right to write into the Config Server database

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

To have an easy access it is useful to place this file on the desktop

Section 2 Base Configuration Tag Importer

3BDD011741-600 A 71

Start > All Programs > ABB Industrial IT 800xA> 800xA for AC870P/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

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 ChangesControl Structure > Connect Configuration Aspect > Management Tab > Select “Synchronize data after each object update”.

7. When prompted for the type of restart (see Figure 35):

a. Check Restart the affected server(s)...

b. Check Restart Servers Manually

c. Click OK

In case of redundant Connectivity Servers restart the first and wait until this Connectivity Server is up again before restarting the second.

After the system operation has been normalized start Tag Importer.

Tag Importer Section 2 Base Configuration

72 3BDD011741-600 A

Figure 35. Restart Options

3BDD011741-600 A 73

Section 3 Topology

Control Network Redundancy

800xA for AC 870P / Melody supports server redundancy and network redundancy. The AC 870P or Melody control network is a standard industrial Ethernet network using standard components. Typically the redundant Control Network is a ring and one cut does not affect system availability. The principle is shown in Figure 36:

Applying this solution one failure does not cause a shutdown because the AC870P or Melody components might be redundant and the connectivity server might be

Figure 36. Example for a Redundant Network Structure

Operator Network Redundancy Section 3 Topology

74 3BDD011741-600 A

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.

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.

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

Section 3 Topology Topology Planning Software

3BDD011741-600 A 75

Topology Planning Software

Overview

Control Structure

Controller objects are placed in the Control Structure under an AC 870P / 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.

Figure 37. System Software Structures edited by 800xA for AC 870P / Melody

Topology Planning Software Section 3 Topology

76 3BDD011741-600 A

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.

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

Figure 38. Example for a Control Structure

Section 3 Topology Topology Planning Software

3BDD011741-600 A 77

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

Figure 39. Example of a Functional Structure

Base Topology Configuration Section 3 Topology

78 3BDD011741-600 A

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 40:

1. Select the Operators, User Group in the User Structure.

2. Right mouse click to enter the menu.

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

Section 3 Topology Creating a new Operator User

3BDD011741-600 A 79

3. Select New Object.

4. Select User in the Common tab.

5. Enter the operator user name as shown in the following Figure 41:

6. Click Next.

7. Select the domain/machine.

Figure 41. Entering User Name for new User

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*).

Creating a new Operator User Section 3 Topology

80 3BDD011741-600 A

Select the new user

8. Select the new user

9. Click Create.

Figure 42. Selecting the User

Section 3 Topology Creating a new Operator User

3BDD011741-600 A 81

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

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

Affinity Section 3 Topology

82 3BDD011741-600 A

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

2. Select new object via right mouse click

Figure 44. Affinity Definition

Section 3 Topology Affinity

3BDD011741-600 A 83

3. In the New Object window select Affinity and enter the Name as shown in Figure 45

4. Click Create.

Figure 45. Defining Affinity Name


84 3BDD011741-600 A

5. Select the Configuration Tab.

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

7. 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 46. Affinity Definition Aspect


3BDD011741-600 A 85

Figure 47:

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 47. 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.


86 3BDD011741-600 A

Figure 48:

9. To change the sequence of access Click up or down.

Figure 48. Adding Connectivity Servers to an even numbered Operator Workplace


3BDD011741-600 A 87

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

Figure 49. Affinity Definition Aspect - Affinity Summary Tab

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


88 3BDD011741-600 A

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

12. Click Apply.

Figure 50. Affinity Definition Aspect - Configuration Tab

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.

Section 3 Topology Control Structure Import

3BDD011741-600 A 89

Control Structure Import

During commissioning in Composer the Control Structure informations will be automatically created.

Manually export of the Control Structure information is only necessary if the ConfigServer is not available during commissioning. To achieve this:

1. Open the System Structure in running mode

2. Select the island or station

3. Click the right mouse button (context menu)

4. Select Export > Control Structure as shown in the following Figure 51.

Figure 51. 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 Settings -> Operations Tab -> Working Directory.

Control Structure Import Section 3 Topology

90 3BDD011741-600 A

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

To extend the Control Structure, select the desired AC 870P or Melody controller in the Control Structure. 800xA Control Structure will automatically be updated.

Figure 52. Control Structure Export Result

3BDD011741-600 A 91

Section 4 Engineering Workflow

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.

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 AC 870P / Melody life cycle model.

Bulk Data ManagementComposer 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

The engineering workflow always starts in Composer and ends up in 800xA Process Portal and the control system part.

Engineering activities in 800xA Process Portal colliding with AC 870P / Melody business rules in means of consistency and integrity will be rejected. The lifecycle of an AC 870P / Melody object starts and ends in Composer.

Bulk Data Management Section 4 Engineering Workflow

92 3BDD011741-600 A

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.

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

Section 4 Engineering Workflow Import/Export

3BDD011741-600 A 93

Import/ExportFrom a functional point of view Composer provides the import/export functionality. 800xA for AC 870P / 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 “AC 870P / Melody – Engineering Tool Composer, User Manual”, 2PAA101135

Alarms and Events Section 4 Engineering Workflow

94 3BDD011741-600 A

Alarms and EventsAlarm/Event typicals are predefined in the 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.

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.

Figure 54. Alarm and Event Typical in Composer

Section 4 Engineering Workflow Object Life Cycle

3BDD011741-600 A 95

Object Life CycleThe 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 ParametersAll parameters operated via the 800xA Operator Workplace are written down to the AC 870P / 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. The current settings can be manually reloaded by Composer into

Operating Parameters Section 4 Engineering Workflow

96 3BDD011741-600 A

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

Figure 55. Operating Parameters

3BDD011741-600 A 97

Section 5 System Definition

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.

System Definition ObjectEven though 800xA for AC 870P / Melody configuration data is maintained and organized in objects, there is data that does not belong to a single object, but affects

Figure 56. Connect Configuration Aspect

System Definition Object Section 5 System Definition

98 3BDD011741-600 A

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.

Only one system definition object can be configured in the project. Table 3 describes the system definition object properties.

The system definition object is not subject to life cycle management. All changes to information in this object are directed to the runtime system.

Table 3. System Definition Object Properties

Properties Description

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

Indexed Text Refer to Indexed Text Tab on page 99.

Substitutable Text Refer to Substitutable Text Tab on page 105.

Quality Text Refer to Quality Text Tab on page 106.

Management Refer to Management Tab on page 108

Project History Refer to Project History Tab on page 108.

Section 5 System Definition Configurable Text

3BDD011741-600 A 99

Configurable TextSome 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 57). The Indexed Text includes:

• Event Comment.

• Text Selector Text.

• Engineering Unit Descriptor.

• Logic State Descriptor.

• Alarm Priority Text.

Indexed Text Tab Section 5 System Definition

100 3BDD011741-600 A

• 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 57) beside these controls shows the record number that currently has cursor focus and the total number of records in the table.

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.

Figure 57. Indexed Text Tab

Section 5 System Definition Indexed Text Tab

3BDD011741-600 A 101

2. Enter the index number in the provided field.

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.

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. Figure 58 lists as an example engineering unit descriptors and their index numbers

This index number must be unique to the selected Server type.


102 3BDD011741-600 A

provided by Composer.

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.

Figure 58. Engineering Unit Descriptors (Example)

Section 5 System Definition Indexed Text Tab

3BDD011741-600 A 103

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 AC 870P / 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 4 lists the fixed logic state descriptors and their index numbers.

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 5.

Table 4. 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)

Only the default alarm priorities are available. No others can be added.


104 3BDD011741-600 A

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.

Table 5. 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 — —

Section 5 System Definition Substitutable Text Tab

3BDD011741-600 A 105

Substitutable Text Tab

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

To edit a text entry:

Figure 59. Melody System Events

Figure 60. Substitutable Text Tab

Quality Text Tab Section 5 System Definition

106 3BDD011741-600 A

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 TabThe Quality Text tab of the system definition object configures the OPC quality state indicators and the 800xA for AC 870P / Melody increasing and decreasing indicators (Figure 61). A quality indicator is shown in displays to indicate the quality of the tag and property providing values. The increasing and decreasing

Section 5 System Definition Quality Text Tab

3BDD011741-600 A 107

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. 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.

2. Click the Submit Changes button to save the new information.

Figure 61. Quality Text Tab

Changes to the quality text require a node restart to take affect.

Management Tab Section 5 System Definition

108 3BDD011741-600 A

Management TabThe management tab offers the possibility to enable the data synchronization immediately after each object update without system reboot (Figure 63). 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.

To enable data synchronization after each object update set the check box and answer the prompted question: “Enable data synchronization after each object update?” with yes.

Project History TabThe project history tab shows an audit of all the changes made to the configuration (Figure 63).

Figure 62. Management Tab

Figure 63. Project History Tab

3BDD011741-600 A 109

Section 6 Alarm and Event System

The 800xA for AC 870P / Melody event system is based on a Client/Server architecture. 800xA for AC 870P / 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.

Melody 800xA Process Portal Process Events Section 6 Alarm and Event System

110 3BDD011741-600 A

Melody 800xA Process Portal Process Events

Next table shows all possible Attributes with 800xA Process Portal Alarm Pages and AC 870P / Melody.

Table 6. 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 X

Object Description Saw tooth with offset

Message Description

Comment

ViolatedLimit 75.98 X

EngUnit 1/s X

Table 7. Possible Attributes with 800xA Process Portal Alarm Pages and Melody

AttributeExample Data

Example Data (Process Event)Vendor Melody

Ack State

Enable State Enabled

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

Ack Time xxxxxxxxxx

Section 6 Alarm and Event System Melody 800xA Process Portal Process Events

3BDD011741-600 A 111

Object Name FIC 0002

Description Saw tooth with offset X

State>Max1X

ConditionXH01

Sub Condition

Current Value

Priority Level 1

Priority 1000

Type PEX X

Object Description Saw tooth with offset

Category Limit Events

Component

Message Description

Comment

Actor

Auto Disabled

Severity 1000

Section

Class

Blocked Repetitive

Uncertain Time

Tag




Melody 800xA Process Portal Process Events Section 6 Alarm and Event System

112 3BDD011741-600 A

Audible Alarm

Printout Blocked

Guid 3377186754

Campaign ID

Batch ID

Lot ID

Unit ID

Recipe Path

ViolatedLimit 75.98 X

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-AE7A-46C6FD225B0D

X

InactiveTime X

InactiveTimePrecision 3 X




Section 6 Alarm and Event System Melody 800xA Process Portal System Events

3BDD011741-600 A 113

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.

Inhibited FALSE X

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

Table 8. Melody System Messages

Object Name

DescriptionConditi

onPriori

tyMessage

Description

ep064a09 Measured value(s) not actualized 1708/0 850 EP064A09, 1708

ep064a09 Connection to Profibus failed 9bc/3 1000 EP064A09, 9bc

ep064a09 Redundancy take over 2204/0 1000 EP064A09, 2204




Melody Message System Section 6 Alarm and Event System

114 3BDD011741-600 A

Melody Message SystemThis chapter describes the functionality of Melody Control related to Alarms and Events.

A Melody Coupling module can be of module type CCO30, CMC70 or PM875.

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 AC 870P / 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.

ep064a09 Redundancy communication disturbed

2206/0 900 EP064A09, 2206

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, 2208

ep064a09 Profibus: failure of a subscriber d810/a00

1000 EP064A09, 0, 10, DP0010

ep064a11 Measured value(s) not actualized 1708/0 850 EP064A11, 1708

Table 8. Melody System Messages

Object Name

DescriptionConditi

onPriori

tyMessage

Description

Section 6 Alarm and Event System Melody Message Transport and Buffering

3BDD011741-600 A 115

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

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 AC 870P / Melody Components.

Figure 64. Melody Message System Overview

Melody Message Transport and Buffering Section 6 Alarm and Event System

116 3BDD011741-600 A

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.

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

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.

Section 6 Alarm and Event System Melody Process Messages

3BDD011741-600 A 117

• 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:

Melody Process Messages Section 6 Alarm and Event System

118 3BDD011741-600 A

Table 9. Message Parameters

Message Selector

Meaning Remarks

MGEN (Bool)

Message generation 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)

Section 6 Alarm and Event System System and Process Interface Messages

3BDD011741-600 A 119

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.

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.

LOGIC (Bool)

Message logic 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.

Table 10. Total No. of Configurable Process Messages

Coupling module Max.No. of Process Messages

CMC70/PM875 60,000

CCO30 22,500

Table 9. Message Parameters

Message Selector

Meaning Remarks

Alarm & Event System Definitions and Overview Section 6 Alarm and Event System

120 3BDD011741-600 A

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 OverviewEvents 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 65 is a functional diagram of the 800xA for Melody event system.

Figure 65. 800xA for AC 870P / Melody Event System

T04056B

E V EN TD IS TR IBU T IO N

E V EN T S TR E A ME V EN T S TR E A M

E VE N T S TR E AM

O PCAE SE RV E R

S ERV E R SM A IN TAIN IN G

E VE N T P O IN TS A N DG EN ER ATIN G E V EN TS

SE RV ER SM AIN TA IN IN G

E VE N T P O IN TS A N DG E N E R ATIN G E V EN TS

S ERV E R SM AIN TA IN IN G

E VE N T P O IN TS A N DG EN ER ATIN G E V EN TS

Section 6 Alarm and Event System Alarms and Events

3BDD011741-600 A 121

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 AC 870P / Melody similar to the implementation of the abstract OPC condition model.

Event Distribution System Section 6 Alarm and Event System

122 3BDD011741-600 A

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.

Section 6 Alarm and Event System Event Classifications

3BDD011741-600 A 123

A local event concentrator needs to be configured for all nodes in the system that 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 AC 870P / 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.

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:

Client event concentrators have the ability of using a filter. For 800xA for Melody it is recommended not to use filtering.

Event Point Definition Section 6 Alarm and Event System

124 3BDD011741-600 A

• Boolean.

• Limit.

• Deviation.

• Rate.

Event Point DefinitionIn 800xA for AC 870P / 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 AC 870P / 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 11 and Table 12 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

Section 6 Alarm and Event System Event Point Attributes

3BDD011741-600 A 125

identifies if the attribute is accessible as an property in case the event point exists as part of a tag instance.

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.

Table 11. Event Point Identification

Attribute Description ConfigProperty

Source 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.

Yes Yes2

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.

The signal name in combination with the sender name uniquely identifies the event point: <Source>.<SignalName>.

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:

<Source>.<ALI>

Class1 No

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.

Event Point Attributes Section 6 Alarm and Event System

126 3BDD011741-600 A

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

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

Figure 66. Control Connection Definition of an Event

Section 6 Alarm and Event System Event Point Attributes

3BDD011741-600 A 127

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

EPSCAT: Melody only handles only LL and HH.

Figure 67. Overview of Event Point Configuration

Table 12. Event Point State


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

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

Class1 Yes

Behavioral Attributes Section 6 Alarm and Event System

128 3BDD011741-600 A

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 13.

UNACKEP 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 or COM1 dependent on the active state of the event point.

No Yes

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

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

No Yes

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

Table 12. Event Point State (Continued)


Section 6 Alarm and Event System Informational Attributes

3BDD011741-600 A 129

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 14.

Table 13. Behavioral Attributes

Attribute Description Config Property

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

Yes Yes

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.

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 inactive state. A non dual event point will only generate an event upon transition into active state.

Composer Configuration

Yes Yes

COMP Not implemented — —

The list in Table 14 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.

Informational Attributes Section 6 Alarm and Event System

130 3BDD011741-600 A

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 14. 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 <source>.<ALI>

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 point. Usually this attribute is defined through configuration.

Yes 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).

Note: Active event (PRI0)and inactive event (return to normal event) have the same priority (PRI0 = PRI1).

Yes Yes

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

Section 6 Alarm and Event System Event Point State Attributes

3BDD011741-600 A 131

Event Point State Attributes

Event points have several boolean state attributes. They are:

• Acknowledged.

• Active.

• Enabled.

• 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 68 describes the event point acknowledgement flow. 800xA for AC 870P / 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 State Attributes Section 6 Alarm and Event System

132 3BDD011741-600 A

Event Point Acknowledgment

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

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

AC 870P / Melody tags can be inhibited. Either via Faceplate or OPC Property. Means that all Event Points belong to the Tag will be disabled.

Figure 68. Event Point Acknowledgment Flow

T04058A

IN AC TIV E ,AC KE D

VA LIDAC KN OW LE D G M EN T

VA LIDAC K N OW LED G M E N T

BE C O M E SIN AC TIV E

BE C O M E SAC TIV E

BE C O M E SIN AC TIV E

E N A B LE D,U N SU P P R E SS E D

AC TIV E ,U N AC K ED

IN AC TIV E ,U N AC K ED

AC TIV E ,AC KE D

Section 6 Alarm and Event System Dual Event Point Behavior

3BDD011741-600 A 133

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 68.

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.

Redundancy Section 6 Alarm and Event System

134 3BDD011741-600 A

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

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.

Figure 69. Redundant AE System with Event Concentrators

Section 6 Alarm and Event System Severity, OPC Severity and Device Priority

3BDD011741-600 A 135

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 PriorityThe 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.

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.

The priority mapping has to be harmonized with Faceplates and Graphics to have the OPC alarms fitted. (texts, priority, colors).

Device Severity (Melody Priorities) Section 6 Alarm and Event System

136 3BDD011741-600 A

For example, a client wishing to present five severity levels to a user should be able to do the following mapping:

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 15. Client Severity Mapping

Client Severity OPC Severity

HIGH 801 - 1000

MEDIUM HIGH 601 - 800

MEDIUM 401 - 600

MEDIUM LOW 201 - 400

LOW 1 - 200

Table 16. Priority Mapping

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

Section 6 Alarm and Event System Device Severity (Melody Priorities)

3BDD011741-600 A 137

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.

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

Table 16. Priority Mapping

Melody Priority OPC AE Severity Process Portal Priority

Device Severity (Melody Priorities) Section 6 Alarm and Event System

138 3BDD011741-600 A

3BDD011741-600 A 139

Section 7 Time Synchronization

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 AC 870P / 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 AC 870P / 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 AC 870P / 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.

Operation Overview Section 7 Time Synchronization

140 3BDD011741-600 A

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

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 AC 870P / Melody software (Connectivity Server). By default the Time Server is installed on all System Product server nodes.

Figure 70. Synchronization Direction

Section 7 Time Synchronization Time Adjustment

3BDD011741-600 A 141

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.

800xA Process Portal Time Server Configuration Section 7 Time Synchronization

142 3BDD011741-600 A

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.

Any service providers added for nodes that do not have 800xA for AC 870P / 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).

Figure 71. Time Server Service Provider Configuration

Section 7 Time Synchronization 800xA Process Portal Time Server Client Configuration

3BDD011741-600 A 143

800xA Process Portal Time Server Client 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 > <ComputerName>, Node.

Figure 72. Time Server Client Aspect Configuration

Windows Time Synchronization Service (W32Time) Section 7 Time Synchronization

144 3BDD011741-600 A

For the configuration settings refer to the following Table 17:

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!

Computer that neither belong to Melody nor to the 800xA Process Portal but that need a time synchronization must use the SNTP protocol. Refer to System 800xA Network Configuration (3BSE034463*).

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.

Table 17. Time Server Client 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.

During the installation of 800xA for AC 870P / Melody the Windows Time Synchronization Service “W32Time” will be automatically disabled on the Connectivity Server.

The Windows Time Synchronization Service must remain disabled, with the exception of the (redundant pair of) 800xA for AC 870P / Melody Connectivity Server that does the time synchronization.

Section 7 Time Synchronization Master Clock Configuration in Melody

3BDD011741-600 A 145

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.

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 ’Summer time’ (Daylight Saving Time). The Melody Controller module can be connected to a radio controlled clock.

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 AC 870P / Melody Analyzer (see Configuration Check with AC 870P / Melody Analyzer).

Figure 73. Melody Master Clock Configuration

Configuration of Melody Server as Time Master Section 7 Time Synchronization

146 3BDD011741-600 A

Configuration of Melody Server as Time Master

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 TimeSync Configuration Tool allows:

• To change the Network Interface IP address of the network interface for the Primary Client/Server Network (not for the Onet). This interface is responsible for time synchronization and

• To set the Network Priority

Start > All Programs > ABB Industrial IT 800xA > 800xA for AC 870P / Melody > Diagnostics > TimeSync Configuration

The following settings regarding Network Priority have to be done. .

The Time Synchronization Daemon is installed on each Melody Connectivity Server as service.

Figure 74. Time Synchronization Options

Table 18. Settings for the Melody Time Master Server

Primary Connectivity Server Network Priority = 10

Redundant Connectivity Server Network Priority = 9

Section 7 Time Synchronization Deleting all Services that are not Time Master

3BDD011741-600 A 147

Deleting all Services that are not Time Master

During installation 800xA Process Portal activates Time Server Groups on all server nodes by default.

The following Figure 75 shows how to find out the Connectivity Server that works as Time Master.

After failure of the primary Client/Server network the time synchronization is interrupted. The disturbance has to be eliminated as soon as possible to achive the time synchronization with AC 870P / Melody again.

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.

Figure 75. Indicating Connectivity Servers Working as Time Master

Melody TimeSync Daemon installation Section 7 Time Synchronization

148 3BDD011741-600 A

Note: In the example the pair of redundant Connectivity Server MELCON77 and MELCON78 are working as Time Master.

Melody TimeSync Daemon 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 use the SNTP protocol.

For settings referring to the SNTP protocol follow the System 800xA Network Configuration (3BSE034463*).

DHCP Configuration for Time Synchronization

The Melody CCO / CMC / PM875 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.

The final configuration of the Melody module has to be checked by using the diagnostic tool AC 870P / Melody Analyzer (see “Checking the Configuration with AC 870P / Melody Analyzer”).

For Melody Connectivity Servers and for the Melody Config Server the TimeSync Daemon is automatically installed during installation.

Figure 76. DHCP Configuration for Transmission of Time Synchronization

Section 7 Time Synchronization Checking the Configuration with AC 870P/Melody Analyzer

3BDD011741-600 A 149

Checking the Configuration with AC 870P/Melody Analyzer

The final configuration of the Melody module concerning Master clock and time gateway setting has to be checked by using the diagnostic tool AC 870P / Melody Analyzer (for details see also manual AC 870P / Melody - Analyzer, 2PAA101136).

Checking the Master Time Daemon with TsyncCTRL Tool

The Master Time Daemon service is part of the 800xA for AC 870P / 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.

Figure 77. Configuration Check with AC 870P / Melody Analyzer

Melody Server SYSLOG Time Synchronization Diagnostic Section 7 Time Synchronization

150 3BDD011741-600 A

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

Melody Server SYSLOG Time Synchronization Diagnostic

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

Figure 78. Time Sync Daemon Restart

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.

Section 7 Time Synchronization Melody Server SYSLOG Time Synchronization Diagnostic

3BDD011741-600 A 151

IT\Base\SysLogModify.exe”. The Melody log file “..\Operate IT\Base\syslog.log” contains the data.

Figure 79. Time Synchronization Debug Traces for Melody Server

Melody Server SYSLOG Time Synchronization Diagnostic Section 7 Time Synchronization

152 3BDD011741-600 A

3BDD011741-600 A 153

Section 8 Backup and Restore

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 Server Operating System 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 OPPAAdmin Account for this product.

AccessThis feature is accessed through Start > (All) Programs > ABB Industrial IT 800xA > 800xA for AC 870P / Melody > Configuration on the ConfigServer node.

FunctionThe 800xA for AC 870P / 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 AC 870P / Melody configuration contained in its SQL

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

Backup Industrial IT Melody Composer Section 8 Backup and Restore

154 3BDD011741-600 A

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.

Backup Industrial IT Melody ComposerThe Composer backup and restore procedure is described in the manual Engineering for AC 870P / Melody – Composer, Installation (2PAA100254*).

Backup ConfigServer

Backup Configuration

Use the following procedure to save 800xA for AC 870P / Melody information:

1. Log in to the PPAAdmin account on the Config Server node.

2. Use the 800xA for AC 870P / 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 AC 870P / Melody > Configuration > Backup Configuration

For support during the ConfigServer backup the Microsoft SQL-Server online help is also available.

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!

Section 8 Backup and Restore Restore ConfigServer

3BDD011741-600 A 155

b. Click Connect in the 800xA for AC 870P / Melody Configuration Backup/Restore window.

c. Click Backup.

d. Click Exit when the backup is complete.

Restore ConfigServerUse the following procedure to restore existing 800xA for AC 870P / Melody ConfigServer information:

1. Log in PPAAdmin account on the ConfigServer node.

2. Use the 800xA for AC 870P / 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 AC 870P / Melody > Configuration > Restore Configuration

This initiates the connection to the configuration database using the current Server Operating System account security. This account must have Administrative access to the system and ConfigServer database.

The file name is auto generated using the ConfigServer name, date and time.

Example: ConfigServer_20020521_1034.bak

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!

Restore ConfigServer Section 8 Backup and Restore

156 3BDD011741-600 A

b. Click Connect in the 800xA for AC 870P / Melody Configuration Backup/Restore window.

c. Enter the name of the 800xA for AC 870P / Melody Config Server database backup file in the Backup File field.

d. Click Restore.

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

f. Click Exit when the restore operation is complete.

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.

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.

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.

After restoring a ConfigServer restart all Config Server and 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.

3BDD011741-600 A 157

Section 9 Melody Automation Classes

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 AC 870P / Melody - Operation (Utility)

• IIT 800xA - System, 800xA for AC 870P / Melody - Operation (Process Industry)

AC 870P / Melody Composer does not provide the following function block modules with Operation Code Generation, so do not use them:

• BFLAG-H0

• CSCBOOL-00

• CSCCL-00

• CSCDUR-00

• CSCINT-00

• CSCPB-00

• CSCREAL-00

MelodyAnalog – Analog monitoring Section 9 Melody Automation Classes

158 3BDD011741-600 A

MelodyAnalog – Analog monitoring

Features

The analog monitoring (MelodyAnalog) automation classes allow a freely-configurable analog monitoring function from AC 870P / 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 AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.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 manual AC 870P / Melody – Engineering Tool Composer, Operation (2PAA101133*).

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 AC 870P / 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 AC 870P / Melody and 800xA Process Portal, the function block connections on the monitoring function block must be connected to the function blocks in AC 870P / Melody.

Section 9 Melody Automation Classes Configuration

3BDD011741-600 A 159

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

CSCANA3

alw = AlwaysSignal is always/must always be connected.

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

opt = OptionalSignal is only created if the function block connection in Composer is connected and explicitly opened in alphanumeric format.

Configuration Section 9 Melody Automation Classes

160 3BDD011741-600 A

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.


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 references (RX1 … RX3), functional relationships for process control by the operator can be edited (signpost to another function). Used e. g. for MvN selection.


3BDD011741-600 A 161


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.

Event typical

The signaling 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)

Automation class Section 9 Melody Automation Classes

162 3BDD011741-600 A

• 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.

Automation class

Structure

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

Atom DescriptionOPC data type

Melodydata type

MelodyI/O

Read WriteWriteaccess

X1 Real input Double (w)

Real I X

X1/ALARM

Bool

X1/UNACK

Bool

X1V1 Limit signal 1 for X1

Bool Extended Boolean

I X

X1X1 Limit value 1 for X1 (actual)

Double (w)

X High limits

YX11 Limit value 1 for X1

Double (w)

Real O X Computer mode

Section 9 Melody Automation Classes Automation class

3BDD011741-600 A 163



I X


Double (w)

X High limits


Double (w)




I X


Double (w)

X High limits


Double (w)




I X


Double (w)

X High limits

YX14 Limit value 4 Double (w)




I X


Double (w)

X Low limits





I X


Double (w)

X Low limits


Melodydata type

MelodyI/O



164 3BDD011741-600 A





I X


Double (w)

X Low limits





I X


Double (w)

X Low limits



RX1 Reference to 1st analog value

Double ATOMREF

RX2 Reference to 2nd analog value

Double ATOMREF

RX3 Reference to 3rd analog value

Double ATOMREF

RX4 Reference to 4th analog value

Double ATOMREF

X2 Real input Double Real I X




Melodydata type

MelodyI/O



3BDD011741-600 A 165

Legend for columns:

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.

I1 Boolean input Bool Extended Boolean

I X


I X


I X


I X

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.

Atom: Description: Processing standard:

<Tag>.BAD/SIG

Quality of process signals transmitted

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


Melodydata type

MelodyI/O


MelodyAnMon – Analog monitoring Section 9 Melody Automation Classes

166 3BDD011741-600 A

MelodyAnMon – Analog monitoring

Features

The analog monitoring (MelodyAnMon) automation class allows the pre-configured analog monitoring function from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The pre-configured automation function in AC 870P / 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 AC 870P / 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

<Tag>.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)

<Tag>.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)

<Tag>.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)

<Tag>.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)


3BDD011741-600 A 167

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 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 AC 870P / Melody function block identify input and output signals in AC 870P / Melody.Data is exchanged between AC 870P / Melody and 800xA Process Portal, through the internal connections of the Melody function block with a monitoring block inside the yellow backed case.

ANMONB ANMONS


168 3BDD011741-600 A

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

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

Event typical

The signaling 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:


ANMONM ANMONL





3BDD011741-600 A 169





• Signal can be inhibited (Inhib) #


• 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 signaling 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 signaling behavior of precisely one binary signal.Event typicals for Packed Boolean signals define the signaling 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.


170 3BDD011741-600 A

Structure of an event typical, using the example of VAM1. The signaling behavior can be adjusted on a project-specific basis.

Event typical VAM1

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 sub-variant (e. g. ANMON_1) referred to by the event typical. The sub-variant is stored in the Importer for 800xA Process Portal).

NameBrief Desc.

Explanatory text

VAM1 VAM1 ANMON XSTA with events

PROF Packed Boolean sub-variant

0 ANMON_1

MIdx Csel Prio SGen Al PAck Dual Inhib Supp Logic

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


3BDD011741-600 A 171

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

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


172 3BDD011741-600 A

Automation class

Structure

The following table describes the structure of the automation class for the MelodyAnMon analog monitoring function.

Table: Structure of the MelodyAnMon automation class

Atom DescriptionOPC data

type

Melodydata type

MelodyI/O

Read WriteWrite

access

XSTA Actual value status

Integer Packed Boolean

I X

SUS Alternative value trigger active

Bool

SUO Alternative value active

Bool (w) X Lock operator access

ATO Alternative value set


ATOR Reset alternative value


BFO Switching impulse filter active

Bool

AKO Access locked Bool (w) X Lock operator access

AKOR Reset operator access lock


HVO H limit reached Bool

LVO L limit reached Bool


3BDD011741-600 A 173

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

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 X Computer mode

Y Real output Double Real I X

Y/ALARM Bool

Y/UNACK Bool

XRY Non-linearised value

Double (w)

Real I X X Setpoint control

ATV Alternative value Double (w)


XSUY Alternative value Double Real I X

WY Setpoint Double (w)

Real I X X Setpoint control


174 3BDD011741-600 A

W External setpoint Double (w)


AHHY HH limit signal Bool Packed Boolean

I X

AHHX HH limit value (actual)

Double (w)

X High limits priority

AHHV HH limit value Double (w)


AHY HH limit signal Bool Packed Boolean

I X

AHX H limit value (actual)

Double (w)

X High limits

AHV H limit value Double (w)


ALLY LL limit signal Bool Packed Boolean

I X

ALLX LL limit value (actual)

Double (w)

X Low limits priority

ALLV LL limit value Double (w)


ALY L limit signal Bool Packed Boolean

I X

ALX L limit value (actual)

Double (w)

X Low limits

ALV L limit value Double (w)


AHDY H tolerance signal

Bool Packed Boolean

I X

AHDX H tolerance value (actual)

Double (w)


AHDV H tolerance value Double (w)


ALDY L tolerance signal Bool Packed Boolean

I X

ALDX L tolerance value (actual)

Double (w)



3BDD011741-600 A 175

ALDV L tolerance value Double (w)


AHTY H transient signal Bool Packed Boolean

I X

AHTX H transient value (actual)

Double (w)


AHTV H transient value Double (w)


ALTY L transient signal Bool Packed Boolean

I X

ALTX L transient value (actual)

Double (w)


ALTV L transient value Double (w)


RX1 Reference to process signal 1

Double


Double


Double


Double






I X


I X


176 3BDD011741-600 A

Legend for columns:

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 AC 870P / Melody. The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.

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


I X


I X

Atom Atom name






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


800xA Process Portal: commands

Melody control code:

Effect:

AKO/SIG 01800080H Set general operator input inhibit

AKOR/SIG 01800100H Reset general operator input inhibit

SUO/SIG 40004000H Reset the alternative value


3BDD011741-600 A 177

ATO/SIG 40034001H Switch to alternative value

ATOR/SIG 40034002H Switch from alternative value to input variable X


178 3BDD011741-600 A

Calculated atoms



<Tag>.BAD/SIG Quality of process signals transmitted

OR (XSTA/SIG, Y/SIG, XRY/SIG, XSUY/SIG, WY/SIG, 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)


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)


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)

<Tag>.Y/ALARM Limit value violation with alarm signal pending

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

<Tag>.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)

Section 9 Melody Automation Classes Melody AnOut – Analog output

3BDD011741-600 A 179

Melody AnOut – Analog output

Features

The analog output (MelodyAnOut) automation class allows the pre-configured analog output function from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The pre-configured automation function in AC 870P / 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 AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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 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 AC 870P / Melody function block identify input and output signals in AC 870P / Melody.Data is exchanged between AC 870P / Melody and 800xA Process Portal, through


180 3BDD011741-600 A

the internal connections of the AC 870P / Melody function block with a monitoring block inside the yellow backed case.



Event typical


The following configuration data is defined as part of an event typical,:


YS-00 YL-00





3BDD011741-600 A 181











$) Only defined for event typicals for Packed Boolean signals.

For the configuration of signaling 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 signaling behavior of precisely one binary signal.Event typicals for Packed Boolean signals define the signaling 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.


182 3BDD011741-600 A

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

Table: Event typical VYM1

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 sub-variant (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

NameBrief desc.

Explanatory text

VYM1 VYM1 Analog output XSTA with events


0 ANOUT_1


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


3BDD011741-600 A 183

Automation class

Structure

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

Table: Structure of the MelodyAnOut automation class

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)

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


Melodydata type

MelodyI/O



Integer (w) Packed Boolean

I X


Bool


184 3BDD011741-600 A



ATO Set alternative value





Bool







Bool


AHN No H limit Bool

ALN No L limit Bool








O X Computer mode

Y Real output Double Real I X


3BDD011741-600 A 185

Y/ALARM Bool

Y/UNACK Bool


Double (w) Real I X X Setpoint control

ATV Alternative value Double (w) Real O X Computer mode


AHHY HH limit signal Bool Packed Boolean

I X


Double (w) X High limits priority

AHHV HH limit value Double (w) Real O X Computer mode

AHY HH limit signal Bool Packed Boolean

I X


Double (w) X High limits

AHV H limit value Double (w) Real O X Computer mode

ALLY LL limit signal Bool Packed Boolean

I X


Double (w) X Low limits priority

ALLV LL limit value Double (w) Real O X Computer mode

ALY L limit signal Bool Packed Boolean

I X


Double (w) X Low limits

ALV L limit value Double (w) Real O X Computer mode


ATOMREF


186 3BDD011741-600 A

Legend for columns:

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


ATOMREF


ATOMREF


ATOMREF


I X


I X


I X


I X

Atom Atom name








Section 9 Melody Automation Classes Melody APID controller

3BDD011741-600 A 187

function in AC 870P / Melody. The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.


Melody APID controller

Features

The controller (MelodyAPID) automation class allows the pre-configured PID controller function from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The pre-configured automation function in AC 870P / Melody has an operating mode memory, as well as X/W/Y handling and a timer function.


Configuration

The MelodyAnAPID automation class displays the controller function from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / Melody connection components.

Operate IT Process Portalcommands

Melody control code

Effect:



SUO/SIG 40004000H Reset the alternative value




188 3BDD011741-600 A

The configuration data can be tailored to meet the requirements of the operator in the tag configuration screens in 800xA Process Portal.



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 AC 870P / Melody function block identify input and output signals in AC 870P / Melody.Data is exchanged between AC 870P / Melody and 800xA Process Portal, through


3BDD011741-600 A 189

the internal connections of the AC 870P / Melody function block with a monitoring block inside the yellow backed case.

APIDS-00 APIDM-00


190 3BDD011741-600 A

APIDL-00


3BDD011741-600 A 191



Event typical

















192 3BDD011741-600 A



For the configuration of signaling 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 signaling behavior of precisely one binary signal.Event typicals for Packed Boolean signals define the signaling 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 signaling behavior can be adjusted on a project-specific basis.

Table: Event typical VCX1

NameBrief Desc.

Explanatory text

VCX1 VCX1 APID controller XSTA with events


0 APID_1


110 SUO 10


3BDD011741-600 A 193

Table: Event typical VCY1

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

NameBrief Desc.

Explanatory text

VCY1 VCY1 APID controller YSTA with events


0 APID_3


140 AKO 9

141 LKO 9

142 MAN 9

143 AUT 9

144 COMP 9

145 DDC 9

146 LOCO 9

147 MIO 9

148 AIO 9

149 CIO 9

150 YFSO 2


194 3BDD011741-600 A

Table: Event typical VCW1

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

NameBrief Desc.

Explanatory text

VCW1 VCW1 APID controller WSTA with events


0 APID_2


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


3BDD011741-600 A 195

Table: Event typical VCT1

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

NameBrief Desc.

Explanatory text

VCT1 VCT1 APID controller TSTA with events


0 APID_4


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


196 3BDD011741-600 A

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 sub-variant (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.

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

174 DINO 11

175 DDNO 11


SUS SUS

SUO SUO Sv Act (Sv Act)


BFO BFO


HVO HVO MsgMax (MsgMax)

LVO LVO MsgMin (MsgMin)

TRO TRO MsgTrans (MsgTrans)

RDO RDO



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)


3BDD011741-600 A 197


ALTN ALTN ALT Sup (ALT Sup)

AHHO AHHO

AHO AHO

ALO ALO

ALLO ALLO

AHDO AHDO

ALDO ALDO

AHTO AHTO

ALTO ALTO

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 WEFOONEWWI ONEWWIWTXO WTXOWBO WBOWTO WTO WN Act (WN Act)INTW INTWEXTW EXTWSPC 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


198 3BDD011741-600 A


WRE WRE W GL Rdy (W GL Rdy)WSVO WSVOWNO 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)

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 SPCCLOCO LOCO Loc Msg (Loc Msg)MIO MIO LockM M (LockM M)AIO AIO LockA M (LockA M)CIO CIO LockC M (LockC M)OVO OVOYFSO YFSO PSO Act (PSO Act)TFA TFAYBO YBOEBO EBOYHO YHO Y MaxMsg (Y MaxMsg)YHE YHE YLimHRdy (YLimHRdy)YLO YLO Y MinMsg (Y MinMsg)YLE YLE YLimLRdy (YLimLRdy)


3BDD011741-600 A 199


YRO YROYRE YRE Y GL Rdy (Y GL Rdy)YSVO YSVOYNO 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)


ARHA ARHA

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 TFNO Intv TF (Intv TF)

KCNO KCNO SOK KP M (SOK KP M)

PNO PNO P SO Act (P SO Act)


200 3BDD011741-600 A

Automation class

Structure

The following table describes the structure of the automation class for the MelodyAPID controller function.

Table: Structure of the MelodyAPID automation class

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)


Melodydata type

MelodyI/O




I X

WSTA Setpoint status Integer (w) Packed Boolean

I X

YSTA control variable status


I X

TSTA Timer function status


I X


Bool






3BDD011741-600 A 201


BoolW X Lock operator access


Bool



BoolW X Lock operator access



TRO Transient violation

Bool


Bool


AHN No H limit Bool

ALN No L limit Bool


AHDN No H tolerance Bool

ALDN No L tolerance Bool

AHTN No H transient Bool

ALTN No L transient Bool





AHDO H tolerance active

Bool

ALDO L tolerance active Bool

AHTO H transient active Bool


202 3BDD011741-600 A

ALTO L transient active Bool

INT INT operating mode

Bool (w) X Operator mode

EXT EXT operating mode


IIO INT locked Bool

EIO EXT locked Bool

WEFO Wext switching impulse filter active

Bool

ONEWWI New value from operator

Bool

WTXO Adjustment to X active

Bool

WBO Adjustment requirement from W

Bool

WTO Adjustment active Bool

INTW INT active Bool

EXTW EXT active Bool

SPC SPC operating mode

Bool

CAS Yaut and Wext (cascade) operating mode


AUTI Yaut and Wext operating 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


3BDD011741-600 A 203

WRE Gradient limit released

Bool

WSVO Alternative value active

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

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


204 3BDD011741-600 A

LOCO Local action Bool

LKOS Operating mode S/O lock

BoolW X Lock operator mode

LKOR Operating mode S/O release


MIO MAN locked Bool

AIO AUT locked Bool

CIO DDC locked Bool

OVO Override active Bool

YFSO Compulsory disconnection

Bool (w) X Computer mode

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 Alternative value active

Bool

YNO Control action Bool

YNVO External alternative Y value active

Bool

YNHO Keep last Y value Bool


3BDD011741-600 A 205

YN+O Stop direction + 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. H limit active

Bool

ARLA Timer function dyn. L limit active

Bool

ARVA Timer function dyn. limit active

Bool

ARHN Timer function dyn. H limit new

Bool

ARLN Timer function dyn. L limit new

Bool

ARVN Timer function dyn. limit new

Bool

ARH Timer function dyn. H limit

Bool

ARL Timer function dyn. L limit

Bool

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


206 3BDD011741-600 A

TFNO Timer function active

Bool

KCNO No Kp compensation

Bool

PNO P component disconnected

Bool

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



O X Computer mode



XAY Current process value

Double Real I X

XAY/ALARM

Bool

XAY/UNACK

Bool




3BDD011741-600 A 207

AHHY HH limit signal Bool Extended Boolean

I X




AHY HH limit signal Bool Extended Boolean

I X




ALLY LL limit signal Bool Extended Boolean

I X



ALLV LL limit value Double (w) Real O X Computer mode

ALY L limit signal Bool Extended Boolean

I X


Double (w) X Low limits

ALV L limit value Double (w) Real O X Computer mode

AHDY H tolerance signal


I X

AHDX HD limit value (actual)


AHDV H tolerance value Double (w) Real O X Computer mode

ALDY L tolerance signal Bool Extended Boolean

I X

ALDX LD limit value (actual)


ALDV L tolerance value Double (w) Real O X Computer mode


208 3BDD011741-600 A

AHTY H transient signal Bool Extended Boolean

I X

AHTX HT limit value (actual)


AHTV H transient value Double (w) Real O X Computer mode

ALTY L transient signal Bool Extended Boolean

I X

ALTX LT limit value (actual)


ALTV L transient value Double (w) Real O X Computer mode

WAY Current setpoint Double Real I X

WHY Current H limit Double (w) Real I X X Tuning

WHV H limit value Double (w) Real O X Computer mode

WLY Current L limit Double (w) Real I X X Tuning

WLV L limit value Double (w) Real O X Computer mode

WOY Current operator setpoint


WOV Operator setpoint Double (w) Real O X Computer mode

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 X Tuning

WCV Setpoint offset Wext

Double (w) Real O X Computer mode

WEY Evaluated setpoint Wext

Double Real I X


3BDD011741-600 A 209

WKAY Current Wext ratio

Double Real I X

WKY Ratio factor for Wext


WKV Ratio factor for Wext


WKFY Evaluated ratio for Wext.

Double Real I X

YAY Current controller output


YAY/ALARM

Bool

YAY/UNACK

Bool

YOV Operator control variable


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

TYOV Operating point Double (w) Real O X Computer mode

DEVY Control deviation Double Real I X

ARBY End position of ARW range


ARB End position of ARW range


KPY Proportional gain Double (w) Real I X X Tuning


210 3BDD011741-600 A

KP Proportional gain Double (w) Real O X Computer mode

VDY Derivative action gain


VD Derivative action gain


VD+Y Derivative action gain +


VD+ Derivative action gain + (setpoint)


VD-Y Derivative action gain –


VD- Derivative action gain – (setpoint)


WR+Y Gradient limit value +

Duration (w)

Short duration

I X X Tuning

WRT+ Gradient limit value + (setpoint)

Duration (w)

Short duration

O X Computer mode

WR-Y Gradient limit value –

Duration (w)

Short duration

I X X Tuning

WRT- Gradient limit value – (setpoint)

Duration (w)

Short duration

O X Computer mode

YR+Y Gradient limit value +

Duration (w)

Short duration

I X X Tuning

YRT+ Gradient limit value + (setpoint)

Duration (w)

Short duration

O X Computer mode

YR-Y Gradient limit value –

Duration (w)

Short duration

I X X Tuning

YRT- Gradient limit value – (setpoint)

Duration (w)

Short duration

O X Computer mode

TIY Integration time Duration (w)

Short duration

I X X Tuning

TI Integration time Duration (w)

Short duration

O X Computer mode

TI+Y Integration time + Duration (w)

Short duration

I X X Tuning


3BDD011741-600 A 211

TI+ Integration time + (setpoint)

Duration (w)

Short duration

O X Computer mode

TI-Y Integration time – Duration (w)

Short duration

I X X Tuning

TI- Integration time – (setpoint)

Duration (w)

Short duration

O X Computer mode

TDY Recovery time Duration (w)

Short duration

I X X Tuning

TD Recovery time Duration (w)

Short duration

O X Computer mode

TD+Y Recovery time + Duration (w)

Short duration

I X X Tuning

TD+ Recovery time + (setpoint)

Duration (w)

Short duration

O X Computer mode

TD-Y Recovery time – Duration (w)

Short duration

I X X Tuning

TD- Recovery time – (setpoint)

Duration (w)

Short duration

O X Computer mode

COMV Computer value Integer (w) Packed Boolean

O X Computer mode

DBY Neutral zone value


DBV Neutral zone value


YNY External alternative Y value

Double 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



212 3BDD011741-600 A

Legend for columns:





I X


I X


I X


I X

CR1 Telegram 1 criteria


I X



I X


Integerl Packed Boolean

I X

Atom Atom name









3BDD011741-600 A 213

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 AC 870P / Melody.The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in Melody.


Operate IT Process Portal: commands

Melody control code

Effect:

AKO/SIG 01800080H Set general operator input inhibitAKOR/SIG 01800100H Reset general operator input inhibitSUO/SIG 40004000H Reset the alternative valueATO/SIG 40034001H Switch to alternative valueATOR/SIG 40034002H Switch from alternative value to input

variable XINT/SIG 00600020H “Internal” setpointEXT/SIG 00600040H “External” setpointCAS/SIG 007c0048H Cascade operating modeCOMP/SIG 001c0010H Computer operating modeMAN/SIG 081c0804H Manual operating modeAUT/SIG 007c0028H Automatic internal operating modeLKOS/SIG 06000200H Set operating mode lockLKOR/SIG 06000400H Reset operating mode lockYFSO/SIG 08000800H Reset forced manual stateCMD0/SIG 30001000H control variable 0 %CMD1/SIG 30002000H control variable 100 %


214 3BDD011741-600 A

Calculated atoms




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)


3BDD011741-600 A 215


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)


216 3BDD011741-600 A


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)

<Tag>.XAY/ALARM


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

<Tag>.XAY/UNACK


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

Section 9 Melody Automation Classes MelodyBFlagx – Block flag

3BDD011741-600 A 217

MelodyBFlagx – Block flag

Features

The block flag (MelodyBFlagx) automation class allows an operator controllable time and data memory from AC 870P / 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 AC 870P / 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 AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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.


<Tag>.YAY/ALARM

Compulsory disconnection with alarm signal pending

YFSO/ALARM

<Tag>.YAY/UNACK

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

YFSO/UNACK


218 3BDD011741-600 A


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 AC 870P / Melody function block identify input and output signals in AC 870P / Melody.Data is exchanged between AC 870P / Melody and 800xA Process Portal, through the internal connections of the AC 870P / 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


3BDD011741-600 A 219

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


Event typical

















220 3BDD011741-600 A




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 signaling behavior can be adjusted on a project-specific basis.

Table: Event typical V1FL1

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 sub-variant (e. g. BFLAG_1) referred to by the event typical. The sub-variant is stored in the Importer for 800xA Process Portal).

NameBrief desc.

Explanatory text

V1FL1 V1FL1 BFLAG STA with events


0 BFLAG_1


140 AKO 9


3BDD011741-600 A 221

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.

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

ATOM Alias Status text 1 Status text 0 AKO AKO AccLock (AccLock) AKO1 AKO1AKO2 AKO2AKO3 AKO3AKO4 AKO4AKO5 AKO5AKO6 AKO6AKO7 AKO7AKO8 AKO8AKO9 AKO9AKO10 AKO10AKO11 AKO11AKO12 AKO12AKO13 AKO13AKO14 AKO14AKO15 AKO15AKO16 AKO16AKO17 AKO17AKO18 AKO18AKO19 AKO19AKO20 AKO20AKO21 AKO21AKO22 AKO22AKO23 AKO23AKO24 AKO24AKO25 AKO25AKO26 AKO26AKO27 AKO27AKO28 AKO28AKO29 AKO29


222 3BDD011741-600 A

Automation class

Structure

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.

AKO30 AKO30O1 O1

Class Atom name DescriptionOperate IT data type

Melody data type

MelodyBFlagB I1..I30 Boolean input PSigBool Boolean

O1..O30 Boolean output

MelodyBFlagC XC1..XC30 Clock input PSigTime Clock

YC1..YC30 Clock output

MelodyBFlagD XD1..XD30 Duration input PSigDuration Duration

YD1..YD30 Duration output

MelodyBFlagI XI1..XI30 Integer input PSigInt Integer

YI1..YI30 Integer output

MelodyBFlagL XL1..XL30 Long duration input PSigDuration Long duration

YL1..YL30 Long duration output

MelodyBFlagP IP1..IP30 Packed Boolean input

PSigPBool Packed Boolean

OP1..OP30 Packed Boolean output

MelodyBFlagR X1..X30 Real input PSigReal Real

Y1..Y30 Real output


3BDD011741-600 A 223

Table: Structure of the MelodyBFlagB automation class


Melodydata type

MelodyI/O


STA Status Integer (w) Packed Boolean

I X

AKO Access locked Bool (w) X X Lock operator access


Bool (w) X X Lock operator access

O1S Set memory 1 Bool (w) X X Operator action

O1R Reset memory 1 Bool (w) X X Operator action



O X Computer mode

O1 Boolean output Bool (w) Boolean I X X OperatorActionNormal

I1 Boolean input Bool (w) Boolean O X Computer mode

O2 Boolean output Bool (w) Boolean I X X Operator action















224 3BDD011741-600 A






























3BDD011741-600 A 225

Legend for columns:

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

















Atom Atom name









226 3BDD011741-600 A

transmitted to the processing function in AC 870P / Melody.The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.


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.

CommandsOperate IT Process Portal:

Melody control code

Effect:



O1S/SIG 30001000H Set memory 1 commands

O1R/SIG 30001000H Reset memory 1 commands


3BDD011741-600 A 227

Calculated atoms




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)


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


BFLAGB:OR (OP1/UNACK, OP2/UNACK, …, OPn/UNACK, …, OP30/UNACK)

MelodyBinary – Binary Section 9 Melody Automation Classes

228 3BDD011741-600 A

MelodyBinary – Binary

Features

The binary (MelodyBinary) automation class allows binary process variables from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

Configuration

The MelodyBinary automation class displays binary process variables from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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.





3BDD011741-600 A 229

The block connections on the monitor block identify signals exchanged between AC 870P / 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





230 3BDD011741-600 A

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

Event typical










• Signal generation for negative edge change (Logic)




3BDD011741-600 A 231

Automation class

Structure

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

Legend for columns:

Atom Description OPC data type Melodydata type

MelodyI/O

Read Write Writeaccess

I1 Boolean input Bool Boolean I X













Atom Atom name






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



232 3BDD011741-600 A

Calculated atoms




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)


OR (I1/ALARM, I2/ALARM, I3/ALARM, I4/ALARM, I5/ALARM, I6/ALARM, I7/ALARM, I8/ALARM, I9/ALARM, I10/ALARM, I11/ALARM, I12/ALARM, I13/ALARM)


OR (I1/UNACK, I2/UNACK, I3/UNACK, I4/UNACK, I5/UNACK, I6/UNACK, I7/UNACK, I8/UNACK, I9/UNACK, I10/UNACK, I11/UNACK, I12/UNACK, I13/UNACK)

Section 9 Melody Automation Classes Melody CLCx controller

3BDD011741-600 A 233

Melody CLCx controller

Features

The controller (MelodyCLC, MelodyCLCD and MelodyCLCM) automation classes allow pre-configured controller functions with and without a drive function in AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The holding controller modules can be optionally assignedto Y/W/K memories.

A selection of pre-configured faceplates is available, depending on the connection of the controller modules.


234 3BDD011741-600 A

Configuration

The MelodyCLCx automation classes display the controller function from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal. This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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 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 AC 870P / 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 AC 870P / 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 AC 870P / Melody.


3BDD011741-600 A 235

OPCLC-00 OPCLCD-00

OPCLCM-00


236 3BDD011741-600 A



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.





3BDD011741-600 A 237

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


238 3BDD011741-600 A

variables from both automation classes can be accessed in the data display (e. g. faceplate).

The base Operation interface of the CSCCLCD and CSCIDF can be extended using a CSCAUX Funtionblock to support intelligent electrical devices (IED).

Please refer to the AC 870P / Melody Composer User Manual for more details.

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.


3BDD011741-600 A 239

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

Event typical









240 3BDD011741-600 A









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


3BDD011741-600 A 241

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


242 3BDD011741-600 A

Table: Event typical MP1

NameBrief desc.

Explanatory text

MP1 MP1 Variable speed drive


160 CLC_1


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


3BDD011741-600 A 243

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 sub-variant (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

43 MANS 5

44 AUTS 5


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)


244 3BDD011741-600 A

Automation class

Structure

The following table describes the structure of the automation class for MelodyCLC individual control.

Table: Structure of the MelodyCLC and MelodyCLCM automation classes

MAN XC03_1 Manual (Manuell)

AUT XC04_1 Automatic (Automatic)

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

Atom Description OPC data typeMelodydata type

MelodyI/O


IST1 Memory 1 status Integer Packed Boolean

I X


3BDD011741-600 A 245


I X


I X

E1_1 End position 1 SP1 Bool X

E1N_1 End position not 1 SP1

Bool X

E0_1 End position0 SP1

Bool X


Bool X

BLK1_1 Blockade 1 SP1 Bool X


AUT1_1 Release Automatic+ SP1

Bool X

CMD+_1 Activate command + SP1

Bool (w) X Operator action

AUT0_1 Release Automatic- SP1

Bool X

CMD-_1 Activate command- SP1


MAN_1 Manual SP1 Bool (w) X X Operator mode

OMN_1 Manual control SP1

Bool (w) Extended Boolean

O X Computer mode

AUT_1 Automatic SP1 Bool (w) X X Operator mode

OAU_1 Automatic control SP1


O X Computer mode

LOCK_1 Lock SP1 Bool (w) X X Lock operator mode

R1_1 Release 1 SP1 Bool X



246 3BDD011741-600 A

P1_1 Protective action 1 SP1

Bool X


Bool X

ERI_1 Fault action SP1 Bool X

ER_1 Fault SP1 Bool X

CMDAC_1

Command acknowledgement SP1

Bool X

OPL_1 Lock operation SP1


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


O X Computer mode


Bool X

OC01 Command unit 1 Off


O X Computer mode

INHI_1 Inhibit SP1 Bool X

OIN1 Command inhibit SP1


O X Computer mode

PCF_1 Positioning circuit fault SP1

Bool X

DAUT_1 Automatic fault SP1

Bool X

DMAN_1 Manual fault SP1 Bool X


3BDD011741-600 A 247

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) X Acknowledge

A1 control variable (Y) SP1


A1/ALARM

Bool

A1/UNACK

Bool

YA1 Setpoint A1 SP1 Double (w) Real O X Computer mode

A1V1 Limit signal 1 for A1 SP1


I X

A1X1 Limit value 1 for A1 (actual) SP1


YA11 Specified limit value A1V1




I X


Double (w) Real X Low limits

YA12 Specified limit value A1V2 SP1


OOP1 Nominal word SP1 IntegerW Packed Boolean

O X Computer mode



Bool X



248 3BDD011741-600 A


Bool X




Bool X




Bool X




OMN2 Manual control SP2


O X Computer mode


OAU2 Automatic control SP2


O X Computer mode





Bool X


Bool X



CMDAC_2


Bool X


3BDD011741-600 A 249




Bool X




Bool X



O X Computer mode


Bool X



O X Computer mode




O X Computer mode


Bool X


Bool X



Bool X

AUT1_2 Automatic control SP2

Bool X



Bool (w) X Acknow-ledge




250 3BDD011741-600 A

A2/ALARM

Bool

A2/UNACK

Bool


OOP2 Operator setpoint SP2

IntegerW Packed Boolean

O X Computer mode



Bool X



Bool X




Bool X




Bool X




OMN3 Manual control SP3


O X Computer mode


OAU3 Automatic control SP3


O X Computer mode


3BDD011741-600 A 251





Bool X


Bool X



CMDAC_3


Bool X




Bool X




Bool X



O X Computer mode


Bool X



O X Computer mode




O X Computer mode


Bool X


252 3BDD011741-600 A


Bool X



Bool X


Bool X



Bool (w) X Acknowledge



A3/ALARM

Bool

A3/UNACK

Bool


OOP3 Operator setpoint SP3

IntegerW Packed Boolean

O X Computer mode

RX1 Reference signal 1 ATOMREF X










I X


I X


3BDD011741-600 A 253

Table: Structure of the MelodyCLCD automation class


I X


I X

CR1 Criteria telegram 1 Integer Packed Boolean

I X


I X


I X

TOP Object reference SymRef

Atom DescriptionOperate IT

data typeMelodydata type

MelodyI/O



I X



Bool X



Bool X




Bool X




Bool X


254 3BDD011741-600 A




OMN Manual control SP1 Bool (w) Extended Boolean

O X Computer mode


OAU Automatic control SP1


O X Computer mode





Bool X


Bool X



CMDAC_1


Bool X

OPL_1 Lock operation SP1 Bool (w) X X Lock operator access


Bool X



IC1_1 Control system 1 SP1 Bool X



O X Computer mode

IC0_1 Control system 0 SP1 Bool X


3BDD011741-600 A 255

OC0 Command unit 1 Off Bool (w) Extended Boolean

O X Computer mode


OIN Command inhibit SP1 Bool (w) Extended Boolean

O X Computer mode


Bool X

DAUT_1 Automatic fault SP1 Bool X

DMAN_1

Manual fault SP1 Bool X

MANS_1 Manual control SP1 Bool X


Bool X



Bool (w) X Acknow-ledge



A1/ALARM

Bool

A1/UNACK

Bool




I X



YA11 Specified limit value A1V1




I X


Double (w) Real X Low limits


256 3BDD011741-600 A

Legend for columns:

YA12 Specified limit value A1V2 SP1


OOP Nominal word SP1 IntegerW Packed Boolean

O X Computer mode










I X


I X


I X


I X


I X


I X


I X

RCLC Object reference SymRef

Atom Atom name


Operate IT data type

800xA Process Portal data type



3BDD011741-600 A 257

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 AC 870P / Melody.The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.






Memory:800xA Process Portal: commands

Melody control code

Effect:

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


258 3BDD011741-600 A

Calculated atoms


W memory ACK/SIG 00000405H Acknowledge error memory







K memory ACK/SIG 00000c05H Acknowledge error memory

OPL/SIG 00000c0bH Set/reset general operator input inhibit

MAN/SIG 00000c13H Switch the operating mode to “Manual”

AUT/SIG 00000c23H Switch operating mode to “Automatic”

LOCK/SIG 00000c43H Lock operating mode switching – “Lock”

CMD+/SIG 00000c83H Incremental adjustment

CMD-/SIG 00000d03H Decremental adjustment


3BDD011741-600 A 259

Calculation standard for MelodyCLC and Melody CLCM automation classes



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)


260 3BDD011741-600 A


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)


3BDD011741-600 A 261


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)

<Tag>.A1/ALARM

Function fault, alarm signal pending(ER||EER||RF0||BLK0||BLK1||PCF||DAUT||DMAN||A1V1||A1V2)

OR (ER_1/ALARM, EER_1/ALARM, BLK0_1/ALARM, BLK1_1/ALARM, PCF_1/ALARM, DAUT_1/ALARM, DMAN_1/ALARM, A1V1/ALARM, A1V2/ALARM)


262 3BDD011741-600 A

Calculation standard for MelodyCLCD automation class

<Tag>.A1/UNACK

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

OR (ER_1/UNACK, EER_1/UNACK, BLK0_1/UNACK, BLK1_1/UNACK, PCF_1/UNACK, DAUT_1/UNACK, DMAN_1/UNACK, A1V1/UNACK, A1V2/UNACK)

<Tag>.A2/ALARM

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

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

<Tag>.A2/UNACK

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

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

<Tag>.A3/ALARM

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

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

<Tag>.A3/UNACK

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

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


<Tag>.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)


3BDD011741-600 A 263


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)


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)

<Tag>.A1/ALARM

Function fault, alarm signal pending(ER||EER||RF0||BLK0||BLK1||PCF||DAUT||DMAN||A1V1||A1V2)

OR (ER_1/ALARM, EER_1/ALARM, BLK0_1/ALARM, BLK1_1/ALARM, PCF_1/ALARM, DAUT_1/ALARM, DMAN_1/ALARM, A1V1/ALARM, A1V2/ALARM)

<Tag>.A1/UNACK

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

OR (ER_1/UNACK, EER_1/UNACK, BLK0_1/UNACK, BLK1_1/UNACK, PCF_1/UNACK, DAUT_1/UNACK, DMAN_1/UNACK, A1V1/UNACK, A1V2/UNACK)

MelodyCOA – Change over automatic Section 9 Melody Automation Classes

264 3BDD011741-600 A

MelodyCOA – Change over automatic

Features

The change over automatic (MelodyCOA) automation class allows pre-configured automatic reversing from AC 870P / 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.

The base Operation interface of the CSCIDF and CSCCLCD can be extended using a CSCAUX Funtionblock to support intelligent electrical devices (IED).

Please refer to the AC 870P / Melody Composer User Manual for more details.

Configuration

The MelodyCOA automation class displays the change over automatic from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / Melody connection components.


3BDD011741-600 A 265


The configuration from Composer is described in the manual “AC 870P / Melody – Engineering in the manual “AC 870P / Melody – Engineering Tool Composer, Operation“, 2PAA101133.


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 AC 870P / Melody function block identify input and output signals in AC 870P / Melody.Data must be exchanged between AC 870P / 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 AC 870P / 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 AC 870P / 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 AC 870P / Melody.


266 3BDD011741-600 A

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






3BDD011741-600 A 267

Event typical












• Packed Boolean sub-variants $




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.


268 3BDD011741-600 A

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

Table: Event typical MU1

NameBrief desc.

Explanatory text

MU1 MU1 change over automatic


160 COA_1


52 PU1 5

53 PU2 5

54 PU3 5

55 PU4 5

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


3BDD011741-600 A 269

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 sub-variant (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.

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


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)

CMDAC

OPL XM19 OperLock (OperLock)

OPHP XM18 HighPrioOp (HighPrioOp)

PUOFF XA65 PrioAggOff (PrioAggOff)

OL1 XA21 SeqInterv1 (SeqInterv1)


INHI XM17 Inhibit (Inhibit)

SGRA XA66 SP>ActVal (SP>ActVal)

SLEA XA64 SP<ActVal (SP<ActVal)


270 3BDD011741-600 A

Automation class

Structure

The following table describes the structure of the automation class for the MelodyCOA change over automatic.

Table: Structure of the MelodyCOA automation class


MelodyI/O


IST Status Integer (w) Packed Boolean

I X

IST/ALARM

Bool

IST/UNACK

Bool

PU1 Unit 1 Bool (w) X Operator action









OMN Manual Bool (w) Extended Boolean

O X Computer mode


3BDD011741-600 A 271


OAU Automatic Bool (w) Extended Boolean

O X Computer mode

LOCK Lock Bool (w) X Lock operator mode

ER Fault Bool

CMDAC Command acknowledgement

Bool

OPL Lock operator input


OPHP Higher priority operation

Bool

PUOFF Priority unit off Bool

IC1 Control system 1 Bool


INHI Operating mode S/O lock

Bool

OIN Inhibit Bool (w) Extended Boolean

O X Computer mode

SGRA Units Target > Actual

Bool

SLEA Units Target <= Actual

Bool

UNIT Priority unit (decimal)

Integer (w)

CMD+ Unit command + Bool (w) X Operator action

CMD- Unit command – Bool (w) X Operator action

ACK Acknowledge Bool (w) X Acknowledge

OOP Nominal word Integer (w)W Packed Boolean

O X Computer mode


272 3BDD011741-600 A

Legend for columns:


ATOMREF


ATOMREF


ATOMREF


ATOMREF


I X


I X


I X


I X



I X



I X



I X

Atom Atom name









3BDD011741-600 A 273

Control

The operator actions for the MelCOA change over automatic are converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in AC 870P / Melody.The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.


Commands800xA Process Portal:

Melody control code

Effect:

PU1/SIG 0x00018003H Set priority to unit 1








ACK/SIG 00000005H Acknowledge error memory







MelodyCount – Counter Section 9 Melody Automation Classes

274 3BDD011741-600 A

MelodyCount – Counter

Features

The counter (MelodyCount) automation class allows a freely-configurable counter function from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The process variables from the integer data type to be counted can be checked against up to 4 limit values.


Configuration

The MelodyCount automation class displays the counter function from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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 block connections on the monitoring block identify signals exchanged between AC 870P / 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 AC 870P / Melody and


3BDD011741-600 A 275

800xA Process Portal, the function block connections on the monitor function block must be connected to the function blocks in AC 870P / Melody.


CNT-01





276 3BDD011741-600 A

Fig.: Connection example for the MelodyCount automation class(data link to 800xA Process Portal using CNT01 function block)


Automation class

Structure

The following table describes the structure of the automation class for the MelodyCount counter function.

Table: Structure of the MelodyCount automation class


Melodydata type

MelodyI/O


XI Integer input Integer Integer I X

XI/ALARM Bool

XI/UNACK Bool


I X

X11 Limit value 1 Integer (w) Integer I X X High limits

YXV1 Limit value 1 Integer (w) Integer O X Computer mode


3BDD011741-600 A 277

Legend for columns:


I X




I X




I X




I X


I X


I X


I X

Atom Atom name









278 3BDD011741-600 A

Calculated atoms



<Tag>.BAD/SIG


OR (XI/SIG, X11/SIG, I11/SIG, X12/SIG, I12/SIG, X13/SIG, I13/SIG, X14/SIG, I14/SIG, I1/SIG, I2/SIG, I3/SIG, I4/SIG)

<Tag>.ALARM

General function fault, alarm signal pending

OR (I11/ALARM, I12/ALARM, I13/ALARM,I14/ALARM, I1/ALARM, I2/ALARM, I3/ALARM,I4/ALARM)

<Tag>.UNACK

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

OR (I11/UNACK, I12/UNACK, I13/UNACK,I14/UNACK, I1/UNACK, I2/UNACK, I3/UNACK,I4/UNACK)

<Tag>.XI/ALARM


OR (I11/ALARM, I12/ALARM, I13/ALARM,I14/ALARM)

<Tag>.XI/UNACK


OR (I11/UNACK, I12/UNACK, I13/UNACK,I14/UNACK)

Section 9 Melody Automation Classes MelodyDos – Dosing circuit

3BDD011741-600 A 279

MelodyDos – Dosing circuit

Features

The dosing circuit (MelodyDos) automation class allows the pre-configured dosing circuit function from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The dosing circuit function in AC 870P / Melody has an operating mode memory and allows quantity acquisition through integration of the counter values, optionally with pre-deactivation.


Configuration

The MelodyDos automation class displays the dosing circuit function from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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 figures below show the function blocks for the dosing circuit function in Composer. The function blocks have an integrated monitoring block for the link to 800xA Process Portal.



280 3BDD011741-600 A

DOS-00 – Dosing circuit function DOS-01 – Dosing circuit function


3BDD011741-600 A 281



DOS-03 – Dosing circuit function





282 3BDD011741-600 A

Event typical
















For the STA and STA1 function block connections in the MelodyDos automation class, the event typicals VDO1 and VDO2 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.


3BDD011741-600 A 283

Structure of event typicals VDO1 and VDO2 The signaling behavior can be adjusted on a project-specific basis.

Table: Event typical VDO1

NameBrief Desc.

Explanatory text

VDO1 VDO1 STA dosing circuit


0 DOS_1


176 WO 10

177 SOVO 10

178 LRO 10

179 LRSO 10

180 LSTO 10

210 FULL 10

211 PART 10

212 OMAN 10

213 OAUT 10

214 OLK 10

181 RW+O 10

215 SOVW 10

206 LEAK 10

32 PST 10

182 FO 10

216 LOPO 10

183 AUTP 10

184 MANP 10

185 DRP 10

186 DRSP 10


284 3BDD011741-600 A

Table: Event typical VDO2

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 DOS_1 and DOS_2 sub-variants referred to by the event typical. The sub-variant is stored in Importer for 800xA Process Portal).

Structure of sub-variants DOS_1 and DOS_2. The status texts and the alias can be adjusted on a project-specific basis.

187 DSTP 10

188 INHP 10

207 HVO 10

208 LVO 10

217 DSTO 10

218 DRSO 10

219 DRO 10

NameBrief Desc.

Explanatory text

VDO2 VDO2 Dosing circuit STA1


0 DOS_2


220 E11 10

221 E01 10

222 E10 10

223 E00 10

31 TEST 10


3BDD011741-600 A 285

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


WO WO SetPReach (SetPReach)

SSOV SSOV

SOVO SOVO PSV Reach (PSV Reach)

LRO LRO P Rel Msg (P Rel Msg)

LRSO LRSO P Res Msg (P Res Msg)

LSTO LSTO P Stp Msg (P Stp Msg)

FULL FULL Full Dos (Full Dos)

PART PART Part Dos (Part Dos)

OMAN OMAN Manual (Manual)

OAUT OAUT Automatic (Automatic)

OLK OLK Lock (Lock)

RW+O RW+O Rel AD M (Rel AD M)

SOVW SOVW 2SwitchOff (2SwitchOff)

LEAK LEAK Leakage (Leakage)

PST PST PStp (PStp)

FO FO ErrMsg (ErrMsg)

CMDAC CMDAC

LOPO LOPO OP-LockP (OP-LockP)

AUTP AUTP OM AUT P (OM AUT P)

MANP MANP OM MAN P (OM MAN P)

DRP DRP DosRelP (DosRelP)

DRSP DRSP DosResP (DosResP)

DSTP DSTP DosStpP (DosStpP)


286 3BDD011741-600 A

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

Automation class

Structure

The following table describes the structure of the automation class for the MelodyDos dosing circuit function.

Table: Structure of the MelodyDos automation class

INHP INHP OM-LockP (OM-LockP)

HVO HVO MaxMsg (MaxMsg)

LVO LVO MinMsg (MinMsg)

DSTO DSTO Stp Dos (Stp Dos)

DRSO DRSO Res Dos (Res Dos)

DRO DRO Rel Dos (Rel Dos)


E11 E11 E1 Valve 1 (E1 Valve 1)




TEST TEST Test (Test)


Melodydata type

MelodyI/O



I X

STA/ALARM

Bool


3BDD011741-600 A 287

STA/UNACK

Bool

STA1 Status 1 Integer (w) Packed Boolean

I X

WO Setpoint reached Bool

SSOV Pre-deactivation value active

Bool

SOVO Pre-deactivation value reached

Bool

LRO Dosing release lock

Bool

LRSO Dosing reset lock Bool

LSTO Dosing stop lock Bool

FULL Full quantity valve open

BoolW X Operator action

PART Part quantity valve open


OMAN Manual BoolW X Operator mode

OAUT Automatic BoolW X Operator mode

OLK ACTUAL dosing circuit, lock


RW+O Release dosing BoolW X Operator action

SOVW Pre-deactivation value reached

Bool

LEAK Leakage Bool

PST Protection stop Bool

FO Fault Bool


288 3BDD011741-600 A


Bool

LOPO Operator lock BoolW X Lock OperatorAccess

AUTP Process request for AUT operating mode

Bool

MANP Process request for MAN operating mode

Bool

DRP Dosing release from the process

Bool

DRSP Dosing reset from the process

Bool

DSTP Dosing stop from process

Bool

INHP Inhibit from the process

Bool



DSTO Dosing stop BoolW X Operator action

DRSO ACTUAL dosing, reset


DRO Release dosing BoolW X Operator action

ACK Bool (w) X Acknowledge

E11 End position 1, valve 1

Bool


Bool


3BDD011741-600 A 289


Bool


Bool

TEST Test position Bool

OP Nominal word PSigPBoolW

Packed Boolean

O X Computer mode

AUT Automatic Bool (w) Extended Boolean

O X Computer mode

MAN Manual Bool (w) Extended Boolean

O X Computer mode

INHI Operating mode S/O lock


O X Computer mode

R Release Bool (w) Extended Boolean

O X Computer mode

RS Reset static Bool (w) Extended Boolean

O X Computer mode

STP Stop Bool (w) Extended Boolean

O X Computer mode

XCT Analog counter Double (w) Real O X Computer mode

XCTF Frequency counter Double (w) Real O X Computer mode

RTSO PDV as percentage of setpoint


RTY Target/actual percent


CSY Actual counter value

Double Real I X

BSV Basic setting value Double (w) Real O X Computer mode


290 3BDD011741-600 A

BSY Basic setting value Double (w) Real I X X Setpoint control

SOV Pre-deactivation value


SOY Pre-deactivation value


SOV0 Fine valve run out quantity


SOY0 Fine valve run out quantity


W External setpoint Double (w) Real O X Computer mode

WY Setpoint Double (w) Real I X X Setpoint control

W+ Fine dosing quantity


W+Y Fine dosing quantity


RW+ Release fine dosing


O X Computer mode

Y1V Rough dosing value

Double Real I X

Y0V Fine dosing value Double Real I X

Y Pneumatic control variable

Double Real I X

QY Intermediate value Double Real I X

QWY Remaining dosing quantity

Double Real I X


ATOMREF ATOMREF


ATOMREF ATOMREF


3BDD011741-600 A 291

Legend for columns:


ATOMREF ATOMREF


ATOMREF ATOMREF






I X


I X


I X


I X

CR1 Telegram 1 criteria Integer Packed Boolean

I X


I X


I X

Atom Atom name






292 3BDD011741-600 A

Control

The operator actions for the MelDos dosing circuit functions are converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in AC 870P / Melody.The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.





Commands800xA Process Portal

Melody control code

Effect:

LOPO/SIG 0000000bH Set/reset general operator input inhibit

OMAN/SIG 00000013H Manual operating mode

OAUT/SIG 00000023H Automatic operating mode

OLK/SIG 00000043H Operating mode lock

RW+O/SIG 00001003H Fine dosing

PART/SIG 00000103H Fine dosing

FULL/SIG 00000083H Rough dosing

DRSO/SIG 00000803H Reset to basic setting value

DSTO /SIG 00000203H Stop command

DRO/SIG 00000403H Release dosing valves


3BDD011741-600 A 293

Calculated atoms




OR (STA/SIG, STA1/SIG, RTY/SIG, CSY/SIG, BSY/SIG, SOY/SIG, SOY0/SIG, WY/SIG, W+Y/SIG, Y1V/SIG, Y0V/SIG, Y/SIG, QY/SIG, QWY/SIG, X1/SIG, X2/SIG, X3/SIG, X4/SIG, I1/SIG, I2/SIG, I3/SIG, I4/SIG)


OR (WO/ALARM, SOVO/ALARM, LRO/ALARM,LRSO/ALARM, RSO/ALARM, LSTO/ALARM,FULL/ALARM, PART/ALARM, OMAN/ALARM,OAUT/ALARM, OLK/ALARM, RW+O/ALARM,SOVW/ALARM, LEAK/ALARM, PST/ALARM,FO/ALARM, LOPO/ALARM, AUTP/ALARM,MANP/ALARM, DRP/ALARM, DRSP/ALARM,DSTP/ALARM, INHP/ALARM, HVO/ALARM,LVO/ALARM, DSTO/ALARM, DRSO/ALARM,DRO/ALARM, E11/ALARM, E01/ALARM, E10/ALARM, E00/ALARM, TEST/ALARM, I1/ALARM, I2/ALARM,I3/ALARM, I4/ALARM)


294 3BDD011741-600 A


OR (WO/UNACK, SOVO/UNACK, LRO/UNACK,LRSO/UNACK, RSO/UNACK, LSTO/UNACK,FULL/UNACK, PART/UNACK, OMAN/UNACK,OAUT/UNACK, OLK/UNACK, RW+O/UNACK,SOVW/UNACK, LEAK/UNACK, PST/UNACK,FO/UNACK, LOPO/UNACK, AUTP/UNACK,MANP/UNACK, DRP/UNACK, DRSP/UNACK,DSTP/UNACK, INHP/UNACK, HVO/UNACK,LVO/UNACK, DSTO/UNACK, DRSO/UNACK,DRO/UNACK, E11/UNACK, E01/UNACK, E10/UNACK, E00/UNACK, TEST/UNACK, I1/UNACK, I2/UNACK,I3/UNACK, I4/UNACK)

<Tag>.STA/ALARM

Fault with alarm signal pending

(FO/ALARM)

<Tag>.STA/UNACK

Fault with alarm signal pending, error status not yet acknowledged

(FO/UNACK)

Section 9 Melody Automation Classes MelodyIDF – Individual control

3BDD011741-600 A 295

MelodyIDF – Individual control

Features

The individual control (MelodyIDF) automation classes allow freely or pre-configured individual control functions from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The individual control function is used to control the drive motors, actuator and solenoid valves. It has an operating mode memory and monitors the End positions of the units controlled.

In the context of the unit, individual items of analog or binary data can also be presented. A selection of pre-configured faceplates are available.

Configuration

The MelodyIDF automation class displays the individual control function from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by the interconnection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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.


296 3BDD011741-600 A



The figures below show the function blocks for the individual control function in Composer. The figures show a monitoring block with the interface to Composer and 800xA Process Portal, as well as a function block with integrated monitoring block.

Fig.: Monitoring block – interface to Composer and 800xA Process Portal

Fig.: Melody function block with integrated monitor

The block connections on the monitoring block identify signals exchanged between AC 870P / 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 AC 870P / Melody and 800xA Process Portal the function block connections on the monitor function block must be connected to the function blocks for an individual control function in AC 870P / Melody.

To reduce the design costs, the monitoring block can be connected inside a macro cover (integrated monitoring block, see right hand figure).

The connections to the AC 870P / Melody function block identify input and output signals in AC 870P / Melody.Data is exchanged between AC 870P / Melody and 800xA Process Portal, through the internal connections of the AC 870P / Melody function block with a monitoring block inside the yellow backed case. The costly external connections between the function blocks are removed, reducing the overall design costs.


3BDD011741-600 A 297


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






298 3BDD011741-600 A

Event typical
















For the STA function block connection in the MelodyIDF automation class, the event typicals MA1, MA2, MA3 MM1, MP1, VP01 … VP10 and VM01 … VM10 are defined as standard in Composer.


3BDD011741-600 A 299

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 MA1. The signaling behavior can be adjusted on a project-specific basis.

Table: Event typical MA1

NameBrief Desc.

Explanatory text

MA1 MA1 Individual control Open/Closed/Stop


49336 IDF_P1


0 E1 6

1 E0 6

2 BLK1 5

3 BLK0 5

6 R1 5

7 R0 5

8 P1 5

9 P0 5

10 OL1 5

11 OL0 5

16 STP 5

17 EFL 5

19 EF1 3

20 EF0 3

21 EF1L 5

22 EF0L 5

25 EF1P0 5

26 EF0P1 5


300 3BDD011741-600 A

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 sub-variant (e. g. IDF_P1) 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 IDF-P1. The status texts and the alias can be adjusted on a project- specific basis.

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

27 RF1 3

28 RF0 3

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


E1 XB01 Open (Open)

E0 XB02 N Open (N Open)

BLK1 XM01 Torque 1 (Torque 1)

BLK0 XM02 Torque 0 (Torque 0)

R1 XB25 Release 1 (Release 1)


3BDD011741-600 A 301

R0 XB26 Release 0 (Release 0)

P1 XB37 Protect 1 (Protect 1)

P0 XB38 Protect 0 (Protect 0)

OL1 XB21 SeqInterv1 (SeqInterv1)

OL0 XB22 SeqInterv0 (SeqInterv0)

STP XB03 Stop (Stop)

EFL XM09 EFL (EFL)

EF1 XM07 EF1 (EF1)

EF0 XM08 EF0 (EF0)

EF1L XN61 EF1L (EF1L)

EF0L XN62 EF0L (EF0L)

EF1P0 XN63 EF1P0 (EF1P0)


RF1 XM05 Runtime 1 (Runtime 1)


EER XM41 ExtError (ExtError)

TEST XB04 Test (Test)

ERI XM43 DistInterv (DistInterv)

LI XM57 LocInterv (LocInterv)

MAN XB08 Manual (Manual)

AUT XB07 Automatic (Automatic)



OPL XB19 OperLock (OperLock)



302 3BDD011741-600 A

Automation class

Structure

The following table describes the structure of the automation class for MelodyIDF individual control.

Table: Structure of the MelodyIDF automation class


CMD1 XB63 Command 1 (Command 1)

CMD0 XB64 Command 0 (Command 0)

E1N XB51 N Open (N Open)

E0N XB52 N Close (N Close)

CMDAC


Melodydata type

MelodyI/O


ACTUAL Status Integer Packed Boolean

I X

IST/ALARM Bool X

IST/UNACK Bool X

IST/FL12 Bool X

IST/FL18 Bool X

IST/FL02 Bool X

IST/FL08 Bool X

E1 End position 1 Bool X

E1N End position not 1 Bool X


E0N End position not 0 Bool X

BLK1 Blockade 1 Bool X


3BDD011741-600 A 303

BLK0 Blockade 0 Bool X

CMD1 Activate command Bool (w) X X Operator action

CMD+ Activate command + Bool (w) X Operator action

CMD0 De-activate command Bool (w) X X Operator action

CMD- De-activate command –


MAN Manual Bool (w) X X Operator mode

OMN Manual control Bool (w) Extended Boolean

O X Computer mode

AUT Automatic Bool (w) X X Operator mode

OAU Automatic control Bool (w) Extended Boolean

O X Computer mode

LOCK Lock Bool (w) X X Lock operator mode

R1 Release 1 Bool X

R0 Release 0 Bool X

P1 Protective action 1 Bool X

P0 Protective action 0 Bool X

ERI Fault action Bool X

ER Fault Bool X


Bool X

OPL Lock operator input Bool (w) X X Lock operator access


304 3BDD011741-600 A


Bool X

EER External fault Bool X

TEST Test position Bool X

IC1 Control system 1 Bool X

OC1 Command 1 Bool (w) Extended Boolean

O X Computer mode

IC0 Control system 0 Bool X


O X Computer mode

STP Stop Bool (w) X X Operator action

OCS Stop command Bool (w) Extended Boolean

O X Computer mode

INHI Inhibit Bool X

OIN Inhibit command Bool (w) Extended Boolean

O X Computer mode

EFL Local End position error

Bool X

EF1 End position error 1 Bool X

EF0 End position error 0 Bool X

EF1L Local End position error 1

Bool X

EF0L Local End position error 0

Bool X

EF1P0 End position error 1 via protection 0

Bool X


Bool X

RF1 Execution time error 1 Bool X

RF0 Execution time error 0 Bool X


3BDD011741-600 A 305

LI Local action Bool X

ACK Acknowledge Bool (w) X Acknow ledge

OOP Nominal word Integer (w) Packed Boolean

O X Computer mode

RX1 Reference to signal 1 ATOMREF X









I X


I X


I X


I X


I X


I X


I X


306 3BDD011741-600 A

Legend for columns:

Control

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


Atom Atom name





Read Atom can be read in 800xA Process Portal



CommandsOperate IT:

Melody control code

Effect:






CMD1/SIG 00000083H “ON” commands

CMD0/SIG 00000103H “OFF” commands

STP/SIG 00000203H “STOP” commands


3BDD011741-600 A 307

Calculated atoms






OR (IST/SIG, X1/SIG, X2/SIG, X3/SIG, X4/SIG, I1/SIG,I2/SIG, I3/SIG, I4/SIG)


OR (E1/ALARM, E0/ALARM, BLK1/ALARM,BLK0/ALARM, MAN/ALARM, AUT/ALARM,LOCK/ALARM, R1/ALARM, R0/ALARM, P1/ALARM,P0/ALARM, ERI/ALARM, ER/ALARM, OPL/ALARM, OPHP/ALARM, EER/ALARM, TEST/ALARM, IC1/ALARM, IC0/ALARM, STP/ALARM, INHI/ALARM, EFL/ALARM, EF1/ALARM, EF0/ALARM, EF1L/ALARM, EF0L/ALARM, EF1P0/ALARM, EF0P1/ALARM, RF1/ALARM, RF0/ALARM, LI/ALARM, I1/ALARM, I2/ALARM, I3/ALARM, I4/ALARM)


308 3BDD011741-600 A


OR (E1/UNACK, E0/UNACK, BLK1/UNACK,BLK0/UNACK, MAN/UNACK, AUT/UNACK,LOCK/UNACK, R1/UNACK, R0/UNACK, P1/UNACK,P0/UNACK, ERI/UNACK, ER/UNACK, OPL/UNACK, OPHP/UNACK, EER/UNACK, TEST/UNACK,IC1/UNACK, IC0/UNACK, STP/UNACK, INHI/UNACK, EFL/UNACK, EF1/UNACK, EF0/UNACK, EF1L/UNACK, EF0L/UNACK, EF1P0/UNACK, EF0P1/UNACK,RF1/UNACK, RF0/UNACK, LI/UNACK, I1/UNACK,I2/UNACK, I3/UNACK, I4/UNACK)

<Tag>.IST/ALARM Function fault, alarm signal pending(ER||EER||RF0||RF1||BLK0||BLK1||EF0||EF1)

OR (ER/ALARM, EER/ALARM, RF0/ALARM,RF1/ALARM, BLK0/ALARM, BLK1/ALARM, EF0/ALARM, EF1/ALARM)

<Tag>.IST/UNACK Function fault, alarm signal pending, error status not yet acknowledged(ER||EER||RF0||RF1||BLK0||BLK1||EF0||EF1)

OR (ER/UNACK, EER/UNACK, RF0/UNACK,RF1/UNACK, BLK0/UNACK, BLK1/UNACK, EF0/UNACK, EF1/UNACK)

<Tag>.IST/FL12 Error status in End position 1(RF1||EF1||BLK1)

OR (RF1/SIG, EF1/SIG, BLK1/SIG)

Section 9 Melody Automation Classes MelodyOPA – Binary memory

3BDD011741-600 A 309

MelodyOPA – Binary memory

Features

The binary memory (MelodyOPA) automation class allows a pre-configured binary memory from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The binary memory has an operating mode memory and has dynamic and static set and reset inputs.


Configuration

The MelodyOPA automation class displays the binary memory from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / Melody connection components.

<Tag>.IST/FL18 Drive moving to End position 1 for (CMD1 & !E1)

AND (CMD1/SIG, NOT (E1/SIG))

<Tag>.IST/FL02 Error status in End position 0(RF0||EF0||BLK0)

OR (RF0/SIG, EF0/SIG, BLK0/SIG)

<Tag>.IST/FL08 Drive moving to End position 0 for (CMD0 & !E0)



310 3BDD011741-600 A




The following figures show the binary memory 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 blockFig.: Monitoring block – interface to Composer and

800xA Process Portal

The connections to the AC 870P / Melody function block identify input and output signals in AC 870P / Melody.Data must be exchanged between AC 870P / Melody and 800xA Process Portal using an external connection between the BMEM-02 function block and the BMEM-00 monitoring block.

The block connections on the monitoring block identify signals exchanged between AC 870P / 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 AC 870P / Melody and 800xA Process Portal, the function block connections on the monitor function block must be connected to the function blocks for the binary memory in AC 870P / Melody.


3BDD011741-600 A 311


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






312 3BDD011741-600 A

Event typical
















For the STA function block connection in the MelodyOPA automation class, the event typicals MX1 and MX2 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.


3BDD011741-600 A 313

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

Table: Event typical MX1

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 sub-variant (e. g. OPA_1) referred to by the event typical. The sub-variant is stored in the Importer for 800xA Process Portal).

NameBrief Desc.

Explanatory text

MX1 MX1 Binary memory On/Off


184 OPA_1


0 E1 6

1 E0 6

6 R1 5

7 R0 5

12 SET 5

13 RES 5

14 SETD 5

15 RESD 5

35 MAN 5

36 AUT 5

37 LOCK 5

38 INHI 5

49 OPL 5

51 ER 5


314 3BDD011741-600 A

Structure of a sub-variant using the example of OPA_1. The status texts and the alias can be adjusted on a project- specific basis.

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

Automation class

Structure

The following table describes the structure of the automation class for the MelodyOPA binary memory.


E1 XA81 On (On)

E0 XA82 Off (Off)




R1 XA25 Release 1 (Release 1)


SET XA41 Set (Set)

RES XA42 Reset (Reset)


OPL XA19 OperLock (OperLock)

OPHP XA18 HighPrioOp (HighPrioOp)

CMDAC

SETD XA43 SetDyn (SetDyn)

RESD XA44 ResDyn (ResDyn)



3BDD011741-600 A 315

Table: Structure of the MelodyOPA automation class


Melodydata type

MelodyI/O



I X

IST/ALARM Bool X

IST/UNACK Bool X



CMD1 Activate command Bool (w) X X Operator action


Bool (w) X X Operator action

MAN Manual BoolW X X Operator mode

OMN Manual control Bool (w) Extended Boolean

O X Computer mode

AUT Automatic BoolW X X Operator mode

OAU Automatic control Bool (w) Extended Boolean

O X Computer mode

LOCK Lock BoolW X X Lock operator mode

R1 Release 1 Bool X

R0 Release 0 Bool X

SET Set memory Bool X

RES Reset memory Bool X

ER Fault Bool X


Bool X


316 3BDD011741-600 A


BoolW X X Lock operator access


Bool X

SETD Set dyn. memory Bool X


O X Computer mode

RESD Reset dyn. memory

Bool X


O X Computer mode

INHI Inhibit Bool X

OIN Inhibit command Bool (w) Extended Boolean

O X Computer mode



O X Computer mode

RX1 Reference to signal 1

ATOMREF X


ATOMREF X


ATOMREF X


ATOMREF X


I X


3BDD011741-600 A 317

Legend for columns:

Control

The operator actions for the MelOPA binary memory is converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in AC 870P / Melody.


I X


I X


I X


I X


I X


I X

Atom Atom name









318 3BDD011741-600 A

The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.


Calculated atoms


CommandsOperate IT

Melody control code

Effect:










OR (IST/SIG, I1/SIG, I2/SIG, I3/SIG, I4/SIG)


OR (E1/ALARM, E0/ALARM, MAN/ALARM, AUT/ALARM, LOCK/ALARM, R1/ALARM, R0/ALARM, SET/ALARM, RES/ALARM, OPL/ALARM, OPHP/ALARM,SETD/ALARM, RESD/ALARM, INHI/ALARM, I1/ALARM, I2/ALARM, I3/ALARM, I4/ALARM)

Section 9 Melody Automation Classes MelodySel – Preselection

3BDD011741-600 A 319

MelodySel – Preselection

Features

The selection (MelodySel) automation class allows the pre-configured preselection from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The preselection is used for setting between 2 and 11 outputs. It can be controlled both by control inputs or by the operator.


OR (E1/UNACK, E0/UNACK, MAN/UNACK, AUT/UNACK, LOCK/UNACK, R1/UNACK,R0/UNACK, SET/UNACK, RES/UNACK, OPL/UNACK,OPHP/UNACK, SETD/UNACK, RESD/UNACK,INHI/UNACK, I1/UNACK, I2/UNACK, I3/UNACK,I4/UNACK)

<Tag>.IST/ALARM

Function fault, alarm signal pending (ER)

(ER/ALARM)

<Tag>.IST/UNACK

Function fault, alarm signal pending, error status not yet acknowledged (ER)

(ER/UNACK)


320 3BDD011741-600 A


Configuration

The MelodySel automation class displays the preselection from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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 following figures show the preselection 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 blockFig.: Monitoring block – interface to Composer and 800xA Process Portal


3BDD011741-600 A 321


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


To permit the exchange of process signals between AC 870P / Melody and 800xA Process Portal the function block connections on the monitor function block must be connected to the function blocks for the binary memory in AC 870P / Melody.





322 3BDD011741-600 A

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


Event typical











3BDD011741-600 A 323







For the STA function block connection in the MelodySel automation class, the event typicals MZ1, MZ2, MZ3 and MZ4 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 MZ1. The signaling behavior can be adjusted on a project-specific basis.

Table: Event typical MZ1

NameBrief Desc.

Explanatory text

MZ1 MZ1 Preselection 1, 2, …


0 SEL_1


63 SEL1 5

64 SEL2 5

65 SEL3 5


324 3BDD011741-600 A

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 sub-variant (e. g. SEL_1) referred to by the event typical. The sub-variant is stored in Importer for 800xA Process Portal).

Structure of a sub-variant using the example of SEL_1. The status texts and the alias can be adjusted on a project-specific basis.

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

66 SEL4 5

67 SEL5 5

68 SEL6 5

69 SEL7 5

70 SEL8 5

71 SEL9 5

72 SEL10 5

73 SEL11 5

49 OPL 5

51 ER 5


SEL1 XA83 01 (01)

SEL2 XA84 02 (02)

SEL3 XA85 03 (03)

SEL4 XA86 04 (04)

SEL5 XA87 05 (05)

SEL6 XA88 06 (06)

SEL7 XA89 07 (07)


3BDD011741-600 A 325

Automation class

Structure

The following table describes the structure of the automation class for MelodySel preselection.

Table: Structure of the MelodySel automation class

SEL8 XA90 08 (08)

SEL9 XA91 09 (09)

SEL10 XA92 10 (10)

SEL11 XA93 11 (11)

OPHP XA18 HighPrioOp (HighPrioOp)

CMDAC

OPL XA19 OperLock (OperLock)



Melodydata type

MelodyI/O


ACTUAL Status Integer (w) Packed Boolean

I X

IST/ALARM Bool

IST/UNACK Bool

SEL1 Unit 1 Bool (w) X Operator action





326 3BDD011741-600 A








ER Fault Bool


Bool




Bool

UNIT Pre-selected unit

Integer (w)

CMD+ Unit command +


CMD- Unit command –




O X Computer mode


3BDD011741-600 A 327

Legend for columns:


ATOMREF


ATOMREF


ATOMREF


ATOMREF


I X


I X


I X


I X

Atom Atom name









328 3BDD011741-600 A

Control

The operator actions for the MelodySel preselection is converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in AC 870P / Melody.The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.


CommandsOperate IT Process Portal:

Melody control code

Effect:

SEL1/SIG 0x00018003H Unit 1 preselection









SEL10/SIG 0x000a8003H Unit 10 preselection

SEL11/SIG 0x000b8003H Unit 11 preselection


CMD+/SIG 00000083H Incremental adjustment to “higher” units

CMD-/SIG 00000103H Decremental adjustment to “lower” units

Section 9 Melody Automation Classes Melody SFC – Sequence control

3BDD011741-600 A 329

Melody SFC – Sequence control

Features

The sequence control (MelodySFC) automation class allows pre-configured sequence control from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

Sequence control meets the IEC 1131-3 definitions and ISA-S88 standard.

A selection can be made from several configured faceplates, as well as a structure diagram with the option of calling up action and transition diagrams.

Configuration

The MelodySFC automation class displays the sequence control from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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.



330 3BDD011741-600 A


The figures below show the function blocks for the individual control function in Composer. The figures show a monitoring block with the interface to Composer and 800xA Process Portal, as well as a function block with integrated monitoring block.

Monitoring block – interface to Composer and 800xA Process Portal


To permit the exchange of process signals between AC 870P / Melody and 800xA Process Portal, the function block connections on the monitor function block must be connected to the function blocks for an individual control function in AC 870P / Melody.


3BDD011741-600 A 331


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






332 3BDD011741-600 A

Event typical
















For the STA function block connection in the MelodySFC automation class, the event typicals MK1, VSF1 and VSF2 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.


3BDD011741-600 A 333

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

Table: Event typical MK1

NameBrief Desc.

Explanatory text

MK1 MK1 Sequence control


160 SFC_1


74 E1 5

75 E0 5

6 R1 5

7 R0 5

8 P1 5

9 P0 5

10 OL1 5

11 OL0 5

16 STP 5

18 EFCR 5

19 EF1 5

20 EF0 5

23 EF1CR 3

24 EF0CR 3

25 EF1P0 3

26 EF0P1 3

27 RF1 3

28 RF0 3


334 3BDD011741-600 A

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 sub-variant (e. g. SFC_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 SFC_1. The status texts and the alias can be adjusted on a project-specific basis.

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

34 NSTR 5

32 PST 5

35 MAN 5

36 AUT 5

37 LOCK 5

38 INHI 5

39 KM1 5

40 KM2 5

41 KM3 5

42 KM4 5

49 OPL 5

76 CMD1 5

77 CMD0 5

51 ER 5


E1 XA01 On (On)

E0 XA02 Off (Off)

KM1 XM11 TippMode 1 (TippMode 1)



3BDD011741-600 A 335



CMD1 XA07 Command 1 (Command 1)

CMD0 XA08 Command 0 (Command 0)






P1 XA31 Protect 1 (Protect 1)

P0 XA32 Protect 0 (Protect 0)

PST XM43 PStop (PStop)


CMDAC

OPL XM19 OperLock (OperLock)


HLD Hold (Hold)

BRKM BrKeyMode (BrKeyMode)



STP XA09 Stop (Stop)


EFCR XM09 EF_Cri (EF_Cri)

EF1 XM07 EF1 (EF1)

EF0 XM08 EF0 (EF0)



NSTR XM20 NewStartTi (NewStartTi)


EF0CR XN62 EF0_Cri (EF0_Cri)


336 3BDD011741-600 A

Automation class

Structure

The following table describes the structure of the automation class for MelodySFC sequence control.

Table: Structure of the MelodySFC automation class


EF1CR XN61 EF1_Cri (EF1_Cri)


Melodydata type

MelodyI/O



I X

IST/ALARM

Bool

IST/UNACK

Bool

IST/FL12 Bool

IST/FL18 Bool

IST/FL02 Bool

IST/FL08 Bool

E1 End position 1 Bool

E0 End position 0 Bool

KM1 Keying mode 1 Bool (w) X Key mode




CMD1 Activate command Bool (w) X Operator action


3BDD011741-600 A 337




OMN Manual command Bool (w) Extended Boolean

O X Computer mode


OAU Automatic command


O X Computer mode

LOCK Lock Bool (w) X Lock operator mode

R1 Release 1 Bool

R0 Release 0 Bool

P1 Protective action 1 Bool

P0 Protective action 0 Bool

PST Protection stop Bool

ER Fault Bool


Bool




Bool

HLD Stop Bool X Operator action priority

OHLD Stop command Bool (w) Extended Boolean

O X Computer mode

BRKM Branching Bool (w) X Key mode



338 3BDD011741-600 A


O X Computer mode



O X Computer mode

STP Stop Bool (w) X Operator action

OCS Stop command Bool (w) Extended Boolean

O X Computer mode

RES Reset memory Bool (w) X Reset

ORES Reset command Bool (w) Extended Boolean

O X Computer mode

END End Bool (w) X Operator action priority

OEND End command Bool (w) Extended Boolean

O X Computer mode

INHI Operating modeS/O lock

Bool

OIN Inhibit Bool (w) Extended Boolean

O X Computer mode

EFCR End position error Bool

EF1 End position error 1

Bool

EF0 End position error 0

Bool

EF1CR End position error 1, missing criteria

Bool


3BDD011741-600 A 339

EF0CR End position error 0, missing criteria

Bool


Bool


Bool

RF1 Execution time error 1

Bool

RF0 Execution time error 0

Bool

NSTR Restart time reached

Bool


OPSC Sequence control operation


O X Computer mode

OCLK Activate timer function


O X Computer mode

TRE Repeat time Duration (w) Long duration

I X X Setpoint control

OTRE Repeat time (target)

Duration (w) Long duration

O X Computer mode

TNS Restart time Time (w) Clock I X X Setpoint control

OTNS Restart time (setpoint)

Time (w) Clock O X Computer mode

TLS Last start time Time Clock I X

TRC Execution time Duration Long duration

I X

SST1 Step status branch 1

Uint Packed Boolean

I X


Uint Packed Boolean

I X


340 3BDD011741-600 A


Uint Packed Boolean

I X


Uint Packed Boolean

I X


Uint Packed Boolean

I X


Uint Packed Boolean

I X


Uint Packed Boolean

I X


Uint Packed Boolean

I X

STR1 Transition status, alternative 1


I X



I X



I X



I X



I X



I X



I X



I X



I X



I X


3BDD011741-600 A 341



I X



I X



I X



I X



I X



I X

OPIDX Transition nominal word

Integer (w) Integer O X Key mode

TRS1 Step execution time in branch 1

Duration Short duration

I X



I X



I X



I X



I X



I X



I X



I X

TRW1 Remaining waiting time for step in branch 1


I X


342 3BDD011741-600 A



I X



I X



I X



I X



I X



I X



I X

TRM1 Remaining monitoring time for step in branch 1


I X



I X



I X



I X


3BDD011741-600 A 343



I X



I X



I X



I X


I X


I X


I X


I X


I X


I X

CRT011 Transition criteria, alternative 1


I X



I X



I X



I X



I X


344 3BDD011741-600 A



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X


3BDD011741-600 A 345



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X


346 3BDD011741-600 A



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X



I X


I X


I X


I X


I X


3BDD011741-600 A 347

Legend for columns:

Control

The operator actions for SFC sequence control is converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in AC 870P / Melody.The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.


Atom Atom name









Melody control code

Effect:


OPL/SIG 0000000aH Set/reset general operator input inhibit






STP/SIG 00000202H “STOP” commands


348 3BDD011741-600 A

Calculated atoms


BRA/SIG 00006002H “Branch” commands

RES/SIG 00040002H “Reset” command

KM1/SIG 10002002H “Keying mode 1” command






OR (IST/SIG, TRE/SIG, TNS/SIG, TLS/SIG,TRC/SIG, SST1/SIG, …, SST8/SIG, STR1/SIG, …, STR16/SIG, TRS1/SIG, …, TRS8/SIG, TRW1/SIG, …, TRW8/SIG, TRM1/SIG, …, TRM8/SIG, CR1/SIG, …, CR6/SIG, CRT011/SIG, …, CRT163/SIG, I1/SIG, I2/SIG, I3/SIG, I4/SIG)


3BDD011741-600 A 349


OR (E1/ALARM, E0/ALARM, KM1/ALARM,KM2/ALARM, KM3/ALARM, KM4/ALARM,CMD1/ALARM, CMD0/ALARM, MAN/ALARM,AUT/ALARM, LOCK/ALARM, R1/ALARM,R0/ALARM, P1/ALARM, P0/ALARM, PST/ALARM, ER/ALARM, OPL/ALARM, OPHP/ALARM,HLD/ALARM, IC1/ALARM, IC0/ALARM,STP/ALARM, INHI/ALARM, EFCR/ALARM,EF1/ALARM, EF0/ALARM, EF1CR/ALARM,EF0CR/ALARM, EF1P0/ALARM, EF0P1/ALARM, RF1/ALARM, RF0/ALARM, NSTR/ALARM,I1/ALARM, I2/ALARM, I3/ALARM, I4/ALARM)


350 3BDD011741-600 A


OR (E1/UNACK, E0/UNACK, KM1/UNACK,KM2/UNACK, KM3/UNACK, KM4/UNACK,CMD1/UNACK, CMD0/UNACK, MAN/UNACK,AUT/UNACK, LOCK/UNACK, R1/UNACK,R0/UNACK, P1/UNACK, P0/UNACK, PST/UNACK, ER/UNACK, OPL/UNACK, OPHP/UNACK,HLD/UNACK, IC1/UNACK, IC0/UNACK,STP/UNACK, INHI/UNACK, EFCR/UNACK,EF1/UNACK, EF0/UNACK, EF1CR/UNACK, EF0CR/UNACK, EF1P0/UNACK, EF0P1/UNACK, RF1/UNACK, RF0/UNACK, NSTR/UNACK,I1/UNACK, I2/UNACK, I3/UNACK, I4/UNACK)

<Tag>.IST/ALARM

Function fault, alarm signal pending(ER||RF0||RF1||EF0||EF1)

OR (ER/ALARM, RF0/ALARM, RF1/ALARM,EF0/ALARM, EF1/ALARM)

<Tag>.IST/UNACK

Function fault, alarm signal pending, error status not yet acknowledged(ER||RF0||RF1||EF0||EF1)

OR (ER/UNACK, RF0/UNACK, RF1/UNACK,EF0/UNACK, EF1/UNACK)

<Tag>.IST/FL12 Error status in End position 1(RF1||EF1)

OR (RF1/SIG, EF1/SIG)

Section 9 Melody Automation Classes MelodySFlagx – Single flag

3BDD011741-600 A 351

MelodySFlagx – Single flag

Features

The single flag (MelodySFlagx) automation class allows an operator controllable time and data memory from AC 870P / 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.

SFlag automation classes are provided for all the data types available in AC 870P / Melody (real, integer, duration, Boolean, clock and packed Boolean).

A configured faceplate for each data type is available for selection.

Configuration

The MelodySFlagx automation classes display the operator controllable time and data memory from the AC 870P / Melody automation system in a variable structure in Operate IT Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for Operate IT Process Portal and the AC 870P / 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.

<Tag>.IST/FL18 Sequence control is running in on programme(CMD1 & !E1)


<Tag>.IST/FL02 Error status in End position 0(RF0||EF0)

OR (RF0/SIG, EF0/SIG)

<Tag>.IST/FL08 Sequence control is running in off programme(CMD0 & !E0)



352 3BDD011741-600 A



The figures below show the function blocks for the operator controllable register blocks in Composer.All function blocks have an integrated monitoring block for the link to 800xA Process Portal.


Boolean SFlag Clock SFlag Duration SFlag

Integer SFlag Long duration SFlag Packed Boolean SFlag

Real SFlag


3BDD011741-600 A 353



Event typical

















354 3BDD011741-600 A

Automation class

Structure

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

ClassAtom name

DescriptionOperate IT

data typeMelodydata type

MelodySFlagB I Boolean input PSigBool Boolean

O Boolean output

MelodySFlagC XC Clock input PSigTime Clock

YC Clock output

MelodySFlagD XD Duration input PSigDuration Duration

YD Duration output

MelodySFlagI XI Integer input PSigInt Integer

YI Integer output

MelodySFlagL XL Long duration input

PSigDuration Long duration

YL Long duration output

MelodySFlagP IP Packed Boolean input

PSigPBool Packed Boolean

OP Packed Boolean output

MelodySFlagR X Real input PSigReal Real

Y Real output


3BDD011741-600 A 355

Table: Structure of the MelodySFlagB automation class

Legend for columns:

Control

All operator actions for the SFlagx automation classes 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.

Atom DescriptionOPC

data type

Melodydata type

MelodyI/O


O Output value to O

Bool (w) Boolean I X X Operator action

I Boolean input Bool (w) Boolean O X Computer mode

Atom Atom name









356 3BDD011741-600 A

Calculated atoms



<Tag>.BAD/SIG


SFALGB:(O/SIG)SFLAGC:(YC/SIG)SFLAGD:(YD/SIG)SFLAGI:(YI/SIG)SFLAGL:(YL/SIG)SFLAGP:(OP/SIG)SFLAGR:(Y/SIG)


SFLAGB:(O/ALARM)


SFLAGB:(O/UNACK)

Section 9 Melody Automation Classes MelodySwClock – Calendar and timing function

3BDD011741-600 A 357

MelodySwClock – Calendar and timing function

Features

The calendar and timing function (MelodySwClock) automation class allows calendar and timing function from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The pre-configured automation function in AC 870P / Melody is intended for general applications, which include time-controlled periodic switching operations. The internal calendar function allows periodic switching operations of seconds, minutes, hours, days, weeks, months or even years to be set.


Configuration

The MelodySwClock automation class displays the calendar and timing function from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.The automation class displays the time variables, the status information and the repetition counter.Signals can be sent by the individual binary data items in the status STA.

This standard display is configured by the connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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 figures below show the function blocks for the calendar and timing function in Composer. The function block has an integrated monitoring block for the link to 800xA Process Portal.


358 3BDD011741-600 A




Event typical




Fig.: Melody function block with integrated monitor





3BDD011741-600 A 359













For the STA function block connection in the MelodySwClock automation class, the event typical MT2 is 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 MT1. The signaling behavior can be adjusted on a project-specific basis.


360 3BDD011741-600 A

Table: Event typical MT2

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 sub-variant (e. g. SWCLOCK_1) referred to by the event typical. The sub-variant is stored in Importer for 800xA Process Portal).

Structure of a sub-variant using the example of SWCLOCK_1. The status texts and the alias can be adjusted on a project-specific basis.

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

NameBrief Desc.

Explanatory text

MT2 MT2 Calendar and timing function


0 SWCLOCK_1


112 AKO 10

203 O 10

204 REP 10

205 DI 10


AKO AKO Output set (Output set)

O O RepFct act (RepFct act)

REP REP Disturban. (Disturban.)

DI DI AccessLock (AccessLock)


3BDD011741-600 A 361

Automation class

Structure

The following table describes the structure of the automation class for the MelodySwClock calendar and timing function.

Table: Structure of the MelodySwClock automation class


MelodyI/O



I X

STA/ALARM

Bool

STA/UNACK

Bool

O Boolean output Bool

REP Repeat function active

Bool

DI Fault Bool

AKO Access blocked Bool (w) X Lock operator access



STDT Standard time Bool

DLT Summertime Bool

SRPO Per second repetition


MIRPO Per minute repetition


HRPO Hourly repetition



362 3BDD011741-600 A

Legend for columns:

DRPO Daily repetition Bool (w) X Operator action

WRPO Weekly repetition


MRPO Monthly repetition


YRPO Yearly repetition


ACK Bool (w) X Acknowledge



O X Computer mode

RFO Repeat function Integer (w) Integer I X X Setpoint control

RF Execution time error

Integer (w) Integer O X Computer mode

TONO Restart time Time (w) Clock I X X Setpoint control

TON Restart time Time (w) Clock O X Computer mode

TSON Last start on Time (w) Clock I X X Setpoint control

Atom Atom name






3BDD011741-600 A 363

Control

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






Melody control code

Effect:

ACK/SIG 00000800H Error acknowledgement



SRPO/SIG 02000000H Activate per second repetition

MIRPO/SIG 04000000H Activate per minute repetition

HRPO/SIG 08000000H Activate hourly repetition

DRPO/SIG 10000000H Activate daily repetition

WRPO/SIG 20000000H Activate weekly repetition

MRPO/SIG 40000000H Activate monthly repetition

YRPO/SIG 80000000H Activate yearly repetition


364 3BDD011741-600 A

Calculated atoms




OR (STA/SIG, RFO/SIG, TONO/SIG, TSON/SIG)


OR (O/ALARM, REP/ALARM, DI/ALARM, AKO/ALARM)


OR (O/UNACK, REP/UNACK, DI/UNACK, AKO/UNACK)

<Tag>.IST/ALARM Function fault, alarm signal pending (DI)

DI/ALARM

<Tag>.IST/UNACK Function fault, alarm signal pending, error status not yet acknowledged (DI)

DI/UNACK

Section 9 Melody Automation Classes MelodyTCount – Time and pulse counter

3BDD011741-600 A 365

MelodyTCount – Time and pulse counter

Features

The time and pulse counter (MelodyTCount) automation class allows a pre-configured time and pulse counter from AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The pre-configured automation function in AC 870P / Melody has the functions of starting value definition, time counting, pulse counting and alarm generation for time period and pulse counting.


Configuration

The MelodyTCount automation class displays the time and pulse counter function from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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 manual AC 70P/Melody – Engineering Tool Composer, Operation (2PAA101133*).


366 3BDD011741-600 A


The figures below show the function blocks for the time and pulse counter function in Composer. The function blocks have an integrated monitoring block for the link to 800xA Process Portal.




TP_CNT-00





3BDD011741-600 A 367

Event typical
















For the STA function block connection in the MelodyTCount automation class, the event typical MT1 is defined as standard in Composer.The event typical refers to a sub-variant, which describes the structure and status texts for the packed Boolean signal.


368 3BDD011741-600 A

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

Table: Event typical MT1

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 sub-variant (e. g. TCOUNT_1) referred to by the event typical. The sub-variant is stored in Importer for 800xA Process Portal).

Structure of a sub-variant using the example of TCOUNT_1. The status texts and the alias can be adjusted on a project-specific basis.

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

NameBrief Desc.

Explanatory text

MT1 MT1 Time and pulse counter


0 TCOUNT_1


112 AKO 10

198 RSO 10

199 TUP 10

200 TDOWN

10

201 PUP 10

202 PDOWN

10


TUP TUP T up Cnt (T up Cnt)


3BDD011741-600 A 369

Automation class

Structure

The following table describes the structure of the automation class for the MelodyTCount analog output function.

Table: Structure of the MelodyTCount automation class

TDOWN TDOWN T down Cnt (T down Cnt)

PUP PUP P up Cnt (P up Cnt)

PDOWN PDOWN P down Cnt (P down Cnt)

AKO AKO AccessLock (AccessLock)

LVTR LTR T Limit (T Limit)

LVPR LPR P Limit (P Limit)

RSO RSO Reset Act (Reset Act)


Melodydata type

MelodyI/O



I X

TUP Time upwards

Bool

TDOWN Time downwards

Bool

PUP Pulse upwards

Bool

PDOWN Pulse downwards

Bool

AKO Access locked



370 3BDD011741-600 A


Bool (w) X LockOperator Access

LTR Time counter limit value reached

Bool

LPR Pulse counter limit value reached

Bool

RSO Reset active Bool

QOR Reset time/pulse


X Reset


Bool (w) Packed Boolean

O X Computer mode

TIME Time Double Real I X

TIME/ALARM

Bool

TIME/UNACK

Bool

TOLD Time, last period

Double Real I X

SVTO Time, initial value


SVT Time, initial value


LVTO Time limit value

Double (w) Real I X X High limits priority

LVT Time limit value

Double (w) Real O Computer mode


3BDD011741-600 A 371

Legend for columns:

LVTR Time limit reached


PCNT Pulse Integer Integer I X

PCNT/ALARM

Bool

PCNT/UNACK

Bool

POLD Pulse, last period

Integer Integer I X

SVPO Initial pulse value

Integer (w) Integer I X X Setpoint control

SVP Initial pulse value


LVPO Pulse limit value

Integer (w) Integer I X X High limits priority

LVP Pulse limit value


LVPR Pulse limit reached


I X

RST Reset Bool (w) Extended Boolean

O X Reset

Atom Atom name






372 3BDD011741-600 A

Control

The operator actions for the TCOUNT time and pulse counter function are converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in AC 870P / Melody.The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.


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..



Write access Atom requires the access rights detailed for write access.


Melody control code

Effect:



QOR/SIG 80008000H Reset time and pulse counter



OR (STA/SIG, TIME/SIG, TOLD/SIG, SVTO/SIG, LVTO/SIG, PCNT/SIG, POLD/SIG, SVPO/SIG, LVPO/SIG, LVPR/SIG)


3BDD011741-600 A 373


OR (TUP/ALARM, TDOWN/ALARM, PUP/ALARM, PDOWN/ALARM, AKO/ALARM, RSO/ALARM, LVTR/ALARM, LVPR/ALARM)


OR (TUP/UNACK, TDOWN/UNACK, PUP/UNACK, PDOWN/UNACK, AKO/UNACK, RSO/UNACK, LVTR/UNACK, LVPR/UNACK)

<Tag>.TIME/ALARM

Time counter limit value violation with alarm signal pending

LVTR/ALARM

<Tag>.TIME/UNACK

Time counter limit value violation with alarm signal pending, error status not yet acknowledged

LVTR/UNACK

<Tag>.PCNT/ALARM

Pulse counter limit value violation with alarm signal pending

LVPR/ALARM

<Tag>.PCNT/UNACK

Pulse counter limit value violation with alarm signal pending, error status not yet acknowledged

LVPR/UNACK

MelodyTotal – Quantity value acquisition Section 9 Melody Automation Classes

374 3BDD011741-600 A

MelodyTotal – Quantity value acquisition

Features

The quantity acquisition (MelodyTotal) automation class allows pre-configured quantity acquisition in AC 870P / Melody to be displayed in a data structure in 800xA Process Portal.

The pre-configured automation function in AC 870P / Melody is used for highly accurate integration/summation of analog or binary input signals. Summation can take place continuously or be reset periodically.

Alongside the actual summation function, functions such as replacement and alternative value processing and limit value checking are implemented.


Configuration

The MelodyTotal automation class displays the quantity acquisition function from the AC 870P / Melody automation system in a variable structure in 800xA Process Portal.This standard display is configured by connection of the process signals in Composer.As part of code generation for Operations, configuration data is provided for 800xA Process Portal and the AC 870P / 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 figures below show the function blocks for the quantity acquisition function in Composer. The function blocks have an integrated monitoring block for the link to 800xA Process Portal.

The connections to the AC 870P / Melody function block identify input and output signals in AC 870P / Melody.


3BDD011741-600 A 375

Data is exchanged between AC 870P / Melody and 800xA Process Portal, through the internal connections of the AC 870P / Melody function block with a monitoring block inside the yellow backed case.


ANTOT-00 – Real analog quantity value

ANTOTP-00 – Real analog quantity value, periodic

BINTOT-00 – Binary quantity value BINTOTP-00 – Binary quantity value, periodic





376 3BDD011741-600 A


Event typical

















3BDD011741-600 A 377

For the STA function block connection in the MelodyTotal automation class, the event typicals VMT1 and VTOT 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 VMT1. The signaling behavior can be adjusted on a project-specific basis.

Table: Event typical VAM1

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 sub-variant (e. g. TOTAL_1) referred to by the event typical. The sub-variant is stored in Importer for 800xA Process Portal).

Structure of a sub-variant using the example of TOTAL_1. The status texts and the alias can be adjusted on a project- specific basis.

NameBrief desc.

Explanatory text

VMT1 VMT1 Quantity value calculation


0 TOTAL_1


110 SUO 10

111 ATO 10

112 AKO 10

197 REO 10

198 RSO 10

189 AHHN 10

190 AHN 10


378 3BDD011741-600 A

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

Automation class

Structure

The following table describes the structure of the automation class for the MelodyTotal quantity acquisition function.

Table: Structure of the MelodyTotal automation class


SUS SUS

SUO SUO SV Act (SV Act)



REO REO Rel Act (Rel Act)

RSO RSO Reset Act (Reset Act)



AHHO AHHO

AHO AHO


Melodydata type

MelodyI/O



I X


Bool


3BDD011741-600 A 379


Bool X Lock operator access





AKO Access blocked Bool (w) X Lock operator access



REO Release active Bool

RSO Reset active Bool


AHN No H limit Bool



QOR Reset time/pulse Bool (w) X Reset



O X Computer mode

QY Intermediate value


QY/ALARM

Bool

QY/UNACK

Bool



380 3BDD011741-600 A

TPY Period length Duration (w) Short duration

I X X Setpoint control

TPV Period length Duration (w) Short duration

O X Computer mode

TOPA Execution time for current period

Double Real I X

TPA Execution time for current period


I X

QOY Period measured value

Double Real I X

AHHY HH limit signal Bool Extended Boolean

I X


Double (w) X X High limits priority


AHY HH limit signal Bool Extended Boolean

I


Double (w) X X High limits



ATOMREF ATOMREF


ATOMREF ATOMREF


ATOMREF ATOMREF


ATOMREF ATOMREF



3BDD011741-600 A 381

Legend for columns:

Control

The operator actions for the MelTotal quantity acquisition function is converted to a hexadecimal code in 800xA Process Portal and transmitted to the processing function in AC 870P / Melody.





I X


I X


I X


I X

Atom Atom name









382 3BDD011741-600 A

The meaning of the individual items of information in the operator action can be found in the associated function block descriptions in AC 870P / Melody.


Calculated atoms


800xA Process Portal commands

Melody control code

Effect:



SUR/SIG 80008000H Reset the period intermediate value





OR (STA/SIG, QY/SIG, QOY/SIG, TPY/SIG, TOPA/SIG, TPA/SIG, AHHY/SIG, AHY/SIG,ALY/SIG, ALLY/SIG, X1/SIG, X2/SIG, X3/SIG,X4/SIG, I1/SIG, I2/SIG, I3/SIG, I4/SIG)


OR (SUO/ALARM, ATO/ALARM, AKO/ALARM, REO/ALARM, RSO/ALARM, AHHN/ALARM, AHN/ALARM, AHHY/ALARM, AHY/ALARM,I1/ALARM, I2/ALARM, I3/ALARM, I4/ALARM)


3BDD011741-600 A 383


OR (SUO/UNACK, ATO/UNACK, AKO/UNACK, REO/UNACK, RSO/UNACK, AHHN/UNACK, AHN/UNACK, AHHY/UNACK, AHY/UNACK,I1/UNACK, I2/UNACK, I3/UNACK, I4/UNACK)

<Tag>.QY/ALARM


OR (REO/ALARM, AHHY/ALARM, AHY/ALARM)

<Tag>.QY/UNACK


OR (REO/UNACK, AHHY/UNACK, AHY/UNACK)


384 3BDD011741-600 A

3BDD011741-600 A 385

Section 10 Special Functions

A sequence control is designed in Composer. Composer provides the SFC Editor to design the petri network of the steps and transitions.

The overall behavior and the type of SFC application is defined in the SFC main control module. The corresponding engineering is done in the CFC Editor of Composer. Transitions and actions are designed in the Composer CFC function chart editor.

For displaying the SFC structures the 800xA-System provides a “SFC Viewer”. The “SFC Viewer” is an aspect system that allows the operator to displaying SFC structures with live data for active steps and transitions on operator workplaces without additional installation of a controller configuration tool.

For more details about the SFC viewer refer to Industrial IT System 800xA- Basic Operation (3BSE036903).

In addition to the standard 800xA SFC viewer functionality the SFC viewer for Melody allows to enter links in the Action window.

Not supported with AC 870P / Melody is the use of the following 800xA SFC viewer functionality.

- Subsequences

- Blocking transitions

IDF Viewer Section 10 Special Functions

386 3BDD011741-600 A

The following figure shows the SFC viewer aspect from operators point of view.

IDF ViewerThe following automation classes have an aspect for viewing the configured control conditions (Release and Protection): Individual Drive Function, Control Loop modules, Operable Binary Flag, Dosing Function and Change-Over Automatic.

The aspect is named “Control Conditions” except for the Individual Drive Function which uses the traditional name “IDF Viewer” (see example in Figure 81). The functionality is also available via the context menu entry “Control Conditions” which allows the operator to select a specific release condition.

Figure 80. SFC Viewer Aspect to Open Diagram in Zoom Level 1

Section 10 Special Functions IDF Viewer

3BDD011741-600 A 387

When selecting the IDF Viewer aspect the current criteria of the IDF will be displayed (see example in Figure 81).

Figure 81. IDF Viewer Aspect

The default presentation of the criteria is the ‘List form’. The change between the list form and the ‘Graph form’ can be done by selecting the List/Graph button. The button text shows either List or Graph, i.e. the alternative, selectable presentation form.

The change between the views, in case of the IDF-viewer of the Control Conditions (release conditions) can be done either via menu as described above or via the change button .

IDF Viewer Section 10 Special Functions

388 3BDD011741-600 A

After the selection of a release condition a filtered list appears showing all criteria missing at the moment (see Figure 82).

To show all criteria (also the available) Click the Reset button.

Figure 82. Display of Missing IDF Criteria

In some cases when negations are used in logic, the filtered list may not be correct. We recommend to use the Graph View.

The usage of the object names opens the option of direct navigation.

This means, a double click on the criteria in the Description text field (List view) or a double click on the criteria in the Signal text field (Graphic view) leads to a call of the belonging object according to its default settings, normally the faceplate. The missing criteria can then directly be influenced via the object.

Section 10 Special Functions Data Exchange to AC 800M

3BDD011741-600 A 389

Data Exchange to AC 800MThe 800xA-System supports mixed systems of AC870P, Melody and AC800M. For such a mixed system there are following conditions:

• AC 870P / Melody and AC800M may use the same aspect server.

• AC 870P / Melody and AC800M use independent connectivity server.

• Time synchronization has to be done independently.

If AC800M is in certain plant areas in parallel use to AC870P Controller or Melody Controller it might be helpful to exchange some cross controller process signals.

Because it is uncommon to close loops across different controller technologies therefore only a certain amount of non-mission critical data needs to be exchanged.

If AC 870P / Melody and AC800M work in the same system then the connectivity servers have to run in own service groups.

Data Exchange to AC 800M Section 10 Special Functions

390 3BDD011741-600 A

800xA for AC 870P / Melody as well as AC800M Connect provide an OPC server. Both OPC servers interface the same OPC server and work in a global unique OPC name space. These data might be exchanged on pure OPC level.

The Server concept allows different standard OPC servers to run in the context of one common server (the AfwServer). This common server provides one set of stan-dard OPC interfaces. The OPC Server covers the name resolution and therefore the client application doesn’t need to know which data is accessible via which applica-tion dedicated OPC server.

This allows to exchange data either via the “Property Translation Aspect” or via a OPC data pump, which also available as an ABB product.

Figure 83. OPC Server Connection

Section 10 Special Functions Additional Connection to OperateIT B or Maestro UX

3BDD011741-600 A 391

Additional Connection to OperateIT B or Maestro UX800xA for AC 870P / Melody is able to coexist with other operations systems like OperateIT Process Portal B or Maestro UX.

Fieldbus SupportComposer contains the same FDT frame application software as the Fieldbus Builder PROFIBUS/HART. So, IndustrialIT 800xA AC 870P / Melody includes full fieldbus support. The DTMs are hosted in a so-called “FDT Base Container”.

As a comprehensive DCS engineering tool Composer exploits full FDT/DTM functionality.

AC870P or Melody coupling units support two connections for alarms and events. In case of a redundant connectivity the event connection needs to be limited to one console type.

Figure 84. Industrial IT AC 870P / Melody: FDT 1.2 Support

Security Section 10 Special Functions

392 3BDD011741-600 A

For pure GSD based devices Composer incorporates a GSD based so called Default-DTM to configure the device and to connect to the AC 870P / Melody control applications. Working on a GSD base often requires the device manual to set up the correct settings.

Composer incorporates an implicit automatic calculation of the PROFIBUS setting, so the user does not bother with all the PROFIBUS business to be considered to calculate the correct bus parameters.

For further details refer to the Composer documentation (AC 870P / Melody – Engineering Tool Composer, User Manual (2PAA101135*)).

SecurityThe 800xA-System requires an own Windows Domain or Sub Domain. User rights are managed according to the Windows standards by assigning user to groups and determine user rights at login time.

Security may be defined on OPC property level. In 800xA for AC 870P / Melody the different OPC items are set to a default access permission depending on the semantic of the item. 800xA for AC 870P / Melody provides basic settings for read, write, operate permission.

800xA for AC 870P / Melody uses security as provided by the 800xA-System.

Composer Supports only FDT 1.2

Section 10 Special Functions Batch Support

3BDD011741-600 A 393

Batch Support

800xA Batch for AC 870P / Melody

800xA Batch for AC 870P / Melody is an evolution for the Maestro UX - SymBatch Product and supports the migration of the installed base towards 800xA solutions. The current state model of the SymBatch SFCs is compensated on the batch manager level so that for migration of SymBatch to 800xA Batch is no need to modify the controller or the control application.

For support of 800xA Batch in association with AC 870P / Melody there is no explicit Melody Batch Extension necessary.

The configuration for the batch processing are created in Composer and are linked to the batch environment by means of assignments. For each unit a Batch configuration file can generate in Composer and passed to the Melody uploader. This is the link between the batch environment of 800xA Batch Management and the AC 870P / Melody automation.

Figure 85. IndustrialIT AC 870P / Melody - Batch Support

800xA Batch for AC 870P / Melody Section 10 Special Functions

394 3BDD011741-600 A

For 800xA Batch in association with AC 870P / Melody the sequence control block SC02-01 for AC 870P / Melody SFC’s will only be supported.

Figure 86. Sequence Control Block SC02-01 Extended

Figure 87. SFC structure with SC02-01

Section 10 Special Functions 800xA Batch for AC 870P / Melody

3BDD011741-600 A 395

The Batch Configuration data will be exported in Composer from the Functional Structure using the context menu on a functional unit of type Batch:

“Generate batch configuration”

Composer generates the XML-files on the \bin\ocs folder where the Melody Tag-Importer picks this file up and stores the content into the Configuration Server Database. A Tag-Importer log file can be found in the bin folder.

Figure 88. Principles of the interplay of 800xA Batch and Composer


396 3BDD011741-600 A

Based on the Composer Batch configuration-data, the TagImporter / Uploader automatically add a Batch Equipment aspect to the AC 870P / Melody Functional Unit Object and set the controller type automatically to “Melody”.

Figure 89. Batch Equipment Aspect for Functional Unit


3BDD011741-600 A 397

Parameters, which are not assigned to a phase, will be added as equipment attributes to the Batch Equipment Aspect. These parameters are of an OPC data type and the Default Value will contain the path to the OPC Datapoint. For equipment parameters there is only one OPC Datapoint and there won’t be any write validation.

Name: Parameter Name. In Composer named as “Batch Selector”,is composed from Alias Structure Name and Selector (Signal)

Figure 90. Equipment Attributes


398 3BDD011741-600 A

Description: Signal text as defined in Composer.

A Batch Phase Aspect will be added to a AC 870P / Melody SFC object if it is a Batch Phase. The Batch Phase Aspect can contain Phase parameters. Those will be configured also from the Uploader and the OPC Data point will be set.

Changes of parameter attributes in Composer will be performed only after commissioning and generation of Batch configuration data in Composer. The Default value will also be initialized. The Access level will not be touched.

The Configurator Admin Aspect displays wrong Numbers of “Total” and “Differences” of “Batch Units/Phases”. It could be possible that there are no differences since the last upload.

Figure 91. Batch Phase Aspect


3BDD011741-600 A 399

Name: Parameter Name. In Composer named as “Batch Selector”,is composed from Alias Structure Name and Selector (Signal)

Description: Signal text as defined in Composer.

Type: Signal type as defined in Composer.

Direction: Signal direction as defined in the basic function csv file. Parameters with the access method "In" (csv: w- write) are written bystart of the Batch Phase into the controller, parameter with the accessmethod "Out" (csv: r- read) are read at the end of the Batch Phase.Parameters with the access method "InOut" (csv: rw - read-write) arewritten by start of the Batch Phase and are read at the end.

Default: Default value, that will be written to the controller if it’s notinitialized from the recipe. First initialized value is the low limitvalue.

Low: low limit as defined in Composer

High: high limit as defined in Composer

Eng.Unit: Engineering unit as defined in Composer

Access Level: Access Level for the parameter

Basically text, limits and unit are taken from Signal, if not defined the values are taken from Process Point.

Changes of parameter attributes in Composer will be performed only after commissioning and generation of Batch configuration data in Composer. The Default value will also be initialized. The Access Level will not be touched.


400 3BDD011741-600 A

The Uploader add this phases to the Batch Equipment Aspect and set the alias name for phases using the name of the basic function.

Parameter Read back

Input Parameters are Batch Parameters that will be written via the Melody Phase Driver to the Melody OPC Control Connection Aspect. This could be any Melody Object Type; mainly these are Melody BFlags or Melody SFlags.

Figure 92. Batch Equipment Phase

The gereration of Batch configuration data in Composer during runnig recipes might be effectuate malfunction or abortion of the recipes.

Section 10 Special Functions Operational Issues

3BDD011741-600 A 401

The written value will be validated from the Melody Phase Driver, e.g. it writes to the input X/SIG and reads back from output Y/SIG and this ensures that the value is 100% written to the controller. This will be done before the Phase will be started

The Melody Phase Driver does not validate the given Limits nor is the Melody Server doing such validation. The limit validation will be done during configuration, not at runtime.

The Uploader determines the Readback Parameter using the Batch Parameter Definition Aspect on the Melody Object Type and configures the OPC Datapoint Out, which is used by the Phase Driver for write validation.

A write parameter can also be configured as In/Out. Such a parameter is written by the Phase Driver (using the OPC Datapoint In), validated (using OPC Datapoint Out) and read after the phase ends (using OPC Datapoint Out).

Operational Issues

Please consider the following operational issues:

1. Melody SFC delayed auto reset

If the SFC is configured in Composer to “auto reset” and the auto reset occurs during a redundancy switch over of the Batch Server, the auto reset is unnoticed by the Batch Server. The collection of output parameter will not happen by 800xA Batch because the redundant Batch Server does not know that the Phase was running. The Phase will continue to work after an auto reset or if the phase driver will get stuck if the SFC returns to initial state without being triggered by the phase driver. No impact has beend noticed in that case.

It is possible to configure the SymBatch SFC not automatically reset and/or not got automatically in AUT after reaching the end position.

2. Behaviour with short time Protection Stop (PST)

If a phase is Running or Holding and a Protection Stop intervention forces the SFC to stop, Batch displays the Stopping status only during the time the Protection Stop signal is active. If the Protection Stop disappears before the SFC reaches the status Stopped, Batch wrongly displays the phase as running or holding.

When the SFC reaches the status Stopped, the displayed status in Batch is correct again.

Event Concentrator - Filter out Melody Tracking Events Section 10 Special Functions

402 3BDD011741-600 A

3. Limit validations during configuration not at runtime

It could be possible that the Batch values written during Phase Start can be outside of the limits. This could happen if someone changes the range in the Composer. The parameter configuration will updated on Phase level from the Uploader but the limits on Recipe level remains with the old values. Batch Management validates the limits only during configuration, not at runtime.

Event Concentrator - Filter out Melody Tracking Events

The OA Type Events from Melody Server can be filtered to reduce the amount of Tracking and Auditrail Events generated from Batch.

Section 10 Special Functions Event Concentrator - Filter out Melody Tracking Events

3BDD011741-600 A 403

1. Create new EventGroupFilter or copy an existing one:

Figure 93. EventGroupFilter

Event Concentrator - Filter out Melody Tracking Events Section 10 Special Functions

404 3BDD011741-600 A

2. Give the new EventGroup Filter a name:

3. Uncheck the OA (Operator Action), this will filter out the OA Type Events from Melody Server to reduce the amount of Tracking and Audittrail Events generated from Batch.

Figure 94. EventGroupFilter - General

Figure 95. EventGroupFilter - Event Group

Section 10 Special Functions Information Manger

3BDD011741-600 A 405

4. Assign this Filters to the Client Event Concentrators:

Information MangerIndustrial IT 800xA Melody based works with the Information Manager as a standard OPC client.

Figure 96. EventGroupFilter - Event Concentrator

Information Manger Section 10 Special Functions

406 3BDD011741-600 A

3BDD011741-600 A 407

Section 11 Melody Simulation Events

The Melody Simulation Events component enables a Melody system in conjunction with 800xA to automatically create events in 800xA when a Melody engineer creates / changes / removes a simulation for a variable in the melody controller (using the Composer). In other words, any simulations created / changed or removed in the Composer Melody are visible and traceable in 800xA if this system extension is loaded and properly configured.

The Composer Melody will create the simulation files. The 800xA part will be installed with “800xA for Melody” and can be added to an 800xA system as a system extension.

Installation

System Extension

The system extension “Melody Simulation Events” will be installed as part of “800xA for AC 870P / Melody” and can be added to an 800xA system. The component will run as an 800xA service and can be started and stopped in the usual way.

Control Structure Section 11 Melody Simulation Events

408 3BDD011741-600 A

Control Structure

The system extension will add a node named “Melody Simulation Events” to the Control Structure. This object contains the aspects necessary to configure the 800xA service which processes the input files from Composer.

Figure 97. System Extension AC 870P / Melody Simulation Events

Figure 98. Melody Simulation Event node in Control Structure

Section 11 Melody Simulation Events Configuration

3BDD011741-600 A 409

Configuration

Simulation Events Settings Aspect

The Simulation Events Settings aspect will be used to configure the Operations working directory and the object in 800xA that will be the receiver of the events generated for simulations:

• Button “Test” checks the inserted values

• Button “Apply” stores the settings in aspect system

The aspect also provides the test functionality (Test send …, Test Parse …, …), it may help in case of problems.

Figure 99. Simulation Events Settings aspect

The aspect “Simulation Events Settings” should be operated on the same node where the Composer Melody puts the simulation files (the Melody ConfigServer node). On other nodes, not all the functions may be available.

SAC Data Source Aspect Section 11 Melody Simulation Events

410 3BDD011741-600 A

SAC Data Source Aspect

The SAC Data source aspect will be used to configure an 800xA service that automatically scans for simulation files and generates simulation events:

• Create a service group

• Specify the node on which the 800xA service should run

• Apply

It is recommended to run the simulation events service on the same node where the Composer puts the simulation files, the Melody Config Server.

Figure 100. SAC Data source aspect

Section 11 Melody Simulation Events Simulation Event Service

3BDD011741-600 A 411

Simulation Event Service

The SAC Data Source aspect will add the simulation events service to the service structure and start it. The service group or service provider can be used to start or stop the service.

If the simulation event service has started you will find the message “Melody/AC870P simulation event service is ready for scanning” in the System

Figure 101. Service Structure

Simulation Events Section 11 Melody Simulation Events

412 3BDD011741-600 A

Event List of the Melody Simulation Event object. Error messages can be found in this event list too.

Simulation Events

The simulation event service will create simple events of category System Status and send them to the configured receiver. The simulation events service puts the information into the fields “Message” and “Long Message”:

Figure 102. Melody Simulation Event object

Figure 103. Simulation event service

Section 11 Melody Simulation Events Error and Exception Handling

3BDD011741-600 A 413

Message: “action: process point: function block name: function block identifier: function block pin”

Long Message: “signal: station identifier: function diagram name: simulation type: simulation origin: date: time: simulation value: user”

Error and Exception Handling

The settings aspect will display error message on screen. The service component sends system messages to the Melody Simulation Events object to show errors.

Operations working directory

At the moment when an engineer creates, removes or changes a simulation, the composer automatically writes / appends this information in/to log files in special folders in the operations working directory. The simulation specific folders will be created from Composer. The operations working directory entered in the Simulation Events Settings aspect must match the entry in Composer project.

Example: operations working directory: “c:\Melody” on Melody Config Server node.

Composer Simulation Records

Switch on/off Support of Simulation Records

The creation of Composer Simulation Records can activated/deactivated for 800xA Operation systems in Composer Project Settings tab. If activated for a single (or multiple) 800xA system(s), each simulation action concerning a processing unit

Simulation Regeneration Section 11 Melody Simulation Events

414 3BDD011741-600 A

which is attached to such an 800xA system will result in a new/updated simulation record *.sim file.

Simulation Regeneration

If necessary, simulation record files can be regenerated on demand by user. This can be performed in Engineering Workplace running phase for complete processing unit

Figure 104. Composer Project Settings

Section 11 Melody Simulation Events Simulation Regeneration

3BDD011741-600 A 415

via cubicle layout or process item mask of system / island / station. Still existing simulation record files will not be deleted via this action.

The <Simulation Records> menu item is hidden in cubicle layout diagram if processing unit isn’t attached to an 800xA system or creation of simulation records is disabled for this 800xA system.

The menu item is always visible for above-mentioned process item masks, but only enabled for those items which have at least one processing unit which is attached to an 800xA system with enabled creation of simulation records.

Figure 105. Simulation Record regeneration via Cubicle Layout

Figure 106. Simulation Record regeneration via Station mask

Simulation Regeneration Section 11 Melody Simulation Events

416 3BDD011741-600 A

3BDD011741-600 A 417

Appendix A Quality Definition

The purpose of this appendix is to describe the tag.property qualities in 800xA for Melody.

DescriptionEvery property consists of following three pieces of information: a value, a quality, and a timestamp. The quality describes the state of the property that originates anywhere in the process control system.

An application in the process control system (function block in a controller or in 800xA for Melody) can evaluate the provided quality information and can apply rules for further processing (use of values with a determined quality, displaying of values with quality, use the quality for filter purposes).

IndicatorsTag quality is indicated with ASCII characters. The quality indicator appears in several functions in the 800xA for AC 870P / Melody system (event page, faceplate,

OPC Quality Definition Appendix A Quality Definition

418 3BDD011741-600 A

reports). Table 19 contains a list of the quality indicators and their descriptions.

OPC Quality DefinitionThe quality definition is based on the quality defined by OPC. The OPC standard defines property quality as a 16 bit data item. The lower eight bits of quality flags are defined as a combination of three enumerated values: quality status (two bits), substatus (four bits), and limit status (two bits). The higher eight bits are available for vendor specific use (vendor specific status). The OPC quality structure is shown in Table 20.

L = limit status.

Table 19. Quality Indicators

Condition Character Quality

Bad quality * Nonspecific, device failure, or sensor failure

. Configuration error

? Not connected

/ Last known value

@ Communication failure

~ Out of service

Uncertain quality

! Nonspecific, last usable value, sensor not accurate, engineering units exceeded, or subnormal

Good quality <blank> Nonspecific

& Local override

Table 20. OPC Quality Structure

Bit 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

Use VS VS VS VS VS VS VS VS Q Q S S S S L L

Appendix A Quality Definition 800xA for AC 870P / Melody Quality Definition

3BDD011741-600 A 419

S = substatus.

Q = quality status.

VS = vendor specific status.

OPC subdivides the quality into the three categories of good, uncertain, and bad. Each category is further subdivided into up to 16 substatuses. The current definition of the OPC quality is described in OPC Quality Flags on page 424.

800xA for AC 870P / Melody Quality DefinitionIn contrast to OPC, 800xA for AC 870P / Melody provides the quality as a 32 bit word. The 32 bits are composed of the OPC standard (lower 16 bits) and 800xA for AC 870P / Melody standard extensions (upper 16 bit). The definition of a 32 bit quality allows using the OPC vendor specific bits by a specific Connectivity Server type as it is intended by the OPC specification.

All quality information inside the process control system is mapped as much as possible to the OPC quality specification.

Process control system specific quality information that cannot be mapped to the OPC quality specification, can be mapped to the 800xA for AC 870P / Melody standard extension. These quality bits can only be used in an application that has knowledge of these quality extensions. The structure of the 800xA for AC 870P / Melody quality is shown in Table 21. A description of the bits is provided in Table 22.

Table 21. 800xA for AC 870P / Melody Quality Structure

Bit 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

Use VS VS VS VS VS VS VS VS Q Q S S S S L L

Bit 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16

Use AMD INT NOD DLS NLD ANN CLC CER PRJ RES RES RES RES IVI DVI UTS

Tag.Property Quality for Process Properties Appendix A Quality Definition

420 3BDD011741-600 A

In addition to the OPC quality specification (quality for process properties), 800xA for Melody also provides quality on a tag basis. This quality is derived from the quality of the properties. The quality on property and tag basis, have the same structure.

Tag.Property Quality for Process PropertiesProcess properties change their value, quality, and timestamp dependent on process state. The current process properties consist of value, quality, and timestamp. Quality and timestamp represent the last change of the associated value.

Tag.Property Quality for Computed PropertiesComputed properties usually inherit the timestamp from the most recently changed source of the computation. The quality of these properties is usually inherited from the source as well. A common rule is that all needed properties will influence the resulting quality.

Table 22. Quality Bit Descriptions

Bit Abbreviation Description

00 – 01 L OPC limit status.

02 – 05 S OPC substatus.

06 – 07 Q OPC quality status.

08 – 15 VS OPC vendor specific status.

16 UTS 800xA for AC 870P / Melody uncertain timestamp.

17 DVI 800xA for AC 870P / Melody decreasing value indicator.

18 INI 800xA for AC 870P / Melody increasing value indicator.

19 – 22 RES 800xA for AC 870P / Melody reserved.

Appendix A Quality Definition Tag.Property Quality for Configuration Data

3BDD011741-600 A 421

An OR needs only one input to be true. If that input has a good quality the result will have a good quality as well. In case of an AND, all inputs need to have a good quality. That means the worst quality will rule the resulting quality. If the result encounters a scaling or conversion error, a CER error can be reported. The result should also have the calculated bit set. This allows an application to discern that the result is from a calculation.

Tag.Property Quality for Configuration DataAll configuration data are part of basic components (SymObject, PSigReal). The quality of these values is always GOOD non_specifc. The associated timestamp is the time of the configuration (property CHTIME). The only exception is when the configuration data is corrupt or not accessible.

Tag.Property Quality for Event Point Related PropertiesMost of the event point related properties contain configuration data (refer to Tag.Property Quality for Configuration Data on page 421). The computed properties have a direct relationship to the generated event. These are the properties ACT (event point active) and UNACKEP (event point not acknowledged).

Every event is generated from an property with quality and timestamp. The computed event point related properties get the quality of the associated process property. The timestamp has a direct relationship to the associated event.

Tag QualityOPC defines a quality specified on property basis. In addition, 800xA for AC 870P / Melody also provides a quality on tag basis. The tag class (SymTag) provides separate properties for the tag related quality. These properties are derived from other properties.

Properties Appendix A Quality Definition

422 3BDD011741-600 A

Properties

Quality

This property is part of the SymTag class. It represents the overall quality of the tag. It provides this quality in the same format defined previously for tag property quality. Specifically the value component of this property returns numerically the 800xA for AC 870P / Melody quality word and textually the three character quality string. The quality component of this property always returns the quality status GOOD non_specific as it represents the quality of this property, not the tag. The timestamp represents the last change in the value of this property.

Bad

This property is part of the SymTag class. It represents the overall BAD quality of the tag. It provides this quality as a Boolean status signal with an associated event point. The quality component of this property always returns the quality status GOOD non_specific as it represents the quality of this property, not the tag. The timestamp represents the last change in the value of this property.

Suspended

This property is a part of the MelodyTag class (used for the Melody functionality substitution and off scan). It provides this quality as a Boolean status signal. The quality component of this property always returns the quality status GOOD non_specific as it represents the quality of this property, not the tag. The timestamp represents the last change in the value of this property.

Appendix A Quality Definition 800xA for AC 870P / Melody Quality Information

3BDD011741-600 A 423

800xA for AC 870P / Melody Quality Information

The Connectivity Server provides the quality information shown in Table 23. Table 24 describes the mapping rules.

Table 23. 800xA for AC 870P / Melody Quality Information

Quality Description Cause

No connection to gateway(control system).

The gateway or all connections to the gateway are not available.

Communication error, component failure.

Connection for the requested tag/tag.property not available.

For the requested property not connection handle available (no actualization).

Configuration of CCO and Connectivity Server do not match.

Requested property not available.

Requested property not available in the Connectivity Server.

Application requested for a Property not defined in the class definition.

Configuration change. Tag affected by configuration change. Not applicable.

Decreasing value indicator. Comparing old received value with current received value.

TRUE: value decreasing to the last received value.FALSE: old value less than or equal to new value.

Increasing value indicator. Comparing old received value with current received value.

TRUE: value increasing to the last received value.FALSE: old value greater than or equal to new value.

Table 24. Quality Mapping Rules

Connectivity Server Quality OPC Quality OPC Substatus

Connection gateway BAD Comm_Failure

Connection tag BAD Not_Connected

Not permitted request BAD Configuration_Error

Configuration not found BAD Configuration_Error

OPC Quality Flags Appendix A Quality Definition

424 3BDD011741-600 A

OPC Quality FlagsThe low eight bits of the quality flags are currently defined in the form of three bit fields: quality, substatus, and limit status. The eight quality bits are arranged as follows:

QQSSSSLL

Quality Bits

Table 25 describes the values for the quality bits.

Substatus Bits

The layout of these bits depends on the value of the quality bits. The substatus bits for bad quality are shown in Table 26. Table 27 shows the substatus bits for

Connectivity ServerS quality 800xA for AC 870P / Melody quality status

Value decreasing DVI Decreasing value indicator

Value increasing IVI Increasing value indicator

Table 25. OPC Quality Bits

QQ Bit Value Define Description

0 00SSSSLL Bad Value is not useful for reasons indicated by the substatus.

1 01SSSSLL Uncertain Quality of the value is uncertain for reasons indicated by the substatus.

2 10SSSSLL N/A Not used by OPC.

3 11SSSSLL Good Quality of the value is good.

Table 24. Quality Mapping Rules (Continued)

Connectivity Server Quality OPC Quality OPC Substatus

Appendix A Quality Definition Substatus Bits

3BDD011741-600 A 425

uncertain quality. Table 28 shows the substatus bits for good quality.

Table 26. Bad Quality Substatus

SSSS Bit Value Define Description

0 000000LL Non specific Value is bad but no specific reason is known.

1 000001LL Configuration error

Some Server specific problem with the configuration. For example the item is question has been deleted from the configuration.

2 000010LL Not connected Input is required to be logically connected to something but is not. This quality may reflect that no value is available at this time, for reasons like the value may have not been provided by the data source.

3 000011LL Device failure A device failure has been detected.

4 000100LL Sensor failure A sensor failure had been detected (the limit bits can provide additional diagnostic information in some situations.)

5 000101LL Last known value Communications have failed. However, the last known value is available. Note that the age of the value may be determined from the TIMESTAMP in the OPCITEMSTATE.

6 000110LL Comm failure Communications have failed. There is no last known value is available.

7 000111LL Out of service Off scan or otherwise locked. This quality is also used when the active state of the item or the group containing the item is InActive.

8 - 15 N/A Not used by OPC.

NOTE: Servers that do not support substatus should return 0. An old value can be returned with the quality set to bad (0) and the substatus set to 5. This is for consistency with the fieldbus specification. This is the only case in which a client may assume that a bad value is still usable by the application.

Substatus Bits Appendix A Quality Definition

426 3BDD011741-600 A

Table 27. Uncertain Quality Substatus

SSSS Bit Value Define Description

0 010000LL Non specific No specific reason why the value is uncertain.

1 010001LL Last usable value Whatever was writing this value has stopped doing so. The returned value should be regarded as stale. This differs from a bad value with substatus 5 (last known value). That status is associated specifically with a detectable communications error on a fetched value. This error is associated with the failure of some external source to put something into the value within an acceptable period of time. The age of the value can be determined from the TIMESTAMP in OPCITEMSTATE.

2 - 3 N/A Not used by OPC

4 010100LL Sensor not accurate

Either the value has pegged at one of the sensor limits (in which case the limit field should be set to 1 or 2), or the sensor is otherwise known to be out of calibration via some form of internal diagnostics (in which case the limit field should be 0).

5 010101LL Engineering units exceeded

Returned value is outside the limits defined for this parameter. In this case (per the fieldbus specification) the limits field indicates which limit has been exceeded but does not necessarily imply that the value cannot move farther out of range.

6 010110LL Subnormal Value is derived from multiple sources and has less than the required number of good sources.

7 - 15 N/A Not used by OPC

NOTE: Servers that do not support substatus should return 0.

Appendix A Quality Definition Limit Bits

3BDD011741-600 A 427

Limit Bits

The limit bits are valid regardless of the quality and substatus. In some cases, such as sensor failure, it can provide useful diagnostic information. Table 28 provides the descriptions of the limit bits.

OPCHDA Quality

OPCHDA_QUALITY values identify quality values specific to retrieval of historical data. These quality values are described in Table 29.

Table 28. Limit Bits

LL Bit Value Define Description

0 QQSSSS00 Not limited Value is free to move up or down.

1 QQSSSS01 Low limited Value has pegged at some lower limit.

2 QQSSSS10 High limited Value has pegged at some high limit.

3 QQSSSS11 Constant Value is a constant and cannot move.

NOTE: Servers that do not support limit should return 0.

Table 29. OPCHDA_QUALITY Values

Quality Values Description

OPC_EXTRADATA More than one piece of data that may be hidden exists at same timestamp.

OPC_INTERPOLATED Interpolated data value.

OPC_RAW Raw data value.

OPC_CALCULATED Calculated data value.

OPC_BADSOURCE Interpolated value – source may not be good.

OPC_NOBOUND1 No data found to provide upper or lower bound value.

OPC_NODATA No data collected. Archiving not active (for item or all items).

OPC_DATALOST Collection started/stopped/lost.

OPCHDA Quality Appendix A Quality Definition

428 3BDD011741-600 A

OPC_CONVERSION Scaling / conversion error.

OPC_ANNOTATION An annotation exists for this data value.

OPC_ANNOTATION_NODATA An annotation exists at this timestamp but there is no associated data value.

NOTE: 1. OPC_NOBOUND is intended to be used when bounding values are requested but not available. The Server returns an empty place holder (value NULL, timestamp Server dependent) with a quality of OPC_NOBOUND.

Table 29. OPCHDA_QUALITY Values (Continued)

Quality Values Description

3BDD011741-600 A 429

Appendix B Hints, Handlings andWorkarounds

This appendix is intended to provide handlings and workarounds that may help to configure and to run 800xA for AC 870P / Melody.

Starting a Redundant Pair of Connectivity ServerWhen starting a redundant pair of Connectivity Server wait to start the second Connectivity Server until the first Connectivity Server has finished SQL replication to avoid that one Connectivity Server gets not in Operation service state due to temporary high load.

After system restart prior to operation check the system status by help of the system status viewer from service structure.

Simultaneously Starting a Configuration and Connectivity Server

Use the Replication Monitor on the Melody Configuration Server node to check that all Connectivity Server nodes are online after Configuration and Connectivity Server nodes were started at the same time (for example, after offline update). If some of them are displayed as offline, restart the Configuration Server node and then, one by one, the Connectivity Server nodes. The Replication Monitor should show all nodes as online.

Hints on Partitioning Appendix B Hints, Handlings and Workarounds

430 3BDD011741-600 A

Hints on Partitioning

Partitioning of a Melody Connectivity Server

Before installing 800xA for AC 870P / Melody Connectivity Server it is recommended to create 3 partitions conforming with following basic rules:

c:\ for Windows & 800xA & programs

• capacity: 30 GB (min.)d:\ for SQL-Server data

• capacitiy: 20 GB (min.)e:\ for Basic history

• capacity: 40 GB (min.) + rest of available disc space.

Partitioning of a Melody Config Server

Before installing 800xA for AC 870P / Melody Config Server it is recommended to create 2 partitions conforming with following basic rules:

c:\ for Windows & 800xA & programs

• capacity: 30 GB (min.)d:\ for SQL-Server data

• capacitiy: 20 GB (min.)

Appendix B Hints, Handlings and Workarounds Illegal Character Set

3BDD011741-600 A 431

Illegal Character SetThe following characters must not be used in names:

<character> (<name>) <ASCII Value>

“ (quotation) 034

# (pound) 035

% (percent) 037

& (and) 038

’ (apostrphe) 039

( (parantheses open) 040

) (parantheses close) 041

* (asterisk) 042

, (comma) 044

. (period) 046

/ (slash) 047

: (colon) 058

; (semicolon) 059

? (question mark) 063

[ (bracket open) 091

\ (backslash) 092

] (bracket close) 093

{ (curly bracket open) 123

} (curly bracket close) 125

(del) 127

(control and format char.) 00 through 31

Illegal First and Last Characters Appendix B Hints, Handlings and Workarounds

432 3BDD011741-600 A

Illegal First and Last CharactersTable 5 lists the characters that cannot be used for the first or last character in a name.

Live Values in Alarm and Event ListOptional it is possible to show Live Values in the Alarm and Event List. Therefore you need to extend the Melody Object Types (e.g. Single Flag Real) with Property Translation Aspect for a property with name VALUE. The VALUE property must be configured in the Expression Field to point to Y/SIG of the Control Connection Aspect (it is always the property where the Process Value comes from you are interested in to see in the Alarm and Event List)

If the current value column is included in the list the live values can be shown if you click the Enable Live Value button of the Alarm and Event List.

Table 30. Illegal First Characters

Character ASCII Value

Space 032

! (exclamation point) 033

+ (plus sign) 043

- (minus sign) 045

_ (underscore) 095

The space character is the only illegal last character

Appendix B Hints, Handlings and Workarounds Update of PROF dependent settings

3BDD011741-600 A 433

Update of PROF dependent settingsThe TagImporter configures the PROF dependent settings (e.g. MAN / AUT Set) only when the tag is imported for the first time. If the tag already exists in the ConfigServer database and you change the default of the PROF (e.g. IDF 49156 -> 49340) or the PROF definition in CONVDB (e.g. SetValue from 0 -> 1) afterwards, the settings for an updated tag will not change Tag configuration for existing Tags. You have to delete the tag and reload it again to get the correct settings.

Melody tracking eventsMelody tracking events show the wrong actor identity. It is possible to combine both Melody Tracking Events and AuditEvent_OperatorAction to get full information in form of two entries in the Alarm & Event list. The 800xA Audit Trail message for AuditEvent_OperatorAction events shows the correct actor identity.

Melody tracking events Appendix B Hints, Handlings and Workarounds

434 3BDD011741-600 A

3BDD011741-600 A 435

Revision History

The following table lists the revision history of this User Manual.

Updates in Revision Index AThe following table shows the updates made in this User Manual for 800xA 6.0.3.

Revision Index

Description Date

- First version published for 800xA 6.0 August 2014

A Published for 800xA 6.0.3 September 2016

Updated Section/Sub-section Description of Update

Section 1 Introduction Supported Operating Systems > Figure 4 updated for generalized wordings for Windows server and client operating system.

Section 2 Base Configuration Removed 2008 version under Install DHCP Server subsection.

Added “Internet Explorer Language Settings” subsection.

Appendix B Hints, Handlings and Workarounds

Added “Simultaneously Starting a Configuration and Connectivity Server” subsection.

Updates in Revision Index A

436 3BDD011741-600 A

3BDD011741-600 A 437

AAC 800M

Data Exchange 389Affinity 82Alarm and Event Page

Enabling 110Alarm Priority Text 103Alarms and Events 121Aspects

Time adjustment 141, 144, 146Audit Trail 59Auto Configurator 62Automation Class

Melody AnOut, Analog output 179Melody APID controller 187Melody CLCx controller 233Melody SFC, Sequence control 329MelodyAnalog, Analog monitoring 158MelodyAnMon, Analog monitoring 166MelodyBFlagx, Block flag 217MelodyBinary, Binary 228MelodyCOA, Change over automatic 264MelodyCount, Counter 274MelodyDos, Dosing circuit 279MelodyIDF, Individual control 295MelodyOPA, Binary memory 309MelodySel, Preselection 319MelodySFlagx, Single flag 351MelodySwClock, Calendar and timing

function 357MelodyTCount, Time and pulse counter 365MelodyTotal, Quantity value acquisition 374

Automation Classes 157

BBackup

Composer 154ConfigServer 154

Batch 393Bulk Data Management 91

CConfigurable Text 99Configurable text 99Configurator Admin 60Connectivity Server

Adding to the System 34Control Structure 75Control Structure Import 89Coupling Modules

Adding 34

DDHCP Server (Installation) 28

EEtc/host File 28Event Categories 123Event Classifications 123Event Concentrators 122Event Distribution System 122Event Point 121Event Point Attributes 124Event Point Definition 124Event Point State Attributes 131Event System Redundancy 133Export 93

Index

Index

3BDD011741-600 A 438

FFaceplate Mapping 53Fieldbus Support 391Functional Structure 76

HHistory Log Configuration 57

IIDF Viewer 386Import 93Indexed Text Tab 99Indexed text tab 99Information Manger 405

LLogic State Descriptor 103

MMaestro UX 391Melody System Events 104Message System 114Message Transport and Buffering 115

NNetwork Redundancy

Control Network 73Operator Network 74

OObject Life Cycle 95OPC Data Source 65OPC Quality Definition 418Operate IT B 391Operating Parameters 95Operator User 78

PProcess Messages 117

Project history tab 108

QQuality

Tag 421Quality Definition

800xA for Melody 419OPC 418

Quality text tab 106

RRestore

ConfigServe 155

SSecurity 392Sequence Control (SFC) 385, 407Settings 52Severity

Client Severity 135Device Severity (Melody Priorities) 136OPC Severity 135

Severity, OPC Severity and Device Priority 135Substitutable Text Tab 105Substitutable text tab 105System and Process Interface Messages 119System Definition 97System definition object 97System Events 113

TTag Importer 70Tag.Property Quality

Computed Properties 420Event Point Related Properties 421Process Properties 420

TagConfig AspectBody 30Tabs 30

Technical Data 417

Index

3BDD011741-600 A 439

Time adjustmentNew time adjust target 143 to 146, 148 to 150

Index

440 3BDD011741-600 A

Index

440 3BDD011741-600 A