Specifications

RSLinx – Training Guide 69
Training Section 9: Local and Remote OPC
Introduction
This section outlines step by step the configuration of Windows to use OPC, local and
remote, with Rockwell Software products. Both Windows 95/98 and NT are covered
along with RSLinx, RSView32 and RSTools.
The steps outlined here are the results of actual experimentation with Windows and RSI
products. There may be other ways to configure Windows for OPC over a network, but
these are the steps that Rockwell Software has found to be successful.
OPC on one PC
Configuring Windows
OPC between two applications on the same PC uses windows COM (Component Object
Model). No special configuration of COM or windows is required if only one PC is
involved. However, if you are using Windows 95, you will have to install DCOM
(Distributed Component Object Model) for Windows 95 before you can use COM.
• DCOM does not ship as part of Windows 95. A self-extracting executable
can be found on http://www.Microsoft.com/com/dcom95 . Download and run
it. DCOM installs as part of Windows 98 and Windows NT 4.0 or higher so
this step is not necessary.
Configuring Rockwell Software Products
No special configuration should be required for Rockwell Software Inc. (RSI) servers
built with the RSServer OPC Toolkit such as RSLinx or other RSServer products. You
must have RSLinx 2.0 or higher to use OPC. See the help files of each specific
RSServer to see if it supports OPC or call Rockwell Software.
Configuration of OPC varies from client to client. RSView32 and RSTools will be
covered here. See the help files of other RSI client product for instructions on
configuring OPC or call Rockwell Software.
Note: OPC is not available
with RSLinx Lite.