RoviSys OPC90 User manual

OPC90 Server
For Bailey
®®
Command Series / NETWORK 90 / INFI 90
TW NE ORK 90 and INFI 90 are registered trademarks of ABB (Formerly Bailey Controls Company).

OPC90 Server
1INTRODUCTION................................................................................................................................ 5
2
3
4
5
5. ILE
1.2
1.6
5. DD
5. DIT
5. Po
.2
5. IEW
4.1
4.2
5.
5.3
BE
6PS
7KS
7.
FUNCTIONAL DESCRIPTION ........................................................................................................ 6
INSTALLATION ................................................................................................................................. 7
BAILEY COMMUNICATION OVERVIEW ................................................................................... 8
OPC90 SERVER APPLICATION MENU ITEMS ........................................................................ 12
1F............................................................................................................................................... 13
5.1.1 New....................................................................................................................................... 13
5. Open ..................................................................................................................................... 13
5.1.3 Save ...................................................................................................................................... 13
5.1.4 Save As ................................................................................................................................. 13
5.1.5 Auto Save.............................................................................................................................. 14
5. Import CSV........................................................................................................................... 14
5.1.7 Reimport CSV....................................................................................................................... 14
5.1.8 Export CSV........................................................................................................................... 14
5.1.9 Reexport CSV........................................................................................................................ 14
2A.............................................................................................................................................. 15
5.2.1 Device................................................................................................................................... 16
5.2.2 Group.................................................................................................................................... 16
5.2.3 Block..................................................................................................................................... 17
3E.............................................................................................................................................. 18
5.3.1 Deletion ................................................................................................................................ 18
3.2 rts ..................................................................................................................................... 18
3.3 gineering Units................................................................................................................. 195. En
5.3.4 Text Messages....................................................................................................................... 19
5. Red Tag Users ...................................................................................................................... 203.5
5.3.6 SOE Point Names.................................................................................................................22
5.3.7 Properties............................................................................................................................. 23
5.3.8 Priority ................................................................................................................................. 23
5.3.9 Configuration Shadowing Between Redundant Servers....................................................... 24
5.3.
5.3.9 OPC Client Access of Redundant Servers........................................................................................ 26
9.1 Redundant Same Address CIUs...................................................................................................... 25
5.3.10 Error Detection .................................................................................................................... 26
4V............................................................................................................................................. 28
5. View Monitor........................................................................................................................ 29
5. View Status ........................................................................................................................... 30
5.4.3 View Start In Runtime...........................................................................................................31
5.4.4 View Run As Service.............................................................................................................31
5UTILITIES ...................................................................................................................................... 32
5.5.1 Service Manager................................................................................................................... 32
5.5.2 DCOM Configuration........................................................................................................... 32
5. View My Logs....................................................................................................................... 32
5.6 LOCK FACEPLATES...................................................................................................................... 32
5.7 LP ............................................................................................................................................. 33H
5.7.1 Block Finder......................................................................................................................... 34
GROU ............................................................................................................................................. 36
BLOC ............................................................................................................................................. 37
1NALOG INPUT LOOP (AIL) .................................................................................................... 40A
7.2 NALOG OUTPUT LOOP (AOL)................................................................................................ 41A
7.3 BLOCK DATA (BLK) ............................................................................................................... 43
7.3.1 Reading A Bailey Block........................................................................................................ 45
The RoviSys Company Version 7.0 Page 2

