3bse023698r101 - en ac 100 engineering methods 1.0 - reference manual

OperateIT �� Version 1.0

��

OperateIT

��

Version 1.0

Reference Manual3BSE 023 698R101

3BSE 023 698R101

��

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

In no event shall ABB Automation Technology Products AB be liable for direct, indirect, special, incidental, or consequential damages of any nature or kind arising from the use of this document, nor shall ABB Automation Technology Products AB be liable for incidental or consequential damages arising from use of any software or hardware described in this document.

This document and parts thereof must not be reproduced or copied without ABB Automation Technology Products AB’s written permission, and the contents thereof must not be imparted to a third party nor be used for any unauthorized purpose.

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

��

IndustrialIT, ControlIT and OperateIT are registered trademarks of ABB Ltd., Switzerland.

Microsoft, MS-DOS, Visual Basic and Windows 2000 are registered trademarks of Microsoft Corporation.

Copyright © ABB Automation Technology Products AB 2001

��,7��

�� !��

��" ��#�� 1.1 About This Book ....................................................................................................1

1.1.1 How to Use this Book ...........................................................................3

1.2 Product Overview...................................................................................................4

1.2.1 Product Scope........................................................................................5

1.2.2 What You Can Do with the AC 100 Controller Integration..................5

1.3 Prerequisites and Requirements .............................................................................6

1.4 Conventions............................................................................................................6

1.5 Related Documentation ..........................................................................................8

1.6 Terminology .........................................................................................................10

��" ��$�#�� 2.1 Site Planning ........................................................................................................13

2.2 Installation Procedures .........................................................................................13

2.3 Start-up and Shut-down Procedures .....................................................................13

��" ��%�#�� 3.1 Before You Start ...................................................................................................15

3.2 Set Up Daylight Saving and Time Synchronization ............................................15

3.3 Build the Control Structure ..................................................................................18

3.3.1 General ................................................................................................18

3.3.2 Restart the Advant OPC Server for AF100.........................................19

3.3.3 Populating the Control System Structure ............................................20

3.3.4 Obsolete Objects .................................................................................23

3.3.5 Verifying the Integration of the AC 100 CI ........................................24

3.3.6 Available AC 100 Series Object Types ...............................................26

3.3.7 Building a Control Structure for Test and Demo Purposes .................27

��" ��&�#��"�� 4.1 Operating Overview .............................................................................................31

3BSE 023 698R101 i

��,7��

��'�� (

��" ��)�#�� 5.2 Hardware Indicators.............................................................................................33

5.3 Error Messages ....................................................................................................33

5.4 Fault Finding and User Repair.............................................................................33

5.4.1 System Status ...................................................................................... 34

5.4.1.1 System Status - Network.............................................. 36

5.4.1.2 System Status - Station Node ....................................... 37

5.4.1.3 System Status - PM Objects ......................................... 39

5.4.1.4 System Status - CI Objects...........................................40

5.4.1.5 System Status - IO Objects...........................................41

5.4.1.6 System Status - OPC Objects ....................................... 42

5.4.2 Graphical Aspect for System Status presentation...............................42

5.4.3 System Events..................................................................................... 43

5.4.4 Control Connection Aspect.................................................................45

5.4.4.1 The CCA Property view............................................... 45

5.4.4.2 CCA Property Info .......................................................46

5.4.4.3 CCA - Additional info.................................................. 48

5.4.4.4 CCA - OPC ..................................................................50

5.5 Backup/Restore Procedures .................................................................................51

��*+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++)%

ii 3BSE 023 698R101

��,7��

��" ��

�+� �,�� -This book describes the OperateITAC 100 Controller Integration product. The AC 100 Controller Integration product is used for connecting the OperateIT workplace to an Advant Fieldbus 100 control network with connected AC 100 Controllers.

The information in this User’s guide is intended for:

• The Engineer that sets up the control system functionality (including defining displays, writing the control programs, etc.)

• The System administrator that sets up the control system configuration

You should have a good understanding about distributed automated process control, the hardware and software functionality of the OperateIT products. You should already know how to use and maintain the hardware platform (PC), and the operating system (Microsoft Windows 2000).

In addition, you should be logged in as an Engineer or Administrator (on the OperateIT workplace) to be allowed to perform some of the procedures that are described in this book.

There are a number of User’s guides for the OperateIT product and options, see Section 1.5, Related Documentation for a complete list of references. ABB Automation Products has a number of useful training courses for persons that shall setup, operate, and maintain the OperateIT products.

3BSE 023 698R101 1

��,7��

.��/��0�� 0��1� ��0��"

This publication includes ��, ��, and �� where appropriate to point out safety related or other important information. It also includes �� to point out useful hints to the reader. The corresponding symbols should be interpreted as follows:

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

