hit counter script
ABB 800xA User Manual
  1. Manuals
  2. Brands
  3. ABB Manuals
  4. Control Systems
  5. Ability 800xA Series
  6. User manual

ABB 800xA User Manual

Distributed control system
Hide thumbs Also See for 800xA:
Table of Contents

Advertisement

Quick Links

See also: Operation
800xA History
Administration and Configuration
User Manual
System Version 6.0
Power and productivity
for a better world™

Advertisement

Table of Contents
loading

Related Manuals for ABB 800xA

Summary of Contents for ABB 800xA

  • Page 1 800xA History Administration and Configuration User Manual System Version 6.0 Power and productivity for a better world™...
  • Page 3 800xA History Administration and Configuration User Manual System Version 6.0...
  • Page 4 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 ref- erenced standard.

  • Page 5: Table Of Contents

    Related Documentation ....................11 Section 2 - Introduction History ..........................13 History Features.......................14 Section 3 - Engineering and Configuration Overview..........................17 Configuring Using 800xA ....................17 Configuring Using Vtrin....................17 Configuring 3 party OPC AE Server with RTDB............30 Section 4 - Visualization and Data Access Overview..........................33 Viewing Numeric Data ....................34...

  • Page 6: Table Of Contents

    System Failure Recovery....................71 Section 6 - Diagnostics and Troubleshooting Introduction ........................75 Tags not Created in 800xA History Embedded Data Collector for 800xA History Logs Created in 800xA ....................75 Events not Appearing in 800xA History Embedded Data Collector ......76 Trends not Appearing in 800xA..................

  • Page 7: Table Of Contents

    Appendix G - Accessing 800xA History DA Server Accessing 800xA History DA Server Using DCOM Settings ........177 Appendix H - User Name Update Procedure User Name Update Procedure on the 800xA History Server and 800xA History DCN nodes Revision History Updates in Revision Index A..................183 Updates in Revision Index B ..................184...
  • Page 8 Table of Contents 2PAA107563-600 B...

  • Page 9: General

    Section 1 About This User Manual General Any security measures described in this User Manual, for example, for user access, password security, network security, firewalls, virus protection, etc., represent possible steps that a user may want to consider based on a risk assessment for a particular application and installation.

  • Page 10: Terminology

    Terminology Section 1 About This User Manual point out useful hints to the reader. The corresponding symbols should be interpreted as follows: Electrical warning icon indicates the presence of a hazard which could result in electrical shock. Warning icon indicates the presence of a hazard which could result in personal injury.

  • Page 11: Related Documentation

    Related Documentation This section includes a complete list of all documents applicable to the History. Title Description History Installation Describes the installation of History using the System Installer utility. For more information, refer 800xA History Installation (2PAA107280*). 2PAA107563-600 B...
  • Page 12 Related Documentation Section 1 About This User Manual 2PAA107563-600 B...

  • Page 13: History

    Section 2 Introduction History History helps to collect information from the sensor to the executive's desktop. It is designed to be a high-performance process historian for the management of real- time data and events. It reliably gathers and serve large volumes of data. It delivers information to the right people at the right time and brings system and people together.

  • Page 14: History Features

    History Features Section 2 Introduction Figure 1. History Layout History Features History comprises of the following features: • History Server • History Embedded Data Collector 2PAA107563-600 B...
  • Page 15 Section 2 Introduction History Server History Server History Server is responsible for storing raw data and aggregated data from the control system. It stores the raw data in Real time database and aggregates the same data. History also stores events and manages system configuration. It provides open interfaces for external applications.
  • Page 16 History Embedded Data Collector Section 2 Introduction 2PAA107563-600 B...

  • Page 17: Overview

    In High Availability Server Configuration, make sure to keep the First Node of High Availability Server Up and Running before you begin creating tags in DCN. To configure History Logs using 800xA, please refer to 800xA System Configuration (3BDS011222*) Configuring Using 800xA Refer System 800xA Configuration (3BDS011222*) for configuring tag using 800xA.
  • Page 18 Configuring Using Vtrin Section 3 Engineering and Configuration definition the tag objects contains definition for the Data Type of the tag, Update Rate with which the data is collected and many other definitions which will be explained in this section. For each tag created in database there is an associated Variable created which represents the current value update of the tag as well current history data, aggregates data can be accessed via trends in VTrin GUI with Variables.
  • Page 19 Section 3 Engineering and Configuration Configuring Using Vtrin Right-click the tabs in the Tag window to view the context menu as shown in Figure Figure 3. Tags List - context menu Click New to view a Properties window for the new tags. 2PAA107563-600 B...
  • Page 20 Configuring Using Vtrin Section 3 Engineering and Configuration In the General Tab, fill in the mandatory fields. Figure 4. Tags - General tab 2PAA107563-600 B...
  • Page 21 Section 3 Engineering and Configuration Configuring Using Vtrin For more information on the available fields in General tab, refer Table Table 1. General Tab - Available Fields Field name Description Proposed Name The name of the tag that is required in the database. This is a mandatory field.
  • Page 22 Configuring Using Vtrin Section 3 Engineering and Configuration Click Current Data Collection tab and fill the details of tag collection, activation fields as shown in Figure Figure 5. Current Data Collection tab For more information on the available fields, refer Table 2PAA107563-600 B...
  • Page 23 Section 3 Engineering and Configuration Configuring Using Vtrin Table 2. Current Data Collection - Fields and Description Field name Description Activity Drop-down menu to enable or disable storing data in history server. This is a mandatory field. By default, Inactive will be selected. This will not update the tag data.
  • Page 24 The syntax for OPC UA path is: opc.tcp://nodename:port/progid//ItemId;namespace=name For example: opc.tcp://fi8- main:4841///Variable.SYS_CPU0_Time;UaNamespace=http://fi.abb.c om/Vtrin The progid value is just some name that can be used if multiple connections to the same OPC UA server is wanted to be configured. If the ProgId is present, the SID name for the connection is nodename_port_progid.
  • Page 25 Section 3 Engineering and Configuration Configuring Using Vtrin Click History Data Collection tab and fill in the available fields as shown in Figure Figure 6. History Data Collection tab 2PAA107563-600 B...
  • Page 26 Configuring Using Vtrin Section 3 Engineering and Configuration For more information on the available fields, refer Table Table 3. History Data Collection tab- Fields and Description Field name Description History Collection If aggregation is required, then click the appropriate option in the Template History Collection Template field.
  • Page 27 Section 3 Engineering and Configuration Configuring Using Vtrin Click Processing Tab and fill in the Compression Error filed as shown in Figure Figure 7. Processing tab 2PAA107563-600 B...
  • Page 28 Configuring Using Vtrin Section 3 Engineering and Configuration For more information on the available fields, refer Table Table 4. Processing Tab - Fields and Description Field name Description Compression Error If compression for storing of the tags is required then user is required to enter here as, 0.1,0.2 (show as equivalent of Percentage) etc.
  • Page 29 Section 3 Engineering and Configuration Configuring Using Vtrin Click Hierarchy tab and enter the values for the appropriate fields as shown in Figure Figure 8. Hierarchy tab 2PAA107563-600 B...

  • Page 30: Configuring 3 Rd Party Opc Ae Server With Rtdb

    Configuring 3 party OPC AE Server with RTDB Section 3 Engineering and Configuration For more information on the available fields, refer Table Table 5. Hierarchy tab Field name Description Enable Consistency If check, it will allow to replicate the tag to DCN (if Tag created in Control History Server Directly) or will replicate to History Server (If the tag is created in DCN directly).
  • Page 31 Section 3 Engineering and Configuration Configuring 3 party OPC AE Server with RTDB 'DA=0;AE=1;node=127.0.0.1;ClsId={6211C2F8-D24C-11d3-8D0D- 00C04F60F050}')" praotstx %APP_DSN% -sql "INSERT INTO eccrossrefs (ProcNumber, TimeClass, OrderBy, CommType, LocalId, RemoteId) VALUES(4, 661, 0, 'OPCAES', 'EID=Events', 'SID=OPCAECLIENT;SOURCES=*')" After the above commands are run. Restart the RTDB-EcOpcClient in DCN using Windows Service Control Manager.
  • Page 32 Configuring 3 party OPC AE Server with RTDB Section 3 Engineering and Configuration 2PAA107563-600 B...
  • Page 33 Section 4 Visualization and Data Access Overview This section describes the procedure for retrieval and viewing the numeric and event data. • Viewing Numeric Data – Using DataDirect – Using Trend Display • Viewing Events Data – Viewing Events on Duration Basis –...

  • Page 34: Viewing Numeric Data

    DataDirect add-in to the excel by browsing to the path, C:\ProgramData\ABB\IM\DataDirect\Bin\ABBDataDirect.xla. Usage of DataDirect requires DataDirect license. For more information about DataDirect, refer System 800xA Information Management Data Access and Reports (3BUF001094*). Open MS Excel and the select the Add-Ins tab to use the Industrial IT functions of DataDirect.
  • Page 35 Section 4 Visualization and Data Access Using DataDirect Figure 10. PPA Process Values 2PAA107563-600 B...
  • Page 36 Using DataDirect Section 4 Visualization and Data Access Industrial IT History Values Using this function, the history data can be retrieved to MS Excel. Figure 11. DataDirect - Industrial IT History Values command 2PAA107563-600 B...
  • Page 37 Figure 12. Industrial IT History Values Using Trend Display Trend display is used to plot traces in a graphical manner. The 800xA History server collects historical data from 800xA System, which can be plotted in a trend display. For visualizing seamless trends a basic history log should be created along with the 800xA History log in the 800xA History Log template.
  • Page 38 Using Trend Display Section 4 Visualization and Data Access Configuring Trend Display For more information about Trend Display Aspects, refer to System 800xA Information Management Display Services (3BUF001093*). Create Trend Display aspect. Double-click Trend Display aspect. The Trend Display window appears as...

  • Page 39: Viewing Events Data

    Section 4 Visualization and Data Access Viewing Events Data Figure 14. Select Object window Select the required object and click OK. The selected object is available in the Object Name field. Object can be dragged and dropped from the plant explorer into the Object Name field.
  • Page 40 Viewing Events by Specific Time and Date Section 4 Visualization and Data Access drop-down menu and then click Hour(s) option from the second drop-down menu as shown in Figure 15. The events for the selected duration appears in the main window. Figure 15.

  • Page 41: Opc Interfaces

    Section 4 Visualization and Data Access OPC Interfaces A list of events pertaining to specific date and time appears in the main window. Figure 16. Viewing Events by Time and Date OPC Interfaces OPC is used to bridge Windows based software applications and process control hardware, control system.
  • Page 42 OPC DA Section 4 Visualization and Data Access OPC DA OPC DA facilitates History Data transfer from History Embedded Data Collector Node to History Server. RealTime History - Opc DA Server is the service responsible for transferring real time data and object path from History Embedded Data Collector Node to History server and representing it in OPC Client.
  • Page 43 Section 4 Visualization and Data Access OPC DA The real time data can be extracted from History server through OPC DA interface available for the History Server. Figure 18. RealTime History-OpcDaServer Service For Real Time Data And Object Path 2PAA107563-600 B...
  • Page 44 OPC HDA Section 4 Visualization and Data Access OPC HDA OPC HDA service facilitates History Data Transfer from History server to History Embedded Data Collector Node. The Historical Data can also be made available to any other applications using the HDA interface available on the History Server side. Figure 19.
  • Page 45 Section 4 Visualization and Data Access OPC HDA CpmPlusKM-OpcHdaServer is the service responsible for sending historical data from History server to History Embedded Data Collector Node. Figure 20. CpmPlusKM-OpcHdaServer Service For Historical Data 2PAA107563-600 B...
  • Page 46 OPC UA Section 4 Visualization and Data Access OPC UA OPC UA Server is installed only on History Server(s) by default and not installed in Data Collectors. Any OPC UA client can connect to OPC UA Server of History and subscribe data.

  • Page 47: Using Dcom Settings For Accessing History Da Server

    Section 4 Visualization and Data Access Using DCOM Settings for Accessing History DA Server Modify the Security Setting as shown in the following screen. Figure 22. Modification of RTDBOpcUaServerConfig file Save and Close the file RTDB-EcOpcClient, using OPC UA Specification 1.01, can subscribe data from OPC UA Servers which can further be processed and stored in History Server.
  • Page 48 Workgroup Environment Section 4 Visualization and Data Access Refer important information related to DCOM settings required for accessing History DA server mentioned below. Ensure to have administrative privileges to create user accounts that are mentioned in the following description. Workgroup Environment In workgroup environment, if the OPC Client PC is in same workgroup as History DA Server then following should be done.

  • Page 49: Odbc Interface

    Section 4 Visualization and Data Access Workgroup to Domain Environment When the History DA Server and Client PC are in different domain When the History DA Server and Client PC are in different domain, first, ensure that to setup a 'Trust Relationship' between both domains. Please contact your system administrator for configuring the 'Trust Relationship' between domains.
  • Page 50 Configuring Excel Data Source Section 4 Visualization and Data Access Perform the following procedure to configure the Data source. Open MS Excel. From the Data tab, select Get External Data > From Other Sources > From Data Connection Wizard as shown in Figure 23.
  • Page 51 Section 4 Visualization and Data Access Configuring Excel Data Source Figure 24. Data Connection Wizard In the Data Connection Wizard, select ODBC DSN and then click Next to view the Select Database and Table screen as shown in Figure Figure 25. Data Connection Wizard - Select Database and Table screen 2PAA107563-600 B...
  • Page 52 Configuring Excel Data Source Section 4 Visualization and Data Access Select OpcEventLog_All or other tables if required and then click Next to view the Save Data Connection File and Finish screen as shown in Figure Figure 26. Data Connection Wizard - Save Data Connection File and Finish screen Select the Always attempt to use this file to refresh data checkbox and then click Finish to view the Import Data wizard as shown in Figure...
  • Page 53 Section 4 Visualization and Data Access Configuring Excel Data Source Select the desired format for Data Export and then click OK. The Historical Data gets exported in the desired format. Figure 28 shows the Excel sheet of exported data. Figure 28. Excel sheet - Exported data 2PAA107563-600 B...
  • Page 54 Configuring Excel Data Source Section 4 Visualization and Data Access 2PAA107563-600 B...

  • Page 55: Diagnostic Information For History

    Section 5 Maintenance and Administration Diagnostic Information for History The following information is common for History Embedded Data Collector as well as History Server Node. The diagnostic information is written to text files and can be accessed from the following location: From Desktop, open RTDB Control Panel folder and then navigate to Diagonistics Tools >...
  • Page 56 Starting Database using RTDB Control Panel Section 5 Maintenance and Administration Double-click the RTDB Control Panel folder shortcut icon on the desktop. Three folders as shown in Figure 29 appears. Figure 29. Folders in RTDB Control Panel Double-click the Start and Stopping folder to open it. The Start RTDB and Stop RTDB batch files appears as shown in Figure Figure 30.
  • Page 57 Section 5 Maintenance and Administration Stopping Database using RTDB Control Panel Stopping Database using RTDB Control Panel To stop the Database: Double-click the RTDB Control Panel folder shortcut icon on the desktop. Three folders as shown in Figure 29 appears. Figure 31.

  • Page 58: Start/Stop History Embedded Data Collector Database

    Once the Database stopping process is completed, the system displays the message “RTDB-service has now been stopped. All tables are OK”. Start/Stop History Embedded Data Collector Database To stop the 800xA History Embedded Data Collector database perform one of the following methods: Start/Stop the database from the database control panel.
  • Page 59 Click the left side, structure drop-down menu and click Service Structure in the menu item as shown in Figure 34 Figure 34. Service Structure in Plant Explorer Workplace Select 800xA History Embedded Data Collector Sync Service Group in Service Structure through 800xA History SyncService, Service as shown in Figure 2PAA107563-600 B...
  • Page 60 Starting Database from ABB System 800xA Section 5 Maintenance and Administration Figure 35. Sync Service in Service structure By default, the Service Group Definition is selected in the right pane as shown Figure 2PAA107563-600 B...
  • Page 61 Section 5 Maintenance and Administration Starting Database from ABB System 800xA Figure 36. Service Group Definition Select the 800xA History StatusViewer aspect as shown in Figure 2PAA107563-600 B...
  • Page 62 Starting Database from ABB System 800xA Section 5 Maintenance and Administration Figure 37. 800xA History Status Viewer Click 800xA History Service Manager as shown in Figure 2PAA107563-600 B...
  • Page 63 Section 5 Maintenance and Administration Starting Database from ABB System 800xA Figure 38. 800xA History Service Manager Check the appropriate Service Provider as shown in Figure 39 in the 800xA History Services window and click Start. Figure 39. 800xA History Services Window...
  • Page 64 Figure Select 800xA History Embedded Data Collector Sync Service Group in Service Structure through 800xA History SyncService, Service in the left pane of Service Structure as shown in Figure By default, the Service Group Definition is selected in the right pane as shown...

  • Page 65: Tag Synchronization

    Section 5 Maintenance and Administration Tag Synchronization Tag Synchronization RealTime History-TagConsistencyController is the service responsible for tag synchronization between the Data Collector Node and History Server. Figure 41. RealTime History-TagConsistencyController Service For Tag Synchronization 2PAA107563-600 B...
  • Page 66 Tag Synchronization Section 5 Maintenance and Administration RealTime History-EventForwarder is the service responsible to pull the events from the Data Collector Node to the History Server. Figure 42. RealTime History-EventForwarder Service For Events 2PAA107563-600 B...

  • Page 67: History Database Disk Configuration

    Section 5 Maintenance and Administration History Database Disk Configuration VtrinLink is the service responsible for real time and historical data transfer between the Data Collector Node and History Server. Figure 43. VtrinLink Service For Real Time And Historical Data Transfer History Database Disk Configuration The Database disk is located on a separate data disk (hard disk drive) and the software is located on another disk.
  • Page 68 History Database Disk Configuration Section 5 Maintenance and Administration A very typical disk configuration is the following: Table 6. Typical Disk Configuration Disk Description Operating System and Product Software History Database and project specific application files. The allocation unit size of this disk is 64kB (kilo bytes) for the best History Database performance.

  • Page 69: Backup And Restore

    Section 5 Maintenance and Administration Backup and Restore Figure 45. History Database - Complex Setup The guidelines to remember when planning for RTDB disk configurations are; • The RTDB database must reside in a single Windows folder, thus, if a sizeable database is required then an adequately sized single logical disk must be provided.
  • Page 70 Database Folders Backup Section 5 Maintenance and Administration From the Desktop select RTDB Control Panel folder. Double-click to open the folder. Double-click the Starting and Stopping folder to open it. Double-click Stop_RTDB.bat. Type Y in the pop-window and then click Enter. Wait for the Database service to stop.

  • Page 71: System Failure Recovery

    Section 5 Maintenance and Administration System Failure Recovery The Daily Backup is run automatically by the History Server Scheduler Service at specific time (default is 21:30 Hrs). The Daily Backup is incremental, i.e., only last day data is updated or last two tables from previous day are updated in the database.
  • Page 72 History Embedded Data Collector Node Section 5 Maintenance and Administration History Embedded Data Collector Node In the History Embedded Data Collector Node, perform the following steps: ShutDown the Machine and remove the failed disk and insert new Hard Disk Drive for the Database. Start the machine.
  • Page 73 Section 5 Maintenance and Administration History Server Before you perform the following steps make sure to re-configure the NLB settings with the same common name and common IP used in the previous configuration. Failing to do so will not allow the NLB in history server to load the cluster.
  • Page 74 History Server Section 5 Maintenance and Administration To restore RTDBData Directory, do the following: Navigate to E:\EssentialBackup folder and choose the latest available backup, unless it is known that a better backup can be made use of, like WeekDay7, Day9 and so on. Run the following command in cmd editor.

  • Page 75: Introduction

    Tags not Created in 800xA History Embedded Data Collector for 800xA History Logs Created in 800xA Check that 800xA History Source Aspect is created in the Root of the control project. In 800xA Workplace, select service structure and go to: ...

  • Page 76: Events Not Appearing In 800Xa History Embedded Data Collector

    In 800xA History Embedded Data Collector Node, select any log configuration in control structure and check that you are able to get log values. If not, then verify from Service Control Manager, that 800xA History OPC HDA Server is in "Started" state. Start HDA server if it is in stopped state.

  • Page 77: Tags Not Created In Redundant 800Xa History Embedded Data Collector Node

    The 800xA HistorySync Service for Redundant 800xA History Embedded Data Collector Node should be standby mode. When a log is created, the tags will be first created in Primary 800xA History Embedded Data Collector Node then to 800xA History Server and then will be created in secondary 800xA History Embedded Data Collector Node (by 800xA History Server).

  • Page 78: Checking Logs For Rtdb Services

    Navigate to D:\RTDBData\Diag Folder. The Diag folder includes RTDB service related logs. 800xA History Re-installed Whenever 800xA History Server is re-installed, run the following batch file on all 800xA history nodes i.e., History Server and Embedded Data Collector Nodes as a part of post installation step.
  • Page 79 Overview The archive function supports permanent offline storage for numeric process data stored in history logs in 800xA History Server. Without the archive function, when a history log becomes full, the oldest entries will be overwritten by newer entries. When archiving is used, the contents of specified logs are copied to a designated archive media to prevent the loss of critical historical data.
  • Page 80 Overview Section 7 Configuring Archives of filled archive volumes on network file servers. Use both ISO image files and shadow copies as needed. Archive Configuration Archiving is managed by one or more archive device objects which are configured in the Node Administration structure. An archive device is a logical entity that defines where and how archive data is written.

  • Page 81: Configuring Archive Devices

    Section 7 Configuring Archives Media Full Indication In order for client applications to access archived numeric log data, the archived numeric logs must be published. For numeric (property) logs, the archive volume where the archived data resides must be published. The contents of a complete volume, or even multiple volumes can be published in relatively few steps.
  • Page 82 Adding an Archive Device Section 7 Configuring Archives • MO Drive - requires removing and replacing platters as they become full. • Disk Drive - The hard disk may be partitioned into multiple volumes which are sized to match CD ROM or DVD media. Several archive devices can be configured on the same media to satisfy several different archive schemes.
  • Page 83 Section 7 Configuring Archives Adding an Archive Device Select the Archive Service Aspect from this object’s aspect list. Figure 46. Adding an Archive Device in the Node Administration Structure Click Archive Device in the Create New Archive Object section. This displays the New Archive Device dialog, Figure Enter a name for the object in the Name field, for example: ArchDev2OnAD,...
  • Page 84 Archive Device Aspect Section 7 Configuring Archives This adds the Archive Device object under the Industrial IT Archive object and creates an Archive Device Aspect for the new object. Use this aspect to configure the device as described in Archive Device Aspect.
  • Page 85 If these features are enabled, the alarms recorded in the 800xA System message buffer. Attempting to apply an invalid parameter setting causes the Device State field to be highlighted in red to indicate an invalid configuration.
  • Page 86 Archive Device Aspect Section 7 Configuring Archives specify the full path to the directory where data will be archived for example: E:\archive (root directory is not a valid entry for disk drive). Device Behavior and Overwrite Timeout Device Behavior and Overwrite Timeout fields determine how archiving will proceed when the current archive media (volume) becomes full.
  • Page 87 Section 7 Configuring Archives Archive Device Aspect When using archive backup, it is recommended that the device behavior be set to Wrap When Full, and set the overwrite timeout to allow for periodic checking of the backup destination to make sure its not full. The overwrite timeout should be two to three times the interval that is checked for the backup destination.
  • Page 88 Archive Device Aspect Section 7 Configuring Archives The Volume Name Format is a format string for generating the volume ID when initializing a volume during timed archive. Enter any string with/without format characters (all strftime format characters are accepted). This can be changed when manually initializing a volume.
  • Page 89 • The computer must have a Windows user account identical to the account for the user under which the Archive Service runs. This is typically the 800xA system service account. If these conditions are not met, the error message shown in...

  • Page 90: Configuring Archive Groups

    Specify the limit as a percentage of disk usage, or as megabytes used. Choose to generate alarms by checking the respective check boxes. The alarms are recorded in the 800xA System Message Services. Activate/Deactivate an Archive Device An archive device must be active in order to archive data to, or restore data from the device.
  • Page 91 Section 7 Configuring Archives Adding an Archive Group Adding an Archive Group Archive groups are configured and managed via the update object. Typically, this object is added under the Industrial IT Archive object in the Node Administration structure (using the Archive Service Aspect as described in Adding an Archive Device on page 82).
  • Page 92 Archive Group Aspect Section 7 Configuring Archives Figure 52. New Archive Device Object Dialog Enter a name for the object in the Name field, for example: ArchGroupOnAD, click OK. Keep the Show Aspect Config Page check box checked. This will automatically open the configuration view of the Archive Device aspect.
  • Page 93 Section 7 Configuring Archives Archive Group Aspect Figure 53. Archive Group Aspect The primary function of the Archive Group aspect is to add and configure archive groups. This is described in Adding and Configuring an Archive Group on page 93. After configuring an archive group, make changes to the group, or to the archive entries added to the group.
  • Page 94 Archive Group Aspect Section 7 Configuring Archives Figure 54. Adding an Archive Group This displays the Add Archive Group dialog, Figure Figure 55. Add Archive Group Dialog Use this dialog to specify the Group name, description (optional), and the Industrial IT Archive Service Group whose service provider will manage this archive group.
  • Page 95 Section 7 Configuring Archives Archive Group Aspect Click Apply to initialize the new group. Repeat this to add as many groups as required. Then specify the contents of each archive group as described in Adding Entries to Archive Groups. Adding Entries to Archive Groups This procedure specifies the logs (and/or objects) to be archived as part of this archive group.
  • Page 96 Wildcard characters are * and ?. Asterisk (*) means 0 or more of any character. Question Mark (?) means a single character. Event Log Creates an entry for alarm/event messages stored in the 800xA System alarm/event buffer. There is no dialog associated with this option. 2PAA107563-600 B...
  • Page 97 Section 7 Configuring Archives Archive Group Aspect If adjustments are needed to an archive group configuration, refer to Adjusting Archive Group Configurations on page 96. Figure 58. Add Archive Group Numeric Log Entry Adjusting Archive Group Configurations Changes can be made to the archive group configuration on two levels. When selecting an archive group in the archive group list, the context menu, Figure 59, (or...
  • Page 98 Archive Group Aspect Section 7 Configuring Archives Figure 59. Changing an Archive Group Configuration When selecting an entry from the entries list for an archive group, the context menu (or Group Entries button) modify or delete the entry, Figure 60. The is used to Modify Entry command displays the object selection dialog as described in Adding...

  • Page 99: Reading And Managing Archive Data

    Section 7 Configuring Archives Reading and Managing Archive Data Reading and Managing Archive Data The archive function supports permanent offline storage for historical data collected in property (numeric) logs. This section describes how to make archive data available for desktop applications such as DataDirect, how to perform manual archives, and how to maintain archive data.
  • Page 100 User Interface for Managing Archive Data Section 7 Configuring Archives – Removing/Replacing Platters – Activating/Deactivating an Archive Device – Remounting a Volume – Initializing an Archive Volume – Copying Volumes – Overriding Volume Backup • Archiving Logs Manually describes how to perform ad-hoc archive operations for archive groups, or selected logs.
  • Page 101 Section 7 Configuring Archives User Interface for Managing Archive Data Archive Device Aspect The Archive Device aspect has two views. The config view is used to configure the archive device. The main view, Figure 61, provides a user interface for managing the archive volumes on the archive device.
  • Page 102 User Interface for Managing Archive Data Section 7 Configuring Archives Supported Functions. The archive functions supported by this aspect are described in Table 8. These functions are available through the context menu and Actions button as shown in Figure Table 8. Archive Functions Supported by the Archive Device Aspect - Main View Function Description Opening an Archive Volume from the...
  • Page 103 Section 7 Configuring Archives User Interface for Managing Archive Data Table 8. Archive Functions Supported by the Archive Device Aspect - Main View (Continued) Function Description Overriding Volume Backup There are certain situations when a volume may need to be marked as backed up, even though the volume has not been backed up.
  • Page 104 User Interface for Managing Archive Data Section 7 Configuring Archives Table 9. Archive Device Aspect Main View (Continued) Field Description Active Volume Indicates which volume is currently active. Volume Indicates the Volume number (Volume Index). Volume ID For scheduled archive, the volume ID is auto-generated based on the configured Next label and Volume Format attributes.
  • Page 105 Section 7 Configuring Archives User Interface for Managing Archive Data within a selected entry. This view also supports initialization of volumes, as well as publishing and unpublishing of volumes. Archive Volume objects are located under their respective archive device object which is typically under an Industrial IT Archive service provider object in the Node Administration structure.
  • Page 106 User Interface for Managing Archive Data Section 7 Configuring Archives Table 10. Archive Functions for Archive Volume Aspect (Continued) Field Description Verifying Signatures for Used to verify electronic signatures on a a Volume volume to determine whether or not the contents of the volume have been altered without authorization.
  • Page 107 Section 7 Configuring Archives User Interface for Managing Archive Data Table 11. Volume Information - Top Section (Continued) Field Description Archive Entries Number of occasions when data have been archived to this volume (number of archive entries written to the volume).
  • Page 108 User Interface for Managing Archive Data Section 7 Configuring Archives Table 13. Log Information for Selected Entry - Bottom Section Field Description Index Sequential number. Type Numeric as specified in the archive group. Start Time Start time for archived data. End Time End time for archived data.
  • Page 109 Section 7 Configuring Archives User Interface for Managing Archive Data Further details related to archive group entries are accessible through the List Group Items function. Figure 63. Archive Group Aspect The functions supported by this aspect are described in Supported Functions. 2PAA107563-600 B...
  • Page 110 User Interface for Managing Archive Data Section 7 Configuring Archives The runtime functions supported by this aspect are Supported Functions. described in Table 14. All functions are available through the Action button and context menu as shown in Figure Table 14. Functions Supported by Archive Group Aspect Field Description Archiving Logs...
  • Page 111 Section 7 Configuring Archives Maintaining Archive Media Maintaining Archive Media The media where archive data is written will eventually become full and need to be replaced or erased to make room for new archive data. When an archive device is configured, consider generating an alarm message when the media is approaching full capacity.
  • Page 112 Maintaining Archive Media Section 7 Configuring Archives Removing/Replacing Platters If MO media is being used for archiving, the platter in the MO drive must be changed periodically as the platter is filled. To remove the platter, first deactivate the device as described in Activating/Deactivating an Archive Device. If the platter still cannot be removed, power down the MO drive, then power it up and remove the platter.
  • Page 113 Section 7 Configuring Archives Maintaining Archive Media go to the Archive Device aspect main view, click Actions and choose Activate or Deactivate as shown in Figure Figure 66. Activating an Archive Device Remounting a Volume Volumes should be remounted prior to initializing. A volume may also be remounted to refresh the volume information on the archive device aspect.
  • Page 114 Maintaining Archive Media Section 7 Configuring Archives set to Advance When Full or Wrap When Full. For manual archives, the volume must be manually initialized. For MO drives, before the archive volume is initialized, make sure the media has been formatted as described in Removing/Replacing Platters on page 110 .
  • Page 115 Section 7 Configuring Archives Maintaining Archive Media If the archive device aspect is being used, select and remount the volume. This is not required when using the archive volume aspect. Always remount a volume BEFORE initializing it from the archive device aspect. The information in the archive device aspect is not automatically updated when a new archive media is inserted, and so may not accurately indicate the current Contents of the archive device.
  • Page 116 Maintaining Archive Media Section 7 Configuring Archives The Volume ID and Overwrite Timeout default to the values specified for all volumes on the archive device config view. Use this dialog to change these values if necessary. As an option, enter a Volume Label. For further details regarding these initialization parameters refer to Table Table 15.
  • Page 117 Section 7 Configuring Archives Maintaining Archive Media the Overwrite Timeout has not expired on the media being initialized, then verify whether or not to overwrite it. Figure 71. Initialize Successful Volume Copying Volumes Archive devices can be configured to automatically create shadow copies and/or ISO images of archive volumes when those volumes become full.
  • Page 118 Maintaining Archive Media Section 7 Configuring Archives This displays the Copy Volume dialog, Figure 72. Use this dialog to specify the copy volume parameters as described in Table 16. Click OK when done. Figure 72. Copy Volume Dialog Table 16. Copy Volume Specification Field Description Source Volume ID...
  • Page 119 Section 7 Configuring Archives Archiving Logs Manually Table 16. Copy Volume Specification (Continued) Field Description Destination Quota Used to specify a new quota. The default is to use the quota of the volume being copied. The value is entered in megabytes (MB). Temporary Storage path Overwrite Destination This check box is used to specify whether or not to overwrite the...
  • Page 120 Archiving Logs Manually Section 7 Configuring Archives also be performed. For manual archives, if the specified time range has no samples, no data will be archived. Perform the following method to perform manual archive: • Perform a manual archive of an archive group. This functionality is supported by the Archive Group aspect.
  • Page 121 Section 7 Configuring Archives Making Archived Data Available to Client Applications This displays the Manual Archive dialog as shown in Figure Figure 74. Manual Archive Dialog Specify the manual archive settings as described in Table Table 17. Manual Archive Settings Parameter Description Device...
  • Page 122 Making Archived Data Available to Client Applications Section 7 Configuring Archives Publishing reads the information needed to locate the archive entries from the archive volume and copies the information to media database files located in the directory pointed to by the HS_TMP environment variable. When a request for published archive data occurs, History uses this media database to find the requested data.
  • Page 123 Section 7 Configuring Archives Making Archived Data Available to Client Applications Archive volume aspects are typically located in the Node Administration structure, under their respective archive device aspects. When using an archive volume aspect, the Publish command is available through the Action button, Figure Figure 75.
  • Page 124 Making Archived Data Available to Client Applications Section 7 Configuring Archives At this point the archive data are available for client applications. Figure 76. Publishing from the Archive Volume Aspect 2PAA107563-600 B...
  • Page 125 Section 7 Configuring Archives Making Archived Data Available to Client Applications Figure 77. Success Message Accessing Published Logs Published logs can be accessed by external applications such as DataDirect as easily as runtime logs. The only difference is that the full log name must be used, and the - r suffix must be used in place of the -o suffix to distinguish between original (runtime) and published logs.
  • Page 126 Making Archived Data Available to Client Applications Section 7 Configuring Archives Right-click and choose Unpublish Volume from the context menu. Unpublishing a volume does not decrease the size of the media database files. To recover disk space, these files may be deleted. The files are located in the directory pointed to by the HS_TMP environment variable.
  • Page 127 Appendix A IP Address Change Introduction This section details the procedure for changing the IP Address of History Embedded Data Collector Node and History Server. History Embedded Data Collector Nodes The detection of the change in IP Address in DCN is automatic. In case of DCN node containing multiple IP Addresses, the primary one that is used by the IP stack for History Server communication is used.

  • Page 128: Xa History Server

    800xA History Server Appendix A IP Address Change In IP_Address_of_DCN enter the new IP Address of DCN. For example, @echo "P_MYIPFORMAIN=192.168.0.1" Save and close the document. Activate the Post-Install script: Open windows service control manager from Control Panel > Systems and Security >...
  • Page 129 Appendix A IP Address Change 800xA History Server Change the IP Address of the History Server. Perform the following steps in all the DCNs connected to the History Server: Change the IP Address setup parameter in setup configuration file: –...
  • Page 130 IP Address, on both HA History Servers. Refer to Appendix B Network Load Balancing (NLB) of 2PAA107280-200 800xA History Installation manual for more details. Perform this step if Common IP (Cluster IP) is being changed.
  • Page 131 Appendix A IP Address Change Change of Consistency Controller Network IP SET "ANS_P_MAINSERVERIP=<newNLBCommonIP>" Save and close the file. Open Command Prompt and run the following command to update DatabaseNodes table. "%app_root%\config\featureinstall\APP_TimedTask_HierarchicalCpmPlusK M_activate_after.bat" Change of Consistency Controller Network IP Perform the following steps to change the IP address of Consistency Controller Network (CCN).
  • Page 132 Change of Consistency Controller Network IP Appendix A IP Address Change After restart, open Vtrin UI and navigate to Maintenance > Basics > Service Parameters (SimpleConfig). Verify that the new CCN IP is updated for RTDB_ConsistencyController and RTDB-CVMCServer of both HA Servers. 2PAA107563-600 B...
  • Page 133 Appendix B Calculation using C# Calculation File Introduction This section describes the basic usage of C# Calculations in History. The intended audience is expected to have basic knowledge of Historian Software and usage of Vtrin user interface. Also basic understanding of Microsoft C# programming language and usage of Microsoft Visual Studio.

  • Page 134: Creating Simple Calculation

    Creating Simple Calculation Appendix B Calculation using C# Calculation File Creating Simple Calculation Installing RTDB-CalcScheduler By default, RTDB-CalcScheduler is not installed with History. This is installed by running the bat file: %APP_ROOT%\Calculations\install\APP_Install_CalcScheduler_Calc.bat from the command line. A new service RTDB-CalcScheduler will be visible in the Windows services (services.msc).
  • Page 135 Appendix B Calculation using C# Calculation File Creating Calculation Module and Task Definitions Figure 80. Calculation task properties Click OK and press Ctrl+S to save the settings in the list view. This results in the displaying the no calculation tasks as shown in Figure 2PAA107563-600 B...
  • Page 136 Creating Calculation Module and Task Definitions Appendix B Calculation using C# Calculation File Figure 81. Calculation tasks Similarly, create list displays for Calculation Modules (Vtrin class CalculationModule) and for Calculation task states (Vtrin class CalculatioTaskState). After creating the above displays, the tree structure appears as shown in Figure 2PAA107563-600 B...
  • Page 137 Appendix B Calculation using C# Calculation File Creating Calculation Module and Task Definitions Figure 82. Calculation tasks, modules and task states created To execute four simple calculations a Calculation Module that executes the calculation and one Calculation Task must be created. Select Calculation Modules list and select Edit >...
  • Page 138 Creating Test Variables Appendix B Calculation using C# Calculation File Figure 83. Calculation module configuration created To create a new calculation task, do the following: Select the newly Calculation Module and select Edit > New. Specify the properties. Refer Table Creating Test Variables In order to run the calculations, certain test variables must be created.
  • Page 139 Appendix B Calculation using C# Calculation File Generating Base Class The variable available in History and Vtrin can be used to monitor values as shown Figure Figure 84. Calculation variables created for CalculationExample1 Generating Base Class To create calculations, base class must be generated. The generated base class is then extended in actual calculation code.
  • Page 140 Variable Sections for Calculations Appendix B Calculation using C# Calculation File Special Cases Total variable count is >64000 The current .NET CLR implementation allows only 65536 member fields per class (1534 fields are reserved for other base class functionality). Hence there are only 64000 member fields available.
  • Page 141 Appendix B Calculation using C# Calculation File Variable Sections for Calculations Figure 85. Service Parameters(SimpleConfig) Click Revert tab and accept changes. Define sections for Variable Tables. The idea is to define a section with Maximum 64000 or less Variables. Since the definition of the Section can be trivial, following example explains how to generate variable sections.
  • Page 142 Variable Sections for Calculations Appendix B Calculation using C# Calculation File After performing the above steps, generate the base class run (as single command line): RTDB_CalcGenerator -b "%APP_DATAPATH%" -cb "%APP_ROOT%\bin\RTDB_CalcBase.dll" -bs "%APP_ROOT%\src\Calculations\RTDB_CalcBase.cs" Variables with Section other than empty string (''), will be presented in the calculation class as sSectionName.vVariableName.
  • Page 143 Appendix B Calculation using C# Calculation File Variable Sections for Calculations After this the process of demonstrating the behavior is accelerated by mapping days to minutes. One day is actually one minute in the examples. Calculating c=a+b every 10 seconds This example demonstrates the calculation of sum of two values and writing the result in a third variable.
  • Page 144 Variable Sections for Calculations Appendix B Calculation using C# Calculation File Figure 86. Monitoring calculation variables using Vtrin variables and current values Figure 87 illustrates how different calculation task properties are used to solve first exercise. The actual calculation task can be created bu using Vtrin or using following batch file.
  • Page 145 Appendix B Calculation using C# Calculation File Variable Sections for Calculations Figure 87. Calculating sum of two historical values every 10 seconds 2PAA107563-600 B...
  • Page 146 Variable Sections for Calculations Appendix B Calculation using C# Calculation File Figure 88. Configuring first calculation using Vtrin 2PAA107563-600 B...
  • Page 147 Appendix B Calculation using C# Calculation File Variable Sections for Calculations Daily average calculated once a week Figure 89. Daily averages calculated once a week 2PAA107563-600 B...
  • Page 148 Variable Sections for Calculations Appendix B Calculation using C# Calculation File Moving average Figure 90. Moving average over 5 days calculated every night Calculating daily average and triggering event when condition applies for 5 continuous periods In this previous example it is demonstrated how to observe the beginning of "Thermal autumn".
  • Page 149 Appendix B Calculation using C# Calculation File Variable Sections for Calculations Figure 91. Calculating daily averages after every day to be able to notice when thermal autumn begins Diagnostics For diagnostics purposes there is a class CalculationTaskState. It shows the last execution time and as well when the task is to be run next time.
  • Page 150 Figure 92. Monitoring calculation scheduling from Calculation Task States Creating own calculation Open Visual Studio 2012. Create a new Visual C# Class Library project. Add following References: RTDB_CalcInterface.dll and RTDB_ CalcBase.dll Use the following skeleton: using ABB.Data.RTDB.Calculation; namespace ABB.Data.RTDB.EndUser public class Calc ABB.Data.RTDB.EndUser.CalcBase 2PAA107563-600 B...
  • Page 151 Appendix B Calculation using C# Calculation File Variable Sections for Calculations public override void Initialize() //Your Initializations comes here. Example below is for current history. DefaultCvhHistory = hCurrentHistory; public override void Calculate() //Your Calculation Equations Comes here The variables are accessed using following: •...
  • Page 152 Variable Sections for Calculations Appendix B Calculation using C# Calculation File Table 19. Calculation Task Column Description Name The name for the calculation task. Module Calculation module to be used. Class The name(s) of the calculation class(es) to be run by this task.
  • Page 153 Appendix B Calculation using C# Calculation File Variable Sections for Calculations Table 19. Calculation Task (Continued) Column Description OffsetUnit The time unit of the offset. If left null, Period Length is used as the offset unit. PeriodCount PeriodCount defines the number of consecutive periods to be calculated in the calculation task.
  • Page 154 Variable Sections for Calculations Appendix B Calculation using C# Calculation File 10. Restart RTDBCalcScheduler service. 2PAA107563-600 B...
  • Page 155 This view is also responsible for getting the history server credential details from the user. To view history server status, do the following: Go to Service Structure > 800xA History SyncService, Service. In the Aspect View, select History Supervision as shown in Figure...
  • Page 156 History Supervision Aspect Appendix C History Supervision Figure 93. History Supervision Select Config View. Go to Special Configuration tab and configure history server database details as shown in Figure Click Apply. 2PAA107563-600 B...
  • Page 157 Appendix C History Supervision History Supervision Aspect Go back to the Main View to view the history server connected status - connected as shown in Figure Figure 94. History Supervision - Main View If the connection fails, go to Config View and check for credentials. 2PAA107563-600 B...
  • Page 158 History Supervision Aspect Appendix C History Supervision In the event of network disconnection between Data Collector and History Server, the disconnected status gets updated in History Supervision aspect within one hour. If there is no network disconnection between Data Collector and History Server, the status of History Server RTDB Services gets updated within two minutes.

  • Page 159: Diagnostic Information For 800Xa History

    Control Panel | Diagonistic Tools. Start/Stop History Server Database Starting and Stopping the Database (either in 800xA History Server or the 800xA History Embedded Data Collector Node) can be carried out by various methods. However, it is advised to use the batch file called Start RTDB/ Stop RTDB available in the Desktop in folder Database Control Panel.
  • Page 160 Starting Database Using Database Control Panel Appendix D Diagnostic Information for 800xA Starting Database Using Database Control Panel To start the database: Double-click the Real Time History Control Panel folder shortcut icon on the desktop. Three folders as shown in Figure 95 will be displayed.
  • Page 161 Appendix D Diagnostic Information for 800xA Stopping Database using History Control Panel Figure 96. Start and Stop Real Time Histoy batch files (selected) Double-click the Start RTDB batch file to start the main real time database service in Data Collector Node.
  • Page 162 Stopping Database using History Control Panel Appendix D Diagnostic Information for 800xA Figure 97. Folders in Real Time History Control Panel Double-click the Start and Stopping folder to open it. The Start RTDB and Stop RTDB batch files will be displayed as shown in Figure Figure 98.

  • Page 163: Start/Stop 800Xa History Embedded Data Collector Database

    Once the Database stopping process is completed, the system displays the message “RTDB-service has now been stopped. All tables are OK”. Start/Stop 800xA History Embedded Data Collector Database To stop the 800xA History Embedded Data Collector database follow one of the methods: Start/Stop the database from the database control panel. –...
  • Page 164 Click the left side, structure drop-down menu and click Service Structure in the menu item as shown in Figure 100 Figure 100. Service Structure in Plant Explorer Workplace Select 800xA History Embedded Data Collector Sync Service Group in Service Structure through 800xA History SyncService, Service as shown in Figure 101.
  • Page 165 Appendix D Diagnostic Information for 800xA Starting Database from ABB System 800xA (if Figure 101. Sync Service in Service structure By default, the Service Group Definition is selected in the right pane as shown Figure 102. 2PAA107563-600 B...
  • Page 166 Starting Database from ABB System 800xA (if installed) Appendix D Diagnostic Information for Figure 102. Service Group Definition Select the 800xA History StatusViewer aspect as shown in Figure 103. 2PAA107563-600 B...
  • Page 167 Appendix D Diagnostic Information for 800xA Starting Database from ABB System 800xA (if Figure 103. 800xA History Status Viewer Click 800xA History Service Manager as shown in Figure 104. 2PAA107563-600 B...
  • Page 168 Starting Database from ABB System 800xA (if installed) Appendix D Diagnostic Information for Figure 104. 800xA History Service Manager Check the appropriate Service Provider as shown in Figure 105 in the 800xA History Services window and click Start. Figure 105. 800xA History Services Window...
  • Page 169 Figure 100. Select 800xA History Embedded Data Collector Sync Service Group in Service Structure through 800xA History SyncService, Service in the left pane of Service Structure as shown in Figure 101. By default, the Service Group Definition is selected in the right pane as shown...
  • Page 170 Stopping Database From ABB System 800xA (if installed) Appendix D Diagnostic Information for 2PAA107563-600 B...

  • Page 171: Disconnection

    Appendix E History Sync Service During Network Disconnection Refer to the additional information that follows on functionality of History Sync Service, when there is a network disconnection between the Aspect Server and the Data Collector during tag synchronization. • For example consider the Data Collector containing 7941 Tags, as shown in Figure 107.
  • Page 172 Figure 108. Figure 108. Synchronization Stopped State Based on the disconnection timing, the Sync can be stopped at any moment. In the example given, the Sync stopped at 800xA History Tags value of 936. • Based on Figure 108, it is important to understand that the tags are not actually deleted, instead, the Sync Service Synchronization is stopped.

  • Page 173: Password Update Procedure On The History Server

    Appendix F Password Update Procedure This section describes the steps that have to be followed on the History Server and Data Collector when the Database Admin User Password is changed. This section does not include the procedure to change the password of the source historian that the Data Collector is collecting from.

  • Page 174: Password Update Procedure On The Data Collector

    Close the Credential Manager. Start the RTDB Services. Open Plant Explorer. Navigate to the Service Structure and update the password of History Server for 800xA History EventServer Service and History Supervision aspect. Password Update Procedure on the Data Collector: Perform the following steps to update the Data Collector with the new Password.
  • Page 175 Start the RTDB services from the Data Collector. 10. Open Plant Explorer. Navigate to Service Structure and update the new password in Special Configuration tabs of 800xA History SyncService, 800xA History Event Collector and 800xA History EventServer Services and restart the services.
  • Page 176 Password Update Procedure on the Data Collector: Appendix F Password Update Procedure 2PAA107563-600 B...

  • Page 177: Accessing 800Xa History Da Server Using Dcom Settings

    Ensure to have administrative privileges to create user accounts which are mentioned in the following description. Workgroup Environment In workgroup environment, if the OPC Client PC is in same workgroup as 800xA History DA Server than following should be done. •...
  • Page 178 Server and Client PC. When the 800xA History DA Server and Client PC are in different domain When the 800xA History DA Server and Client PC are in different domain, first, ensure that to setup a 'Trust Relationship' between both domains. Please contact your system administrator for configuring the 'Trust Relationship' between domains.

  • Page 179: User Name Update Procedure On The 800Xa History Server And 800Xa History Dcn Nodes

    Appendix H User Name Update Procedure User Name Update Procedure on the 800xA History Server and 800xA History DCN nodes This section describes the steps that have to be followed on the History Server and Data Collector when the Database Admin User Name or DB Admin User Name is changed.
  • Page 180 Add the user to the RTDB-Admin group by running: "%app_root%\Config\Security\APP_Create_users.bat" If this was the 800xA History Server node, you need to tell the new user name and password to each data collector node: Log on to the data collector node with the user account that was originally used for installing RTDB Update the vault information for entry "CPIMS/MAIN_DBADMIN"...
  • Page 181 Appendix H User Name Update Procedure Instructions for Changing the DB Admin User If this was a DCN node, force re-registration of the DCN node to the main node: In the main node: praotstx %app_dsn% -sql "delete from simpleconfig where sectionname like 'DatabaseNodes_%' and KeyName like 'Added_NN'"...
  • Page 182 Instructions for Changing the DB Admin User Appendix H User Name Update Procedure 2PAA107563-600 B...

  • Page 183: Revision History

    Revision History The revision index of this User Manual is not related to the 800xA 6.0 System Revision. The following table lists the revision history of this User Manual. Revision Description Date Index Published for 800xA System Version 6.0. Octoberr 2014 Published for 800xA System Version 6.0.

  • Page 184: Updates In Revision Index B

    Updates in Revision Index B Updates in Revision Index B The following table shows the updates made in this User Manual for System 800xA 6.0.1: Updated Section/Sub-section Description of Update Appendix H Added the User Name Update Procedure 2PAA107563-600 B...
  • Page 185 Create Auto-Published Volume 87 OPC Interfaces 41 Overwrite Timeout, Archive Device 86 DCOM Settings for Accessing History DA Server Quota, Volume 87 Device Behavior, Archive Device 86 Device Type, Archive Device 85 Diagnostic Information for 800xA History 159 2PAA107563-600 B...
  • Page 186 Index Index shadow copy, backup method 89 Start 58 Start History Server Database 55 Start/Stop History Server Database 159 Starting Database Using Database Control Panel 160 Stop History Embedded Data Collector Database 58 Stop History Server Database 55 Supervision 155, 177 Tag Synchronization 65 Utilization Warning, Archive Device 90 Viewing...
  • Page 188 Contact us www.abb.com/800xA Copyright © 2015 ABB. www.abb.com/controlsystems All rights reserved. Power and productivity for a better world...

Table of Contents

Save PDF