OPC90 Server
7. Tuning A Bailey Block.......................................................................................................... 453.2
3.3
3.4
3.5
3.6
3.9
7. Reading The Entire Bailey Configuration............................................................................ 45
7. Changing Bailey Controller Module Modes......................................................................... 46
7. Writing Bailey Controller Blocks ......................................................................................... 47
7. Modifying Bailey Controller Blocks..................................................................................... 47
7.3.7 Deleting Bailey Controller Blocks........................................................................................ 48
7.3.8 Configuration Command Processing ................................................................................... 48
7. ABB Bailey Controller Configuration Faceplate ................................................................. 53
7.4 DATA ACQUISITION ANALOG (DAANG)................................................................................. 56
7.5 DATA ACQUISITION DIGITAL (DADIG)................................................................................... 58
7.6 DATA BLOCK (DATA)............................................................................................................ 60
7.7 DEVICE DRIVER (DD).............................................................................................................. 61
7.8 DEVICE DEFINITION BLOCK (DEVICE)................................................................................. 62
7.8 SCSI Communication............................................................................................................ 70.1
.27.8 Device Communication Faceplate........................................................................................ 72
7.9 DIGITAL INPUT LOOP (DIL)..................................................................................................... 74
7.10 DIGITAL OUTPUT LOOP (DOL) ................................................................................................ 75
7.11 HARMONY ANALOG INPUT (HAI)............................................................................................ 77
7.12 HARMONY ANALOG OUTPUT (HAO)....................................................................................... 78
7.13 HARMONY DIGITAL INPUT (HDI) ............................................................................................ 79
7.14 HARMONY DIGITAL OUTPUT (HDO)........................................................................................ 80
7.15 MODULE STATUS (MODSTAT).............................................................................................. 81
7.16 MULTI-STATE DEVICE DRIVER (MSDD)................................................................................. 83
7.17 MULTIPLEX CIU (MUXCIU)................................................................................................... 85
7.18 OUTPUT DEVICE DRIVER (ODD) ............................................................................................. 89
7.19 OUTPUT MULTI-STATE DEVICE DRIVER (OMSDD)................................................................ 91
7.20 OUTPUT REMOTE CONTROL MEMORY (ORCM)...................................................................... 94
7.21 OUTPUT REMOTE MOTOR CONTROL (ORMC)......................................................................... 96
7.22 OUTPUT REMOTE MANUAL SET CONSTANT (ORMSC)........................................................... 98
7.23 OUTPUT STATION CONTROL (OSTN) ...................................................................................... 100
7.24 POLL ANY BLOCK (POLL) .................................................................................................... 103
7.25 REMOTE CONTROL MEMORY (RCM)..................................................................................... 104
7.26 R M C (RMC) ....................................................................................... 105EMOTE OTOR ONTROL
7.27 REMOTE MANUAL SET CONSTANT (RMSC) .......................................................................... 107
7.28 SEQUENCE OF ................................................................................................
EVENTS (SOE) 108 7.2 SPECIFICATION BLOCK (SPEC) ............................................................................................. 11397.30 ONTROL
7.31 STATION PID C(STN)................................................................................................ 115 TEXT SELECTOR (TXT) ......................................................................................................... 118
7TEXT STRING (TEXTSTR).................................................................................................... 119.32
8
9
10 R
SC
N
A
N
R
SP
CSV FILE FORMATS..................................................................................................................... 120
SETTING UP OPC CLIENT ACCESS OF OPC90...................................................................... 125
9.1 CONFIGURING N C90 PC ..................................................................... 125
ONFIGURING DCOM ON THE REMOTE O C CLIENT PC..........
DCOM OTHE LOCAL OP
9.2 CP.................................................. 131
ALIDATING OPC CLIENT ACCESS OF OPC90......... ..........9.3 V... ...................................................... 133
T OUBLESHOOTING HINTS ................................................................................................. 135
10.1 LIDATI G E ONDIVIDUAL OPC90 ER BLOCKS.................................................... 136
IPORT OT ISIBLE I DELOCK PROPERTIES COMM PRT LIST
VA N STAT F ISERV
10.2 SN V N VICE BOBOX....................... 137
10.3 O COMMUNICATION.................................................................................................................. 137
ARS TOE COMMUNICATING BUO D BEIN10.4 PPE BT NATA IS G RECEIVED ...................................... 138
ALL BLE RECEIVING DTA .................. ....... ........... ................10.5 OT OCKS ARA.... ... ... ..................... 138
DBLOC ARR BAQ I IC ON10.6 AN OM KS E ECEIVING D UALITY ND ATI .................................................. 139
ADI DATA TNSF R OF E B10.7 OR C RA E XPORT LOCKS TO BAILEY...................................................... 139
The RoviSys Company Version 7.0 Page 3