Warning indicates the presence of a hazard which could result in �� .

Caution indicates the presence of a hazard which could result in �� .

Information alerts the reader to pertinent facts and conditions.

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

2 3BSE 023 698R101

��,7�� !�"��#��

�+�+� 2�3� ��.�� -This section is a quick guideline to help you find what you are looking for in this book.

/��

Read Product Overview to learn more about the AC 100 Controller Integration product.

Read the Release Notes if you want to Upgrade an existing AdvaSoft 2.0 for Windows NT system to OperateIT and AC 100 Controller Integration.

Read the �� if you want to start installing the product.

Start reading the Getting started section of chapter 3, Configuration, if you want to start to setup the configuration.

Read chapter 5, Maintenance, if you shall start to trace a problem in the control system.

Read the �� !�� for more information about the following items:

• If you want to setup the handling of process events: severity, event texts etc.

• For useful hints and summaries of how to configure your AC 100 Controllers.

2�3� ��

The AC 100 Controller Integration product is installed as an option to the OperateIT workplace software. Refer to the �� for instructions on how to install the AC 100 Controller Integration software.

��

The configuration of the AC 100 Controller Integration product is described in Chapter 3, Configuration. There are also a number of OperateIT User´s Guides that are useful when the configuration is done. Examples are the ��,7��"#� ��$��which is needed when the engineers build the graphic displays presenting the process.

3BSE 023 698R101 3

��,7��

2�3� ��.��

Refer to the ��,7��$�� for information about viewing and using the AC 100 Controller Integration product. You could also find some information in Chapter 3, Configuration, and Chapter 5, Maintenance.

�� 1�� 4�5��

Chapter 5, Maintenance, describes how to inspect the status of the AF100 network and the OperateIT system. Refer also to the ��,7 ��$�� for information on system administration procedures such as:

• licensing software

• managing users (creating new users, setting up passwords, and configuration of user preferences)

��# ��2�"

Comprehensive on-line help is available for the software. Access to the complete help files is available via the menu bar. Context-sensitive help (��) is available for all windows, dialogs, and entry fields.

�+$ 5�� 4�43The OperateIT software is a family of products for process monitoring and control. The generic design makes it possible to use OperateIT together with many different types of Process Control Systems, both systems provided by ABB as well as systems provided by other suppliers.

This book describes the AC 100 Controller Integration software, a software product that not only enables you to connect an OperateIT workplace to a system of AC 100 Controllers1, but also extends the total functionality of OperateIT utilizing the best of the AC 100 Controller system.

1. Also called AF100 network. The supported controllers are Advant Controller 110, Advant Controller 70, Advant Controller 160 and Advant Controller 80.

4 3BSE 023 698R101

��,7�� $� %��

�+$+� 5�� "AC 100 Controller Integration is an optional package to the OperateIT product. It gives you the following features:

• A connection to the control system through the Advant OPC Server for Advant Fieldbus 100 and the communication boards and equipment.

• Tools to build your OperateIT Control structure on-line from the AC 100 Controllers.

• The possibility to customize the event and alarm reporting and presentation with just a few configuration actions.

• Powerful maintenance and supervision of the AC 100 Control system itself using the System Status and System Event functions.

�+$+$ /�� 6��3 �� This list is an example of the engineering that you can do with the AC 100 Controller Integration product.

• Upgrade your existing AdvaSoft 2.0 for Windows NT installation to OperateIT and AC 100 Controller Integration.

• Re-use configuration data from existing AdvaSoft 1.x for Windows installations.

• Setup the OperateIT workplace to describe the process data that is defined in the database of the AC 100 controllers (create the so called Control structure). You do not need to define the database again, it is read from the Advant OPC Server for Advant Fieldbus 100.

• Build the functional and location structure using the object types and aspects pre-defined in OperateIT and in AC 100 Controller Integration.

• Build Graphic displays for monitoring and control of the process utilizing the AC 100 Controller Integration graphical aspects.

• Create Alarm and Event lists using the AC 100 Controller Integration default set-ups.

3BSE 023 698R101 5

��,7��

• Define and activate the logging of process data, including presentation of the stored data logs.

• Check the AF100 network using the System status functions for the entire control system, including the AC 100 controllers and the Advant Fieldbus 100 control network.

�+% 5��7�� 7��1� �The general hardware and software requirements for the OperateIT product are described in the ��.

�+& ��4� ��The following conventions are used throughout this book for the presentation of material:

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

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

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

• A plus sign is used to indicate that you must simultaneously press several keys. For example, CTRL+C indicates that you must hold down the CTRL�key while pressing the C key.

• The phrase “press and release” is used to indicate that you sequentially press several keys. For example, to close a window, press ALT, and then F4. This indicates that you press ALT key, and then you press and release the F4 function key.

