MatrikonOPC Server For OMRON User Manual
MatrikonOPC Server For OMRON User Manual
User's Manual
Document
Version
Description
Author
2008-07-02
1.0
Initial document.
ZY
2008-07-18
1.1
LW
2008-10-07
1.2
2008-11-20
1.3
LW, LB
2010-01-08
2.0
LB
ZA, SN,
LB
2010-01-18
2.1
LB
2010-01-22
2.2
LB, SN
2010-01-26
2.3
ZA
2010-01-28
2.4
ZA, LB,
CN
2010-04-07
2.5
LB
2010-05-05
2.6
GEAK
2010-05-25
3.0
GEAK
2010-06-08
4.0
LB
SOFTWARE VERSION
Version:
1.2.0
DOCUMENT VERSION
Version:
4.0
COPYRIGHT INFORMATION
Copyright 1997 - 2010, Matrikon Inc. 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 Inc.
CONFIDENTIAL
The information contained herein is confidential and proprietary to Matrikon Inc. It may not be disclosed or transferred,
directly or indirectly, to any third party without the explicit written permission of Matrikon Inc.
LIMITATIONS
Matrikon has made its best effort to prepare this manual. Matrikon makes no representation or warranties of
any kind with regard to the completeness or accuracy of the contents herein and accepts no liability of any kind
including without limitation warranties of merchantable quality, satisfactory quality, merchantability and
fitness for a particular purpose on those arising by law, statute, usage of trade, course of dealing or otherwise.
Matrikon shall not be liable for any losses or damages of any kind caused or alleged to be caused directly or
indirectly from this manual.
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 Inc.
OTHER
MatrikonOPC is a division of Matrikon Inc.
Table of Contents
Introduction ................................................................................................................... 11
Who Should Use This Manual ............................................................................................ 12
Overview of Manual ......................................................................................................... 12
References ..................................................................................................................... 13
Document Terminology .................................................................................................... 14
Getting Started............................................................................................................... 15
System Requirements ...................................................................................................... 15
Software Requirements ................................................................................................. 15
Hardware Requirements ................................................................................................ 15
Configuration ................................................................................................................. 16
Starting the MatrikonOPC Server for Omron PLCs ................................................................ 16
Tool Tray Menu ............................................................................................................... 17
Control Panel .................................................................................................................. 17
Configuration Window ...................................................................................................... 18
File Menu ..................................................................................................................... 20
Edit Menu .................................................................................................................... 20
View Menu ................................................................................................................... 21
Tools Menu .................................................................................................................. 21
Help Menu ................................................................................................................... 22
Options Window .............................................................................................................. 22
General Options............................................................................................................ 22
General Logging Options................................................................................................ 24
Interface Logging Options .............................................................................................. 25
Advanced Options ......................................................................................................... 26
Server Configuration ........................................................................................................ 28
Creating Objects ........................................................................................................... 28
Creating and Configuring an Ethernet Network Object ....................................................... 30
Creating and Configuring an Ethernet FINS Connection Object ........................................... 32
Creating and Configuring a HostLink Network Object ......................................................... 38
Creating and Configuring a C-Mode Connection Object ...................................................... 44
Creating and Configuring a HostLink FINS Connection Object ............................................. 48
Creating and Configuring a Redundancy Group Object ....................................................... 54
Changing Objects ......................................................................................................... 58
Removing Objects ......................................................................................................... 58
Alias Configuration .......................................................................................................... 59
Inserting Alias Groups ................................................................................................... 59
Renaming Alias Groups.................................................................................................. 60
Inserting New Aliases .................................................................................................... 60
Editing Aliases .............................................................................................................. 62
Removing Aliases.......................................................................................................... 63
Removing Alias Groups .................................................................................................. 63
Exporting Aliases .......................................................................................................... 63
Importing Aliases.......................................................................................................... 63
Configure Alias Scaling .................................................................................................. 64
Configure Alias Events ................................................................................................... 65
Configure Categories ..................................................................................................... 67
Expression Wizard ........................................................................................................... 68
Examples ..................................................................................................................... 68
Item Path Browser........................................................................................................... 72
Saving a Configuration ..................................................................................................... 73
MatrikonOPC Server for Omron PLCs v1.2.0 Users Manual
Table of Appendices
Appendix A
Distributed COM (DCOM)......................................................................... 98
DCOM Configuration Utility ............................................................................................... 98
Default Properties............................................................................................................ 98
Security Permissions ........................................................................................................ 99
Server Identity.............................................................................................................. 103
Default Protocols ........................................................................................................... 103
Remote Program ID ....................................................................................................... 104
Appendix B
Aliases .................................................................................................. 105
Scaling Expressions ....................................................................................................... 105
Advanced Calculations ................................................................................................... 106
CSV File Format ............................................................................................................ 108
Scaling Algorithms ......................................................................................................... 110
Appendix C
Standard Data Types ............................................................................. 111
Appendix D
Microsoft Excel as a DDE Client ............................................................. 112
MatrikonOPC Server for Omron PLCs v1.2.0 Users Manual
Table of Figures
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
11
11
12
16
17
18
19
23
24
26
27
28
30
32
33
35
36
37
38
39
41
42
43
44
45
46
47
48
49
50
52
53
7
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
85
86
87
88
89
90
91
92
93
150
151
152
153
157
158
159
160
161
Table of Tables
Table 1 - Terms and Definitions...................................................................................... 14
Table 2 - Tool Tray Menu Commands .............................................................................. 17
Table 3 - Control Panel Commands ................................................................................. 18
Table 4 - Configuration Window Commands ................................................................... 20
Table 5 - File Menu Commands ....................................................................................... 20
Table 6 - Edit Menu Commands (Server Configuration) .................................................. 21
Table 7 - Edit Menu Commands (Alias Configuration)..................................................... 21
Table 8 - View Menu Commands ..................................................................................... 21
Table 9 - Tools Menu Commands .................................................................................... 22
Table 10 - Help Menu Commands ................................................................................... 22
Table 11 - General Options Tab Components .................................................................. 24
Table 12 - General Logging Options Tab Components .................................................... 25
Table 13 - Interface Logging Options Tab Components .................................................. 26
Table 14 - Advanced Options Tab Components ............................................................... 28
Table 15 - Insert New Object Window Options ............................................................... 29
Table 16 - Create New Ethernet Network Window Components ..................................... 31
Table 17 - Create New Ethernet FINS Connection Window (General Tab) Components .. 34
Table 18 - Create New Ethernet FINS Connection Window (Timing Tab) Components ... 35
Table 19 - Create New FINS Connection Window (FINS Tab) Components ..................... 37
Table 20 - Create New HostLink Network Window (Serial Port Tab) Components .......... 40
Table 21 - Create New HostLink Network Window (Timing Tab) Components ................ 41
Table 22 - Create New HostLink Network Window (Advanced Options Tab) Components
....................................................................................................................................... 43
Table 23 - Create New C-Mode Connection Window (Serial Port Tab) Components ........ 45
Table 24 - Create New C-Mode Connection Window (Timing Tab) Components .............. 46
Table 25 - Create New C-Mode Connection Window (Advanced Options Tab) Components
....................................................................................................................................... 47
Table 26 - Create New FINS Connection Window (General Tab) Components ................ 50
Table 27 - Create New HostLink FINS Connection Window (Timing Tab) Components ... 51
Table 28 - Create New HostLink FINS Connection Window (FINS Tab) Components ...... 53
Table 29 - Redundancy Modes ........................................................................................ 55
Table 30 - Create New Redundancy Group Window Components ................................... 57
Table 31 - Insert New Alias Window Alias Type Options ............................................. 61
Table 32 - Insert New Alias Window Alias Properties Options ..................................... 62
Table 33 - Configure Scaling Window Options ................................................................ 64
Table 34 - Generate Events Window Options .................................................................. 67
Table 35 - New Category Window Options ..................................................................... 67
Table 36 - Expression Wizard Options ............................................................................ 69
Table 37 Item Path Browser Options ........................................................................... 73
MatrikonOPC Server for Omron PLCs v1.2.0 Users Manual
10
Introduction
The MatrikonOPC Server for Omron PLCs provides real-time data access to the Omron
Programmable Logic Controllers (see Figure 2 and Figure 3 for some examples) using the C-Mode
protocol (over HostLink) and the FINS protocol (over Ethernet or HostLink) as illustrated below in
Figure 1.
IP 192.168.10.3
Node 3
IP 192.168.10.2
Node 2
Network 1
Ethernet
Server for
Omron PLC
IP 192.168.10.1
Node 1
IP 192.168.10.4
Node 4
The MatrikonOPC Server for Omron PLCs supports, among others, the following features:
C-Mode connections over HostLink.
FINS connections over HostLink.
FINS connections over Ethernet using TCP and UDP.
Offline mode for simulations and testing.
11
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:
Introduction this introductory chapter.
Getting Started provides system requirements information.
12
Configuration shows how to start and configure the server, and describes each
component in detail, including windows/screens, panels, tabs, and menu commands.
OPC Data Items describes the servers items.
Diagnostics explains how to use logging, statistical items, data qualities, timestamps,
and result codes to get the most efficiency from the users system.
Limitations provides information on specific performance and operational limitations of
the software.
Troubleshooting provides licensing, MatrikonOPC Support contact information, solutions
for common problems that may be encountered, and answers to frequently asked questions.
OPC Compliance details supported interfaces with regard to installation, common
interfaces, and data access.
Appendices:
o
A - DCOM
B Aliases
F Security
G Offline Mode
H Installation
I Installed Files
J Un-Installation
References
This document references information found within the following documents/sites:
www.opcfoundation.org
www.matrikonopc.com
www.opcsupport.com
MatrikonOPC Server Users Manual
OPC Overview 1.0
OPC Common Definitions and Interfaces 1.0
OPC Data Access Specification 2.05a
OPC Data Access Specification 3.00
OPC Historical Data Access Specification 1.2
OPC Alarms and Events Specification 1.10
13
Document Terminology
The following terms are used interchangeably throughout this document:
screen and window
tab and panel
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 Inc.
MatrikonOPC
OPC
PLC
14
Getting Started
This chapter contains important information about installing the server 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 H - Installation walks you through the installation process. Appendix I
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 server 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
The server requires the following software:
Microsoft Windows XP SP2, or
Microsoft Windows 2003 SP0, or
Microsoft .NET 2.0 Framework (included with this install program)
Note: It is recommended that the most current service packs are
installed.
Hardware Requirements
The server requires the following hardware:
Intel Pentium 4 Processor
512 MB RAM
40 GB 7200 RPM Hard Drive
The server requires the following additional hardware to make use of the following functionality:
Standard Ethernet adapter.
Serial port for serial communication.
HostLink serial cable for Omron PLCs.
15
Configuration
The servers 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 server when submitted.
Minimal configuration of the MatrikonOPC Server for Omron PLCs is required for the server to
function properly, but you can customize the servers behaviour as required. This section of the
manual shows you how to start and configure the server and describes each component in detail,
including the windows, panels, and menu commands.
The Starting the MatrikonOPC Server for Omron PLCs section of this manual shows you how
to start the software. The next four sub-sections describe the Tool Tray Menu, Control Panel,
Configuration window, and the Options window, in detail.
The Server Configuration section describes in detail how to configure the server. Instructions for
configuring the MatrikonOPC Server for Omron PLCs as a DDE service appear in Appendix D Microsoft Excel as a DDE Client. The Alias Configuration section explains how to create userdefined aliases in place of regular OPC items, followed by four sub-sections that cover saving,
clearing, and loading configuration settings, and shutting down the server.
If the server is not installed as a Windows service, the Welcome screen appears briefly
when the server starts up.
Notes:
If the server is not installed as a service, the server will
automatically start up when a client (such as MatrikonOPC
Explorer) first tries to connect to it.
If the server is installed as a service, users can choose to run it
as an application by re-registering the OPC server executable
using the /REGSERVER command-line switch.
16
Description
Displays the configuration control panel.
Configure
Shutdown
About
Control Panel
Note: If the server is installed as a Windows service, the Control Panel is not available.
The Control Panel displays the servers status, system time, and number of clients connected to
the server. The Control Panel allows users to:
Access the Configuration window.
Access the About screen.
Execute the command to shut down the server.
The Control Panel stays on top of every other window on the desktop to help monitor the status
of the server.
To view the Control Panel:
1. Right-click your mouse on the Matrikon logo
17
5. To window shade the Control Panel so that it displays only the client count, double-click
your mouse on the title bar.
Table 3 describes the commands in the Tool Tray Menu.
Command
Description
Status
Time
Clients
Displays the total number of OPC clients presently connected to the server.
Configure
Shutdown
About
Displays the servers Welcome screen, which includes information about the
software.
Table 3 - Control Panel Commands
Configuration Window
Note: If the server is installed as a Windows service, the Tool Tray Menu and Control Panel are
not available. In this case, the Configuration window is then accessed via the Windows Start
menu.
The Configuration window displays a tree view of objects configured in the server. Select an
object to display its current configuration, which appears on the right-hand side of the window.
If the server runs as a local executable, it will remain running even after the main configuration
window is closed, even if no clients are connected. Displaying the control panel or main
configuration window for the server will lock it so that it will not shut down while configuration is
being performed.
If the server runs as an NT service, it will remain running so long as there are clients connected to
it. Closing the main configuration window will shut down the configuration utility, but will not
interfere with the normal operation of the server.
To view the Configuration window:
1. From the Tool Tray Menu or the Control Panel, select Configure.
2. The Configuration window (Figure 7) appears.
18
Description
Main Menu
Provides access to the File, Edit, View, Tools, and Help menus.
Main Toolbar
Current Configuration
Server Configuration
Objects under this node affect how the server communicates with the data
source.
Alias Configuration
Displays the current settings of the object presently selected in the tree.
Statistics Panel
Displays available statistics for the object presently selected in the tree:
19
Command
Description
Sent, Received, Timed Out, Retried, Failed, Overrun.
Reset Statistics
Matrikon Logo
Clients
Displays the total number of OPC clients presently connected to the server.
Server Time
The following sections describe the menus available from the Configuration window, and what
they are used for.
File Menu
Table 5 describes the File menu commands.
Command
Description
New
Clears the current configuration and starts a new one. If OPC clients are still
connected to the server, the user is prompted for confirmation before
continuing.
Open
Clears the current configuration and loads a new one from an existing file.
Displays the Open Configuration window to prompt for the file name. If
OPC clients are still connected to the server, the user is prompted for
confirmation before continuing.
Save
Save As
Export Aliases
Exports all currently configured aliases to a CSV file. Displays the Export
Aliases window to prompt for a file name.
Import Aliases
Clears all aliases and imports new ones from a CSV file. Displays the Import
Aliases window to prompt for an existing file name.
Shutdown Server
Closes the current configuration and shuts down the server after signalling
the shutdown event to all connected clients. If OPC clients are still connected
to the server, the user is prompted for confirmation before continuing.
Hides the main Configuration window. The server shuts down after a short
delay if no OPC clients are currently connected to the server.
Close
Edit Menu
Table 6 describes the Edit menu commands that appear when the currently selected object
appears under the Server Configuration node.
Command
Undo/Cant Undo
Description
Not implemented.
20
Command
Description
Delete
Define New
Displays the Insert New Object window used to create a new configuration
object under the currently selected configuration object.
Table 6 - Edit Menu Commands (Server Configuration)
Table 7 describes the Edit menu commands that appear when the currently selected object
appears under the Alias Configuration node.
Command
Undo/Cant Undo
Description
Not implemented.
Rename
Removes the currently selected alias group and all subordinate groups and
aliases.
Delete Alias
Insert Alias Group
Insert New Alias
View Menu
Table 8 describes the View menu commands.
Command
Description
Statistics
Reset Statistics
Defaults
Displays the Server Defaults window used to configure the default settings
for the various types of communication objects available in the server.
Refresh
Options
Rebuilds the tree display of the server configuration and fully expands all
branches.
Displays the Options window used to change general server options.
Table 8 - View Menu Commands
Tools Menu
Table 9 describes the Tools menu commands.
Command
DCOM Configurator
Description
Launches the Microsoft Distributed COM Configuration Properties
utility. This utility can be used to edit DCOM settings for specific COM
21
Command
Description
servers to allow client applications on remote computers to connect to the
server.
View Tags
Security Settings
Help Menu
Table 10 describes the Help menu commands.
Command
MatrikonOPC on the
Web
About
Description
Opens a link to the MatrikonOPC web site.
Displays the Welcome screen, which includes information about the
software version.
Table 10 - Help Menu Commands
Options Window
The Options window is used to edit the servers options and contains four tabs: General, General
Logging, Interface Logging, and Advanced.
General Options
The General tab allows users to edit general server options (i.e., settings).
To view the General options:
1. On the Configuration window, from the View menu, select the Options menu item.
2. The Options window appears.
3. From the Options window, select the General tab (Figure 8).
22
Description
Automatically saves the current configuration to the specified file before
shutting down, if selected.
Backup: X copies
Load configuration on
setup
Automatically loads a configuration from the specified file when starting up,
if selected.
Displays the full path of an existing file for load and save operations. Click on
Filename
Launch configuration
program on startup
Restrict items to
preconfigured aliases
Prevents OPC clients from adding items other than configured aliases, if
selected. Selecting this option will cause clients to see only aliases when
23
Field
only
Description
browsing this server.
Note: As is the case with any changes to General options, if this option is
changed you will need to restart the server for the change to take effect.
Table 11 - General Options Tab Components
Note: The server loads these settings from the Windows registry upon start-up. Changes to the
General options settings take effect when the server is restarted.
24
Field
Enable activity
logging
Description
Enables/disables general activity logging at the specified detail level (High,
Medium, Low, or None), if selected.
Note: This option should not be selected unless users are debugging a
problem as this will have a negative effect on performance of the OPC server.
Always set this back to None when not in use.
Purges the file buffer after each message is logged in the event of an
unexpected server shut down.
Overwrites the old log file each time the server starts up, if selected.
Otherwise, rename the old log file with a (*.bak) suffix.
Displays the full path for the general activity log file. Click on the ellipsis
General Activity
Logging Filename
button (
Filter String
Filtering Filename
Displays the full path for the filtered log file. Click on the ellipsis button (
display the Open window used to select an existing file name.
) to
25
Description
Enable logging
Purges the file buffer after each message is logged in the event of an
unexpected server shut down.
Table 13 - Interface Logging Options Tab Components
Note: Interface Logging options settings take effect when the next OPC client connects to the
server.
Advanced Options
The Advanced tab allows users to view and edit advanced server options.
MatrikonOPC Server for Omron PLCs v1.2.0 Users Manual
26
Description
Time granularity
This is the rate (in milliseconds) at which the Alias features subscribe
27
Field
Description
to underlying data items. This rate is used by the Alias Events
features and by the Expression and Calculation engines when other
tags are referenced in the expressions.
Default = 1000.
Selecting this checkbox this will allow the server to accept Dynamic
Data Exchange (DDE) connections.
Note: The server loads these settings from the Windows registry on start-up. Changes to
Advanced options settings take effect when the server is shut down and restarted.
Server Configuration
The server requires minimal configuration for it to run properly. You can customize the servers
behaviour as required. This section shows you how to create and edit objects, using the
Configuration window.
Creating Objects
The Insert New Object and Create New windows are used to create Omron PLCs device link
objects.
Table 15 describes the types of objects that are available for insertion as a child in the Insert New
Object window, depending on which object is currently selected.
Selected Object
HostLink Network
Redundancy Group
28
Selected Object
Ethernet Network
FINS Connection
<None>
C-mode Connection
FINS Connection
HostLink Network
C-mode Connection
<None>
FINS Connection
<None>
Redundancy Group
<None>
Table 15 - Insert New Object Window Options
icon.
29
The following sub-sections contain information on the types of objects available and how to
configure them.
Table 16 describes the components of the Create New Ethernet Network window.
Component
Description
Name
Name of the object, which becomes an element of the item ID for data items
under the object.
Automatically converted to title case for display purposes.
Enabled
Description
This field is optional, takes any user-defined text (64-character maximum) for
documentation purposes.
By default, this field is blank.
30
Component
Description
Network Adapter
Allows you to select, from the drop-down list, the network adapter to sue for
communication on the Ethernet network.
Port Number
Allows you to enter the port number to use for communication on the Ethernet
network. This port is used to receive incoming UDP messages.
Default = 9600.
OK
Select this button to save any changes and close the window.
Cancel
Select this button to close the window without saving any changes made.
Table 16 - Create New Ethernet Network Window Components
icon.
31
General Tab
Figure 15 displays the General tab. The tab components are described in Table 17.
32
Component
Description
Name
Name of the object, which becomes an element of the item ID for data items
under the object. Automatically converted to title case for display purposes.
Note: This information stays consistent across all tabs.
Enabled
Description
This field is optional, takes any user-defined text (64-character maximum) for
documentation purposes.
By default, this field is blank.
Note: This information stays consistent across all tabs.
IP Address
Allows you to enter the IP address of the PLC. This address should be
accessible from the network adapter specified in the parent Ethernet Network
link.
Default = 0.0.0.0.
33
Component
Description
Allows you to select, from the drop-down list, the FINS mode to use when
communicating with the PLC. The accepted values are Detect Mode, CV or
CS/CJ.
Default = Detect Mode.
FINS Mode
Allows you to select, from the drop-down list, the transport layer to use when
communicating with the PLC. The accepted values are UDP and TCP.
Transport
Default = UDP.
Model
Displays the model of the PLC. This field is read-only and is automatically
populated by the OPC server.
Port
Allows you to enter the destination port number to use when communicating
with the PLC.
Default = 9600.
Maximum Gap
Allows you to enter the maximum number of bytes allowed between two
memory addresses before splitting the request into multiple requests.
Default = 100.
Table 17 - Create New Ethernet FINS Connection Window (General Tab) Components
Timing Tab
Figure 16 displays the Timing tab. The tab components are described in Table 18.
34
Component
Description
Allows you to enter the number of milliseconds (to a maximum of 60000) to
wait before a timeout occurs.
Default = 1000.
Timeout
Retry Delay
Retries
Allows you to enter the amount of time to wait after a timeout before
resending the request.
Default = 10.
Allows you to enter the number of times (to a maximum of 99) a read request
is resent when communication timeouts occur.
Default = 3.
Table 18 - Create New Ethernet FINS Connection Window (Timing Tab) Components
35
FINS Tab
Figure 17 displays the FINS tab. The tab components are described in Table 19.
Component
Source
Network
Address
Description
Allows you to enter the network address number of the machine running the OPC
server (also called SNA in Omron FINS documentation). Valid values are from 0 to
127 where 0 means the local network.
Default = 0.
Note: Do not use 0 if the data will be routed to a different network.
Allows you to enter the node number of the machine running the OPC server (also
called SA1 in Omron FINS documentation). Valid values are from 0 to 254.
Source Node
Source Unit
If the destination PLC is using automatic address generation, this number must be
set to the last three digits of the machines IP address. For example, if the IP address
of the machine is 192.168.1.150 then the value should be 150.
Default = 0.
Allows you to enter the source unit number (also called SA2 in Omron FINS
documentation). Valid values are from 0 to 31.
Default = 0.
36
Component
Destination
Network
Address
Destination
Node
Destination
Unit
Description
Allows you to enter the network address number of the PLC (also called DNA in
Omron FINS documentation). Valid values are from 0 to 127 where 0 means the
local network.
Default = 0.
Note: Do not use 0 if the data will be routed to a different network.
Allows you to enter the network number of the PLC (also called DA1 in Omron FINS
documentation). Valid values are from 0 to 255.
Default = 0.
Allows you to enter the device unit number (also called DA2 in Omron FINS
documentation). Valid values are from 0 to 255.
Default = 0.
Table 19 - Create New FINS Connection Window (FINS Tab) Components
Notes:
When the transport mode is set to TCP, the FINS source and
destination node numbers that should be used with this TCP
connection are automatically retrieved from the PLC. Please
refer to the Omron FINS documentation for more details about
how the FINS node numbers are allocated by the PLC for each
TCP connection.
When switching the transport mode from TCP to UDP, please
change the FINS parameters accordingly.
To create an Ethernet FINS Connection object:
1. Once an Ethernet Network object has been created, select it in the tree view panel on the
Configuration window.
Note: For more information on creating/configuring an Ethernet Network object, refer to
Creating and Configuring an Ethernet Network.
2. Right-click your mouse and select Define New from the menu that appears, or
Select the Define New menu option from the Edit menu, or
Click on the
icon.
37
4. From the displayed list, select the FINS Connection object type.
5. Click on the OK button.
6. The Create New window appears (Figure 15).
Note: The item selected in the Insert New Object window determines which Create New
window is displayed. For example, when FINS Connection is selected, then the Create
New FINS Connection window is displayed.
7. From the Create New window, enter a name for the object.
Note: An error message is displayed when a valid name is not entered. If the entered name
is a duplicate of an existing object, the new object will not be created. The Description
field is optional.
8. Edit the configuration components as desired.
Note: For the object to be used for communication, it must be enabled (i.e., the Enabled
checkbox is selected). This can be done at any time.
9. Click on the OK button. The object is created and appears as a child of the Ethernet
Network item as shown in Figure 19.
38
Component
Description
Name
Name of the object, which becomes an element of the item ID for data items
under the object. Automatically converted to title case for display purposes.
Note: This information stays consistent across all tabs.
Enabled
Use this checkbox to enable (i.e., checkbox is selected) or disable (i.e., checkbox
is cleared) communication for the object.
By default, the checkbox is selected.
Note: This information stays consistent across all tabs.
Description
This field is optional, takes any user-defined text (64-character maximum) for
documentation purposes.
By default, this field is blank.
Note: This information stays consistent across all tabs.
Port
Allows you to select, from the drop-down list, the serial port the device is using
to communicate on the HostLink network.
Baud Rate
Allows you to select, from the drop-down list, the communication rate. Accepts
values between 110 and 256000.
39
Component
Description
Default = 9600.
Allows you to select, from the drop-down list, the type of parity to be used.
Accepts None, Odd, Even, Mark, and Space.
Default = Even.
Parity
Allows you to select, from the drop-down list, the number of data bits. Accepts
between 4 and 8.
Data Bits
Default value = 8.
Allows you to select, from the drop-down list, the number of stop bits. Accepts 1,
1.5, and 2.
Default = 1.
Stop Bits
Discover CMode
Compliant Devices
OK
Cancel
Table 20 - Create New HostLink Network Window (Serial Port Tab) Components
Timing Tab
Figure 21 displays the Timing tab. The tab components are described in Table 21.
40
Component
Description
Reply Timeout
Allows you to enter the number of seconds (to a maximum of 3600) to wait
between two consecutive connection attempts.
Default = 60.
Retries
41
Component
DSR Flow Control
CTS Flow Control
Description
Enables/disables Data Set Ready flow control.
Default = disabled (i.e., checkbox is cleared).
Enables/disables Clear To Send flow control.
Default = disabled (i.e., checkbox is cleared).
DSR Sensitivity
XON\XOFF Flow
Control
RTS Control
Number of milliseconds (to a maximum of 1000) for rise delay. This option is
only available when RTS Control set to Enable.
DTR Control
42
Component
RTS Drop Delay
Description
Number of milliseconds (to a maximum of 1000) for drop delay. This option is
only available when RTS Control set to Enable.
Table 22 - Create New HostLink Network Window (Advanced Options Tab) Components
icon.
43
General Tab
Table 23 describes the General tab components displayed in Figure 24.
Component
Name
Enabled
Description
Name of the object, which becomes an element of the item ID for data items
under the object. Automatically converted to title case for display purposes.
Note: This information stays consistent across all tabs.
Use this checkbox to enable (i.e., checkbox is selected) or disable (i.e.,
checkbox is cleared) communication for the object.
By default, the checkbox is selected.
Note: This information stays consistent across all tabs.
44
Component
Description
Description
This field is optional, takes any user-defined text (64-character maximum) for
documentation purposes.
By default, this field is blank.
Note: This information stays consistent across all tabs.
Model
Device ID
The HostLink protocol supports up to 32 devices, each device has its own
unique ID (i.e., unit number). The Device ID range is from 0 to 31.
Default = 0.
OK
Select this button to save any changes and close the window.
Note: This information stays consistent across all tabs.
Cancel
Select this button to close the window without saving any changes made.
Note: This information stays consistent across all tabs.
Table 23 - Create New C-Mode Connection Window (Serial Port Tab) Components
Timing Tab
Figure 25 displays the Timing tab. The tab components are described in Table 24.
45
Component
Description
Reconnect Delay
Allows you to specify the number of seconds (to a maximum of 3600) to wait
between two consecutive connection attempts.
Default = 10.
Allows you to specify the number of retries (to a maximum of 10) if
communication timeouts occur.
Retries
Default = 3.
Table 24 - Create New C-Mode Connection Window (Timing Tab) Components
Component
Description
Enable reading
optimization
Enable writing
46
Component
optimization
Description
multiple items.
By default, this checkbox is cleared.
Allows you to indicate the maximum items in a single request. Set to 0 means
no restriction.
Default = 0.
If this option is selected, the data is simulated instead of read from the device.
This feature can be used when access to devices is not available.
By default, this checkbox is cleared.
Table 25 - Create New C-Mode Connection Window (Advanced Options Tab) Components
icon.
4. From the displayed list, select the C-Mode Connection object type.
5. Click on the OK button.
6. The Create New window appears (Figure 24).
Note: The item selected in the Insert New Object window determines which Create New
window is displayed. For example, when C-Mode Connection is selected, then the Create
New C-Mode Connection window is displayed.
7. From the Create New window, enter a name for the object.
Note: An error message is displayed when a valid name is not entered. If the entered name
is a duplicate of an existing object, the new object will not be created. The Description
field is optional.
8. Edit the configuration components as desired.
MatrikonOPC Server for Omron PLCs v1.2.0 Users Manual
47
Note: For the object to be used for communication, it must be enabled (i.e., the Enabled
checkbox is selected). This can be done at any time.
9. Click on the OK button. The object is created and appears as a child of the HostLink
Network item as shown in Figure 28.
General Tab
Figure 29 displays the General tab. The tab components are described in Table 26.
48
Component
Description
Name
Name of the object, which becomes an element of the item ID for data items
under the object. Automatically converted to title case for display purposes.
Note: This information stays consistent across all tabs.
Enabled
Description
This field is optional, takes any user-defined text (64-character maximum) for
documentation purposes.
By default, this field is blank.
Note: This information stays consistent across all tabs.
FINS Mode
Allows you to select, from the drop-down list, the FINS mode to use when
communicating with the PLC. The accepted values are Detect Mode, CV or
CS/CJ.
Default = Detect Mode.
49
Component
Description
Model
Displays the model of the PLC. This field is read-only and is automatically
populated by the OPC server.
Maximum Gap
Allows you to enter the maximum number of bytes allowed between two
memory addresses before splitting the request into multiple requests.
Default = 100.
OK
Select this button to save any changes and close the window.
Note: This information stays consistent across all tabs.
Cancel
Select this button to close the window without saving any changes made.
Note: This information stays consistent across all tabs.
Table 26 - Create New FINS Connection Window (General Tab) Components
Timing Tab
Figure 30 displays the Timing tab. The tab components are described in Table 27.
50
Component
Description
Allows you to enter the number of milliseconds (to a maximum of 60000) to
wait before a timeout occurs.
Timeout
Default = 1000.
Inter Connect Delay
Retry Delay
Allows you to enter the amount of time to wait after a timeout before
resending the request.
Default = 10.
Retries
Allows you to enter the number of times (to a maximum of 99) a read request
is resent when communication timeouts occur.
Default = 3.
Table 27 - Create New HostLink FINS Connection Window (Timing Tab) Components
FINS Tab
Figure 31 displays the FINS tab. The tab components are in Table 28.
51
Component
Source
Network
Address
Description
Allows you to specify the network address number of the machine running the OPC
server (also called SNA in Omron FINS documentation). Valid values are from 0 to
127 where 0 means the local network.
Default = 0.
Note: Do not use 0 if the data will be routed to a different network.
Source Node
Allows you to specify the node number of the machine running the OPC server (also
called SA1 in Omron FINS documentation). Valid values are from 0 to 254.
Default = 0.
Source Unit
Destination
Network
Address
Allows you to specify the source unit number (also called SA2 in Omron FINS
documentation). Valid values are from 0 to 31.
Default = 0.
Allows you to specify the network address number of the PLC (also called DNA in
Omron FINS documentation). Valid values are from 0 to 127 where 0 means the
local network.
Default = 0.
Note: Do not use 0 if the data will be routed to a different network.
52
Component
Destination
Node
Destination
Unit
Description
Allows you to specify the network number of the PLC (also called DA1 in Omron FINS
documentation). Valid values are from 0 to 255.
Default = 0.
Allows you to specify the device unit number (also called DA2 in Omron FINS
documentation). Valid values are from 0 to 255.
Default = 0.
Table 28 - Create New HostLink FINS Connection Window (FINS Tab) Components
icon.
4. From the displayed list, select the FINS Connection object type.
5. Click on the OK button.
6. The Create New window appears (Figure 29).
Note: The item selected in the Insert New Object window determines which Create New
window is displayed. For example, when FINS Connection is selected, then the Create
New FINS Connection window is displayed.
7. From the Create New window, enter a name for the object.
Note: An error message is displayed when a valid name is not entered. If the entered name
is a duplicate of an existing object, the new object will not be created. The Description
field is optional.
8. Edit the configuration components as desired.
Note: For the object to be used for communication, it must be enabled (i.e., the Enabled
checkbox is selected). This can be done at any time.
MatrikonOPC Server for Omron PLCs v1.2.0 Users Manual
53
9. Click on the OK button. The object is created and appears as a child of the HostLink
Network item as shown in Figure 33.
54
The Create New Redundancy Group window (Figure 34) displays the settings available for
configuring a Redundancy Group object.
Mode
Description
Classic
All device links are connected. Items are added only to the active device
link, but are not removed when a fail over occurs. As failovers occur and
cause multiple device links to become active, the collection state becomes
the same as Hot.
Hot
All device links are connected. When items are added they are added to all
device links in the redundancy group. This means that all device links are
actively collecting all the time.
Warm
All device links are connected. When items are added they are added to
the active device link. When a failover occurs the items will be removed
from the formerly active device link.
Cold
Only the active device link is connected. When items are added they are
added to the active device link. When a failover occurs the items will be
removed from the formerly active device link.
Note: When a device link is a member of a Cold mode redundancy group
and not the active device link, then all communication through that
device link is disabled.
Table 29 - Redundancy Modes
55
Table 30 describes the components of the Create New Redundancy Group window.
Component
Name
Description
Allows you to enter the name of the device link, which becomes an
element of the item ID for data items. The full path of the device link must
be entered.
Automatically converted to title case for display purposes.
Enabled
Description
Allows you to enter a value to define how often (in milliseconds) to check
connected device links to make sure they are still actively communicating
with a device.
Default = 5000 ms.
56
Component
Description
Connection Period
Allows you to enter a value to define how often (in milliseconds) to check
connections that have failed (i.e., communication is down) to determine if
connections have been restored.
Default = 1000 ms.
Mode
Allows you to select, from the drop-down list, the style (Classic, Hot,
Warm, Cold) of redundancy management that should be used by this
group.
Subscriptions
This section of the General tab displays those device links defined as part
of this particular redundant set, and the priorities of the device links. The
Subscriptions section contains the following fields and buttons which are
described below: Device Link Name, Priority, Add, Delete.
Allows you to enter the name of the device link that is going to be added.
Priority
Allows you to select a priority (High, Medium, or Low) for the current
device link from the drop-down list. Device links of higher priority are
preferred to lower priority device links.
Add
After entering a Device Link Name and selecting a Priority, use the Add
button to add the device link to the list of redundant device links that
appears at the bottom of the General tab.
Note: Once you have added a device link, you can make changes to it or
delete it (see Delete for more information). To update a device link, from
the list, highlight the one you want to change. Notice that the Add button
now reads Update. Make the necessary changes and click on the Update
button.
Delete
From the list of redundant device links that appears at the bottom of the
General tab, select the device link you want to remove and click on the
Delete button to delete it from the list.
OK
Select this button to save any changes and close the window.
Cancel
Select this button to close the window without saving any changes made.
Table 30 - Create New Redundancy Group Window Components
icon.
57
6. From the Create New window, enter a name for the object.
Note: An error message is displayed when a valid name is not entered. If the entered name
is a duplicate of an existing device link, the new device link is not created. The Description
field is optional.
7. Edit the configuration components as desired.
Note: For the object to be used for communication, it must be enabled (i.e., the Enabled
checkbox is selected). This can be done at any time.
8. Click on the OK button. The object is created and appears as a child of the Server
Configuration item as shown in Figure 35.
Changing Objects
To change an objects configuration:
1. Once an object is created, select it in the tree view (i.e., Current configuration) panel.
2. In the configuration panel (i.e., pane on the right), make the applicable changes.
3. Click on the Apply button to accept the changes, or click on the Cancel button to discard
them.
Removing Objects
Note: Users can easily remove any object that they have created, but a warning message (Figure
36) will appear when users remove an object that has data items to which one or more OPC clients
hold reference.
58
To remove an object:
1. In the Configuration window, under Server Configuration, select the object to be
removed.
2. From the Edit menu, select the Delete menu option (or click on the
button).
Note: If one or more OPC clients hold references to data items somewhere under the
selected object, a warning message (Figure 36) appears.
3. To mark the object for later deletion, click on the Yes button. To leave the object
unmodified, click on the No button.
Note: Items marked for deletion are disabled and a red X appears over the icon on the right
side of the window when the object is selected.
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.
button.
59
button.
Description
Name
Allows you to enter a name for the alias (which must be unique within
the alias group).
Basic Alias
A basic alias is an alias that renames a data item in the server and
optionally allows the configuration of simple scaling. This Alias type is
typically used when trying to simplify a servers address space.
Item Path
Fully-qualified item ID for the OPC item to which the alias refers. Click
60
Component
Description
on the Browse button to display the Item Path Browser window
used to select an existing OPC item on the server.
Note: If Events are enabled, the alias creates a data subscription to
the configured item at the Alias Subscription Rate. This rate is
configured in the Advanced Options window.
Equation
The equation to apply to calculate the data value of the alias. Use the
Insert Item button to display the Item Path Browser window used
to select an existing OPC item on the server and insert a reference
into the equation.
A Holding Register Alias is a data item that is not associated with any
data items in the server. These registers can be read from and
written to like any other data item. Typically Holding Register Aliases
are used as temporary data locations or for configuration testing
during system deployment.
Data Type
The canonical data type of the holding register. All values written to
this alias will be converted to this data type. By default, clients will be
sent data as this data type.
Initial Value
Save
Cancel
Discards changes to (abandon creation of) the alias and closes the
window.
Table 31 - Insert New Alias Window Alias Type Options
Component
Data Type
Description
Allows you to select, from the drop-down list, the value of the OPC
item to the specified type unless Default is selected. Also serves as
the canonical data type for the alias.
61
Component
Description
Default = (Default).
Allows you to enter a value defining the update rate (in milliseconds)
to use with the Poll when inactive option.
Default = 0.
Update Rate
Note: This option is not available for Calculation aliases, as they are
read-only.
By default, this checkbox is cleared.
If selected, continues updating the value for the alias at the specified
update rate even if there are no OPC clients currently accessing the
alias.
Editing Aliases
Note: Aliases can be edited after they have been created using the Edit Alias window. This is
virtually the same as the Insert New Alias window (Figure 37) with the exception that it appears
after the alias has been created.
62
To edit an alias:
1. On the Configuration window, select the alias you want to change, and then double-click
or press Enter.
2. The Edit Alias window appears.
3. Make the changes as required.
Removing Aliases
Note: Any alias that was created can be removed.
To remove an alias:
1. On the Configuration Window, select one or more aliases that you want to remove.
2. From the Edit menu, choose the Delete Alias menu option.
3. The alias is removed.
button.
Exporting Aliases
Note: Use the Export Aliases window to export all currently configured aliases to a CSV file.
To export all currently configured aliases:
1. From the File menu, select the Export Aliases menu option or click on the
button.
Importing Aliases
Note: Use the Import Aliases window to clear all aliases and import new ones from a CSV file.
The CSV file format does not support event generation settings. All imported aliases will be
configured to not generate events.
To import aliases from a CSV file:
1. From the File menu, select the Import Aliases menu option or click on the
button.
63
Table 33 describes the Scaling Options for the Configure Scaling window.
Selection
Linear and
Square Root
Gain/Offset
Component
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.
Gain
Offset
Scaling offset.
Simple text equation to apply to incoming values (reads). Click on the
Input
Expression
Output
64
Notes:
The data type for scaled values is double-precision real unless
the alias data type is specified.
Using invalid settings, such as zero-zero for the high-low
range in Linear scaling, may be fatal to the server, OPC
clients, and communications.
The OPC item values must be numeric for Linear, Square
Root, and Gain/Offset scaling to work.
The OPC item values must be non-negative for Square Root
scaling to work. Otherwise, the scaled value will be -1 with a
bad quality.
The server may be unable to load configuration files containing
invalid scaling expressions, and may fail to start up properly. If
this occurs, rename the configuration file so that the server will
not load it upon start-up. Alternatively, edit the XML file to
correct the invalid alias settings.
65
Description
Source
Allows you to enter the name of the source of the event. By default,
this field is the Alias Group name, or if there is no Alias Group then
the Alias name.
Category
Allows you to select from the drop-down list, the event category
under which the event is to be registered. Select either the New
Category or Edit Category option to configure the registered
categories in the server. For more information, refer to the
Configure Categories section for more information.
Severity
Allows you to enter a value defining the severity of the alarm. The
allowable range is 1 through 1000.
Message
66
Component
Description
configured in the Advanced Options window.
Table 34 - Generate Events Window Options
Configure Categories
The New Category window (Figure 41) is presented when you choose to add a new category to
the server from the Generate Events window (Figure 40).
Description
Category ID
Name
Description
The Edit Categories window is displayed when you choose to edit categories from the Generate
Events window (Figure 40).
67
When presented with the Edit Categories window, select the category to edit and click the Edit
button. This causes the Edit Category window to appear which is virtually identical to the New
Category window.
Note: Some categories cannot be edited. These categories are marked as Read Only and can be
viewed, but not edited. From the Edit Categories window, if you wish to view existing category
details, select the required category. Click on the View button. The View Category window is
displayed, which again, is virtually identical to the New Category window.
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 36 describes the Expression Wizard fields.
68
Component
Description
Input/Output Expression
Database field
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
Validate
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 36 - Expression Wizard Options
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.
To create an Input or Output Expression:
1. On the Configuration window, select Alias Configuration or a previously configured Alias
Group.
2. The Contents table for that alias group is displayed on the right side of the Configuration
window, listing the aliases it contains.
3. Either create a new alias (for instructions, refer to Inserting New Aliases), or
Double-click your mouse on an existing alias, or
Click on the Edit the selected alias item (
) button.
69
7. Click on the Configure button adjacent to the Input field (or Output field).
8. The Expression Wizard (Figure 44) is displayed.
9. Manually enter your new expression in the Input/Output Expression field and proceed to
step 14.
Or,
Perform steps 9 through 13 using a combination of the Function, Variable, and Operators
buttons to create your expression, which will be displayed in the Input/Output
Expression field as you build it.
10. Click on the Function button to go to the Select function (Figure 45) window. After
selecting the required function, click on the Continue button to close the Select function
window and return to the Expression Wizard.
70
11. Click on the Variable button to go to the Select variable (Figure 46) window. After
selecting the required variable, click on the OK button to close the Select variable window
and return to the Expression Wizard.
12. If required, from the Select variable window, click on the Modify variables button to
access the User Defined Functions Editor (Figure 47) which allows you to add, change,
or delete variables.
71
13. The Operators buttons (Figure 48) allow you to enter an operation descriptor based on the
selected button.
14. Click on the Validate button to determine whether or not the expression is valid.
15. If the expression is valid (i.e., a confirmation message is displayed), click on the OK button
to close the message window and return to the Expression Wizard screen.
16. Click on 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.
17. From the Edit Alias window, click on the Save button.
18. The Edit Alias window closes and you are returned to the Configuration window.
Description
Branch Hierarchy
Displays the branch hierarchy of the OPC server when browsing actions
are being performed. The +/- symbols can be used to display/hide the
branches below the specified branch. Left-clicking a branch displays its
leaves in the Leaf List component.
Leaf List
OK
Select this button to add the selected item from the Leaf List to the
Input/Output component of the Insert New Alias form.
Cancel
Select this button to exit the Item Path Browser without adding any
72
Component
Description
item paths.
Select this button to refresh the browsing hierarchy in the Branch
Hierarchy component.
Refresh
Saving a Configuration
Note: When the server configuration is complete, use the Save Configuration window to save the
configuration to an XML file.
To save a configuration to an XML file:
1. From the File menu, select the Save As menu option or click on the
(alternatively, users can choose Save or click
).
button
Clearing a Configuration
Note: Starting a new configuration will clear the existing one.
To clear a configuration:
1. From the File menu, choose the New menu option or click on the
button.
2. If OPC clients are still connected to the server, a warning message appears.
3. Click OK.
4. The configuration is cleared.
button.
73
6. Click OK.
7. The old configuration is cleared and the new configuration is loaded from the file.
74
Field
Description
Network Name
Connection Name
Area
Offset
Bit
Start
Length
Count
Table 38:
Network Name/Connection Name/Area<Offset>
Network Name/Connection Name/Area<Offset>.Bit
C-Mode connections allow the user to sum a specific range of bits from an item and the format is:
Network Name/Connection Name/Area<Offset>:Start,Length
C-Mode connections also allow the user to read consecutive addresses and return them as an OPC
Array by using the following syntax:
Network Name/Connection Name/Area<Offset>[Count]
Statistical and control items can also be added, where the format is as follows:
Network Name/Item Name
Network Name/Connection Name/Item Name
MatrikonOPC Server for Omron PLCs v1.2.0 Users Manual
75
Field
Description
Network Name
Connection Name
Area
Offset
Bit
Start
Length
Count
Examples
Examples of valid item syntax can be found in Table 39.
Syntax
Description
HostLink/C-mode/CIO0000
Network/FINS/CIO0000.0
Access the first bit as a Boolean in area type CIO at offset 0000.
HostLink/C-mode/CIO0000:0,2
Access the first and second bit as an array in area type CIO at
offset 0000.
Table 39 - Item Syntax Examples
Auxiliary Relay
CIO
Counter
Counter Status
Data Memory
Data Type
Access Right
Word
Read Only
Word
Read-Write
Boolean
Read Only
Boolean
Read-Write
Word
Read-Write
Boolean
Read-Write
Word
Read-Write
Byte
Read-Write
Word
Read-Write
76
D00000.0-D32767.15(1)
DM00000.0-DM32767.15(1)
Boolean
Data Register
DR00-DR15
Word
Read-Write
Expansion
Memory
(current bank)
CEM00000- CEM32767
Word
Read-Write
Boolean
Read-Write
Expansion
Memory
EM000000- EMC32767
Word
Read-Write
Boolean
Read-Write
CEM00000.0- CEM32767.15
EM000000.0- EMC32767.15(1)
Holding Relay(1)
Index Register
Task Flag
H0000-H0511
HR0000-HR0511
Word
(1)
IR00-IR15(1)
TK00-TK31
(1)
(1)
TKS00-TKS31
Read-Write
Boolean
Read Only
Byte
Read Only
Word
Read-Write
Byte
Read-Write
Word
Read-Write
Boolean
Read-Write
(1)
TIM0000-TIM4095
Timer Status
Working Relay(1)
TS0000-TS4095
TIMS0000-TIMS4095
W0000-W0511(1)
WR0000-WR0511(1)
W0000.0-W0511(1)
WR0000.0-WR0511(1)
Read-Write
Word
T0000-T4095
Timer
Read-Write
Auxiliary
Relay
CIO
Data Type
Access
Right
AR000-AR447
Word
Read Only
AR448-AR959
Word
Read-Write
AR000.0-AR959.15
Boolean
Read Only
CIO0000-CIO6143
Word
Read-Write
77
CIO0000.0-CIO6143.15
Boolean
Read-Write
Counter
CNT0000.PVCNT2047.PV
Word
Read-Write
Counter
Status
CNT0000.STACNT2047.STA
Word
Read Only
CNT0000.SVCNT2047.SV
CNT0000:0000.SVCNT2047:9999.SV
CNT0000:10000.SVCNT2047:1000000.SV
Word
Read-Write
String
Read-Write
String
Read-Write
Counter Wait
SV1
CNTW0000.SVCNTW2047.SV
Word
Read-Write
Counter Wait
SV2
CNTW0000:0000.SVCNTW2047:9999.SV
String
Read-Write
Counter Wait
SV3
CNTW0000:10000.SVCNTW2047:1000000.SV
String
Read-Write
DM0000-DM9999
Word
Read-Write
Boolean
Read Only
Word
Read-Write
Boolean
Read-Write
Word
Read-Write
Boolean
Read-Write
IR0000-IR0019
Word
Read-Write
IR0200-IR0252
Word
Read-Write
IR0253-IR255
Word
Read Only
Boolean
Read Only
Word
Read-Write
Boolean
Read-Write
Counter SV1
Counter SV2
Counter SV3
Data Memory
Holding Relay
LR
IR
SR
DM0000.0-DM9999.15
HR0000-HR0511
HR0000.0-HR0511.15
LR0000-LR0199
LR0000.0-LR0199.15
IR0000.0-IR0019.15
IR0200.0-IR0252.15
IR0253.0-IR255.15
SR0000-SR0019
SR0200-SR0255
SR0000.0-SR0019.15
SR0200.0-SR0255.15
Timer
TIM0000.PVTIM2047.PV
Word
Read-Write
Timer Status
TIM0000.STATIM2047.STA
Word
Read Only
Timer SV1
TIM0000.SVTIM2047.SV
Word
Read-Write
Timer SV2
TIM0000:0000.SVTIM2047:9999.SV
String
Read-Write
Timer SV3
TIM0000:10000.SV-
String
Read-Write
78
TIM2047:1000000.SV
Timer Wait
SV1
TIMW0000.SVTIMW2047.SV
Word
Read-Write
Timer Wait
SV2
TIMW0000:0000.SVTIMW2047:9999.SV
String
Read-Write
Timer Wait
SV3
TIMW0000:10000.SVTIMW2047:1000000.SV
String
Read-Write
Totalizing
Timer SV1
TTIM0000.SVTTIM2047.SV
Word
Read-Write
Totalizing
Timer SV2
TTIM0000:0000.SVTTIM2047:9999.SV
String
Read-Write
Totalizing
Timer SV3
TTIM0000:10000.SVTTIM2047:1000000.SV
String
Read-Write
High Speed
Timer SV1
TIMH0000-TIMH2047
Word
Read-Write
High Speed
Timer SV2
TIMH0000:0000.SVTIMH2047:9999.SV
String
Read-Write
High Speed
Timer SV3
TIMH0000:10000.SVTIMH2047:1000000.SV
String
Read-Write
Notes:
Writing to the registers is only possible when the PLC is in Monitor or
Programming Mode.
The ranges mentioned in the examples above differs by PLC type.
Control Items
The MatrikonOPC Server for Omron PLCs supplies control items to allow a connected OPC client to
obtain status information by reading values and manipulating its operation by simply writing
values.
Description
Default
FALSE
$Connected
$Enabled
FALSE
Writing any value to this item will trigger the OPC Communication
statistics for the Ethernet Network object, as well as all of the
underlying connections, to be reinitialized.
FALSE
$ResetStats
79
Description
Default
FALSE
$Connected
$Enabled
FALSE
$ResetStats
Writing any value to this item will trigger the OPC Communication
statistics for the connection to be reinitialized.
FALSE
Indicates the time based on the PLCs clock. Writing now (quotes
not included) sets the PLCs clock to the OPC servers host machine
time.
Blank
$Clock
Description
Default
$Connected
FALSE
$Enabled
FALSE
$AutoDiscovery
FALSE
#OfflineMode
FALSE
Description
Default
$Connected
FALSE
$Enabled
FALSE
$ClearForced
FALSE
#OfflineMode
FALSE
Statistical Items
The server supplies statistical information pertaining to communication in the form of real-time
data items for the Network Device Link, and each connection.
80
Description
Default
#Sent
#Received
#Retried
#Failure
#Overrun
#Timeout
Description
Default
#Sent
#Received
#Retried
#Failure
#Overrun
Total number of times that a scheduled poll has come due a second
time before it has yet been sent and cleared from the due list.
#Timeout
#Latency
#Mode
The PLCs current mode. PROGRAM, MONITOR and RUN are the
possible values.
Blank
Indicates the most serious error that occurred when commands were
executed. If there are no errors, it will be 0. Refer to Omron FINS
documentation for a description of the errors.
#ErrorCode
81
Item ID
Description
Default
#Description
Blank
#Message
Blank
#Mode
The current mode for the PLC. You can write a value to this item to
change the mode for the PLC.
Unknown
#UMWrite
Unknown
#Program
Unknown
The MatrikonOPC Server Framework creates a number of standard data items which can be used
for monitoring and controlling certain behaviour.
Table 49 describes the standard items available for most device links.
Field
Description
#Enabled
This is a Boolean OPC tag which indicates whether or not the Device Link to
which it belongs is enabled. If the value is True or a value of True is written
to this item then the Device Link is enabled.
#OfflineMode
Adding this item allows an OPC client to monitor the offline mode for that
location using read operations and provide the ability to toggle offline mode
for that location using write operations. For more information, refer to
Appendix G - Offline Mode.
@Connected
This is a Boolean OPC tag which indicates whether or not the Device Link is
connected to its resources. Typically True indicates that a connection of an
end device has been established.
Table 49 - Standard Data Items
Table 50 describes the standard items available for at the root branch of the server browse tree.
Field
Description
#MonitorACLFile
This is a Boolean OPC tag that has a default value of True when the server
starts which indicates that the tag security permissions are monitored and
applied while the server is running. By adding this item to an OPC group and
writing a value of False to this item, the server no longer applies tag security
configuration changes while the server is running. The server would need to
be stopped and restarted for the changes to take effect. For more
information, refer to Appendix F - Security.
@Clients
This is a read-only string item which lists the name of every client currently
connected to the OPC server.
Table 50 - Server Data Items
Table 51 describes the statistical and control items available for the Redundancy Group device link.
Field
#Manual Device Link
Description
Write to this control item to indicate which device link, of the device links to
which the Redundancy Group is subscribed, is forced to be active, whether
or not it is available. Clear the value of this control item in order to allow
82
Field
Description
the OPC server to decide which of the subscribed device links should be
active, according to their configured priorities and availabilities.
The current active device link, which will be the highest-priority of the
available device links on the Redundancy Group device links subscription
list.
@Redundancy Group
A numbered list of device links to which the Redundancy Group device link
is subscribed. They are ordered from highest to lowest priority.
Table 51 - Redundancy Device Link OPC Items
83
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 of the Options dialogue in the main configuration
window 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 Matrikon 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.
84
Limitations
The MatrikonOPC Server for Omron PLCs has the following limitations when using C-Mode
commands:
1. WR area words - WR area words cannot be read or written.
2. Timers - timers 2048 to 4095 and counters 2048 to 4095 cannot be read or written.
3. D10000 to D32767 and E10000 or E32767 - cannot be read or written.
4. SV SV can be read and written only in cyclic task 0. Also, timer SV can be read and
written only when the timer number is not indirectly addressed.
5.
WARNING! There is always potential risk involved when writing to memory areas
within a PLC as this could cause unpredictable issues.
6. The OPC server has not been tested with CV mode-compatible PLCs.
7. Expansion modules are not supported.
Refer to the MatrikonOPC Server for Omron PLCs Release Notes for known issues.
85
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:
For our installations to work correctly, the install must be able to access the
C:\WINDOWS\system32 directory to add, use, and remove the file called
aprxdist.exe and add the file opcenum.exe.
Generally, we will see this error on Windows 2003 SP1 system where this is not
possible. To resolve the issue, download these files, and place them in
C:\WINDOWS\system32, and rerun the install.
Solution:
For MatrikonOPC software to install correctly, you must be logged in as a user with
access to the registry. If you are not an Administrator on the system, the installation
will not be able to register the software correctly.
PSTCFG error
Problem:
After my OPC server died, I tried to access the Configuration screen and now I am
experiencing access violations and PSTCFG errors.
Solution:
If your OPC server process stops and you leave the PSTCFG running, when you
attempt to access the Configuration screen to do anything to your configuration
items (add, change, delete, and so on), you will experience access violations. You will
need to kill the configuration and restart the server.
Server stops updating client with item values after two hours
Problem:
The server stops updating the client with item values after two hours.
Solution:
The server may be licensed with a hardware key and the hardware key may not be
properly detected, or the software license has expired.
Alternatively, try running the MatrikonOPC Licensing utility from the shortcut menu.
Click on the Check Licenses button to see the status of all MatrikonOPC product
licenses.
Check that the correct HASP hardware key is securely fastened to the parallel port. If it
is, run the HINSTALL program that is located in the Program Files\Common
Files\MatrikonOPC\Common directory.
86
The server stops updating the client with item values after 30 days.
Solution:
The evaluation period for the license has expired. Please contact MatrikonOPC
Support.
The server automatically shuts down after five minutes when there are no clients
connected.
Solution:
This is standard behaviour for COM servers. However, this behaviour can be overridden
as shown in the following example:
Note: Microsoft highly recommends that you back up the registry
before editing it or making changes to it.
1. From the Run command, enter REGEDIT.
2. The Registry Editor (Figure 49) is launched.
3. In the Registry Editor, under HKEY_CLASSES_ROOT, look for the required
program ID (e.g., Matrikon.OPC.Simulation.1).
87
The OPC client does not provide a means to configure access paths, making it difficult
to correctly specify the data acquisition options for the items.
88
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 which would
accommodate clients that do not support access paths.
Perform the following steps as shown (with example) below:
Note: Microsoft highly recommends that you back up the registry
before editing it or making changes to it.
1. From the Run command, enter REGEDIT.
2. The Registry Editor is launched.
3. In the Registry Editor, under HKEY_CLASSES_ROOT, look for the required
program ID (e.g., Matrikon.OPC.Simulation.1).
4. Expand the program ID branch.
5. Click on the CLSID branch.
6. Record the global universal ID (GUID).
7. Under the HKEY_CLASSES_ROOT\CLSID branch, search for the GUID
retrieved in the previous step (e.g.,
HKEY_CLASSES_ROOT\CLSID\{024C7FFC-9CC3-476f-867ABC3CAD79F4FE}).
8. Create a string value called ItemIDEscapeCharacter in the Options branch
underneath the GUID (e.g., HKEY_CLASSES_ROOT\CLSID\{024C7FFC9CC3-476f-867A-BC3CAD79F4FE}\Options).
Note: To create a new value, use the context menu and select the New
String Value menu option.
9. Set the value of ItemIDEscapeCharacter to a single character, such as |
(pipe).
Note: To edit the value, select the entry and select the Modify menu option
from the Edit menu.
10. Shut down the server and restart it for the change to take effect.
11. 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 Matrikon attached to the parallel
port, but the software recognizes only the first one.
Solution:
HASP keys from the same vendor cannot be chained together. Send an email to the
MatrikonOPC Support team to obtain a HASP key containing the combined codes of all
installed MatrikonOPC servers.
89
Solution:
in the Tool
To configure the server, start the configuration utility by using the shortcut to the
OPC server in the Windows Start menu (this shortcut starts the Configuration utility
as well as the OPC server).
Note: If the server configuration utility generates an access denied
error on launch, the DCOM permissions have not been configured
properly.
OPC client unable to create or read items under configured object (device)
Problem:
The OPC client is unable to create or read items under a configured object (device).
Solution:
Check the object configuration (for more information, refer to Server Configuration).
Ensure the Enabled checkbox is selected.
The server does not retain its previous settings and needs to be reconfigured each
time it starts up.
Solution:
In the Configuration window, choose Options from the View menu. Under the
General tab, ensure that the Load configuration on start-up checkbox is selected
and that the correct file name appears in the edit box (see General Options).
Solution:
Microsoft Internet Explorer 4.01 (or later) must be installed to use the XML format.
Server does not show up in the list of locally available program IDs in OPC client
application
Problem:
The server does not show up in a list of locally available program IDs in the OPC client
application.
Solution:
Make sure that a user with local administrative rights installs the OPC server 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.
Also, especially for older OPC clients that do not use the OPC server browser, make
sure the client is running as a user that has read access to the registry.
The OPC server does not show up in a list of remotely available program IDs in my
OPC client application.
90
Solution:
Follow the steps found in Appendix A Distributed COM (DCOM) to copy the
program ID from the server machine to the client machine.
Access denied or time-out error when connecting to remove server via DCOM
Problem:
Access Denied error message appears, or time out occurs when trying to connect to
a remote OPC server via DCOM.
Solution:
Ensure that the access and launch permissions for the OPC server are set correctly on
the server machine. For more information, refer to Appendix A Distributed COM
(DCOM).
A client tries to connect to the server and fails, or the server does not start up.
Solution:
Ensure that the access and launch permissions for the OPC server are set correctly.
For more information, refer to Appendix A Distributed COM (DCOM).
The About screen and Configuration window do not show up when a remotely
connecting client or a client that runs as a service (such as the Aspen Technologies
CIMIO OPC Manager) tries to launch the OPC server.
Solution:
Either set the identity for the OPC server to the interactive user, or consider running
the server as a service. For more information, refer to Appendix A Distributed
COM (DCOM).
After installing an older OPC server, DA 2.05 asynchronous I/O no longer works.
Solution:
The old installation program installed and registered its own (older) version of the OPC
proxy/stub DLL.
Reinstall the standard OPC proxy/stub DLLs, using an up-to-date installation program
or re-register them using the REGSVR32 command-line utility (refer to the OPC
Compliance - Installation section in this manual).
Solution:
Check the servers Time Granularity settings in the servers Advanced Options.
Ensure the granularity is not set to 0. It is recommended that you not set the value
lower than 100.
Solution:
Make sure users can ping the device. Use the Start -> Run with command CMD to
bring up a command window and type:
Ping ipaddress ( e.g., C:\temp>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
91
0ms, Average =
0ms)
Where ipaddress is the IP address of the users <System X> device. If it says no
response, then there are likely network issues between users computer and the
product.
Note: Refer to the DCOM Manual to further diagnose any DCOM issues.
Aliases have been configured to generate events, but a subscribed A&E client is not
receiving events as expected.
Solution:
It is possible to disable event generation at the Alias Group level. Make sure that all of
the Alias Groups are set to have events enabled.
The OPC server is unable to establish a connection with the PLC through FINS
Connection.
If using FINS over Ethernet, ensure that the network adapter used has access
to the FINS network and that the port number is not used by any other
application.
If using FINS over Ethernet, ensure that the IP address entered matches with
the PLCs IP address and that the address is reachable through the network
adapter selected.
Ensure that the FINS parameters entered in the FINS tab are correct. Please
refer to the PLC configuration information to double-check the values entered.
OPC server is unable to validate or read some items using FINS Connection
Problem:
The OPC server is unable to validate or read some items through FINS Connection.
Solution:
Ensure that the FINS mode being currently used is correct and correspond to the PLC
mode (CV series or CS/CJ series).
Solution:
Re-register the OPC server executable using the /REGSERVER command-line switch.
92
Solution:
No, the first OPC client that tries to connect will start the OPC server.
How can I get OPC data into Microsoft Excel, Microsoft Word, or another application
with support for Visual Basic, VBA, or VB Script?
Solution:
Use the MatrikonOPC Automation Component to create a Visual Basic script that
connects to a server, creates groups and items, and receives data change updates.
Contact Support for examples of how to do this in Excel, Visual Basic, or an HTML
document.
Solution:
In order to do this, users will have to apply a mask to the value, which will null all of
the bits in the integer value except the one that users want to keep.
For example, if the user wanted to isolate the third bit, they would have to apply a
mask that is in binary which will only have the third bit present. In binary, this is the
number 4 (0100).
To apply the mask, users must use the AND operator, which will leave a 1, if and only
if, both the bits in that position are 1.
0110 1100
+ 0000 0100
= 0000 0100
Licensing
Most MatrikonOPC products require that some form of licensing criteria be met for it to function
correctly.
The MatrikonOPC Server for Omron PLCs supports software licensing only.
93
Note: Alias Events needs to be licensed separately, and by default, is delivered with only a 30-day
demo. To purchase a full Alias Events license, please contact your MatrikonOPC Account Manager.
IMPORTANT TO NOTE:
The following licensing information is described in detail within the
Licensing Procedures document which accompanies the MatrikonOPC
Server for Omron PLCs software and Users Manual:
Software key licensing information.
Information about the MatrikonOPC Licensing Utility that is
used to license driver software, and the variety of ways in
which licenses can be obtained (e.g., Internet Connection, Web
Page, Email).
Licensing Q&A and Troubleshooting.
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
([email protected]).
For Monday to Friday daytime support requests, contact MatrikonOPC Support using the regional
phone numbers provided in Table 52.
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 either of the following numbers. There is no
extra charge from MatrikonOPC for calling their after-hours support numbers.
Region
Contact Information
+1-780-231-9480
All
+1-780-264-6714
Table 53 - After-Hours Support
94
OPC Compliance
For more information on OPC, view the documents listed below (as well as other OPC
Specifications) at http://www.opcfoundation.org. MatrikonOPC supports the following
interfaces:
OPC Overview 1.0
OPC Common Definitions and Interfaces 1.0
OPC Data Access Specification 2.05a
OPC Data Access Specification 3.00
OPC Historical Data Access Specification 1.2
OPC Alarms and Events Specification 1.10
Installation
The server is by default installed as a local out-of-process COM server and enters its registration
information in the Windows registry when instructed to do so with the /REGSERVER commandline option. The server installs itself as a Windows service and enters its registration information in
the Windows registry when instructed to do so with the /SERVICE command-line option.
Version-independent program ID is Matrikon.OPC.OMRON.
Version-specific program ID is Matrikon.OPC.OMRON.1.
OPC sub-key and vendor information string.
Globally unique application ID (e.g., 9FA8E7F7-3610-4FEA-91E5-E0f8A3D8C866).
Globally unique class ID number (e.g., 189547C8-82A4-48C7-B462-A4BBDB73FDD6).
Full path of 32-bit local server executable.
OPC Data Access Server 2.05a and 3.00 implemented component categories.
The server removes its registration information from the Windows registry when commanded to do
so with the /UNREGSERVER command-line option.
Common Interfaces
The server supports the mandatory functionality specified in OPC Common Definitions and
Interfaces. The server supports the following locales for result code translation:
US English (0x0409)
System default (0x0800)
User default (0x0400)
Neutral (0x0000).
The server allows the client to set the client name for each connection. The server supports the
shutdown event notification client-side interface.
Data Access
The server supports the mandatory functionality specified in the OPC Data Access Custom Interface
Standard.
95
Groups
The server supports the addition, removal, and cloning of private groups. The server allows the
client to manage group state.
Name
Active state
Update rate (100 millisecond resolution)
Time bias
Dead-band (percent of analog item high-low range)
Items
The server supports the addition, removal, and validation of items in a group. The server allows the
client to manage item configuration.
Active state
Requested data type
Dead-band (percent of analog item high-low range)
Sampling rate
Buffer values (used only when sampling rate is enabled and is sampling faster than the
group update rate).
I/O Operations
The server supports synchronous I/O operations.
Read active item values from cache.
Read item values from device.
Read items value from device based on how old the cache items value is.
Read items without adding the item to an OPC group.
Write control values to items (on device).
MatrikonOPC Server for Omron PLCs v1.2.0 Users Manual
96
Write control value, quality, and/or timestamp to items (if the server supports such
features).
Write control values without adding the item to an OPC group.
The server supports asynchronous I/O operations as defined for DA 3.00.
Read items value from device based on how old the cache items value is.
Write control value, quality, and/or timestamp (if the server supports such feature).
The server supports the data change event notification client-side interface as defined for DA 3.00.
Keep-alive call-back indicating server is alive.
The server supports asynchronous I/O operations as defined for DA 2.05a.
Read items value from device.
Write control values to items (on device).
Refresh active items from cache.
Cancel outstanding operations.
Enable/disable event notifications.
The server supports the data change event notification client-side interface as defined for DA
2.05a.
Data change or dead-band exceeded.
Asynchronous refresh operation complete.
Asynchronous read operation complete.
Asynchronous write operation complete.
Asynchronous operation cancellation complete.
The server supports asynchronous I/O operations as defined for DA 1.0.
Read items values from device.
Read items values from cache.
Write control values to items (on device).
Refresh active items from cache.
Cancel outstanding operations.
The server supports the data change event notification client-side interface as defined for DA 1.0.
Data change or dead-band exceeded data with timestamps.
Data change or dead-band exceeded data without timestamps.
Asynchronous write operation complete.
97
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.
98
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.
99
4. Click on the Security tab to set the security for the server.
5. The Distributed COM Configuration Security tab (Figure 52) appears.
100
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 53) appears.
101
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 Server for Omron PLCs v1.2.0 Users Manual
102
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.
103
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 Matrikon OPC 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.
104
Appendix B
Aliases
Scaling Expressions
Alias scaling expressions may use any of the expression constructs listed in Table 54.
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
105
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]
If the OPC item being referenced in a calculation is not found within the servers address space, the
server attempts to add it. If successful, the OPC server uses the Alias Subscription Rate to
update the OPC item. The Alias Subscription Rate is configured in the Advanced Options panel.
In the event that the server cannot create a subscription to the OPC item, the alias quality reports
Bad, bad configuration.
Advanced alias calculations may use any of the operators listed in Table 55.
Construct
Description
Examples
Minus operator.
x-y
-x
!=
of x by y.
And logical operator.
&
!x
x != y
x%y
x&y
Multiplication operator.
x*y
Division operator.
x/y
x^y
Or logical operator.
Addition operator.
<
<=
x|y
x+y
x<y
x <= y
106
Construct
==
Description
Equal logical operator.
Returns 1 if true, 0 if false.
Examples
x == y
>
x>y
>=
x >= y
Alias scaling calculations may use any of the functions listed in Table 56.
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)
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
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,...)
values.
to a decimal number.
val1 else returns val2.
107
Construct
Description
Examples
min
min(x,y)
min
min(x,y,z)
rand
rand()
rand
rand(min, max)
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)
max.
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.
Data Type
Read-only
Poll Always
108
Field
Description
Update Rate
Scaling
When the scaling field specifies linear (1) or square root (2) scaling, the line contains the additional
fields listed in Table 58.
Field
High Raw
Description
Raw value range (double-precision real).
Low Raw
High Scaled
Low Scaled
Clamp options.
0 = none
1 = clamp low value
2 = clamp high value
3 = clamp both high and low values
Clamp
When the scaling field specifies gain/offset (3) scaling, the line contains the additional fields listed
in Table 59.
Field
Description
Gain
Offset
When the scaling field specifies expression (4) scaling, the line contains the additional fields listed
in Table 60.
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 line contains the additional fields listed
in Table 61.
109
Field
Description
Input Calculation
Scaling Algorithms
For each type of scaling, a different algorithm (Table 62) is applied to values read from the OPC
item. A reverse algorithm is applied to any values written to the OPC item.
Scaling
Algorithm/Example
Linear
x RawLow
Square
Root
x RawLow
Gain/
Offset
Expression
Scaled High
RawHigh
Scaled High
RawHigh
Scaled Low
RawLow
Scaled Low
RawLow
Reverse Algorithm/Example
Scaled Low
Scaled Low
x Scaled Low
x Scaled Low
RawHigh
Scaled High
RawHigh
Scaled High
RawLow
RawLow
Scaled Low
RawLow
Scaled Low
RawLow
Gain x Offset
x Offset
Gain
SQRT(INPUT) + 5
(OUTPUT 5) * (OUTPUT 5)
110
Appendix C
The Standard data types and their descriptions are listed in Table 63.
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
111
Appendix D
Microsoft Excel can act as both DDE client and DDE server. When using Excel as the client, DDE
items can be bound to specific cells in a spreadsheet, creating a read-only hot link to the DDE
items. Using Visual Basic, Excel can also be used to transmit (write) the data contained in a specific
cell of a spreadsheet to a DDE server.
DDE Read
To perform a DDE Read using Excel, simply enter a DDE Item as a formula in some spreadsheet
cell:
=SERVICE|TOPIC! NAME
Excel will initiate a DDE Advise loop, or hot link, to the topic and item within the service. The DDE
Management system (in this case, Windows) will forward any update sent by the DDE service, to
the appropriate DDE client (in this case, Microsoft Excel). The DDE service is responsible for update
rate/behaviour.
To disable a specific hotlink in Excel, use the Links menu option under the Edit menu.
DDE Write
To perform any DDE command other than requests (read) or advise (hot link), a Visual Basic (VB)
function must be used. Most DDE commands are available by using the application object. For
example, the following function will poke (write) the contents of column 1, row 1 to an item in the
OPC Simulation server:
Sub WriteToDDE()
' open a DDE channel. Field 1 = SERVICE, Field 2 = TOPIC
'channel = DDEInitiate("matrikon_opc_simulation", "Bucket Brigade.Real4")
' poke to the Item 1000\, the value of cell A1
DDEPoke channel, "1000\", Worksheets("Sheet1").Range("A1")
' close the channel
DDETerminate channel
End Sub
112
Net DDE
Since DDE commands are routed by the operating system, it is not possible to establish a DDE
session between two computers unless some transport mechanism is used. This is usually supplied
as a plug-in component of the operating system. In the Windows Environment, the NetDDE
Windows Service allows DDE communication between two computers.
NetDDE must first be configured using the DDEShare application (DDEShare.exe) as shown in
Figure 55. Each SERVICE and TOPIC pair, or NetDDE Share, that is to be available through
NetDDE must be assigned a unique name.
113
Appendix E
Configuring Dynamic Data
Exchange (DDE)
The server may act as a DDE service. In this way, a DDE client can request data from the server
using the following DDE commands:
XTYP_POKE
XTYP_REQUEST
XTYP_ADVREQ
XTYP_ADVSTART
XTYP_ADVSTOP
DDE service can be enabled or disabled using a checkbox (refer to Advanced Options for more
information, including the location of, this checkbox). Note that these options will not be available
if the server does not support DDE.
Items within the server can be referenced using the following syntax:
SERVICE_NAME |ITEM! SCANDETAILS
SERVICE_NAME represents the name of the DDE service. The first edit box specifies the service
name used by this server.
ITEM refers to an Item ID of a point within the server.
SCANDETAILS is a combination of the desired scan rate of the item, and an access path. One or
more delimiting characters separate the scan rate and access path. The second edit box can be
used to change the delimiters. The delimiting characters must be provided when referencing an
item in the server. However, the scan rate and access path are optional. If no scan rate is
specified, only data contained in the server cache is available through DDE, and an advise loop is
not created.
Changes to the DDE options do not take effect until the server is restarted.
Note: DDE Name Syntax DDE Names may be described in the
following syntax: SERVICE|TOPIC|NAME
In this case, consider the TOPIC to be the item ID, and the NAME to
be a combination of the scan rate and access path.
114
Appendix F
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:
Introduction this introductory section.
OPC Security Implementation description of user access dependencies.
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.
115
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 four 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. Reading
4. Writing
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 four functionality types listed above, three 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, or Writing.
When browsing, only a partial path leading to an OPC item may be known at any location in the
browsing hierarchy.
116
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 58) appears.
117
Layout
The MatrikonOPC Tag Security Configuration Utility screen displays the name of the OPC
server that is being configured for tag security. In Figure 58 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 59). 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.
118
Figure 59 - 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 Server for Omron PLCs v1.2.0 Users Manual
119
2. The Add User window (Figure 60) 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 61 for a sample list of defined users and
groups).
6. The Edit <Username> window (Figure 66) appears. Follow the instructions in the Edit
User section for adding permissions.
120
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 60) appears.
3. Select the Private User option button (Figure 62).
121
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.
122
2. The Add Group window (Figure 63) 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 61 for a sample list of defined users
and groups).
6. The Edit <Groupname> window (Figure 73) 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 63) appears.
3. Select the Private Group option button (Figure 64).
123
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 61 for a sample list of defined users and groups).
6. The Edit <Groupname> window (Figure 73) 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 65) appears.
124
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:
Double-click your mouse on the user you wish to edit, or
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.
2. The Edit <Username> window (Figure 66) appears.
Notes:
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.
125
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, and
Read 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 67 provides an example of a null branch and items below it, all of which are outlined in
black.
126
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, 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, 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 (Saw-toothed
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 68) 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.
127
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 69) 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.
128
129
On the General tab (Figure 71) 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.
130
131
Edit Group
To edit a group:
1. From the MatrikonOPC Tag Security Configuration Utility main screen, either:
Double-click your mouse on the group you wish to edit, or
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.
2. The Edit <Groupname> window (Figure 73) appears.
Notes:
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
section regarding configuration on the Permissions tab. Group and user permissions are
configured in the same way.
132
On the General tab (Figure 74) 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 75), the users that are part of the current group are defined. By
default, the Group Members screen section is empty. In Figure 75, User1 has been added to
Group1.
133
134
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 75).
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, 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 61), or
MatrikonOPC Server for Omron PLCs v1.2.0 Users Manual
135
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 58).
2. The Change Password window (Figure 77) appears.
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 64:
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.
136
Example 1
Table 65 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 65 - 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 66 lists all defined users and groups and their
associated permissions. Table 67 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 67 - Example 2: Groups and Members
Tip 1
Adding a user name and not defining any permissions for that user name (or any group it belongs
to), will completely restrict their access to information in the OPC server.
137
Case 1
User DOMAIN\john.doe connects. The user is unable to perform any function at any level, since
no permissions have been defined for this user name or the Restricted group to which it belongs.
Tip 2
Use the root location to define permissions for locations that have not been defined. Use the
default user to define permissions for users that are not listed.
Case 2
User DOMAIN\no.name connects. This name is not defined so the default user 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 here browsing is
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 for
under Configured Aliases, it would use the permissions defined at the root level.
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.
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
MatrikonOPC Server for Omron PLCs v1.2.0 Users Manual
138
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.
Determining Permission
Whenever a browsing, item addition, read, or write 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:
139
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.
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, or write) is specified
(Figure 70). 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.
Example
The following is an example of a tag security configuration. Table 68 lists all defined users and their
associated permissions.
User/Group
Configured Paths
Browse
Add
Read
Write
Everyone
DOMAIN\john.doe
Allow
Allow
Allow
Allow
DOMAIN\john.doe
Random
Allow
Deny
Deny
Deny
DOMAIN\john.doe
Random.Int
Allow
Allow
Allow
Allow
The user DOMAIN\john.doe wants to read the item Random.Int4. The permission routine would
not be able to find an exact location match under the Configured Paths list. However, it would
loop through each partial match in the Configured Paths list looking for a defined permission. The
location Random.Int would be the closest match and the permission would be ALLOW.
The user DOMAIN\john.doe wants to read the item Random.Real4. The permission routine
would not be able to find an exact location match under the Configured Paths list. However, it
would loop through each partial match in the Configured Paths list looking for a defined permission.
The location Random would be the closest match and the permission would be DENY.
140
Appendix G
Offline Mode
Introduction
Offline mode allows the MatrikonOPC Server Framework to be disconnected to the end device, but
still return data as if the date was coming from it. This is useful in two situations:
1. A configuration can be set up with to interact with any hardware, allowing any problems in
the configuration to be worked out without having them affect the device.
2. Diagnosing problems becomes much simpler when an implementer can remove the device
hardware from the architecture.
Offline mode can be applied to the entire configuration of a MatrikonOPC server or to a portion of
it.
Behaviour
Boolean (VT_BOOL)
True or False.
Character (VT_I1)
Byte (VT_UI1)
Word (VT_UI2)
Float (VT_R4)
Double (VT_R8)
Date (VT_DATE)
141
Data Type
Behaviour
String (VT_BSTR)
Simulated or Data.
Table 69 - Offline Mode Item Values
Operational Effects
When offline mode is enabled at a particular location in a servers hierarchy, there is no
communication between the server and the end-device/application to which the location refers.
Note: Some servers allow communication to multiple
devices/applications. To ensure there is no communication in the
entire server, offline mode should be enabled at the root level.
To ensure that there is no communication when offline mode is enabled, the MatrikonOPC Server
Framework will disable the object associated with that branch. When an object is disabled due to
offline mode, the Enabled checkbox will be cleared (i.e., unselected) in its panel within the
configuration utility. Enabling the object will have no effect while the object has offline mode
enabled. When offline mode is disabled for that particular object, the MatrikonOPC Server
Framework will re-enable it and the Enabled checkbox will be selected (i.e., checked) once again.
142
Appendix H
Installation
Once the system requirements have been met, you are ready to install the software.
Note: As part of the installation process, the MatrikonOPC Analyzer
tool is installed and used to detect the system settings that affect the
use of this software. No information is communicated back to
Matrikon. Information is stored on this system only for future use by
MatrikonOPC Support to assist with troubleshooting, if required.
To install the software:
1. Insert the MatrikonOPC Server for Omron PLCs CD into the CD drive.
2. If the MatrikonOPC InstallAware screen does not automatically appear, double-click the
installation .exe file. The MatrikonOPC Server InstallAware Wizard verifies its
contents (Figure 78).
3. Either a Pre-Requisites screen (Figure 79) appears, or you are taken directly to the
Licensing Agreement (Figure 80) screen. If the Licensing 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.
143
5. After all pre-requisites have been installed, the License Agreement screen (Figure 80)
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.
144
6. Read the Software 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. The Setup Type screen (Figure 81) appears.
145
146
11. Select the folder in which to install the MatrikonOPC server, or accept the default location
displayed in the Folder path field.
12. Click on the Next button. The Start Menu screen (Figure 83) appears.
147
13. Select the Start Menu group and specify whether you want shortcuts created only for
yourself, or for all users, by selecting the applicable option button.
14. Click on the Next button. The Enter Password screen (Figure 84) appears.
148
15. 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.
If you need to change the password at a later date, access the
Tag Security shortcut from the Start menu. Click on the
Windows Start button. Select Programs -> MatrikonOPC ->
<OPC Server Name> -> Tag Security. For more
information, refer to Appendix E Security.
16. Click on the Next button to accept the default password. The Licensing screen (Figure 85)
appears.
149
150
19. Click on the Next button. The Installing MatrikonOPC Server for Omron PLCs screen
(Figure 87) 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.
151
20. When the installation has finished, the MatrikonOPC Server for Omron PLCs Setup
Complete screen (Figure 88) appears stating that the MatrikonOPC server has been
successfully installed.
152
21. 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
22. Click on the Finish button to complete the installation and exit the Wizard.
23. 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.
153
Appendix I
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 70 are installed by default, in the following location:
C:\Program Files\Matrikon\OPC\Omron
File Name
Description
ACL.sec
ACLSecure.exe
Altova.dll
AltovaXML.dll
CalcEngine.dll
CalcEngineResource.dll
CalEngineServerPS.dll
CalEngineWrapper.dll
CalculationGraph.dll
clipsdll.dll
dbghelp.dll
icudt40.dll
icuin40.dll
icuuc40.dll
log4cxx.dll
lsapiw32.dll
NetPortalQueryServerPS.dll
ProcessNetDataDelivery.dll
RmsApiProxy.dll
Scheduler.dll
ScriptLibrary.dll
Xerces-c_2_8.dll
OPCOmron.exe
Licensing Procedures.pdf
ProgID.txt
PSTCFGOmronLib.ocx
security.cfg
Security settings.
154
File Name
Description
The initialization file for recording the servers initial settings.
ServerOpts.ini
The files listed in Table 71 are installed by default, in the following location:
C:\Program Files\Common Files\MatrikonOPC\Common
File Name
Description
OPCAnalyzer Logs\
ACLConfig.exe
MatrikonOPC Tag Security Configuration Utility that configures taglevel security in MatrikonOPC servers.
EULA.pdf
License document.
OEM_Matrikon_OPC.dll
OPCAuto.dll
opcda20_auto.doc
OPCDAAuto.dll
opchda10_auto.doc
opchda_ps.dll
OPCHDAAuto.dll
PSTCFG.exe
PSTCFGBasicInnerLayerLib.ocx
PSTcfgps.dll
PXPComfigps.dll
Description
EXPREVAL.DLL
OPC_AEPS.DLL
OPCBC_PS.DLL
OPCCOMN_PS.DLL
OPCDXPS.DLL
OPCENUM.EXE
155
File Name
Description
OPCHDA_PS.dll
OPCPROXY.DLL
OPC Data Access 2.0 and 1.0a Interfaces and Marshalling Library.
OPCSEC_PS.DLL
ACTXPRXY.DLL
156
Appendix J
Un-Installation
To successfully un-install MatrikonOPC Server for Omron PLCs, using the Add or Remove
Programs from the Microsoft Windows Control Panel is recommended.
To un-install MatrikonOPC Server for Omron PLCs:
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 89) is displayed.
4. Scroll through the list of currently installed programs and updates to find and select
MatrikonOPC Server for Omron PLCs.
5. Click on the Remove button associated with the MatrikonOPC Server for Omron PLCs
program to initiate the un-install process.
6. The MatrikonOPC Server for Omron PLCs InstallAware Wizard appears, and the
Welcome to MatrikonOPC Server for Omron PLCs Maintenance screen (Figure 90) is
displayed.
157
7. Select the Remove option button to un-install MatrikonOPC Server for Omron PLCs entirely.
8. Click on the Next button. The Ready to Uninstall screen (Figure 91) is displayed.
158
159
11. When the un-install has finished, the MatrikonOPC Server for Omron PLCs Setup
Complete screen (Figure 93) appears stating that MatrikonOPC Server for Omron PLCs
was successfully un-installed.
160
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.
161