OPC90 Server
10.8 ANNOT EXPORT OR CONTROL DATA WITHIN BAILEY............................................................... 140C
C
10.11 CLIENT DOES NOT SEE ANY OPC SERVERS WHEN BROWSING REMOTE PC........................... 141
10.12 CLIENT CONNECTS BUT DOES NOT RECEIVE DATA ................................................................ 141
10.13 VIEWING DATA IN MONITOR MODE DOES NOT WORK ........................................................... 141
10.14 WRITING RMSC BLOCKS CAUSE CONTROLLER OR NODE OFFLINE CONDITION ..................... 142
10.15 LAST SAVED DATABASE NOT AUTOMATICALLY RESTORED ON PROGRAM START................. 142
10.16 DATA UPDATES STOP AFTER 2HOURS.................................................................................... 142
10.17 DATA UPDATES STOP AFTER 8HOURS.................................................................................... 143
10.18 SCSI ADDRESSES DIFFERENT BETWEEN TWO SHADOWED PCS.............................................. 144
10.19 OPC90 RUNNING AS A SERVICE RANDOMLY STOPS OR CRASHES........................................... 145
10.9 ANNOT SEE ALL DOCUMENTED BLOCK ATTRIBUTES .................................................................. 140
10.10 OPC90 SERVER WILL NOT TIME SYNC BAILEY...................................................................... 140
The RoviSys Company Version 7.0 Page 4

OPC90 Server
1 Introduction
The RoviSys Company has developed a tightly integrated interface between
OPC clients and a Bailey DCS that promotes future plant upgrades using OPC.
This interface is called the OPC90 Server. It allows easy and extremely user
intuitive replacement of Bailey operator consoles with Windows
NT/2000/XP/2003_Server based OPC Client consoles. It also provides an open
migration path from the Bailey control platform to OPC as plant time, resources
and schedule permits.
The OPC90 Server enables seamless DCS access to the Bailey Controls
Command Series, NETWORK 90 and INFI 90 Distributed Control Systems. The
server can communicate at the network level via the appropriate Computer
Interface Unit (NCIU0X), Plant Loop to Computer Interface (INPCI0X), Infi-net to
Computer Interface (INICI01, INICI03, INICI12, INICI13, IIMCP01/02) or, within a
single Process Control Unit, via a Computer Interface Command (CIC01), Serial
Port Module (NSPM01, IMSPM01) and Computer Port Module (CPM02/03). The
bottom line is OPC90 can communicate with all interfaces available for
NETWORK 90 / INFI 90 and Command Series Distributed Control Systems.
System integrity, functionality, and data throughput is maintained by utilizing
standard exception reporting techniques. Bandwidth improvements are realized
over existing Bailey use of these same hardware interfaces by implementing dual
channel capability and redundant interfaces.
This document is intended for individuals who are familiar with the Bailey
configuration principals in terms of the types and how to access exception report
blocks. An understanding OPC is also required.
OPC90 Server is an OPC Data Access 1.0, 2.0 and 2.05 compliant server. This
is achieved by using an industrial grade OPC toolkit to implement its OPC
interfaces. The ongoing maintenance and certification of this toolkit is managed
by a company that is a charter member of the OPC Foundation.
OPC90 Server supports DCOM. DCOM allows one PC running OPC90 to
provide its data via a local area network to other PCs running OPC client
software. Refer to the OPC90 Remote Access section of this document for
instructions on how to setup DCOM.
Throughout this document the OPC90 Server will be referenced as OPC90. The
Bailey system is referenced as BLY which is defined to include Command Series,
NETWORK 90 and INFI 90 systems.
The RoviSys Company Version 7.0 Page 5

