System 800xA Configuration System Version 5.
System 800xA Configuration System Version 5.
NOTICE This document contains information about one or more ABB products and may include a description of or a reference to one or more standards that may be generally relevant to the ABB products. The presence of any such description of a standard or reference to a standard is not a representation that all of the ABB products referenced in this document support all of the features of the described or referenced standard.
Table of Contents About this User Manual General ............................................................................................................................15 Intended User...................................................................................................................17 User Manual Conventions ...............................................................................................17 Feature Pack ......................................................................
Open Project ...................................................................................... 39 Reserve Project .................................................................................. 39 Release Project ................................................................................... 40 Control Logic ....................................................................................................... 41 Working with a Function Diagram ...................................................
Alarm Analysis Configuration ...........................................................................124 Property View of the Alarm Analysis Aspect ...................................126 Alarm Analysis with OLE DB ..........................................................126 Creating an Alarm Logger - Alarm and Event List for Printing .......127 Creating an Alarm Band....................................................................135 Alarm Expression...................................................
Pre-configuration of AC 800M Controller........................................ 234 Setting up a Fieldbus Topology for PROFIBUS and HART ............ 237 Insert HART Device Type Objects ................................................... 244 Insert PROFIBUS Device Type Objects ........................................... 248 Configuration and Commissioning of Field Device Type Objects ... 253 Configuration of OPC Server PROFIBUS/HART ............................
Performance...................................................................................................................323 Data Collection...................................................................................................323 SQL Server.........................................................................................................324 Batch Management ........................................................................................................
SAP/PM Integration........................................................................................... 395 PC, Network and Software Monitoring......................................................................... 396 Configuration Change and Access Management .......................................................... 397 Authorization ..................................................................................................... 397 Access Control ............................................
OLE DB Provider for HDA...............................................................468 Property Transfer................................................................................................478 Purpose ....................................................................................478 Property Transfer Definition Aspect .................................................478 Property Transfer Service..................................................................481 Security Handling......
Object Type Group Reference Aspect .............................................. 524 Aspect Category Definition Aspect .................................................. 525 Formal Instance List Definition Aspect ............................................ 525 Formal Instance Definition Aspect ................................................... 525 Formal Instance Reference Aspect ................................................... 525 Aspect Group Definition Aspect........................................
Library Definition Aspect ..................................................................................554 Library Version Definition Aspect .....................................................................554 Library Member Aspect .....................................................................................563 Deleting a Library ..............................................................................................565 Renaming a Library...............................................
3BDS011222-510 B
About this User Manual General Any security measures described in this document, 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.
General About this User Manual Building the automation solution is described with focus on the process oriented Functional Planning approach, based on Function Designer, including Library Structure, Object Type Structure, Functional Structure and Control Structure. It is described in more detail in System 800xA Engineering, Engineering Studio Function Designer Getting Started (3BDS100968*) and System 800xA Engineering, Engineering Studio, Function Designer (3BDS011224*).
About this User Manual Intended User Intended User This User Manual is written for application engineers performing the tasks to engineer and configure the automation solution in the software production and test phase of an engineering project. As a reader of this User Manual you should have basic knowledge of engineering and configuration of process automation systems in general.
Warning, Caution, Information, and Tip Icons About this User Manual Feature Pack functionality included in an existing table is indicated using a table footnote (*): * Feature Pack Functionality Unless noted, all other information in this User Manual applies to 800xA Systems with or without a Feature Pack installed. 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.
About this User Manual Terminology Terminology A 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 Notes 20 About this User Manual 3BDS011222-510 B
Section 1 Introduction System Overview The Extended Automation System 800xA, System Version 5.1, covers operation as well as engineering and configuration of continuous and batch automation applications and supports FDA 21 CFR part 11 compliance of these applications. An overview of the system functions and system infrastructure of System 800xA is given in System 800xA, System Guide, Functional Description (3BSE038018*). The foundation of System 800xA is the Aspect Object architecture.
Prerequisites and Requirements 22 Section 1 Introduction 3BDS011222-510 B
Section 2 Configuration This section provides you with information on the basic configuration steps according to the Overall Project Workflow and Site Engineering Workflow described in System 800xA System Planning (3BSE041389*). These workflows are summarized in the following tables Table 1 and Table 2: Table 1.
Section 2 Configuration Table 1.
Section 2 Configuration Table 2. Overall Project Workflow Activities Site Engineering Workflow Step Activities according overall project workflow on Engineering System (ES) Activities See Table 1. Create System Configuration Define System Configuration Version in System Version on Production (PS) Configuration Version Definition object /aspect in the Maintenance Structure. Execute Creation of the System Configuration Version (full backup).
Section 2 Configuration objects in the 800xA system. Reservation functionality is available with right mouse click at the object in 800xA Plant Explorers Control Structure.
Section 2 Configuration Automation Solution Automation Solution Control Structure To start implementing an automation solution you need a Control Network and a Control Project in the Control Structure. The Control Project is structured in Libraries, Applications and Controllers.
Control Structure Section 2 Configuration Create Control Network, Control Project and Controller 1. Switch to Control Structure in Plant Explorer. 2. Select the root node. 3. Click with the right mouse button and select New Object. Figure 1. Select New Object... 4. Browse to the Control Network object (Object Types > Control System > AC 800M/C Connect > Control Types), select Control Network and insert a new name, if required. Figure 2.
Section 2 Configuration Control Structure 5. Click Create. 6. Select the newly created Control Network object and click with the right mouse button. 7. Select New Object in the context menu. 8. Select the Control Project object type for the required controller type, for example AC 800M, and enter a project name in the Name box. Figure 3. Selecting the Project Object Type for AC 800M 9. Click Create. You have now created the Control Network and the Control Project with an AC 800M Controller.
Control Structure Section 2 Configuration Configure OPC Data Source 1. Switch to Control Structure in Plant Explorer. 2. Select the control network object. The following steps shall be done on every control network, placed in the system and containing the OPC Data Source Definition aspect. 3. Select the OPC Data Source Definition aspect. 4. Select the Connectivity tab. 5. Click New…. 6. Change the name of the service group, if required.
Section 2 Configuration Control Structure The AC 800M OPC Server needs to be configured separately. For more information on configuration of AC 800M OPC Server, see System 800xA Control and I/O, OPC Server for AC 800M, Configuration (3BSE035983*). Create Control Application The project created according to Create Control Network, Control Project and Controller on page 28 provides one control application by default. To add an additional application object to this project: 1.
Control Structure Section 2 Configuration 10. Press Close on window level leave the dialog. Repeat Step 6 to Step 9 to insert other libraries needed. Connect Application Libraries To be able to use a standard (or user defined) control application library inserted into your project in an application you have to connect it your application: 1. In Plant Explorer switch to the Control Structure. 2. Select the application object. 3.
Section 2 Configuration Control Structure 5. Press Create to create the new controller object. 6. Right click on the Hardware object below the new controller object. 7. Click New Object.... 8. In the New Object dialog browse to Object Types\Control System\ AC 800M/C Connect\Libraries\Hardware\BasicHWLib 5.1-0, select the processor module type (for example PM860 / TP830), change / edit Name and Object Description. 9. Press Create to create the new processor module object.
Control Structure Section 2 Configuration To configure the task´s properties: 1. Right-click on the task object. 2. Click Task Properties. 3. In the Task Properties dialog edit the required properties and click Apply. 4. Click OK. Connect Application to Task To connect an application to a controller and a task: 1. In Plant Explorer switch to the Control Structure. 2. Right click the Applications object below the corresponding controller object. 3. Click Insert Object.... 4.
Section 2 Configuration Control Structure Insert Hardware Libraries Hardware libraries are standard hardware libraries, device hardware libraries, user created libraries. Standard hardware libraries are included in the AC 800M Connect system extensions. Only when the project is reserved it is possible to insert hardware libraries in the project. See Reserve Project on page 39 1. In Plant Explorer switch to the Control Structure. 2. Select the Control Project object. 3.
Control Structure Section 2 Configuration Control Builder M Professional. In the Project Explorer of CBM you see the inserted hardware libraries under \Libraries\Hardware\.... Figure 4. Insert Hardware Libraries Standard hardware libraries for example are: • S800IoModulebusHwLib S800 I/O-modules for modulebus • CI854PROIBUSHwLib PROFIBUS-DPV1 master • S800CI840CI854HwLib CI840 slave and S800 I/O-modules for CI854 10. Press Close on window level to close the dialog.
Section 2 Configuration Control Structure Connect Hardware Libraries to Controller Only when the controller is reserved it is possible to connect hardware libraries in the project. 1. In Plant Explorer switch to the Control Structure. 2. Select the Control Project object, if not already opened: Open the project. 3. Select the Controller object. 4. In the aspect list right click on the Controller aspect. 5. Click Config View. 6. In the :Controller dialog select the Libraries tab.
Control Structure 9. Section 2 Configuration In the Hardware Libraries tab of the :Controller dialog press Apply. Figure 5. Connect Library 10. Press Close on window level to close the dialog. Create Hardware Units To create hardware units, for example standard I/O boards on ModuleBus: 38 1. Open Plant Explorer. 2. Switch to Control Structure. 3. Open the substructure below the Project object. 4. To place S800 local I/O on the controller, select the ModuleBus object. 5.
Section 2 Configuration Control Structure 6. Browse to the required S800 module, e.g. AI895. 7. Enter the slot number of the module placed, e.g. 1, in the Name box. S800 local I/Os always start at slot 1. For more information on S800 modules and their instantiation, refer to System 800xA Control and I/O, Basic Control Software, Introduction and Configuration (3BSE035980*) and the hardware related manuals on S800 I/O. 8. Click Create.
Control Structure Section 2 Configuration 6. Click Reserve... in the context menu. 7. In the Reserve dialog all entities (project, application, controller) shown are by default marked. Unmark the check boxes you want to exclude. 8. Click the Reserve icon. Figure 6. Reserve Project To reserve an application is required if changes to the application shall be done. To reserve a controller is required e.g.
Section 2 Configuration Control Logic 3. In the Release dialog all entities (project, application, controller) shown are by default marked. Unmark the check boxes you want to exclude. 4. Click the Release icon. Figure 7. Release Project 5. Press Close on window level to close the dialog.
Control Logic Section 2 Configuration Using existing standard control libraries and, if needed, having prepared control libraries with own object types, you build your project´s control logic in Function Diagrams. Examples for own object types are shown in Process Object Type with Signals on page 504 or Process Object Type Built in Function Designer on page 508.
Section 2 Configuration Control Logic Creating a new Function Diagram To create an object that shall hold a Function Diagram for a process function or sequence you can use a ready-made diagram template object type: 1. In Plant Explorer navigate to a parent object in the Functional Structure 2. Right click on the parent object to open the context menu. 3. Click on New Object... to open the New Object dialog. 4.
Control Logic Section 2 Configuration Figure 8. Function Diagram, A3 Landscape Template It also contains a Function Diagram Document aspect that can be used to enter administrative data (meta data) to be displayed in the Function Diagram footer and to represent the Function Diagram in Document Management. Editing a Function Diagram 44 1. Navigate to and double click on the Function aspect of object 1T1FC1 to open the Function Diagram. Enlarge the popup window to full size. 2.
Section 2 Configuration Control Logic Reserve the diagram by selecting File > Reserve Diagram to get exclusive modify access to the diagram, and then insert the required Function Components listed in Table 3 into the Function Diagram. Function Designer inserts the required application libraries into the control project and connects them to the applications as far as possible automatically.
Control Logic Section 2 Configuration Table 3. Function Components 1T1FC1 Function Component Object Type Name Description Additional Action Object Types\Control System \AC 800M/C Connect\Libraries \ControlStandardLib 1.3-3 \Control Module Types\PidCC 1T1FC1 _FIC Flow controller Object Types\Control System \AC 800M/C Connect\Libraries \ControlStandardLib 1.
Section 2 Configuration Control Logic Figure 10. Function Diagram 1T1FC1 in Functional Structure 4. Click File > Save or File > Save All to finally save the diagram contents. Allocating a Function Diagram If a Control Module, Function Block, or Function instance is created in the Functional Structure, a Control Application named Unallocated_Inst_App is automatically created in the Control Structure under Applications.
Control Logic Section 2 Configuration Allocating I/O Signals 1. Click the IO Allocation icon from the Quick Access menu/tool bar. In the grid on the right side of the IO-Allocation dialog all engineering signal objects inserted in the Function Diagram are shown. 2. In the tree on the left side of the IO-Allocation dialog right-click on the Boards object, select Insert Board from the context menu. 3. In the Insert Board dialog, navigate to the required location and select ModuleBus, click Insert.
Section 2 Configuration Control Logic 5. Drag and drop one or several signal objects from the grid on the right side of the IO-Allocation dialog to the Boards object or to an I/O board object or to a channel stub of an I/O board object on the left side. After Drop the allocation is shown on both sides. 6. Click File > Exit to close the IO-Allocation dialog. IO Allocation supports allocating signal objects and HART devices (represented as signal objects) to channels of I/O boards. From SV 5.
Control Logic Section 2 Configuration 4. Click Apply to assign the new Data Flow Order to the respective function components. 5. Click Close to exit. The Data Flow Order of blocks on a diagram is crucial for execution. It is suggested to ensure that the order is as intended, for example, by clicking the Generate button in the Data Flow Order in Allocatable Group dialog.
Section 2 Configuration b. 2. 3. 4. Control Logic Click on Tools > Download Project and Go Online to start the download procedure. To display online value of a port in Function Diagram: a. Click on the port in Function Diagram to select it. b. Click on Online > Add Links to Current Page. c. Click on Online > Subscribe for Live Data Now the value is displayed at the port and updated. To display and force online values in Watch Window: a.
Control Logic Section 2 Configuration Printing the Function Diagram 1. Open the diagram to print. 2. Click File > Print. 3. Press OK to accept the defaults in the Print dialog. 4. Press OK in the Print dialog of Windows to print. Working with a Sequence Function Designer supports the design of sequences with steps, transitions and actions. A sequence can be inserted in a Function Diagram or in a Function Diagram type.
Section 2 Configuration Control Logic 5. Press OK. The graphical block symbol for this Function Component appears on the diagram. Ports are still hidden. 6. To show the hidden ports: a. Right-click on the symbol. b. Click Show Hidden Ports.... c. In the dialog Show Hidden Ports select the ports to show or mark check box All Hidden Ports. d. Press OK. The visible ports can now be connected to control and supervise the sequence.
Control Logic Section 2 Configuration transition symbol, but no step symbol and optional action diagrams. The jump symbol defines the step name to jump to. A step, which is a jump target, displays an additional arrow. Even if the step is target for multiple jumps, there is only one arrow displayed. At the step itself there is no indication, where the jump comes from. • Simultaneous Sequence. The divergence and convergence of simultaneous sequences is indicated by a double horizontal line.
Section 2 Configuration Control Logic a. Select the required port. b. Right-click and select Insert Step from the available context menu. c. In the New Component Name dialog enter step Name, for example Agitate, Number and Description or accept the given defaults. d. Press to quit insertion mode. 7. Repeat steps Step 5 and Step 6 to add a transition Agitated and a step Drain and repeat Step 5 to add a final transition Drained. 8.
Control Logic Section 2 Configuration Figure 12. Sequence Overview Diagram Editing Step Detail Diagram You add action code in a step detail diagram, working similar as in a normal Function Diagram. A step has three outputs of data type Boolean: N, P1, P0, to initiate Action, P1 Action, P0 Action. P1 is true when the step becomes active, P0 is true when the step becomes inactive and N is true while the step is active.
Section 2 Configuration Control Logic Feature Pack Functionality Action Display with Target Diagram Reference Name and Description An additional setting is required to generate action display with target diagram reference name and its description: 1. Open the Object Type Structure > Function Planning > Settings > Function Settings aspect (refer to Figure 13). 2. Set the value of ConfigDataForSFC to True. 3. Click Apply. Figure 13.
Control Logic Section 2 Configuration Naming Conventions To ensure that naming conventions are followed for diagrams, the property DiagramSuffixString, available in Object Type Structure > Function Planning > Settings > Function Settings aspect, can be used (refer to Figure 13). Set the required suffix in the Value column. This suffix can be used as reference while creating diagrams.
Section 2 Configuration Control Logic The Function Diagram containing the sequence with a project constant need to be generated (using the Generate Configuration Data option) every time the value of the project constant is changed. This ensures that the project constant value is updated in SFC Viewer.
Control Logic Section 2 Configuration Data flow order within a detail diagram is not supported and is not displayed. This order is calculated automatically and cannot be modified. Editing Action Diagram You add action code in an action diagram, working similar as in a normal Function Diagram. Restrictions: Action code is generated into CBM Structured Text (ST) code. Action diagrams are sub-diagrams.
Section 2 Configuration Control Logic 2. Double click on the corresponding transition symbol in the overview diagram. A diagram named according to the transition is opened and shown as further workbook tab. It initially contains the transition symbol. 3. Insert and connect allowed components from Object Type Structure: Object Types\Control System\AC 800M/C Connect\System Functions\Functions. If you try to insert a not allowed component an error message is shown.
Control Logic Section 2 Configuration In addition to the functions available to download and test Function Diagrams (see Downloading and Testing the Function Diagram on page 50 you use additional sequence test functions available in the Sequences toolbar: • Disable actions • Block transition • Force forward • Force backward Printing Normal Function Diagram print functions are used. Step detail and transition detail are printed together in one diagram.
Section 2 Configuration Control Logic 5. In the objects representing the process functions in Functional Structure open a Function Diagram by double click on Function aspect. The Function Components of the levels below show up in the diagram automatically. 6. Connect the component ports on the current diagram graphically as required. 7. If needed add additional glue or interlock control logic by inserting and connecting further Function Components. 8.
Control Logic Section 2 Configuration b. In the open Contents diagram click File > Print, in the Print dialog set the options to print the Contents and the Diagrams and then finish the print action. If plant modelling to the level of process functions has been done before, steps Step 1 and Step 2 have already been done.
Section 2 Configuration Control Logic In effect, diagram references consist of an input/output reference and communication variable. Diagram references can be connected using Function Designer or Bulk Data Manager. For more information, refer to System 800xA Engineering, Engineering Studio Function Designer (3BDS011224*). In the sense of a structural programming language, diagram references and diagram variables refer to global or communication variables.
Control Logic 66 Section 2 Configuration 2. Open and attach workbook BDM_for_Function_Diagrams for start object 1T1 in Function Structure. 3. Drag and Drop the object 1T1FC1 from the Functional Structure into the Excel worksheet Typical. This gives you the correct Template path to be used in the Copy FuD worksheet. 4. Switch to worksheet Copy FuD. 5. In the row Typical insert n times the template path from the picklist if you require n copies of the diagram. 6.
Section 2 Configuration 8. Control Logic In the row Application insert the path to the existing control application the copied diagram shall be allocated to. Use Insert Object Path as described above. Figure 15. BDM_for_Function_Diagrams: Creating Copies of a Typical 9. In the Bulk Data Manager tool bar press Save all Objects to create the instances. The required objects with Function Diagrams are created and named below the parent object defined in the worksheet.
Control Logic Section 2 Configuration Exporting / Importing Function Diagrams Function Diagrams can be transferred between systems using the Import Export tool. Figure 16. Function Diagram Object in Import / Export Tool The Import / Export tool is described in System 800xA, Maintenance (3BSE046784*). Import/export for control projects, control applications, control libraries, control module types and so on is described in System 800xA Control, AC800M Configuration (3BSE035980*).
Section 2 Configuration Control Logic available, the target Control Project is available and the needed libraries are connected to the target Control Application. 1. Launch the Import / Export tool from the toolbar of Plant Explorer. 2. Drag and drop the Function Diagram object into the left pane of the Contents tab of the Import / Export tool window. 3. Accept the check-marked contents shown in the Add Items dialog and press OK. By default export is done without dependencies. 4.
Control Logic Section 2 Configuration 8. A progress dialog pops up. Wait until an end message like “Import succeeded” is shown in the grid area of this dialog. 9. If no further error messages are shown in the grid area of the progress dialog: Press Done to exit. 10. To complete the imported diagram: a. Re-connect the diagram references to appropriate diagram variables. b. If not allocated: Allocate the diagram to an application. c. (Re-)Allocate the signals to I/O boards. d.
Section 2 Configuration Control Hardware Units For more information on working with Function Diagrams, refer to System 800xA Engineering, Engineering Studio Function Designer Getting Started (3BDS100968*) and System 800xA Engineering, Engineering Studio, Function Designer (3BDS011224*). Detailed Difference Report Difference report provides the differences between Function Diagrams in the system and Diagrams present in the .afw file to be imported.
Control Hardware Units 5. Section 2 Configuration Do channel parameterization from the I/O Signal objects to I/O board hardware unit objects either explicitly through Engineering Workplace object context menu item Advanced > Write Allocation into CBM or implicitly performing Generate Configuration Data in Function Designer or from the Config View of an Allocatable Group aspect.
Process Graphics Process Graphics Typically you build a graphic display per process function modelled by an object in Functional Structure. The principal steps, corresponding to workflow steps Design / Build Graphic Displays and also to Download and Test Application Software, are: 1. Create a Graphic Display aspect. 2. Edit it with Graphics Builder. 3. Draw / adapt the background picture. 4.
Alarm and Event display. The aspect placed at the top in the default precedence list will appear instead of an aspect which has a lower position in the precedence list in the case that both these aspects are available for the object left-clicked on. 4. Library Structure/Preferences&Customization/Default Precedence List; push the button Add key and find the key MyKey in the list. Move MyKey to the top of the default precedence list by using the arrows. 5.
Alarm and Event Figure 17. Default Alarm and Event List Configurations Feature Pack Functionality The Common Grouped Alarm List Configuration option is available only if System Version 5.1 Feature Pack 1 is installed. The configuration aspects are used as templates defining the look and behavior of Alarm, Event or Audit lists. If you want to have other filter or column settings than the ones in the default templates delivered with the system, you have to create your own as described in the next section.
Alarm and Event A customized list can be created with a descriptive name in the Library Structure with other default configurations or within another structure (usually where it is used). Figure 18 shows an example of the default Common Alarm List configuration view. Feature Pack Functionality The Grouping tab shown in Figure 18 will be available only if System Version 5.1 Feature Pack 1 is installed. Figure 18.
Alarm and Event The configuration view has eight tabs. The Filter tab and the Runtime Filters tab set the type of alarms or events that should be visible in the list, refer to Filtering on page 78. The other tabs set the look and presentation of the list. For more information refer to System 800xA, Operations, Operator Workplace Configuration (3BSE030322*).
Alarm and Event In an Event List Viewer aspect, Alarm filter has four options such as: – – – – All Alarms Object Alarms Object and Descendants Object and Descendants in structure For best performance select either All Alarms or Object Alarms option. Object and Descendants in Structure option gives better performance than Object and Descendants option. Object and Descendants option gives comparatively lesser performance among all the four options.
Alarm and Event The Filter tab holds five tabs. How to set them are described in the following sections. Feature Pack Functionality The Grouping tab shown in Figure 18 will be available only if System Version 5.1 Feature Pack 1 is installed. Figure 19.
Alarm and Event group of controller in for example the Alarm Filter. In this way you may have different alarms and/or external alarm for different Process Sections. When you filter an alarm, you may choose which Process Section this alarm list will cover. This is configured below the Area tab, in the Process Section area. Observe that the used controller(s) must support Process Sectioning. For more information, refer to the controller documentation.
Alarm and Event – 3. Hiding State Choose to show alarms that are in a hidden or in a not hidden state, or both. Select either Event Time or Acknowledge Time in the Filter On area below the Time tab and then set the view range. Newest Event and Oldest Event apply no time filter. To apply a time filter: 4. a. Select Time in the View From or View To area. b.
Alarm and Event b. 3. Select the month, day, year, hour, minute or second segment of the Time area and use the up and down arrows to the right of the area to adjust the time. The actual format of the Time area depends upon how the Format tab was set. Enter a number (1-32) for the From and To in the Priority Level area. Only messages with priority levels that are included in this interval are displayed. Filtering Event Categories Use the Categories area to select message category filters.
Alarm and Event Attribute Filter Tab The Attribute Filter tab allows you to filter on different attributes, refer to Figure 20. Figure 20. Attribute Filter Tab You can for example use wild cards, regular expressions and range expression when creating your filter expressions. Expressions Area.
Alarm and Event Table 4. Expressions Character Meaning . Matches any single character. Same as “?” in a simple query. [] A character class that will match all character inside the brackets. [AB] will match all strings containing the character A or B. ^ [^AB] will match all characters except A and B. - Specifies a range of character or digits if used inside a character class. Example [A-D] matches all characters in the range A to D and [2-6] matches all digits in the range 2 to 6.
Alarm and Event Table 4. Expressions (Continued) Character Meaning | Separates two expressions, for example AI|O in a character class matches both AI and AO ! Negation operator. A!B matches a string starting with A and not followed by a B. There are some abbreviations that could simplify an expression if used. The following exist: Table 5.
Alarm and Event Feature Pack Functionality Grouping The Alarm and Event lists can be configured to display the group alarms. The alarms included in a group will then not appear individually in the Alarm Lists. The configuration to display the group alarms is done in the Grouping tab, refer to Figure 21. Refer to Configuring Alarm Grouping on page 117 for information about the configuration settings. Figure 21.
Alarm and Event Runtime Filtering The Runtime Filters tab is used for configuring the Alarm and Event message list to show only the messages that match the filtering criteria, see Figure 22. It is possible to define several filter sets, which contain attribute filter definitions with expressions. Under the Runtime Filters tab you can add a new filter and edit or delete an existing one.
Alarm and Event Add an Alarm and Event List Create an Alarm and Event List aspect in a Plant Explorer structure as described below: 1. Select the object in the Plant Explorer, to which you want to add an Alarm and Event List. 2. Select New Aspect from the context menu. 3. Select the Alarm and Event List aspect. 4. Click on the Alarm and Event List aspect and select the configuration view. Figure 23. Alarm and Event List Configuration View 5.
Alarm and Event 6. If you want to make a copy of the list configuration, click the Copy Template button. This will create a copy of the selected list configuration and place it on the same object as the list. 7. Go to the Alarm Filter area and select the object filter function: 8. – Select the All alarms to allow this aspect to display alarms and events for all objects. – Select the Object Alarms to show the alarms and events related to the object the Alarm List aspect belongs to.
Alarm and Event Feature Pack Functionality The following icons in the Alarm and Event list tool bar (refer to Figure 24) correspond to the functionalities introduced in System Version 5.1 Feature Pack 1: Alarm Response Navigation To navigate quickly to different aspects from an object. Show List Without Grouping To view the grouped alarms and alarm entries not included in Alarm Groups. View Grouping Configuration To view the Group Alarm Manager or the Group Alarm Definition aspect. 9.
Alarm and Event Figure 26. Auto Start in the Alarm List Status Bar 12. You have now added an Alarm and Event List aspect to your object. Audible Alarms If the Audible Alarms function is configured, active unacknowledged alarms in an alarm list will generate a sound. The sound configuration is by default disabled. Configuration of Audible Alarms is done in two steps, both described below.
Alarm and Event Figure 27. Audible Alarm Workplace Configuration Aspect 3. Select Alarm list aspect to use as alarm filter, that is all alarms that appear in the list will generate a sound. 4. Select Global (silence is set for all workplaces in the system) or Local (silence only for this workplace) silence mode in the drop-down menu. 5. Select the Audible Alarm is enabled check box if you want to enable the function.
Alarm and Event 2. Select the Audible Alarm Configuration object and open the Audible Alarm Sound Configuration aspect. Figure 28. Audible Alarm Sound Configuration Aspect 3. Set one sound for every priority level, by selecting the ... button and browse to a sound file. 4. Select sound mode in the Sound Mode column. The sound can be off (no sound), momentary (one sound when a new alarm gets active) or continuous (a constant sound as long as the alarm is unacknowledged).
Alarm and Event Audible Alarms Toolbar The Audible Alarms Toolbar must be included in the workplace toolbar (such as the Application Bar) for the Audible Alarm function to work properly. Refer to Figure 29.The operator clicks the icon to silence the audible alarms. Figure 29. Audible Alarms Toolbar This is configured on the workplace object for the selected workplace.
Alarm and Event Figure 30. Hot Key Aspect Hiding Hiding is a way of avoiding alarm situations where numerous sequential alarms make it hard to determine the root cause of a problem. By using the hiding function in 800xA, it is possible to hide non-relevant equal alarms. The hiding of alarms is initiated by hiding rules, which can be process conditions or logical expressions. All the hiding rules are kept in the Hiding Mask Manager. Hiding affects the presentation of the alarm list.
Alarm and Event During a specific operational mode, for example a start-up or a shut-down, it is common that alarms, which are relevant during a normal operation, are totally irrelevant. With Hiding Rules it is possible to define which alarms that will be hidden during a specific operation. Single alarms can be hidden as well as alarms from an object and its descendants. An exception to the above mentioned is that the hiding functionality does not affect some of the Alarm Categories, i.e.
Alarm and Event Figure 31. Property View of the Alarm Conditions aspect The Alarm Conditions aspect provides alarm condition properties for conditions defined in Alarm Expressions for the object without any extra configuration. If the conditions are defined elsewhere, such as in a connected OPC AE server, then manual configuration is required. Manual configuration is done through Configuration tab of Alarm Conditions dialog window shown in Figure 32.
Alarm and Event Figure 32. Configuration Tab of Alarm Conditions Dialog Window • Click Add button to manually type in the name of the conditions. • Click Remove button to delete an individual condition. • Click Load button to load all conditions defined for the object from all available alarm sources. Adding the Alarm Conditions aspect to the object types and defining proper condition specific alarm properties can save lot of engineering effort.
Alarm and Event Hiding Rules Hiding rules define conditions under which alarms from a specific object will be hidden. The condition can be an expression containing any boolean OPC Property or alarm condition. One hiding rule can only hold one condition. Logic expressions are possible to create directly in the rules. If you want more complex conditions, these can be made by defining for example soft alarms using Alarm Expressions (refer to Alarm Expression on page 138).
Alarm and Event The Hiding Mask Manager has the following options: The A column shows whether an activating condition is true or not. The list also shows the Name, Activating Condition, Deactivation Delay, and Description of all hiding mask. The buttons in the dialog box are used as follows: • New Mask - Select New Mask to create a new Hiding mask. To edit a Hiding Mask, double-click on the Mask or select a Mask and click Edit Rules (refer to Edit Rules).
Alarm and Event Figure 34. Hiding Mask Definition In this window Hiding rules are added and removed for a specific Hiding mask. Rules can be added or changed directly in this interface. Refer to Configure Alarm Hiding on page 106 for more information.
Alarm and Event Select the hiding condition from the Condition drop-down list. Click Browse to select a condition from the Activating Condition dialog (refer to Figure 35). Figure 35.
Alarm and Event Click Advanced to write your own expressions, Figure 36. See also Alarm Expression on page 138 and Item Syntaxes on page 147. Figure 36. Advanced Activating Condition Edit Condition. An Edit Condition dialog is launched from the Browse button to the right of Activity Condition for a mask, and Condition for a rule. The expression for the row is automatically entered in the Expression field. Expression Field .
Alarm and Event When defining hiding conditions, the time required for an alarm to be hidden can be longer than the time the actual hiding condition is active. To achieve this, a Hiding Off Delay can be defined. When a Hiding Off Delay is defined, alarms will remain hidden during the delay even if the hiding condition is inactive. The off delay can be applied to both the hiding mask (deactivation delay) and hiding rules (hiding off delay).
Alarm and Event • In selected mask This option delimits the searching to selected mask(s). This is the default option. If the Find dialog was opened from the Mask Manager, one or more of the masks was probably selected. If the dialog box was opened from a single hiding mask, that mask is selected. • In all masks This option enables searching in all masks. This is the default option if no masks were selected when the find dialog box was opened from the Mask manager.
Alarm and Event Configure Alarm Hiding To configure Alarm Hiding, a Hiding Mask and a Hiding Rule that defines a Hidden Alarm must be created. 1. Navigate to the Library Structure > Alarm & Event > Alarm Hiding Configuration, refer to Figure 39. Figure 39. Alarm Hiding Configuration 106 2. Select the Hiding Mask Manager aspect. 3. Click New mask to create a new mask. 4. Enter a name in the Mask Name field.
Alarm and Event 5. Define a condition that activates the Hiding Mask. Select a condition for the activating condition from the Activating Condition drop-down box or click Browse to display the Activating Condition dialog box (refer to Figure 40). Select the alarm signal of the object that is to be hidden and click OK. Figure 40. Activating Condition Dialog 6. Enter a delay time (in seconds) in the Deactivation Delay (s) field. 7. Enter a description for the Hiding Mask in the Description field. 8.
Alarm and Event Figure 41. Hiding Mask Definition Dialog Box 10. In the Hiding Mask Definition dialog, click New Rule to add a rule. 11. Enter a value in the Hiding Off Delay (s) field. 12. Click Browse next to the Hide Object field to select the object to be hidden.
Alarm and Event Figure 42. Hide Object Dialog Box 13. Select the object to be hidden and click OK, refer to Figure 42. 14. Click Hide Alarms and select the alarm(s) to be hidden. To hide specific alarms of an object, select Specific Alarms and then select the alarms from the list provided. Hiding specific alarms is enabled only if the application is downloaded to the controller. Select All Alarms to hide all the alarms of the object. 15. Open the object faceplate and click On to activate the Hiding Mask.
Alarm and Event Alarm band Hidden alarm list Normal alarm list Faceplate Graphic element Figure 43. Alarm Lists, Faceplate and Alarm Band The alarms hidden by Alarm hiding mask and rules, does not appear in the Alarm list, see figure above (Figure 43), but in the Hidden Alarm’s list. The faceplate shows that the object has hidden alarms that are active, but the graphic element in the process display does not indicate the alarm condition.
Alarm and Event Alarm Shelving Alarm Shelving is an integrated component of the Alarm & Event function in the 800xA system. Alarm shelving allows the operators to temporarily remove standing or nuisance alarms from the main alarm list and places it on the shelve list. Alarm Shelving is a license-protected feature. The alarm does not reappear on the main list until it is removed from the shelf.
Alarm and Event Figure 44. Alarm Shelving Configuration Object • Basic Settings. This tab provides an option for the System Administrators to enable or disable the Alarm Shelving feature. To enable the Alarm Shelving feature for the operators, select the Shelving Enabled check box (refer to Figure 45). Figure 45.
Alarm and Event The Shelving Enabled check box is unavailable if the user does not have the required license to use this feature. When the Show the Shelve Alarms dialog check box is not selected, alarms are shelved with the default settings. • Shelving Time. Shelving time indicates the maximum time allowed for an alarm before the alarm is removed from the shelf. System administrators can add or remove shelving times from the list according to the plant specifications.
Alarm and Event • Shelving Reasons. Operators can select a shelving reason from the list of reasons provided. A reason helps the operators to keep track of the alarms in the shelf, refer to Figure 47. Figure 47. Shelving Reasons Configuration • Shelving Authentication. Shelving Authentication ensures that the alarms are shelved only by the logged in user. The following authentication options (refer to Figure 48) are available: U 114 – No Authentication Required. – Authentication Required.
Alarm and Event Figure 48. Shelving Authentication Configuration Feature Pack Functionality This section is applicable to the System Version 5.1 Feature Pack 1 release only. Alarm Grouping Alarm Grouping is a feature in the 800xA system that allows grouping of several alarms that require a similar response from the operator. It is recommended that the alarms to be grouped have the same priority.
Alarm and Event • The individual alarm conditions are automatically acknowledged when the alarm group is acknowledged. Enabling Alarm Grouping The Alarm Grouping feature must be enabled before it can be configured and used. Alarm Grouping can be configured only by users that belong to the Application Engineer group having the Modify Alarm Grouping permission. Refer to System Administration and Security (3BSE037410*), Security Configurations for more information.
Alarm and Event 3. Select the Alarm Grouping On check box to display the group alarms in the alarm lists (applies to alarm lists with a configuration where alarm grouping is set to Default). Configuring Alarm Grouping An alarm group is configured using the Group Alarm Definition aspect on the Alarm Object: 1. Navigate to the Library Structure > Alarm & Event > Alarm Grouping Configuration (refer to Figure 50). Figure 50.
Alarm and Event 2. Select the Group Alarm Manager aspect (refer to Figure 51). Figure 51. Group Alarm Manager Ensure that the Alarm Grouping Enabled and the Alarm Grouping On check boxes are enabled. These settings are replicated from the System Configuration Console. The Alarm Grouping On check box controls the behavior of the alarm lists with configuration for alarm grouping set to Default.
Alarm and Event 3. In the Alarm Groups section, click New... to add a new group alarm object. Figure 52. Group Manager - Select Object Dialog 4. 3BDS011222-510 B In the Select object... dialog (refer to Figure 52), select the required structure from the drop-down list and select the object to which the alarm groups is to be configured and click Ok.
Alarm and Event 5. In the Group Alarm Definition dialog, enter the Name and Description for the group alarm. Figure 53. Group Alarm Definition Dialog 6. Select the alarm category from the Category drop-down list. 7. Enter a class range in the Class text field. The class range must be in a range between -9999 and 9999. 8. Type a name for the group alarm condition in the Condition text field. 9.
Alarm and Event 11. Click Add... to add the alarm conditions in the group. A condition can also be manually added to the group. Click OK. Figure 54. Alarm Conditions The objects that are uploaded with Multisystem Integration support are not listed in the Select Object and Conditions... dialog. The conditions defined on an object will appear only if the Alarm Server is running.
Alarm and Event Right-click an alarm entry and select the required Alarm Group from Add To Group in the context menu. Figure 55. Add to Group • To add the alarm entry to a new Alarm Group, select New Group On from Add To Group in the context menu. The object and the parent objects of the selected alarm entry are displayed. Refer to System 800xA Operations (3BSE036904*) for more information.
Alarm and Event Figure 56. Context Menu - Open Group Definition Figure 57.
Alarm Analysis Configuration Select an alarm entry that is not a group alarm and click Toolbar to view the Group Alarm Manager aspect. in the Alarm List Alarm Analysis Configuration The Alarm Analysis function is an effective alarm management function that allows the operators to monitor the quality of the alarm system and analyze problems in the alarm system. The Alarm Analysis function is a license-protected function that is installed as part of the 800xA base system.
Alarm Analysis Configuration 2. By default, the Alarm Analysis aspect selects one Alarm List aspect and one Alarm Analysis Service Group. It is possible to modify the selections in the Alarm List and Service Group drop-down lists (refer to Figure 58). If the configuration of the selected Alarm list is modified, the next reporting period will be uncertain. Figure 58.
Alarm Analysis Configuration Property View of the Alarm Analysis Aspect The Property View (refer to Figure 59) shows the available KPIs for the selected Alarm and Event list. Figure 59. Property View These properties can be: • Visualized in Graphic Displays. Refer to the System 800xA Operations (3BSE036904*) for information about Alarm Analysis Reports. • Logged in the Operator History server. Refer to History Configuration on page 329 for information about configuring the History Server.
Alarm Analysis Configuration Figure 60. Alarm Analysis with OLE DB Sample To be able to access the Alarm Analysis data, the Object path must be specified. The syntax for the path is for example, [Functional Structure]/
Alarm Analysis Configuration The following configurations (some of them described in System 800xA Operations, Operator Workplace Configuration, 3BSE030322*) are not available for the Alarm Logger: All settings under the Sort tab and settings for showing row headers, showing column headers, viewable messages under the Columns tab. Printer Hardware Considerations It is important to use a printer that has good support for reporting its status to the operating system.
Alarm Analysis Configuration In a parallel redundant configuration more than one printer will be active printing the same alarms or events. Parallel redundancy is achieved by creating separate service groups for each printer. How to do this is described in How to Create Parallel Redundancy for the Alarm Printers. on page 133. Setting up an Alarm Printer with the Delivered Default Aspects Here we will setup a printer to function as an alarm printer with help of the delivered default aspects.
Alarm Analysis Configuration 5. Select the Service Provider object, see Figure 62, and open the Service Provider Definition aspect. 6. Select the Configuration tab and choose the node where the printer is connected in the Node drop-down menu. Click Apply. Figure 62. Service Provider Definition Aspect - Configuration Tab 7. 130 Select the Special Configuration tab to customize the list printout. See Figure 63. – Select printer from the Printer name drop-down menu.
Alarm Analysis Configuration 3BDS011222-510 B – Select Transparent background if you want the list to be printed without background color. – Select Enable printing for the list to be printed. – Set the number of lines to be printed on each page in the Max number of printed lines field.The Alarm Logger will buffer alarms until this limit is reached and then print a page. – Set interval for the printouts in the Time interval between printouts field.
Alarm Analysis Configuration – The Information area shows detailed information about the printer, such as status and errors. Figure 63.
Alarm Analysis Configuration 1. Add two or more Alarm Logger, Service Providers to a Service Group in the Service Structure. See Figure 64. Figure 64. Alarm Logger, Service 2. Configure each Service Provider to run on the node where the printer is connected. This is done from the Configuration tab on the Service Provider Definition aspect. 3. Configure the printer attributes below the Special Configuration tab. See Figure 63. How to Create Parallel Redundancy for the Alarm Printers.
Alarm Analysis Configuration Figure 65. Logger Aspects in the Service Structure 4. You may now connect the two Alarm Logger aspects to two different printers. Each printer will create a list according to the info given in the configuration. How to set up a Network Printer To set up a network printer over an TCP/IP port follow the steps below: 134 1. From the Start menu select: Control Panel > Hardware and Sound > Devices and Printers > Add Printer. 2. The Add Printer Wizard will open. Click Next.
Alarm Analysis Configuration Creating an Alarm Band The Alarm Band provides an overview indication of the status of Alarm and Event Lists selected for display. The number of alarms or events are given in figures in the indicating squares and their highest priority are indicated with the defined color. The operator can use an alarm band button to call the list aspect. Create the Alarm Band as described below: 1. Expand the Functional Structure and select the Test object. 2.
Alarm Analysis Configuration Figure 66. Alarm Band Aspect - Config View The result of the configuration according to Figure 66, is displayed in Figure 67. Hidden Alarms Indication Figure 67. Hidden Alarms Indication Hidden Alarms in the Alarm Band. The alarm band shows an indication of hidden alarms. It indicates the fact that alarms are hidden and it provides a link to open the list of Hidden alarms.
Alarm Analysis Configuration 3 unacknowledged, 5 active and 1 hidden alarm. Read more about Hiding on page 95. Refer to System 800xA Operations (3BSE036904*) for description of operation of the Alarm Band. Creating a Sequence Bar Aspect The Sequence Bar provides an overview indication of the status of the Alarm List selected for display. The number of alarms is set at configuration, and may be between zero and ten. The operator may select a band button to call the default aspect for the associated object.
Alarm Analysis Configuration Figure 68. Config View for the Sequence Bar Aspect When configuring a Sequence Bar aspect or an Alarm band aspect, the changes will not be applied directly. The changes are applied after reloading the aspect or restarting the workplace. See System 800xA Operations (3BSE036904*) for information about operation of the Sequence Bar. Alarm Expression Alarm Expression is used for states that are not reported through the process object alarms.
Alarm Analysis Configuration The aspect is configured as shown below: 1. Add an Alarm Expression aspect to an object associated to the property. 2. Configure this aspect according to below: a. Select Condition Alarm or Simple Event in the Message Type area. The text areas Condition, Subcondition and Inactive Message Text are only valid for alarms. b. Select a category from the Category drop-down menu. The predefined categories in the system are shown in the table below. Table 6.
Alarm Analysis Configuration f. Enter a message in the Message Text field. Here you type the message which will be display in the Alarm and Event list. g. Enter a message in the Inactive Message Text field. This message is displayed when the alarm is inactive. h. Enter an expression in the Expression field. This is the expression that gives if the message will be displayed.
Alarm Analysis Configuration For 800xA system version 5.0 SP1a and later versions, each alarm expression receiving bad or uncertain data quality on subscribed properties will generate an alarm representing bad quality. In this situation, when there are several alarm expressions the system can have excess alarms during the system restart. This behavior of alarm expressions can be configured. This configuration is valid for 800xA system version 5.0 SP1a and later versions.
Alarm Analysis Configuration Expression Examples The expression can be more or less complicated, below are some examples: Example 1 - Boiler Temperature. Say, for example, that you have a boiler and you want to have an indication when the temperature goes above 80 and one indication when above 90 degrees centigrade. You do this as follows: 1. Add an Alarm Expression aspect to a propriety Aspect Object. 2. Select Condition Alarm in the Message Type area. 3.
Alarm Analysis Configuration 14. In the Message field, enter the message you want to have in the Alarm and Event list, in this case “+Very High Level”. 15. In the Inactive Message field, enter the message you want to have when the alarm is inactive, in this case “-Very High Level”. 16. Give an expression in the Expression field, in this example Value > 90. 17. Click Apply. Figure 69. Alarm Expression Aspect Example 2 - OPC Server with no event handling.
Alarm Analysis Configuration 5. In the Subcondition field, enter a second description for identification, in this case Property #1. 6. Select a priority level. The value will give the color of the alarm list line according to the setting in the Alarm and Event list definition. In this case we choose priority level 1. 7. In the Message field, enter the message you want to have in the Alarm and Event list, in this case “Alarm from the OPC server”. 8.
Alarm Analysis Configuration For example the object name “valve 3 HI” contains spaces so it must be quoted like this $’valve 3 HI:VALUE’. Valid Operators Valid operators are specified in Table 7. Table 7.
Alarm Analysis Configuration Table 7. Valid Operators for the Alarm Expression Aspect (Continued) Operator Description || Logical OR ?: Condition ex: expr1 ? expr2 : expr3 ! Logical NOT ~ Bitwise complement () Parenthesis, encapsulates expression iif Condition ex: iif(expr1,expr2,expr3) : Resolution ex: object:value . Used to refer to the owner object of the aspect containing the property expression. ex: $’.:Function Block:Value’ .
Alarm Analysis Configuration Table 7. Valid Operators for the Alarm Expression Aspect (Continued) Operator Description true Keyword that can be used as one of two possible boolean values false Keyword that can be used as one of two possible boolean values If numbers are used as property names in the Expression field you must quote them. For example: $’1’>3. For better performance always include aspect whenever specifying properties.
Alarm Analysis Configuration 3. {Object ID}:Aspect Name:propertyName Example: {DA6BFD30-E1D3-11d2-B126-080009DCF329}:Control Connection:VALUE For the syntaxes listed below, the “Object Path” is translated to an Object ID with help of the name resolving mechanism in the system. The path can be anything that the name server can translate into an Object ID. These syntaxes should be used when a more user friendly syntax is required.
Alarm Analysis Configuration 1. Add an Alarm and Event List aspect and an Alarm and Event List Configuration aspect to a proper aspect object. Give them the name Expression List and Expression List Configuration. See Figure 70. Figure 70. Expression List and Expression List Configuration Aspects added to an Object 2. Select the Config view of the Expression List Configuration aspect. Go to the Filter tab and select the appropriate category from the Categories area, in this case Process Events.
Alarm Analysis Configuration 3. Go to the Columns tab and for example select Event Time, Object Name and Message. 4. Click Apply. 5. Go to the Expression List and open the Config View. Open the Configuration Name drop-down menu and select your object. Figure 72. Expression List - Config View 6. Click Apply. You have now configured a special Expression Line, to which you can refer to see all messages created by your Alarm Expressions.
Alarm Analysis Configuration the filtering criteria, are received by the external alarm function the Audible Alarm output is set. The operator can silence the external alarm (resetting the Audible Alarm output) through the silence view. Silence can be done for all configured alarms or for one explicit external alarm. Configuring the External Alarm service Execute the following steps to add a service group and a service provider to the External Alarm service. 1.
Alarm Analysis Configuration 3. Right-click the newly created service group and select New Object from the context menu. Figure 74. External Alarm - Service Provider aspect 4. Enter a name for the service provider and click Create. It is recommended to create a service provider on each aspect server node for redundancy. 5. 152 Select the Service Provider Definition aspect of the newly created service provider.
Alarm Analysis Configuration Figure 75. Service Provider Definition - Selecting the node 6. In the preview area of this aspect, select the Node and click Apply to save the changes. Configuring External Alarm The External Alarm consists of two views, the External Alarm Configuration View and the External Alarm Silence View. External Alarm Configuration View.
Alarm Analysis Configuration uses to subscribe alarms from. Users can also configure the digital inputs and outputs. To create a basic External Alarm Configuration aspect follow the procedure below: 1. Select the object to add an External Alarm Configuration aspect to. 2. Right-click in an empty part of the aspect list and select New Aspect. 3. Select External Alarm Configuration. 4. Type a name in the Name text field and an aspect description in the Aspect description field and click Create. 5.
Alarm Analysis Configuration – If Acknowledged and/or Acknowledge are configured the following applies: When all alarms in the alarm list have been acknowledged, the output Acknowledged will be set. When the input Acknowledge is set, all alarms in the alarm list will be acknowledged. – If Removed and/or Remove are configured the following applies: When all alarms in the alarm list have been removed, the output Removed will be set.
Alarm Analysis Configuration 8. Click Apply. To remove a specific signal right-click on the row and select Delete from the context menu. External Alarm Silence View. In the External Alarm Silence View (see Figure 76) a list with all the configured external alarms is shown. You have the possibility to silence all alarms that are active. Silence is possible for each individual external alarm or as a general silence for all displayed alarms.
Alarm Analysis Configuration To silence an individual external alarm the operator can select the external alarm in the External Alarm Configurations area and then click Silence Selected, or just double-click on the external alarm. To silence all the displayed active external alarms the operator clicks Silence All.
SMS and e-mail Messaging SMS and e-mail Messaging The following subsections describe how you extend basic Alarm and Event handling with SMS and e-mail Messaging. Throughout the SMS and e-mail Messaging procedures, unless otherwise specified, access to aspect views is accomplished by right-clicking on the object and selecting the aspect from the context menu. This opens the aspect in a new window. It is also possible to double-click an aspect in the Aspect List Area to open the aspect in a new window.
SMS and e-mail Messaging Setup and Configuration Workflow The following is a typical setup and configuration workflow for SMS and e-mail Messaging. 1. 2. Set up hardware (one, two, or all). a. Set up GSM hardware. b. Set up Hayes compatible modem hardware and run test utility. c. Run e-mail test utility. Set up system. a. Define default telephone number for Central Paging Terminal of paging service provider. b.
SMS and e-mail Messaging Configure timeout before resending the message and number of attempts before changing destinations. Enable/disable destinations. c. Configure Alarm and Event Service Groups if required. Setup and Configuration Worksheets Appendix C, SMS and E-Mail Messaging, subsection Setup and Configuration Worksheets on page 577 contains worksheets to help in setting up and configuring SMS and e-mail Messaging. • Table 32: GSM Hardware Setup Worksheet.
SMS and e-mail Messaging GSM Hardware GSM hardware (GSM modem or a telephone with a built-in GSM modem) supporting the AT+C command set (GSM 07.05 and GSM 07.07) are compatible with the SMS/GSM Device. Configuration of each individual personal GSM telephone number occurs while setting up the Message Subscriber, refer to Message Subscriber on page 187. A list of GSM service providers is shown in Appendix C, SMS and E-Mail Messaging, GSM Service Providers on page 586, Table 37.
SMS and e-mail Messaging 3. Navigate to: Messenger, Aspect System > SMS Device, Aspect Type > SMS Device, Aspect Category. 4. Select SMS Device in Aspect List Area. 5. When the view appears, click ConfigureSMSDevice. Figure 78.
SMS and e-mail Messaging 6. The Settings dialog appears with the General tab selected; however, the settings in the Ports tab must be set up before the settings in the General tab. Select the Ports tab to produce the view shown in Figure 79. Figure 79.
SMS and e-mail Messaging 7. Click Add to produce the COM Port Settings dialog shown in Figure 80. Figure 80. COM Port Settings Dialog 164 8. Select the COM port the GSM hardware is connected to from the Port: drop-down list box. 9. The settings in the Baud Rate:, Data Bits:, Parity:, and Stop Bits: drop-down list boxes are dependent on the GSM hardware configuration.
SMS and e-mail Messaging Figure 81. PIN and Properties Dialog 10. The PIN is used to prevent unauthorized use of the GSM hardware. If it is required by the GSM hardware, or if it is desired to have the GSM hardware protected by a PIN, check the Query PIN: check box and enter the PIN in the PIN: field. To save and encode the PIN so that it does not have to be entered every time the GSM hardware is turned on, check the Save PIN: check box. 11.
SMS and e-mail Messaging Figure 82. Initialization Dialog 13. Enter the initialization string for the specific type of GSM hardware. A list of GSM hardware is shown in Appendix C, SMS and E-Mail Messaging, Table 38. The table indicates whether or not the specific type of GSM hardware has been tested by ABB and also contains initialization strings. The table presents a sample list and does not contain every compatible type of GSM hardware. There are several ways to enter the initialization string: a.
SMS and e-mail Messaging b. If viewing this instruction with Adobe Acrobat Reader, use the text tool to copy the initialization string and paste it into the Initialization commands frame in the Initialization dialog. c. The information in the table is also available by clicking Help in the Initialization dialog. Click the Index tab, double-click on Initialization in the list that appears, and click Display in the Topics Found dialog. This launches the help file that contains the initialization strings.
SMS and e-mail Messaging The pick list as shown in Figure 84 appears only if SrvSetup.exe was run before starting this procedure. Figure 84. Services Dialog - Pick List 15. If the pick list appears and the service provider appears in the pick list, select the service provider and click Next to return to the Ports tab. OK in the status column indicates the COM port configuration is correct.
SMS and e-mail Messaging 16. Select the General tab to produce the view shown in Figure 85. Figure 85. Settings Dialog - General Tab The Help button shown in Figure 85 will not be accessible. However, the same help contents are available when the Help button is clicked on the SMS Device aspect in the Aspect System structure > Messenger Aspect System (refer to Figure 78). 17. Check the Activate Outbox Spooler: and Activate Inbox Spooler: check boxes. 18. Set the interval for checking for incoming messages.
SMS and e-mail Messaging 19. Select the Services tab to produce the view shown in Figure 86. The pick list shown in the figure only appears if SrvSetup.exe was run before starting this procedure. Figure 86.
SMS and e-mail Messaging 20. If the pick list appears and the service provider appears in the pick list, select the service provider and click Properties. If the service provider does not appear in the pick list, click Add. Either method opens the General tab of the Service Properties dialog as shown in Figure 87. The example shown in the following figure uses Voicestream (T-Mobile) as the service provider. Figure 87. Service Properties Dialog - General Tab 21.
SMS and e-mail Messaging 22. Select the Splitting tab to produce the view shown in Figure 88. Figure 88. Service Properties Dialog - Splitting Tab The check boxes are defined as follows: – Splitting: Splits messages that are too long and sends them in multiple messages. – Optimize Splitting: Prevents the splitting of words. – Enumerate: Enumerates the split parts of the message (e.g. 1/2 Part 1 ..., 2/2 Part 2 ..., and so on).
SMS and e-mail Messaging Check the desired check boxes and click Apply. 23. Select the Messaging tab to produce the view shown in Figure 89. Verify that all fields are empty or 0 and click OK to return to the Services tab of the Settings dialog. Figure 89.
SMS and e-mail Messaging 24. Select the Messages tab to produce the view shown in Figure 90. Check the check box to increase the readability of messages and click Apply. Keep in mind that this may increase the length of the messages. Figure 90. Settings Dialog - Messages Tab 25. Repeat Step 20 through Step 24 to add/select other service providers. 26. Select the Services tab and select the desired service provider in the Default Service: drop-down list box, and click Apply. 27.
SMS and e-mail Messaging Modem Hardware (Hayes Compatible) If a new modem is being installed in, or connected to the machine, perform Step 1 through Step 19. If a modem is already installed in, connected to, and recognized by the machine, perform Step 2 through Step 4 and Step 11 through Step 19. The following is a general procedure for setting up the modem hardware. It may differ depending on the specific modem hardware and the Windows operating system being used.
SMS and e-mail Messaging 7. Select Add/Troubleshoot a Device and click Next. 8. The Search for New Hardware dialog box appears, followed by the Choose a Hardware Device dialog box. 9. Verify that the modem hardware installed in Step 1 appears in the list. 10. Click Cancel. 11. Click Device Manager under the Hardware tab in the System Properties dialog box and the Device Manager appears. 12. Right-click on the modem and select Properties from the context menu that appears. 13.
SMS and e-mail Messaging The parameters of the General tab and the Advanced tab are the most common used by TAP providers, however specific setting should be verified with the provider as they may be different and are subject to change. If the communication settings are changed after the Modem Device has been configured to use the port, the machine must be rebooted for the new settings to take affect. 19. Click OK in the Default Preferences and Modem Properties dialog boxes.
SMS and e-mail Messaging Figure 91. TAP Modem Configuration This dialog is comprised of: 1. A pick-list (combo box) that contains the names of the modems that support TAP communication. 2. An Assign button that will assign the selected modem to be used by SMS and Email Messaging. 3. A “read only" text box that shows the currently assigned modem device. The default Assigned Device is "First Available Modem" and is just as the name implies.
SMS and e-mail Messaging 2. Double-click on TestModemObj.exe. The Test Modem Connection dialog box shown in Figure 92 appears. Figure 92. Test Modem Connection Dialog Box 3. Click Load Request and the modem test utility code appears in the Request field as shown in Figure 93. Figure 93.
SMS and e-mail Messaging 4. If an access number is required to access an outside line, insert it between the T and the 1 in the PhoneNumber line of the code. For example, a 9 might be required to access an outside line. Commas can be used after the access number if a pause is required to access the outside line. The comma usually creates a pause of one second; however it can vary by modem. Refer to the modem hardware documentation for the exact duration. It may also be necessary to change the T.
SMS and e-mail Messaging Figure 94. Test E-Mail Dialog Box 3. Fill in the fields with the required information identified at the beginning of this procedure. 4. Click Send e-mail and verify that the message in the Result field says Email sent and that the e-mail recipient receives the message. It is very important to verify that the e-mail recipient receives the message. Email sent in the Result field only indicates that the e-mail was sent to the queue in the root:Inetpub\mailroot directory. 5.
SMS and e-mail Messaging System Setup This section contains procedures for setting up the following: • Aspect System Structure. – Modem Device. – Email Device. – SMS Device. • User Structure. – Creating User Groups and Adding Users. – Message Subscriber. – Message Schedule. • Operational (Functional, Control, Location, and so on) Structures. – Messenger Event Log. • Service Structure. – Enabling/Disabling SMS and e-mail Messaging. – Checking SMS and e-mail Messaging Status.
SMS and e-mail Messaging Table 9. Paging Service Providers Paging Service Provider1 Central Paging Terminal Telephone Number Arch Wireless™ 18002506325 Cingular ® 18004774550 SkyTel 18006792778 Verizon 18668230501 NOTE: 1. The paging service providers listed in this table are only those tested and verified by ABB as of the original publication of this instruction.
SMS and e-mail Messaging Figure 95. Modem Device 184 4. Delete everything in the Phone Number: field to the right of the T (T is for tone) and the 1. It may also be necessary to change the T. Refer to the specific modem hardware documentation for the appropriate code. 5. If an access number is needed to access an outside line, enter it to the immediate right of the T. For example, a 9 might be required to access an outside line.
SMS and e-mail Messaging Email Device If SMTP was not installed during system installation or operating system set-up, it must be installed before attempting to configure the Email Device. The operating system CD may be needed to complete the installation. For Windows Server 2008, the local SMTP server is not automatically configured. The SMTP server must be manually configured on Windows Server 2008 if the user decides not to use a relay server.
SMS and e-mail Messaging Aspect System Structure, Aspect Category > Messenger, Aspect System > Email Device, Aspect Type > Email Device, Aspect Category 3. Right-click Email Device, Aspect Category and select Email Device from the context menu that appears. This opens the Email Device shown in Figure 96. Figure 96. Email Device 186 4. Delete the existing text from the From: field. 5. Enter a valid e-mail address in the From: field.
SMS and e-mail Messaging Creating User Groups and Adding Users The User Structure holds the defined users and user groups allowed to work in the system. Adding users and defining user roles is performed using the Configuration Wizard. All users must have a related Windows user account. The User object contains information about a user and what the user is allowed to do within the system. It also contains data specific to the user, such as profile configuration values.
SMS and e-mail Messaging 2. Right-click on the user and select Message Subscriber from the context menu that appears. This opens the Message Subscriber shown in Figure 97. Figure 97. Message Subscriber 3. Click New to add the SMS/GSM Device to this user. The New Device dialog box appears with SMS/GSM as the default in the Device: drop-down list box as shown in Figure 98. 4. Click OK. Figure 98. New Device Dialog Box (SMS/GSM) 188 5. Click New to add the SMTP/Email Device to this user.
SMS and e-mail Messaging 7. Click OK. 8. Click New to add the TAP/Modem Device to this user. The New Device dialog box appears with SMS/GSM as the default in the Device: drop-down list box. 9. Click the down arrow and select TAP/Modem from the list that appears in the Device: drop-down list box. 10. Click OK. 11. Figure 99 shows the Message Subscriber at this point in the procedure. Select SMS/GSM in the Message Subscriber and click Edit to access the SMS/GSM Device.
SMS and e-mail Messaging 13. Enter this user’s GSM telephone number to produce a view similar to the one shown in Figure 100. Enter the GSM telephone number without spaces and always include the Country Code. Figure 100. SMS/GSM Device 14. Click Apply and then close the SMS/GSM Device. 15. Select SMTP/Email in the Message Subscriber and click Edit to access the SMTP/Email Device. 16. Enter the e-mail address for the user in the To: field to produce a view similar to the one shown in Figure 101.
SMS and e-mail Messaging Figure 101. SMTP/Email Device 17. Click Apply and then close the SMTP/Email Device. 18. Select TAP/Modem in the Message Subscriber and click Edit to access the TAP/Modem Device. 19. Either accept the default in the Phone Number: field that was entered in the Aspect System Structure under Modem Device on page 182, or change it to the desired telephone number.
SMS and e-mail Messaging Figure 102. TAP/Modem Device The PIN is the 10-digit personal pager and/or mobile telephone number for the current user. 21. Click Apply and then close the TAP/Modem Device. 22. The list in the Message Subscriber shows the configured devices. The top device has the highest priority, followed by the rest in top-down order. To change the order in the list, and thus the priority order, select the device and click Move Up or Move Down.
SMS and e-mail Messaging 24. The Message Subscriber now looks like the view shown in Figure 103. Figure 103. Configured Message Subscriber 25. To enable these devices, make sure the Enabled check box in the Message Subscriber is checked (Figure 103). To disable these devices, clear the check box. If the check box is cleared the user will not receive messages. 26. Click Apply and then close the Message Subscriber.
SMS and e-mail Messaging 3. Right-click on the user and select New Aspect... from the context menu that appears. 4. The New Aspect dialog box appears. a. Navigate to and select Message Schedule from the list that appears to produce the view shown in Figure 104. b. Click Create. Figure 104. New Aspect Dialog Box (Message Schedule) 5. 194 Right-click on the user and select Message Schedule from the context menu that appears. This opens the Message Schedule shown in Figure 105.
SMS and e-mail Messaging Figure 105. Message Schedule (Always Deliver) 3BDS011222-510 B a. To have this user receive messages 24 hours a day, seven days a week, leave Always Deliver selected. b. To disable sending of messages to this user, choose Never Deliver and click Apply. c. To schedule the delivery of messages for this user: – Select Delivery Based on Schedule. – Check the check boxes for the desired days of the week in the Time Schedule frame.
SMS and e-mail Messaging only to define the time range. Click Apply and the time range appears for every day of the week. The schedule is still only active for the days of the week selected. Figure 106 shows an example. When the Use Sunday Start and End time for all days check box is selected, the other days of the week are disabled (the down arrows are grayed out), so the time range for those days can not be changed individually. Figure 106.
SMS and e-mail Messaging When the Use Sunday Start and End time for all days check box is not selected, the other days of the week are enabled, so the time range for those days can be changed individually. Figure 107. Message Schedule (Delivery Based on Schedule) 6. Click Apply and then close the Message Schedule. If the start time is equal to the end time, the messages will always be active for the days of the week selected.
SMS and e-mail Messaging Messenger Event Log The Messenger Event Log is a preconfigured Alarm and Event List that filters out everything but SMS and e-mail Messaging activity. This pre-configured Alarm and Event list is automatically loaded with the SMS and e-mail Messaging system extension as Messenger Event Log aspect on the SMS and e-mail Messaging object in the Control Structure. Multiple instances of the Messenger object, which includes the Messenger Even Log aspect, can be created.
SMS and e-mail Messaging Refer to the appropriate 800xA system documentation for information on creating and customizing preconfigured Alarm and Event Lists Enabling/Disabling SMS and e-mail Messaging SMS and e-mail Messaging can be enabled and disabled in the Service Structure. 1. Use the Structure Selector to open the Service Structure in the Plant Explorer. 2. Use the Object Browser to navigate to: Services > Messenger Server, Service 3. Select Service Definition in the Aspect List Area. 4.
SMS and e-mail Messaging Alarm and Event List (Alarm Grouping) Alarm and Event Lists are part of the 800xA system and are added to objects when building the various structures. Building the various structures is beyond the scope of this instruction. Refer to the appropriate 800xA system documentation for detailed information on the various structures. The Alarm and Event Lists are used to group alarm points together. They define the group of events being sent to the same group of people.
SMS and e-mail Messaging Figure 109. New Aspect Dialog Box (Alarm and Event Message Source) 4. Right-click the object and select Alarm and Event Message Source from the context menu that appears. This opens the Alarm and Event Message Source shown in Figure 110 with the Alarm List tab selected. This tab allows for selection of the Alarm and Event List to monitor. Figure 110. Alarm and Event Message Source - Alarm List Tab 5.
SMS and e-mail Messaging 6. Choose the desired action in the Message action for a new alarm condition frame. The actions are defined as follows: – Only send message if previous alarm condition was acknowledged: Sends only one message for an alarm that goes from active to inactive and back to active again (once or several times). Choose the Only send message if previous alarm condition was acknowledged option carefully.
SMS and e-mail Messaging Figure 111. Alarm and Event Message Source - Message Configuration Tab 9. The checked fields in the Name column are in the order they will appear in the message, with the top field at the beginning of the message (after the prefix, if configured) and the bottom field at the end (before the suffix, if configured). Click Move Up or Move Down to change the position of the field.
SMS and e-mail Messaging Figure 112. Edit Length Dialog Box 11. Enter the new field length (number of characters). Enter 0 for unlimited length. Check with your service provider for information on maximum allowable message length for the device in use. Make sure the total message length is less than or equal to the maximum allowable message length for the particular device. Exceeding the maximum allowable message length may cause SMS and e-mail messaging to malfunction. 12. Click OK. 13.
SMS and e-mail Messaging Message Handler The Message Handler specifies the destinations of the messages. A separate Message Handler is required for each Alarm and Event Message Source. The Log tab in the Message Handler contains a message directing the user to the Messenger Event Log. It has no other functionality. Refer to Messenger Event Log on page 198. 1. Use the Object Browser to navigate to the desired object. 2. Right-click the object and select New Aspect... from the context menu that appears.
SMS and e-mail Messaging 4. Right-click the object and select Message Handler from the context menu that appears. This opens the Message Handler. 5. Select the Message Source tab and click the down arrow in the Message Source field. Select the desired Alarm and Event Message Source from the drop-down list box. This produces a view similar to the one shown in Figure 114.
SMS and e-mail Messaging message or switching destinations, and number of attempts before switching destinations. Figure 115. Message Handler - Destination Tab 9. Click New to create a new destination. The New Destination dialog box as shown in Figure 116 appears. If User Group is selected in the New Destination dialog box, messages go to the device with the highest priority for each user in that group. If User is selected, messages go to the device selected for that user.
SMS and e-mail Messaging Figure 116. New Destination Dialog Box (Users Selected) 10. Select either a User Group or a User device. To select a User Group, perform Step a through Step c. To select a User device, perform Step d through Step g. a. To select a User Group, click Groups. b. Select a User Group from the Groups/Users pane on the left. c. Click OK. d. To select a User device, click Users. e. Select a User from the Groups/Users pane on the left.
SMS and e-mail Messaging Figure 117. Edit Destination Dialog Box 13. Check the Enabled check box so that messages will be sent to the destination. Clear the check box to disable the destination. 14. The Timeout (s.): field contains the number of seconds SMS and e-mail Messaging waits for the user to acknowledge the alarm line corresponding to the message before the message is resent to that destination. If it is the last attempt, it is the number of seconds before switching to the next destination.
SMS and e-mail Messaging destination is a group, the message is sent to the device with the highest priority for every group member before timing begins; however, the lower priority devices do not receive messages. Acknowledgement of the alarm, or receipt confirmation (messages sent via SMS/GSM Device only), by one member of the group is considered successful notification of the group. 19. To change the order in the list, and thus the send order, select a destination and click Move Up or Move Down. 20.
SMS and e-mail Messaging PAGE SAMPLE EPLANT USER GROUP USER 1 HIGHEST PRIORITY DEVICE USER 2 HIGHEST PRIORITY DEVICE USER 3 HIGHEST PRIORITY DEVICE USER 4 HIGHEST PRIORITY DEVICE ALARM ACKNOWLEDGED YES WITHIN TIME OUT PERIOD? NO NO LAST ATTEMPT? YES OPERATOR USER GROUP OPER 1 HIGHEST PRIORITY DEVICE OPER 2 HIGHEST PRIORITY DEVICE OPER 3 HIGHEST PRIORITY DEVICE OPER 4 HIGHEST PRIORITY DEVICE ALARM ACKNOWLEDGED WITHIN TIME OUT PERIOD? YES NO NO LAST ATTEMPT? YES GUEST USER ALARM ACKNOWLEDGED YES W
SMS and e-mail Messaging Alarm Manager Service Group Configuration The Only send message if previous alarm condition was acknowledged in the Alarm and Event Message Source is designed to prevent the same alarm condition from sending several messages due to alarm chatter (alarm going from inactive to active and back again several times over a relatively short period of time). However, this option also requires configuration of the Alarm Manager Basic Service Group in the Service Structure. 1.
System Status 5. Uncheck the Make new alarms entry each time a condition gets active check box. If this check box is selected, each change from the inactive to active state will result in a new alarm. 6. Click Apply to save the entered data. Alarm Storage The number of alarms in main storage is 10,000. This means the Alarm manager server can keep 10,000 conditions (alarms) in memory.
System Status 3. Create Topology aspects and configure the Component view for the objects to represent in the hierarchy above the controllers. 4. If applicable add texts/labels to the new Components with aspect property references that subscribe to status information. Or include other elements with access to and representation of status information, for example ActiveX controls. 5.
System Status 5. Use the object context menu item Goto Parent Diagram (for example on an object shown in the diagram) to navigate to the parent diagram. 6. Navigate through the collection of opened Topology Diagrams using the Workbook tabs. Additionally you can print out the Topology Diagrams.
System Status 216 3BDS011222-510 B
Device Management & Fieldbusses Device Management & Fieldbusses This section describes how to use Device Management software for efficient planning, operation and monitoring of field devices within the 800xA System. Before starting to work with the specific Device Management section, follow the instructions of Device Library Wizard.
Device Library Wizard • The Device Library Wizard has been installed and configured according 800xA Installation and Post-installation guideline. • An 800xA system has been created and started. • The system extensions for the corresponding fieldbus protocols have been added. • The user has Windows administrator privileges, e.g. System Engineer role. Source for Device Types ABB provides a continuously increasing portfolio of 800xA system tested and certified ABB and third party device types.
Device Library Wizard 3. Browse to – Control Products and Systems / 800xA / Device Management FOUNDATION Fieldbus / Device Library - for FOUNDATION Fieldbus device types or – Control Products and Systems / 800xA / Device Management HART / Device Library - for HART device types or – Control Products and Systems / 800xA / Device Management PROFIBUS / Device Library - for PROFIBUS device types and download device type files to your local machine or media.
Device Library Wizard 4. Select the required device type files (multiple selection is possible) and click Open. Figure 121.
Device Library Wizard 5. Click Next to start the extracting operation. Figure 122.
Device Library Wizard 6. Click Finish to complete the extracting operation. Successful extracting operation will be shown in the logger area. Figure 123. Extraction successful window 7. 222 Repeat step 3 to 6 in this chapter for all required device types. Use Main Menu button to navigate directly to the main window. Click Exit to close the program if no more operations are required.
Device Library Wizard Read Release Notes of the Device Types Each device type file includes a release note for the corresponding device type. Please read the release note carefully for detailed information or limitations. The release notes are stored in the root folder of the specific device type.
Device Library Wizard Install Device Types Execute the installation of device types on all 800xA system nodes, where 800xA Device Management software has been installed. Starting with the Aspect Server the following sequence of system nodes shall be considered for installation: • Aspect Server • Connectivity Server • Application Server • Clients Prepare System Node for Device Type Installation.
Device Library Wizard Start Device Type Installation. 1. Open the Device Library Wizard: Start > All Programs > ABB Industrial IT 800xA > Device Mgmt > ABB Device Library Wizard or double-click ABB Device Library Wizard shortcut on the desktop. Windows and 800xA System administrator rights are required to execute the Device Library Wizard on the node. 2. Select Install Device Types to install new device types or re-install device type to the 800xA System. Click Next. Figure 124.
Device Library Wizard 4. Click Next to confirm fieldbus selection. Figure 125. Fieldbus Protocol Selection Dialog 5. The new windows opened list all extracted device type files of the specific fieldbus protocol except those which have been installed already. This window offers two tab cards representing the available device types for installation. – Install view shows the device types that will be installed. – Restore view shows device types that are already installed.
Device Library Wizard Figure 126. Device Selection Dialogue - Install View Device specific release notes can be accessed by right-clicking on the listed device type name. Figure 127.
Device Library Wizard The following table lists the Icons which show the status of the selected device types: Installation successful Already installed Device Type Installation failed Installation is not completed 6. Click Next to confirm the selection. 7. Click Finish to start the installation of the selected device types. Figure 128. Finish Installation Device types already installed in the 800xA System are overwritten.
Device Library Wizard The status of operation is displayed in the logger area. Wait till installation is completed. Next to the Device Library Wizard window, a status window appears, which gives additional information on the installation process. Figure 129. Progress Messages During installation of device types, additional software may be installed on the node, for example, DTM.
Device Library Wizard While installing ABB Instruments device types with device specific DTMs, the DLW installation window may stop responding. Execute the following steps to continue the installation process: 1. Open Windows Task Manager. 2. In the Applications tab, select the device type(s) for which the DTM installation stopped responding. 3. Click the Processes tab and select launcher.exe. 4. Click End Process. 5. In the Task Manager Warning window, click Yes.
Device Library Wizard Successful installation is indicated with Installation completed! entry in the logger area. Figure 130. Installation Successful The Device Library Wizard displays a message indicating successful installation even if the device specific DTMs are not installed completely. Reinstall the device type if the DTM installation fails or stops responding. Device Library Wizard generates a log file. To view the contents of the log file, click View Log in the Device Library Wizard window.
Device Management PROFIBUS & HART Special Handling for 800xA System Restore Additional system restore activities to be performed after restore of a system backup are described in System 800xA Administration and Security (3BSE037410*), sub-section Recover Function-Specific Information. System upgrade from previous to new versions is described in System 800xA, System Upgrade (3BSE036342*).
Device Management PROFIBUS & HART – PROFIBUS Device Integration Library - Basics – optional HART Device Library - Asset Monitoring (if Asset Optimization related system extensions have been loaded) – optional PROFIBUS Device Library - Asset Monitoring (if Asset Optimization related system extensions have been loaded) – optional Function Designer for AC800M Connect, Function Designer for FBB P/H (if engineering related system extensions (Function Designer) have been loaded) • The user has permissio
Device Management PROFIBUS & HART • Function block types, except hidden function block types Online and offline engineering for PROFIBUS and HART devices requires a reservation of the main entity object in the 800xA Plant Explorer Control Structure. As the Operator user role does not have permissions to reserve an entity, it may not be possible to open certain DTMs with the Operator user role. Set a higher access right to the Operator role, if applicable.
Device Management PROFIBUS & HART Figure 131. Control Structure with Fieldbus Topology In order that field devices can be accessed with DTM via the AC 800M controller, the communication path (Tool Routing) must be enabled in each controller. In 800xA system, communication with field devices through DTMs is possible, only when Tool Routing is enabled. Tool Routing is disabled by default. In order to activate it, the processor module of the AC 800M controller, e.g.
Device Management PROFIBUS & HART Set this Property Value to Enabled and click Apply. Figure 132. Tool Routing Enabled for DTM Access Increase TOOLROUTINGNBRCON to 50, if more than 20 HART and PROFIBUS devices containing a DTM are placed below the connected AC 800M controller.
Device Management PROFIBUS & HART Setting up a Fieldbus Topology for PROFIBUS and HART The 800xA system is capable of setting up HART and PROFIBUS communication. Together with the AC 800M Controller and local S800 modules HART devices can be connected. Added with the CI854(A) communication interface (PROFIBUS) and PROFIBUS remote I/O like ABB S800 or S900 a connection to HART devices can be realized additionally.
Device Management PROFIBUS & HART PROFIBUS and HART Fieldbus Preparation in Control Builder M. Before device types in the form of hardware units can be used, the corresponding hardware libraries have to be inserted in the Control Builder M project. The inserted hardware libraries have to be connected to a specific controller afterwards. Hardware libraries represents the physical device type in the 800xA system.
Device Management PROFIBUS & HART Pre-setting before inserting of Field Device Type Object . Two different network areas are available at each AC 800M Controller object: • • ModuleBus at AC 800M Each CI854(A) at AC 800M Instantiation of field devices is possible with the Fieldbus Builder PROFIBUS/HART in Communication disabled mode only. If Communication enabled mode is active, it MUST be deactivated (Communication disabled). Each area must be separately set to Communication disabled mode.
Device Management PROFIBUS & HART Figure 133. Fieldbus Management Aspect 7. The device object can be switched to Communication enabled mode by selecting Communication enabled in the context menu. Fieldbus Builder Communication Mode (Device Functions...) 1. Select the ModuleBus or CI854(A) object in the Control Structure. 2. Click with the right mouse button to open the context menu. 3. Select Device Functions in the context menu. Figure 134. Device Functions...
Device Management PROFIBUS & HART 4. The sub menu of Device Functions... indicates the current mode (will be Communication disabled for fieldbus configuration). The sub menu allows also changing the mode by selecting the menu item. Insert S800 I/O Modules at AC 800M ModuleBus. This subsection can be skipped, if no HART devices are used on local S800 I/O modules. For instantiation of local S800 I/O modules to AC 800M Controller refer to Create Hardware Units on page 38 and the following.
Device Management PROFIBUS & HART 4. To insert a PROFIBUS communication interface on the controller, select the Hardware object, placed below the AC 800M controller. Figure 135. Control Structure with AC 800M 5. Right-click with the mouse and select New Object in the context menu. 6. Browse to the required communication interface, e.g. CI854 for PROFIBUS. DTMs exchange data with field devices using acyclic communication (DPV1). CI854(A) supports this type of communication, although CI851 does not. 7.
Device Management PROFIBUS & HART Do not use the Replace Unit function for the units which have a DTM assignment. Use “MoveDown” and “MoveUp” in Control Builder to adapt the slave address. Otherwise, online operation with DTM may not be possible for this unit. PROFIBUS Remote I/O with HART Modules. 1. Open Plant Explorer. 2. Switch to Control Structure. 3. Open the substructure below the Project object. 4. To insert a Remote I/O communication interface on the PROFIBUS, select the CI854 object. 5.
Device Management PROFIBUS & HART Insert HART Device Type Objects To create or delete an instance of the HART device types with an Application Engineer user role, either of following setting has to be done: • Change the security definition for Application Engineers to the permissions Operate and Operator Configure. • Add the Operator role also to the Application Engineer role. HART Device Type Objects are installed with the Device Library Wizard.
Device Management PROFIBUS & HART 4. Select the I/O module (e.g. at ModuleBus or Remote I/O), where the HART Device Type Object shall be inserted, for example S800’s AI895. 5. Click with the right mouse button to open the context menu. 6. Select New Object in the context menu. Figure 136. Creating a new Device Object Instance 7. A folder structure containing the various device objects appears. Click "+" to open the next level of the partial tree and select the required device object.
Device Management PROFIBUS & HART 8. Enter a name for the specific device in the Name box, e.g. the TAG. Figure 137. Selecting a Device Object 9. Click Create. The new device object is placed below the I/O module object. 10. Repeat steps 4 to 9 until all of the desired device objects have been placed below the I/O module. HART I/O modules always provide multi-channel support. This allows the user to connect several HART devices at one I/O module.
Device Management PROFIBUS & HART Channel Allocation on HART I/O Modules. The following operations must be carried out to assign HART devices to defined channel at the I/O module: 1. Open Plant Explorer. 2. Enable 800xA preview window, if applicable. The preview window is located in the right lower corner of 800xA Plant Explorer. If the preview window is disabled, double-click the required aspects to access them. 3. Switch to Control Structure. 4. Open the substructure below the Project object. 5.
Device Management PROFIBUS & HART 9. The HART device is selected and moved to the required channel by pressing and holding down the mouse button (drag and drop). The HART device is automatically connected to the channel. 10. If the check box next to the device object is selected, the status window is updated and the object information is displayed. Figure 139. Assigned Device Objects with DTM Information 11.
Device Management PROFIBUS & HART Insert PROFIBUS Device Type Objects in 800xA Plant Explorer. It is recommended to always use Control Builder M to create instances of PROFIBUS device types. For details, refer to Insert PROFIBUS Device Type Objects on page 251. 1. Open Plant Explorer. 2. Switch to Control Structure. 3. Open the substructure below the Project object. 4. To insert a PROFIBUS Device Type Object on the CI854, select the CI854 Hardware object. 5.
Device Management PROFIBUS & HART 8. Click Create. 9. To insert a device specific module below the PROFIBUS master object, select the PROFIBUS master object. 10. Right-click on the mouse and select New Object. 11. Browse to the required device module in the hardware library, e.g. ABB_TFx12_Temp1. Figure 141. Select PROFIBUS specific device module 12. Enter the position number of the module placed, e.g. 0, in the name box. Position number 0 means slot number 1.
Device Management PROFIBUS & HART Insert PROFIBUS Device Type Objects in Control Builder M Project. 1. Open the Control Project and switch to the Control Builder M project window. 2. Browse to and select the CI854 object. 3. Right-click on the mouse and select Insert Unit. 4. Browse to the required PROFIBUS master object in the connected hardware library catalog, e.g. ABB_TFx12_YP0_v1_0. Figure 142. Select PROFIBUS master object in the CBM Project 5.
Device Management PROFIBUS & HART 9. Browse to the required device module, e.g. ABB_TFx12_Temp1. Figure 143. Select PROFIBUS specific device module in the CBM Project 10. Select the position number of the module placed, e.g. 0, in the pull down menu. Position number 0 means slot number 1. Specific device module to be related to the slot number. Additional information about slot number can be found in corresponding Device Type Release Notes. 11. Click Insert. 12.
Device Management PROFIBUS & HART Configuration and Commissioning of Field Device Type Objects After inserting the HART or PROFIBUS Device Type Objects can be configured for application by means of Device Type Manager (DTM). HART Device Type Objects are not handled by Control Builder M. Higher-level assemblies such as PROFIBUS devices, Remote I/Os and CI854 are mainly handled in the Control builder project.
Device Management PROFIBUS & HART Instance data can be verified and exported with the Fieldbus Management in Communication disabled mode, but loading is only possible in Communication enabled mode. To load fieldbus lines, select the line through the context menu of the Fieldbus Management and then click on Download selection to start. Verify. Selecting the verify option in the Fieldbus Management menu compares the online device data with the offline configuration data set stored in System 800xA.
Device Management PROFIBUS & HART DTMs can be started in Communication disabled mode to configure field device objects offline or, if changes are to be made directly in the device, in online mode by changing the mode to Communication enabled. Depending on the mode, the DTM will appear with various functional windows. The various modes are selected via the Fieldbus Management aspect of the relevant device object. Communication enabled mode starts all DTMs required for the communication sequence.
Device Management PROFIBUS & HART 5. Other DTM views can be activated via the menu bar of the Device Management window. Figure 144. Preview Window with DTM and Context Menu via Device Management. Open DTM through the Context Menu of Control Structure in Plant Explorer 256 1. Open Control Structure in Plant Explorer. 2. Open the project sub-structure and select the field device type object. 3. Click with the right mouse button to open the context menu.
Device Management PROFIBUS & HART 4. Select Device Functions... > “DTM Application” in the context menu. Figure 145. Device Functions... 5. The DTM with the selected application appears in a new window 6. Other DTM views can be activated via the menu bar of the DTM window or via Device Functions... > “DTM Application” in the context menu.
Device Management PROFIBUS & HART Configuration of OPC Server PROFIBUS/HART The OPC Server PROFIBUS/HART shall be configured only, if Asset Optimization for asset monitoring is installed and used in System 800xA. It is not allowed to use OPC server PROFIBUS/HART to acquire device data to applications such as Trend, Graphics, Faceplates etc. Only Asset Optimization server can be a client to PROFIBUS/HART OPC Server.
Device Management PROFIBUS & HART 2. Select the control network in the fieldbus topology. The following steps shall be done on every control network, placed in the system and containing the FBB-OPC Data Source Definition aspect. 3. Select FBB-OPC Data Source Definition aspect. Figure 146.
Device Management PROFIBUS & HART 4. Select the Connectivity tab. Figure 147. Connectivity Tab 5. Click New…. Figure 148.
Device Management PROFIBUS & HART 6. Change the name of the service group, if required. The service group name can be found under Service Structure > Services > OpcDA_Connector. Example of a service group name: FBB_OPC_ControlNetwork1 Each control network needs a unique service group name and shall not given twice in the system 7. Click Add.... Figure 149. Adding a Service Provider 8. Select the Connectivity Server system node on which the OPC Server PROFIBUS/HART shall be executed. 9.
Device Management PROFIBUS & HART Figure 150. OPC Server Configuration Complete Creating OPC Topology File . To provide the complete fieldbus topology of the 800xA system to the OPC Server PROFIBUS/HART, it is mandatory to switch all CI854 objects and the ModuleBus objects to the Communication enabled mode once. Configuration of the OPC Server PROFIBUS/HART shall be done for each control network object configured in the system. 262 1. Open the Control Structure in Plant Explorer. 2.
Device Management PROFIBUS & HART 8. Select Configure OPC Server. Figure 151. Configuring the OPC Server 9. The message window indicates the current status of the configuration. If more than one Control Network for AC 800M or Multiplexer is available in the 800xA System, the OPC Server PROFIBUS/HART needs to be configured for each Network, if applicable. Changes in the topology require a re-configuration of the OPC Server. 10.
Device Management PROFIBUS & HART 1. Open the Plant Explorers Control Structure and select the FBB-OPC Configuration aspect (as default at the instantiated Control Network object). Figure 152. Selected FBB-OPC Configuration Aspect 2. In the preview window select the tab OPC Timing Statistics. Figure 153.
Device Management PROFIBUS & HART The cycle time of the OPC Server is set to a default value in the following aspects at the Asset Optimization node in Plant Explorers Control Structure: – – DIP HART Asset Monitor Data Source aspect (HART devices) DIP PROFIBUS Asset Monitor Data Source aspect (PROFIBUS devices) By rule of thumb the following timings should be configured in the specific aspect for the particular fieldbus protocol: The default cycle times mentioned below are only indicative numbers.
Device Management PROFIBUS & HART . Figure 154. OPC Cycle time Configuration 6. Confirm changes with Apply. 7. Load all required Asset Monitors of the instantiated device types into the Asset Optimization Server (refer to Asset Optimization section for more details). 8. In the Plant Explorers Control Structure select the FBB-OPC Configuration aspect (default at the instantiated Control Network object). 9. In the preview window select the tab OPC Server Statistics. Figure 155.
Device Management PROFIBUS & HART 10. Wait according to the configured Update Time, till the Duration Time is displayed next to the Update Time entry as shown in Figure 155. If the Duration Time is less than the Update Time, the OPC Server is able to call all configured OPC items in one cycle.
Device Management PROFIBUS & HART HART Devices in Function Diagrams HART Device Type Objects in 800xA system are supported in Function Designer by default. To configure a signal connection to a HART device in a Function Diagram perform the following steps: the Function Component for the HART device from Object Type Structure: Object Types > Field Device > \HART Actuators or Object Types > Field Devices > HART Transmitters, e.g. ABB Generic HART Transmitter. 12.
Device Management PROFIBUS & HART 2. On the Boards object in the left pane of the IO Allocation tool click right to open the context menu. 3. Click Insert Elements and add the needed boards from the Control Structure of the structure browser. 4. Drag and drop the HART Device Type Objects from the right pane to the left pane, for example on the Boards object to automatically do the allocation. Figure 157. IO Allocation of HART Devices 5.
Device Management FOUNDATION Fieldbus PROFIBUS Devices in Function Diagrams There are two possibilities to support documentation and navigation needs for a PROFIBUS device in Function Diagrams of Function Designer: • Referencing the IO variable representing the device in the control application using a diagram reference. • Adding an own Function aspect with a Function Component to the device type. Refer to System 800xA Engineering, Engineering Studio Function Designer (3BDS011224*).
Device Management FOUNDATION Fieldbus If the 800xA system includes several HSE subnets, which can be configured by different instances of Fieldbus Builder FF. All Fieldbus Builder FF instances and the Plant Explorer Workplace work with the same FF libraries. A new opened instance of Fieldbus Builder FF always provides the actual FF libraries. If during runtime of a Fieldbus Builder FF instance a library update has been performed it gets visible in the status bar by a red LIB writing.
Device Management FOUNDATION Fieldbus It is possible to switch directly between configuration and commissioning modes.
Device Management FOUNDATION Fieldbus Target Group The instructions address users, who are familiar with FOUNDATION Fieldbus and are acquainted with the parameter setting of the FF devices used. Step 1: Check, Save, and Upload FF Libraries After device object types have been added to the FF device library with the Device Library Wizard, a plausibility check of the FF libraries has to be carried out following the procedure below. 1. Open a Plant Explorer Workplace. 2.
Device Management FOUNDATION Fieldbus 8. After a successful check for plausibility, save the FF libraries by means of FF Object editor > Save. 9. Exit Fieldbus Builder FF by FF Object editor > Exit 10. Return to the Plant Explorer Workplace and select the FFUpload aspect. 11. Click Upload. The upload mirrors the FF class objects checked in Fieldbus Builder FF to the Object Type Structure in the Plant Explorer Workplace. 12.
Device Management FOUNDATION Fieldbus 3. Select the HSE Subnet object and enter a name for the object (refer to Figure 160). Figure 160. Selection of the HSE Subnet 4. Insert the object by clicking Create. You have thereby created a new HSE subnet with up-to-date data for the FF device and block classes from the FF Library. In the following this HSE subnet will be configured with Fieldbus Builder FF.
Device Management FOUNDATION Fieldbus 3. Fieldbus Builder FF starts with an empty HSE subnet. Only a new and empty HSE subnet does not need to be reserved for editing in Fieldbus Builder FF. In this case the reservation will be set automatically. Create HSE Subnet Structure 4. Configure your desired FF network by successively inserting objects in the sub-level of an object by means of 5. a) In Plant Explorer Workplace: Context menu > New Object...
Device Management FOUNDATION Fieldbus An HSE subnet with all the FF objects listed in Table 10 is shown in the example in Figure 161 (displayed in Fieldbus Builder FF). Figure 161. Example of a Configured H1 Link Set Parameters After the FF devices have been inserted into the FF Application, their parameters must be set following the procedure below. 6. 7. 3BDS011222-510 B Define the IP addresses and network settings for all stations in the HSE Subnet: a.
Device Management FOUNDATION Fieldbus Select the OPC Server FF and enter IP address in the Client/Server network as well as IP address in the HSE subnet. The properties dialogs will appear automatically while creating the new objects. All network settings are condensed displayed in the Network Configuration dialog and can be edited there as well. Instantiate Function Blocks (optional) Some H1 devices do not display any function blocks after the insertion.
Device Management FOUNDATION Fieldbus The number of created instances is displayed in the Created Instances column and the available number of function blocks for each type is displayed in the Available Instances column. Figure 162. Instantiation of Function Blocks Check and Save Project 10. After all the FF objects have been edited, check the whole project for plausibility by means of Tools > Check whole project or Check button.
Device Management FOUNDATION Fieldbus has not been generated completely, and indicates an element which has not yet been checked for logical errors or which has an error (refer to Figure 163). Figure 163. HSE Subnet Partially Checked for Logical Errors 11. After a successful check for plausibility, store the HSE Subnet by means of FF Object editor > Save or Check button. 12. Exit Fieldbus Builder FF. Upload HSE Subnet 13. Return to the Plant Explorer Workplace.
Device Management FOUNDATION Fieldbus Step 3: Configure the FF Application For executing the desired automation function, FF blocks are linked together in an FF Application. In the following example a simple control loop, which is controlled by means of an external set point from the AC 800M controller, is configured in FF devices. 1. Select an FF Application object in the Plant Explorer Control Structure (refer to Figure 164). Figure 164. Selection of the FF Application 2.
Device Management FOUNDATION Fieldbus 3. Reserve node by means of Context menu > Reserve node. Then the H1 Link where the Application is connected to will be locked for editing. 4. Select the application object in the object tree. Fieldbus Builder FF opens the FF Application Editor for the selected object. The editor starts with an empty canvas. Now function blocks can be placed on the canvas of the editor and connected to each other following the procedure below. Insert Function Blocks 5.
Device Management FOUNDATION Fieldbus 7. After insertion, give the function blocks a tag name: a. Select the function block. b. Open the parameter dialog by means of Edit > Properties or Context menu > Properties. or simple double click the function block. c. Enter the tag name in the Name field. d. Click OK to close the dialog. Insert FF Signals FF signals are used for the connection to the AC 800M controller or between H1 links/FF applications within the HSE subnet. 8.
Device Management FOUNDATION Fieldbus d. The signal dialog is now opened. Check the settings in the dialog. It is recommended to use the default setting Auto for Data Type and Usage. These settings will be defined during the commissioning process. Table 11. FF Signal Settings Data Type Auto Analog Discrete Usage Auto H1 HSE e. Confirm these settings by means of Apply. f. Select the Host by which the signal shall be used in the Used by area of the signal Properties dialog.
Device Management FOUNDATION Fieldbus Connect Function Blocks and FF Signals 9. Connect the function block pins as shown in Figure 169. To do this, drag the connecting lines with the left mouse button held down, the routing of the signal line is automatically defined by Fieldbus Builder FF. Figure 169. FF Application The FF PID control loop requires a feedback from the FF AO block. In the example, the BKCAL_OUT of the FF AO block is fed back to the BKCAL_IN of the FF PID block.
Device Management FOUNDATION Fieldbus a. Open the Properties dialog of the function block by double clicking the block in the FF Application object or in the H1 device object (refer to Figure 170). Figure 170. Block Properties Dialog b. 286 At least check the parameters of Table 12 during parameter setting.
Device Management FOUNDATION Fieldbus Table 12. Parameters to be Checked Parameter Description ALERT_KEY The value of the ALERT_KEY must be in the range 1 .. 255. MODE_BLK The mode parameter consists of several parts. The Target mode defines the mode of operation which the block should adopt. The modes of operation into which the block can be switched via the Target mode are specified by means of the Permitted Mode. The Actual mode shows the current mode of the block.
Device Management FOUNDATION Fieldbus – Configure FF alarms and events for each block. 11. For each FF device which shall support FF alarms and events enable this feature following the procedure below: a. Open the Properties dialog of the resource block. b. Check the “Reports” bit of the FEATURE_SEL parameter. c. Configure the parameter LIM_NOTIFY. This parameter defines the maximum number of alarms the device sends out an event notification for, without receiving a confirmation.
Device Management FOUNDATION Fieldbus b. a priority (e.g. HI_PRI) for each alarm point, and c. a limit (e.g. HI_LIM) for each alarm point. FF contains the alarm priorities 0 to 15. Priority 15 represents most important alarms. The FF alarm priority impacts the communication of an alarm. In the case of multiple alarms in a FF device, alarms with the higher priority are communicated with preference. In particular there is no notification for alarms of priority less than 2.
Device Management FOUNDATION Fieldbus c. enter alarm texts for FF Process alarms (refer to Figure 171). Figure 171. Alarm Parameters Tab Configure Data Exchange with AC 800M Controller 15. Configure the HSEHostCI860 object for data exchange with the AC 800M controller following the steps below. 290 a. Select the Signal list by means of Tools > Signal List. b. Select the signals to be configured. Multi selection is possible. c. Check the Host by which the signal shall be used.
Device Management FOUNDATION Fieldbus d. Define Data Type and Direction for the channel; refer to Table 14. Table 14. Channel Definition Data Type Analog (DS-65) Discrete (DS-66) Direction FF -> IEC61131 from the FF device to the AC 800M IEC61131 -> FF in the opposite direction Figure 172.
Device Management FOUNDATION Fieldbus Signals displays read only the assigned signals and its configuration (see Figure 173). Figure 173. Example of an HSEHostCI860 Configuration The thus defined channels of the CI860 module can be assigned with I/O variables in Control Builder M. Schedule A schedule which includes the time sequence of the function blocks and communications from FF signals is automatically generated on storage of the FF Application object.
Device Management FOUNDATION Fieldbus select the H1 Schedule object (refer to Figure 174). For experienced users, there is the possibility of moving the individual blocks in the schedule manually. Figure 174. Example of a Schedule Check and Save Project 16. After the FF Applications have been created, check the configuration for plausibility by means of Tools > Check whole project and correct any errors which occurred. 17.
Device Management FOUNDATION Fieldbus 20. After correction of the errors, an upload can be started manually by clicking Upload. After completion of the upload the Available Subnet Version and the Uploaded Version are identical. The configuration of the FF network with the FF Application has now been completed. Subsequently the configured data must be distributed to the connected devices.
Device Management FOUNDATION Fieldbus 5. Switch Fieldbus Builder FF into the commissioning mode by means of FF Object editor > Commissioning. Status information for the individual objects is displayed in the commissioning mode. 6. Open the Write Linking Device Settings dialog by means of Object > Linking device initialization and address assignment... 7. Start the precommissioning of the linking device by means of Continue (refer to Figure 175). Figure 175.
Device Management FOUNDATION Fieldbus The live list is divided into two sections (refer to Figure 176). The H1 devices Figure 176. Device Assignment actually present in the H1 link are listed in the right-hand section. The left-hand section contains a list of the configured H1 devices. 10. Select an active H1 device in the right-hand section and use the mouse to drag it to the configured H1 device in the left-hand section which contains the configured data for the active H1 device.
Device Management FOUNDATION Fieldbus Load FF Devices 12. Select the H1 Link, a Linking Device or if sufficient only a single H1 device. The complete HSE subnet can also be selected for commissioning. Previously not reserved objects will not be considered for commissioning. 13. Open the Online dialog with Object > Online Dialog... (refer to Figure 177). Figure 177. Online Dialog 14. Wait until version check has completed, then switch to Download to device tab.
Device Management FOUNDATION Fieldbus on-line version check has been performed yet (e.g. because it was not reserved). It is recommended not to change the default Global Download settings which will result in an incremental download with block parameters not being loaded and the LAS on the H1 links not being stopped. Default Global Download settings do not include block parameters. To include block parameters select Changed parameters or All parameters in the Block Parameters Download settings. 15.
Device Management FOUNDATION Fieldbus a. Select an FF Application object. b. Move the mouse cursor on a block pin or an FF signal line to display the current values of input or outputs (refer to Figure 179). Figure 179. Online Data 18. Display Online data for block parameters: a. Open the Properties dialog of a function block by double clicking the block in the FF Application object or in the H1 device object (refer to Figure 180). Figure 180.
Device Management FOUNDATION Fieldbus The column Value shows the Current values, a parameter value displayed with a yellow background indicates that the current value read from the device is different from the configured value in the Fieldbus Builder FF database. The configured values are displayed in the column Configuration Value at the right end of the table. In commissioning mode methods are processing on the current values.
Device Management FOUNDATION Fieldbus Upload HSE Subnet 21. Exit Fieldbus Builder FF. When the Fieldbus Builder FF configuration is being saved, the FF data are automatically uploaded to the PPA. In the FF Management aspect of the HSE Subnet object the status of the last upload is displayed by a traffic light. When the upload failed, the Available Subnet Version and the Uploaded Version are different. 22.
Device Management FOUNDATION Fieldbus 4. Select the appropriate HSEHostCI860 object from an HSE Subnet in the following dialog (refer to Figure 181). Figure 181. Insertion of an HSEHostCI860 Object 5. Press Insert to confirm the insertion. Thus a reference of the HSEHostCI860 object has been inserted below the CI860 object as shown in Figure 182. Figure 182.
Device Management FOUNDATION Fieldbus 6. Press Close to close the dialog. 7. Select the CI860 object in Control Structure and switch to Control Builder M. 8. Open the hardware editor via the context menu by means of Editor (see Figure 183). Figure 183. Hardware Editor of the CI860 Object The FF signals assigned in Fieldbus Builder FF are displayed in the Connections tab in the Protocol Info column. 9.
Device Management FOUNDATION Fieldbus The data for the FF objects is available in the Control Connection Aspect. Graphics, faceplates, trends, archives, among others, can access this data. Refer to the respective manuals to configure these applications. For further configuration information on Fieldbus Builder FF refer to System 800xA Device Management, FOUNDATION Fieldbus Configuration (3BDD012902*).
Structured Data Logger Structured Data Logger Structured Data Logger (SDL) is used to log sets of production data typically residing in a controller. 800xA access these data through Process Control Aspects. The data to be logged needs to be prepared by the controller application before they can be read by SDL. For the preparation of data in the controller see Controller Data Exchange on page 315.
SDL Architecture Figure 184. SDL Overview SDL Manager Aspect System consists of Aspects for • Configuring the SDL LogType record layouts. • Configuring the individual SDL Logs with the connections to the process (Control System). • Viewing logged records. Data records are logged by SDL Collector Service.
SDL Configuration in SDL database. More Collector Services are allowed to support different SDL databases typically used for different purposes. SDL Configuration The SDL configuration comprises the setup of SDL Logs using aspect types of SDL Manager Aspect System. SDL provides two new aspect types: • SDL LogType. • SDL Log. SDL Collector Service must be configured using 800xA standard Service Group Definition aspect, to collect data for the configured SDL logs.
SDL Configuration Figure 185. Configuring SDL Log Type SDL LogType aspect is Enabled (or Disabled) for collection of data, which affects all SDL Logs using this LogType directly, whereas SDL Logs using LogTypes that are extended from this LogType are not affected. SDL LogType aspects are connected to atleast one SDL Collector service. This is explained in System 800xA, Post Installation (3BUA000156*). SDL LogType aspect Name can be used by other programs to recognize SDL Logs of interest.
SDL Configuration • A Data Type (Integer, Float, String, and Date). • A Mandatory flag used by SDL Collector Service. The SDL Collector stores the value and 'OPC Quality' of the properties. If the Mandatory flag is set, then SDL Collector is forced to wait until the property has 'good OPC Quality'. See SDL Collector Functions on page 313. SDL LogType aspects can extend an existing LogType. Inherited properties cannot be modified. Figure 186 is an example of extended LogType.
SDL Configuration record to the properties of other aspects. SDL Log aspects can be added to any object including object type objects. It is recommended to have SDL Log aspects on objects in Object TypeStructure with Aspect Control inherit flag enabled and to bind the SDL Log aspect properties by relative paths. When the object is instantiated, the properties are bound automatically to absolute paths of actual process values.
SDL Configuration The properties are bound to properties of other aspects using the Property Browser shown in Figure 188. The Binding of properties is expressed either as an absolute path or a relative path to the property. The relative path is useful for object type objects. Figure 188. Item Property Browser The Property Browser browses properties on aspects in a similar manner as the property browser of the Graphics Builder does.
SDL Configuration Table 15.
SDL Data View The time taken to log a data of the data type String in SDL may be greater compared to Integer or Float variables. SDL SoftAlarms Alarm type per object: SDL Collector Service Group and SDL Collector Service Provider aspects: • "Data base connection” – error connecting to the database. • "Data base error return" – error during store of SDL Log data. Objects with SDL Log aspect: • "OPC Add item error" with a list of faulty OPC items – properties do not exist. • "OPC Read time out".
SDL Collector Functions Figure 189. SDL Collector States Figure 189 shows various states of SDL Collector and the actions against each stage is given below.
Controller Data Exchange STATE ACTION 1 SDL Collector locates enabled SDL Log aspects that refers to the service. A service is referred through the SDL LogType of SDL Log aspect. 2 SDL Collector subscribes TRIGGER properties of SDL Log aspects. 3 SDL Collector waits for 'Data Changed' event on TRIGGER's. 4 SDL Collector reads all the properties of data record. 5 SDL Collector checks the OPC Quality of mandatory properties.
Process Interface Control logic that supports the Trigger/Acknowledge handling must be implemented in PLC from which process values shall be retrieved. The SDL provides ready made control logic as control module types for the AC 800M controller. These libraries are distributed on the 800xA distribution media. By default the following control logic softwares are included: • SDL_DataExchangeLib for AC 800M.
Using the DataExchange Control Module Using the DataExchange Control Module DataExchange Library Control Module included in SDL_DataExchangeLib library is supplied with SDL. Figure 190 shows the parameter interface, and part of sequencer implementing the Data Exchange Protocol. Figure 190. Data Exchange Control Module Type To use this library module: • Create an application Control Module (e.g.: Tank1). • Make an instance of DataExchange Library Control Module (e.g.
Using the DataExchange Control Module • Create 5 variables (e.g.: var_trigger, var_acknowledge, var_start, var_asb_to, and var_arb_to). • Bind these variables to the corresponding formal parameters of DataEx1, i.e. TRIGGER_Word, ACK_Word, Start, ASB_TO, and ARB_TO respectively. • Make further property variables that SDL Log properties are bound to. • Aggregate values for the property variables. • Initiate communication with SDL Collector by setting variable var_start = “true”.
Data Exchange Protocol Data Exchange Protocol Figure 191 shows a simplified description of this protocol. Figure 191. Data Exchange Protocol, Simplified Description The direction of application data flow exchanged by the protocol is from Control network (PLC) to SDL Collector (PC).
Data Exchange Protocol Figure 192 shows the detailed view of protocol work flow. Figure 192. Data Exchange Protocol, Detailed Description Characteristics of the protocol is listed below: 320 • A protocol cycle is always initiated by PLC. It will prepare data and raise Command bit when the state is 0. • The PLC will not lower its Command bit until the PC has Acknowledged it (i.e. raised the Acknowledge Bit by copying TRIGGER word to ACKNOWLEDGE word).
Data Exchange Protocol Without Acknowledge • If Retry Counter (RC) reaches maximum value, that can be stored in TRIGGER word part. If time-out happens, it will wrap to 1. Hence Retry Counter gets incremented and wrapped within the given protocol cycle. • The protocol is prepared with a simple transaction control feature. Transaction Counter occupies 2 most significant bytes of TRIGGER and ACKNOWLEDGE word.
Data Exchange Protocol Without Acknowledge Figure 194 shows the detailed view of protocol work flow. Figure 194. Data Exchange Protocol without Acknowledge, detailed description Characteristics of the protocol is listed below: 322 • A protocol cycle is always initiated by the PLC. It will prepare data and raise Command bit when the state is 0. • PLC will lower its Command bit by itself. The data will be lost, if the PC has not read the data at that time.
Performance wrapping), it is useful to the PC to determine whether a data package is about to be duplicated or it has been lost. As there is no Acknowledge associated with this protocol, the SDL Collector buffers the data prepared by PLC before storing it in the SDL database. This will reduce the possibility of data loss due to slow database response.
SQL Server SQL Server SDL data collection never gives severe loads on the system. But it will give server loads, when starts using the data stored in SDL database. This is caused by the processes of data retrieval from the databases. The following parameters can affect the system performance • Number of users accessing SDL databases. • Number of other databases supported by this particular database instance. • Number of queries being run and their occurrences.
Batch Management Batch Management This section describes the Batch Management functions. Flexible Batch Processing Flexible batch processing permits control logic and resources such as equipment to be used in a variety of ways to produce different products. Flexibility is built into the Batch Management approach to configuring recipes. The master recipe is created by drawing a flowchart of the process using an object oriented approach. This flowchart is called a procedure function chart (PFC).
Batch Management • Planning resource use. • Writing equipment phase control logic. • Configuring the controller modules required to handle input and output data, control loops, and execution of sequence logic. • Configuring the equipment database that describes the hardware and software resources available at the site. • Creating recipes that can include both subprocedures and formulas, using reusable logic components. The controller and Batch Management can be configured simultaneously.
Batch Management 2. Verify the phases match the equipment phases defined for the controller (EPT control modules only). 3. Configure equipment names. 4. Specify equipment attributes. Identify characteristics of the equipment that could have an effect on which equipment should be used for a particular batch. 5. Specify which phases can run on which equipment. 6. Define equipment groups.
Batch Management Miscellaneous Batch Configuration Additional batch configuration activities are performed using various methods. These activities include defining message priorities, specifying the number of backup versions of procedures to be retained, and the option to change the colors used in PFCs. The retention limit for display of completed batches is also specified using these methods. The Batch Management batch manager runs under System 800xA.
Information Management Information Management Historical Process Data Configuration to log historical process data in System 800xA is done using two aspect categories, the Log Template and the Log Configuration. The Log Template defines how to log and the Log Configuration is used to produce a log for every object you would like to log. Default Log Templates are provided in the Library Structure in the Plant Explorer.
History Configuration History configuration from the history log perspective is described in System 800xA Information Management, Configuration (3BUF001092*). The subsection Bulk Configuration on page 358 describes how you can do bulk configuration of Log Configuration aspects and of Property Logs of the Information Management History Services. Log Template A Log Template is a re-usable template for building many similar logs.
History Configuration Figure 196. Mark History Log Template Library 5. Select the History Log Template. Give the object a name and a description. Click Create. Figure 197.
History Configuration 6. Select the created object in the object area, and select Log Template in the aspect list. Figure 198. Select History Log Template Object 7. Select Property Log in the Property log Template area and either click Add and get the New Log Template dialog box or open the context menu and choose the log needs to be added, without getting the New Log Template dialog box. Figure 199.
History Configuration 8. In the pop-up dialog box New Log Template, select a source from the Data Source drop-down menu and click OK. In this example OPC is selected. See Figure 200. Figure 200. New Log Template Pop-Up Dialog Box The sources available depend on the OCS Integration package installed. The option to configure the Collector Link is only enabled if third party history servers are being used. 9. Type a log name in the Log Name text field under the Log Definition tab.
History Configuration Absolute value, Percent of span or Percent of value. You must also set the Exception Deviation value. The static min and max ranges must be set on the Presentation tab of the Log Configuration aspect, if Percent of span is selected. Do not configure Max Time and Min Time in the Storage area with the same value. This may result in decreased storage capacity for the actual log. 10. Click Apply. Figure 201. Log Template 11.
History Configuration Log Configuration Log Configuration aspects are placed on the object that should be logged. For more details see Log Configuration Details on page 339. A log for an object is configured in this way: 1. Select, for example, the Control Structure. 2. Go down in the structure in the Object Tree, to select the object that you want to log. Figure 202. Select Object 3. Right-click in an empty part of the aspect list and select New Aspect from the context menu. 4.
History Configuration Figure 203. Create Log Configuration 336 5. Give the aspect a name and a description and click Create. 6. Select the created aspect in the aspect list. 7. Make one of the following actions to create a Property Log: – Select the object in the Logged Properties area and click Add Property. – Select the object in the Logged Properties area and select Add Log from the context menu. – Double-click a property in the Property column.
History Configuration Figure 204. Create a Property Log 8. In the pop-up dialog box New Property Log, select the property which will be logged. In this example VALUE is selected. Figure 205.
History Configuration 9. Select a new data type in the Data Type drop-down menu if needed and Log Template from the Template drop-down menu. Click OK. In this example the Log Template created in Log Configuration on page 335 is used. Only suitable templates will appear. Figure 206. Select from Template List 10. The Logged Properties area will look like Figure 207. Figure 207.
History Configuration 11. Under the Presentation tab you can override Engineering Unit, Normal Maximum, Normal Minimum, No of Decimals or Display Mode from the object. 12. To implement the log click Apply. The log is created in the server and the sampling is started. Log Configuration Details In this section all selections for Log Configuration are handled more in detail. Pop-up dialog New Log Template Figure 208.
History Configuration Table 16 and Table 17 explain the selection possibilities in the New Log Template dialog. The available sources depends on the system extensions installed. Table 16. Source Options Source Description OPC An OPC accessible property. TTD A log in the Advant Controller 400 System. Only present if 800xA for Advant Master is installed. Table 17. Log Type Log Type Description Direct The inputs are retrieved directly from the specified property.
History Configuration The recommended way to write the log name is: Log__. If there are more logs with the same storage interval and storage size, add _ or _ at the end of the name. The value for Log Type, see Table 17, is only possible to select when creating the log template. The Log Source is depending on log type, see Table 18. The source value is not possible to change. The Service Group is only possible to change for linked logs, i.e.
History Configuration Data Collection Tab. The Data Collection tab is displayed in the figure below. Figure 210. Data Collection Tab 342 – Aggregation The Aggregate is only possible to change for logs with another log as source. Available aggregates are explained in Table 19. Bad Data Quality Limit specifies the maximum allowed percent of bad data in the resample interval for an aggregated point to be considered to be good.
History Configuration not changed. Max Time set to zero means that there is no sampling if the input changes are less than the Exception Deviation. In all other cases Max Time must be greater or equal to Min Time. Set Max Time greater than 2*Min Time for minimum storage capacity time to be guaranteed. Setting a Max Time also enables the trace knee functionality.
History Configuration There is no need to have a short Max Time value to get the "knee" at the right place, since the added point is placed Min Time before the point with the new value. For direct logs having hierarchical logs, the Max Time should be set to a strictly lower value then the shortest Min Time of the hierarchical logs. Storage size can either be specified as number of Points stored in the log or as the Time covered in the log.
History Configuration value added to the log must be greater or equal to 70.35 or less or equal to 63.65. The data in a log is reduced by several methods without losing the process critical information because of limited storage capacity in a log. Also refer to Figure 212. • If a sample is received more often than the minimal storage interval of the log (For example, 1s), the log stores the latest of all values of the interval.
History Configuration Table 19. Aggregates (Continued) Aggregate Description Count The number of raw values over the re-sample interval. Standard Deviation The standard deviation over the re-sample interval. Minimum Actual Time The minimum value in the re-sample interval and the time stamp of the minimum value (in seconds). Minimum The minimum value in the re-sample interval. Maximum Actual Time The maximum value in the re-sample interval and the time stamp of the maximum value (in seconds).
History Configuration Table 19. Aggregates (Continued) Aggregate Description Duration Bad The duration (in seconds) of time in the interval during which the data is bad. Percentage Good The percent of data (one (1) equals 100 percent) in the interval which has good quality. Percentage Bad The percent of data (where one (1) equals 100 percent) in the interval which has bad quality. Worst Quality The worst quality of data in the interval. Annotations The number of annotations in the interval.
History Configuration When a property is selected, the default Data Type is automatically displayed. The available Data Types are Boolean, Byte, Char (8-bit integer), Double (64 bit), Float (32 bit), Integer, Long Integer (32 bit), Short Integer (16 bit), Unsigned Integer, Unsigned Long (32 bit), Unsigned Short (16 bit) and Very Long Integer (64 bit). One reason to change the Data Type is when an aggregate sums up a large number of values.
History Configuration Log Configuration Aspect View Object Tab. The Object tab is displayed in the figure below: Enabled check box Figure 214. Object Tab Add Property is used to implement a new Property Log. A double-click on a property in the Property column will have the same effect. Delete is used to delete a Property Log. To delete a Property Log, select the property log and click Delete. The Service Status row shows status information for the configured Service Group.
History Configuration Status for Configured Service Group: OK: All providers in the service group are up and running. OK/ERROR: At least one service provider is up and running. ERROR: All providers in the service group are down. Note that you can not delete a single log in the log structure, since the log is defined in the template. For example Log_5m_1month in Figure 214 is not possible to delete. All properties are listed for the selected object.
History Configuration The Property Log tab displays log information. The Data Size is the size of the Property Log on disk. It is the sum of the size of all logs. The size of each log file is the sum of the file header and the data storage size. Log Definition Tab. A read-only tab which hold the same information as Log Template, see Figure 209. Data Collection Tab. A read-only tab which hold the same information as Log Template, see Figure 210. Presentation Tab.
History Configuration When choosing Momentary (raw data) as Treatment the trace can only show a maximum of 86400 points even though more data exists. The above listed are in override order. For example you can override a value set in the Object Type by writing a value in the Object Instance. Another example is a value set in the Object Type, the Object Instance for presentation attribute or the Log can be overridden in the Trend Display.
History Configuration The precedence of Presentation Attributes in a trend display are derived from the configuration in the following order: 1) Log Configuration aspect (changing the default presentation attributes will override the presentation values). 2) Control Connection aspect / Property Extension Info (for general properties) aspect.
History Configuration By clicking Read the log values are displayed. By clicking Settings you can change the time frame and the number of data points to be retrieved. Figure 219. Data Retrieval Settings In the Page Size area you can set the number of points the page will display. Default is set to 1000 and max is 10 000. In the Time Frame area you can set the time for the retrieval of data from the log. If you check the Latest radio button the 1000 (if set) most recent data are displayed.
History Configuration By clicking Display you can change the appearance of the logged data. Figure 220. Data Display Options If you clear the check box in the Quality area, the value will be displayed as hexadecimals. If you clear the first check box in the Time & Date area, the value timestamps are displayed in UTC time. If you select the second check box in the Time & Date area, the value timestamps will be displayed in milliseconds.
History Configuration In the overview you can see if the Log Configuration is enabled, the path to it and if it is passed the consistency check. By right-clicking over the list of Log Configurations, a menu will be displayed where you can choose to enable, disable or delete the Log Configurations. You can also choose to run auto-correct if they have not passed the consistency check.See Figure 221. Figure 221.
History Configuration Archive Tool The Archive Tool is used to insert backup data into History logs during runtime. See Figure 222. Figure 222. Archive Tool File / Select/Open Archive is used to browse to the directory containing the history log files. Action / Insert Data into logs is used to insert the data into the log. The data will be merged into the existing logs. When inserting data into logs the start and end time for the data to insert can be chosen in the Time selection dialog.
History Configuration The tool can also be used to validate and correct History log references from backups and save a list of the log items. Use Action / Validate Item to display status of the individual History data logs. If not all History data logs show good status Action / Repair Item References can be used to repair the files with bad item references.
History Configuration You can also create a list of properties for which logs have already been created, in the event that you want to modify or delete the log configurations for those properties. Work Flow Configure all other history objects, including log templates, before using this tool. The recommended work flow is as follows: 1. Configure log sets, message logs, report logs as required by your application. If you require archival, create an Archive Device and Archive Groups. 2.
History Configuration The file system must be in a consistent state at all times. Defragment disks on a regular basis using the defragmentation software provided with the operating system. • Size disks so they will be 25 percent empty for defragmentation purposes. • Check the system for fragmented files on all nodes where trend and history logs reside, and defragment the applicable disks as required.
Extended Configuration Data Extended Configuration Data Parameter Management Parameter Manager aspects can be used to gather extended configuration data and expose them to other aspects in the system in a very flexible manner. To provide extended configuration data in Parameter Management aspects you have to perform the following principal steps: 1. Define a corresponding Parameter Manager aspect category in Aspect System Structure with the needed properties.
Extended Configuration Data To create an own Parameter Manager aspect category with simple table-like properties you perform the steps: 1. In the Aspect System Structure select the Parameter Manager aspect type object. 2. Execute the New Object context menu item and create an object with a name at your choice. 3. In the aspect pane of this Aspect Category object add the properties via the context menu on the Categories item. 4.
Extended Configuration Data These object types serve as models by which to instantiate actual process objects under a Softpoint Generic Control Network object in Control Structure. The softpoint object types specify the signal properties for the softpoint objects. This includes signal ranges for real and integer signals, alarm limits, event triggers, and whether or not the signals will be controllable. The process objects inherit the properties of the object types from which they are instantiated.
Document Management • Defining alarm text groups. • Deploying the finished softpoint configuration. Whenever you create new softpoint objects, or make changes to existing softpoint objects, the new configuration will not go into effect until the changes are deployed. While softpoint configurations are being deployed, softpoint processing is suspended, current values and new inputs are held. This process is generally completed within five minutes, even for large configurations.
Document Management For example you can include a dynamic document into an object type of the ProcessObjExtLib delivered with of AC 800M connectivity to make it possible to get a snapshot status of the object for maintenance or operation documentation purposes. Assumption is that the Library is closed or released. The principal steps to include a dynamic document for into a Process Object object type are as follows: 1. Select the object type in the Object Type Structure. 2.
Document Management 1. Select the Library Structure / Document Manager Templates / Document File Templates / Documents 2. Select one of the existing document template aspects, copy and rename it or create a completely new one. 3. Edit the document as needed and check it in: The new template is ready. 4. When you now create a Document aspect in an object in the Object Type Structure or in another structure and you set the file for the Document aspect the new template is additionally offered for use.
Document Management 5. Now the Document aspect of your documentation object holds the file you selected either as a copied file or as a moved file or as a referenced file. If you have many of those files to include into documentation objects as copies you can import them using a Bulk Data Management worksheet. The steps are: 1. On for example the folder object open context menu item Advanced > Bulk Data Manager 2.
Information Access Aspects If you want also to access the operation / maintenance documents via Documentation Structure you can place the corresponding objects from Functional Structure, Control Structure or Location Structure additionally in the Documentation Structure, e.g. by configuring and using a corresponding Bulk Data Management worksheet. For more details on Document Management refer to System 800xA Engineering, Engineering Studio (3BDS011223*).
Information Access Aspects To add a File Viewer aspect to an aspect object, do as follows: 1. Select an object in Plant Explorer. 2. Select New Aspect from the object’s context menu and add a File Viewer aspect, see Figure 224. Figure 224. File Viewer Aspect The first time you open a File Viewer aspect it will be empty. The main view displays a default page. The File Viewer aspect has two views, the main view and the configuration view.
Information Access Aspects 3. In the Web Browser Options section, select the Display PDF in browser check box. 4. Click Ok. Using .pdf makes it possible to go to a specific page automatically when used together with a bookmark aspect. See Figure 225. Figure 225. The Main View The configuration view includes two areas, one for a Public document and one for a Work document, see Figure 226 below.
Information Access Aspects Pdf document to display in the Main View The source file used to generate the pdf-file Figure 226. The Configuration View Some status information is displayed in the Work Document area. An example is shown in Figure 227.
Information Access Aspects Figure 227. Status Information 372 • Locked by - displays the name of the user who performed an Edit or a Check Out. This information is only displayed if the document has been checked out by someone other then the current user. • Directory - displays the name of the directory in which the file is saved. This information is shown only if the current node is the node that the document was checked out from. • Filename - displays the file name of the document.
Information Access Aspects Only Adobe Acrobat PDF documents have been tested and verified to work with in the File Viewer aspect main view. However, the File Viewer is based on Microsoft Internet Explorer technology and supports all document formats that can be displayed inside Internet Explorer. Make sure to make the changes in the specific applications to view the documents in Internet Explorer.
Information Access Aspects 3. Select file and click Open in the dialog. You can access both Public and Work files from any node on the network. Automatic Detection of pdf-documents When you use the Attach and Check In operations on Work Documents, the file viewer aspect searches the same directory for pdf-files. If a pdf-file with the same name as the Work documents is detected, the file viewer will automatically propose to attach the pdf-file as the Public document.
Information Access Aspects Save If you edit a Work file, you have to save it before it is updated in the system. To save a Work file: 1. Select aspect and the configuration view. 2. Click Save in the Work Document area. The Edit operation is also available as aspect verbs Manual File Selection If you check the Manual File Selection box, you are able to select file name and directory during Edit.
Information Access Aspects Clear Clear enables you to remove an associated document from an aspect. Clear can be used on both Public and Work documents. This operation is not to be confused with the Delete aspect operation, that is available through the aspect context menu. To Clear a file: 1. Select aspect and bring up the configuration view. 2. Click the Clear button (in appropriate section). Template Support The File Viewer aspect supports template functionality.
Information Access Aspects Follow the steps below to use any of the predefined templates: 1. Add a File Viewer aspect to a selected object. Figure 229. Existing Templates To create your own template, follow the steps below: 1. Go to the Aspect System Structure and select the File Viewer Aspect Type object. 2. Select New Object in the context menu and create a new Aspect Category. This object (Category) will represent the template. 3. Give it a suitable name and click OK. 4.
Information Access Aspects Figure 230. Technical Reference Manual, Aspect Category Object 378 5. Add a Technical Reference Manual aspect to the object. 6. Select Details in the aspect’s context menu and then the Aspect Details tab. 7. Add a Template Aspect key and click OK, see Figure 231.
Information Access Aspects Figure 231.
Information Access Aspects 8. Select the configuration view and attach an empty template, in this case Technical Reference Manual, as Work Document, see the figure below: Figure 232. Attached Template Now you are able to create a Technical Reference Manual aspect on your objects. This aspect contains an empty Technical Reference Manual which can be modified to suit your needs. If you create your own category, user role and permission need to be set manually.
Information Access Aspects 1. Create a new aspect of a suitable Bookmark Category, for example Technical Reference Manual, see the figure below: Figure 233. New Aspect Dialog The proposed name for a Bookmark aspect is the same as the proposed name for a standalone File Viewer aspect. For example the Technical Reference Manual Bookmark aspect gets the name Technical Reference Manual. This matches the File Viewer aspect of the same name.
Information Access Aspects 4. Enter the page number in the Document Page field. Figure 234. Technical Reference Manual - Chapter 5. Select the main view to see the selected page of the pdf-document. To use the generic Bookmark aspect: 382 1. Create a new aspect of the general Bookmark Category. 2. Give it a proper name that identifies the page in the document, you want to enter, see Figure 235 and Figure 236.
Information Access Aspects Figure 235. General Bookmark - Important Page 3. Bring up the Config View and enter the number of the wanted page, Figure 236. An Important Page in a Technical Reference Manual 4. 3BDS011222-510 B Select the main view to see the selected page of the pdf-document.
Information Access Aspects How to use the Web Page Aspect To create a Web Page aspect, do as follows: 1. Add a Web Page aspect to the object concerned. 2. Open the Config View of the Web Page aspect. See Figure 237. Address field Figure 237. The Web Page Aspect in the Config View 3. Enter the web address in the Address field. 4. Click Show or press Enter to open the web page. 5. Click Apply.
Information Access Aspects 6. In the upper part of the window the Tool bars check boxes are shown. Select these if you want the Application Bar and the Navigation Bar be shown in the Main View. If you select Explore in the Web Page aspect context menu, your default web browser opens with the web page connected to the Web Page aspect. How to use the ActiveX Wrapper Aspect The ActiveX Wrapper aspect provides a container to allow ActiveX Control to be used with the workplace environment.
Information Access Aspects Figure 238. Browse for Components Dialog 386 4. Click on the OK button in the dialog (browser) window. 5. Click the Refresh button in the ActiveX Wrapper dialog, see Figure 239, to verify that you have selected the proper ActiveX Wrapper.
Information Access Aspects Figure 239. The ActiveX Wrapper Aspect Dialog Box 6. A preview of the chart in the dialog box that pops up, see Figure 240. Figure 240. ActiveX Wrapper Aspect Dialog Box Showing a Preview of the Chart 7. 3BDS011222-510 B Click Apply to save your configuration.
Information Access Aspects 8. Properties dialog can be opened if available for an ActiveX, by clicking the Properties button, see Figure 241. Figure 241. The Properties Dialog Box (showing MSChar20Lib.MSChart.2) You can now set the parameters for the Chart according to your preferences. 9. Click Apply, then OK to activate your parameter changes. You can use your own ActiveX in the Active Wrapper. The ActiveX can include controls like buttons and text controls.
Information Access Aspects How to use the Windows Application Aspect In a multi client system, make sure to link to the executable application as well as to the argument files in such a way that they can be found from all of the current Workplaces. Web page and File Viewer aspects can often be used instead of the windows application aspect if the argument is a file. Usually that is the preferred method since this will open a workplace overlap instead of just an application window.
Help Aspect 3. Enter the path to the program to be used, or browse to the destination. Figure 243. The Windows Open Dialog 4. If the application takes arguments, enter these in the Program Arguments field (see Figure 242). 5. Click Apply to save the configuration. The default action for a non configured Windows Application aspect is to show the Config View. For a configured Windows Application aspect the default action is Open. Help Aspect How to use the Help Aspect 1.
Help Aspect 2. Select the aspect and the configuration view, see the figure below: Figure 244. The Instance Help Aspect 3. Use the Browse button in the File area to find the help file to be referenced. If no file is chosen, the default help file will be used. 4. Enter the index for the section in the help file you want to reference, in the Map area. The index can be an integer, string or a binary number, depending on the type of help-tags that are included in the document. 5.
Help Aspect Figure 245. Aspect Context Menu - Help Aspect Figure 246. Object Context Menu - Help Aspect 7. 392 Now view the help for the selected section.
Asset Optimization Asset Optimization Asset Monitoring Workflow for configuring Basic Asset Monitors: 1. Configure the Asset Monitoring Server. Each AO Server object should be added under the Asset Optimization object in the Control Structure. 2. Add desired Asset Monitors to the object that represents the asset to be monitored. 3. Configure the Asset Monitors. 4. Load the Asset Monitors to an AO Server. a.
Maximo Integration d. Make sure that the Asset Monitor aspects to be loaded are assigned to the target Asset Optimization Server and that they are enabled. e. To load the enabled Asset Monitor aspects to the Asset Optimization Server, click Load all AMs. f. To load only selected Asset Monitor aspects, select the AMs Assigned to this AO Srv option, select the desired Asset Monitors, and right-click and select Load/Unload Config from the context menu that appears.
SAP/PM Integration Alarm and Event List upon successful submittal, or to not perform these actions. 3. Set up Maximo Credentials that contain the Maximo user credentials used to access the Maximo Server by the specific System 800xA user. 4. Add desired Asset Monitors to the object that represents the asset to be monitored. 5. Configure the CMMS views, which consists of adding the desired views to the desired objects. For more details see System 800xA, Asset Optimization, Configuration (3BUA000118*).
PC, Network and Software Monitoring PC, Network and Software Monitoring Workflow for creating and configuring IT Asset objects using PNSM Asset types. This workflow is generic for any IT Asset type. 1. Create a new object of the appropriate IT Asset type in Control Structure, under the IT OPC Server Network. 2. Edit the IT General Property aspect on the new object to set the appropriate general asset configuration parameters. 3.
Configuration Change and Access Management Configuration Change and Access Management Authorization For configuration of Security and Authorization for an 800xA system refer to System 800xA, Administration and Security (3BSE037410*). Access Control Re-Authentication and Double-Authentication requires activation of Advanced Access Control, by setting its value as True in System Settings aspect. System Settings aspect is placed in Admin Structure under Administrative Objects\Domains\ system.
Electronic Signature 3. Set the password for the inactivity user in the Password field. 4. Set the time-out for automatic revert to inactivity user in the Revert to Inactivity User drop-down menu. 5. Click Apply. For further details refer to System 800xA, Administration and Security (3BSE037410*). Electronic Signature Before activate the first and second signatures, set the Signature Required property of System Settings aspect as True.
Engineering Repository The backup files of a System Configuration Version can be restored to the same or to another node using Configuration Wizard to fall back to a saved consistent version of system configuration. It can also be used to set up initially an new Engineering System with the current configuration of a Production System. For more details on System Configuration Version and Backup / Restore refer to System 800xA, Maintenance (3BSE046784*).
Engineering Repository The Engineering Repository functionality is initially limited to: • 800xA Operations. • Control and I/O (except generic OPC). • Fieldbuses. • Batch Management. • Information Management. Permissions To work with Engineering Repository following three new permissions listed in Table 20 need to be granted to the users. Table 20. Permissions to Work with Engineering Repository.
Engineering Repository Figure 248. Permissions for Engineering Repository When creating a system or upgrading from an earlier version, the new permissions for Engineering Repository are added to the Security Definition aspect of Environments object. Different users can be configured to have different permissions in different Environments. Generally when performing actions with engineering repository a single level of confirmation is used.
Engineering Repository • Entity Difference View (compare). Contents View • The Contents View is used to view what are in the Engineering Repository. It is possible to view the repository on an entity level. The entities are located in a tree structure on an entity level as shown in Figure 249. Figure 249.
Engineering Repository Figure 250. Engineering Repository Browser - System Difference View Description of the icons present in Engineering Repository browser is explained in Table 21. Table 21. Icons in Engineering Repository Browser Icon Name Description Equal Entity/Object/Aspect is equal in repository and system. Placeholder Not a real object in the system. Only in System Entity/Object/Aspect exists only in system.
Engineering Repository Table 21. Icons in Engineering Repository Browser Icon Name Description Modified in Repository Entity/Object/Aspect exists both in system and repository but is modified in Repository. Reserved by Another (Breakable) Entity/Object/Aspect is reserved by another user in the system. The reservation is breakable by current user. Reserved by Another (Not Breakable) Entity/Object/Aspect is reserved by another user in the system. The reservation is not breakable by current user.
Engineering Repository Figure 251. Engineering Repository Browser - Entity Difference View Menus Every action or command offered by the application is present in the menus. File Menu • • • • Open Error Log - Opens the error log. Save Messages - Saves the clients error log. Print Messages - Prints the clients error log. Exit - Exits the Engineering Repository Browser. Edit Menu • Add Item - Add Item to Repository dialog will display all entities from the selected system and all defined Custom Entities.
Engineering Repository • Filter Settings - This opens the filter dialog for Aspect Categories and Object Types View Menu • Contents - Select this to view the contents of the repository. • Differences - Select this, the Difference View, to view the differences between the repository and the selected system. • Messages - Select this to view error and warnings generated in the application. When new entries are added to the log the log view is automatically displayed as shown in Figure 252. Figure 252.
Engineering Repository • Refresh - Reload the information from the repository and the system. Tools Menu • Select Repository- If an Engineering Repository web service is not installed on the same node as where the application is running the repository must be pointed out. • Select System - Use Select System when changing from for example the engineering environment to the production environment. When Engineering Repository Browser is first started it connects to a system on the local node.
Engineering Repository The toolbar contains a subset of the commands found in the menus. Plant Explorer Context Menu From the context menu in the Plant Explorer (Figure 253), it is possible to add items (projects, applications, controllers and libraries) to the Engineering Repository. The Engineering Repository context menu entry appears when the selected object belongs to an Entity or a Custom Entity. Figure 253.
Engineering Repository • Compare item with Engineering Repository - Opens up the difference UI and makes it possible to see what differs. Configuration Custom Entities Entities like projects, applications, controllers, libraries, and Control Networks can be exported to the Engineering Repository without any special configuration. Objects which are not part of an entity to the Engineering Repository need to be defined in Engineering Repository as Custom Entities.
Engineering Repository Table 22 compares System Synchronization tool (existing function in previous systems which is replaced with Engineering Repository) functionality with the new similar Engineering Repository functionality. Table 22.
Engineering Repository Select the configurable filter for Aspect Categories from the Repository Browser menu. Add the required category to the filter and set one of the following properties: – Always Filter Out. Do not import aspects of a specified category. – Never Overwrite. Never overwrite aspects of a specific category. – Overwrite Older Aspects. Overwrite aspects of a specific category if current modification date is older than the date in the destination.
Import / Export tool – Overwrite Older Aspects. Overwrite aspects of a specific object if current modification date of the aspect is older than the date in the destination. • The filter applies to the whole repository so that all imports from the repository to the system are filtered. The filter also applies to compare when producing the difference report. Aspects that are filtered out will not indicate differences in the difference view.
Synchronizing Changes Between Environments 8. Import the afw-file (Import All) or only a required selected part within the afw-file (Import), taking decisions on replacements if needed. 9. Execute Step 4 to Step 8 for all afw-files. 10. Verify the imported contents, use for example the Consistency Check tool on the imported items. 11. Do further actions make the imported contents work, such as Generate Configuration Data on Function Diagrams, Download the Control Application, and so on.
Audit Trail 3. Pre-test them in Engineering environment. Note that no download to a controller is possible in the Engineering environment. Only Test Mode (simulated controller) in Control Builder M Professional can be used. Note that there can be aspect categories that cannot be configured in the Engineering environment: Production-only aspects. 4. Use the Environment Difference tool to verify the differences between Production environment and Engineering environment. 5.
Audit Trail There is only one Audit Trail Configuration aspect in a system. It is placed in the Admin Structure under Administrative Objects\Domains\ system. The Security Configure permission is required to alter audit trail settings. The available settings are shown in Figure 254 below. Figure 254. Audit Trail Configuration The Audit Trail active checkbox activates or deactivates the whole audit trail function.
Archive Archive Archiving of data collected in audit trail logs is supported by Information Management History Services. For configuration instructions see System 800xA, Information Management, Configuration (3BUF001092*). System and Device Checks For configuration and use of system and device checks see the applicable configuration and operation manuals of the corresponding functional areas of System 800xA.
Accessing 800xA via OPC 800xA OPC Support exposes interfaces for OPC Data Access, OPC Alarm and Event and OPC History Data Access. These are three central interface specifications as stated by the OPC Foundation. Refer to the System 800xA, System Planning (3BSE041389*) manual for a definition and explanation of OPC. In order to use OPC Support both hardware and software must be configured in certain ways. The following sections explain this in more detail.
Accessing 800xA via OPC OPC Data Access Version 2.05A IOPCBrowseServerAddressSpace The IOPCBrowseServerAddressSpace interface as implemented by the 800xA System OPC Server is not fully compliant with the OPC Data Access Standard Version 2.05A. This interface can still be used considering the constraints described below: • Flat namespace is not supported. Retrieving an itemID enumerator from the BrowseOPCItemIDs method with OPC_FLAT as browse filter type will result in an empty enumerator.
Accessing 800xA via OPC Accessing the 800xA OPC AE Server OPC AE Support in the 800xA system enables you to subscribe to alarm and events from a third party OPC AE client. The status of the server is checked by calling the method GetStatus on IOPCEventServer. The client should wait for the return code OPCAE_STATUS_RUNNING before calling the other methods. OPC AE Program Identities The Program Identity for the System 800xA OPC AE Server to be used by third party OPC AE clients is ABB.
Integrating OPC Servers into 800xA Accessing the 800xA OPC HDA Server OPC HDA Server Support in the 800xA system enables you to read, write or subscribe to history logs from a third party OPC HDA client. The status of the server is checked by calling the method GetHistorianStatus on IOPCHDA_Server. The client should wait for the return code OPCHDA_UP before calling the other methods.
Integrating OPC Servers into 800xA Hardware Setup 800xA does not impose any restrictions on which machine the third party OPC server software is to be installed. It can be installed directly on the 800xA connectivity servers or on a separate dedicated server. Installation on a separate machine gives better system performance and it gives the 800xA connectivity servers a better fault isolation from poorly implemented OPC servers.
Integrating OPC Servers into 800xA Running the OPC Server in a Connectivity Server is the standard and recommended configuration. It is also possible to integrate an OPC Server into the aspect directory by importing a Control Structure using the Import/Export tool. Note that you have to add a Service Group from the Data Source Definition aspect, found in the Generic OPC Server Network object, see Configuring DA Connectivity on page 427.
Integrating OPC Servers into 800xA Figure 255. Connection of an OPC Server in Control Structure 3. Perform an Upload. See Upload on page 439. 4. Check the Data Access functionality by looking in the Property View in the Control Connection Aspect. See Configuring DA Connectivity on page 430. How to Connect to an OPC DA Server in a Non-System Node In most cases DCOM security settings need to be configured. For more information see DCOM Security Settings for OPC on page 457. 1.
Integrating OPC Servers into 800xA Figure 256. Connection of OPC Server in non-system node. 3. Go to the Service Structure and make manual configuration of the OPC Server and the remote node for every Service Provider. Enable each Service Provider. See Configuring DA Connectivity on page 427. 4. Perform an Upload. See Upload on page 439. 5. Check the Data Access functionality by looking in the Property View in the Control Connection Aspect. See Configuring DA Connectivity on page 430.
Integrating OPC Servers into 800xA Figure 257. Connection of Generic OPC Server Network Object 3. Manually create a Service Group and a Service Provider. See Configuring DA Connectivity on page 427. 4. Manually configure the Data Source Definition Aspect. See Configuring DA Connectivity on page 425. Data Source Definition Aspect. The Data Source Definition aspect binds a system OPC property to a data provider and is normally situated in Control Structure on the Network Object.
Integrating OPC Servers into 800xA All service providers in a service group must provide the same data. The OPC servers, which the service providers are connected to, must collect data from exactly the same set of equipment. The Data Source Definition aspect has two tabs which are described below. The Connectivity Tab Figure 258. The Connectivity Tab 426 • The Service Group drop down menu. Shows a list with available Service Groups defined in the Service Structure under the OPC DA_Connector Service.
Integrating OPC Servers into 800xA The Data Key is normally not changed The OPC Configuration Tab Figure 259. The OPC Configuration Tab • This field shows the identity of the OPC server that the service providers are using. It is also used when a new service group or provider is created from the OPC Data Source Definition aspect. The value can only be changed if the Service Group field in the Connectivity tab is empty.
Integrating OPC Servers into 800xA Service Group Figure 260. Server Group Definition - Special Configuration • Adapter Identity field: The ProgID for the Adapter to be used by the Service Providers in this group. Normally, no need to change. • Allow Parallel Redundancy check box: When this alternative is checked, parallel redundancy is allowed for this Service Group. Parallel redundancy is only used when an OPC DA client requests it explicitly.
Integrating OPC Servers into 800xA For information about locking, refer to System 800xA, Engineering, Process Graphics (3BSE049230*). Service Provider Figure 261. Server Provider Definition - Special Configuration • OPC server identity field: The ProgID for the OPC server. Click Refresh to update the list with available OPC servers. All service providers in the same service group should have the same OPC Server identity.
Integrating OPC Servers into 800xA Properties of the Control Connection Aspect. The Properties of the Generic OPC Object are shown in the Control Connection Aspect. The dialog box has five tabs (some tabs are only visible in Object Type Structure): • Property View • Property Info • Additional Info • OPC • Item Properties Property View Tab The Property View Tab contains information about the properties in the Control Connection Aspect. See Figure 262. Figure 262.
Integrating OPC Servers into 800xA Name Property name in the system. Data Type The data type of the property. Access The setting of the property, (readable and/or writable) Update Rate The default update rate for the property in milliseconds. Value The collected value of the property. Quality The quality of the property value. Timestamp The time when the property got its value. Flags See information about the Property Info Tab. Read Permission Security setting for reading.
Integrating OPC Servers into 800xA Property Info Tab Select the Property Info tab and mark one of the properties in the Properties area. The Property Info area contains information about the selected property. See Figure 263. Figure 263. Property Info 432 Data Type The data type of the property. Name Property name in the system. Update Rate The default update rate for the property in milliseconds. ID Internal ID number of property. Description Description field (for example a different name).
Integrating OPC Servers into 800xA Read Permission Security setting for reading. A star indicates that the default permission is used. Write Permission Security setting for writing. A star indicates that the default permission is used. Additional Info The selected property has additional Info. For example used by Trend and Historian. Can be used for other purpose. Real Time For application specific use. Runtime For application specific use. Primary For application specific use.
Integrating OPC Servers into 800xA Figure 264. Additional Info 434 Normal Maximum Name of the property that specifies max range or a max range value. Example of a property: max_value. Example of a value: 100.00. Normal Minimum Name of the property that specifies min range or min range value. Example of a property: min_value. Example of a value: 0.00. Engineering Unit Name of the property that specifies Engineering Unit or a value. Example of a property: unit. Example of a value. No.
Integrating OPC Servers into 800xA Data is displayed as vertically connected horizontal lines between points. See Figure 265. Presentation Mode Interpolated Data is displayed as sloped lines between points. See Figure 265. Value Value Normal Max Value Presentation Mode Stepped Normal Min Time The data collected through the data subscription. Time Data presentation with the Presentation Mode Stepped selected. Time Data presentation with the Presentation Mode Interpolated selected. Figure 265.
Integrating OPC Servers into 800xA OPC Settings Select the OPC tab to see the OPC settings. See Figure 266. Figure 266. OPC Settings Property Selector for the property name in the control connection aspect. Use the arrow to the right to show the properties. Item ID Property identity in the accessed OPC server. Edit according to the rules given for the connected OPC server. Access Path Optional. You may edit the path according to the rules given for the connected OPC server.
Integrating OPC Servers into 800xA Item Properties The Item Properties tab is used for configuration of Item Properties for an object according to the OPC DA 2.0 specification. An Item Property consists of an ID, description, data type and a value. The source of the value is a property on the object that holds the Control Connection Aspect. All Item Properties for an object are displayed in the list view. See Figure 267. Figure 267.
Integrating OPC Servers into 800xA If no Property is marked as default the first Property in the list will automatically be set as default. Only one Property can be marked as default. • • How to add a new Item Property: – Fill in the Property, Description and Object Property fields – Click the Add button. – The Item Property will be added for all properties in the Control Connection aspect.
Integrating OPC Servers into 800xA Verifying DA Connectivity You can test data access to OPC items from the property view tab. Mark the Subscribe for live data check box to test the connection between this node and the OPC Server. Figure 269. The Subscribe for Live Data Option in the Property View Upload By uploading, you collect all the objects in the OPC Server and append them as aspect objects in Control Structure.
Integrating OPC Servers into 800xA The Upload in Control Structure, reflects the structure of the branches in the OPC Server. All branches in the OPC Server are represented by aspect objects. The OPC branch leaves are declared in a Control Connection aspect as aspect object properties. OPC leaves are the items you can access in an OPC Server. To perform an Upload the user needs to have Security permission Configure.
Integrating OPC Servers into 800xA Figure 271. Result of Generic OPC Upload Advanced Upload. An Advanced Upload is like a Standard Upload but the operation is split into two steps: • Retrieve objects (The command Retrieve creates an .ocs file). • Append objects (This will use the .ocs file created in the first step. This can be changed by typing in or browsing to another file.). The reason for an Advanced upload is that you retrieve in one system and later append in another system.
Integrating OPC Servers into 800xA Browse button Figure 272. Uploader - Advanced Tab Description of Uploader Append Name Resolving The Append function in the Uploader has a name resolving feature. The function tries to find an object with the same name in other structures than Control Structure. If an object is found, that object will be inserted into Control Structure according to the following rules: 1. An object is found in Functional Structure but not in Control Structure. See Table 23, example 1.
Integrating OPC Servers into 800xA 5. No object is found. An object will be created in Control Structure. See Table 23, example 5. Table 23. Uploader Append Name Resolving Before Upload Object Control Structure Ex 1 Ex 2 X AI_117 AI_117 AI_117 Ex 4 Ex 5 Control Structure X Other Structure X Obsolete Structure X X AI_117 Ex 3 Other Structure After Upload X X X X X X X X AI_117 X X AI_117 X X AI_117 X X X An obsolete object can be re-created from the Obsolete Structure.
Integrating OPC Servers into 800xA Changes of the Settings for Uploaded Items Normally only the Permission, Flags and Additional Info settings is changed. This can be done under the Property Info Tab. See Figure 263. Property Signal Generator Aspect You can use the Property Signal Generator aspect to generate a simulated value that can be used to test a display, a display element, or any other client application that subscribes for OPC items (object properties).
Integrating OPC Servers into 800xA View the Control Connection aspect on the Pump object and select the Property Info tab. Add a new property, Flow, with the type VT_R4. Click Apply. 6. Create a Property Signal Generator aspect on the Pump object and view the aspect. Select the Flow property and select Sine Wave with default values. 7. To test the value, view the Control Connection Aspect and select the Property View tab.
Integrating OPC Servers into 800xA Creating an Event Collector Service Provider. Create an event collector service group and an event collector service provider. Follow the steps below: 1. Create an event collector service group: a. 2. 3. 4. Create an event collector service provider: a. Create a service provider below the created service group. b. Open the Service Provider Definition aspect and select the node where the OPC AE server is running.
Integrating OPC Servers into 800xA Figure 273. Special Configuration Tab Connecting to a Remote OPC AE Server. For OPC AE there is no built-in 800xA mechanism to connect to a server on a non-system node. This means the server needs to be registered locally on the machines that run the event collector service that is used to connect to the OPC AE server.
Integrating OPC Servers into 800xA information on which node the server is installed. The server can then be accessed through remote activation. Registration of the 3rd party OPC AE server on the connectivity server can be achieved in the following ways: 1. The install program of the OPC server supports client registration/installation. 2. A registry file is supplied from the 3rd party vendor.
Integrating OPC Servers into 800xA Figure 274. Component Services 3. Open the context menu and select Properties. 4. Select the Location tab and deselect the Run application on this computer check box. Select the Run application on the following computer check box and browse to the machine where the OPC AE server should be instantiated. See Figure 275.
Integrating OPC Servers into 800xA Figure 275. Properties Creating a Collection Definition. The Alarm Collection Definition should be set up according to the functionality of the connected OPC server. Review the different options and consult the manuals for the connected OPC server to determine the appropriate settings. 1. 450 Specify the appropriate settings for the OPC server, refer to Figure 276.
Integrating OPC Servers into 800xA Figure 276. Alarm Collection Definition – If the OPC AE server supports refresh, the Supports Refresh check box should be selected. If the selected Alarm Manager relies on refresh from OPC server whenever a connection to the server has been re-established (and alarms not part of the refresh will be thrown away). – If the OPC AE server supports disabling the Supports Disabling check box should be selected.
Integrating OPC Servers into 800xA For OPC AE servers that only maintains acknowledge state within the server, with synchronization between two redundant servers, the Require Dual Acknowledge feature can be used so that acknowledge requests also gets sent to the stand-by provider. – If a connection between an alarm source and an alarm list is lost, an orange frame around the alarm list is displayed by default. To change the default configuration, do the following: a.
Integrating OPC Servers into 800xA Figure 277. Alarm Priority Mapping Selecting Category Mappings. By default the uploaded categories belongs the “Un-categorized” category group, but the uploaded categories can be configured to belong to either existing or new category groups. By mapping categories to existing category groups, events will appear in the corresponding alarm and event lists.
Integrating OPC Servers into 800xA Alarm Expression category is mapped to Process Alarm Category. Soft Alarm event categories like Soft Alarm (simple) and Soft Alarm (condition) exists for backwards compatibility are grouped in "Un-categorized" group. Process Alarms for Soft Alarms category should be used to configure new Alarm Expressions. System Alarm for Soft Alarms category should be used to create an Alarm Expression for generating system condition alarm. For each uploaded category: 1.
Integrating OPC Servers into 800xA Source Object Interceptor (optional step). By default the Event Collector will try to find an object with a name equal to the source name of the event. The Source Object Interceptor configurations can be used to limit the scope/set of objects that is searched and to create new objects if no matching source name is found. If the Source Object Interceptor configuration is not used, events from unknown sources will be discarded.
Integrating OPC Servers into 800xA If an alarm is generated for any object that is yet to be uploaded, a temporary object is created under the Lost and Found object. When the corresponding source object is uploaded, the system will have two different objects with the same name. The alarm will still be associated with the temporary object until this object is deleted and a new alarm is generated.
Integrating OPC Servers into 800xA provider. There you can see connectivity status and if there is a warning or an error there is a problem description in the ‘Description’ column. 2. In the Control Structure browse to the network object of the connected OPC AE server. Insert an ‘Alarm and Event List’ aspect. This list will show all alarms and events generated by the connected OPC AE Server. Integrating OPC HDA Servers Integration of OPC HDA servers is not a supported function of 800xA.
Integrating OPC Servers into 800xA Figure 280. COM Security Tab 2. Edit the Limits for Access and Launch a. Access Permissions – Edit Limits... You need to check the Remote Access box for the user labeled ANONYMOUS LOGIN in this dialog. This setting is necessary for OPCEnum.exe to function and for some OPC Servers and Clients that set their DCOM 'Authentication Level' to 'None' in order to allow anonymous connections.
Integrating OPC Servers into 800xA Figure 281. Access Permissions – Edit Limits b. Launch and Activation Permissions – Edit Limits... You need to check the remote boxes for the user labeled Everyone in this dialog. Since Everyone includes all authenticated users, it is often desirable to add these permissions to a smaller subset of users. One suggested way to accomplish this is to create a group named “OPC Users” and add all user accounts to this group that will execute any OPC Server or Client.
Integrating OPC Servers into 800xA Figure 282. Launch and Activation Permissions – Edit Limits 3. Edit Default Permissions for Access and Launch For each user (or group) that participates in OPC communication (e.g. “OPC Users”), make sure that both the Local Allow and Remote Allow check boxes are both checked. Figure 283.
Integrating OPC Servers into 800xA Launch and Activation permissions per user: Figure 284. Launch and Activation Permissions per User You can find the original description for using OPC via DCOM with Windows 7 under http://www.opcfoundation.org. Accessing the 800xA OPC Servers Follow this description when accessing the 800xA OPC Servers remotely from a third party OPC client. OPC Client Node 3rd Party OPC Client 800xA System Node DCOM 800xA OPC Server Figure 285.
Integrating OPC Servers into 800xA for the server(s) that will be accessed. The application names that show up in dcomcnfg can be found in Table 24. Table 24. Application Names for DCOM Security Configuration OPC Spec Application Name ProgId OPC AE AfwEventOPCServer ABB.OPCEventServer OPC DA AfwDsOpcSurrogate ABB.AfwOpcDaSurrogate OPC HDA AdvHtHda ABB.AdvHtHistorySrv Third Party OPC Client Node in the same Domain as 800xA.
Integrating OPC Servers into 800xA 4. Create a local user with the same name and password as created in Step 1. Make sure that the user never has to change its password.If several accounts are used, repeat this step for each account. 5. Add the user created in Step 4 to Access Permissions in DCOM Security and allow both Local Access and Remote Access. 6.
Integrating OPC Servers into 800xA 3. Add the 800xA System service account to Launch and Activation Permissions in DCOM Security and allow Local Launch, Remote Launch, Local Activation and Remote Activation. If you do not want to use the 800xA System service account, follow the steps for Third Party OPC Server Node in another Domain or without Domain. Third Party OPC Server Node in another Domain or without Domain. Configure the computer(s) running the third party OPC Server. 1.
Accessing 800xA via OLE DB 2. Add the account(s) that will be used when performing an upload to Launch and Activation Permissions in Security for the third party OPC Server. Allow Local Launch, Remote Launch, Local Activation and Remote Activation. Third Party OPC Server in another Domain or without Domain. Configure the computer(s) running the third party OPC Server. 1. Create a local user with the same name and password as the account that will be used when performing an upload.
Accessing 800xA via OLE DB The name of the OLE DB provider is ABB OLE DB Provider for Data Access. It is only possible to connect to the OLE DB Provider from an OLE DB Client running on an 800xA client workstation. Command Line The syntax for the command line is built up by a command followed by one or more keywords as shown below. Command Syntax.
Accessing 800xA via OLE DB Table 25. Keywords (Continued) Keyword Description ASPECT The name or GUID of the aspect where the property belongs. PROPERTY The name of the property. (1) The Object GUID, Globally Unique Identifiers, uniquely identifies each object.
Accessing 800xA via OLE DB The name of the object which has the OLE DB DA Access Table aspect is used with the keyword OBJECTHELPER, described earlier. Configuration 1. Browse for the object or write the full path for the object, in the Object Path area. 2. Select aspect in the Aspect Name drop-down menu 3. Select property in the Property Name drop-down menu. 4. Click Apply to verify the changes. Figure 287. The Help Aspect in Data Access.
Accessing 800xA via OLE DB The name of the OLE DB provider is ABB OLE DB Provider for HT. It is only possible to connect to the OLE DB Provider from the OLE DB Client running on an 800xA client workstation. Command Line The syntax for the command line is built up by a command followed by one or several keywords as shown below. Command Syntax. The command is GET_HISTORY, which has four syntaxes.
Accessing 800xA via OLE DB Keywords A description of the keywords and their respective meaning and syntax can be seen in the table below:. Table 26. Keywords Keyword Description (1) OBJECT The full path or the GUID ASPECT The name or GUID of the aspect where the property belongs. OBJECTHEL PER The name of the short references that holds the OleDB Tables, DA or HDA, i.e. the help aspects. PROPERTY The name of the property. LOG The name of the log.
Accessing 800xA via OLE DB Table 26. Keywords (Continued) Keyword RESAMPLE Description The time between resample on processed reading, in seconds. Ex, RESAMPLE=10000 COUNT Number of returned values expected from the command (overrides and/or changes the resample value) Ex, COUNT=2 (returns two values) MAXCOUNT Maximal number of values to read on a raw reading.
Accessing 800xA via OLE DB • You cannot use the keywords COUNT and RESAMPLE without using the Aggregate keyword. All the keywords must be written in capital letters. If you do not write the command line according to the syntax and restriction above the provider will return an error code that tells you that you have an invalid argument. When you use GUIDs to identify the object you also need to use it for the aspect and vice verse.
Accessing 800xA via OLE DB Similarly, if you write, “MO-1D+5h”, then the start time is 5 a.m. on the last day of the previous month, “NOW-1H15M” is one hour and fifteen minutes ago, and “YEAR+3MO” is the first timestamp of April 1 this year. Table 27. Description of the Keywords in the OPCHDA_TIME Format Keyword Offset NOW Description The current UTC time as calculated on the server. SECOND S The start of the current second. MINUTE M The start of the current minute.
Accessing 800xA via OLE DB Short References. You use a graphical user interface to predefine short references to Historical logs (OPC HDA) or object properties (OPC DA). These short references are objects of the OLE DB Access Table for DS or the OLE DB Access Table for History object types. The aspects contain all the information needed for a specific OPCHDA or OPCDA call to get the requested data. You can use the short references in two ways, from the command line or through the reporting packages.
Accessing 800xA via OLE DB To fill this, perform the following steps: 1. Browse for the object, or write the full path for the object in the Object Path area. If you choose to browse you will get a new dialog box according to Figure 289. Figure 289. The Dialog where you Browse for the Object. 2. Select aspect in the Aspect Name drop-down menu. Slash characters, “/” and “\” are not supported in object and aspect names being historized. 3. Select property in the Property Name drop-down menu. 4.
Accessing 800xA via OLE DB 7. If you choose a raw reading the default number of max item returned is 0, which means that you will get all values in the log. You can limit this by putting a number in this field. 8. If you choose a processed reading you have more options. You can choose what kind of calculation you want to perform on the data. This by changing the calculation field with help of the list. Observe that all OPCHDA servers may not support all type of calculations. 9.
Accessing 800xA via OLE DB GET_HISTORY(OBJECT=[Control Structure]MB300 Test Network/Extended Process Objects x/MB300 AI/AIC4_1; ASPECT=Control Connection; PROPERTY=VALUE; LOG=OPC_5s_5h; FROM=HOUR; TO=NOW) GET_HISTORY(OBJECT=[Control Structure]MB300 Test Network.Extended Process Objects x.MB300 AI.AIC4_1; ASPECT=Control Connection; PROPERTY=VALUE; LOG=OPC_5s_5h; FROM=HOUR; TO=NOW) These paths are fairly long but it is possible to shorting them down.
Property Transfer You can make a processed reading with a certain number of values back. GET_HISTORY(OBJECT= ; ASPECT= ; PROPERTY= ;LOG= ; FROM= ;TO= ;Aggregate= ;COUNT= ) Another alternative you have is to decide how often the values are read. GET_HISTORY(OBJECT= ; ASPECT= ; PROPERTY= ;LOG= ; FROM= ;TO= ;Aggregate= ;RESAMPLE= ) You can also give both, but then it is the value on COUNT that decides the sample rate.
Property Transfer been supplied and the source data can not be computed, then no data transfer takes place. You can make a consistency check of expression syntax and validation of properties by clicking Verify. The result of the consistency check will be displayed in the field at the bottom of the dialog box. It will display if there are any errors, or if the consistency check went well.
Property Transfer The different fields in Figure 290 are described below: Table 29. Property Transfer Aspect Aspect The destination aspect name. Property A destination property in the selected aspect. Expression Source expression. Substitution Value This value will be transferred if the source expression results in bad quality. Abs. Deadband Absolute deadband. An absolute numeric range through which the value can be varied without initiating a transfer.
Property Transfer • 6001 ms for 20 properties Property Transfer Service The Property Transfer service runs transfers defined through Property Transfer aspects. The Property Transfer service is not started by default, so before you can start any transfers the server must be configured. How to set up the Property Transfer 1. Log in as System Administrator. 2. Go to the Service Structure in Plant Explorer. 3. Create a Service Group under the Property Transfer service, see Figure 291 below.
Property Transfer 6. Select the Configuration tab. 7. Click the Add button to add a provider and enter a Name, for example PT_Basic, see Figure 292 below. Figure 292. Add Provider Dialog Box Click OK and then Apply. 8. Go to the new created Provider object (PT_Basic) and its Service Provider Definition aspect. 9. Select the Configuration tab. 10. Select Node in the drop-down menu and click Apply.
Property Transfer See the result below in Figure 293. Make sure the enabled box is checked. Figure 293. Configuration Tab - Service Provider Definition The Status tab displays current status, which in this case should be Service. Redundancy Support The Property Transfer service supports redundancy and allows one or more service providers in each service group. Redundant service provider will use the ServiceStandby concept, only one provider will be in Service state and the others in Standby state.
Property Transfer This is shown in the figure below. Figure 294. Multiple Transfer Service Providers Running the Same Configuration Security Handling The Property Transfer service provider runs under the main administration account for the 800xA System, allowing it to perform any write. If you want to protect the configuration of Property Transfer aspects, the 800xA System manager needs to change the access rights. The default role to configure Property Transfer is Operate.
Libraries Libraries Building Versioned Object Type Libraries The following example creates a new versioned library that shall get object types with control aspects for Control Builder M Professional. How to create object types in this new library is shown in Process Object Type with Signals on page 504 and Process Object Type Built in Function Designer on page 508.
Object Types a. Insert the library into your Control Project. b. Connect the library to the Application. It is possible to package an own library as a System Extension installation kit using Aspect Express, refer to System 800xA Engineering, Aspect Express (3BSE032793*). Then the new library is imported by loading the corresponding system extension in Configuration Wizard.
Building Object Types Object Type Group Creation Object types are collected into object type groups placed in the Object Type Structure. The following steps have to be done to create a new object type group, in our case named Cell Information Object Type Group. 1. Go to the Object Type Structure and select the root object Object Types. 2. Using the New Object dialog, make a new aspect object of the type Object Type Group below the object Object Types, and name it Cell Information Object Type Group.
Building Object Types Table 30. Aspects on an Empty Object Type (Continued) Object Type Type Reference A reference to the type of the Cell Information object. Since it is an object type, it is a reference to an predefined object type “Object Type”. Cell Information Type Definition The definition aspect for the Cell Information object type. It is in this aspect most configuration work is done. So far the object type is empty.
Building Object Types The Cell Information object type should now look like this: Figure 295. Aspects on the Cell Information Object Type Next step is to define how the new aspects should be treated when an instance of the object type is created. There are three different methods to treat an aspect on the object type when an instance is created. It can be inherited to the instance, it can be used as a template for new aspects, or a new aspect of the same aspect category can be created on the instance.
Building Object Types 5. In the Aspect Control tab, on the Cell Information Type Definition aspect, select the General Properties aspect. Uncheck the Inherit to all instances check box and check the Use as template. For Log Document check the Copy to all instances check box and leave Inherit to all instances check box for the Operating Manual. Figure 296. Cell Information Object Type Aspect Control Tab 6.
Building Object Types Figure 297. Cell Information Object Type Category Control Tab These steps are the minimal configuration that has to be done for a simple object type. There are a lot of other configurations described in Reference Information for Object Types on page 521 in Appendix A, Object Types. The newly created object type will immediately show up in the New Object dialog. See Figure 298.
Building Object Types Figure 298. New Object Dialog Box with the Cell Information Object Type An instance of the Cell Information object type will get these aspects: Figure 299.
Building Object Types The Cell Information Type Reference aspect is the reference to the object type this object is an instance of. Figure 300. Relation between Object Type and Object Type Instances When the New Aspect dialog is activated on the Cell Information instance the dialog only will contain the proposed File Viewer category, until the Show all check box is checked.
Building Object Types Figure 301. New Aspect Dialog Box on a Cell Information Instance The General Properties aspect and the Operating Manual aspect are required by the object type, and cannot be deleted from the instance. If an aspect on the object type is changed, the change will be propagated to all instances, unless the aspect on an instance has been overridden by a local change.
Building Object Types Extending an Object Type / Subtype Assume that we, in our imaginary application, have a protected cell that needs additional information compared with an ordinary cell. Instead of doing a complete new object type Protected Cell Information, the Cell Information object type could be extended with the additional information for a protected cell.
Building Object Types 3. Create the Maintenance and Service Manual aspects on the Protect Cell Information object type and configure them. 4. Select the Aspect Control tab on the Protected Cell Information Type Definition aspect and check the Inherit to all instances check box for the Maintenance and Service Manual aspect.
Building Object Types Extend an Object Type / Object Type Extension Definition Aspect Sometimes it is necessary to be able to develop an object type at different locations. It could be, for an example, that the subcontractor for the electronic drawings will deliver the drawings that should be part of the Cell Information object type.
Building Object Types • By using composite object types, you are able to break down your system into blocks. This makes it easier to build and maintain the structures. • A composite object type makes it possible to create multiple objects in more than one structure. For technical reasons composite object types have to be put into a library (see Libraries on page 485 and Appendix B, Library Handling) or have to belong to a system extension.
Building Object Types 1. First we build a simple Drain System object type and configure it using the Drain System Type Definition aspect. 2. Below the object type, we then create a Formal Instance List object, with the New Object dialog, for each structure where we require that the composite object will be created. Below each formal instance list we will describe the wanted layout of the composite instance for this particular structure. Each formal instance list defines a required minimum structure.
Building Object Types When you create a formal instance list, Plant Explorer will automatically insert the top-level type object below the formal instance list. Since the objects below the formal instance lists defines the complete wanted object hierarchy we must include also the top object. It is allowed to remove the inserted top object if we only want to insert some child objects in a specific structure.
Building Object Types 4. We can now create an instance of the Drain System type in the Functional Structure, see Figure 307. Figure 307. Instance of Drain System in the Functional Structure In the structure where you are working, the object instance is placed where you create it. In all other structures it is placed at the root level, from where you can drag it into its proper position.
Examples of Object Types Figure 309. Instance of the Drain System in the Location Structure Examples of Object Types Control Object Types / Composite Control Object Types To build object types or composite objects with control aspects you can either start from within Control Builder M Professional or from within Plant Explorer. Start with CBM: 1. Create the object type in the your library in CBM 2. Edit the control contents in CBM 3.
Examples of Object Types 4. Add the non-control aspects to the corresponding object type aspect object in the Object Type Structure in Plant Explorer. 5. Edit the control contents in CBM or, if the control aspect is a Control Module Type, in Function Designer. To edit control content of a Control Module Type aspect of such an object type you can use Function Designer as shown in Process Object Type Built in Function Designer on page 508.
Examples of Object Types Process Object Type with Signals In the following example you add an composite object type to the library ProcObjSigExtLib created in Building Versioned Object Type Libraries on page 485.
Examples of Object Types Figure 310.
Examples of Object Types 4. Modify the CBM_SignalInformation aspect of each Signal object as follow: Select Create and Connect to Local Variable on Diagram, see Figure 311. Figure 311. Modify Signal Information Aspect 5. Result after Instantiation and having performed I/O Allocation: The instance in the Functional Structure shows the Process Object and its corresponding Signal objects (as shown in Figure 312). Figure 312.
Examples of Object Types The engineering data contained in the Parameter aspects of the Signal objects is transferred to the corresponding Control Module properties using the I/O Allocation function of Engineering Workplace. In a process function object above the instance a Function Diagram in Function Designer shows immediately shows the components that easily can be placed an connected to show the complete function as shown in Figure 313. Figure 313.
Examples of Object Types More details are given in System 800xA Engineering, Engineering Studio (3BDS011223*) and System 800xA Engineering, Engineering Studio, Function Designer (3BDS011224*). Process Object Type Built in Function Designer The basic steps to built an object type comparable to the one described in Process Object Type with Signals on page 504 within Function Designer are: 508 1.
Examples of Object Types 9. With the Insert> Symbol... menu item and its Insert Objects dialog add Input/Output Parameters (from Functional Planning / Generic Function Components / Connectors / Diagram Parameters / ...) as required and connect them to function component ports as required. This will allow you to connect to corresponding ports of the new object type´s component in an upper level Function Diagram. 10. Execute File > Generate Configuration Data: Now the object type is ready to be used.
Examples of Object Types Result is shown in and in Figure 314 and Figure 315. Figure 314.
Examples of Object Types Figure 315. Object Type with Signals in Plant Explorer Note that Input / Output Parameter objects of Figure 315 by default are Symbol Objects and therefore not visible in Functional Structure. They can be switched to Aspect Objects. When instantiating this object type the instance shows as shown in Figure 316 and Figure 317. Figure 316.
Examples of Object Types You can navigate from the Function Diagram on the upper level to the nested diagram on the lower level with the context menu item Goto Child Diagram. This is called vertical navigation. Figure 317. Instance in Function Diagram on Upper Level / Goto Nested Diagram Signal Group A Signal Group is a specific signal object type and represents a number of base IO signal objects types (e.g. CBM_AIS, CBM_DOS).
Examples of Object Types To build a Signal Group you perform the following steps: 1. In Control Builder M create a new structured data type which represents the IO connection. Figure 318. Structured Datatype for I/O 2. Add an additional Object Type Group in your library and create a new object type, for example IOSAgitator. Figure 319. Object Type IOSAgitator 3.
Examples of Object Types 4. Add a CBM_SignalInformation aspect and configure Allocation Type of IO Signal = Connect to Local Variable on Diagram of Structured Data Type, Variable Data Type = IO_SAgitator, Attributes= retain as shown in Figure 320. Figure 320. Signal Information 514 5. Create a Formal Instance List object for the Functional Structure below the IOSAgitator object type. 6.
Examples of Object Types The following additional steps have to be performed if the object type shall be used in Function Designer: 1. Copy and paste the Function Parameter aspect and then the Function aspect from the CBM_DIS object type into IOSAgitator signal group object type. 2. Open the component view from the Function aspect and modify the component a. Right click on the copied Function Aspect and click Component, see Figure 321. b. Right click on the lower label and click Delete. c.
Building Reuse Instructions h. In the Aspect Properties dialog click on the first row dealing with IN port. i. Shift click on the last row dealing with IN port. j. Right click in the selected area and click Remove Property. k. Click on the value cell of property Value.DataType. l. Replace data type BoolIO by IO_SAgitator. m. In the Aspect Properties dialog press OK. 3. In the Function Designer window press Save and Close on window level to exit. 4.
Building Reuse Instructions Category Control, Modify Child Control, Set Supertype) or Control Builder M operations (Add Variable, Add Parameter, Add Alarm, Modify Alarm, Generate FB Calls). 7. Below the Reuse Instruction object you configure the Question and Answer tree by creating instances of Reuse Question and Reuse Answer object types. You name the objects according to the questions and answers.
Building Reuse Instructions The example in Figure 322 and Figure 323 show a generic drive system implemented by a Reuse Instruction. Figure 322.
Building Reuse Instructions Figure 323.
Building Reuse Instructions 520 3BDS011222-510 B
Appendix A Object Types Reference Information for Object Types The chapter contains detailed information about object type configuration, and explains the mechanisms used when creating and maintaining instances of an object type. The Object Type Structure contains all object types, which are defined in the system. The object types are structured into different folders called Object Type Groups.
Aspect Groups Appendix A Object Types When an object type is created it automatically gets an Object Type Definition aspect. This aspect defines the behavior of the object type. Its Configuration View has a number of tabs, and they are described in detail in Configuration Dialogs on page 526. To create an instance of an object type you use the New Object dialog, where you can browse among the object types defined in the Object Type Structure. An object type also acts as an aspect category.
Appendix A Object Types Aspects An instance can only be of one object type, and an object type can only have one supertype. But with aspect groups it is possible to inherited aspects from other sources. When an aspect group is created it automatically gets an Aspect Group Definition aspect. It also gets an Aspect Category Definition aspect, which makes it an aspect category object.
Aspects Appendix A Object Types The super type reference aspect has the same user interface as the type definition, but all controls are read-only. Object Type Extension Definition Aspect The Object Type Definition aspect mentioned above is a central place where rules regarding many different aspect systems can be specified. If these aspect systems are delivered from different sources, it can be hard to combine all rules in one single type definition aspect.
Appendix A Object Types Aspects Aspect Category Definition Aspect The Aspect Category Definition aspect is used internally by the system, and is necessary to make aspect inheritance possible. This aspect is automatically created on object types, object type groups, and aspect groups. Formal Instance List Definition Aspect Each formal instance list object has a Formal Instance List Definition aspect that defines which structure the formal instance objects below it should be instantiated in.
Configuration Dialogs Appendix A Object Types Aspect Group Reference Aspect When you create an aspect group, you actually define a new aspect category of the predefined aspect type Aspect Group Reference. When you use the aspect group you create an aspect of this aspect category on the objects where you want to inherit the aspects in the aspect group. This aspect that you create acts as a reference to the aspect group, and its aspect name is the same as the aspect group.
Appendix A Object Types Configuration Dialogs Mark the Can be subtyped check box, to allow this object type to be subtyped by other object types. If this box is unmarked, no subtypes are allowed. The Subtype Info area displays the names of the subtypes having inherited characteristics from this object type. A subtype inherits aspects and type rules of the supertype, and can specify additional aspects and type rules.
Configuration Dialogs Appendix A Object Types Figure 325. Create Info Tab In the User Role Info area, mark the Can be created by all users check box, if instances of the object type can be created by all users. Click Select to choose a specific user role, for example the System Engineer role, to create the object type instance. In the Structure Info area you specify if the object type is allowed to be created as a root object, and if it can be created in all structures or just a specific one.
Appendix A Object Types Configuration Dialogs If you mark the Explicit object type check box, the object type will not be available in the New Object dialog, unless it is proposed as a child in the parent’s object type. The Explicit object type field is not inherited from supertypes. It needs to be set locally on each type. This makes it possible to have hidden supertypes (marked explicit) but visible subtypes. Other specifications are inherited from supertypes, but can be overridden in subtypes.
Configuration Dialogs Appendix A Object Types Normally, aspects are inherited from the object type to all instances of the object type, but instead of inheriting an aspect, you can set up an explicit aspect rule in the type definition to copy the aspect using aspect propagation. Propagated aspects are used as initial data for the instances, and are therefore copied to each instance.1 This connection is dynamic.
Appendix A Object Types Configuration Dialogs It is available on the Object Type Definition, Object Type Extension Definition, Object Factory, Object Type Reference and Super Type Reference aspects. Figure 327. Category Control Tab You add desired aspect categories to the list by clicking the Add button. In this example, we have added a File Viewer and a General Properties aspect category. To remove a category select the category and click the Remove button.
Configuration Dialogs Appendix A Object Types If the Allow other categories check box is disabled, then only aspect categories in the list are allowed on instances of the object type. In the Aspect Rule area, you specify how many aspects of an aspect category that are allowed per specific instance. The default values are displayed. Max value set to –1 implies unlimited number of aspects. If min value is greater than zero then the specified number of aspects will automatically be created on the instance.
Appendix A Object Types Configuration Dialogs To add settings for a structure, click the Add button below the Structure drop-down menu. In our example Functional Structure has been added. The list in the tab contains object types that have some settings for the specified structure. Use the Add button below the list to add an object type. In our example a Pump object type is added.
Configuration Dialogs Appendix A Object Types Figure 329. Select Group of Object Types In the Child Sort Order area, you specify how the children created under this object type should be sorted. By default, the As Default radio button is selected. This means that the configuration set up for the Plant Explorer is used as sort order. Rules inherited from a supertype can only be overridden if they have the default values, otherwise they are dimmed out.
Appendix A Object Types Configuration Dialogs Composite Info Tab The Object Type Reference aspect of a composite instance has an additional tab, the Composite Info tab that shows the embedded instances of the composite instance. Figure 330. Composite Info Tab Consistency Tab The Consistency tab is used to activate consistency checking and correction on one specific object type or object type instance. If the object is composite, the children will be checked as well.
Configuration Dialogs Appendix A Object Types Figure 331. Consistency Tab The consistency checking is the same as performed by the Consistency Checker aspect, except that only the aspects belonging to the Object Types aspect system will be checked here. The consistency of user-added aspects will not be checked. The Try to Repair button is activated if inconsistencies are detected during a consistency check. If you press it the inconsistency may, if possible, be removed.
Appendix A Object Types Composite Object Types Formal Instance List Definition Aspect Figure 332. Formal Instance List Definition Aspect View The Formal Instance List Definition aspect makes it possible to change the wanted instantiation structure of a formal instance list after it has been created. Composite Object Types Formal instances are used when composing composite object types.
Composite Object Types Appendix A Object Types Figure 333. Composite Object Type and Instance The object type group contains two simple object types, AI and DI, and one composite object type Tank that has two formal instances of AI and DI. One instance of the composite object type is also shown in Figure 333. The Functional Structure object below Tank is a Formal Instance List object that determines which structure the branch below it will be created in.
Appendix A Object Types Composite Object Types Every formal instance object has a Formal Instance Definition aspect, and actual instances of the formal instance have a corresponding Formal Instance Reference aspect. Terminology A composite object type describes a set of objects organized in structures, with a parent object and one or several child objects.
Composite Object Types Appendix A Object Types Independent Instance Embedded Instance Figure 335. Composite Instance The main type object and the formal instance objects can belong to several formal instance lists (by using several structure aspects on the same object). In the actual instance, only one physical child object will be created, but it will be shown in all the wanted structures. The formal instance lists are placed directly below the top object of the composite type.
Appendix A Object Types Composite Object Types minimum structure for the instance, not the complete structure. The minimum structure can be extended in each instance, but not reduced. In the same way, it is allowed to create additional subobjects below any formal instance. They will be treated as normal formal instances, and be propagated to the actual instances. The formal instances themselves can also be of composite types, and they must follow the same restrictions as actual instances.
Creating an Object Icon Aspect Appendix A Object Types The only difference is that the Copy to all instances check box is marked by default for formal instances, and not the Inherit to all instances check box. But aspect propagation can be disabled, or replaced with inheritance, using the Aspect Control tab. If the formal instance itself is an instance of an object type, that object type defines the initial set of aspects for the formal instance.
Appendix A Object Types 3. Creating an Object Icon Aspect Double click on Small or Large icon box as shown in Figure 336. Figure 336. Selecting an Icon 4. From the opened State Normal Icon dialog box, select required icon from the list of existing stored icons. If no icon exists then Click Add (see Figure 337). Figure 337. State Normal Icon Dialog Box 5. In the opened file browser window browse the file system for the icon you have built and select it. 6. Click the Open button.
Creating Other Aspects Appendix A Object Types 7. Select the now listed icon from State Normal Icon dialog box and Click OK. 8. Click Apply button in the Config View window. You have now added and selected an icon as default object icon to the object type, or added an icon to the aspect’s icon file. The Object Icon aspect on the object type will be inherited to all instances of that type.
Appendix B Library Handling System 800xA supports development, distribution and management of versioned libraries. Libraries are important entities in the 800xA system. They structure the information in the Object Type Structure into higher-level version-controlled units, and define the building blocks that are used to build the applications that the 800xA system is designed to support.
Creating a New Base Library 1. Appendix B Library Handling Go to the Library Structure and select the Libraries object. All base libraries must be placed here. Figure 338. Library Structure 2. Right-click and select New Object from the context menu. Select Library and name the new library object. 3. In the Additional Arguments dialog box, see Figure 339, you select version number for the first version of the library.
Appendix B Library Handling 4. Creating a New Base Library Now a Library object is created for the new library and a Library Version object for the first version of the library is created. The Library Version is also inserted in the Object Type Structure, at the specified insertion point, refer to Figure 340. Figure 340. New Library Version in the Object Type Structure and Library Structure 5.
Creating a New Base Library Appendix B Library Handling Below the Library Version object the folder objects Control Module Types, Data Types, Function Block Types and Internal Types are created. 3. Now you can start to add your object types to the library. Adding Data to a Base Library Version A base library can contain object type groups, object types and aspect groups. How to add objects and aspects is described below.
Appendix B Library Handling – Creating a New Base Library If the source aspect belongs to an extension library, the target aspect is assigned to the same extension library if the source object and the target object belong to the same base library, and the extension library is open. When an aspect is copied from one library to another the following applies: If the source aspect belongs to a base library, the target aspect is assigned to the other base library that owns the target object.
Creating a New Base Library Appendix B Library Handling The archive file will include the Library Version object and its children in the Object Type Structure (without aspects assigned to other libraries), the Library Version object in the Library Structure including its top-level object, and the library key from the Admin Structure. The top-level Library object is included for all exported library version. This means that it will be overwritten every time you import a new version.
Appendix B Library Handling Creating a New Base Library It is possible to re-open a released library to create a new minor version or revision of it that keeps the same identities of all object types, see Creating a New Minor Version or Revision on page 551 for more information. To stop end-users from doing that, a released library should be protected with a password.
Creating a New Base Library 3. Appendix B Library Handling When the library version is updated, it can be released again and exported to the end-users. For other Libraries: 1. Select the old released library version on your development system and set the state to open. 2. The Set Re-Open Password dialog box will appear. By using the password that was set when the library was released, the state will change to open. Figure 344.
Appendix B Library Handling – Creating a New Base Library Right-click the Library object and select New Object. Select Library Version. Enter or accept the proposed version designation for the predetermined Library, see Figure 345. Click Create. All objects from the previous library version are automatically copied to the new version. Figure 345.
Creating a New Base Library Appendix B Library Handling Library Definition Aspect The Library Object has a Library Definition Aspect that has one tab. The Versions tab lists all versions of the library. It is possible to create a new version by using the New Version button. You also have the possibility to change the insertion point, in the Object Type Structure, for future versions of the library. Figure 347.
Appendix B Library Handling Creating a New Base Library General Tab The General tab is used for managing owner information, library states, and generation of library archives. It is also possible to create a new version of the library from this tab. Figure 348. General Tab To set a state to a library you use the radio buttons in the State area. More information on Library States is given in IndustrialIT 800xA - System, Engineering Planning (3BSE041389*).
Creating a New Base Library Appendix B Library Handling Figure 349. History Tab You may also add or own comments by using the Add Comment button. Type your comment and click OK and the comment will be added to the history list. Figure 350. Add History Comment Dialog Box If you want to delete a comment click the Delete button. Aspects Tab This tab allows you to examine and work with the set of aspects that belong to the object types of the chosen library version.
Appendix B Library Handling Creating a New Base Library are unassigned and do not belong to any library). Such aspects may be added to the library version from this tab. Aspects may also be removed, which means that the aspects are unassigned but still present on the object type. There are three different filters that can be applied: • Aspects included in this library - Select this check box to display the aspects that are assigned to the library. The aspects will be displayed in the left side view.
Creating a New Base Library Appendix B Library Handling By clicking the Search button a check is made of the objects in the library and their aspects. Aspects that are included in the current library will be listed in the left list view. Other aspects that are found will be listed in the right list view. To assign an aspect to the library you select it in the right side view and click the arrow button to move it to the left side view. To remove an aspect from the library you do the opposite.
Appendix B Library Handling Creating a New Base Library • Aspect group dependency - The base Library (or extension library) has a reference to an aspect group declared outside the current library. • Implementation dependency - The base library (or extension library) contains an aspect that declares that it depends on some aspect outside the current library.
Creating a New Base Library Appendix B Library Handling a single lines instead of a line for every formal instance. A library version can only have dependencies to one version of another library. Figure 353. Library Usage Tab The Library Usage tab also handles upgrade of instances from other versions of the library to the current version. This is not supported for AC 800M libraries.
Appendix B Library Handling Creating a New Base Library To upgrade (or downgrade) a non-AC 800M instance to the current version you must select it in the right side view and the move it, by using the arrow button, to the left side view. See Figure 354. Figure 354. Library Usage Tab - Upgrade Instances If you want to see which library version a particular instances’s object type is placed in you right-click on the object in the object browser of the Plant Explorer and select Show Type.
Creating a New Base Library 5. Appendix B Library Handling As a result all object instances in the Application of the object types in the 1.0-0 version of the library are upgraded to the corresponding object types of the 2.0-0 version. Consistency Tab Under the Consistency tab you can check the consistency within a library. By using the Check Consistency button all aspects included in the base library version, including all its active extension libraries will be checked for errors.
Appendix B Library Handling Creating a New Base Library If an aspect reports an error, it sometimes can make a correction to make it consistent again. If at least one aspect can be corrected, the Try to Repair button will be enabled. If you select Try to Repair, all such aspects will be told to repair themselves. It is recommended to make a backup before trying to repair aspects. The recommended procedure to repair aspects are: 1.
Creating a New Base Library Appendix B Library Handling History Tab The history list in the History tab shows history information or the member. Figure 357. Library Member Aspect - History Tab Aspects Tab The Aspects tab has the same functionality as the Aspects tab on the Library Version Definition aspect (see Library Version Definition Aspect on page 554), except for the Search button. When clicking the Search button in Figure 358, it will only check the current object.
Appendix B Library Handling Deleting a Library Figure 358. Library Member Aspect - Aspects Tab Deleting a Library When you delete a Library Version object from any structure, it removes itself from both the Object Type Structure and the Library Structure and removes all its object types from the Object Type Structure. All versions of a library can be deleted in this way except the last one.
Extension Libraries Appendix B Library Handling Renaming is done in the Name aspect or under the General tab of the Library Version Definition aspect. If you use the Name aspect, the version part can be omitted. The current version as specified in the Library Version Definition aspect will the be appended. You can also increase the revision number together with the rename operation in the Name aspect. The Library Version Definition aspect will be updated accordingly.
Appendix B Library Handling Extension Libraries Extending Object Type Definitions If the extension library needs to add new type rules for the object types in the base library, e.g. a Copy-to-all-instances rule for an aspect added by the extension library, they could not be set up in the normal Object Type Definition aspect. It always belongs to the base library and the base library can have been released when the extension library is loaded.
Extension Libraries 3. Appendix B Library Handling Select Extension Library and type the new library name in the Name field. Select version number for the new extension library and the version of the base library to connect with, refer to Figure 360. Figure 360. Creating New Extension Library - New Object Dialog Box 4. Click Create. Now an Extension Library object is created for the new extension library.
Appendix B Library Handling Adding Data to an Extension Library Version The Extension Library Version object is placed both below the Extension Library object and below the Base Library Version object to which it is connected, refer to Figure 361. Figure 361. Extension Library With Three Versions Adding Data to an Extension Library Version To add data (aspects) to an extension library version, you create aspects on the objects in the corresponding Base Library version in the Object Type Structure.
Creating a New Extension Library Version Appendix B Library Handling The assignments to libraries can be adjusted afterwards. To assign aspects to an extension library version, you open its Extension Library Version Definition aspect (on the Extension Library Version object in the Library Structure), and use its Aspects tab, refer to Figure 363. Figure 363.
Appendix B Library Handling Creating a New Extension Library Version extension library version can be active in parallel because they are connected to different objects. A new version can be created either by using the New Object dialog box (which uses the last version as predecessor) or by using the New Version button under the General tab. The predecessor version must always be released and active in both cases. Both procedures are described below.
Creating a New Extension Library Version 4. Appendix B Library Handling Click Create. The new version will be open and active when you have created it. To create a new Extension Library Version using the New Version button, follow the steps below: 1. Open the Extension Library Version Definition aspect for the wanted predecessor. 2. Click the New Version button. 3.
Appendix B Library Handling Extension Library Version Definition Aspect Figure 366. Extension Library Definition Aspect Extension Library Version Definition Aspect Each extension library version object has an Extension Library Version Definition aspect. This aspect manages the version of the extension library and all the aspects that belong to the extension library version. The aspect has five tabs, which are described below: • General Tab - Is used for basic management of the extension library version.
Extension Library Version Definition Aspect Appendix B Library Handling General Tab The General tab is used for managing owner information, library states and activation, and generation of library archives. It is also possible to create a new version of the extension library from this tab. Figure 367. Extension Library Version Aspect - General Tab Refer to IndustrialIT 800xA - System, Engineering Planning (3BSE041389*) for information on Extension Library States.
Appendix B Library Handling Extension Library Version Definition Aspect If the new extension library version includes only a part of the aspects from the old version, the obsolete aspects of the old version will continue to exist in the new version. To overcome this scenario, inactivate the old version prior to importing a new version.
Extension Library Version Definition Aspect 576 Appendix B Library Handling 3BDS011222-510 B
Appendix C SMS and E-Mail Messaging Setup and Configuration Worksheets The following tables are worksheets to help in setting up and configuring SMS and e-mail Messaging. • Table 32: GSM Hardware Setup Worksheet. • Table 33: Aspect System Structure Setup Worksheet. • Table 34: Users Worksheet. • Table 35: User Setup Worksheet. • Table 36: Configuration Worksheet. The worksheets are also designed to be used as configuration records. Each one starts on a new page for ease of copying.
Setup and Configuration Worksheets Appendix C SMS and E-Mail Messaging Table 32.
Appendix C SMS and E-Mail Messaging Setup and Configuration Worksheets Table 32.
Setup and Configuration Worksheets Appendix C SMS and E-Mail Messaging Table 33. SMS and e-mail Messaging Aspect System Structure Setup Worksheet Item Setting/Value Modem Device Aspect Phone Number (default pager service provider’s Central Paging Terminal telephone number) Value: ___________________ Email Device Aspect 580 From (default e-mail address where error messages (e.g.
Appendix C SMS and E-Mail Messaging Setup and Configuration Worksheets Table 34.
Setup and Configuration Worksheets Appendix C SMS and E-Mail Messaging Table 34.
Appendix C SMS and E-Mail Messaging Setup and Configuration Worksheets Table 35.
Setup and Configuration Worksheets Appendix C SMS and E-Mail Messaging Table 36.
Appendix C SMS and E-Mail Messaging Setup and Configuration Worksheets Table 36.
GSM Service Providers Appendix C SMS and E-Mail Messaging GSM Service Providers Table 37.
Appendix C SMS and E-Mail Messaging GSM Service Providers Table 37.
GSM Hardware Devices Appendix C SMS and E-Mail Messaging Table 37. GSM Service Providers (Continued) GSM Service Provider1 Omni - GSM (I) SMSC Number2 GSM Service Provider SMSC Number +393492000200 Westel900 - GSM (H) +36309888000 NOTE: 1. This table lists GSM service providers and their SMSC numbers as of the original publication of this instruction.
Appendix C SMS and E-Mail Messaging GSM Hardware Devices Table 38.
GSM Hardware Devices Appendix C SMS and E-Mail Messaging Table 38. GSM Hardware Devices (Continued) GSM Hardware1 Westermo GD-01 Initialization String AT+CSCS=”HEX” Tested by ABB Yes NOTE: 1. This table lists specific types of GSM hardware and their initialization strings as of the original publication of this instruction. The exclusion of GSM hardware information is not intended to imply that the GSM hardware is not compatible with SMS and e-mail Messaging.
Index A ABB SolutionsBank 218 AC 800M Controller 29 Access Control 397 ActiveX Wrapper Aspect Add 385 Create 385 Additional Info Tab 433 Advanced Access Control 397 Aggregate 342 Annotations 347 Average 345 Bad Data Quality Limit 342 Count 346 Delta 346 Duration Bad 347 Duration Good 346 End 346 Exception Deviation 344 Interpolated 345 Max Actual Time 346 Maximum 346 Min Actual Time 346 Minimum 346 Percentage Bad 347 Percentage Good 347 Range 346 Regression Const 346 Regression Deviation 346 Regression Slop
Email device 185 Modem device 182 Asset Monitoring 393 Attempts field 209 Audit Trail 414 Configuration 414 Authentication 397 Authorization 397 Automation Solution 27 B Base Library 545 Add Data 548 Create New Base Library 545 New Major Version 552 New Minor Version/Revision 551 Basic Alarm Analysis 124 Batch Management 325 Bookmark Aspect 380 bring on line 364 Bulk Configuration 358 Property Logs 358 Bulk Data Manager 41 C Category Control Tab 490, 522, 530 Central paging system 184 Child Control Tab 53
FOUNDATION Fieldbus 217, 270 PROFIBUS & HART 217 Device Management System DMS 267 Device Object Types 226 Device Type 232 device type 223 device type file 223 Device Type Manager 254 device types 217 Document Management 364 Document Manager 365 Documentation 364 Double Authentication 397 Download 218 Download and Upload DTM Data Set 254 DTM 223, 254 E Edit destination dialog box 208 Edit length dialog box 203 Electronic Signature 398 Email device 185 Message subscriber 188, 190 Relay server 180, 186 E-mail
External Alarm 156 External Alarm Silence View 156 F FF alarm 287 FF alarm priority 289 FF Application 271, 281, 294 FF blocks 271, 281 FF device library 273 FF HSE subnet 270 FF signal 283 Field delimiter 204 Field Devices 218 Fieldbus Builder PROFIBUS/HART 239 fieldbus topology 234 File Viewer Aspect 368 How to use 369 File Viewer Functions 373 Filter Acknowledge Time 81 Events 81 Process Alarms 80 Filter states 80 Formal Instance 525, 537 Formal Instance Definition 525 Formal Instance Delete 541 Formal
HART Device Type Objects 244, 268 HART Devices 73, 232 HART Transmitter 245 Help Aspect Instance Help 390 Hiding Masks 98 Hiding Masks Manager 99 Hiding Rules 99 Historical Process Data 329 History Log Template 330 HSE Subnet 275 HSE subnet 271, 274 I I/O Allocation 41 I/O Signal Engineering 504 Icon Aspect 542 import 364 Inbox spooling 169 Independent Instance 539 Initialization string 166 IOPCBrowseServerAddressSpace 421 Item Properties Tab 437 L Libraries 485 Delete 565 Move 566 Release Version 550 Ren
Log Source 341 OPC 340 TTD 340 Log Template 330, 338, 348 Log Type Direct 340 to 341 Hierarchical 340 to 341 M Maximo Integration 394 Message configuration tab 202 Message handler Configuration 205 Destination tab 206 Edit destination dialog box 208 Message source tab 206 New destination dialog box 207 Message length 203 Message prefix 204 Message schedule Setup 193 Message source tab 206 Message subscriber Email device 190 Modem device 188, 191 Setup 187 SMS device 189 SMS/GSM 188 Message suffix 204 Modem
Outbox spooling 169 P Paging service providers 183 Parameter Management 361 Parameter Manager 361 PC, Network and Software Monitoring 396 pdf-file 374 PIN 165 Plant Explorer 27 Prerequisites 217 Process Graphics 73 Process Object Type 504 Built in Function Designer 508 PROFIBUS 217, 232 PROFIBUS Device Type Objects 248 Property Available Sources 350 Data Type 348 Property Info Tab 432 Property Log 332 Property Signal Generator 444 Property Transfer service 481 Property Transfer Definition aspect 478 Proper
SDL Collector Function 313 SDL Manager Extended SDL LogType 309 Mapping of Data Types 312 Property Browser 311 SDL Log 310 SDL Log Property binding 311 SDL LogType 308 Security 397 Service Group 428 Service Provider 429 Service providers Paging 183 SMS/GSM 586 Service structure 199 Soft alarms 199 SIM card telephone number 165 SMS and e-mail messaging 158 Configuration 199 System setup 182 SMS device Message subscriber 189 SMS/GSM hardware device COM port settings 164 Inbox spooling 169 Initialization strin
User structure 187 User setup Message schedule 193 Message subscriber 187 Users Message schedule 193 Message subscriber 187 V Valid Operators 145 Verify DTM Data Set 254 Versioned Object Type Libraries 485 Versioning 398 View Log 231 W Web Page 384 Web Server 248 Windows Application 389 3BDS011222-510 B 599
3BDS011222-510 B
Revision History Introduction This section provides information on the revision history of this User Manual. The revision index of this User Manual is not related to the 800xA 5.1 System Revision. Revision History The following table lists the revision history of this User Manual. Revision Index Description Date - First version published for 800xA 5.1 June 2010 A Updated for 800xA 5.1 Rev A May 2011 B Updated for 800xA 5.
Updates in Revision Index B Updates in Revision Index A The following table shows the updates made in this User Manual for 800xA 5.1 Rev A. Updated Section/Sub-section Description of Update Section 2, Configuration > SMS and e-mail Updated the Alarm and Event Message Source subMessaging section. Section 2, Configuration > Information Management Updated the Information Access Aspects subsection. Updates in Revision Index B The following table shows the updates made in this User Manual for 800xA 5.
ABB AB Control Systems Västerås, Sweden Phone: +46 (0) 21 32 50 00 Fax: +46 (0) 21 13 78 45 E-Mail: processautomation@se.abb.com www.abb.com/controlsystems Copyright © 2003-2011 by ABB. All Rights Reserved ABB Inc. Control Systems Wickliffe, Ohio, USA Phone: +1 440 585 8500 Fax: +1 440 585 8756 E-Mail: industrialitsolutions@us.abb.com www.abb.com/controlsystems ABB Industry Pte Ltd Control Systems Singapore Phone: +65 6776 5711 Fax: +65 6778 0222 E-Mail: processautomation@sg.abb.com www.abb.
