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

Configuration
8-40
MICON OPC Server Initialization
When MOPS starts up, the following screen is displayed:
On startup, MOPS always tries to connect to the controllers defined in the devlist,.txt file. If it is
able to get a response from a controller, it requests the tags available in that controller. This
process is repeated for each controller in the database. At the end of the startup sequence, MOPS’s
database is initialized with the tags available in all controllers that are alive and responding to
queries. After startup, if any controller comes on-line, and if that controller has been defined in
MOPS’s device database, then that controller’s tags are automatically requested and added to the
database.
If a controller comes on-line after MOPS has been started, and if it did not exist in MOPS’ device
database, then that controller’s tags are added to MOPS’s database only if the controller has been
initialized with a valid ID (name). Such a controller is also added to MOPS’s device database
(devlist.txt) so that all future startups of MOPS automatically upload this controller’s tag list. Note
that this functionality assumes that the checkbox titled “Lock Device List” is not checked.
The various fields and buttons on this screen are described in the following sections.
FIGURE 8-26
OPC Server
Main Screen