Specifications

RSLinx – Training Guide A - 19
RSLinx Gateway currently supports up to 5 remote clients. The easiest way to
make a successful remote connection is to run RSLinx as a Service
Automatically. For more information on DCOM configuration requirements for
RSLinx,
Jump to A1239 DCOM Configuration Requirements for RSLinx Gateway Remote
OPC
Enabling Client Software:
RSLinx Gateway CD provides the Remote OPC Client enabling software. This
enabling software must be installed on each remote RSView32 OPC client where
RSLinx is not installed.
Node Configuration:
For each RSLinx Gateway connection, a node must be configured in RSView32.
In the Node configuration, select OPC Server and type a node name. Click the
Server Name browse button and select the RSLinx OPC Server - Remote type
(RSLinx 2.0), or RSLinx Remote OPC Server - Remote type (RSLinx 2.1). Click
the Server Computer Name or Address browse button and browse to the remote
OPC Server Computer.
The Access Path is optional in the node configuration. If specified, it is an OPC
topic name in RSLinx on the remote OPC Server. When the Access Path is
omitted from the node configuration, the address line of each tag must include
the OPC topic name surrounded by brackets. For example, the address for a tag
using N7:0 would be entered as [TopicName]N7:0.
The Update Rate defaults to 1 second.
This represents the frequency that the RSView32 OPC client will ask the RSLinx
OPC server for an update. RSLinx Gateway also specifies a poll rate for each
OPC topic. The default poll rate is 1000 ms or 1 second. When the OPC Topic
poll rate is modified, then the Update Rate should be modified as well. The
Update Rate should not be set faster than the corresponding OPC topic poll rate.
RSLinx Gateway Server name change:
RSLinx 2.0 name = RSLinx OPC Server
RSLinx 2.1 name = RSLinx Remote OPC Server.