• The names of push and toggle buttons are boldfaced. For example, click ��.

6 3BSE 023 698R101

��,7�� & �� '� ��

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

– The following convention is used for menu operations: MenuName > MenuItem > CascadedMenuItem. For example: choose �� > �� > ��.

– The �� menu name always refers to the �� menu on the Windows 2000 Task Bar.

• System prompts/messages are shown in the Courier font, and user responses/input are in the boldfaced Courier font. For example, if you enter a value out of range, the following message is displayed:

Entered value is not valid. The value must be 0-30.

In a tutorial, you may be told to enter the string TIC132 in a field. The string is shown as follows in the procedure:

��

3BSE 023 698R101 7

��,7��

�+) �� 1� � ��Table 1-1 lists all documentation related to the AC 100 Controller Integration.

%�� &�' (��)�#��

�� 8 � � ��" ��

Installation ��,7 �� (�� This book describes how you install the OperateIT including the requirements on the hardware.

System Administration

��,7��)� ��*�(�� This book describes how you configure the OperateIT and how you then perform maintenance.

Software ��,7+�� %�� ,��#��*�(��

This book describes everything about the user interface, for example how you present information, navigate and control objects.

��,7(��#��*�(��

This book describes how you build and use graphics in OperateIT. It includes information about the basic building blocks provided by ABB.

��,7�'� �-��)�� #��*�(��

This book explains how to use the OperateIT Alarm and Event functions. It covers alarm and event configuration and presentation.

��,7�� !�� #��*�(��

This book describes how to use the trend graphs and historian to view historical data during runtime.

��,7��*�(�� This book is an extract from all other guides, and describes a number of selected operator scenarios.

��,7%��

This book is intended as a guide for plant engineering using OperateIT.

8 3BSE 023 698R101

��,7�� . ��/��)� ��

Product Guides

��,7%��(�� This book is a presentation of the software and software options in OperateIT Products. It also includes hardware and software requirements and specifications.

�� %��(��

This book is a presentation of the AC 100 Controller Integration software. It also includes hardware and software requirements and specifications.

��'� ��%��'��'� �0��%��(��

This book is a presentation of the software Advant OPC Server for Advant Fieldbus 100 and the related hardware. It also includes hardware and software requirements and specifications.

Software Advant OPC Server for Advant Fieldbus 100 User´s Guide

This book describes all the details concerning installation and configuration of the Advant OPC Server for Advant Fieldbus 100 and the installation of the chosen communication board.

Installation ��,7�� (��

This book describes how you install the AC 100 Controller Integration product on top of the OperateIT software.

��,7��

This book describes the object types and the aspects contained in AC 100 Controller Integration.

%�� &�' (��)�#��

�� 8 � � ��" ��

3BSE 023 698R101 9

��,7��

�+9 ��1��8The following is a list of terms associated with the AC 100 Controller Integration product that you should be familiar with:

��1 ��" ��

AC 100 Advant Controller 100 - the ABB family of Controllers: AC110, AC70 and AC160.

ActiveX Microsoft standard for user interface components.

Advant Fieldbus 100 The control network communication protocol that is used by the AC 100 controllers.

AIS, AOS Abbreviation of the signal objects Analog Input and Analog Output respectively

Aspect An aspect is a description of some properties of an ��1��. Some examples of aspects are name, circuit diagram, process display, and control logic.

Aspect Objects A computer representation of a real object like a pump, a valve, an order or a virtual object like a service or an object type. An Aspect Object is described by its �� and organized in ��

CBA Control Builder A. The engineering tool for the Controller applications.

CCA Control Connection Aspect - defines the details about the connection.

AMPL ABB MasterPiece Language - the programming language for logic programs in the Advant Controller 100 and 400 series.

DIS, DOS Abbreviation of the signal objects Digital Input and Digital Output respectively

IndustrialIT IndustrialIT is ABBs solution, that creates a business enterprise where your plant automation, asset optimization, and collaborative business systems are seamlessly linked in real time.

10 3BSE 023 698R101

��,7�� 2 ��)� ��3

Node A computer on the Internet, Plant, Control or IO network. Each node has a unique node address with a format depending on the network it is connected to.

OPC An application programming interface from the OPC Foundation. The application of the OPC standard interface makes possible inter operability between automation/control applications, field systems/devices and business/office applications.

OperateIT The name for the collection of products for daily operation and supervision of an automated process

OperateIT Plant Explorer

A configuration of the Internet Explorer for creating the Aspect Object that you use to put together the plant. You can also use it to browse and search the structures of the plant.

Property A data field on an aspect of an Aspect Object that can be accessed through OPC.

A data field on an ��'�4 control accessible from the Visual Basic editor.

Structure A hierarchical tree organization of ��1�� that describes the dependencies between the real objects. An �� object can exist in multiple structures, for example both in a functional structure and in a location structure.

View An �� can have several ways to be presented depending on the task performed, like viewing or configuration. Each presentation form is called a view.

��1 ��" ��

3BSE 023 698R101 11

��,7��

12 3BSE 023 698R101

��,7��

��" ��$ ��

$+� � �5��The AC 100 Controller Integration product is installed and runs in a PC, which must have the OperateIT workplace product installed. The physical, electrical, and environmental requirements are described in the ��,7�� (for the PC), the �� and the �� $��'

$+$ �� 5��The installation procedures are described in the ��.

$+% � �� #�"�� #��3��5��The start-up and shut-down procedures are described in the ��,7��$�� (for the PC and workplace), and in the ��.

3BSE 023 698R101 13

��,7�� $ ��

14 3BSE 023 698R101

��,7�� 5� ��6��

��" ��% ��

%+� ��6�� Make sure that the following prerequisites are fulfilled:

• The results from the Control Builder A1 engineering tools are stored in a BCD file.

• The OperateIT server is connected directly to the Advant Fieldbus 100 control network.

• The AF100 network includes controllers with running applications.

You should have read, at least briefly, the ��,7��*��+��"�� !�� before you go into the details of this book.

You must be logged in as an Engineer or Administrator to be able to perform the engineering work described in this chapter.

If you have to configure or learn more about the controller application and the AF100 network, see �� $��.

%+$ � �."��8�� 4��1��8��:� ��There are a number of alternative ways to configure the clock synchronization for an Advant Fieldbus 100 network together with a network of OperateIT products.

The Advant Fieldbus 100 network has a clock synchronization functionality in itself. The details of how this functions and is configured can be studied in the �� !�� and in the corresponding User´s Guide for the DB-elements of each controller.

An OperateIT network consists of one or several servers and a number of clients connected via TCP/IP. Synchronization of that network of PC:s in itself is supported by the OperateIT product. This is described in the ��,7��,-.�*��/01/. One clock server synchronizes the other PC:s in the network.

1. The Control Builder A replaces the tools called AMPL CC.

3BSE 023 698R101 15

��,7�� 5 ��

The Advant OPC Server for Advant Fieldbus 100 can function as time master or as slave versus the Advant Fieldbus 100 network. How to configure this is described in the �� !��'

The recommended configuration for clock synchronization and daylight saving is described below.

��11��

It is recommended that you set-up an OperateIT server, that hosts the Advant OPC Server for Advant Fieldbus 100, as time master. It will be time master both for the OperateIT network as well as for the Advant Fieldbus 100 network. Any adjustments of the network time is done (from the time server) using Windows 2000 Date and Time dialog in the Control Panel. See Figure 3-1.

You can also set time and date by using the Command Prompt.

�� -&�' 2��3�0��)��%��)��

16 3BSE 023 698R101

��,7�� 5�$ ��#�/�3��'� �� )��3 �� 7��

To set-up the Advant Workplace product network for such a configuration you do the following:

• Set up the selected server machine as time server. If you have several server machines, set-up the others to request for the correct time from the time server.

• Set up all the Workplace nodes to accept the clock synchronization.

• Make sure that automatic daylight saving is set on all the PC:s according to Figure 3-2.

• Set up the Time synchronization of the Advant OPC Server for Advant Fieldbus 100 to ��according to the instructions in the �� !��'

Set up the Time synchronization of other Advant OPC Servers for Advant Fieldbus 100 to ��according to the instructions in the �� !��'Those PC:s shall collect their time from the time server.

�� -&0' ��#)� ��"��

3BSE 023 698R101 17

��,7�� 5 ��

The result of this solution is as follows for time tagged data:

• Alarm data and Historical data are stored according to UTC time, that is the local time does not matter. Alarm and History data presentation takes care of presenting data with local time.

%+% ��

%+%+� ;��The Advant OPC Server for AF100 does not support on-line additions of information. It uses the so called BCD.MDB (Bus Configuration Database) file as a source for its knowledge about the Controller objects. When the Advant OPC Server for AF100 is started it reads the BCD.MDB file and builds up a list of signal objects and their properties. This information is used by the OperateIT A1.x software to populate the Control structure.

To make use of a new or updated information in the Controller, the Advant OPC Server for AF100 needs to be restarted and the Control structure needs to be populated, see Figure 3-3.

�� -&-' ��"��#��

BuildControl

Application

DownloadAMPL to theControllers

Store informationin BCD.MDB

Restart theOPC server

Populate theControl,Structure

18 3BSE 023 698R101

��,7�� 5�5�$ ��'� ��%��'��0��

%+%+$ �� 4�� 5��4��!��

To restart the OPC server do as follows:

1. Make sure that you have Administrator access rights to the PC.

2. Start the Task Manager and find the process called “wiaopc.exe” and select only that process.

3. Open the Control Panel by selecting �� !�� "# ��$�� $��%

4. Find the service called “Advant OPC Server for AF100”. Make sure it has status ��# and then press the �� button.

5. Change quickly back to the Task Manager and verify that the process “wiaopc.exe” decreases its memory consumption and finally disappears from the process list.

6. Now, you can change back to the Administrative Tools and the Services dialog and press the �� button for “Advant OPC Server for AF100”.

The Service Manager might launch a message box claiming that the service could not be stopped. This message can be disregarded if the Task Manager behaved correctly in step 5 above. The reason is simply that the Service Manager expects the service to terminate within a certain amount of time (about 20 seconds). The “wiaopc.exe” process might need longer time to disconnect from all controllers and free all its allocated memory. In large configurations you will most likely get this message all the time.

As a restart of the Advant OPC Server for AF100 prevents monitoring and operation of a plant during the restart time you have to be careful when you do this. Especially if you are working in a multi node configuration.

Before you restart the OPC Server you need to shut down Operate IT according to the instructions for Operate IT. The reason is that Operate IT, once the Advant OPC Server for AF100 is established as a service provider to it, will restart the OPC Server as soon as it notifies that it is stopped.

If the procedure above gives you a problem, the entire system should be restarted for safety reasons.

3BSE 023 698R101 19

��,7�� 5 ��

%+%+% 5�"�� 8� 1�� The Control structure describes the structure of the Control network, its Controllers and signal objects. When you create the Network objects you specify how communication with the Controllers shall be done by selecting the OPC server provider.

The OPC Server uses the information stored by the engineering tools in the so called BCD.MDB file, see Figure 3-3, as the base to build up the corresponding OPC items.

As a middle step you also need to restart the Advant OPC Server for AF100, see Section 3.3.2, Restart the Advant OPC Server for AF100.

When the Advant OPC Server for AF100 is restarted and its initialization is finished you can execute the Upload aspect. When you do, all objects that are created are instances of the object types presented in Figure 3-9.

Steps to upload objects are the following:

1. Select �� !�� "&&��#�� Choose the !��'(��.

2. Select �� from the Structure selector.

Each time you have changed the content of the Engineering database, you need to store the result also in the BCD file, restart the Advant OPC Server for AF100 and re-run the Upload to make sure that the objects and object attributes in the Control Structure correspond to the content in the Controllers.

20 3BSE 023 698R101

��,7�� 5�5�5 %�� 3��)��

3. Create an object of the "��))��*��type.When the following dialog appears click on the "## button and select the correct provider.

Select the appropriate type of connection to the OPC Server which is normally Connector with CSlib. In the ProgID drop-down box select the "&&%"��))%� OPC DA Server ID and click on the �� button.

4. Select the "��))��*��, by the name you entered above, then select the +��#�� aspect.

�� -&/' ��"�4��3��5��#�

Once the Network object is created you can start at step 4 whenever you need to do an Upload.

3BSE 023 698R101 21

��,7�� 5 ��

5. Click �� +��#�on the Standard Tab.

Typically, the Control structure will now contain the Controllers (system objects that represent the Controller nodes), the object types (system objects representing the group of objects of that type), the Signal objects and the System status objects.

�� -&1' ��#�)��

22 3BSE 023 698R101

��,7�� 5�5�& ��1��

Figure 3-6 shows an example of the control structure.

See the relevant sections of ��,7��*��+��"��(��#�+��, how to create objects in a structure and how to assign engineering/application data to objects.

%+%+& �,�� ,<� �All objects that have disappeared from the Controllers are placed under the ��#��# ��and can be removed from the system by the ordinary Delete function.

�� -&6' *7��#��

3BSE 023 698R101 23

��,7�� 5 ��

%+%+) =��8�� All objects that are now populated into the Control structure can be subscribed upon, even controlled. If you want to verify that a few of the Signal objects work properly you can use either one of the Graphic element aspects, see Figure 3-7, that exist for that object type or you can use the CCA aspect which allows you to verify the value of all object properties.