OPC90 Server
2 Functional Description
OPC90 Server can run on the Windows NT/2000/XP/2003_Server operating
system. It is implemented as a collection of blocks that are specific to each type
of exception report block found within a Bailey system. This collection of blocks
is stored as an OPC90 Configuration. A special block called the Device block
(DEVICE) is configured to setup the communication port(s) used to access the
Bailey interface, define required update rates and report various statuses of the
communication channels. All other OPC90 Server blocks are linked to a DEVICE
that provides the necessary information it needs to manage communication with
the Bailey system. The various other OPC90 Server blocks linked to the
DEVICE contain the address within Bailey where the exception report block is
located. The DEVICE uses this address and block type to determine how the
point is established and managed within the Bailey interface. As data is received
from the Bailey interface for each of the established points it is parsed and
copied to the appropriate tags within the corresponding OPC90 Server block.
This implementation has several advantages:
•Extremely intuitive to Bailey users.
•Developed with an industrial grade OPC toolkit manufactured by an OPC
Foundation Charter Member company insures 100% compliance to the OPC
1.0, 2.0 and 2.05 specifications.
•Point capacity is not limited by type of points utilized by the plant but only by
the type of Bailey interface available (typically up to 10,000 tags).
•Alarm levels are set in real time by data received from the Bailey system
(eliminates the need to maintain alarm level settings in two areas).
•Includes ability to tune Bailey control loops from OPC Client applications.
•Supports redundant Bailey interfaces or redundant communication channels
to a single Bailey interface.
•Supports the ability to easily import and export OPC90 function blocks to/from
comma delimited (*.csv) files. The CSV file can be easily created using
Microsoft Excel and then simply imported into the OPC90 Server to create a
OPC90 Configuration.
The RoviSys Company Version 7.0 Page 6

OPC90 Server
3 Installation
The installation procedure utilizes the industry standard Install shield Setup
program. Do the following procedure to install OPC90. This procedure
assumes that the OPC90 Server is being installed on a Windows
NT/2000/XP/2003Server operating system.
1.) Log into a user account with administrator privilege.
2.) Insert the OPC90 Server installation CD into the CD drive.
3.) Run the setup program found in the root directory of the CD.
4.) Follow the instructions given by the Setup program.
5.) Insert the Hardware Key onto the parallel port or USB port.
6.) You have completed installation of OPC90 Server!
When upgrading, first uninstall using Windows add/remove programs and then
run the above procedure. If running OPC90 as a service, make sure it is stopped
before uninstalling.
Note that the demo version of OPC90 downloaded from the RoviSys website
does not support software licensing. It must be uninstalled and the official
version installed from the CD to accomplish licensing of the OPC90 software.
The RoviSys Company Version 7.0 Page 7

OPC90 Server
4 Bailey Communication Overview
Bailey utilizes a communication technique for data exchange called exception
reporting. Exception reporting means the data is sent when it has changed
significantly or a maximum time has expired since the last time it was sent. All
exception reported data is made available to the rest of the system via a set of
exception report related function blocks which are matched by an equivalent
OPC90 Server block. Bailey has a series of RS232 serial based devices
generically called Computer Interface Units that are utilized to receive this
exception report data. Note that communication with the INICI03 interface can
be either RS232 or SCSI. RoviSys is extremely knowledgeable on the use of the
various Bailey interfaces and has implemented a single driver that can utilize the
following types of interfaces:
Bailey Interface Max. Number
Bailey Blocks Exception Reporting Control Operation
NSPM01 500 No No
IMSPM01 500 No No
IMCPM02 500 No No
IMCPM03 500 Yes Yes
NCIC01 500 Yes Yes
NCIU01 500 Yes Yes
NCIU02 2,500 Yes Yes
NCIU03 5,000 Yes Yes
NCIU04 10,000 Yes Yes
INPCI01 500 Yes Yes
INPCI02 5,000 Yes Yes
IIMCP01 10,000 Yes Yes
IIMCP02 30,000 Yes Yes
INICI01 10,000 Yes Yes
INICI12* 10,000 Yes Yes
INICI13* 30,000 Yes Yes
INICI03* 30,000 Yes Yes
•When using these interfaces, the ABB Bailey semAPI software environment is
not required. The INICI12, INIC13, and INICI03 do not support dual channel
serial communication. When using serial communication to the INICI12,
INICI13 and INICI03, make sure the cable is attached to the port labeled
“terminal” on the ABB Bailey termination unit or termination module. See the
sections “Add” and “Device Definition Block” for information regarding SCSI
communication with the INICI03.
The RoviSys Company Version 7.0 Page 8

