Enterprise Buildings Integrator

OPC Client Interface Reference

Apr 2013

Release 500
 Document Release Issue Date
500 18 Apr 2013

Disclaimer
This document contains Honeywell proprietary information. Information contained
herein is to be used solely for the purpose submitted, and no part of this document or its
contents shall be reproduced, published, or disclosed to a third party without the express
permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate, Honeywell
disclaims the implied warranties of merchantability and fitness for a purpose and makes
no express warranties except as may be stated in its written agreement with and for its
customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential
damages. The information and specifications in this document are subject to change
without notice.
Copyright 2016 - Honeywell International Sàrl

2 [Link]
Contents

Getting started with OPC controllers .......................................................................................... 5

OPC configuration checklist ...................................................................................................................... 6
OPC Client support .................................................................................................................................... 7
OPC server documentation ........................................................................................................................ 8
OPC-specific terms .................................................................................................................................... 9
OPC Client Interface setup ......................................................................................................... 11
Description of OPC .................................................................................................................................. 12
How OPC data transfer works ..................................................................................................... 12
Callback ....................................................................................................................................... 12
Explicit read request ..................................................................................................................... 13
Interfaces and methods used .................................................................................................................... 14
Architectures ............................................................................................................................................ 15
Valid OPC interface configurations ............................................................................................. 15
OPC Client controllers, channels, and points .......................................................................................... 16
OPC Client controller configuration and addressing .............................................................. 17
Defining an OPC Client channel .............................................................................................................. 18
OPC Client channel Main properties ........................................................................................... 18
Defining an OPC Client controller ........................................................................................................... 21
OPC Client controller Main properties ........................................................................................ 21
Defining an OPC Client address for a point parameter value .................................................................. 24
Entering an address for an OPC controller .................................................................................. 24
Using the Address Builder to enter an address ............................................................................ 24
Importing OPC items using the import wizard ........................................................................................ 27
Optimizing scanning performance ........................................................................................................... 29
OPC Client scan packets .............................................................................................................. 29
Server and Station tasks for OPC Client .................................................................................. 31
Testing OPC communications with the server ......................................................................................... 32
Troubleshooting OPC Client communication errors .................................................................... 32

3
CONTENTS

4 [Link]
Getting started with OPC controllers

This reference describes how to set up, configure, and test the OPC Client Interface.

Related topics
“OPC configuration checklist” on page 6
“OPC Client support” on page 7
“OPC server documentation” on page 8
“OPC-specific terms” on page 9

5
GETTING STARTED WITH OPC CONTROLLERS

OPC configuration checklist

Complete each step in the order specified.

Steps: Go to:
Install and set up the OPC server as specified in the
documentation supplied by the OPC server manufacturer.
Install any OPC server configuration files on the OPC client
computer as specified in the documentation supplied by the
OPC server manufacturer.
Test communications between the OPC client computer and the “Testing OPC communications
OPC server computer. with the server” on page 32
Define channels with Quick Builder. “Defining an OPC Client
channel” on page 18
Define controllers with Quick Builder. “Defining an OPC Client
controller” on page 21
Download channel and controller definitions to the server.
Define points to address OPC server items with Quick Builder. “Defining an OPC Client
address for a point parameter
value” on page 24

6 [Link]
 GETTING STARTED WITH OPC CONTROLLERS

OPC Client support

The OPC Client Interface is an OPC client which supports communications to OPC
servers that meet the specification of the OPC Data Access Standard version 1.0a or 2.0.
The OPC Client Interface supports both local and remote OPC servers.

7
GETTING STARTED WITH OPC CONTROLLERS

OPC server documentation

You should read the documentation supplied by the OPC server manufacturer before
creating any OPC Client controllers.

8 [Link]
 GETTING STARTED WITH OPC CONTROLLERS

OPC-specific terms
This section contains OPC-specific terms.