�� -&8' *7��#�)�� #�

24 3BSE 023 698R101

��,7�� 5�5�. 8��3� ��

�� >�1"��3� �� "�

You find the CCAs as aspects to the signal objects. They are found in the ��,�-��*�� ,��. Use the CCA, to verify the connection to the OPC server.

Check the Subscribe for live data check box, to display the objects property values. The fields .��, /�� and �� will start showing live data. When live data can be displayed, the connection to the OPC server is OK.

�� -&9' :��)��"��"�"��

3BSE 023 698R101 25

��,7�� 5 ��

%+%+9 �4��,��,<� ��8"�Figure 3-9 shows all the available AC 100 Series object types in the control structure.

�� -&;' ��#�� #��

26 3BSE 023 698R101

��,7�� 5�5�9 �� /�)�%��

The following object types exist:

• The Network types: AF100 Network and AF100 Test Network

• AC 100 Station: Either an AC 100 Series Controller or a PC with either an Advant OPC Server for AF100 or an AdvaSoft 1.x software.

• Signals - AC100 AIS, AC100 AOS, AC100 DIS, AC100 DOS

• Calculated Data - AC100 DAT_AI, AC100 DAT_AO, AC100 DAT_DAT, AC100 DAT_DI, AC100 DAT_DO, AC100 MB, AC100 MBS, AC100 MI, AC100 ML, AC100 MR.

