Documente Academic
Documente Profesional
Documente Cultură
User's Manual
Document
Version
Description
Author
1.0
1.1 1.7
Initial document.
THN
THN,
SML, IMF,
EJM, EW
2006-03-30
2.0
EW
2006-10-04
2.1
CAV
2007-01-12
3.0
LB
4.0
CGAP, LB
2003-09-15
2005-10-18
2007-10-09
2007-11-29
2008-04-22
4.1 4.8
2008-08-26
5.0
CGAP
2008-12-16
6.0
CGAP, LB
2009-01-14
6.1
CGAP
2009-01-15
7.0
CHB
2009-02-11
7.1
CGAP, LB
2009-02-18
8.0
LB
2009-03-03
8.1
CHB
2009-03-17
8.2
CHB
9.0
TM
2009-04-28
CGAP, LB,
CHB
2009-06-03
9.1
2009-06-12
9.2
LB
9.3
TM
2009-08-24
10.0
CGAP, LB
2009-09-03
11.0
CGAP
2009-10-14
12.0
CGAP, LB
2009-10-22
12.1
LB
2010-02-03
13.0
CB, LB
13.1
CB, LB
2010-09-01
14.0
BP, LB
2010-09-03
14.1
BP, LB
2009-06-26
2010-02-12
TM, LB
2012-01-10
15.0
MRP, LB
2012-05-07
16.0
LB
2012-08-17
17.0
LB
2013-03-07
17.1
SG
2016-03-09
17.2
SG
SOFTWARE VERSION
Version:
4.7.0
DOCUMENT VERSION
Version:
17.2
COPYRIGHT INFORMATION
Copyright 1997 - 2016, Matrikon International. All rights reserved. No part of this document may be reproduced,
stored in a retrieval system, translated, or transmitted in any form or by any means, electronic, mechanical, photocopying,
recording, or otherwise, without prior written permission of Matrikon International.
CONFIDENTIAL
The information contained herein is confidential and proprietary to Matrikon International. It may not be disclosed or
transferred, directly or indirectly, to any third party without the explicit written permission of Matrikon International.
IMPORTANT NOTICE
Although every endeavor has been made to ensure that the information contained within this document is up
to date and accurate, Matrikon cannot be held responsible for any inaccuracy or error in the information
contained within this document. Matrikon makes no warranty of any kind with regard to the information
contained within this document and Matrikon shall not be liable for any direct, indirect, incidental or
consequential damages which may arise in connection with the furnishing, reliance, or use of the information
contained within this document.
Specifications and statements as to performance in this document are Matrikon estimates, intended for general
guidance. Matrikon reserves the right to change the information contained within this document and any
product specification without notice.
Statements in this document are not part of a contract or program product licence insofar as they are
incorporated into a contract or licence by express preference. Issue of this document does not entitle the
recipient to access or use of the products described, and such access or use shall be subject to separate
contracts or licences.
The receiving party shall not disclose, publish, report, communicate, or otherwise transfer any information in
this document to any third party, and shall protect all information contained herein from unauthorized
disclosure. The receiving party shall permit access to this document only to its employees, agents,
subcontractors, and affiliates who reasonably require access to such information contained herein, have been
made aware of the confidential nature of this document and have executed a written employment or other
confidentiality agreement party to maintain the confidential status of this document.
LICENSE AGREEMENT
This document and the software described in this document are supplied under a license agreement and may only be used
in accordance with the terms of that agreement. Matrikon reserves the right to make any improvements and/or changes to
product specifications at any time without notice.
TRADEMARK INFORMATION
The following are either trademarks or registered trademarks of their respective organizations:
Matrikon and MatrikonOPC are trademarks or registered trademarks of Matrikon International.
OTHER
MatrikonOPC is a division of Matrikon International.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/). Copyright 1998-2008 The OpenSSL Project. All rights reserved.
Table of Contents
Introduction ................................................................................................................... 15
Who Should Use This Manual ............................................................................................ 15
Overview of Manual ......................................................................................................... 15
References ..................................................................................................................... 17
Document Terminology .................................................................................................... 17
Getting Started............................................................................................................... 19
System Requirements ...................................................................................................... 19
Software Requirements ................................................................................................. 19
Hardware Requirements ................................................................................................ 20
Configuration ................................................................................................................. 21
Launching the MatrikonOPC Desktop Historian .................................................................... 21
Configuration Window ...................................................................................................... 21
Toolbar........................................................................................................................ 22
File Menu ..................................................................................................................... 24
Edit Menu .................................................................................................................... 24
View Menu ................................................................................................................... 25
Window Menu............................................................................................................... 25
Help Menu ................................................................................................................... 26
Starting and Stopping MatrikonOPC Desktop Historian ......................................................... 26
Generic Management...................................................................................................... 27
Log Settings ................................................................................................................... 27
Version Information ......................................................................................................... 29
Data Storage Management ............................................................................................. 30
File Format Selection ....................................................................................................... 31
FF7 Configuration Options ................................................................................................ 31
FF7R Configuration Options............................................................................................... 31
FF4 Configuration Options ................................................................................................ 33
Backup Utility ................................................................................................................. 35
Schedule Backup Operation .............................................................................................. 36
Modify Backup Operation .................................................................................................. 51
Remove Backup Operation ................................................................................................ 54
Perform Backup Now........................................................................................................ 55
Restore Backup ............................................................................................................... 57
Backup Utility Logging Options .......................................................................................... 59
Version .......................................................................................................................... 62
Command Line Use .......................................................................................................... 62
Accessing the Command Line ......................................................................................... 63
Command Line Options.................................................................................................. 63
Data Collection Management .......................................................................................... 67
Tag Browser ................................................................................................................... 68
Tag Workspace ............................................................................................................... 71
Tag Management Toolbar............................................................................................... 71
Tag Management Context Menu...................................................................................... 72
Tag Status ................................................................................................................... 73
Adding a Tag .................................................................................................................. 74
Removing a Tag .............................................................................................................. 75
Changing a Tag Attribute .................................................................................................. 76
Renaming a Tag .............................................................................................................. 77
Turning Tags On or Off ..................................................................................................... 78
Changing the Update Rate ................................................................................................ 78
MatrikonOPC Desktop Historian v4.7.0 Users Manual
Table of Appendices
Appendix A
Distributed COM (DCOM)....................................................................... 145
DCOM Configuration Utility ............................................................................................. 145
Default Properties.......................................................................................................... 145
Security Permissions ...................................................................................................... 146
Server Identity.............................................................................................................. 150
Default Protocols ........................................................................................................... 150
Remote Program ID ....................................................................................................... 151
Appendix B
Aliases .................................................................................................. 152
Scaling Expressions ....................................................................................................... 152
Advanced Calculations.................................................................................................... 153
CSV File Format ............................................................................................................ 155
Scaling Algorithms ......................................................................................................... 157
Appendix C
Standard Data Types ............................................................................. 158
Appendix D
Security ................................................................................................ 159
Introduction.................................................................................................................. 159
OPC Security Implementation ......................................................................................... 159
MatrikonOPC Tag Security Configuration Utility ................................................................. 160
Security Details ............................................................................................................. 180
Appendix E
Installation ........................................................................................... 185
Appendix F
Installed Files ....................................................................................... 200
Appendix G
Un-Installation...................................................................................... 207
Appendix H
File Formats .......................................................................................... 212
High Resolution Rolling Buffer (FF4)................................................................................. 212
High Resolution Rolling Buffer (FF7R) ............................................................................... 212
Dynamic File Creation (FF7) ............................................................................................ 213
Appendix I
Attributes.............................................................................................. 214
Appendix J
Desktop Historian Data Types ............................................................... 216
Appendix K
Third-Party Licensing ............................................................................ 217
Syncfusion Essential Studio 4.4.0.51................................................................................ 217
Appendix L
Sample Custom Script ........................................................................... 218
Appendix M
HDA Relative Time Format .................................................................... 219
Appendix N
HDA Aggregate Functions ..................................................................... 221
Table of Figures
Figure 1 - Configuration Window .................................................................................... 22
Figure 2 - Windows Services Panel................................................................................. 26
Figure 3 - Log Settings Tab ............................................................................................ 28
10
11
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
165
166
167
168
168
170
171
172
173
174
175
175
176
177
178
179
180
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
207
208
209
210
211
Table of Tables
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
18
22
23
24
25
25
26
26
29
31
32
12
13
14
Introduction
MatrikonOPC Desktop Historian is an economical, easy to install, easy to configure, and easy to
administer data archiving tool. It focuses on data collection, not data presentation and processing.
It is a solution for time-based data storage that can stand alone, or become part of a total
enterprise data historian solution. Desktop Historian is designed to be a low-maintenance data
storage solution.
Built on MatrikonOPC Integrated Configuration (iC!) architecture, Desktop Historian enables total
MatrikonOPC configuration management. Multiple Desktop Historians can be combined to create a
true distributed historian solution.
Desktop Historian provides storage for OPC Data and has three components:
Core
OPC Server
OPC Client
The embedded OPC client allows data collection from any OPC DA server. The embedded OPC
server allows any software package containing an OPC Client, to be used to inspect the data
contained in Desktop Historian. The Core acts as a storage space within Desktop Historian from
which the OPC server accesses the data.
Data is collected using OPC, and accessed using OPC. MatrikonOPC Desktop Historian is a
standards-based product that can be combined with any OPC product to create a best of breed
solution.
Overview of Manual
This document uses icons to highlight valuable information. Remember these icons and what they
mean, as they will assist you throughout the manual.
This symbol denotes important information that must be
acknowledged. Failure to do so may result in the software not
functioning properly.
BOLD
The Users Manual has been designed as such so that you can click on references in the document
to jump to that referenced point without having to scroll through several pages (in some cases).
For example, if you were to see the sentence Refer to Figure 1 for more information, pressing the
CTRL key and clicking your mouse on the text Figure 1 automatically takes you to the location of
Figure 1 within the document.
This manual consists of several sections and is structured as follows:
MatrikonOPC Desktop Historian v4.7.0 Users Manual
15
Configuration shows how to start and configure the product, and describes each
component in detail, including windows/screens, panels, tabs, and menu commands.
Data Storage Management shows how to customize historical data to be stored and
accessed.
Backup Utility shows how to schedule and manage backups on data stored in Desktop
Historian.
OPC Server Configuration shows how to start and configure Desktop Historians OPC
server.
OPC Client Configuration shows how to configure Desktop Historians OPC client.
Tag Manager Excel Plug-in shows how Tag Manager is used to work with tags in
Desktop Historian.
Diagnostics explains how to use logging, statistical items, data qualities, timestamps,
and result codes to get the most efficiency from the users system.
Appendices:
o
A - DCOM
B Aliases
D Security
E Installation
F Installed Files
G Un-Installation
H File Formats
I Attributes
K Third-Party Licensing
16
References
This document references information found within the following documents/sites:
www.opcfoundation.org
www.matrikonopc.com
www.opcsupport.com
Document Terminology
The following terms are used interchangeably throughout this document:
Table 1 provides a list of definitions for terms used throughout this document.
Term/Abbreviation
Description
A&E
OPC Alarms and Events. Provides access to process alarm and event data.
COM
DA
DCOM
DDE
Dynamic Data Exchange. Allows the transfer of data between two running
applications.
HDA
HMI
Human Machine Interface. Device that allows interaction between the user and
machine. Typically used in process control applications.
Matrikon
Matrikon International.
MatrikonOPC
ODBC
Open Database Connectivity a set of interfaces that allow any ODBC client to
17
Term/Abbreviation
Description
access any ODBC compatible database system using a consistent set of
commands.
ODH
OPC
PLC
18
Getting Started
This chapter contains important information about installing the product and how to contact the
MatrikonOPC Support team.
The System Requirements section shows how to avoid future problems by ensuring that the
system meets the minimum software and hardware requirements. Detailed step-by-step
instructions in Appendix E - Installation walk you through the installation process. Appendix F
Installed Files lists the files that are installed during this process.
Once the software is installed, refer to the Licensing section for information on how to obtain the
appropriate license. The Licensing section will refer you to the Licensing Procedures document that
was installed along with the product and this Users Manual. If any problems are encountered
during installation or licensing, refer to the Contacting Support section for information about how
to contact the MatrikonOPC Support team for assistance.
System Requirements
The software has minimum Software and Hardware system requirements. These requirements
must be met for the software to function properly.
Note: To install and configure a MatrikonOPC server, you must be set
up as an administrative user account rather than a restricted user
account.
Software Requirements
At the minimum, the product requires the following software:
Operating System
Software
Microsoft .NET 2.0 Framework
Internet Explorer 6.0, Service Pack 1 (or better)
For Matrikon Analytics Excel Reporter:
Microsoft Excel 97, 2000, 2003, 2007, or 2010
For Tag Manager:
Note: Tag Manager works with Excel 2007 versions 12.0.6425.1000 and higher. Microsoft Office
Service Packs SP1 and SP2 have to be installed for Tag Manager to work correctly.
19
Note: Tag Manager works with only 32-bit Microsoft Excel and it is
recommended that the most current service packs are installed.
Hardware Requirements
The product requires the following hardware:
2 GB RAM
The software requires the following additional hardware to make use of the corresponding
functionality:
Free Hard Disk Space at least 200 MB of free disk space is recommended for the Historical
Data files. See Appendix H File Formats for specific size requirements, as most
installations will require more than 200 MB of free disk space.
20
Configuration
The products Graphical User Interface (GUI) allows users to view and alter configuration
parameters at run time. When you view a configuration parameter, the information is retrieved and
displayed. The updated parameters are sent as a group to the product when submitted.
Minimal configuration of the MatrikonOPC Desktop Historian is required for the product to function
properly, but you can customize the tools behavior as required. This section of the manual shows
you how to start and configure the tool and describes each component in detail, including the
windows, panels, and menu commands.
The Launching the MatrikonOPC Desktop Historian section of this manual shows you how to
start the software. Also described here, in detail, is the Configuration window.
Configuration Window
The Configuration window is used to configure the tool. It displays the current configuration and
allows users to change configuration parameters.
To view the Configuration window:
1. From the Windows Start button, access MatrikonOPC Desktop Historian (for assistance,
refer to Launching MatrikonOPC Desktop Historian.
2. The Configuration window appears and the Start Page is displayed (Figure 1).
21
Description
Main Menu
Provides access to the File, Edit, View, Window, and Help menus.
Toolbar
Location Bar
Navigation Panel
Settings Panel
Displays the current settings of the item presently selected in the tree-view
pane.
Table 2 - Configuration Window Components
The following sections describe the menus available from the Configuration window, and what
they are used for.
Toolbar
Table 3 describes those items available from the Toolbar.
Note: The node or item selected in the navigation pane will determine the items displayed on the
Toolbar.
22
Command
Description
Returns you to the previous configuration.
Back
Moves you to the next configuration history.
Forward
Selects the node in the navigation pane that is above the currentlyselected node.
Up
New Configuration
Import Configuration
Export Configuration
Selecting this item (when it is enabled) allows you to create a new Alias
Group by accessing the New Alias Group window (Figure 57).
New Group
This toolbar item is available only when you have selected either the Alias
Configuration node, or an existing Alias Group, in the Configuration
windows navigation pane.
Selecting this item (when it is enabled) allows you to create a new Alias
by accessing the Alias Configuration Wizard (Figure 59).
New Alias
Edit
Clone
Delete
This toolbar item is available only when you have selected either the Alias
Configuration node, an existing Alias Group, or an existing Alias, in the
Configuration windows navigation pane.
Select this item to display the Alias Configuration Wizard (Figure 59),
allowing you to edit an Alias Group or Alias.
This toolbar item is available only when you have selected an existing
Alias in the Configuration windows settings pane (i.e., pane on the right
side of the window).
Select this item to display the Alias Configuration Wizard (Figure 59),
allowing you to clone the selected Alias.
This toolbar item is available only when you have selected an existing
Alias in the Configuration windows settings pane (i.e., pane on the right
side of the window).
Selecting this item (when it is enabled) allows you to delete the selected
node or item.
Import
Select this item to display the Import Alias File window which allows you
to select the .csv file you wish to import.
Export
Select this item to display the Export Alias File window which allows you
to select the .csv file you wish to export.
Table 3 - Toolbar Items
The following sections describe the menus available from the Configuration window, and what
they are used for.
23
File Menu
Table 5 describes the File menu commands.
New Configuration
Import Configuration
Export Configuration
Exit
Edit Menu
The Edit menu options are determined by the item selected in the navigation pane.
Table 5 describes the Edit menu commands that are available when an Alias Group is selected in
the navigation pane.
Command
Description
Selecting this option allows you to create a new Alias Group by
accessing the New Alias Group window (Figure 57).
New Group
This menu option is available only when you have selected either the
Alias Configuration node in the Configuration windows navigation
pane, or an existing Alias in the settings pane (i.e., pane on the right
side of the window).
Selecting this option allows you to create a new Alias by accessing the
Alias Configuration Wizard (Figure 59).
New Alias
This menu option is available only when you have selected either the
Alias Configuration node in the Configuration windows navigation
pane, or an existing Alias in the settings pane.
Select this option to display the Alias Configuration Wizard (Figure
59), allowing you to edit the selected Alias.
Edit
This menu option is available only when you have selected either the
Alias Configuration node in the Configuration windows navigation
pane, or an existing Alias in the settings pane.
Select this option to display the Alias Configuration Wizard (Figure
59), allowing you to clone the selected Alias.
Clone
This menu option is available only when you have selected either the
Alias Configuration node in the Configuration windows navigation
pane, or an existing Alias in the settings pane.
Delete
Selecting this option allows you to delete the selected Alias in the
Configuration windows settings pane.
Select this option to display the Import Alias File window which allows
you to select the .csv file you wish to import.
This menu option is available only when you have selected either the
Alias Configuration node or Alias Group in the Configuration
windows navigation pane, or an existing Alias in the settings pane.
24
Command
Export To CSV
Description
Select this option to display the Export Alias File window which allows
you to select the .csv file you wish to export.
This menu option is available only when you have selected either the
Alias Configuration node or Alias Group in the Configuration
windows navigation pane, or an existing Alias in the settings pane.
Table 5 - Edit Menu Commands (Alias Group)
View Menu
Table 6 describes the View menu commands.
Command
Description
Toolbar
Location Bar
When selected, displays the Location Bar below the Main Menu and above
the navigation pane. The Location Bar allows you to track the current
configurations location. By clicking on each segment of the Location Bar,
you can easily navigate to the required configuration screen.
Each segment of the Location Bar also provides a drop-down menu that
allows you to browse to the next available configuration. To access the dropdown menu, click on the arrow on the right side of the required Location
Bar segment.
Navigation Tree
When selected, displays the navigation pane including the navigation tree.
Allows you to efficiently browse through the available configuration of the
current product.
Window Tabs
When selected, shows the available windows tabs at the bottom of the
Configuration window. Allows you to view all currently-open configurations.
The currently-open configurations may be organized with options offered in
the Windows menu from the Main Menu.
Note: This option is not selected by default.
Start Page
Go To
Window Menu
Table 7 describes the Window menu commands that allow you to define how the settings of
pages/tabs are to appear on the right side of the Configuration window.
Command
Cascade
Description
Cascades the currently-opened windows within the configuration.
25
Command
Tile Horizontally
Tile Vertically
Close All
Description
Horizontally arranges the currently-opened windows within the
configuration.
Vertically arranges the currently-opened windows within the configuration.
Closes all currently-opened windows in the configuration. The product
continues to run even with the windows closed.
Table 7 - Window Menu Commands
Help Menu
Table 8 describes the Help menu command.
Command
About iC
Description
Displays an About screen, which includes information about the Integrated
Configuration (iC) configuration management system version.
Table 8 - Help Menu Command
26
Generic Management
Generic settings, including log settings and version information, can be accessed on the Desktop
Historian Options screen panel.
To access the Desktop Historian Options page:
1. From the configuration window, in the tree-view pane (navigation pane on the left side of
the screen), select and expand the following nodes:
Desktop -> Localhost -> OPC Desktop Historian -> Options -> Desktop
Historian Options
2. Click on the Configure item displayed under the Desktop Historian Options node. Figure
3 displays the navigation pane and Desktop Historian Options page.
Log Settings
The Log Settings screen allows for the editing of general logging options. The log files will be
contained within the following location ([ ] indicates the default installation path):
[C:\Program Files\Matrikon]\OPC\Desktop Historian\Core\Log
To view the General Logging Options:
1. From the Desktop Historian Options panel described above, select the Log Settings tab.
2. The Log Settings panel is displayed (Figure 3).
27
Description
Displays the default location where the system activity log file is
saved. To save the log file in a different location, click Browse.
Configuration
Displays the default location where the configuration activity log file
is saved. To save the log file in a different location, click Browse.
Audit
Displays the default location where the log action file is saved. To
save the log file in a different location, click Browse.
Configuration
Audit
28
Command
Description
Higher log levels include lower-level activities. The Data Operations
level also records Tag and System operations. The Tag Operations
level also records System operations.
Apply
Select this button to apply any changes made to the current page.
Cancel
Select this button to discard any changes made to the current page.
Table 9 - General Logging Options Settings Tab
Note: For the General Logging Options Settings to take effect, the Apply button
MUST be selected.
Version Information
Desktop Historian is composed of several components, each of which controls a different task. The
version number of each component used can be found under the Version Information tab (Figure
4) of the Desktop Historian Options panel. This information may be required when contacting
MatrikonOPC Support.
29
Desktop -> Localhost -> OPC Desktop Historian -> Options -> Data Storage
Management
2. Click on the Configure item displayed under the Data Storage Management node. Figure
5 displays the navigation pane and Data Storage Management page.
The file format type (Desired file format field) and configuration settings (Configuration screen
section) for the selected file format can be selected on this tab.
30
Description
Apply
Cancel
Description
31
Apply
Cancel
32
Description
Apply
Cancel
33
34
Backup Utility
MatrikonOPC Desktop Historian includes a utility to configure and schedule backup procedures.
WARNING: The Backup Utility can cause data loss to occur if used
incorrectly.
To prevent this from occurring, the backup command should be
written to only those backup files that are older than the possible
range of insertions, and should not include the active file.
The Backup Utility locks the data files, one at a time, while it is
copying them. While a file is locked, it cannot be written to, and
therefore writes will fail. This means that if data is being archived by
the ODH OPC client with timestamps that fall within the locked file, or
if an OPC HDA client is pushing data into the historian through the
OPC server for ODH with timestamps in the past, those data points
may not be written.
If you need assistance regarding these issues, please contact
MatrikonOPC Support.
Notes:
The Backup Utility requires the entry of a user name and
password for use in executing backup tasks. It is recommended
that the user that is used (i.e., entered) does not change the
password. If the password is changed then each configured
backup task must be updated with the new password.
The Backup Utility can only be used with the FF7 storage
format. While FF7R or FF4 is selected in the Data Storage
Management configuration, backups cannot be scheduled. If
backups are scheduled, and the storage format is changed
from FF7 to FF7R or FF4, the configured backups will not be
executed.
The Backup Utility makes use of the Windows Task Scheduler built into the Microsoft Windows
operating system to schedule the tasks. Scheduled backup operations created by the Backup
Utility are visible in the Microsoft Windows Scheduled Tasks control panel, and can be edited
there as well. However, the Backup Utility provides an easier-to-use means of configuring the
options to the command-line tool that performs the backup operation.
To access the Backup Utility configuration settings:
1. From the Configuration window, in the tree-view pane (navigation pane on the left side of
the screen), select and expand the following nodes:
Desktop -> Localhost -> OPC Desktop Historian -> Backup Utility
2. Click on the Configure item displayed under the Backup Utility node. Figure 8 displays
the navigation pane and the Backup Utility pane.
35
Restore Backup
36
2. Enter a Backup Name and Comment to identify and describe the task being created.
3. Click on the Next button to go to the backup operation selection screen (Figure 10).
37
38
6. From the Destination screen, select the destination to which you want the backup files
sent. The backup can either place the files in a folder, or it can compress the files into a ZIP
file. In either case, a copy of the current tag database files will be included in the folder or
compressed file. The Overwrite existing file(s) option is selected by default. With that
option selected, the Backup Utility overwrites existing data files in the selected folder, or
overwrites the entire compressed backup file. If the Overwrite existing file(s) option is
not selected and the backup operation runs and determines that the files already exist in
the selected destination, the backup operation fails without backing up the data.
7. Click on the Next button to proceed to the Select Files screen (Figure 12).
39
Figure 13 - Create New Scheduled Backup Wizard: Select Files (Delete or Move Operation Selected)
40
8. The Select Files pane is used to set the criteria by which the Backup Utility will choose
which files are to be included in the backup. See Table 13 for a description of each of the
options. See Figure 14 and Table 14 for more details about the Select Files By Date
option.
Option
Description
Selecting this option instructs the Backup Utility to choose all of the data files
in the data directory, except for the one file that is considered the active file.
The active file is the file to which new data points are being written.
Selecting this option selects just the active file.
Note: If the Move or Delete command is selected, this option is not available
(Figure 13).
Selecting this option includes all files in the directory.
All Files
Note: If the Move or Delete command was selected, this option is not
available (Figure 13).
Selecting this option allows for the selection of data files according to the date
range of data that they contain. Selecting this option causes the Select Files
screen to display the date selection options (Figure 14).
Table 13 - Select Files Options
41
Figure 15 - Create New Scheduled Backup Wizard: Select Files By Date (Move or Delete Operation Selected)
Option
Description
Date
Select which of the dates associated with each data file to use for the
selection. Each data file contains all the data between a Start and End date.
The Last Modified of a data file is maintained by the operating system, and
is the date and time to which the file was last written.
Comparison
Select the comparison to use. For the Before and After options, only one of
the two date expression fields will be available. The Between option requires
entries in both of the date expression fields.
[date expression]
and [date
expression]
Enter the date(s) or date expression(s) to set the range of files to be selected
by the backup utility for inclusion in the backup. HDA relative time
expressions may be used or specific dates can be entered. For more
information refer to Appendix M HDA Relative Time Format in this
manual.
Each of the fields has an ellipsis button adjacent to it which displays a form to
simplify the entry of these fields (Figure 16).
The active file is normally excluded from selections by date. If the Date,
Comparison, and date expression(s) include the active file, and this option is
checked, then the Backup Utility includes the active file in the backup.
Note: This option is not available if the Move or Delete operation is selected
(Figure 15).
Table 14 - Select Files By Date Options
42
9. If the ellipsis button for a time expression is selected, the Date Editor window (Figure 16)
appears. Select either a Fixed Date or a Relative Time Expression, and fill out the
associated fields. Click on the Ok button to return to the Select Files By Date screen of
the Create New Scheduled Backup Wizard, with the selected date or date expression in
the date expression field. Clicking on the Cancel button discards any changes made in the
form and returns you to the Select Files By Date screen.
10. From the Select Files By Date screen, click on the Next button to continue to the schedule
type selection screen (Figure 17).
43
11. Select one of the scheduling options and click on the Next button to proceed to the specific
configuration panel for the selected schedule type (listed below). The When my computer
starts option does not have any additional configuration options. Clicking on the Next when
that option is selected will skip ahead to the applicable Credentials screen (Figure 22).
Daily Schedule
Weekly Schedule
Monthly Schedule
12. The Daily Schedule type (Figure 18) configuration screen has the options described in
Table 15.
44
Option
Description
Start Time
The time of day to run the backup. The time of day will be formatted
according to the computers configured regional settings. Seconds, if
displayed, are ignored in the schedule.
Every Day
The default option. When selected, the backup is performed every day at the
selected Start time.
Weekdays
When selected, the numeric selection box is enabled. Enter the period in days
after each scheduled run before the next run should occur.
Start Date
13. Click on the Next button to go to the Credentials screen (Figure 22).
14. The Weekly Schedule type configuration screen (Figure 19) has the options described in
Table 16.
45
Option
Description
Start Time
15. Click on the Next button to go to the Credentials screen (Figure 22).
16. The Monthly Schedule type configuration screen (Figure 20) has the options described in
Table 17.
46
Option
Description
Start Time
Day
17. Click on the Next button to go to the Credentials screen (Figure 22).
18. The One Time Only schedule type configuration screen (Figure 21) has the options
described in Table 18.
47
Figure 21 - Create New Scheduled Backup Wizard: One Time Only Schedule
Option
Description
Date
Time
The time of day to run the backup. The time of day will be formatted according
to the computers configured regional settings. Seconds, if displayed, are
ignored in the schedule.
Table 18 - One Time Only Schedule Options
19. Click on the Next button to go to the Credentials screen (Figure 22).
20. The Credentials Panel (Figure 22) requires the entry of a user name and password for a
Windows account that has privileges to connect to the Desktop Historian service, read
from the data and database directories, and write to the selected destination directory. If
the account selected does not have sufficient permissions for those tasks, the backup
operation is not able to execute or complete. Enter the full DOMAIN\Username and enter
the Password for the account. You need to enter the password a second time to confirm it
was typed correctly.
48
21. Click on the Next button to continue. The Wizard tests the user name and password to
ensure that it is a valid combination. If the user name and password combination do not
work, a warning is displayed and you are returned to the Credentials panel. If the user
name and password are valid, the Summary screen is shown.
Notes:
The check performed does not ensure the user has adequate permissions to perform
the operation, only that the password is correct for the provided user name.
It is recommended that the user that is used (i.e., entered) does not change the
password. If the password is changed then each configured backup task must be
updated with the new password.
22. The Summary screen (Figure 23) is displayed which provides a textual summary of the
scheduled backup item to create. If any of the settings need to be changed, the Back
button can be used to go backwards through the Wizard sequence to reach the appropriate
screen where the settings can be changed.
49
50
51
2. The Modify Scheduled Backup screen lists all of the scheduled backup operations. Each
operation can be enabled or disabled by toggling the Enabled checkbox. A disabled backup
will not be run. Selecting the Back button returns you to the Backup Utility configuration
screen (Figure 8.) Selecting the Modify button on any of the listed backups opens the
Modify Scheduled Backup Wizard on the Backup Name panel (Figure 26.)
Note: The Backup Name cannot be changed when modifying a task.
52
3. Modify the task as required. The Modify Scheduled Backup Wizard uses the same
sequence of panels as the Create New Scheduled Backup Wizard. Use the Next and
Back buttons to navigate through the Wizard screens. Use the Cancel button at any time
to discard any changes made and return to the Modify Scheduled Backup list (Figure 25).
When you reach the Summary panel (Figure 27), the Finish button is available. Click on
the Finish button to commit the changes and return to the Modify Scheduled Task list
(Figure 25).
53
54
2. Click on the Remove button associated with the backup you wish to remove. A confirmation
message (Figure 29) appears. Click OK to confirm the task deletion, or click on Cancel to
return to the Remove Scheduled Backup list (Figure 28).
3. If the OK button was selected, the task is removed and the Remove Scheduled Backup
list is shown with a confirmation message. If the last task was removed, the Backup Utility
configuration screen (Figure 8) is displayed with a confirmation message.
55
2. The Custom Backup entry on the list can be used to configure the backup and run it right
away. Select the Create and Execute button to build a backup operation. Each of the
configured scheduled backups is also listed. If you select the Execute button on one of the
scheduled backups, the settings for that scheduled backup are used to set the options for
the backup operation.
Note: Changing the settings for an existing backup for the Backup Now operation will not
change the settings for the scheduled backup. Those changes apply for the immediate
backup operation only.
3. If the Custom Backup items Create and Execute option was chosen, the Backup Now
Wizard is displayed showing the Backup Operation panel (Figure 31).
56
4. The Backup Now Wizard uses the Backup Operation, Destination, Select Files,
Credentials, and Summary screens in the same way as the Create New Scheduled
Backup Wizard and the Modify Scheduled Backup Wizard. Clicking on the Finish
button on the Summary screen executes the backup.
5. If the Execute button on one of the existing Scheduled Backup operations is selected, the
Backup Now Wizard will skip to the Summary screen. The Back button can be used to
access the other portions of the Wizard.
Note: The credentials stored for a scheduled task are lost if you click on the Back button
(from the Summary screen in this case). You are required to re-enter the password for the
account to execute the backup.
Restore Backup
The Restore Backup Operation is used to get data files stored in a backup location and add them
to the live system.
To restore data files from a backup:
1. Click on the Restore Backup icon from the Backup Utility configuration panel (Figure 8).
2. The Restore Backup screen (Figure 32) appears.
57
3. Select the applicable option indicating either a folder source (Folder) or zip file
(Compressed ZIP file) from which the backup is to be restored.
4. Click on the Next button to proceed to the Select Files screen (Figure 12).
Note: The Select Files pane is used to set the criteria by which the Backup Utility
chooses which files from the backup set are to be restored to the live system. See Table 13
for a description of each of the options. See Figure 14 and Table 14 for more details about
the Select Files By Date option.
IMPORTANT: A backup can only be restored to the live system if the
following conditions are met:
The tag database file in the backup system must exactly match
the tag database in the live system.
The selected files from the backup source must not contain
time ranges that overlap or replace any files in the live system.
58
the account selected does not have sufficient permissions for those tasks, the backup
operation will not be able to execute or complete. Enter the full DOMAIN\Username and
enter the Password for the account. You will need to enter the password a second time to
confirm it was typed correctly and to enable the Next button.
7. Click on the Next button.
8. The Summary screen (Figure 33) is displayed which provides a textual summary of the
Restore Backup Operation to complete. If any of the settings need to be changed, the
Back button can be used to go backwards through the Wizard sequence to reach the
appropriate screen where the settings can be changed.
59
Desktop -> Localhost -> OPC Desktop Historian -> Backup Utility
2. Click on the Logging Options item displayed under the Backup Utility node. Figure 34
displays the navigation pane and Logging Options page.
Description
Selecting this checkbox enables general activity logging. If this
checkbox is not selected (i.e., the checkbox is cleared), none of the
fields on the Logging Options page are available.
By default, this checkbox is selected.
Filename
If this field is enabled, allows you to enter a full path for the activity
log file.
Log files for individual backup jobs also appear in this same
60
Command
Description
directory. Individual job logs are named [JobName].log. The
default path is: C:\Program Files\Matrikon\OPC\Desktop
Historian\TaskScheduler\Log\TaskScheduler.log.
If the Enable server activity logging checkbox is not selected
(i.e., the checkbox is cleared), this field is not available.
Browse
Select this button to access the Open window which allows you to
locate and select the necessary log file. The selected file is displayed
in the Filename field.
If enabled, selecting this checkbox ensures that the old log file is
overwritten each time the server starts up. Otherwise, the old log file
is renamed with an underscore (_) prefix.
If the Enable server activity logging checkbox is not selected
(i.e., the checkbox is cleared), this field is not available.
By default, this checkbox is cleared.
Filter String
If this field is enabled, allows you to enter a match string for filtered
log.
If the Enable server activity logging checkbox is not selected
(i.e., the checkbox is cleared), this field is not available.
Filename
If this field is enabled, allows you to enter a full path for the filtered
log file.
If the Enable server activity logging checkbox is not selected
(i.e., the checkbox is cleared), this field is not available.
Browse
Select this button to access the Open window which allows you to
locate and select the necessary log file. The selected file is displayed
in the Filename field.
Apply
Cancel
61
Version
This page is display only and shows OPC product version information.
To view Backup Utility version information:
1. On the navigation pane of the Configuration window, select and expand the following
nodes:
Desktop -> Localhost -> OPC Desktop Historian -> Backup Utility
2. Click on the Version item displayed under the Backup Utility node. Figure 35 displays the
Version page.
62
Lists the data files and provides information about them including the time range of the data
stored within them. By default, all files that are part of the historical data storage are listed.
However, a subset of files may be listed as well.
Ability to copy or move data files to another folder while ensuring that those files cannot be
changed during the copy. Different subsets of data files can be selected based on the time
ranges, and current status of each data file. Data files may also be stored in a compressed
(ZIP) archive file.
Can close and finalize the active data file to allow that file to be included in a backup.
Read header information about a data file or backup zip file or directory.
From the Start Menu, choose Run, and type in the full command line in the resulting box.
From the Start Menu, choose Run, and type in the command cmd and press the Enter
key. This will launch the command interpreter which can then be used to run the backup
tool.
From the Start Menu, choose All Programs -> Accessories -> Command Prompt. This
launches the command interpreter which can then be used to run the backup tool.
General Options
Option
Description
-F
Closes and finalizes the active file. This will allow new data to go into a new
active file, and the current active file will become inactive. This is
recommended for any backup situation where the active file needs to be
backed up.
-V
Verbose logging. This will provide more detailed log messages on the console.
-S selection
Select which files to act on. See Valid Selections for more information.
--FORCE
Forces the move and deletes commands to take files offline without user input.
--OVERWRITE
Allows the Move and Copy commands to overwrite existing files in the
destination folder, or to overwrite an existing zip file.
--CONTINUE
63
Option
Description
files.
--NONINTERACTIVE
This option indicates that the backup utility is being run in the background (by
the task scheduler).
The backup command overwrites files only if --OVERWRITE was specified,
and deletes or move files offline only if the --FORCE option was specified.
Specify a file to which to direct console text. Using the option forces the
--NONINTERACTIVE option to be applied as well. If the specified output file
already exists, it will be overwritten.
--CSV
Causes the L, -RH, -RV and --RESTORE commands to list the information
about each data file in a comma separated values format.
-?, -H
Commands
Only one command may be used at a time.
Command
Description
-L
-C "destination path"
-M "destination path"
Moves selected files to the destination path. Selected files will not be
available in the historian following this command.
Copies selected files to the destination zip file. The destination file should
end in the extension .zip, If it does not, .zip will be added to the end of
the provided name.
Moves selected files to the destination zip file. Selected files will not be
available in the historian following this command. The destination file
should end in the extension .zip, If it does not, .zip will be added to the
end of the provided name.
-U
Unlocks all files. The selection is ignored. This is intended to help recover
from a crash during the backup process.
--DELETE
Deletes selected files. This takes the data off line. This will cause data
loss and is not recommended.
--RESTORE source
Attempts to restore data from a backup. The source may be a single data
file, a backup zip file, or a backup folder. The restore command can only
complete a restore operation if data files do not overlap, and if the tag
database in the backup source (n/a for single data files) matches the tag
database in the live system. A S SELECTION option may be used to
specify which data files in the backup source to restore.
-RH source
Reads and lists the file information for a target zip file or directory. The
S SELECTION option will allow a specific sub set of the files to be
listed. source may be a backup folder, zip file, or single data file.
-RV source
Tests if a target zip file or directory can be restored to the live system.
The S SELECTION option will allow a specific sub set of the files to be
64
Command
Description
listed. source may be a backup folder, zip file, or single data file. If
the test passes, then the same command can be executed again replacing
RV for --RESTORE to run a restore command that can be expected to
work (provided the live system has not changed in such a way to prevent
the restore from succeeding.)
Table 21 - Commands
Valid Selections
Only one selection command may be used.
Command
Description
-S "NONACTIVE"
-S "ALL"
-S "ACTIVE"
-S "<timetype> <timecomp>
<dateexpr>[ AND <dateexpr>][ ACTIVE]"
Selection Examples
All files that start prior to one week before this week began.
-S "STARTS BEFORE WEEK-1W"
65
All files that start some time in the last month. Include the active file if it is in that time range.
-S "STARTS AFTER NOW-1MO ACTIVE"
All files that end more than three full calendar months ago.
-S "ENDS BEFORE MONTH-3MO"
All files last modified during January 2008.
-S "MODIFIED BETWEEN 2008-01-01 00:00 AND 2008-02-01 00:00"
66
Desktop -> Localhost -> OPC Desktop Historian -> Data Collection
Management
2. Click on the Configure item displayed under the Data Collection Management node.
Figure 36 displays the navigation pane and Data Collection Management page.
The Data Collection Management tab consists of the following sections which are described in
more detail below:
Tag Browser
Tag Workspace
Data Collector
67
Tag Browser
The Tag Browser (Figure 37) provides features for locating data servers and items. It provides
both hierarchical and flat browsing to the data server. This simplifies the process of adding tags to
the Tag Workspace. Refer to Adding a Tag for more information about adding tags to Desktop
Historian.
Description
Flat Browse
Browse
Item Display
68
Component
Description
archived.
From the drop-down list, allows you to select a data type that will
be applied to the item if the source items data type cannot be
found, or is not supported by Data Storage.
Advanced
Figure 38 displays the Advanced Tag Options window which is accessed via the Advanced
button on the Tag Browser (Figure 37). The window components are described in Table 24.
69
Component
Description
Timestamp Processing
Select this checkbox to replace the server-provided timestamp
with one from the system clock on the Desktop Historian
computer, for the selected items.
Use System Timestamp
Timestamp Bias
Tag Lifetime
Select this checkbox to enable the Tag Lifetime feature for the
selected tags. Tags using the feature are periodically polled
according to the Lifetime Update Rate when values have not
changed in that time period.
Enable Tag Lifetime
Accept
Cancel
70
Component
Description
Tag Options window.
Table 24 - Advanced Tag Options Window Components
Tag Workspace
The Tag Workspace (identified as Tag Management screen section) contains all tags in Desktop
Historian. Each tag (row) represents a piece of data to be archived. Each tag consists of several
attributes (cells) that include a unique display name, matching data item, and several data update
parameters.
The Tag Workspace can be used to add new tags, remove tags, or modify the update behavior of
a tag.
The Apply button (located in the bottom right corner of the tab) synchronizes Desktop Historian
with the workspace by adding, removing, and modifying tags to match the contents of the
Workspace.
The Cancel button (located in the bottom right corner of the tab) resets the workspace with the
last known configuration. This effectively ignores any changes to the Workspace since the last time
the Apply button was used, or since the tab was opened.
The workspace cells change colour based on the expected action to be performed, and the results
of an action. Refer to Colour Legend for more information.
71
Description
Cuts selected values/rows to clipboard.
Cut
Copy
Paste
Marks all selected tags for deletion. Tags will be deleted with the
Commit button has been pressed.
Unmarks all selected tags for deletion. This may be used after
tags have been marked for deletion, but before the Commit
button has been pressed.
Visible Attributes
Refresh Tags
Refreshes the tag list from the tag database. This will cause all
pending changes to be lost.
Show Legend
72
Description
Cuts selected values/rows to clipboard.
Cut
Copy
Paste
Refreshes the tag list from the tag database. This will cause all
pending changes to be lost.
Legend
Tag Status
The Tag Status (Figure 42) is found at the bottom of the Tag Workspace and displays the
following:
73
Note: When the Data Collector is stopped, the OPC client configuration node will go offline.
Adding a Tag
Tags can be added using the Tag Browser (Figure 37). A data server may provide a list of item
IDs contained in the server. Retrieving this list is referred to as browsing. The Tag Browser can
be used to find and select data items to archive.
To add a tag:
1. In the Tag Browser, enter or select the source data server you want to browse in the
Source OPC Server field.
2. If required, enter a filter string in the Tag Name Filter field.
3. If required, select the Flat Browse checkbox.
Note: Leaving this checkbox cleared will mean that hierarchical browsing will occur rather
than flat browsing. Refer to Figure 37 which shows how the Tag Browser screen section
appears when the Flat Browse checkbox is cleared, and when it is selected.
4. Click on the Browse button. This will retrieve the list of OPC items available in the selected
OPC server.
5. Select the tag or tags you wish to add.
Note: Typical Windows functionality can be used to select multiple items. To select nonadjacent items, select one item and then hold down the CTRL key and click on each
additional item. To select adjacent items, select the first item in the sequence and then hold
down the SHIFT key and click on the last item in the sequence.
6. If required, make changes to the following fields: Enable Archiving of these Tags,
Default Update Rate, Default Data Type.
7. If required, click on the Advanced button.
8. The Advanced Tag Options window (Figure 38) appears.
9. Enable and define the Timestamp Processing and Tag Lifetime options as necessary.
10. Click on the Accept button to close the Advanced Tag Options window and return to the
Tag Browser.
Note: Any changes you made in the Advanced Tag Options window and then accepted
will be reflected in field below the Advanced button in the Tag Browser.
11. Click on the Add Selected Tags button (which is now enabled) to create the new Desktop
Historian tags in the workspace.
Note: The tags are added to MatrikonOPC Desktop Historian immediately after the Add
Selected Tags button is pressed.
74
Removing a Tag
Notes:
Removing a tag from Desktop Historian is an irreversible
event. When a tag is removed, all access to the tags
historical data will be lost. Adding a new tag with the same
name as the previously removed tag will NOT allow access to
previously collected history.
The Mark Tag For Deletion and Unmark Tag For Deletion
menu options are enabled only when rows have been selected.
The tags will not be removed from Desktop Historian until the
Commit button has been selected.
To remove/delete a tag:
1. In the Tag Workspace, highlight the tag or tags you want to remove. Clicking in the item
number column will highlight the required row/tag.
Note: Typical Windows functionality can be used to select multiple items. To select nonadjacent items, select one item and then hold down the CTRL key and click on each
additional item. To select adjacent items, select the first item in the sequence and then hold
down the SHIFT key and click on the last item in the sequence.
2. Right-click your mouse and select the Mark Tag For Deletion option from the displayed
context menu. The tag is now highlighted in red to acknowledge the request.
Or,
Select the Mark Items for Deletion button
Notes:
Once the Mark Items for Deletion button has been selected, the selected tag or
tags appear highlighted in red to acknowledge the request (Figure 44).
If required, you can unmark those tags marked for deletion by selecting Unmark
Tag for Deletion from the context menu, or by selecting the Unmark Items for
Deletion button from the toolbar. For more information refer to Tag Management
Context Menu.
The Mark Tag For Deletion and Unmark Tag For Deletion context menu options
are enabled only when rows have been selected.
75
3. Click on the Commit button. The selected tag or tags are removed.
76
Renaming a Tag
A tags display name can be modified just like any other attribute. For more information, refer to
Changing a Tag Attribute.
Note: Deleting a tag and then creating a new tag with the same name
will not recover old tag data.
To rename a tag:
1. In the Tag Workspace, click in Item Name field you want to change.
2. Make the required name change.
Note: A tags display name MUST be unique. If not, once the
Commit button is selected, the cell is highlighted in yellow to
acknowledge an invalid name and the change will not be applied. In
that case, click on the Cancel button and the cell value will revert back
to its original value.
3. Press Enter on your keyboard, or click your mouse anywhere outside of the changed cell.
4. The display name is now highlighted in blue to acknowledge the request.
5. Click on the Commit button.
6. The changed name is displayed in the workspace.
77
78
Invalid Attributes
Invalid attributes are highlighted in yellow with a red triangle displayed in the top right corner of
the cell, as show in Figure 47. When your cursor is moved over the red triangle, a comment
window is displayed with a detailed explanation of why that particular attribute is invalid.
Note: Tags are updated only once all invalid attribute fields are
corrected.
79
80
Historian, those tags would only record a data point when they are changed. However, some
trending and analysis packages cannot properly display that item as a flat line if its value has not
been updated recently. To accommodate those situations, the following tag attributes have been
added to the application: Tag Lifetime Enabled, Lifetime Update Rate, Lifetime Read
Interface, Use System Timestamp, and Timestamp Bias (Figure 49).
Note: Timestamp Bias and Lifetime Read Interface are not visible by default. Refer to Visible
Attributes for more information.
Figure 49 - Lifetime and Timestamp Processing Attributes (with Lifetime Update Rate Field Options Displayed)
Description
If this checkbox is selected, lifetime processing is enabled. A tag
with lifetime processing enabled will be demand-read from the
OPC server if the lifetime expires without an update from the
data server.
Note: If the tags Update Rate is set to 0 then this setting is
ignored and Lifetime updates will not occur.
The amount of time to wait after the last updated value from the
data server before attempting a demand-read to refresh the tag
value and timestamp.
Clicking on the down arrow displayed on the right side of this
field displays two additional fields:
81
Attribute
Description
Note: MatrikonOPC does not recommend changing this option
unless it is necessary to address known issues and the data
server providing the data.
Timestamp Bias
Notes:
As per all other attributes, changes to those items listed in
Table 27 will take effect only once the Commit button is
selected.
If the configured tag does not have an external source
configured, then configuring Lifetime Processing will have no
effect.
82
83
You also have the option of floating the Tag Browser window by clicking on the Tag Browser
screen section title bar, and dragging it anywhere on the screen (Figure 53). To return the Tag
Browser to its locked-in position, double-click your mouse on the Tag Browser title bar.
84
Visible Attributes
Note: For a detailed list of all attributes, refer to Appendix I Attributes.
When the Tag Workspace is initially displayed, only the attributes for an OPC tag are displayed.
There are two methods by which to display select attributes.
1. First Approach:
a. Right-click your mouse anywhere in the Tag Workspace.
b. From the displayed menu, select the Set Visible Attributes (Shortcut) menu
option (Figure 54).
c. A sub-menu is displayed listing the available attributes. The currently visible
attributes are checked.
d. Click on an attribute to make it visible (checked) or invisible (not checked).
85
2. Second Approach:
The Preferences window can also be used to select which attributes are visible in the Tag
Workspace. This window provides detailed information (Name, Data Type, and Description) for
each attribute and allows you to perform multiple changes at once.
a. Right-click your mouse anywhere in the Tag Workspace.
b. From the displayed menu, select the Set Visible Attributes menu option.
c. The Preferences window (Figure 55) is displayed.
d. Click on an attribute to make it visible (checked) or invisible (not checked).
e. Click on the Apply button to accept the attribute selection, and to close the
Preferences window to return to the Tag Workspace.
86
Colour Legend
The Legend window illustrates the different colours used for different information, including
deleted tags, changed attributes, invalid attributes, etc.
To display the Legend window:
1. Right-click your mouse anywhere in the Tag Workspace.
2. From the displayed menu, select the Legend menu option.
Or,
Click on the Show Legend button on the Tag Management toolbar.
3. The Legend window appears.
87
Alias Configuration
MatrikonOPC servers, including this one, provide the ability to create user-defined aliases that can
be used in place of regular OPC items. This feature is particularly useful when the item path for a
given server is very complex or difficult to remember, for example: Com1.Radio1.Unit1.41.4.123.
Servers can also be configured so that client applications have access to configured aliases only,
rather than every available item.
This section of the manual describes how to create and edit aliases using the Configuration
window.
Note: It is not necessary to define aliases before accessing server data items from an OPC client.
Creating an Alias Group is optional. You can create an Alias without grouping it.
Desktop -> Localhost -> OPC Desktop Historian -> Options -> OPC Server
2. Select the Alias Configuration item displayed under the OPC Server node, and either:
Right-click your mouse on the Alias Configuration item in the navigation pane, and
select New Group from the displayed menu.
88
Select the
Or,
Right-click your mouse on the selected Alias Group in the navigation pane, and select
New Alias from the displayed menu.
2. The Alias Configuration Wizard (Figure 59) appears. The wizard provides the necessary
guidance to create your own Alias.
89
Description
Basic
This Alias type is used to rename an item in this server. Basic Aliases also
provide basic scaling options. Refer to Basic Alias Configuration for more
information.
Calculation
Use this Alias type to define an Alias that is the result of a mathematical
equation involving one or more data items in the server. Refer to
Calculation Alias Configuration for more information.
Holding
Use this Alias type to create a brand new data item not associated with any
item in the server. This type of item is useful for temporary items and
testing. Refer to Holding Alias Configuration for more information.
Table 28 - Alias Configuration Wizard - Alias Type Components
90
Description
Alias Group
Displays the path where the new Alias item will reside once created.
This field is read-only.
Alias Name
Allows you to enter a name for the Alias you are creating. This name
must be unique within the Alias Group.
OPC Tag
Figure 61 shows the Browse OPC Tag window which allows you to browse for tags on existing
OPC servers.
91
Description
Browser
Available Tags
Refresh
Filter
Allows you to filter available tags using a string pattern. For example
*a will display all tags starting with the letter a. Enter a string pattern
in the field to the left of the Filter button. Select the Filter button,
and all applicable tags are listed in the Available Tags screen
section.
OK
Click on this button to confirm the tag you have selected, and to close
the Browse OPC Tag window.
Cancel
Click on this button to cancel your selection and return to the previous
window.
Table 30 - Browse OPC Tag Window Components
Figure 62 shows the Alias Properties configuration step when the Basic Alias configuration option
has been selected.
MatrikonOPC Desktop Historian v4.7.0 Users Manual
92
Description
Data Type
From the drop-down list, allows you to set the value of the OPC item
to the specified type unless Default is selected. Also serves as the
canonical data type for the Alias.
Read-Only
Figure 63 shows the Scaling Algorithm configuration step when the Basic Alias configuration
option has been selected.
93
Description
Allows you to select, from the drop-down list, the required scaling
option for the Alias.
Figure 64 shows the Linear Scaling configuration step when the Basic Alias configuration option
has been selected.
94
Description
Raw High
Raw Low
Scaled High
Scaled Low
Clamp High
Clamp the scaled value at the high limit to prevent it from going out
of range.
Clamp Low
Clamp the scaled value at the low limit to prevent it from going out
of range.
Table 33 - Alias Configuration Wizard - Step 4: Scaling Algorithms (Linear Scaling)
Figure 65 shows the Square Root Scaling configuration step when the Basic Alias configuration
option has been selected.
95
Figure 65 - Alias Configuration Wizard - Step 4: Scaling Algorithms (Square Root Scaling)
Description
Raw High
Raw Low
Scaled High
Scaled Low
Clamp High
Clamp the scaled value at the high limit to prevent it from going out
of range.
Clamp Low
Clamp the scaled value at the low limit to prevent it from going out
of range.
Table 34 - Alias Configuration Wizard - Step 4: Scaling Algorithms (Square Root Scaling) Components
Figure 66 shows the Gain/Offset configuration step when the Basic Alias configuration option has
been selected.
96
Description
Gain
Offset
Scaling offset.
Table 35 - Alias Configuration Wizard - Step 4: Scaling Algorithms (Gain/Offset Scaling) Components
Figure 67 shows the Expression Scaling configuration step when the Basic Alias configuration
option has been selected.
97
Description
Input
Simple text equation to apply to incoming values (reads). Click on the Editor button
to display the Expression Wizard screen used to help build a formula. For more
information, refer to the Expression Wizard section in this manual.
Output
Simple text equation to apply to outgoing values (writes). Click on the Editor button
to display the Expression Wizard screen used to help build a formula. For more
information, refer to the Expression Wizard section in this manual.
Table 36 - Alias Configuration Wizard - Step 4: Scaling Algorithms (Expression Scaling) Components
Figure 68 shows the Expression Wizard that is used to configure the input and output
expressions.
Notes:
The Expression Wizard appears and functions the same for an input expression as it does
for an output expression. The differences being the expression field label: Input
Expression, Output Expression, and that one is for reads and the other for writes.
If you are expecting to read a particular alias, create an Input Expression. If you are
expecting to write to a particular alias, create an Output Expression.
Please refer to the Expression Wizard section in this Users Manual for examples.
98
Description
Input/Output
Expression
Displays the expression as it is created. This field is free-form which allows you to
manually enter or edit information. This field reads Input Expression when
creating an input or read expression. It reads Output Expression when
creating an output or write expression.
Function
Select this button to display the Select Function window which allows you to
select the necessary function from those available.
Variable
Select this button to display the Select Variable window which allows you to
select the necessary variable from those available.
Operators
Select the applicable button to add the corresponding operator or operators to the
expression.
Clear
OK
Select this button to accept changes to (or the creation of) the expression.
Cancel
Select this button to discard changes to (or abandon the creation of) the
expression.
Table 37 - Expression Wizard Components
99
Description
Category
Displays the available categories for selection. Allows you to select the
required category.
Available Functions
Continue
Select this button to accept the selections made and return to the
initial Expression Wizard window.
Cancel
Select this button to disregard the selections made and return to the
initial Expression Wizard window.
Table 38 - Select Function Window Components
100
Description
Select variable
Displays the available variables for selection. Allows you to select the
required variable.
OK
Select this button to accept the selection made and return to the
initial Expression Wizard window.
Cancel
Select this button to disregard the selection made and return to the
initial Expression Wizard window.
Table 39 - Select Variable Window Components
Table 40 describes the components of Alias Identity step when the Calculation Alias
configuration option has been selected.
Component
Description
Alias Group
Displays the path where the new Alias item will reside once created. This field
is read-only.
Alias Name
Allows you to enter a name for the Alias you are creating. This name must be
unique within the Alias Group.
Table 40 - Alias Configuration Wizard - Step 2: Alias Identity Components
101
Figure 72 shows the Alias Properties configuration step when the Calculation Alias configuration
option has been selected.
Description
Data Type
From the drop-down list, allows you to set the value of the OPC item
to the specified type unless Default is selected. Also serves as the
canonical data type for the Alias.
Figure 73 shows the Alias Calculation configuration step when the Calculation Alias
configuration option has been selected.
102
Description
Alias Calculation
Select this button to display the Insert OPC Tag window (i.e., Tag
Browser Figure 61) allowing you to insert OPC tags as part of the
calculation formula.
Insert Function
Figure 74 shows the Alias Events configuration step when the Calculation Alias configuration has
been selected.
103
Description
When this checkbox is selected, Alias events are enabled for this
Alias item.
Source
Severity
Category
Allows you to select, from the drop-down list, the event category
under which the event is to be registered.
Manage Categories
Trigger Condition
Allows you to select, from the drop-down list, how the Alias event is
to be triggered: Value Change, Positive Edge.
Timestamp Source
Message
104
Component
Insert OPC Tag
Description
Select this button to display the Browse OPC Tag window (Figure
61) which is used to add item paths to this field.
Table 43 - Alias Configuration Wizard - Alias Events Components
Description
Select this button to access the New Event Category window (Figure 76) and
create a new category.
Select this button to edit the currently selected category.
Edit
Note: This button is available only if at least one event category has been created
and selected.
Select this button to delete the selected category.
Delete
Close
Note: This button is available only if at least one event category has been created
and selected.
Select this button to close the Manage Event Categories window and return to
Step 5 of the Alias Configuration Wizard.
Table 44 - Manage Event Categories Window Components
105
Description
Category ID
Name
Description
106
Table 46 describes the components of Step 2: Alias Identity when the Holding Alias
configuration option has been selected.
Component
Description
Alias Group
Displays the path where the new Alias item will reside once created.
This field is read-only.
Alias Name
Allows you to enter a name for the Alias you are creating. This name
must be unique within the Alias Group.
Table 46 - Alias Configuration Wizard - Step 2: Alias Identity Components
Figure 78 shows the Alias Properties configuration when the Holding Alias configuration option
has been selected.
107
Description
Data Type
From the drop-down list, allows you to set the value of the OPC item
to the specified type unless Default is selected. Also serves as the
canonical data type for the Alias.
Read-only
Default Value
Editing Aliases
To edit an Alias:
1. From the Alias Configuration panel, select the Alias item you wish to edit.
2. Click on the
Or,
button.
108
Removing Aliases
Note: Any Alias that was created can be removed.
To remove an Alias:
1. From the Alias Configuration panel, select one or more Aliases you wish to remove.
2. Click on the
Or,
button.
Deleting an Alias Group removes that group and all of its contents (i.e., Aliases).
button.
109
Cloning Aliases
To clone an Alias:
1. From the Alias Configuration panel, select the Alias that you wish to clone.
2. Click on the
button.
Or,
Select Clone from the Edit menu.
Or,
Right-click your mouse on the Alias you wish to clone, and select Clone from the displayed
menu.
3. The Alias Configuration Wizard appears.
4. By default, the Alias Name will be the name of the selected Alias item with a number
appended in parentheses. For example, Alias_003 (1).
5. Configure the cloned Alias, as required.
6. Click on the Finish button when you have completed the configuration.
Exporting Aliases
Note: Use the Export Alias File window to export all currently configured Aliases to a CSV file.
To export all currently configured Aliases:
1. From the navigation pane, select the Alias Configuration node.
2. Click on the
Or,
button.
From the File menu, select the Export To CSV menu option.
Or,
Right-click your mouse and select the Export To CSV option from the displayed menu.
3. The Export Alias File window appears.
4. Enter a file name for the CSV export file and specify a location for it.
5. Click Save.
6. The Aliases are exported.
Importing Aliases
Note: Use the Import Alias File window to clear all Aliases and import new ones from a CSV file.
To import Aliases from a CSV file:
1. From the navigation pane, select the Alias Configuration node, and either:
Click on the
Or,
button.
110
From the File menu, select the Import To CSV menu option.
Or,
Right-click your mouse and select the Import To CSV option from the displayed menu.
2. The Import Alias File window appears.
3. Browse to the required CSV file name.
4. Click Open.
5. The previous Aliases are cleared and the new ones are imported.
Expression Wizard
The Expression form of scaling uses an Expression Wizard to build formulas. The created
formula is a simple text equation that is applied to either incoming values (i.e., reads), or outgoing
values (i.e., writes).
Examples
Example 1:
The following turns any number into a Boolean value. Any non-zero value shows up as a 1.
IF(INPUT = 0,0,1)
OUTPUT
Example 2:
The following takes the text out of SAMPLE and converts it to ON. All other values show as OFF. If
OUTPUT is specified in the Output field, then the value is transferred to the end OPC item. Using
this alias, you can write SAMPLE or any other value to the Alias to get the display to changed from
OFF to ON.
String comparisons are case-sensitive.
IF(INPUT = SAMPLE,ON,OFF)
OUTPUT
Table 48 describes the Expression Wizard fields.
Component
Description
Input/Output Expression
Function
Select this button to display the Select Function window which allows
you to select the necessary function from those available.
Variable
Select this button to display the Select variable window which allows
you to select the necessary variable from those available.
Operators
Clear
OK
Select this button to accept changes to (or the creation of) the
111
Component
Description
expression.
Select this button to discard changes to (or abandon the creation of) the
expression.
Cancel
Notes:
The Expression Wizard appears and functions the same for an input expression as it does
for an output expression. The differences being the expression field label: Input
Expression, Output Expression, and that one is for reads and the other for writes.
If you are expecting to read a particular Alias, create an Input Expression. If you are
expecting to write to a particular Alias, create an Output Expression.
112
6. The Operators buttons (Figure 80) allow you to enter an operation descriptor based on the
selected button.
7. Click on the OK button on the Expression Wizard screen to close the wizard and display
the expression in either the Input or Output field, depending on which expression you
defined.
Logging Options
The Logging Options page allows you to customize the way error and debug information is
recorded by the server.
Note: Logging Options settings are saved once the Apply button is
selected. However, they do not take effect until the back-end server is
re-started.
To view logging options:
1. On the navigation pane of the Configuration window, select and expand the following
nodes:
Desktop -> Localhost -> OPC Desktop Historian -> Options -> OPC Server
2. Click on the Logging Options item displayed under the OPC Server node. Figure 81
displays the navigation pane and Logging Options page.
113
Description
Selecting this checkbox enables general activity logging. If this
checkbox is not selected (i.e., the checkbox is cleared), none of the
fields on the Logging Options page are available.
By default, this checkbox is selected.
Filename
If this field is enabled, allows you to enter a full path for the activity
log file. The default path is: C:\Program Files\Common
Files\MatrikonOPC\Common\
PSTCFGMatrikon.OPC.DesktopHistorian.1.log.
If the Enable server activity logging checkbox is not selected
(i.e., the checkbox is cleared), this field is not available.
Browse
Select this button to access the Open window which allows you to
locate and select the necessary log file. The selected file is dislayed
in the Filename field.
If enabled, selecting this checkbox ensures that the old log file is
overwritten each time the server starts up. Otherwise, the old log file
is renamed with an underscore (_) prefix.
If the Enable server activity logging checkbox is not selected
(i.e., the checkbox is cleared), this field is not available.
By default, this checkbox is cleared.
114
Command
Description
Filter String
If this field is enabled, allows you to enter a match string for filtered
log.
If the Enable server activity logging checkbox is not selected
(i.e., the checkbox is cleared), this field is not available.
If this field is enabled, allows you to enter a full path for the filtered
log file.
Filename
Browse
Select this button to access the Open window which allows you to
locate and select the required filtered log file. The selected file is
dislayed in the Filename field.
Apply
Cancel
Version
This page is display only and shows OPC server version information.
To view OPC server version information:
1. On the navigation pane of the Configuration window, select and expand the following
nodes:
Desktop -> Localhost -> OPC Desktop Historian -> Options -> OPC Server
2. Click on the Version item displayed under the OPC Server node. Figure 82 displays the
Version page.
115
Server Options
Note: Server Options settings take effect only once the Apply
button is selected.
Desktop -> Localhost -> OPC Desktop Historian -> Options -> OPC Server ->
Server Options
2. Click on the Configure item displayed under the Server Options node. Figure 83 displays
the navigation pane and Server Options page.
116
Description
Allows you to set a maximum number of values that can be returned
from an HDA ReadRaw request. If an HDA client makes a request
which exceeds this value, then no data is returned and the client
receives an error code indicating that they exceeded the servers
limit. Setting this value to 0 means that no limit is enforced on the
number of items returned.
Default value = 0.
Notes:
117
Command
Description
When an aggregate calculation is performed the server performs a
ReadRaw operation internally to gather the data needed to perform
the calculation. This option modifies the time span of this ReadRaw
call. If this option is 0, then the ReadRaw call uses the start and end
times from the ReadProcessed call. If this option is non-zero then the
time extends the start and end times of the ReadRaw call by the
number of intervals configured.
An interval is defined as the interval requested in the ReadProcessed
call. See the example below for further explanation.
Default value = 0.
Aggregate Overread
Cancel
Use this button to discard any changes made on the Server Options
page.
Table 50 - Server Options Page Components
118
Logging Settings
Desktop -> Localhost -> OPC Desktop Historian -> Options -> OPC Client
2. Click on the Configure item displayed under the OPC Client node. Figure 84 displays the
navigation pane and OPC Client Configuration page with the Client Settings tab
selected.
Client Settings tab variables (i.e., fields) and functions are described in Table 51.
119
Command
Description
The Data Buffer Settings manage how the OPC client will buffer the received data before sending
it to the core. The OPC client will first store data (buffer) in the memory. When the amount of
buffered data in memory exceeds certain limits, the OPC client will start buffering data in files. All
of these operations are transparent to the user, but you can customize how much data is to be
buffered in memory and in the data files.
The Data Buffer Settings variables and functions are described in Table 52.
Command
Description
Allows you to enter the directory where the data files will be created.
By default, this directory is: C:\Program Files\Matrikon\OPC\Desktop
Historian\OPC Client\Data Buffer\.
Allows you to enter the maximum file size (in MB) for each file. By
default, this value is 25 MB.
Apply
Use this button to commit any changes made on the Client Settings
tab.
Cancel
Use this button to discard any changes made on the Client Settings
tab.
Table 52 - Client Settings (Data Buffer Settings) Tab Components
120
The Logging Settings tab variables (i.e., fields) and functions are described in Table 53.
Command
Log file directory
Description
Displays the log file directory (read-only).
Allows you to select from the drop-down list, the amount of detail to
provide in the log file:
Log level
None
Low Errors (default setting)
Medium Errors and Warnings
High Errors, Warnings, and Information
Default = Low.
Allows you to define the maximum size of the log file (in MB). Once
this size is reached, the oldest data in the file is erased at the same
rate that new information is written to the log file. This value will be
ignored if Forced writing is activated.
Apply
Cancel
121
Version
This page is display only and shows OPC client version information.
To view OPC client version information:
1. On the navigation pane of the Configuration window, select and expand the following
nodes:
Desktop -> Localhost -> OPC Desktop Historian -> Options -> OPC Client
2. Click on the Version item displayed under the OPC Client node. Figure 82 displays the
Version page.
122
FileCollector
FileCollector is an OPC client that transfers historical process data from a Comma Separated Value
(CSV) file to the MatrikonOPC Desktop Historian via OPC HDA. This product will monitor a specified
directory for the new CSV files. If a CSV file is found, this product will read the data and transfer it
to the Desktop Historian. Depending on the configuration, the process file will either be deleted, or
moved to a back-up directory.
For more information about the FileCollector component, refer to the MatrikonOPC FileCollector
Users Manual.
123
ODBC Server
The ODBC Server component allows ODBC clients to read data from Desktop Historian. You may
configure the ODBC server and view the applicable version information.
To access the Matrikon ODBC Server for OPC page:
1. From the main Configuration window, select and expand the following nodes:
Databases
General
Databases Tab
The Databases tab is shown in Figure 87 and the components are described in Table 54.
Command
Description
Name
Description
Allows you to specify the host where the OPC HDA server resides.
Allows you to specify the OPC HDA server program ID for the database.
124
Command
Description
New
Delete
Select this button to remove the selected database from the list on the
left side of the page.
Apply
Refresh
Select this button to refresh the Databases tab, clearing the fields in
the Database Configuration panel.
Note: Although the fields are cleared, no saved information is lost.
Table 54 - Databases Tab Components
125
Removing a Database
To remove/delete an existing database:
1. From the main Configuration window, select and expand the following nodes:
Right-click your mouse on the database you want to remove and select Delete from
the displayed menu.
Or,
General Tab
The General tab is shown in Figure 89 and the components are described in Table 55.
126
Command
Description
Disconnect Delay
Allows you to specify the amount of time (in seconds) the OPC server
remains running after all clients have disconnected.
Allows you to enter the directory of the log file, or accept the default
directory.
Log Level
Allows you to specify the amount of detail to be provided in the log file:
None, Low, Medium, or High.
Log Size
Apply
Refresh
Version
This page is display only and shows ODBC server version information.
To view ODBC server version information:
1. On the navigation pane of the Configuration window, select and expand the following
nodes:
2. Click on the Version item displayed under the ODBC Server node. Figure 90 displays the
Version page.
MatrikonOPC Desktop Historian v4.7.0 Users Manual
127
128
3. From the Excel Tools menu, select the Add-Ins menu option. The Add-Ins window
appears.
4. From the Add-Ins window, click on the Browse button. The Browse window appears.
5. In the Browse window, navigate to [C:\Program Files\Matrikon\OPC\]Desktop
Historian\Utils.
Note: [ ] indicates the default installation path.
6. Click on the TagMgr.xll file.
7. The entry Matrikon Desktop Historian Tag Manager should now appear selected in
the list of add-ins. Click on the OK button to close the dialog box.
129
Loading Attributes
To load tag attributes:
Note: Use the new Excel work book you created in the previous procedure (Connecting to Tag
Manager).
1. From the Excel Desktop Historian menu, select the Load Attributes menu option.
2. The default OPC tag attributes are loaded into the Excel worksheet and the following
columns are displayed: Action, Attr Name, Data Type, and Description.
130
Renaming an Attribute
To rename a tag attribute:
1. Using the Excel worksheet, in the Attr Name column, select the name you want to change.
2. In the Action column, type MOD next to the name to be changed.
3. In the Excel formula bar, type REN before the existing name, place quotation marks
around the existing name, add a space and type in the new name surrounded by quotation
marks. For example, REN Existing Name New Name.
4. Click your mouse anywhere outside of the row.
5. From the Excel Desktop Historian menu, select the Commit Changes menu option.
6. A message appears stating that all changes were committed successfully.
7. Click on the OK button.
8. From the Excel Desktop Historian menu, select the Load Tags menu option.
9. The Load Tags window appears listing all selected tags (refer to Figure 92).
131
10. Click on the OK button to add all tags and tag attributes.
11. The worksheet refreshes and the change is displayed.
Filtering Tags
Note: Data Type and Name filters may be combined.
To filter tags by name:
1. On the Load Tags window, in the Name Filter field, enter the tag name (or part of tag
name) that you want to match. Use an asterisk as a wildcard character.
And/or,
MatrikonOPC Desktop Historian v4.7.0 Users Manual
132
In the Data Type Filter field, from the drop-down list, select the data type to which you
want to match tags.
2. Click on the OK button.
3. Those tags that meet the filter specification are loaded into an Excel worksheet.
6. Expand the navigation tree in the left pane to display the available tags.
133
7. In the pane on the right side of the window, double-click your mouse on the tag you want to
add. The tag is added to the Excel worksheet.
Note: Tags can also be added by right-clicking your mouse on the tag you want to add and
selecting Add Selected from the menu that appears. This is particularly useful when adding
multiple tags.
8. From the Excel Desktop Historian menu, select the Commit Changes menu option.
9. A message appears stating that all changes were committed successfully.
10. Click on the OK button.
134
Renaming a Tag
To rename a tag:
1. Using the Excel spreadsheet, load the tags present in Desktop Historian.
2. In the Action column, type MOD next to the name to be changed.
3. In the Tag Name column, type REN before the existing name, place quotation marks
around the existing name, add a space and type in the new name surrounded by quotation
marks. For example, REN Existing Name New Name.
4. From the Excel Desktop Historian menu, select the Commit Changes menu option.
5. A message appears stating that all changes were committed successfully.
6. Click on the OK button.
135
Diagnostics
The server supplies diagnostic information to assist operators and support personnel with
troubleshooting communication problems and software faults.
Logging
All MatrikonOPC servers produce log files that record errors and debugging information. The log
files can be extremely valuable for troubleshooting. As such, it is important to note that the default
log level is set to low. The General Logging tab on the Options window in the main configuration
screen contains settings to control server logging.
General Activity Logging records information about the internal workings of the OPC server. It is
useful for troubleshooting problems with configuration and device communication. Interface
Activity Logging records information about the client/server OPC communication. It is useful for
troubleshooting compliance issues.
For General logging, the higher the log level, the more information that is recorded. However,
server performance may decrease at higher log levels. The recommended operating level is
Medium. More log levels are available for both types of logging which record more detailed
information, as well as the ability to output log statements to a console window at run time.
Contact MatrikonOPC support for further instructions on how to enable the higher log levels and
console logging.
For Interface logging, the log level can be considered very high and therefore should never be used
during normal operation of the OPC server unless specifically working on problems related to
interfacing.
MatrikonOPC Sniffer is a useful tool for logging OPC client/server communication. It enhances
the Interface Activity Logging by recording the client-side transactions. It can also be used with
other OPC servers. MatrikonOPC Sniffer is a utility used to troubleshoot OPC client/server
interoperability issues. Contact the MatrikonOPC Sales department for further information about
this product, or use the following link to access the MatrikonOPC Sniffer Download.
In general, the server logs all errors and other information of immediate importance to the user at
the low detail level, all warnings and other information of moderate importance to the user at a
medium detail level, and additional information concerning the normal functioning of the software
at a high detail level. The server also logs further information of concern to support personnel at
the debug log level.
Note: The higher the log level, the slower the performance of the
server. It is recommended that the log level be left at the default,
unless troubleshooting needs to be performed.
136
Limitations
MatrikonOPC Desktop Historian has the following limitations:
1. Microsoft Windows NT is not supported if running MatrikonOPC Desktop Historian on
the Windows NT operating system, users will experience problems while adding, changing,
and removing tags.
2. MatrikonOPC Performance Monitor, File Collector and ODBC server - currently not
supported on Windows 7 and Windows 2008.
3. Array data type is not supported MatrikonOPC Desktop Historian does not support
storing tags of Array data type. However, it is possible to store individual elements. To store
an element of an array tag, please refer to Configuring Array Elements.
4. String data type is not supported in FF4 storage format.
5. Insert/Replace is not supported in FF7R and FF4 storage formats. All data insertions
must be done using the Insert method call.
6. Maximum string length supported in FF7 storage format is 2,033 if the input string
length is longer than 2,033, the string will be truncated before being stored.
7. Storage format FF7 will not store data properly when the DAT file size exceeds 4
gigabytes (232 bytes). In the Data Storage Management window, the Store no more
than xxx minutes of history in each file option must be set to prevent the DAT file from
exceeding this size, and leave at least 10 percent for overhead. For example, with 5,000
tags at a 1 second update rate, this configuration setting should be set to no more than 420
minutes (7 hours) of history in all file.
Total file size = 15 [bytes/value] * 5000[values/second] * 60[seconds/minute] *
420[minutes] * 1.1 [overhead factor of 10%] < 232 [bytes]
Refer to Appendix H File Formats of the Users Manual for specific size requirement of
storage format FF7.
8. FF7R size limits not strictly enforced - the 25MB file size is not strictly enforced. If data
is written to Desktop Historian that is older than the latest data written (i.e., back filling),
then the data files may grow to exceed the target 25 MB. If the .DAT file size is greater than
3.5 GB, or the data point time stamp is too far in the future when compared to the (latest
time stamp + configured offset time), the data is rejected and recorded in a .CSV file for
future use. The .CSV file location is C:\matrikon data\Exempt_FF7R.
9. Pasting large number of rows into tag configuration - the configuration tools Tag
Management screen does not work properly when pasting large number of rows into the
tag configuration.
Workaround: Paste the desired rows in smaller batches, or use the Excel plug-in to
configure large numbers of tags.
10. Scheduled backups with concurrent execution times if multiple backups are
scheduled to run concurrently, it is possible that some of these backups will not execute.
11. Scheduled backups during Desktop Historian upgrade if any backups are scheduled
to take place while an upgrade to a newer version of Desktop Historian is performed, it is
possible that some of these backups will not execute.
12. Maximum Return Values does not avoid all load issues - this limit is not enforced for
browsing operations. It is only enforced for the number of data points returned to the OPC
HDA client making the read request. The number of data points retrieved in internal Read
MatrikonOPC Desktop Historian v4.7.0 Users Manual
137
Raw operations (performed to gather the data needed to make aggregate calculations) is
not limited unless the Apply Maximum Return Values to Processed Reads option is
enabled. In that case, the limit applies to the underlying request for raw data necessary to
compute the requested aggregate. Therefore, load issues can still occur when a Maximum
Return Values limit is in place.
13. Restore functionality - a backup can only be restored to the live system if the following
conditions are met:
The tag database file in the backup system must exactly match the tag database in
the live system.
The selected files from the backup source must not contain time ranges that overlap
or replace any files in the live system.
14. Communication failure - if communication failure occurs with a source OPC server,
Desktop Historian records a bad quality point in history. When communication is reestablished, Desktop Historian does not record a good quality point until the point value at
the data source changes.
Workaround: Enabling the lifetime functionality for tags that rarely change prevents
points from appearing bad in history for extended periods.
Refer to the MatrikonOPC Desktop Historian Release Notes for known issues.
138
Troubleshooting
This section is intended to assist you by providing licensing information and MatrikonOPC
Support contact information. Also addressed here are some of the most common problems
encountered, and questions asked, while using this OPC server. Please check the following
Problems/Solutions and Questions/Answers sections before contacting the MatrikonOPC
Support team.
Solution:
The OPC server is licensed with a hardware or software key, and the demonstration
period for the server has expired.
A third-party OPC client does not provide a means to configure access paths, making it
difficult to correctly specify the data acquisition options for the items.
Solution:
The server provides a global parameter for configuring an escape character to allow
users to append communication options to the end of an Item ID to accommodate
those clients that do not support access paths.
Perform the following steps:
1. Create a string value named ItemIDEscapeCharacter in the following
location: HKEY_CLASSES_ROOT\CLSID\{20DE4721-17CD-4912-AD78B3702370B733}\Options.
2. To create a new value, select the Options key and then choose New String
Value from the Edit menu.
3. Set the value of ItemIDEscapeCharacter entry a single character such as |
(pipe).
4. To edit the value, select the entry and choose Modify from the Edit menu.
5. Shut down the server and restart it for the change to take effect.
6. Configure the ItemIDEscapeCharacter Item ID in the OPC Client with the
access path appended to the end with the configured escape character (e.g.,
ITEMID|ACCESSPATH).
More than one HASP attached to parallel port, but only first one is recognized
Problem:
There is more than one HASP hardware key from MatrikonOPC attached to the parallel
port, but the software only recognizes the first one.
Solution:
HASP keys from the same vendor cannot be chained together. Contact your Account
Manager to obtain a HASP key containing the combined codes of all installed
139
MatrikonOPC servers.
OPC server does not show up as local program in OPC client application
Problem:
The OPC server does not show up in a list of locally available program IDs in a thirdparty OPC client application.
Solution:
Make certain that a user with local administrative rights installs the OPC server so that
it can create the necessary entries in the registry.
Also, particularly for older OPC clients that do not use the OPC Server Browser, make
certain that the client is running as a user that has Read access to the registry.
In addition, make sure that Microsoft Execution Prevention (DEP) is not on during
installation.
None of the OPC servers shows up in a list of locally available program IDs under ODH.
Solution:
Make sure that a user with local administrative rights installs ODH so that it can
create the necessary entries in the registry.
Ensure OPCEnum is registered as a service, DCOM permissions are configured
properly, and the OPCEnum service is running.
If OPCEnum is not running as a service, perform the following steps:
1. Open Command Prompt with Administrator Rights.
2. Go to Windows directory by below command
cd C:\Windows\System32 -for 32 bit operating systems
Or,
cd C:\Windows\SysWOW64 - for 64 bit Operating Systems.
3. Type command in following order:
OpcEnum.exe /unregserver
OpcEnum.exe /regserver
OpcEnum.exe /service
4. Start the OpcEnum service from Service Manager.
The OPC server does not report any new data for tags that should be updating.
140
Solution:
Check that the Data Collector (Desktop Historian OPC Client Service) has been started,
and that the Archiving attribute for the tags of interest is set to True, or
There may be a problem with either the tag configuration, or communication to the
OPC server. Both of these conditions will be reported in the OPC client log file. This
may include incorrect parameters (such as invalid Item IDs, or an unknown OPC
Server Program ID), as well as communication failure codes (such as a failure to
connect to a remote OPC server), or
If an OPC server is not active when the OPC client attempts to connect, the OPC server
may not have sufficient time to configure itself for proper use. To avoid this, the OPC
client has the ability to pause during the connection operation at several stages and
retry communication if a full or partial communication failure is encountered. Contact
MatrikonOPC Support for instructions on customizing the connection behavior of the
OPC client.
An Unknown error message appears when setting the FF4 file format in the Data
Storage Management window.
Solution:
One of the possible reasons for getting this error message is because there is not
enough disk space for the number of files you specified. If you have specified the
history is to be stored in 1,000 25 MB files, make sure you have at least 25G of disk
space free.
Installation stops and an error message indicating that a Microsoft update is not
present, is displayed.
Solution:
The installation stops as it cannot find the necessary Microsoft hotfixes. Install the
KB973687-64 and msxml6_x64.msi updates from the Microsoft website and then
install ODH again.
Solution:
When using the Pi OPC client with MatrikonOPC servers, please go into the OPC server
Advanced Options setting and select the Enable Mass Tag Adding checkbox. This
causes Pi to validate and add all tags in one group at a time rather than one tag at a
time, resulting in significant improvements in time and network bandwidth used when
initializing. Although this is highly recommended with any MatrikonOPC server, the
difference is most noticeable when using products such as MatrikonOPC SCADA servers
and Tunneller where each OPC operation has a high latency.
141
Question:
How is the OPC HDA ReadProcessed INTERP Aggregate function implemented in the
MatrikonOPC Server for Desktop Historian?
Answer:
This varies depending on whether the stepped attribute for a particular item is set to
True or False within Desktop Historian. In the case where the stepped attribute for
an item is set to True, stepped interpolation is used between data points. In the case
where the stepped attribute for an item is set to False, linear interpolation is used
between data points. In both cases, stepped extrapolation is used at end boundary
conditions.
Answer:
MatrikonOPC Desktop Historian includes a Tag Manager that allows you to add, change
or delete tags in Excel. Refer to the Tag Manager Excel Plug-In section in this
manual for more information.
Lifetime Enabled tags do not receive new timestamps at every lifetime interval
Question:
Answer:
Tags that are configured to use the Lifetime feature must have the Use System
Timestamp option configured properly for the system that is being read from.
If Use System Timestamp is disabled then MatrikonOPC Desktop Historian will
always use the timestamp that is provided by the OPC Server that is providing the
data. This behavior is desirable if the data source updates its timestamps frequently
but does not send new data to MatrikonOPC Desktop Historian unless the value
changes.
If Use System Timestamp is enabled then MatrikonOPC Desktop Historian will use
the current time from the computer on which it is installed to timestamp all data
points that are read for the configured tag. This is the desired setting when using
Lifetime configuration on tags that do not get updated timestamps on the OPC server.
Search the MatrikonOPC Support Knowledge Base at www.opcsupport.com to find the answers
to other commonly-asked MatrikonOPC Desktop Historian questions.
Licensing
Most MatrikonOPC products require that some form of licensing criteria be met for it to function
correctly. A license is required to enable the servers functionality.
The MatrikonOPC Desktop Historian supports both software and hardware licensing.
142
IMPORTANT TO NOTE:
The following licensing information is described in detail within the
Licensing Procedures document which accompanies the MatrikonOPC
Desktop Historian software and Users Manual:
De-licensing software.
Licensing ODBC Server for OPC, Matrikon Analytics Excel Reporter, and
Performance Monitor
A 30-day demo license for MatrikonOPC ODBC Server for OPC is included in the MatrikonOPC
Desktop Historian installation.
Note: The demo license is a time-limited license. The product is fully functioning until the demo
period has expired, after which it will cease to function. A permanent MatrikonOPC ODBC Server for
OPC license is not included with MatrikonOPC Desktop Historian and must be purchased
separately. Contact your Account Manager for assistance and more information.
During the installation of MatrikonOPC Desktop Historian, you are given the option of installing a
demonstration version of MatrikonOPC Performance Monitor, and/or Matrikon Analytics Excel
Reporter, and/or MatrikonOPC Trender. If a permanent license is required, contact your Account
Manager for more information.
Feature Licenses
Featured Component
Default License
State
30-Day Demo
30-Day Demo
Security
30-Day Demo
143
30-Day Demo
30-Day Demo
MatrikonOPC Trender
30-Day Demo
Table 56 - Feature Licenses
Note: MatrikonOPC Desktop Historian, Security, Performance Monitor, Excel Reporter, and Trender
need to be licensed separately, and by default, are delivered with only a 30-day demo. To purchase
a full license for any or all components, please contact your MatrikonOPC Account Manager.
Contacting Support
The MatrikonOPC Customer Services department (www.opcsupport.com) is available 24 hours a
day, seven days a week.
Contact MatrikonOPC Support using the information below, or send an email
(support@MatrikonOPC.com).
For Monday to Friday daytime support requests, contact MatrikonOPC Support using the regional
phone numbers provided in Table 57.
Region
Office Hours
North America
8:00 am-5:00 pm
9:00 am-5:00 pm
9:00 am-5:00 pm
Contact Information
+1-877-OPC-4-ALL
+49-221-969-77-0
(Request OPC Support)
+61-2-4908-2198
(Request OPC Support)
For after-hours support in all regions, please use the following number. There is no extra charge
from MatrikonOPC for calling their after-hours support number.
Region
All
Contact Information
+1-780-231-9480
144
Appendix A
DCOM is an object protocol that enables COM components (such as OPC clients and servers) to
communicate directly with each other across a network. A certain amount of configuration is
required on the system where the OPC server is installed to allow remote clients to connect to it
over the network.
Readers should be familiar with DCOM and with Windows 2000 security features and security
administration. Information regarding Distributed COM and various links to related sites, white
papers, specifications, and so on, can be found at
http://www.microsoft.com/com/default.mspx.
Notes:
The following steps are suggestions only. Ask your Windows
Network Administrator for more information about the settings
that you should use, especially between different domains.
The steps provided in this appendix apply to Windows NT
operating systems only. For information on how to configure
DCOM settings for newer Windows operating systems, please
refer to the MatrikonOPC Online Support page on DCOM
Settings.
Default Properties
The Default Properties tab contains settings that affect all DCOM communication on the machine.
First of all, ensure that the Enable Distributed COM on this computer is selected in
so that the machine is available to others via DCOM.
Select the Enable COM Internet Services on this computer to allow DCOM access to
the machine from the Internet (check with your administrator).
In general, the other settings do not need to be changed.
The Authentication Level specifies when COM should authenticate the identity of calling clients
(each call, each packet, etc).
Normally, it should be set to Connect, indicating that COM should authenticate clients
when they first connect to a server. If it is set to None, then COM performs no
authentication and ignores any access permission settings.
145
The Impersonation Level specifies whether servers can ascertain the identity of calling clients
and whether they can then perform operations on the client's behalf (as if the server is the client).
Normally, it should be set to Identify, allowing the server to identify the calling client to
see if it is allowed access to a certain resource but not to actually access any of these
resources as the client.
Select the Provide additional security for reference tracking to make even the
reference counting on COM objects secure. This setting is not generally required.
Security Permissions
The most important DCOM settings for an OPC server are the security permissions. There are two
ways for you to set these:
1. Change the specific settings for the server (recommended).
2. Change the default settings (not recommended) and make sure that the OPC server will use
these.
Either way, be certain that the access and launch permissions are correct for the server.
146
4. Click on the Security tab to set the security for the server.
5. The Distributed COM Configuration Security tab (Figure 95) appears.
147
Notes:
The Access Permissions contain an Access Control List of principals that are
allowed to interact with objects supplied by a server.
The Launch Permissions contain an Access Control List of principals that are
allowed to start up a server process or service.
6. Include the names of users or user groups from trusted domains that you wish to be able to
use the OPC server on this machine. Include the Everyone group to allow access to all
users on a particular domain.
7. To set the Access permissions, click Use custom access permissions and then click Edit.
8. The Registry Value Permissions window (Figure 96) appears.
148
11. To add a user to the list, select the user, and then click Add. If the user you wish to add
does not appear then click Show Users.
MatrikonOPC Desktop Historian v4.7.0 Users Manual
149
12. When you are done adding users, click OK to close the Add Users and Groups window.
You can then choose to Allow Access or Deny Access for each user.
Notes:
The procedure to set the launch permissions is similar to the above, but instead of
choosing Allow Access for a user you would choose Allow Launch.
The Configuration Permissions contain an Access Control List of principals that are
allowed to modify the configuration information for a server. In other words, it
indicates who is allowed to alter the registry entries for installed servers as well as
who is able to access the registry for the purposes of installing new servers. It is
usually simpler to install and configure servers as a user with local administrative
rights.
13. To connect to an OPC server from outside of the domain, create a local user account on
both the server and the client machine with identical username and password. Then, add
the local user on the OPC server to the DCOM permissions. Use the local account on the
client machine to connect to the OPC server.
Server Identity
The Identity tab for a selected COM (or OPC) server specifies the user account that should be
used when COM starts up the process. The available settings are different for servers that run as
local executables as opposed to those that run as NT services.
Note: It is strongly recommended that OPC servers should be
installed to run as NT services if they are going to be accessed by
remote clients via DCOM. This ensures that the server can always be
accessed even if no one is presently logged on to the machine, and
only one server process ever starts up. It also adds a greater degree
of security in terms of who is able to shut down the server process.
Servers that run as local executables have the option of running as the launching user (the calling
clientthis is the default), the interactive user (the one currently logged onto the machine), or a
specified user. It is usually best to use the interactive user or a specified user. Otherwise, remote
clients might start up multiple separate server processes that are not accessible to others.
Servers that run as NT services should generally run as the local System account. Alternatively,
the server can be set to run as a specified user, although this is usually done from the Service
Control Manager applet rather than DCOMCNFG. Access and Launch permissions are particularly
important when installing a server to run as an NT service.
Default Protocols
The Default Protocols tab specifies the communication protocols available to DCOM. The order
that protocols appear in the list indicates the priority in which they will be used (the topmost
having the highest priority).
The more protocols that appear in the list, the better the chances of connecting to an OPC server
on an unknown remote machine (such as at an OPC Interoperability Workshop). However, it may
also take longer for DCOM to time out if a server machine is not present since it has to try each
protocol in turn.
For most situations, it is best to remove all unused protocols from the list and only include those
that are necessary for your network. For example, on a TCP/IP network, one would include the
Connection-oriented TCP/IP protocol. Contact your IT personnel for more information about
your network.
150
Note: Evidence indicates that there are problems with the datagramoriented protocols (such as UDP/IP) that can cause memory leaks in
DCOM. Therefore, it is strongly recommended that these protocols be
removed from the list of default protocols. Datagram-oriented
protocols are not supported under Windows 2000 at all (although the
DCOM configuration utility still allows you to configure them).
Remote Program ID
Before the OPC Server Browser became available, OPC client applications had to search the
registry to generate a list of available OPC servers. Therefore, some older OPC clients need to have
a program ID in the local registry in order to connect to a particular OPC server.
The simplest solution is to install the OPC server software on the client machine even if it is not
used. Alternatively, use the following steps to copy a program ID to the client machine.
Note: This method may not work for every OPC client. Please check the client documentation for
more information.
WARNING: Any changes made to the registry must be made with
extreme caution!
1. Back up your registry.
2. On the server machine, run REGEDIT as a user that has access rights to the local registry.
3. Expand the HKEY_CLASSES_ROOT key.
4. Find the program ID(s) for the desired OPC server(s).
Note: In the case of MatrikonOPC servers, the ID has the form Matrikon.OPC.Device. If you
quickly type the first few letters then REGEDIT should jump to the location of that key.
Some servers may have both a version-specific as well as a version-independent program
ID. In this case both IDs should be copied to the client machine.
5. For each program ID, select the key and choose Export Registry File from the Registry
menu. Enter a file name, and then click Save. Be careful not to overwrite other export files
that you are creating.
6. Copy the exported REG files to the client machine.
7. Merge the REG files into the registry of the client machine.
Note: This should simply be a matter of double clicking on the file from the desktop of the
client machine. Alternatively, run REGEDIT on the client machine and choose Import
Registry File from the Registry menu, selecting each file in turn. This must be done as a
user who has write access to the local registry.
8. Use REGEDIT to check that the program IDs have in fact, been copied.
9. Delete the REG files since they are no longer needed.
151
Appendix B
Aliases
Scaling Expressions
Alias scaling expressions may use any of the expression constructs listed in Table 59.
Construct
Description
Examples
hello
Joes Alias
+ - * /
(3 * 7 + 1) / 8 2
hi + there
3<4
Not And Or
TIME
DATE
Today is + DATE
INT(x)
INT(3.14) = 3
FRAC(x)
FRAC(3.14) = 0.14
SQRT(x)
SQRT(16) = 4
DIV(x, y)
Divides x by y.
DIV(42, 7) = 6
IF(expr, x, y)
TRUE FALSE
(5 > 6) = FALSE
TYPEOF(x)
TYPEOF(hello) = STRING
STR(x)
STR(3.14) = 3.14
UPPER(x)
LOWER(x)
PRETTY(x)
UPPER(alarm) = ALARM
LOWER(ALARM) = alarm
PRETTY(ALARM) = Alarm
COPY(FIDDLE, 2, 4) = IDDL
FORMATNUMERIC(mask, x)
FORMATNUMERIC('####.#',
123.4567) = 123.5
INPUT
INPUT * 3.1415
OUTPUT
OUTPUT / 3.1415
text
152
Construct
Description
Text value (single quotation marks).
text
Examples
hello
Joes Alias
Advanced Calculations
Calculations may contain references to any OPC item in the servers syntax. However, they may
not contain references to other alias items. There are no limits on how many items can be used in
a calculation. The only limiting factor may be performance related. To reference another OPC item
in the calculation, wrap the items full item path in square brackets. For example to add the items
Com1.Rtu.Reg1 and Com1.Rtu.Reg2 together, the correct expression would be:
[Com1.Rtu.Reg1] + [Com1.Rtu.Reg2]
Advanced alias calculations may use any of the operators listed in Table 60.
Construct
Description
Examples
Minus operator.
x-y
-x
!=
of x by y.
!x
x != y
x%y
&
x&y
Multiplication operator.
x*y
Division operator.
x/y
x^y
Or logical operator.
Returns 1 if true, 0 if false.
x|y
Addition operator.
x+y
<
x<y
<=
==
>
>=
x <= y
x == y
x>y
x >= y
153
Construct
Description
Examples
Alias scaling calculations may use any of the functions listed in Table 61.
Construct
Description
Examples
abs
Absolute value.
abs(x)
acos
Arccosine
acos(x)
asin
Arcsine
asin(x)
atan
Arctangent
atan(x)
avg
avg(v1,v2,v3,...)
bin
bin(binNumber)
decimal number.
ceil
Ceiling.
ceil(x)
cos
Cosine.
cos(x)
cosh
Hyperbolic cosine.
cosh(x)
fact
fact(x)
floor
Floor.
floor(x)
hex
hex(hexNumber)
if
isNaN(value)
log
Natural logarithm.
log(x)
log10
Base-10 logarithm
log10(x)
max
max(v1,v2,v3,...)
max
max(x,y)
max
max(x,y,z)
min
min(v1,v2,v3,...)
Min
min(x,y)
Min
min(x,y,z)
Rand
rand()
Rand
rand(min, max)
154
Construct
Description
Examples
Round
round(x)
Sin
Sine.
sin(x)
Sinh
Hyperbolic sine.
sinh(x)
Sqrt
Square root.
sqrt(x)
Sum
sum(v1,v2,v3,...)
Tan
Tangent.
tan(x)
Tanh
Hyperbolic tangent.
tanh(x)
Double-quotation marks occurring inside quoted values are escaped with an extra doublequotation mark.
Lines beginning with a hash mark (#) are ignored (used for comments).
Field
Description
Alias Group
Name of the alias group folder where the alias belongs. Periods in the name
indicate subfolders below the root (e.g., North.FIC101 = alias group North
under the Alias Configuration root and alias group FIC101 under that).
Alias Name
Name of the alias. Full alias path name composed of the alias group path, a
period, and the alias name (e.g., North.FIC101.CV for an alias named CV).
Item Path
Fully qualified item ID for the OPC item to which the alias refers. Leave this field
blank to specify a holding register.
Data Type
Read-only
Poll Always
Update Rate
Scaling
155
Field
Description
2
3
4
5
=
=
=
=
square root
gain/offset
expression
calculation
Scaling Option 1
Scaling Option 2
Scaling Option 3
Scaling Option 4
Scaling Option 5
Clamp if Scaling is 1 or 2.
Register Initial
Value
Event Enabled
Event Source
Event Category ID
ID of an event category for the generated events. If the category ID does not
exist at import time, the import will fail.
Event Severity
Event Message
Event Timestamp
Type
When the scaling field specifies linear (1) or square root (2) scaling, the five scaling option fields
are defined in Table 63.
Field
High Raw
Description
Raw value range (double-precision real).
Low Raw
High Scaled
Low Scaled
Clamp
Clamp options.
0 = none
1 = clamp low value
2 = clamp high value
3 = clamp both high and low values
156
When the scaling field specifies gain/offset (3) scaling, the first two scaling option fields are defined
as listed in Table 64. The other scaling option fields can be left blank.
Field
Description
Gain
Offset
When the scaling field specifies expression (4) scaling, the first two scaling option fields are defined
as listed in Table 65. The other scaling option fields can be left blank.
Field
Description
Input Expression
Simple formula applied to the value read from the OPC item.
Output Expression
When the scaling field specifies calculation (5) scaling, the first scaling option field is defined as
listed in Table 66. The other scaling option fields can be left blank.
Field
Description
Input Calculation
Scaling Algorithms
For each type of scaling, a different algorithm (Table 67) is applied to values read from the OPC
item. A reverse algorithm is applied to any values written to the OPC item.
Scaling
Linear
Square
Root
Gain/
Offset
Expression
Algorithm/Example
Scaled High Scaled Low
Scaled Low
Raw
Raw
High
Low
x RawLow
Scaled
Scaled Low
High
Scaled
x RawLow
Low
Raw
Raw
High
Low
Reverse Algorithm/Example
x Scaled Low
x Scaled Low 2
RawHigh RawLow
Scaled
Scaled
High
Low
RawLow
RawHigh RawLow
Scaled
Scaled
High
Low
Raw Low
Gain x Offset
x Offset
Gain
SQRT(INPUT) + 5
(OUTPUT 5) * (OUTPUT 5)
157
Appendix C
The Standard data types and their descriptions are listed in Table 68.
Hex
Dec
Data Type
Description
0000
VT_EMPTY
Default/Empty (nothing)
0002
VT_I2
0003
VT_I4
0004
VT_R4
0005
VT_R8
0006
VT_CY
Currency
0007
VT_DATE
Date
0008
VT_BSTR
Text (UNICODE)
000A
10
VT_ERROR
Error code
000B
11
VT_BOOL
0011
16
VT_I1
0012
17
VT_UI1
0013
18
VT_UI2
0014
19
VT_UI4
2002
8194
VT_ARRAY | VT_I2
2003
8195
VT_ARRAY | VT_I4
2004
8196
VT_ARRAY | VT_R4
2005
8197
VT_ARRAY | VT_R8
2006
8198
VT_ARRAY | VT_CY
2007
8199
VT_ARRAY | VT_DATE
Array of dates
2008
8200
VT_ARRAY | VT_BSTR
200A
8202
VT_ARRAY | VT_ERROR
200B
8203
VT_ARRAY | VT_BOOL
2011
8208
VT_ARRAY | VT_I1
2012
8209
VT_ARRAY | VT_UI1
2013
8210
VT_ARRAY | VT_UI2
2014
8211
VT_ARRAY | VT_UI4
158
Appendix D
Security
Introduction
The OPC Framework has implemented the OPC Security Customer Interface version 1.0 of the
specification. Both the IOPCSecurityNT and IOPCSecurityPrivate interfaces are fully supported
(there are no optional pieces).
IOPCSecurityNT describes how NT authentication is used in OPC Security. IOPCSecurityPrivate
describes how proprietary user credentials are used in OPC Security. The OPC Security specification
defines how user credentials are passed from client to server, but very little else. The type of
functionality in an OPC server that is controlled by OPC Security is vendor-determined.
Appendix Structure
This appendix is structured as follows:
MatrikonOPC Tag Security Configuration Utility describes the utility that is used to
configure security for MatrikonOPC servers.
Security Details describes how permissions are applied, how security settings are
stored, and other important details.
Identity
Using the IOPCSecurityNT interface for OPC Security, the identity of the OPC client is the domain
user that is running the OPC client and connecting to the OPC server. The OPC Framework will
attempt to impersonate the client that is connected to the server, and use the name from those
credentials for access control. This method does not require any implementation of OPC Security by
the OPC client, since no interface calls are necessary.
Using the IOPCSecurityPrivate interface for OPC Security, the OPC client must make a call to the
OPC server to log on with a user name and password. In this scenario, the OPC client must
implement and follow the OPC Security specification in terms of following the calls necessary to
provide credentials. The credentials provided through the private interface override those provided
from the NT interface. The OPC client may choose to log off, at which point the NT credentials are
used until the log on call is made again.
Location
Some of the interface calls made from an OPC client to an OPC server require the client to provide
an OPC item ID. The OPC Framework will take the OPC item ID provided, and determine whether
access to that location is allowed or not. A particular server installation may want to control access
to a particular device or branch in the hierarchy, and is able to do so by setting permissions for a
partial item ID or path.
159
Other interface calls do not provide an ID, but may depend on the state of the server with respect
to previous calls. OPC Browsing (DA 2.0) is an example of this. In this case, the full path up to that
particular location is used for determining access rights.
Type
There are seven types of interface functionality in the OPC Framework (specifically the OPC Outer
Layer) that are controlled using OPC Security:
1. Browsing
2. Adding items
3. DA Reading
4. DA Writing
5. HDA Reading
6. HDA Writing
7. HDA Deleting
Browsing is the least intrusive, followed by adding items, reading values from the items, and finally
writing to the items being the most intrusive. There are multiple interfaces, and functions within
those interfaces, that can be used to perform the types of functionality listed above. Thus, security
control has been added to each possible entry. For example, read control has been added to group
subscriptions call-backs as well as synchronous reads and asynchronous reads denying read
control would disable reads for the possible types.
A location that is being accessed by an OPC client may have different permissions for the different
types of access. For example, one particular item may be browseable, added, and read, but the
writing permissions might be restricted so that the user cannot interfere with the operation of the
end device.
Note: Of the seven functionality types listed above, six of them make use of the full OPC item ID
when an interface call is made from the client to the server: Adding Items, Reading, Writing, or
Deleting. When browsing, only a partial path leading to an OPC item may be known at any location
in the browsing hierarchy.
Security settings configured using this utility are read by the OPC Framework and populated in
memory upon server start-up, and are monitored for changes.
Note: In order for the MatrikonOPC Tag Security Configuration Utility to work properly, the
windows user running the utility must have Administrator rights to the computer.
The MatrikonOPC Tag Security Configuration Utility is a component of an OPC server
installation, and is installed in the following location:
C:\Program Files\Common Files\MatrikonOPC\Common\ACLConfig.exe
160
The MatrikonOPC Tag Security Configuration Utility can be run either directly from its
installed location, or from a shortcut found in the Start Menu. If the utility is run from the installed
location, then the user must select the OPC server for which security will be configured. If the
MatrikonOPC Tag Security Configuration Utility is run from the shortcut, then it will configure
security for the OPC server to which the shortcut belongs.
To run the MatrikonOPC Tag Security Configuration Utility from its shortcut:
1. Click on the Windows Start button.
2. Select Programs -> MatrikonOPC -> <OPC Server Name> ->Tag Security.
2. Enter the password created during the installation of the OPC server.
Note: The default password provided for you during installation (if you chose to use the
default) is MatrikonOPC.
3. Click on the OK button.
4. The MatrikonOPC Tag Security Configuration Utility screen (Figure 100) appears.
MatrikonOPC Desktop Historian v4.7.0 Users Manual
161
Layout
The MatrikonOPC Tag Security Configuration Utility screen displays the name of the OPC
server that is being configured for tag security. In Figure 100 above, the Utility screen shows that
the MatrikonOPC Server for Simulation and Testing tag security is being configured.
The left-hand side of the Utility screen shows a column of action icons that can be clicked upon.
These actions are further described later in this appendix. Some actions may not be applicable,
depending on the context in which they are used, and are identified by greyed-out icons.
In the center of the Utility screen there are descriptions for each of the actions that can be
performed. The appearance of these descriptions can be toggled at any time by clicking on the
Hide Help/Show Help link that exists in the bottom-right corner of the Utility screen. When the
Help screen is hidden, a list of users and groups that have been added appears (Figure 101). By
default, there is always a user named Everyone in the Users & Groups list. This user defines the
permissions used for other NT users that are not configured.
162
Figure 101 - MatrikonOPC Tag Security Configuration Utility Main Screen: Users & Groups
Note: After any action is performed, the changes made do not take effect until either the OK or
Apply button has been selected. Clicking on the OK button saves the changes and closes the
Utility screen. Clicking on the Apply button saves the changes and keeps the Utility screen open.
Clicking on the Cancel button or the X button on the top-right of the screen, discards any changes
made.
Add User
There are two types of users for which security can be configured: NT Users and Private Users.
Adding a user to the configuration will allow permissions to be defined for that user. For NT users,
the IOPCSecurityNT interface is used, and for Private users, the IOPCSecurityPrivate interface is
used.
NT User
To add an NT user:
1. From the MatrikonOPC Tag Security Configuration Utility main screen, click on the Add
User button.
MatrikonOPC Desktop Historian v4.7.0 Users Manual
163
2. The Add User window (Figure 102) appears. The NT User option button is selected by
default. This will allow the addition of a user from a Windows NT Domain.
3. By default, the local machine name appears in the From this Location field. To browse to
a different location, click the Locations button.
4. The User field can be entered manually. Clicking on the Check Name button performs
validation on the entered user. The user names are the same as the Windows NT domain
names used on the network. To avoid manually entering a user, click on the Search button,
and select a user from the displayed list of users.
5. To add the selected user, click on the OK button. The user is then added to the list of users
and/or groups currently defined (refer to Figure 103 for a sample list of defined users and
groups).
6. The Edit <Username> window (Figure 108) appears. Follow the instructions in the Edit
User section for adding permissions.
164
Private User
Private users have names and passwords associated with them, custom to the OPC client
application, which must implement the OPC Security Private interface for this section to be
meaningful. Private users exist only in the OPC server. They are not created in any NT domains.
To add a Private user:
1. From the MatrikonOPC Tag Security Configuration Utility main screen, click on the Add
User button.
2. The Add User window (Figure 102) appears.
3. Select the Private User option button (Figure 104).
165
Add Group
Groups are used to group users together so that they can share common permissions. Groups are
not necessary to use OPC Security. However, they are convenient when you need to apply common
permissions to multiple users. A group must contain at least one user, and any combination of
users can be grouped together.
Note: A user can exist in multiple groups, but if two or more of the groups have the same
configured path (refer to the Edit User section), and each group defines a permission (Allow/Deny)
for the type of access, then the group whose name alphabetically comes first is used.
There are two types of groups for which security can be configured: NT Groups and Private
Groups.
NT Group
To add an NT group:
1. From the MatrikonOPC Tag Security Configuration Utility main screen, click on the Add
Group button.
166
2. The Add Group window (Figure 105) appears. The NT Group option button is selected by
default. This will allow the addition of an NT group from a Windows NT Domain.
3. By default, the local machine name appears in the From this Location field. To browse to
a different location, click the Locations button.
4. The Group field can be entered manually. Clicking on the Check Group button performs
validation on the entered group. The group names are the same as the Windows NT domain
group names used on the network. To avoid manually entering a group, click on the Search
button, and select a group from the displayed list of groups.
5. To add the selected group, click on the OK button. The group is then added to the list of
users and/or groups currently defined (refer to Figure 103 for a sample list of defined users
and groups).
6. The Edit <Groupname> window (Figure 115) appears (for NT Groups, there is only the
Permissions tab). Follow the instructions in the Edit Group section for adding
permissions.
Private Group
To add a Private Group:
1. From the MatrikonOPC Tag Security Configuration Utility main screen, click on the Add
Group button.
2. The Add Group window (Figure 105) appears.
3. Select the Private Group option button (Figure 106).
167
4. Enter a name for the group to be created. The group is private and will only exist in the OPC
server. The group cannot be created if there is already a configured user or group with that
same name.
5. Click on the OK button to create the group. It will be added to the list of users and/or
groups currently defined (refer to Figure 103 for a sample list of defined users and groups).
6. The Edit <Groupname> window (Figure 115) appears. Follow the instructions in the Edit
Group section for adding permissions.
Duplicate
Another way to create a new user or group is to duplicate an existing one.
To create a new user or group via duplication:
1. From the MatrikonOPC Tag Security Configuration Utility main screen, right-click your
mouse on the user or group you wish to duplicate.
2. From the displayed menu, select Duplicate.
3. The Enter New Name window (Figure 107) appears.
168
Edit
Once the desired users and/or groups are defined, they must be edited to configure their
respective permissions.
Note: Permissions can also be defined for the user Everyone, which is defined as the default user.
For every NT user not configured in the MatrikonOPC Tag Security Configuration Utility, the user
Everyone is used for determining security permissions.
Permissions for allowing/denying browsing, adding items, reading items, and writing items can be
configured. Permissions are defined for users and groups for a particular location in the servers
address space hierarchy. A location can either be a tag (i.e., OPC Item ID) or a path leading up to
an item.
Edit User
To edit a user:
1. From the MatrikonOPC Tag Security Configuration Utility main screen, either:
Right-click your mouse on the required user and select Edit User from the displayed
menu, or
Click your mouse on the required user, and then select the Edit button.
In this example, the user being edited is User1 so the windows title reads Edit
User1.
There are two tabs on this window: Permissions and General. The General tab
only appears for private users.
169
Permissions
On the Permissions tab, the permissions associated with this user relating to browsing, adding,
reading, and writing for any specific paths or OPC items are configured. The Configured Paths
screen section lists the paths and/or OPC items for which permissions are defined. The
Permissions screen section indicates those permissions with option buttons, which can be set to
Allow, Deny, or Unspecified. Selecting Unspecified directs the OPC Framework to look for the
permission higher up in the hierarchy.
From the Permissions tab, when the Add button is selected, the Add Permission screen is
displayed. In the Server Address Space screen section, folders and items are shown as nodes are
selected and expanded.
Red folders indicate a null branch. This means that the item names below this branch do not
contain the branch name, so permissions set on the branch will not reflect on Add, Write, Read,
and Delete permissions for the items below the branch. To properly set permissions on the items
below the branch, they have to be set on the items themselves.
Figure 109 provides an example of a null branch and items below it, all of which are outlined in
black.
170
When browsing, using the example in the diagram above, Simulation Items is a null branch
(identified by the red folder), Saw-toothed Waves is a non-null branch, and Int1 is an item.
Setting permissions on the Simulation Items branch does not affect Read, Write, Delete, and
Add permissions for the Saw-toothed Waves branch of the Int1 item below that. This is because
when adding the Int1 item, the item ID of the Int1 item is actually Saw-toothed Waves.Int1
and not Simulation Items\Saw-toothed Waves.Int1.
Setting Read, Write, Delete, and Add permissions for the Saw-toothed Waves branch will
affect the items below as Saw-toothed Waves is part of the item ID of the Int1 item (Sawtoothed Waves.Int1), and therefore the Saw-toothed Waves folder does not appear as a red
folder like the Simulation Items folder does.
Note: User permissions override group permissions. For example, if a defined group is denied
writing privileges to an OPC item, Random.Int4, while a defined user (a member of that group) is
allowed writing privilege to Random items (Random.<itemID>), then the user permissions would
take precedence for that OPC item (even though the permissions relating to the group are a better
match for the OPC item, Random.Int4).
To edit a users permissions:
1. Click on the Add button to begin configuring permissions for the current user.
2. The Add User Permission window (Figure 110) appears. This window allows you to browse
the OPC server address space to find either a path in the hierarchy, or a particular OPC
item.
171
3. Expand on the server address spaces root node and continue to browse to the desired path
in the hierarchy, or the desired OPC item.
Note: Branches (i.e., folders) that are red in colour (see Figure 111) are not part of an
items path, but rather are used for browsing organization. Configuring permissions for
adding, reading, and writing will not affect items below it. For more information, refer to
Permissions.
172
173
On the General tab (Figure 113) of the Edit <Username> window, the name and password of
the user can be changed.
To edit a users name:
1. Enter a new name in the Name field.
2. Click on the OK button.
174
175
Edit Group
To edit a group:
1. From the MatrikonOPC Tag Security Configuration Utility main screen, either:
Right-click your mouse on the required group and select Edit Group from the
displayed menu, or
Click your mouse on the required group and then select the Edit button.
In this example, the group being edited is Group1 so the windows title reads Edit
Group1.
For Private Groups, there are three tabs on this window: Permissions, General,
and Members. For NT Groups, there is only the Permissions tab.
On the Permissions tab, the permissions associated with this group relating to browsing, adding,
reading, and writing for any specific paths or OPC items are configured. Refer to the Edit User
176
section regarding configuration on the Permissions tab. Group and user permissions are
configured in the same way.
On the General tab (Figure 116) of the Edit <Groupname> window, the name of the group can
be changed.
To edit a groups name:
1. Enter a new name in the Name field.
2. Click on the OK button.
On the Members tab (Figure 117), the users that are part of the current group are defined. By
default, the Group Members screen section is empty. In Figure 117, User1 has been added to
Group1.
177
178
2. The Members screen section lists all the defined users from which you may choose. Select
one or more desired users to become members of the group.
3. Click on the OK button. The selected user or users appear in the Group Members screen
section on the Members tab (Figure 117).
To remove a user from the group:
1. Select that user in the Group Members screen section.
2. Click on the Remove button.
Notes:
If a user name and a group name (to which the user belongs) have permissions
defined for the same location, the user name will be used. If a user belongs to two
groups that have permissions defined for the same location, the group that is
alphabetically first will be used.
The exact location (full item ID for reading, writing, deleting, and adding, or the full
path for browsing) is always looked for first when determining the permission for a
particular user. If the exact location is not found, or is found but does not contain a
defined permission, then the closest match in location is looked at next, and so on.
The root location (i.e., empty string) will always match, and is used if no partial
location match is made.
Delete
To delete a previously added user or group:
1. From the MatrikonOPC Tag Security Configuration Utility main screen, either:
Select the required user or group from the list and click on the Delete button
(Figure 103), or
179
For a group, right-click your mouse on the required group and select Delete Group
from the displayed menu, or
For a user, right-click your mouse on the required user and select Delete User from
the displayed menu
Change Password
To change the security password for the OPC server:
1. From the MatrikonOPC Security Configuration Utility main screen, click on the Change
Password button (Figure 100).
2. The Change Password window (Figure 119) appears.
Security Details
ACL File
The permissions that the MatrikonOPC Tag Security Configuration Utility creates are stored in
a file named ACL.sec that is located in the same directory as the MatrikonOPC server executable:
C:\Program Files\Matrikon\OPC\< OPC Server Name >\.
ACL.sec is encrypted with 256-bit AES using the password key that was provided during
installation (or changed in the security utility).
While the server is running, if the ACL.sec file is moved or deleted from its location above, security
functions as it did before the file was moved. If the server is re-started with the ACL.sec file
missing, no users will have permissions to do anything (i.e., browsing, adding, reading, writing)
and must re-configure their security settings.
Note: It is advised that this file is backed up and stored somewhere safe, once tag security
configuration has been completed. In the event that this file is lost or deleted by accident, simply
transfer the stored backup (if one was made) to the directory stated above. If ACL.sec becomes
deleted and no backup was made, tag security will need to be re-configured.
MatrikonOPC Desktop Historian v4.7.0 Users Manual
180
Determining Permission
Whenever a browsing, item addition, read, write, or delete operation is performed by the OPC
client, the OPC Framework will call a permission routine to determine if permission is allowed or
denied. Three pieces of information are always sent to this routine call:
1. Identity
2. Location
3. Type
Identity is the user name described in the previous section either the NT domain name, a private
name, or the default user Everyone. In addition, identity includes any groups (private or NT) that
the user belongs to. Location is either the full item ID or a partial path in the server hierarchy.
Type is the access type: browsing, item addition, reading, or writing. Each piece of information is
checked in the order listed above.
The following information details the procedure used in determining permission rights:
1. Look for a permission match with the NT domain name or private name. This step occurs
only if the NT domain name or private name has been defined in the Users & Groups list.
181
2. If a permission match was not yet found, look for one using each group defined in the
Users & Groups list that the NT domain name or private name belongs to. The first group
that contains a permission match will be the one used. An NT domain name does not need
to be defined in the Users & Groups list for a group it belongs to, to have a permission
match. The NT domain name must be part of Group Members for private groups, or in the
Active Directory for NT groups.
3. If a permission match was not yet found, look for a permission match using the default user
Everyone.
The procedure used in finding a permission match for a particular identity is as follows:
1. Check whether the exact location is found in the Configured Paths list for the identity. If
found:
a. Check whether the permission type (browse, add, read, write, or delete) is
specified (Figure 112). If the permission type is specified for the action being
performed, a match is found and the permission (either allow or deny) is used.
2. If a permission match was not found in step 1a, check whether a partial match of the
location is found in the Configured Paths list for the identity. A partial match is always a
sub-string of the given location that starts with the same characters. This represents
starting from the root location and moving down the browsing hierarchy.
For example, the location Random is a partial match of the full item ID Random.String.
However, String is not a partial match (even if it is a sub-string) because it does not match
the first seven characters. The root location \ is considered a partial match for every full
item ID.
For each partial match from step 2, apply step 1a. The best partial match (i.e., the one that
has the most characters) that is successful in step 1a is the one whose permission is used.
Examples
This section contains examples of tag security settings made via the MatrikonOPC Tag Security
Configuration Utility, and the impact of these settings.
Default
The default tag security configuration provided is quite simplistic as is shown in Table 69:
User/Group
Everyone
Configured Paths
\
Browse
Allow
Add
Allow
Read
Allow
Write
Allow
As no users or groups are defined, any NT user connecting to the OPC server will use the
Everyone default user for permissions. Only the root level location is defined under the
Configured Paths list, which gives full permissions to the entire OPC server. An administrator will
want to change these default settings for the OPC server to provide more security on its tags.
182
Example 1
Table 70 contains a possible tag security configuration enforces complete restricted access except
for the NT user DOMAIN\Admin:
User/Group
Configured Paths
Browse
Add
Read
Write
Everyone
Deny
Deny
Deny
Deny
DOMAIN\Admin
Allow
Allow
Allow
Allow
Table 70 - Example 1
At this point, more users can be added which belong to a more restricted group. This group may be
denied write capability or restricted to certain areas in the server hierarchy.
Example 2
Following is an example of a tag security configuration for the MatrikonOPC Server for Simulation
and Testing, with sample use-cases. Table 71 lists all defined users and groups and their
associated permissions. Table 72 indicates which users are members of the defined groups.
Unspec. permission indicates Unspecified. Groups in this example are Private Groups.
User/Group
Configured Paths
Browse
Add
Read
Write
Everyone
Allow
Deny
Deny
Deny
Everyone
Configured Aliases
Deny
Unspec.
Unspec.
Unspec.
Deny
Allow
Allow
Deny
Common (group)
Allow
Allow
Allow
Deny
Common (group)
Triangle Waves
Deny
Deny
Deny
Deny
Admin (group)
Allow
Allow
Allow
Allow
Admin (group)
Bucket Brigade.Int4
Unspec.
Unspec.
Unspec.
Deny
DOMAIN\john.doe
DOMAIN\fred.stone
DOMAIN\sally.simpson
DOMAIN\the.admin
Supervisor
Restricted (group)
User/Group
Configured Paths
Restricted
DOMAIN\john.doe
Common
DOMAIN\fred.stone, DOMAIN\sally.simpson
Admin
DOMAIN\the.admin
Table 72 - Example 2: Groups and Members
Case 1
User DOMAIN\no.name connects. This name is not defined, so the Everyone permissions are
used. At the root level location, the default user can browse but no more. The only other location
where permissions are defined for the default user is Configured Aliases where browsing is
183
denied, and adding, reading, and writing permissions are not defined. Thus, DOMAIN\no.name
will be able to browse the entire server except the Configured Aliases branch and all aliases
under it. Also, DOMAIN\no.name will not be able to do any item addition, reading, or writing.
Since item addition, reading, and writing permissions were not defined for the default user under
Configured Aliases - it would use the permissions defined at the root level.
Case 2
User DOMAIN\john.doe connects. No permissions have been defined for this user name or the
Restricted group to which it belongs - the Everyone permissions apply. The user has no access to
any tags under the Configured Aliases path but has Browse access to the rest of the address
space.
Case 3
User DOMAIN\fred.stone connects. This user belongs to the defined group Common. At the root
level, the group Common can browse, add, and read items, but writing is denied. The only other
location which defines permissions for this group is Triangle Waves. This location has denied all
permissions for the Common group.
Case 4
User Supervisor connects through the private security interface and logs on. This user does not
belong to any group, but its name has a root level permission which allows it to add and read
items. No other locations have permissions defined. Since the user cannot browse, it will need to
know the item syntax for any items it wishes to add and read.
Case 5
User DOMAIN\the.admin connects. This user belongs to the Admin group, which at the root
level has all permissions allowed. The only other location where the Admin group has permissions
defined, is the full item ID Bucket Brigade.Int4. This user is unable to write to that item.
However, the root permissions for browsing, adding, and reading the item apply as they are not
defined at this level.
184
Appendix E
Installation
Once the system requirements have been met, you are ready to install the software.
Notes:
3. Either a Pre-Requisites screen (Figure 121) appears, or you are taken directly to the
License Agreement (Figure 122) screen. If the License Agreement screen is the
displayed screen, go to step 5.
4. If the Pre-Requisites screen appears, then click on the Next button to install the listed
pre-requisites.
185
5. After all pre-requisites have been installed, the License Agreement screen (Figure 122)
appears.
Note: From the License Agreement screen, you have the option of selecting the I reject
the license agreement option. Selecting the I reject the license agreement option
button disables the Next button so your options are to return to the previous screen, cancel
the install by clicking on the Cancel button, or select the I accept the license agreement
option button enabling you to proceed through the install.
186
6. Read the End-User License Agreement, using the scroll bar to view the entire message.
7. Select the I accept the license agreement option button.
8. Click on the Next button.
9. Click on the Next button. The Product Registration screen (Figure 123) appears.
187
11. Click on the Next button. The Setup Type screen (Figure 124) appears.
188
189
14. Select the folder in which to install MatrikonOPC Desktop Historian, or accept the default
location displayed in the Folder path field.
15. Click on the Next button. The Start Menu screen (Figure 126) appears.
190
16. Select the Start Menu group and then specify whether you want shortcuts created only for
yourself, or for all users, by selecting the applicable option button.
17. Click on the Next button. The Enter Password screen (Figure 127) appears.
191
18. A default password is supplied for you in the Password and Confirm Password fields.
Notes:
The default password provided for you is MatrikonOPC. Note
this password for future reference.
19. Click on the Next button to accept the default password. The Licensing screen (Figure
128) appears.
192
193
22. If you would like to install a demonstration (i.e., evaluation) version of MatrikonOPC Server
for Performance Monitor, select the Yes option button. If the product is not required, select
No.
Note: A permanent MatrikonOPC Server for Performance Monitor license is not included
with MatrikonOPC Desktop Historian and must be purchased separately. Contact your
Account Manager for assistance and more information.
23. Click on the Next button. The Matrikon Analytics Excel Reporter screen (Figure 130)
appears.
194
24. If you would like to install a demonstration version of Matrikon Analytics Excel Reporter,
select the Yes option button. If the product is not required, select No.
Notes:
If you do not have Microsoft Excel installed on your machine, this screen is not
displayed. Instead, you are notified that your machine does not meet the
requirements needed to install Excel Reporter. You will need to exit the install, install
Excel, and then re-start the Micro Historian installation. For assistance, contact
MatrikonOPC Support.
If you have OPC2XL installed on your machine, and you select the Yes option,
OPC2XL will be removed during the install of this demonstration version.
25. Click on the Next button. The MatrikonOPC Trender screen (Figure 131) appears.
195
26.If you would like to install a demonstration version of MatrikonOPC Trender, select the Yes
option button. If the product is not required, select No.
Notes:
If the Sun Java Virtual Machine option on your machine is enabled, this screen is not
displayed. Instead, you are notified that your machine does not meet the
requirements needed to install Trender. You will need to exit the install, clear the
option, and then re-start the Micro Historian installation. For assistance, contact
MatrikonOPC Support.
27. Click on the Next button. The Ready to Install screen (Figure 132) appears.
196
28. Click on the Next button. The Installing MatrikonOPC Desktop Historian screen (Figure
133) appears, installation begins, and the product files are copied to the computer.
Note: Prior to starting the installation, you have the option of clicking on the Back button
to change any of the installation information. Click on the Cancel button if you wish to stop
or cancel the installation.
197
29. When the installation has finished, the MatrikonOPC Desktop Historian Setup Complete
screen (Figure 134) appears stating that the MatrikonOPC server has been successfully
installed.
198
30. At this point, you have the option of launching any or all of the following by selecting the
necessary checkbox or checkboxes:
Configuration panel
Release Notes
Users Manual
31. Click on the Finish button to complete the installation and exit the Wizard.
32. The necessary files have now been copied to the target computer, the software components
are registered, and shortcut icons are created in the Start menu.
Note: At this point, it is recommended that you verify the DCOM
settings. Reference to the DCOM configuration can be found in the
DCOM Manual. This configuration varies for different operating
systems.
199
Appendix F
Installed Files
The installation program copies all necessary files to the target computer and creates shortcut
icons in the Start menu.
The files listed in Table 73 are installed by default, in the following location:
C:\Program Files\Matrikon\OPC\Desktop Historian
File Name
Description
The files listed in Table 74 are installed by default, in the following location:
C:\Program Files\Matrikon\OPC\Desktop Historian\Core
File Name
Description
Log\
ArchiveDB.dll
ArchiveDBps.dll
Archiver.exe
ArchiverCoreNode.dll
archiverps.dll
ArchiverStorageEngineNode.dll
ArchiverTagnode.dll
CodeTranslator.dll
CodeTranslatorps.dll
DesktopHistorian.iC
iC Configuration Interface.
lsapiw32.dll
Licensing DLL.
RmsApiProxy.dll
security.cfg
Security Settings.
StorageEngine_FF4.dll
StorageEngine_FF7.dll
StorageEngineConfigps.dll
StorageEngineps.dll
200
File Name
Description
SysMatLogEx.dll
Log Library.
SysMatLogExps.dll
TagDB.dll
TagDBps.dll
UnLicensedNode.dll
UserDB.dll
UserDBps.dll
The files listed in Table 78 are installed by default, in the following location:
C:\Program Files\Matrikon\OPC\Desktop Historian\Database
File Name
Description
Archive_20030827052840.ECF
Holds the information about the storage engine type, location, and
configuration.
Attribute_20080327150700.ECF
Holds the list of configurable attributes for each item (i.e., not the
attribute values, just the meta information about the attribute
itself).
Tag_20090507192209.ECF
Tag_20120416215101.ELF
Holds the tags and the attribute values for the tags
User_20030527183812.ECF
This is intended for user access control and holds defaults included
with the install.
Table 75 - Files Installed in "Database" Folder
The files listed in Table 76 are installed by default, in the following location:
C:\Program Files\Matrikon\OPC\Desktop Historian\OPC Client
File Name
Description
Log\ ArchiverOPC.log
ArchiverOPC.exe
ArchiverOPCClientConfigControl.dll
lsapiw32.dll
Licensing DLL.
ProductInfoChannelControl.dll
security.cfg
Security Settings.
Table 76 - Files Installed in "OPC Client" Folder
201
The files listed in Table 77 are installed by default, in the following location:
C:\Program Files\Matrikon\OPC\Desktop Historian\OPC Server
File Name
Description
Plugins\Calculations\SimpleMath.dll
Plugins\Couriers\
Resources\CalcEngineServerResource\EN.res
Resources\CalcEngineServerResource\EN_CA.res
Resources\CalcEngineServerResource\root.res
Resources\CoreLibraryResource\EN.res
Resources\CoreLibraryResource\EN_CA.res
Resources\CoreLibraryResource\root.res
Resources\NetPortalQueryServerResource\EN.res
Resources\NetPortalQueryServerResource\EN_CA.res
Resources\NetPortalQueryServerResource\root.res
Resources\OpcDataDeliveryResource\EN.res
Resources\OpcDataDeliveryResource\EN_CA.res
Resources\OpcDataDeliveryResource\root.res
Resources\ProcessNetDataDeliveryResource\EN.res
Resources\ProcessNetDataDeliveryResource\EN_CA.res
Resources\ProcessNetDataDeliveryResource\root.res
Resources\SchedulerResource\EN.res
Resources\SchedulerResource\EN_CA.res
Resources\SchedulerResource\root.res
Resources\SimpleMathResource\EN.res
Resources\SimpleMathResource\EN_CA.res
Resources\SimpleMathResource\root.res
AliasControl.dll
Altova.dll
AltovaXML.dll
CalcEngine.dll
CalcEngineResource.dll
CalcEngineServerPS.dll
CalcEngineWrapper.dll
CalculationGraph.dll
clipsdll.dll
DotNetControlsLib.dll
icudt40.dll
icuin40.dll
icuuc40.dll
LogOptions.dll
js32.dll
log4cxx.dll
PreRegistration.LOG
ProcessNetDataDelivery.dll
Scheduler.dll
ScriptLibrary.dll
xerces-c_2_8.dll
ACL.sec
202
File Name
Description
and permissions configured for the
server.
ACLSecure.exe
AliasCalculationLib.dll
AliasControl.dll
ProgID.txt
DefaultConfig.xml
OPCMatArc.exe
OptionChannelControl.dll
ProductInfoChannelControl.dll
RmsApiProxy.dll
security.cfg
Security settings.
ServerConfigControl.dll
ServerOpts.ini
The files listed in Table 78 are installed by default, in the following location:
C:\Program Files\Matrikon\OPC\Desktop Historian\Task Scheduler
File Name
Description
Log\ TaskScheduler.log
LogOptions.dll
ProductInfoChannelControl.dll
security.cfg
Security Settings.
TaskScheduler.exe
TaskScheduler.ic
TaskSchedulerControl.dll
Description
Zip utility for backup functionality.
203
File Name
Description
Command-line tool for backing up stored data.
BackupTool.exe
Note: If Microsoft Excel is present on the machine, the file listed in Table 80 is installed by
default in the following location:
C:\Program Files\Matrikon\OPC\Desktop Historian\Util
File Name
Description
Tag Manager Excel Add-in.
TagMgr.xll
The files listed in Table 81 are installed in the systems Global Assembly Cache
(C:\WINDOWS\assembly):
File Name
Description
Syncfusion.Core.dll
Syncfusion.Core.dll
Syncfusion.Edit.Windows.dll
Syncfusion.Edit.Windows.dll
Syncfusion.Grid.Base.dll
Syncfusion.Grid.Base.dll
Syncfusion.Grid.Windows.dll
Syncfusion.Grid.Windows.dll
Syncfusion.Shared.Base.dll
Syncfusion.Shared.Base.dll
Syncfusion.Shared.Windows.dll
Syncfusion.Shared.Windows.dll
Syncfusion.Tools.Base
Syncfusion.Tools.Base
Syncfusion.Tools.Windows.dll
Syncfusion.Tools.Windows.dll
The files listed in Table 82 are installed by default, in the following location:
C:\Program Files\Common Files\MatrikonOPC\Common
File Name
Description
ACLConfig.exe
ClientToolkit.dll
ClientToolkit.dll
204
File Name
Description
DotNetControlsLib.dll
EULA.pdf
License document.
EventLogger.dll
EventLogger.dll
iC.exe
LicenseRemover.exe
LicenseWizard.exe
LogLibrary.dll
LogLibrary.dll
Marshal.exe
Marshal.log
Marshal.log.bak
Moces.log
MocesInterfaces.dll
MTKAuthorize.exe
ODH.ver
OEM_Matrikon_OPC.dll
OPCAuto.dll
opcda20_auto.doc
OPCDAAuto.dll
opchda10_auto.doc
opchda_ps.dll
OPCHDAAuto.dll
PSTCFG.exe
PSTCFGInterface.dll
PSTcfgps.dll
PSTCFGMatrikon.OPC.DesktopHistorian.1.log
205
File Name
Description
PSTCFGMatrikon.OPC.DesktopHistorian.1.log.bak
Description
EXPREVAL.DLL
OPC_AEPS.DLL
OPCBC_PS.DLL
OPCCOMN_PS.DLL
OPCDAAuto.dll
OPCDXPS.DLL
OPCENUM.EXE
OPCHDA_PS.dll
OPCPROXY.DLL
OPC Data Access 2.0 and 1.0a Interfaces and Marshalling Library.
OPCSEC_PS.DLL
ACTXPRXY.DLL
206
Appendix G
Un-Installation
To successfully un-install MatrikonOPC Desktop Historian, using the Add or Remove Programs
from the Microsoft Windows Control Panel is recommended.
Note: Matrikon strongly recommends that you back up all history and
configuration files prior to upgrading or re-installing the software.
To un-install MatrikonOPC Desktop Historian:
1. Click on the Start button and highlight the Control Panel item.
2. From the displayed menu, select Add or Remove Programs.
3. The Add or Remove Programs window (Figure 135) is displayed.
4. Scroll through the list of currently installed programs and updates to find and select
MatrikonOPC Desktop Historian.
5. Click on the Remove button associated with the MatrikonOPC Desktop Historian program to
initiate the un-install process.
207
7. Select the Remove option button to un-install MatrikonOPC Desktop Historian entirely.
8. Click on the Next button. The Ready to Uninstall screen (Figure 137) is displayed.
208
209
11. When the un-install has finished, the MatrikonOPC Desktop Historian Setup Complete
screen (Figure 139) appears stating that MatrikonOPC Desktop Historian was successfully
un-installed.
210
12. Click on the Finish button to complete the un-install and exit the Wizard.
13. The program no longer appears listed in the Add or Remove Programs window.
211
Appendix H
File Formats
A file format defines how historical data is placed in a data file. Each file format offers trade-offs
between performance and space requirements.
Note: File formats are NOT interchangeable. Data stored in files that
do not conform to the current file format will not be available. It is
recommended that the file format be selected once and that is when
the product is installed. If you need to convert data from one file
format to another, contact MatrikonOPC Support.
The High Resolution Rolling Buffer file format does not support String data types. If String
data is required then MatrikonOPC Desktop Historian must be configured to use FF7.
The High Resolution Rolling Buffer file format only supports data insertion via the OPC Insert
method and will reject all calls to the OPC InsertReplace method.
212
Limitations:
The maximum string length supported in FF7 storage format is 2,033 characters. If the
input string length is longer than 2,033 characters, the string is truncated before being
stored.
The High Resolution Rolling Buffer file format supports only data insertion via the OPC Insert
method and will reject all calls to the OPC InsertReplace method.
The 25MB file size is not strictly enforced. If data is written to Desktop Historian that is
older than the latest data written (i.e., back filling), then the data files may grow to exceed
the target 25 MB.
If the .DAT file size is greater than 3.5 GB, or the data point time stamp is too far in the
future when compared to the (latest time stamp + configured offset time), the data is
rejected and recorded in a .CSV file for future use. The .CSV file is located in C:\matrikon
data\Exempt_FF7R.
The maximum string length supported in FF7 storage format is 2,033 characters. If the
input string length is longer than 2,033 characters, the string will be truncated before being
stored.
The maximum file size must be configured to be less than 4 GB. The data points are
rejected when the file size exceeds 3.5 GB and the rejected data points are stored in the
.CSV file for future use. The .CSV file is located in C:\matrikon data\Exempt_FF7.
213
Appendix I
Name
Attributes
Data Type
Description
Description
String
Engineering Units
String
Stepped
Boolean
Archiving
Boolean
Node Name
String
Process Name
String
Source Name
String
Source Type
String
Normal Maximum
Floating Point
Normal Minimum
Floating Point
Floating Point
Integer
An absolute change.
A percentage change of the High/Low span.
A percentage change from the previous value.
Ignored/disabled.
Floating Point
Low Limit
Floating Point
Array Index
Integer
214
Name
Data Type
Description
based index).
Access Path
String
Update Rate
Integer
Boolean
Timestamp Bias
Integer
Boolean
Integer
String
215
Appendix J
Data Type
Description
NONE
Default empty
BOOL
INT1
INT2
INT4
UINT1
UINT2
UINT4
FLT4
4-byte real
FLT8
STR
216
Appendix K
Third-Party Licensing
217
Appendix L
218
Appendix M
Relative times are optionally used to specify the start and end times for a range of time that is of
interested for trending.
Relative times are specified using an optional keyword (Table 86) to indicate the starting point,
followed by one or more offsets that applied to that starting point. Relative times are always
applied with respect to the local time clock on the OPC HDA server providing the data. Uppercase
letters should be used, as per the HDA standard. However, the Backup Utility also accepts lower or
mixed case.
Keyword
Description
NOW
SECOND
The start of the current second. For example, if the time is now 08:54:20.999,
then SECOND would choose a time of 08:54:20.000.
MINUTE
HOUR
DAY
WEEK
MONTH
YEAR
Relative time offsets consist of a sign (e.g., + or -), an integer count, and an offset unit (Table 87).
If no sign is used between offsets, then the last sign used in the offset will be used. If no sign has
been used in the relative time string yet, the assumed sign is +.
Offset Unit
Description
Second
Minute
Hour
Day
Week
MO
Month
Year
Table 87 - Offset Units
Description
If NOW is 2008-01-02
6:30:27.525 AM UTC, then
NOW-1D
DAY-1D
2008-01-01 6:30:27.525 AM
2008-01-01 12:00:00.000 AM
DAY-1D+2H
2008-01-01 2:00:00.000 AM
219
Relative Time
Example
Description
If NOW is 2008-01-02
6:30:27.525 AM UTC, then
DAY-1D+2h+30M
DAY-1D+2H30M
-1W
2007-12-26 6:30:27.525 AM
2007-12-30 12:00:00.000 AM
WEEK
2007-12-23 12:00:00.000 AM
WEEK-1W
2008-01-02 5:00:27.525 AM
-1H30M
SECOND-30M
2008-01-02 6:00:27.525 AM
2008-01-01 2:30:00.000 AM
2008-01-01 2:30:00.000 AM
220
Appendix N
The following HDA aggregate functions are available in the MatrikonOPC Desktop Historian:
Function
Description
Interpolative
TimeAverage
MinimumActualTime
The minimum raw GOOD value that occurs within the selected
interval. This value is returned with the time stamp at which it
occurs. If there are multiple occurrences, then the oldest time
stamp is returned.
Minimum
MaximumActualTime
The maximum raw GOOD value that occurs within the selected
interval. This value is returned with the time stamp at which it
occurs. If there are multiple occurrences, then the oldest time
stamp is returned.
Maximum
MatrikonAggregate_TrendFriendly
221