Term Description
CLSID CLSID is the class identifier that identifies an object. An object
registers its CLSID in the system registration database so the object can
be loaded and programmed by other applications.
group A number of items with the same update rate and deadband.
item A single data source of the OPC server.
OPC OPC stands for OLE for Process Control. It is a set of standards that
define sets of COM interfaces (based on Microsoft's COM/OLE
technology) to be observed by OPC clients and servers. This set of
standards was established by the OPC Foundation to foster greater
interoperability between automation and control applications, field
systems and devices, and business and office applications. When the
term OPC is used in this Reference, it refers specifically to the OPC
Data Access Standard.
ProgID A programmatic identifier. A registry entry that can be associated with a
class identifier (CLSID). The format of a ProgID is
<Vendor>.<Component>.<Version>, separated by periods and with no
spaces. The ProgID identifies a class, but with less precision. The
ProgID is used to identify the OPC server from other COM/DCOM
components on the same computer. For more details, see any setup and
installation instructions provided by the OPC server manufacturer.
update rate The internal update rate of the items in the OPC server.

9
GETTING STARTED WITH OPC CONTROLLERS

10 [Link]
OPC Client Interface setup

This section describes how to set up an OPC Client Interface.

Related topics
“Description of OPC” on page 12
“Interfaces and methods used” on page 14
“Architectures” on page 15
“OPC Client controllers, channels, and points” on page 16

11
OPC CLIENT INTERFACE SETUP

Description of OPC
OPC provides data from a data source and communicates the data to any client
application in a standard way, thereby eliminating the requirement for an application to
have specific knowledge about a particular data source, such as internal structure and
communications protocols.
An OPC server and an OPC client can reside either on the same computer (local server)
or on different computers (remote server).

How OPC data transfer works

OPC server data is available to the OPC client as items. To receive items from the OPC
server, the OPC client must gather one or more items into a group.
The OPC client requests the OPC server to create a group with a client-specified
maximum (at most) update rate and a deadband. The OPC client then requests the OPC
server to add items to the group. The update rate and the deadband of a group apply to
all items in that group.

Tip
There is no concept of hardware in the OPC Data Access Standard; there are just items.
An OPC server may represent a piece of hardware as an item and the item's value may
indicate the state of the hardware. However, whether or not such representation is
available is server-specific.
Although the OPC client can specify any update rate for a group, the OPC server decides
whether the request is honored.
Although the OPC client can specify the deadband for a group, the OPC server decides
whether the deadband request is honored.