• System Status objects: OPC, PM, CI, IO.

%+%+? �� 1��5��"��It may sometimes be an advantage to be able to test or demonstrate your applications versus a simulated Control structure.

You can build a Control structure with simulated values through the following steps:

1. Start Plant Explorer and select the ��.

2. Build a structure in the Control structure that includes the process and system objects that you want to simulate.

Note that the graphic presentation of object data “the faceplates” do not work directly with simulated values from the Property Signal Generator. You must define supervision and presentation properties to get “simulated live data” in the faceplate presentation.

3BSE 023 698R101 27

��,7�� 5 ��

3. Add the aspect Property Signal Generator to each object (process and system object) that you want simulated data from.

�� -&��' ��#��

28 3BSE 023 698R101

��,7�� 5�5�9 �� /�)�%��

4. Setup the configuration of the Property Signal Generator aspect to generate data for the specific properties. This setup includes specifying variable data style - linear, sine wave, trapeze, etc. You specify the setup for each object property.

5. Build your applications to work with this control structure with simulated properties.

6. Test your applications (demo applications, test applications).

7. Save the Control structure for future use by exporting it with the Import/Export tool. Startup the Import/Export tool via the menu �� !�� "&&��#�� '(��.

�� -&��' ��

3BSE 023 698R101 29

