Rockwell Automation T6200 Compressor Anti-Surge and Capacity Controller - Manual (Page 159)

Configuration
8-39
MICON OPC Server Start-up
The MICON OPC server (MOPS) is used to interact with the T6200 controllers for Configuration and
Operator Interface purposes. Although most of the following description is related to communication
setup and explanation of OPC server screens and fields that are not directly associated with control
configuration, it is helpful to understand the full functionality of the OPC server. If you are already
familiar with the basic functionality of the MICON OPC server, you can directly proceed to the
OPC Server Configuration Interface section
MOPS can be started up in two ways. The manual mechanism involves executing the application
“mlpcomm2d.exe” which must have been installed on the hard drive when the OPC server was
installed. Automatic startup of MOPS occurs when an OPC client tries to make a connection to
MOPS and MOPS is not already running on the computer. The automatic startup occurs even if
the connection request from the OPC client comes over a network from a remote computer.
When MOPS starts up, it reads the registry where it has saved the following parameters:
window location, window minimization, enable/disable downloading of time, and the refresh rate
in seconds.
If MOPS was shut down the last time in the minimized mode, then it will start up again in the
minimized mode. If MOPS was shut down maximized on the desktop, then it reads the registry for
the window co-ordinates and starts up at the same location on the desktop. Enabling/disabling of
time download and Refresh rate are described below.
When MOPS is started up, it reads a file “C:\ICS Triplex\devlist.txt” for Ethernet addresses for the
controllers. The devlist.txt file is a simple ASCII text file, contains three fields, and must be
formatted as follows:
<dev_name>, <primary Ethernet address>, <secondary Ethernet address>,CR,LF
Multiple records can be added on separate lines with one record for each device. The commas
delimiting each field and the carriage return and line-feed delimiting each record are not optional.
An example file for an installation with five controllers would be as follows:
U200_5,0:54:19:OB:00:02,0:19:be:1a:0:02,
R100,00:86:46:f8:06:02,00:9a:46:f8:06:02,
R101,00:62:af:3f:00:2,0:2:be:4c:0:02,
R103,00:42:1B:5:0:4,00:62:20:5:0:4,
U201,00:53:21:8:0:2,00:95:1e:5:0:2,
RCMB,00:12:ef:6b:0:02,00:02:af:3f:0:2,
No additional headers or footers are required in the file.
If a controller comes alive with its memory cleared while the MOPS is running on a PC on the
same network, the MOPS will initialize that controller’s device name. All controllers that are alive
on the network when the MOPS is started, will be polled by the MOPS for their tag lists. The tag
definitions received from each controller will be added to the MOPS database and MOPS will
serve these tags to OPC clients.