Callback
Generally, the OPC server sends data to OPC clients through callbacks. After a group
has been created, the OPC server creates a cache for the group items. The cache is
updated according to the group's update rate. The OPC server sends only updated values
to the OPC client for items in the group if there has been significant change since the last
cache update (based on the group's deadband).
This method of data update significantly reduces traffic between the OPC client and the
OPC server as there is no need for periodic read requests to the OPC server. An OPC
client gets data when there is a significant change. The level of change required to
trigger an update from the OPC server is defined by the OPC client.

12 [Link]
 OPC CLIENT INTERFACE SETUP

Explicit read request

The OPC client can also send explicit read requests to the OPC server, independent of
the server callbacks. The OPC client specifies whether the data should come from the
OPC server's internal cache or from the field/hardware device. This method of scanning
is less efficient than callback.

13
OPC CLIENT INTERFACE SETUP

Interfaces and methods used

The following table lists the interfaces and methods used by the OPC Client Interface.

Interface Methods
IOPCCommon SetClientName
IOPCServer AddGroup
GetStatus
RemoveGroup
IOPCItemMgt AddItems
RemoveItems
ValidateItems
IOPCSyncIO Read
Write
IOPCAsyncIO Read
Refresh
IOPCAsyncIO2 Read (OPC DA 2 only)
Refresh2 (OPC DA 2 only)

The OPC Client Interface implements the IAdviseSink, IOPCDataCallback and

IOPCShutdown interfaces.

14 [Link]
 OPC CLIENT INTERFACE SETUP

Architectures
For the OPC Client Interface to communicate with an OPC server, the OPC server must
be installed on an appropriate computer. (The OPC Client Interface and the OPC server
can reside on the same computer or on different computers.)
To install an OPC server, install and set up the OPC server as specified in the
documentation supplied by the OPC server manufacturer.

Valid OPC interface configurations

The server OPC interface supports single-channel communications.

Single channel communications

A single-channel configuration.

Server OPC Server

OPC Client Interface

Figure 1: OPC Interface single-channel configuration

Alternate data source

The OPC Interface also supports an alternate data source. If the OPC Interface
connection to the primary data source fails, the OPC Interface connects to the alternate
data source.

Server Primary Alternate

Data Source Data Source

OPC Client Interface OPC Server OPC Server

Figure 2: OPC redundant alternate data source configuration

15
OPC CLIENT INTERFACE SETUP

OPC Client controllers, channels, and points

An OPC Client controller is Quick Builder's mechanism for configuring one or more
groups with the same deadband. Unlike most other types of controller, an OPC Client
controller is an abstract entity, and does not represent a physical device.
Similarly, a point parameter is Quick Builder's mechanism for defining an item on an
OPC Client controller. During configuration, you map each item to an appropriate point
parameter on an OPC Client controller. Only floating point number data types are
supported.
An OPC Client controller manages groups as follows:
• A group is created for each scan period used by the point parameters (items) defined
on the controller. (That is, all point parameters that have the same scan period are
placed in the same group.) Note that if a scan period of 0 is used, the item is placed
in a group with an update rate equal to the slowest scan rate of the server system.
• All points defined on the controller have the same OPC deadband. (Note that the
OPC deadband is not the same as the alarm and control deadbands that can be
specified for analog points.)
• The maximum number of items that can be configured in a controller is 735.
An OPC Client channel forms the interface between one or more OPC Client controllers
and an OPC server. You configure an OPC Client channel in the same way as other
channels; however, two properties have special significance as far as OPC is concerned:
• Diagnostic Scan Period. This determines how often the OPC client tests the status
of the OPC server to ensure that it is OK.
• Background Scan Period. This applies to all controllers configured under the
channel and determines how often the OPC client explicitly reads all items
configured on a controller if that controller is configured with background scanning
enabled. This is independent of the callbacks.

Related topics
“Defining an OPC Client controller” on page 21

16 [Link]
OPC Client controller configuration and
addressing

This chapter describes how to configure OPC Client controllers using Quick Builder.

Tip
An OPC Client controller is an abstract entity that is used as a container for OPC groups.
An OPC Client controller does not represent a real controller or a real piece of hardware.

Related topics
“Defining an OPC Client channel” on page 18
“Defining an OPC Client controller” on page 21
“Defining an OPC Client address for a point parameter value” on page 24
“Importing OPC items using the import wizard” on page 27
“Optimizing scanning performance” on page 29

17
OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Defining an OPC Client channel

This section describes how to define an OPC Client channel.

To define an OPC channel using Quick Builder

1 Click to open the Add Items dialog box.
2 Select Channel from Add Items.
3 Select OPC Channel from Type.
4 Specify the Main tab property values.

OPC Client channel Main properties

The Main tab defines the properties of an OPC Client channel.

Tip
If you specify an alternate host name, Quick Builder builds a redundant OPC channel.
Refer to the Configuration Guide for your server for information about monitoring
redundant channels.

Property Description
Name The unique name of the channel. A maximum of 10 alphanumeric
characters (no spaces or double quotes).
Description (Optional) A description of the channel. A maximum of 30
alphanumeric characters, including spaces.
Marginal Alarm Limit The communications alarm marginal limit at which the channel is
declared to be marginal. When this limit is reached, a high priority
alarm is generated. A channel barometer monitors the total number of
requests and the number of times the controller did not respond or
response was incorrect. The barometer increments by 2 or more,
depending on the error and decrements for each good call.
Set the channel marginal alarm limit to 10.
Fail Alarm Limit The communications alarm fail limit at which the channel is declared to
have failed. Set this to 20, that is, double the value specified for the
channel Marginal Alarm Limit.
Connect Timeout Amount of time, in seconds, the server waits to connect to the OPC
server before abandoning the connection. The default is 20 seconds.

18 [Link]
 OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Property Description
Read Timeout Amount of time, in seconds, the server waits for a reply from the OPC
server after a synchronous read request. The default is 2 seconds.
Note: When connecting to legacy third party control networks, it is
recommended that the Read Timeout be set to 5 seconds.
Host Name (preferred) The name of the computer on which the preferred OPC server software
resides.
Note: The OPC Server should not be installed on the Honeywell server.
It should be installed on another machine. The exception to this is the
MatrikonOPC Server for Allen-Bradley PLCs, which may be installed
locally. In this case the name must be LocalHost. This is to support
server redundancy, so that if the Honeywell servers fails over, it always
connects back to the MatrikonOPC server on the local machine.
Note: DCOM configuration is required when connecting to an OPC
server located on another computer. This is required for the MNGR
account to connect properly. For information about configuring DCOM,
see the Configuration and Administration Guide.
Note: When you use Quick Builder to configure non-scanned
parameters that connect to a remote OPC server, your Windows user
account must also reside on the remote OPC server. In addition, the
account must be a member of the Product Administrators group on the
remote OPC server. If your Windows user account does not exist or
does not have sufficient privileges on the remote OPC server, you will
not be able to select parameters from the list of parameters stored on the
server.
Username and passwords must match on both machines.
Host Name (alternate) (Optional) The name of the computer on which the alternate OPC server
software resides. If it is on the same computer as the OPC Client
Interface, the name must be LocalHost.
Note: If you specify an alternate host name, Quick Builder builds a
redundant channel OPC connection. See the Configuration Guide for
the server for information on monitoring the status of redundant
channels.
Diagnostic Scan The amount of time, in seconds, between diagnostic scans. The
period diagnostic rate must be set to one of the valid server scan periods. The
default is 60 seconds.
This value is used as the rate for sending synchronous requests for
checking the OPC server's current status.

19
OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Property Description
Background Scan The background scanning period (in seconds). This must be set to one
Period of the valid server scan periods (defaults to 60).
This value is used as the rate for sending explicit read requests of all
items configured under a controller if that controller is also configured
with background scanning enabled.
Note: When connecting to legacy third party control networks, it is
recommended that the background scan period be set to 10 minutes.
ProgID The ProgID for the OPC server that is to be connected.
OPC server host time Select this check box when connecting to Matrikon OPC Servers.
can drift
You should also select it if the OPC server computer's clock (UTC time)
is known to drift. This can occur if the clock is synchronized to an
external clock. Moving in or out of daylight savings time is not a time
drift as the UTC time does not change.
Item Type Shows the channel's type.
Last Modified Shows the date of the most recent modification to this channel's
property details.
Last Downloaded This shows the date that the item was last downloaded to the server.
Item Number This field displays the unique item number currently assigned to this
item by Quick Builder. You can change the item number displayed in
this field if you need to match your current server database
configuration. The item number must be between 1 and the maximum
number of channels allowed for your system.

20 [Link]
 OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Defining an OPC Client controller

This section describes how to define an OPC Client controller.

To define an OPC controller using Quick Builder

1 Click to open the Add Items dialog box.
2 Select Controller from Add Items.
3 Select OPC Controller from Type.
4 Specify the Main tab property values.

Related topics
“OPC Client controllers, channels, and points” on page 16
“OPC Client controller Main properties” on page 21

OPC Client controller Main properties

The Main tab defines the properties for an OPC Client controller.

Property Description
Name The unique name of the controller. A maximum of 10 alphanumeric
characters (no spaces or double quotes).
Description (Optional) A description of the controller. A maximum of 30
alphanumeric characters, including spaces.
Channel Name The name of the channel on which the controller communicates. You
need to have defined the channel in order for it's name to appear in the
list.
Marginal Alarm Limit The communications alarm marginal limit at which the controller is
declared to be marginal. When this value is reached, a high priority
alarm is generated. This limit applies to the controller barometer which
monitors the total number of requests to the controller and the number
of times the controller did not respond or response was incorrect. The
barometer increments by 2 or more, depending on the error and
decrements for each good call.
Set the channel marginal alarm limit to 10.

21
OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Property Description
Fail Alarm Limit The communications alarm fail limit at which the controller is declared
to have failed. When this barometer value is reached, an urgent alarm is
generated.
Set this to 20, that is, double the value specified for the controller
Marginal Alarm Limit.
Background Scan Specify whether background scanning is performed in addition to
normal callback operation. Select Enabled if you do not want the
default (Disabled). The background scan period is configured under the
channel.
Deadband The OPC deadband, which applies to all items referenced by point
parameters belonging to this controller. Note that although the OPC
client can specify the deadband for a group, the OPC server decides
whether the deadband request is honored.
The deadband Indices are defined as:
0 = 0.000%
1 = 0.001%
2 = 0.002%
3 = 0.005%
4 = 0.010%
5 = 0.020%
6 = 0.050%
7 = 0.100%
8 = 0.200%
9 = 0.500%
10 = 1.000%
11 = 2.000%
12 = 5.000%
13 = 10.000%
14 = 20.000%
15 = 50.000%
Item Type Shows the controller's type.
Last Modified Shows the date of the most recent modification to this controller's
property details.
Last Downloaded The date that the item was last downloaded to the server.

22 [Link]
 OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Property Description
Item Number The unique item number currently assigned to this item by Quick
Builder. You can change the item number displayed in this field if you
need to match your current server database configuration. The number
must be between 1 and the maximum number of controllers allowed for
your system.

Related topics
“Defining an OPC Client controller” on page 21

23
OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Defining an OPC Client address for a point parameter value

A point parameter is Quick Builder's mechanism for “mapping” a single item on an OPC
Client controller. When configuring a point parameter, note that:
• The point parameter's Scan Period is used as the item's update rate. Note that if a
scan period of 0 is used, the item is placed in a group with an update rate equal to the
slowest scan rate of the server system. By default, the slowest scan rate is 1 hour.
• Periodic scanning is based on OPC callbacks, not on OPC synchronous read
requests.

Entering an address for an OPC controller

For Source Address and Destination Address the format for an OPC Client controller
address is:
ControllerName Address

Part Description
ControllerName The name of the OPC Client controller.
Address The address in the controller where the value is recorded.

If you would like help when defining an address, click next to Address to display
Address Builder.

Attention
EBI OPC clients do not support Access Path when defining an address of an OPC item. The
OPC standard states that access path is optional for a client to support. If the client does not
specify the access path then the server should choose the access path to use.

Using the Address Builder to enter an address

To specify a OPC Client controller address, enter the following property values:

Property Description
Address Type Select Controller.
Controller Select the appropriate OPC Client controller. You need to have defined
the controller for the name to appear in this list.
Address The address in the controller where the value is recorded.

24 [Link]
 OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Address syntax
The format for the address is:
[RockwellPath]OPCItemName [DataFormat]

Part Description
[RockwellPath] The Rockwell path is not normally required. However, it is required for
OPC servers developed using the Rockwell OPC Toolkit. You need to
see the vendor's documentation to determine whether a Rockwell path is
required.
The Rockwell path generally represents a device driver or topic (if the
server was previously developed as a DDE server).
Note, if you do specify a Rockwell path:
• You must include the square brackets. (In this particular case, they
do not simply indicate an optional part of the syntax.)
• There is no space between the Rockwell path and the OPCItemName.
OPCItemName The address in the controller where the value is recorded. You need to
see the vendor's documentation for the syntax.
For example, if you are using the system OPC server to access the PV
of a point named sinewave, the address would be [Link].
A maximum of 64 characters. Any printable ASCII character that you
can type, including the space character, is supported.
DataFormat The data format. If you do not specify a data format, the default is
IEEEFP.

Data format definitions

If you want to use a user-defined data format, you must define the format on the server.
See the section titled "About user-defined data formats" in the Configuration and
Administration Guide for more information.

Format Counts
IEEEFP IEEE single-precision floating point
U3BCD 0–999 BCD
U4BCD 0–9999 BCD
U4095 0–4095
U999 0–999
U9999 0–9999
U100 0–100

25
OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Format Counts
U1023 0–1023
U8B 0–255
S16B -32768–32767
S8B -128–127
S9999 -9999–9999
U16B 0–65535
U15B 0–32767
U14B 0–16383

26 [Link]
 OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Importing OPC items using the import wizard

As an alternative to building points for the required OPC items directly in Quick Builder,
you can use the QB OPC Import Wizard.

Prerequisites
• You have configured an OPC channel with the Prog ID of the OPC server that you
are importing from and an OPC controller.
• You have configured a sample point that contains the required parameters for each
type of point you require.

To import OPC items using the QB OPC Import Wizard

1 In Quick Builder choose Tools > QB OPC Import Wizard.
2 Click Next.
3 In the Computer name box, type the name of the computer where the OPC server is
installed.
4 Click the ProgID of the required OPC server and click Next.
5 Click Add Items.
6 Expand the OPC server and click the required items and click Add.
When you have added all the required items, click OK.
7 Click Next.
8 For each required point type, select the sample points you have created and click
Next.
9 Click an item, and from the Point Type list, click the point that this item is to be
mapped to.
10 From the Controller list, click the controller that the points will be added to.
11 If you want to use the default point naming scheme, from the Apply Scheme list
click Default. If you want to use a custom point naming scheme, click the Modify
button and set the naming scheme properties and then click OK.
12 Click the Map button.
13 In the OPC Attribute column, expand the list and choose the OPC attribute to map to
each Quick Builder attribute as required and click OK and then click Next.
14 Click Next.
15 When the message, All points have been validated appears, click Next.
16 Click Finish.
17 Click OK to close the wizard.

27
OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

18 In Quick Builder, click the Point item in the System Components tree and check the
properties for the OPC points that have been imported.

28 [Link]
 OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

Optimizing scanning performance

The maximum amount of data that can be acquired from an controller is influenced by
the rate of sending scan packets to the controller. An understanding of the OPC scan
packets will help you configure points so that optimal data acquisition performance can
be achieved by maximizing the amount of data acquired with each scan packet.
The scan packets that have been built can be listed by using the lisscn (list scan) utility.
Listing scan packets helps verify the scanning strategy. See the Configuration Guide for
your server for usage of lisscn.

OPC Client scan packets

OPC groups are collections of items with the same callback period and deadband. In
order to reduce the number of OPC groups (and hence OPC scan packets) you should:
• Assign all points with the same deadband to the same controller.
• Reduce the number of different scan periods used for points on a controller.

29
OPC CLIENT CONTROLLER CONFIGURATION AND ADDRESSING

30 [Link]
Server and Station tasks for OPC Client

This chapter describes tasks for the OPC Client controller that you perform either on the
server or from any Station.

For: Go to:
Testing communications with the server “Testing OPC communications with the server”
on page 32
Troubleshooting scanning errors “Troubleshooting OPC Client communication
errors” on page 32

Related topics
“Testing OPC communications with the server” on page 32

31
SERVER AND STATION TASKS FOR OPC CLIENT

Testing OPC communications with the server

You use the OPC client test utility, opctst, to test the:
• Connection to an OPC server
• Creation of OPC groups on a server
• Addition of OPC items into groups
• Reading and writing of values to OPC items on the OPC server computer

Prerequisites
Before testing:
• Complete any OPC server setup and configuration as required. See the setup and
installation instructions supplied by the OPC server manufacturer.
• Install any OPC server configuration files on the OPC client computer as required.
See the setup and installation instructions supplied by the OPC server manufacturer.
• Ensure you are logged on using the mngr account as this is the account that the OPC
Client Interface uses to communicate with the OPC server.

To run the opctst utility

1 Open a Command Prompt window, type opctst, and press ENTER.
2 When the Windows application starts, select the OPC menu option and perform each
of the menu operations in turn (that is, Initialize COM, Connect to OPC server, and
so on).

Troubleshooting OPC Client communication errors

If you experience difficulty getting the OPC Client Interface to communicate with an
OPC server, refer to the Enterprise Buildings Integrator log file (accessible via an icon in
the Diagnostic Tools folder). The log file gives an indication as to the cause of any OPC
communications problems.

32 [Link]
Index

A data transfer, described 12

explicit read request, described 13
addressing overview 12
OPC controllers 24 OPC Client Interface
alternate data source 15 architectures 15
architectures 15 communication errors 32
configurations 15
controllers and channels, using 16
C interfaces and methods used 14
channels optimizing scanning performance 29
defining 18 point parameter address 24
OPC channel 18 points, using 16
commands and utilities scan packets 29
opctst 32 OPC controllers
communication errors 32 addressing 24
communications channels 18
testing configuring 5
OPC controllers 32 defining 21
configuring getting started 5
OPC controllers 5 group, described 9
controllers item, described 9
configuring opctst utility 32
OPC controllers 5 testing communications 32
OPC controllers 5, 21, 24 troubleshooting 32
update rate described 9
opctst utility 32
D
defining
controllers 21
P
OPC channel 18 point parameter address, defining 24
OPC controllers 21
diagnostics
OPC controllers 32 S
scanning, optimizing performance 29
single channel communications 15
O
OPC
callback 12

33
INDEX

T U
testing communications utilities
OPC controllers 32 opctst 32

34 [Link]