��,7�� 5 ��

8. Setup Export of the new Control structure via the menu "�� #��(��. Define your Control structure as the object to export.

If you want to use the same demo or test structure in the future, you just import this structure.

�� -&�0' )��3*7��#��

30 3BSE 023 698R101

��,7��

��" ��& �"��

&+� �"�� 4�43The majority of the OperateIT functionality is generic for all Controller types. However, there are a few things with regards to the interpretation of the following information that needs to be described:

• System Status information for AC 100.

• System Events for AC 100�

The details about these functions are described in �� !��and in the ��(��#�+��'

3BSE 023 698R101 31

��,7�� & ��

32 3BSE 023 698R101

��,7�� .�$ !��"��

��" ��) ��

)+� 5�4� 4�� The software product does not require any preventive maintenance.

The communication hardware board towards the Advant Fieldbus 100 network does not require any preventive maintenance.

)+$ 2��3�� Not applicable.

)+% ��The AC 100 Controllers produce a number of event and alarm messages to inform you about errors concerning the AC 100 system and not with the process itself.

You can find a System Event List aspect on the network, on each Controller and on the system status objects of the type OPC, PM, CI and IO. The System Event List aspect enables you to see all system events for the AC 100 Controller Integration system and for the connected Advant OPC Servers for AF100.

The System Events are presented in plain text.

)+& !�� !��.��"��All software products from ABB Automation Products include the following:

• Reporting errors to ABB Automation ProductsIf you find a problem with the software, you can report it to ABB Automation Products. All reported problems are investigated, and you will get an investigation report. All reported problems are tracked until the problem is solved - corrected or a workaround is available.

3BSE 023 698R101 33

��,7�� . ��

• Delivery of new or improved softwareSoftware problems may be fixed in several ways:

– Product patch - to fix a specific problem.

– Product service pack - to update the product (contains several patches).

– New product version - to upgrade the product (contains new functions).

Product patches, Service packs, and New versions are installed in the PC in the same way as the original product. Installation of patches, service packs, and upgrade packages will normally not require uninstallation of the product, but it will normally require a restart of the OperateIT workplace.

Here are some hints on how to identify the cause of malfunctions within the AC 100 system. It could be difficult to decide whether the problem you see is a problem within the process or a problem within the AC 100 system. There are some tools you can use for your trouble shooting:

• System Status aspects

• System Event List aspects

• Communication aspects

)+&+� �8� 1�� The System status presents the status of the control system. It presents the result from the control systems and the Advant OPC Server for Advant Fieldbus 100´s internal supervision programs. A complete overview of the System status for the control system is available in the Network node.

Before we go into the details, let us look at an extract of a typical Control structure so you can identify the different object types that we are discussing and understand how to navigate to them.