OPC90 Server
•INICI03 sites containing INICT03A firmware revision ‘F’ must upgrade to
revision ‘G’ or later or downgrade to revision ‘E’.
•INICI13 is comprised of the INICT13A and INNIS01 modules. The default
factory settings for the INICT13A SW4 are incorrect. The INICT13A SW4
Poles 6, 7, 8 must be open (1) when using SCSI with this module.
Throughput of the supported devices is difficult to calculate empirically since the
data is received and sent by exception and varies according to the data type and
what has changed significantly at any given time. The exception reporting rate
per general data type for RS232 and SCSI interfaces is presented in the
following table:
Data Type RS232 @ 19.2k
values / second SCSI values / second
Analog 260 / 161* 1080 / 1059*
Digital 310 / 260* 1230 / 1206*
Control Loop 106 / 91* 618 / 606*
Average 225 / 170* 976 / 957*
* Rate when the device block “Use DCS Timestamp” option is
enabled.
Note that a few of the above mentioned devices do not support exception
reporting. Specifically the NSPM01, IMSPM01, IMCPM01 and IMCPM02. Data
collection from these devices is basically limited to the OPC90 Server blocks that
poll to get the block values. The names of these blocks are POLL, BLK and
SPEC. The remaining interfaces support the following OPC90 Server blocks and
associated Bailey exception report block types:
OPC90 Server Block Type Bailey Block Name F.C. Number
AIL Analog Output / Loop – AOL 30, 70, 158
BLK Bailey Block Configuration any function code
DAANG Data Acquisition Analog – DAANG 177
DADIG Data Acquisition Digital – DADIG 211
DD Device Driver – DD 123
DIL Digital Output / Loop – DOL 45
HAI Harmony Analog Input 222
HAO Harmony Analog Output 223
HDI Harmony Digital Input 224
HDO Harmony Digital Output 225
MODSTAT Module Status any module
MSDD Multi-State Device Driver – MSDD 129
MUXCIU Multiplexes a PC COM port to Bailey
Interface for configuration related
software (i.e. Bailey CADEWS,
Any function code
The RoviSys Company Version 7.0 Page 9

OPC90 Server
Composer, G.Michaels DBDOC, etc)
POLL Poll Value any block
RCM Remote Control Memory – RCM 62
RMC Remote Motor Control – RMC 136
RMSC Remote Manual Set Constant – RMSC 68
SOE Sequence of Events 99, 243
SPEC Specification – SPEC any block
STN Control Station – STN 21, 22, 23, 80
TXT Text Selector – TEXT 151
TEXTSTR Text String - TEXTSTR 194
The common Bailey computer interfaces used to gain access to the Bailey
exception report blocks presented in the above table also support the ability to
allow a system to emulate and output most of these same point types. They are
called “output report” block types. Bailey consoles receive the point type,
exception reported data directly from the Bailey interface in the same format as if
it was coming from an equivalent Bailey controller. This allows the predefined
Bailey console faceplates for each of these control point types to be utilized when
receiving data from the OPC90 Server report point types. Instead of addressing
the tags to a block in a Bailey controller, they are addressed to a block number
assigned within the Bailey interface that OPC90 is communicating. The ring and
node address to use is that assigned to the interface with a fixed module address
of two.
The following table presents a list of Bailey interfaces supporting the output
report block types.
Bailey Interface Bailey System Max. Number of points Supported by OPC90 Server
NCIU02 Network 90 2,500 Yes
NCIU03 Network 90 5,000 Yes
NCIU04 Infi 90 10,000 Yes
INPCI02 Infi 90 / Symphony 5,000 Yes
IIMCP01 Network 90 10,000 Yes
IIMCP02 Infi 90 / Symphony 30,000 Yes
INICI01 Infi 90 / Symphony 10,000 Yes
INICI12 Infi 90 / Symphony 10,000 Yes
INICI13 Infi 90 / Symphony 30,000 Yes
INICI03 Infi 90 / Symphony 30,000 Yes
The RoviSys Company Version 7.0 Page 10