Rockwell Automation FactoryTalk View Site Edition Users Guide - Manual (Page 173)

9 • S ETTING UP COMMUNICATIONS
9–3
•
•
•
• •
9 • Pl
aceh
ol
der
Local applications can only use one RSLinx Enterprise server, which must be located on
the same computer as the application.
Communicating with multiple controllers
RSLinx Enterprise is designed to serve multiple controllers across multiple networks
simultaneously. RSLinx Enterprise recovers from program downloads, disconnects,
power-offs, and online changes without affecting service to other controllers.
RSLinx Classic can also serve multiple controllers across multiple networks
simultaneously; however, is not designed to manage abnormal conditions. When
controllers or devices are powered off, RSLinx Classic will wait for a time-out before
servicing other devices. RSLinx Classic also does not automatically manage online
changes and may require re-starting after program downloads.
KEPServer Enterprise can also serve multiple controllers across multiple networks
simultaneously.
Setting up communications in FactoryTalk View SE
These are the basic tasks involved in setting up communications for a FactoryTalk
View SE application:
1. Gather information about the network, and the devices that are connected to it. Decide
which of the following data servers will be used:
 Rockwell Automation Device Server (RSLinx Enterprise)
 Other OPC-DA 2.05a-compliant server:
 RSLinx Classic
 KEPServer Enterpriser
2. Install and set up the data servers.
 RSLinx Enterprise is installed automatically with FactoryTalk View SE. Add a
Rockwell Automation Device Server (RSLinx Enterprise) to the FactoryTalk
View SE application and set up the server’s properties. For more information, see
page 9-4.
OPC data servers can be located on different computers; however, it is not recommended.
RSLinx Enterprise is the recommended server for FactoryTalk View applications. For more
information about choosing a data server type, see page 9-1.