34 3BSE 023 698R101

��,7�� .�&� �3��)��

�� 1&�' �� #��#��#��

3BSE 023 698R101 35

��,7�� . ��

)+&+�+� �8� 1�� #�� 3��-

As a start you should have a look at the System Status for the entire network. From Plant Explorer, select the Control Structure, the Network object, and then the System Status Viewer aspect.

In this case you can see that there is something wrong with the AC110 Controller STN5. The next action should be to study the System Status for this controller.

�� 1&0' � ��"�4��3��5

36 3BSE 023 698R101

��,7�� .�&� �3��)��

)+&+�+$ �8� 1�� #��

The System status for a Station node is presented if you select the Control Structure, the Station node, and the System Status Viewer aspect. In the example below (Figure 5-3), the AC110 controller (STN 5) has a problem with one of it´s PM Boards.

�� 1&-' � ��<�3��

3BSE 023 698R101 37

��,7�� . ��

It is possible to get a detailed view of the properties for a specific CI, IO, PM and OPC object if the Details column is marked with an X. To present a detailed view for a CI, IO, PM or OPC object, select it in the System Status Viewer and click on the Details button. An alternative action in your fault finding is to study the system alarm list for the failing Station, see Section 5.4.3, System Events.

�� 1&/' )��<�3��#�

38 3BSE 023 698R101

��,7�� .�&� �3��)��

)+&+�+% �8� 1�� #�5��,<� �

There is one PM system status object underneath each Station object. It is possible to get a detailed view of the properties for a specific PM board if the Details column is marked with an X. To present a detailed view for a PM board, select it in the System Status Viewer and click on the Details button. See Figure 5-5 and the �� !�� for details on the status properties.

�� 1&1' � ��<�3��+��#�

3BSE 023 698R101 39

��,7�� . ��

)+&+�+& �8� 1�� #��,<� �

There is one CI system status object underneath each Station object. It is possible to get a detailed view of the properties for a specific CI board if the Details column is marked with an X. To present a detailed view for a CI board, select it in the System Status Viewer and click on the Details button. See Figure 5-6 and the �� !�� for details on the status properties.

�� 1&6' � ��<�3��#�

40 3BSE 023 698R101

��,7�� .�&� �3��)��

)+&+�+) �8� 1�� #��,<� �

There is one IO system status object underneath each Station object. It is possible to get a detailed view of the properties for a specific IO board if the Details column is marked with an X. To present a detailed view for an IO board, select it in the System Status Viewer and click on the Details button. See Figure 5-7 and the �� !�� for details on the status properties.

�� 1&8' � ��<�3��#�

3BSE 023 698R101 41

��,7�� . ��

)+&+�+9 �8� 1�� #��5��,<� �

There is one OPC system status object for each OPC Server1 in the network. It is possible to get a detailed view of the properties for a specific OPC Server if the Details column is marked with an X. To present a detailed view for an OPC Server, select it in the System Status Viewer and click on the Details button. See Figure 5-7 and the �� !�� for details on the status properties.

)+&+$ ;��"��"� ��8� 1�� "�� There is a graphical aspect available for the System status object types. See the ��(��#�+�� for details. You can include it in a graphical display, for example an overview display. This gives you a combination�of process and control system status.

The graphical aspect is available for the CI, PM, OPC and IO objects underneath each Controller object. Finally, it also exists for the OPC Server running in the OperateIT Server node itself.

1. Node types with AdvaSoft 1.x software installed will show up as OPC objects. The status information will then be very limited.

�� 1&9' � ��<�3��#�

42 3BSE 023 698R101

��,7�� .�&�5 �3��)�'� ��

)+&+% �8� 1��4� �The System Events provide valuable information for fault tracing. Unless you already have a system event aspect on the Network object and the Controller objects in your Control structure, you should create them as they will give you an overview list for all the system events in your system. This is how you create them:

1. From Plant Explorer select the Control structure and then the object on which you want to create the aspect.

2. Create an Alarm and Event List Aspect and give it the name System Events

3. Select the System Events aspect, go into the Config view and select the AC 100 Default System Event List.

4. Save it.

�� 1&;' � ��:��#��

3BSE 023 698R101 43

��,7�� . ��

An example of a typical System Event List is presented in Figure 5-10.

When you have located the Controller where the problem resides, bring up the System Event List on that Controller object (Control structure). This gives you a dedicated system event list for that Controller helping you to close in on the problem. The System Events are in plain text and should help you to continue with your fault tracing.

�� 1&��' � ��*��:��"��4��3��5

44 3BSE 023 698R101

��,7�� .�&�& ��

)+&+& �� "� There is a Control Connection Aspect (CCA) for all process and system objects.The CCA:s can be useful to trace problems specific for a certain object or for the presentation of an object. The CCA has four views, here is a short description of the views and how you can use them in your trouble shooting.

)+&+&+� ��5��"� 8�43

The CCA Property view, see Figure 5-11, gives you a list of all the properties, their data format and how they can be accessed. If you check the ��$��#�� check box, you will also get the current value of all properties updated cyclically.

�� 1&��' %"�� 3

3BSE 023 698R101 45

��,7�� . ��

Use this view to verify the property values of an object, how they are configured and the current property values to compare with other presentations of it. If you suspect an error in a node, an I/O board or a transducer, you can use the CCA:s to narrow in on the problem by verifying which objects that are available over the network and which are not - and what their status properties tell you.

)+&+&+$ ��5��"� 8��

The Property Info view presents all details about the selected property. An example of a Property Info view is found in Figure 5-12.

The CCA Property view gives you a complete list of properties for example their names, data type, permission, value and quality.

The Property Info view includes the possibility to set the definitions for the Property values. To define property value handling and to set these values could severely affect the control of the industrial process, including loosing control of the process.This functionality is only included for testing and fault tracing, and should not be used during normal operation.

0��1��!��$��1��2��%

46 3BSE 023 698R101

��,7�� .�&�& ��

The following Property values are presented and could be changed:

�� - Type of value (boolean, integer, float, etc.).

�� - The name of the property.

+�#��3�� - The update rate for this property (in ms).

0�� - Describes the relation between the property and the object.

!�� - Flag that indicates Read and/or Write permission on the property.

�� - Defines the Read and Write operations for the property.

�� - Indicates how the property is updated: Real time (hard real-time), Runtime (soft real-time), Additional info (no real-time update), or Other.

The Property values are changed locally when you click on the �� button. To save the changes in the system, click "��.

�� 1&�0' ��&��

3BSE 023 698R101 47

��,7�� . ��

)+&+&+% ��#��

The Additional Info tab presents details on property specific information. The example in Figure 5-13 presents information about an analog value.

0��1��"##��$��1��2��%

The following Additional info values are presented and could be changed:

��(�3�� - Maximum range value (for an analog value).

��3�� - Minimum range value (for an analog value).

'��+�� - Engineering unit for this property.

�� 1&�-' ��&��

48 3BSE 023 698R101

��,7�� .�&�& ��

��0�� - This value should be presented with this number of decimals.

!��#� - Defines if this value should be presented between the discrete points in trend curves: Stepped (value is constant between points) or Interpolated (value is linear between points).

The Additional Info values are changed when you click on the "�� button.

The Presentation Mode makes it possible for you to select the default presentation mode in Trace presentations: Stepped or Interpolated, see the ��*��+�� $�� for more information.

3BSE 023 698R101 49

��,7�� . ��

)+&+&+& ��#��5�

The OPC tab presents information about the OPC Properties included in the CCA. The following columns are presented:

Property - The OPC property in question.

Item ID - The identity of the specified OPC property in the AF100 OPC Server.

Access Path - Path to Tag

�� 1&�/' ��&��

50 3BSE 023 698R101

��,7�� .�. ��-��%��

)+) ��-�"@�� 5��General backup procedures are described in the ��,7��.

3BSE 023 698R101 51

��,7�� . ��

52 3BSE 023 698R101

��,7�� ,

��*

�AC 100 Controller Integration 4

Functionality 5Hardware and Software requirements 6Product features 5Product overview 4

�Backup and Restore 51Building Control structure

Demo structure 27Test structure 27

Bus Configuration DatabaseBCD.MDB 18

�Configuration 15

Before you start 15Control Connection Aspect 45

Additional information 48Property information 46Property view 45

Conventions 6

�Document List 8

!Fault Tracing 33

;Graphical Aspect for System Status

presentation 42

2Hardware indicators 33

�Installation 13

Procedures 13Site planning 13

�Operation, Overview 31

5Preventive maintenance 33

�Restart OPC Server 19

�Shut-down procedures 13Signal Object

In control structure 20Simulated process data

Export control structure 29Import control structure 30Property signal generator 28

Startup procedures 13System Alarms

Alarm list for Controllers 44Alarm list for network 44Create and Setup 43

System Error Messages 33System Events 43System Status 34

CI Objects 40Controller node 37IO Objects 41Network 36OPC Objects 42PM Objects 39

3BSE 023 698R101 53

��,7�� ,

�Terminology 10

.Uploader 21

/Where to start 3

54 3BSE 023 698R101

3BSE 023 698R101

November 2001

3bse023698r101 - en ac 100 engineering methods 1.0 - reference manual

Documents

registered trademarks

consequential damages

operateit version

product overview

product scope

installation procedures

reference manual3bse

698r101the information