3BUR002262R3 - en OPC Server For MOD 300 Version 1 1 1 - Installation and Configuration

OPC Server for MOD 300
Version 1.1/1
Installation and Configuration

OPC Server for MOD 300
Version 1.1/1
Installation and Configuration

NOTICE
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB Inc. ABB Inc. assumes no responsibility for any er-
rors that may appear in this document.
In no event shall ABB Inc. be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB Inc.
be liable for incidental or consequential damages arising from use of any software or
hardware described in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission from ABB Inc., and the contents thereof must not be imparted to a third party nor
used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.
Copyright © 2002 ABB Inc.

All rights reserved.
Release: September 2002
Document number: 3BUR002262R3
TRADEMARKS
Registrations and trademarks used in this document include:
Acrobat Registered trademark of Adobe Systems, Incorporated.
Adobe Registered trademark of Adobe Systems, Incorporated.
Industrial IT Trademark of ABB Inc.
Ethernet Trademark of Xerox Corporation

InstallShield Registered trademark of InstallShield Software Corporation
Microsoft Registered trademark of Microsoft Corporation.

MOD 300 Trademark of ABB Inc.
OPC Trademark of the OPC Foundation

Rainbow Registered trademark of the Rainbow Technologies Inc.
SentinelSuperPro Trademark of the Rainbow Technologies Inc.

Windows Registered trademark of Microsoft Corporation
TABLE OF CONTENTS
About This Book

General ..............................................................................................................................9
Use of Warning, Caution, Information, and Tip ................................................................9
Document Conventions ...................................................................................................10
Terminology.....................................................................................................................11
Related Documentation ...................................................................................................13
On-line Documentation ........................................................................................13
Section 1 - Introduction
Product Overview ............................................................................................................15
What You Can Do with OPC Server for MOD 300 .............................................15
What’s New in This Release ................................................................................15
Product Release History .......................................................................................16
Prerequisites and Requirements ......................................................................................16
Operating Software Requirements .......................................................................16
Computer Requirements.......................................................................................17
Software Requirements ........................................................................................17
Intended User...................................................................................................................18
Performance Results ........................................................................................................18
Reads .............................................................................................................18
Writes .............................................................................................................19
Alarms/Events ......................................................................................................20
Section 2 - Installation
Before You get Started.....................................................................................................21
RTAB Requirements.............................................................................................21
3BUR002262R3 5
Table of Contents
Planning ............................................................................................................ 21
Start-up and Shut-down Procedures..................................................................... 22
Product Verification ............................................................................................. 22
Installation Overview ...................................................................................................... 22
Installation Guidelines ......................................................................................... 22
File Download and Security Warning Dialogs ................................... 23
When to Re-start Your Computer ....................................................... 23
Installation Procedure .......................................................................................... 23
Installing a PCI-type Real-time Accelerator Board ........................................................ 25
System Services .............................................................................................................. 26
Prerequisite Support Software ............................................................................. 26
System Services Installation ................................................................................ 27
Create MOD 300 OPC User............................................................................................ 30
OPC Server for MOD 300 Installation............................................................................ 31
Completing Installation ................................................................................................... 32
Server Registry Controls for AdvOPCAEServer ............................................................ 33
Store Ack for Condition Events........................................................................... 33
CCF Require Acknowledge for Clear Messages ................................................. 33
RTAB watchdog(secs).......................................................................................... 33
Use Global Acknowledge (UseGlobalAck)......................................................... 33
Send Global Ack to LCP ..................................................................................... 34
Send Global Ack to MOD30 ............................................................................... 34
Server Registry Controls for AdvOPCDAServer............................................................ 34
RTAB watchdog(secs).......................................................................................... 34
ReadOnlyServer................................................................................................... 34
List Size (ListSize)............................................................................................... 34
Bad Data quality Map (BadDQ_Map)................................................................. 34
Reverse Time Synchronization........................................................................................ 35
Setting the Reverse Time Synchronization Variable on the RTDS...................... 36
Setting the Reversed Interval Variable................................................................. 36
Changing MOD 300 Security Group and DCOM Settings............................................. 37
Section 3 - Configuration
6 3BUR002262R3
Table of Contents
OPC Server Program ID and Class ID ............................................................................39

OPC Data Access Server......................................................................................39
OPC Alarm/Event Server .....................................................................................39
OPC Server Item ID ........................................................................................................40
Creating the Browse XML File .......................................................................................40
Creating the MODOPC.XML File on AdvaBuild for Windows..........................40
Creating the MODOPC.XML File on AdvaBuild for HP-UX.............................41
Appendix A - Software License Entry

Introduction .....................................................................................................................43
Obtaining the Machine ID ...............................................................................................44
Obtaining the Ethernet Address ...........................................................................45
Obtaining and Installing the Dongle ....................................................................45
Installing Sentinel Driver ....................................................................45
Requesting Software Keys...............................................................................................46
Entering Licenses ............................................................................................................51
File Installation.....................................................................................................51
Manual Installation...............................................................................................52
Licensing Troubleshooting ..............................................................................................54
Appendix B - Advant OCS Database

Requirements...................................................................................................................57
GENERICD Object .........................................................................................................58
PHYSICAL DEVICE...........................................................................................59
AUTO START ......................................................................................................60
SOFTWARE NAME ............................................................................................60
DO RATE .............................................................................................................60
SECONDARY DP, BACKUP ENABLE, and BACKUP OVERRIDE................60
DEFAULT ENVIRONMENT ..............................................................................60
NODE TYPE........................................................................................................60
AREA Object...................................................................................................................61
Message Center Fields .........................................................................................62
Message Center Entries for Alarm/Event Loggers ..............................................63
3BUR002262R3 7
Table of Contents
Message Routing from Operator Station ............................................................. 63

Recommended Message Centers for Routing to A/E Server............................... 64
Changes to Loop Type and UREL Tag Name ................................................................. 64
Appendix C - Syntax for Database References

Format of Expressions..................................................................................................... 65
Loop Parameter Reference (Tag Access) Format ................................................ 66
FCM Parameter Reference (Tag-FCM Access) Format ...................................... 67
Array Element Parameter Reference Format ....................................................... 68
Recipe Item Parameter Reference Format ........................................................... 70
Taylor Ladder Logic (TLL) Parameters Reference Format ................................. 72
Alarm/Event OPC References......................................................................................... 73
Appendix D - Upgrade
Introduction ..................................................................................................................... 77
Upgrade Procedure.......................................................................................................... 77
INDEX
8 3BUR002262R3
About This Book
General
This book describes how to install the OPC Server for MOD 300 product. This book
covers procedures for:
• Real-time Accelerator Board (RTAB) installation
• System Services installation
• OPC Server for MOD 300 installation
• ABB License Entry
Use this section as a guide to the conventions and terminology used throughout this
book. For a list of documentation related to the product described in this book, see
Related Documentation on page 13.
Use of Warning, Caution, Information, and Tip

This publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:
Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.
Warning icon indicates the presence of a hazard which could result in personal
injury.
3BUR002262R3 9
Caution icon indicates important information or warning related to the concept
discussed in the text. It might indicate the presence of a hazard which could
result in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.
Document Conventions
The following conventions are used for the presentation of material:
• The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
• Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
• Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
• Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
• The names of push and toggle buttons are boldfaced. For example, click OK.
• The names of menus and menu items are boldfaced. For example, the File
menu.
– The following convention is used for menu operations: MenuName >
MenuItem > CascadedMenuItem. For example: select File > New > Type.
10 3BUR002262R3
– The Start menu name always refers to the Start menu on the Windows
Task Bar.
• System prompts/messages are shown in the Courier font, and user
responses/input are in the boldfaced Courier font. For example, if you enter a
value out of range, the following message is displayed:
Entered value is not valid. The value must be 0 to30.
You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name
Terminology
You should be familiar with the following list of terms used in this instruction.
Term Description
Advant OCS ABB Advant Open Control System
Client Machine used as a client to server.
COM Microsoft’s Common Object Model that is used for
exchanging information within the Windows system. An
object can be a data structure, a system module or a
whole program, for example.
Component Container for files performing a well-defined function.
DCN Distributed Communication Network. E-DCN is an
Ethernet DCN.
DCOM Distributed Component Object Model. An extension of
COM. It defines how objects can interact over a network.
COM/DCOM is available on most Microsoft Windows
platforms and on several Unix platforms.
3BUR002262R3 11
Term Description
Node A point of interconnection to a network. Usually every
PC box with its own host name is considered a node.
OPC OPC is OLE for Process Control. OLE is Object Linking
and Embedding, a technology based on COM.
OPC AE OPC Alarm/Event. The OPC Alarm/Event Server
provides interfaces according to the definition of the AE
interface specification 1.0. It allows OPC AE Clients to
access the event stream of system.
OPC DA OPC Data Access. The OPC Data Access Server
interface meets the DA interface specification 2.0. It
gives OPC DA Clients read and write access to data
from all tags within the system.
OPC Server OPC Server is a data source. It exposes interfaces that
allow client applications to access the exposed data via
the interfaces defined in the OPC specifications. Thus it
makes the data originated in the original data source
(field device, control systems) available to any (one or
more) OPC Client.
SP Service Pack
System Module Container for components. Used to classify components
into groups with similar functions.
Windows Microsoft Windows 2000 Professional or Server
12 3BUR002262R3
Related Documentation
This instruction provides information only for the installation and configuration of
the OPC Server for MOD 300. Table 1 lists additional related documentation.
Table 1. Related Documentation
Category Title Description

Hardware Installation Instructions for Real-time Details regarding installation of RTA
Accelerator Board Board.
applicable PC User’s Guide Details regarding PC
Installation OPC Server for MOD 300 Introduction This book. Installation requirements and
and Installation procedures for the OPC server.
Microsoft Windows Administrator’s Install, uninstall, administration, and
Guide registry of Windows operating system.
Operation applicable OPC user software Details regarding reading and writing the
OPC server.
On-line Documentation
All documentation is supplied in Adobe® Acrobat® reader (.pdf) format. Acrobat
Reader is a freeware program, which can be downloaded from the internet. You can
get it from: http://www.adobe.com. Windows must be set up to start the Acrobat
Reader for .pdf files.
This book is available as on-line documentation on the installation CD. In addition,
you can subscribe to our internet site for on-line documentation.
3BUR002262R3 13
14 3BUR002262R3
Section 1 Introduction
Product Overview
OPC Server for MOD 300 is a Windows 2000 based product that provides an OPC
Data Access 2.0 and/or Alarm/Event 1.0 connection to the Advant OCS/MOD 300
control network (DCN or eDCN). Information from the server can be viewed from
systems with an OPC client interface. This product uses System Services and the
RTAB (Real Time Accelerator Board) connection to the network to gather data for
the OPC server.
What You Can Do with OPC Server for MOD 300

The MOD OPC Server can host up to 30,000 attributes by connecting to the OPC
system through varying interfaces as required by the OPC device. Other than setting
up some tag ID’s and completing the data access requirements, this product uses no
other special configuration or operation options.
The OPC Server can be used for numerous applications to export OPC data and/or
alarms/events from systems using MOD 300 software.
This product can be licensed to support up to 100, 250, 500, 1000, 2500, 5000,
10000, 20000 or 30000 points. See Performance Results on page 18 for examples of
acceptable limits.
The alarm/event functionality supports CCF and TCL alarm/event messages as well
as diagnostic messages as configured through the AREA Object on page 61.
What’s New in This Release

The Version 1.1/1 release of OPC Server for MOD 300 is the current release of this
product. This release supports supports browse functionality for both the DA and
AE server.
3BUR002262R3 15
Product Release History Section 1 Introduction
Product Release History

Table 2 lists the major milestones in the development of the software.
Table 2. Release History
Version Description
1.0 First product release. This release supports data access only. All
reads are performed using OPC subscriptions. OPC
synchronous/asynchronous reads are not supported at this time.
1.1 This release supports the Alarm/Event OPC server functionality. In
addition, synchronous/asynchronous reads are supported and the
performance improved.
1.1/1 This release supports browse functionality for both the DA and AE
server, adds a configurable read only server (registry entry), and
makes several fixes to existing functions.
Prerequisites and Requirements

The following prerequisites and requirements are necessary to support the OPC
Server for MOD 300.
Operating Software Requirements

The OPC Server for MOD 300 requires that the operating software that supports the
MOD 300 System be at the following levels:
• AdvaCommand Version 1.6/x
• AdvaBuild Version 2.7/x (for HP-UX), 3.1 (for Windows)
• MOD 300 System Version 14.4/x, 14.5/x or higher software
• Operate IT B0 with MOD Add-On Version 1 (or MOD 300 Connect Version 2)
16 3BUR002262R3
Section 1 Introduction Computer Requirements
Computer Requirements
The requirements shown in Table 3 must be met to successfully load and run the
software.
Table 3. Computer Requirements
Description Recommended Minimums

Processor Pentium® II, 450 MHz (minimum)
Monitor Any color monitor
Operator Device Keyboard and two-button cursor positioning device
Software media CD drive or network access to one
loading device
Ethernet™ card Required for all platforms that communicate with each other.
Hard Disk Space 10 GByte
Ram Memory 256 MByte
Software Requirements
The software requirements are shown in Table 4. The Microsoft (MS) and IIS
product must already be installed to support the OPC Server for MOD 300
installation.
Table 4. Software Requirements
CD Software
Microsoft Windows 2000 SP 2 Professional or Server
Microsoft IIS (Internet Information Services)
OPC Server for Adobe Acrobat Reader 5 (documentation reader only)
MOD 300
3BUR002262R3 17
Intended User Section 1 Introduction
Intended User
As a prerequisite you should already know how to use and maintain the Microsoft®
Windows operating system, as well as related hardware and software. In addition,
you must have Administrator privileges on the PC where the software runs.
Performance Results
The following data quantifies performance results based upon a 12 DCN address
system, with only a single media active (this provides the worst case loadings). Note
that the Data Base Management System (DBMS) in MOD 300 has two types of list
access: Subscription and Demand.
• Subscription Lists, once created, are automatically sent to the OPCServer on
the subscription rate. The OPCServer supports subscriptions rates of 1 to 4
seconds; however, any OPCGroup with a cycle of 5 to 20 seconds will also use
a subscription list of 4 seconds.
• Demand Lists, the OPCServer sends out a messages to each controller when
this list information is required, used for OPCGroups greater than 20 seconds.
Reads
The number of attributes in these tests is based upon 4-byte data (CCF integer and
real data, not string data). The numbers in Table 5 (DCN loadings) may vary
depending on system configuration. All reads are performed using OPC
subscriptions. FBus loadings are shown in Table 6.
Table 5. DCN Loadings
Number of DCN load

Cycle rate Description
Attributes change
3000 1 sec. 22% Read 3000 attributes per second (no
writes), uses 4 sec. subscription list.
18 3BUR002262R3
Section 1 Introduction Writes
Table 5. DCN Loadings
Number of DCN load

Cycle rate Description
Attributes change
writes), uses demand list.
Table 6. Classic Controller FBus loadings
Number of
Cycle rate Model B SC
Attributes
2800 30 sec. 10% 5%
2800 20 sec. 30% 15%
Writes
Writing 400 attributes to one AC460 Control module every second:
• 10% DCN load increase (single media).
• 50% RTAB CPU increase
Writing 400 attributes to five SC controllers every second:
• 15% F-Bus load increase
Writing 10 attributes to 20 controllers every second:
• 15% F-Bus load increase on Model B (10 attributes to 5 Model B’s in the same
subsystem)
3BUR002262R3 19
Alarms/Events Section 1 Introduction
Alarms/Events
Alarms and events are read as required to support the event categories, types,
conditions and subconditions as described in Alarm/Event OPC References on page
73.
20 3BUR002262R3
Section 2 Installation
These instructions describe how to install the OPC Server for MOD 300 on the
Windows platform.
OPC Server for MOD 300 requires that the DCOM settings be changed if the
client is on another PC.
Before You get Started

The installation procedures in this section assume you are installing on a machine
with Windows 2000 and the required prerequisite software.
Please review all instructions and your ABB support terms and conditions for
precautions, scope of license, restrictions, and, limitation of liability and
warranties, before installing any new software. Any problems or questions with
this installation should be directed to the Technical Support Group via
SUPPORTLINE: in the
U.S. - (1-800-HELP-365); international - (1-614-224-5888).
RTAB Requirements
The Real-time Accelerator Board (RTAB) is required (PCI type only) to connect to
the Advant OCS Control Network (MOD 300 DCN). You must install the RTAB
before you install the System Services software. See Installing a PCI-type Real-time
Accelerator Board on page 25.
Planning
To determine the physical, electrical, and environmental requirements for your PC,
refer to the applicable PC documentation. The only hardware specific to the
3BUR002262R3 21
Start-up and Shut-down Procedures Section 2 Installation
software installation is the Real-time Accelerator Board (used to connect to an

Advant OCS control network). This board is powered from the PCI bus supply in
the PC and does not require any other power supply.
Start-up and Shut-down Procedures

Refer to the PC manufacturer’s documentation for instructions on how to power up
and power down the PC.
Product Verification
Refer to the PC manufacturer’s documentation to determine if your PC is working
properly when powered up. The PC should meet the minimum requirements for the
product. See Computer Requirements on page 17.
Installation Overview
Follow the installation procedure and recommendations given in this section.
Installation Guidelines
The following are general guidelines for installing the software:
• Make sure you have the disk space and the prerequisite software as described
in Prerequisites and Requirements on page 16.
• Exit all Windows applications.
• You must have Administrator privileges to install software.
• Install the software components that you are licensed to use (or plan to
purchase a license for).
A static IP address is required for the LAN Internet Protocol (TCP/IP). DO NOT
use DHCP. This product will not work correctly without a static IP address.
22 3BUR002262R3
Section 2 Installation Installation Procedure
File Download and Security Warning Dialogs

File Download is always the first dialog displayed. This dialog prompts you to run
the installation program from its current location, or save the program to disk. BE
SURE TO SELECT: Run this program from its current location.
Security Warning is displayed next unless you have previously checked the box to
“Always trust content from ABB Inc.”. Select Yes to continue installation if the
Security Warning is displayed. Selecting No will stop the download.
When to Re-start Your Computer

If the installation wizard tells you to re-start your computer at certain points during
the installation procedure, always re-start as directed. DO NOT postpone re-starting
until later unless that option is specifically stated.
Installation Procedure
1. Make sure your computer has sufficient hardware and software to support the
applications you are installing. For general requirements, see Prerequisites and
Requirements on page 16.
2. The RTAB is required to connect to the Advant OCS Control Network (MOD
300 DCN). You must install the RTAB before you install the software. See
Installing a PCI-type Real-time Accelerator Board on page 25. Until the RTAB
provides time from the MOD system to the OPC Server for MOD 300 node, the
PC time uses the standard Windows time.
3. Insert the GENERICD database object into the MOD 300 database hierarchy
using AdvaBuild and set up the Area object (see Appendix B, Advant OCS
Database for guidelines).
4. Insert the OPC Server for MOD 300 CD and use the install screen shown in
Figure 1 to install the software.
You do not need to install the ABB License software if it already installed. For
example, when upgrading from a prior version or when another ABB software
package was installed, the license software would already be installed.
5. Install the license software, at this time, by browsing the CD and executing the
Install License.bat file. The installed programs include: ABB License Entry
3BUR002262R3 23
Installation Procedure Section 2 Installation
Program, ABB Central License Service, ABB License Client Component, and
SoapXML).
Figure 1. OPC Server for MOD 300 Install Screen
6. Install System Services Software, System Services on page 26.

7. Create user, Create MOD 300 OPC User on page 30
8. Install OPC Server for MOD 300, OPC Server for MOD 300 Installation on
page 31.
9. If necessary, install Acrobat Reader to view the documentation on-line.
10. Complete the installation and license the product. See Completing Installation
on page 32 and Appendix A, Software License Entry.
24 3BUR002262R3
Section 2 Installation Installing a PCI-type Real-time Accelerator Board
Installing a PCI-type Real-time Accelerator Board

This is only required if you are installing a Real-time Accelerator Board (RTAB). A
PCI board is used due to ease of installation, operation, and PC support. For further
details regarding the RTAB, refer to the Real-Time Accelerator Board Installation
Instructions.
To install the PCI-type RTAB in the PC:
1. Disconnect the PC from the power line.
You must remove the power cord from the power line before you remove the
cover. There are un-isolated and potentially fatal power line voltages present
under the cover. Remove the power cord before you open the cover!
2. Remove the PC cover. Refer to the PC hardware manual for details.
3. Unpack the RTAB.
Handle the board with care. Do not touch connectors with bare hands. Static
discharges may damage the board when it is removed from the plastic bag!
Follow precautions noted on the bag.
4. Detach the plastic handle from the PCI RTAB, if required.
5. Remove the cover plate of the PCI slot and then mount the RTAB in that slot.
6. Re-install the cover on the PC according to the PC hardware manual, and then
plug the PC power cord into the power line.
7. Turn on the PC.
8. Until you install System Services, Windows will try to configure the PCI
RTAB board. Cancel this attempt.
Windows will detect the PCI RTA board as new hardware. Select Cancel at the
add hardware display. The System Services install will configure the system for
the RTA board.
3BUR002262R3 25
System Services Section 2 Installation
System Services
Install the Server software and necessary patches using the installation wizard’s
default choices, unless otherwise directed in these guidelines. The System Services
software is included on the OPC Server for MOD 300 CD.
Prerequisite Support Software

Before you install the System Services software, make sure all required software
has been installed. Follow the guidelines below during installation.
• Internet Explorer can run during installation; however, it is strongly

recommended that you shut down all other Windows programs prior to
installation.
• If you have a virus protection program active in the PC, you must deactivate
that program during installation.
• If your computer has a newer version of third-party software you are
installing, the installation wizard will notify you that the target software is
newer than the source. If the newer software is a released version (NOT
beta software) select No to cancel installation of that file or component and
use the newer software.
• If you are prompted to install DLLs, click Yes.
• If you are prompted to re-start your computer, click Yes to re-start the
computer immediately.
26 3BUR002262R3
Section 2 Installation System Services Installation
System Services Installation

1. Insert the OPC Server for MOD 300 CD.
2. Select the System Services link (Install System Services 2.1) and follow the
installation wizard. Accept the wizard’s default selections for each dialog
unless directed otherwise in these guidelines.
3. Select: Run this program from its current location in the File Download
dialog. Respond Yes at the Security Warning display if it appears.
4. Welcome. Click Next > to start the System Services installation dialog.
5. License Agreement. Read, then select I accept the terms in the license
agreement and Click Next > to continue. Selecting the I do not accept option
will abort the installation.
6. Customer Information. Enter registered User Name and Organization, install
application for all users, and click Next > to continue.
7. Installation Type. Select MOD300 Connection and click Next > to continue.
8. Ready to Install the Program. Click Install to start the installation.
9. Installing ABB System Services. During the installation, the RTA Board
device driver is installed. Wait for the installation status screen to complete.
– Click YES and continue if the Digital Signature not Found message is
displayed
10. System Settings Change. Select No if you see the message “You must restart
your computer before the new setting will take effect.”.
11. InstallShield Wizard Complete. Select Finish.
12. Restart. When you see the prompt to restart the computer, click Yes to restart
the computer.
The System Services will not start until you initialize the communications
settings as described in step 13.
3BUR002262R3 27
System Services Installation Section 2 Installation
13. After the computer is restarted, initialize the OMF settings to start system
services. To do this, from the Windows task bar, Figure 2, choose
Start > ABB Industrial IT > System Services > Settings > Communications
Figure 2. Launching the Communications Configuration Tool
This displays the Communications Configuration Tool, Figure 3.
Figure 3. Communications Configuration Tool
14. Configure the Control Network section. Select MOD300 to connect this
computer to a MOD 300 Distributed Communications Network (DCN). The
network address parameters are displayed in the Network Address section.
28 3BUR002262R3
Section 2 Installation System Services Installation
15. Configure the Network Address section.

Both the DCN Address and the E-DCN Network Addresses (1 and 2) must be
set to valid values whether you are connecting to the DCN or E-DCN.
The DCN Address is required for both DCN and E-DCN connections. This is
the device number on the DCN. Set the DCN address to the same decimal
value as the Physical Device number specified on the node’s GENERICD
object in the ABB OCS database. Valid entries are 1 - 255 decimal that
represent the hexadecimal address on Unix.
When you connect to the standard DCN, you can leave the E-DCN addresses at
their default values.
For E-DCN connection, follow these guidelines to configure the E-DCN

addresses:
E-DCN Network Address 1 must be set to match the E-DCN Network
Address 1 value for all other nodes connecting to that media. E-DCN
Network Address 1 must be an even number, for example 6.
E-DCN Network Address 2 must be set to match the E-DCN Network
Address 2 value for all other nodes connecting to that media. E-DCN
Network Address 2 must be an odd number, for example 7.
16. Select OK to apply the changes. When you see the restart message, click OK
to acknowledge. You are required to restart if you change the Control Network
Setting, OMF Memory, or TCP/IP enabled setting (TCP/IP not required for this
product).
17. Re-start Windows. Re-start Windows before you do the OPC Server for MOD
300 installation.
3BUR002262R3 29
Create MOD 300 OPC User Section 2 Installation
Create MOD 300 OPC User

Create MOD 300 OPC user with administrator privileges, log off and then log back
in to set up a security account for the MOD 300 OPC installation. This user allows
OMF and DCOM access.
1. Select Start > Settings > Control Panel
2. Select Administrative Tools
3. Select Computer Management
4. From the Computer Management window expand System Tools > Local
Users and Groups.
5. Select Users and right click on New User... to open the New User window and
add additional users.
a. Enter User name: MODOPC
b. Enter Full name: MOD 300 OPC Administrative User
c. Enter Description: Additional User Description
d. Enter case sensitive Password of up to 14 characters (for example): abb
e. Confirm Password (for example): abb
f. Click to clear or set the check boxes for User Must Change Password at
Next Logon, User Cannot Change Password, Password Never
Expires, and Account Disabled as required for your local computer
administration. See Changing MOD 300 Security Group and DCOM
Settings on page 37 when making changes to the MODOPC user name
and password.
g. Select Create to the New User menu and then Select Close.
6. Select Groups, select Administrators and right click on Add to Group... to
open the Administrators Properties window.
a. Select Add...
b. Select the MODOPC user:
c. Select Add to add users to the group.
30 3BUR002262R3
Section 2 Installation OPC Server for MOD 300 Installation
d. Select OK to the Select Users and Groups window and again for the
Administrators Properties window.
7. Close out of the Computer Management window, log off and log back on as the
new user.
OPC Server for MOD 300 Installation

The OPC Server for MOD 300 installation adds the files required for using server
with other products using OPC.
1. Insert the OPC Server for MOD 300 CD-ROM into the CD-ROM drive. The
InstallShield for Windows Installer will automatically start the setup program.
2. Select Install OPC Server from the install screen.
3. Choose Run this program from its current location and select OK.
4. Security Warning. Select YES at the security warning if it is displayed
(Digital Signature is used).
5. Welcome. Select Next >to continue past the welcome window (ABB MOD300
OPC Setup).
6. License Agreement. Read the license agreement. Select acceptance of the
license agreement and select Next > to continue. Selecting the I do not accept
option will abort the installation.
7. Choose Destination Folder. Select Next > to use the default destination folder
or use the Change ... button to use another folder location. The default file path
is: C:\Program Files\ABB Industrial IT
8. Ready to Install Program. Select Install.
9. OPCServers for MOD 300 Security Setup. Enter the MODOPC user name
and password, Figure 4. This will setup the server to run as this user and will
setup the user for OMF access.
10. Install DCOM settings for remote client access. Select Yes to setup for
remote client access; otherwise, select No for local client access.
11. Select Finish to close the Setup program.
3BUR002262R3 31
Completing Installation Section 2 Installation
Figure 4. OPCServers for MOD 300 Security Setup
Completing Installation
12. Make registry changes as follows:
a. Select Start > Run and execute ‘regedit.exe’ or ‘regedt32.exe’ to start the
Registry Editor
b. Open menu HKEY_LOCAL_MACHINE
c. Open the submenu path:
Software > ABB > AdvOPCDAServer > config
d. Set the registry values for read only server, RTAB watchdog, ListSize and
BadDQ_Map as described in Server Registry Controls for
AdvOPCDAServer on page 34.
e. Open the submenu path:
Software > ABB > AdvOPCAEServer > config
f. Set the registry value for Store Ack for Condition Events, CCF Require
Ack for Clear Messages, and RTAB watchdog as described in Server
Registry Controls for AdvOPCAEServer on page 33.
32 3BUR002262R3
Section 2 Installation Server Registry Controls for AdvOPCAEServer
g. Set Reverse Time synchronization, if desired, as described in Reverse

Time Synchronization on page 35.
h. Close the Registry Editor by selecting Registry > Exit from the menu bar.
13. Create a Temp directory at the root level where the server log files (data and
alarm/event) can be written (required only if you want a log file).
14. Complete the license entry program, Appendix A, Software License Entry,
15. Restart Windows. Select Start > Shut Down... > Restart.
Server Registry Controls for AdvOPCAEServer

Store Ack for Condition Events
The Store Ack for Condition Events registry value, when set to 1, the alarm server
will store messages until they are both acknowledged and cleared.
When set to 0, the alarm server will store messages until they are cleared. The
reason for using this setting is for history message collection or logger purposes
where user interaction is not required.
CCF Require Acknowledge for Clear Messages

The CCF Require Ack for Clear Messages registry value, when set to 1, forces the
acknowledge required flag in OPC to be set when a clear message is received
regardless of its previous state.
When set to 0, the acknowledge required flag is not modified for clear messages.
RTAB watchdog(secs)
Number of seconds that the server waits before timing out response from RTAB.
Use Global Acknowledge (UseGlobalAck)

The UseGlobalAck registry value is ignored for this product. This feature is used by
MOD 300 Connect. Set this to a value of 1 to enable.
3BUR002262R3 33
Send Global Ack to LCP Section 2 Installation
Send Global Ack to LCP

If UseGlobalAck is enabled, send the global ack to LCP's. Set this to a value of 1 to
enable.
Send Global Ack to MOD30

If UseGlobalAck is enabled, send the global ack to MOD30's. Set this to a value of
1 to enable.
Server Registry Controls for AdvOPCDAServer

RTAB watchdog(secs)
Number of seconds that the server waits before timing out response from RTAB.
ReadOnlyServer
Setting this value to a non zero value will return all items as read access only and
return errors on any write to any items.
List Size (ListSize)

Set the ListSize value equal to 250 decimal for non dynamic (steady state)
subscriptions (typical for history) or set the value equal to 50 decimal for dynamic
(unstable state) subscriptions (typical for HSI interface).
Bad Data quality Map (BadDQ_Map)

The BadDQ_Map registry value is put into the OPC quality field when requesting
one of the four attributes: MEASURE_COMP, SETPOINT_COMP,
OUTPUT_COMP, DEVICE_COMP. The corresponding data quality for each of
these attributes is BadDQ. The default BadDQ_Map registry value is
OPC_QUALITY_SENSOR_FAILURE (0x10).
Table 7 lists the values that can be used in the "BadDQ_Map" value in the registry.
34 3BUR002262R3
Section 2 Installation Reverse Time Synchronization
Table 7. Valid Registry Values for BadDQ_Map
Value
OPC_QUALITY_BAD 0x00
OPC_QUALITY_UNCERTAIN 0x40
OPC_QUALITY_GOOD 0xC0
OPC_QUALITY_CONFIG_ERROR 0x04
OPC_QUALITY_NOT_CONNECTED 0x08
OPC_QUALITY_DEVICE_FAILURE 0x0c
OPC_QUALITY_SENSOR_FAILURE 0x10
OPC_QUALITY_LAST_KNOWN 0x14
OPC_QUALITY_COMM_FAILURE 0x18
OPC_QUALITY_OUT_OF_SERVICE 0x1C
OPC_QUALITY_LAST_USABLE 0x44
OPC_QUALITY_SENSOR_CAL 0x50
OPC_QUALITY_EGU_EXCEEDED 0x54
OPC_QUALITY_SUB_NORMAL 0x58
OPC_QUALITY_LOCAL_OVERRIDE 0xD8
Reverse Time Synchronization

Reverse Time Synchronization (RTS) can be configured on the windows side of a
DCN node (the RTDS). This feature allows the host (RTDS) to constantly update
the Real-time Accelerator Board (RTAB) clock. An important characteristic of this
feature is that it cannot be changed without re-booting the host node since the
registry controls this feature.
The following rules apply to a node with Reverse Time Synchronization:
• Multiple (more than one) RTS nodes can exist on a ring
3BUR002262R3 35
Setting the Reverse Time Synchronization Variable on the RTDS Section 2 Installation
• RTS nodes will always have their RTAB time synchronized with the host
regardless of the actions of the master timekeeper node
• A non RTS node cannot become master via a console time entry when an RTS
node is master timekeeper. The operator time entry is ignored with the
diagnostic:
OPERATOR TIME CHANGE REQUEST IGNORED
If RTS is disabled (default mode), host clocks are set by time synchronization
messages from their RTAB clock which receives time from the Master System
Timekeeper on the Advant OCS system.
Setting the Reverse Time Synchronization Variable on the RTDS

1. Select Start > Run and execute ‘regedit.exe’ or ‘regedt32.exe’ to start the
Registry Editor
2. Open menu HKEY_LOCAL_MACHINE
3. Open submenu Software
4. Open submenu ABB
5. Open submenu SystemServices
6. Open submenu DxBase
7. Open submenu dxTimeSync
8. Open REVERSED_SYNC_MODE and set Reverse Time Synchronization
mode as follows (must be enabled on the MOD Add-on RTDS node):
– To Enable RTS set: REVERSED_SYNC_MODE = 1
– To Disable RTS set: REVERSED_SYNC_MODE = 0
9. Close the Registry Editor by selecting Registry > Exit from the menu bar.
Setting the Reversed Interval Variable

The rate of transmission of time to the RTAB is set by the REVERSED_INTERVAL
variable. You may change the following line in the same way as described above;
however, 10 is the recommended frequency:
REVERSED_INTERVAL = 10
36 3BUR002262R3
Section 2 Installation Changing MOD 300 Security Group and DCOM Settings
Changing MOD 300 Security Group and DCOM Settings

Run the installer.exe located in:
c:\Program Files\ABB Industrial IT\MOD300 OPCServer\bin
to make changes to the MODOPC user name and password, Figure 4, or the DCOM
settings. This may be necessary if you need to add a remote client or simply change
a password.
3BUR002262R3 37
Changing MOD 300 Security Group and DCOM Settings Section 2 Installation
38 3BUR002262R3
Section 3 Configuration
OPC Server Program ID and Class ID

OPC Data Access Server
The OPC Server Program ID for data access by the OPC operation software is:
AdvOPCDAServer.OPCDAServer.1
In some cases, the class ID is required instead of the program id. In these cases use:
{D3A0BC10-19D4-11D3-8AB0-005004225121}
Registration files (da_progid_2000.reg and da_progid_nt.reg) are located in:
c:\Program Files\ABB Industrial IT\MOD300 OPCServer
Copy the file to the client box and then double click on this file to copy the program
and class ID into the local registry. This is only required if the client requires these
IDs on the local box.
OPC Alarm/Event Server

The OPC Server Program ID for alarm/event handling by the OPC operation
software is:
AdvOPCAEServer.OPCAEServer.1
In some cases, the class ID is required instead of the program id. In these cases use:
{0E9CHE50-2357-11D3-0060B05C2E70}
Registration files (ae_progid_2000.reg and ae_progid_nt.reg) are located in:
c:\Program Files\ABB Industrial IT\MOD300 OPCServer
3BUR002262R3 39
OPC Server Item ID Section 3 Configuration
Copy the file to the client box and then double click on this file to copy the program
and class ID into the local registry. This is only required if the client requires these
IDs on the local box.
OPC Server Item ID

The item ID format is described in Appendix C, Syntax for Database References.
Creating the Browse XML File

The OPC Create Browse utility creates a MODOPC.xml file of your MOD 300
database (CCF loop and FCM only not TCL or TLL) by executing from an
AdvaBuild Engineering Station (Windows or HP-UX). You can copy the utility, as
described below, to the AdvaBuild Engineering Station server and execute it from
there to create the MODOPC.xml file and then copy the XML file to your OPC
server. This allows you to browse for tag attributes locally and quickly.
The OPC Server for MOD 300 reads the MODOPC.xml file on start
up. The server must be restarted if the file is new or modified.
Creating the MODOPC.XML File on AdvaBuild for Windows

To create the MODOPC.xml file on AdvaBuild for Windows, do the following.
1. Copy the OPC Create Browse utility MODOPCBrowse.exe from the location
where it was installed (c:\Program Files\ABB Industrial IT\MOD300
OPCServer\bin) to the pc with Advabuild:
2. Launch the OPC Create Browse utility MODOPCBrowse.exe from the
location where you copied it. The Create XML display, Figure 5, will appear.
3. Enter your logged on User Name for the AdvaBuild server.
4. Enter your Password.
5. Select the AdvaBuild version you are running (used to determine the database
instance type).
6. You can use the default location, browse for a location, or enter a location for
the MODOPC.xml file. The file must be placed in c:\Program Files\ABB
40 3BUR002262R3
Section 3 Configuration Creating the MODOPC.XML File on AdvaBuild for HP-UX
Industrial IT\MOD300 OPCServer\data on the OPC server to use the file.

Specify the OPC server location now or copy the XML file there later.
7. Select Create File. This may take a few minutes depending on the size of the
database.
Figure 5. OPC Create Browse Utility
Creating the MODOPC.XML File on AdvaBuild for HP-UX

To create the MODOPC.xml file on AdvaBuild for HP-UX, do the following.
1. Copy the following files from their installed location on the pc (c:\Program
Files\ABB Industrial IT\MOD300 OPCServer\bin) to a directory on the
AdvaBuild for HP-UX Engineering Station. Do this by mapping a drive or
using FTP in ASCII mode.
modxml.ksh
modxml.awk
2. Enter the following to change file permissions to everyone:
3BUR002262R3 41
Creating the MODOPC.XML File on AdvaBuild for HP-UX Section 3 Configuration
chmod 555 modxml.*

3. Execute the OPC Create Browse utility by entering the following from the unix
box or from the pc using telent:
./modxml.ksh databasename pwd >modopc.xml
where databasename is database name to be browsed that exists on the
AdvaBuild server and pwd is the password for the database.
4. Copy or ftp the resulting modopc.xml file to the OPC Server for MOD 300
using the path:
c:\Program Files\ABB Industrial IT\MOD300 OPCServer\data.
42 3BUR002262R3
Appendix A Software License Entry
Introduction
Following the procedures described in this section is necessary for the proper
operation of the ABB software products and features that require licenses. Software
is licensed by relating a software key for each software feature with a unique
machine identifier. Software keys are obtained from the ABB software license
administration system.
This section describes the procedures for obtaining machine IDs, requesting
software keys, and installing software keys.
An overview of the software licensing procedure is shown in Figure 6.
INSTALL SOFTWARE
FILL OUT
ACCORDING OBTAIN
START SOFTWARE KEY
TO PRODUCT MACHINE ID
REQUEST FORM
INSTRUCTION
ENTER SOFTWARE
SEND RECEIVE KEYS USING
REQUEST FORM SOFTWARE KEYS LICENSE ENTRY DONE
PROGRAM
T02298d
Figure 6. Software Licensing Procedure
For the software to run, the machine ID used to generate the software key must be
present on the computer. The machine ID identifies the computer where the ABB
software will run, and the software periodically checks that the machine ID is still
3BUR002262R3 43
Obtaining the Machine ID Appendix A Software License Entry
present. A single machine ID supports multiple software keys for different features
and for different applications.
Obtaining the Machine ID

There are two types of machine IDs that the ABB licensing program supports: a
dongle or an Ethernet address. Each of the machine ID types has its advantages and
disadvantages.
Using the Ethernet address as a machine ID is generally more convenient. However,
if the Ethernet card that was chosen is ever replaced or permanently removed from
the computer, you must reapply for the software license. Refer to Obtaining the
Ethernet Address on page 45 if this is the type of machine ID you plan to use.
The Rainbow® SentinelSuperPro™ dongle is a copy protection device that attaches
to the 25-pin parallel port of the computer. Some advantages of a dongle are:
• The dongle can be moved from computer to computer. However, the software
licensed to the dongle can only execute on the computer that currently has the
dongle attached.
• Other machine IDs may need to be replaced to upgrade the computer system.
New software keys must then be requested. However, there is no need to
replace the dongle with another one (unless it breaks).
• The Rainbow SentinelSuperPro dongle allows sharing of the parallel port with
most other parallel port devices.
The dongle must be ordered from ABB, since ABB software can read only
dongles manufactured for ABB. Refer to Obtaining and Installing the Dongle on
page 45 for information about ordering a dongle.
In most cases, ABB software licensing functions support multiple dongles which
are daisy chained together. The dongle for this product can be anywhere in the
daisy chain.
44 3BUR002262R3
Appendix A Software License Entry Obtaining the Ethernet Address
Obtaining the Ethernet Address

If you plan to use the Ethernet address as the machine ID, follow the procedure
below to obtain the Ethernet card address of the computer you are installing the
software:
1. From the DOS command prompt, type ipconfig /all and press ENTER.
The Ethernet address can be obtained by choosing any listed Ethernet adapter
and recording the physical address line item. For example:
00-60-08-CC-BB-B8
2. Record this machine ID (without the hyphens) on the ABB licensing
registration form and follow the instructions in Requesting Software Keys on
page 46 to request software license keys from ABB.
Obtaining and Installing the Dongle

If you plan to use a dongle as the machine ID, you must order the dongle from ABB.
Once you receive the dongle, record the dongle number on the ABB licensing
registration form, install the dongle in the 25-pin parallel port of the server with
MOD 300 Add-on, follow the instructions below to install the Sentinel driver, and
then follow the instructions in Requesting Software Keys on page 46 to request
software license keys from ABB.
If there are multiple dongles daisy chained to the parallel port of the server, you
can add the dongle for this software anywhere in the daisy chain.
Installing Sentinel Driver

You can install the Sentinel driver from either the License Entry Program window or
an MSDOS Command Prompt window.
To install the Sentinel driver from the License Entry Program window, choose File >
Load SPRO from the menu bar.
To install the Sentinel driver from an MSDOS Command Prompt window, log in as
the Administrator, change directories to the subdirectory for the license entry
program, and run the setupx86.exe program by entering the following at the
command prompt:
3BUR002262R3 45
Requesting Software Keys Appendix A Software License Entry
…\SPRO\Win_NT\setupx86.exe
Requesting Software Keys

The license to run the OPC Server for MOD 300 must be added to the existing
license configuration. To do so, you must first use the license entry program to
request a software key as described below. Then, you can install the software key to
enter the license as described in Entering Licenses on page 51.
1. If you selected the default program group during installation, start the license
entry program from the Windows task bar by choosing Start > Programs >
ABB Industrial IT > ABB Licensing > License Entry.
This opens the License Entry Program window, Figure 7.
Some software applications automatically open the license entry program at the
end of their installation or on the initial startup of the software product.
The computer can have access to more than one computer interface. The license
entry program can access any supported and configured computer interface to
perform licensing. The default is to use the logical ICI. To select a different
interface, choose RunTime > Set Logical ICI.
2. Select the Available IDs tab of the License Entry Program window, Figure 7.
The available machine ID choices are:
– Removable Rainbow SentinelSuperPro dongle
– Ethernet address
If you plan to use the Rainbow SentinelSuperPro dongle for the machine ID
and it is not listed as an available machine ID, follow the instructions below.
Otherwise, proceed to Step 3
46 3BUR002262R3
Appendix A Software License Entry Requesting Software Keys
Figure 7. Available IDs Tab of License Entry Program Window
a. Verify that the dongle was supplied by ABB. ABB software can read only
dongles manufactured for ABB. If the dongle was not supplied by ABB,
you must obtain one before you can proceed.
b. Verify that the dongle is attached to the parallel port. In most cases, ABB
software licensing functions support multiple dongles which are daisy
chained together. The dongle for the software can be anywhere in the
daisy chain.
c. Verify that the device driver to access the dongle is installed by choosing
Start > Settings > Control Panel > Devices from the Windows task bar.
This opens the Devices window which lists all devices installed on the
computer. If the device driver to access the dongle is installed, the entries
in the Device, Status, and Startup columns of the Devices window for the
dongle should be as listed in Table 8.
3BUR002262R3 47
Table 8. Device Settings for Dongle
Device Status Startup

Sentinel Started Automatic
If an entry for the settings listed in Table 8 is not shown in the Devices
window, you must install the Sentinel driver as described in Installing
Sentinel Driver on page 45.
If you plan to use the Ethernet address for the machine ID and it is not listed as
an available machine ID, check the NetBIOS configuration on the computer as
described below. Otherwise, proceed to Step 3.
a. Choose Start > Settings > Control Panel > Network from the Windows
task bar. This opens the Network window.
b. Select the Services tab.
c. Scroll through the Network Services listed for a NetBIOS Interface entry.
d. If an entry for the NetBIOS Interface is not shown in the list of Network
Services, you must install it by clicking on the Add… button. This opens
the Select Network Services window. Select the NetBIOS Interface entry
and click on the OK button.
The Windows installation disk may be needed to complete the installation of the
NetBIOS Interface network service.
e. If an entry for the NetBIOS Interface is shown in the list of Network

Services, verify that Lana number 0 is assigned by right-clicking on the
NetBIOS Interface entry and choosing Properties… from the pop-up
menu. This opens the NetBIOS Configuration window. If an entry for
Lana number 0 is listed proceed to Step f.
f. Verify that the physical address is available from a MSDOS Command
Prompt window by logging in as the Administrator and entering the
following at the command prompt:
ipconfig/all
3. Click on the Refresh button to scan for any newly inserted machine IDs.
48 3BUR002262R3
Appendix A Software License Entry Requesting Software Keys
4. Select the desired machine ID, and then click on the Set Machine ID button to
make the selected machine ID the default used on the other tabs.
5. Locate and have available the machine ID of the computer on which the
software is already installed or is going to be installed. Otherwise, proceed to
Step 6. Refer to the appropriate Obtaining the Ethernet Address on page 45 or
Obtaining and Installing the Dongle on page 45 for information about
obtaining the machine ID of the computer.
6. Locate and have available the registration number and the validation number on
the registration form shipped with the software you are licensing.
7. Complete the registration form provided or generate and complete a new
request form using the license entry program. To generate a software key
request form,
a. Select the Licenses tab of the License Entry Program window, Figure 8.
Figure 8. Licenses Tab of License Entry Program Window
3BUR002262R3 49
b. Select the MOD300 OPCSERVER license group.
If the MOD300 OPCSERVER license group does not exist, then add a new
license group (File > Add License Group) using the name MOD300
OPCSERVER.
c. Click on the Request SWKey button.
d. Verify that the machine ID is correct. If not, enter a new machine ID and
click on the OK button to continue.
e. Enter the registration number sent with the software, and then click on the
OK button.
f. Enter the validation number sent with the software, and then click on the
OK button.
g. The available methods of returning software keys are Internet mail, postal
mail, or fax. Select the method to return the software keys and enter the
corresponding mail address or fax number.
A mail address or fax number must be included on the form.
h. Edit the form as necessary. Either save the form to a file or print the form.
8. Send the registration form to the ABB software license administrator using one
of the methods described on the registration form.
Sending the registration form also enables the software license administration
process for automatic updates. As future versions of the software become
available, all licensed, registered users will be updated automatically.
9. Wait for the software key to be returned.
50 3BUR002262R3
Appendix A Software License Entry Entering Licenses
Entering Licenses
If you are using a dongle for the machine ID, you must install the dongle before
you enter the license parameters for the software. Failure to do so, will result in
an error when the license entry program attempts to validate that the parameters
you entered match the software key and the dongle is not detected.
To enter a license, you must install the dongle (if necessary) and software key
returned from the ABB software license administrator as described below.
1. Start the license entry program from the Windows task bar by choosing Start >
Programs > ABB Industrial IT > ABB Licensing > License Entry.
2. Select the Licenses tab of the License Entry Program window, Figure 8.
3. Select the MOD300 OPCSERVER license group. If the group is not there, then
use File > Add License Group and specify MOD300 OPCSERVER.
4. Each feature of the software requires a software key to function properly. If the
software key was received as an e-mail message, follow the instructions in File
Installation on page 51. If the software key is to be installed manually, follow
the instructions in Manual Installation on page 52.
File Installation
To install the software key from a file,
1. Save the e-mail message to a temporary file as a text file (for example, lic.txt).
2. From the Licenses tab of the License Entry Program window, click on the Add
From File button.
This opens a standard Open dialog where you identify the file that contains the
software keys.
3. Select the temporary file saved in Step 1.
4. Click on the Open button.
The license entry program then reads the file and obtains the number of
licenses found in the file. The program prompts you to verify each license
before it is installed.
3BUR002262R3 51
Manual Installation Appendix A Software License Entry
5. Click on the Yes button to proceed with the license installation.

6. Click Yes again if the information is correct.
Manual Installation
To manually install the software key,
1. From the Licenses tab of the Licence Entry Program window, select the feature
whose license information you want to edit and then select the Edit License
tab.
2. The license parameters are found on the software keys form received from the
ABB software license administrator. Verify that the parameters match the
machine ID shown on the Edit License tab, Figure 9. Then, enter the following
license parameters in the corresponding fields of the Edit License tab.
– feature
– version
– expiration date
– licensed quantity
– software key
– option/user string
– machine ID
The feature string for the OPC Data Access Server is MDOPCD. The feature string
for the OPC Alarm Event Server is MDOPCA. Either one or both may be set up.
The option/user string must be entered if it is provided. (The option string is

designated as User String when the software key is sent.) In addition, the option
string must be entered in the License String field.
52 3BUR002262R3
Appendix A Software License Entry Manual Installation
Figure 9. Edit License Tab of License Entry Program Window
3. Click on the Validate button to verify that the license parameters entered
match the software key.
4. If any errors are found, including failure to enter the option string if it was
provided, correct them; otherwise, proceed to the next step.
5. Click on the Save button.
This saves the license parameters entered on the local computer.
Be sure to click on the Save button after entering and validating the license
parameters for each feature of the software. Clicking on the Validate button,
only validates the parameters entered and does not save the parameters on the
local computer.
3BUR002262R3 53
Licensing Troubleshooting Appendix A Software License Entry
Licensing Troubleshooting
Licenses are kept in a license file for each license group. Basic troubleshooting
steps are to locate the license file and view its contents.
The most common problem occurs during software key installation if the license
parameter information is validated, but then is not saved. Refer to Entering
Licenses on page 51 for information on how to enter, validate, and save the
license parameters.
To locate the license file:
1. If necessary, start the license entry program from the Windows task bar:
Start > Programs > ABB Industrial IT > ABB Licensing >License Entry.
2. From the Licenses tab of the Licence Entry Program window, select the desired
license group.
The location of the license file for the selected license group is then displayed to the
right of the License Group field. Use the Windows Explorer to verify that the
specified directory and file exist.
Table 9 lists and describes the error codes and messages generated by the License
Entry Program.
Table 9. Error Codes and Messages of License Entry Program
Code Message Description

0 Success
-1 Can’t find license file Determine the expected location of the license file. Verify that
the file does not exist. Install the product.
-2 License file corrupted Delete the license file and then re-install the product.
-3 No machine ID found None of the valid machine IDs could be found. Purchase any of
the valid machine ID types or install the software on a machine
with a valid machine ID type.
-4 Maximum number of Purchase additional licenses.
users reached
54 3BUR002262R3
Appendix A Software License Entry Licensing Troubleshooting

-5 No such feature exists Occurs when checking out a feature that has not been
licensed.
-6 No licenses checked Not an error. This message may occur if the software attempts
out to check in a license when it has not checked out a license yet.
-7 Format of feature line is Indicates an invalid license has been found in the license file.
invalid This may be due to a program other than the license entry
program being used to edit the license file. Delete the license
for the feature from the Licenses tab of the license entry
program, by selecting the feature and clicking on the Delete
button. Then, add the feature.
-8 Bad encryption code Indicates an invalid license has been found in the license file.
Re-enter the software key.
-9 Feature found but A license for the feature was found, but not for this computer.
machine ID mismatch Get a license for this computer. Use the Available IDs tab of
the license entry program to view the machine IDs found on
this computer.
-10 Feature found but A license for the feature was found, but for a different version
wrong version of the software. Obtain a license for this version of the product.
-11 Feature found but A license for the feature was found, but for a different option
wrong option string string of the software. Obtain a license for this option string of
the product. Not all products utilize an option string.
-12 Software expired The license for the feature was a temporary license which has
since expired. Ensure the date on your computer is correct, or
obtain a current license.
-13 Bad date The license entered had an invalid date.
-14 Duplicate license entry When adding a new license, an existing license for the same
feature, version, number of users and machine ID was found.
-15 Software key does not Occurs with an invalid license entry. The software key entered
match parameters does not match the features, version, and so on. Check all
fields in the license; one or more parameters may be incorrect.
3BUR002262R3 55
Licensing Troubleshooting Appendix A Software License Entry

-16 License entry not found When the license entry program deleted a license, the
specified feature was not found.
-17 Cannot write to license Determine the expected location of the license file. Verify the
file file does not exist or is not read-only. Install the product.
-18 Too many licenses A program requested more licenses than were available. This
requested error indicates that licenses for the desired feature are
available, but not in the quantity requested. Request fewer
licenses, if possible, or obtain more licenses.
-19 Cannot read license file Determine the expected location of the license file. Verify the
file does not exist or is not read-only. Install the product.
-20 Start date for feature not
reached
-21 Machine ID not found A license was found, but for a machine ID that is not present in
this computer. Get a license for this computer. Use the
Available IDs tab of the license entry program to view the
machine IDs found on this computer.
-22 Machine ID type not A request for a specific machine ID type was made, but that
found machine ID type could not be found on this computer.
-23 Machine ID type not A request for a specific machine ID type was made, but that
supported machine ID type could not be found on this computer.
-24 Could not read machine Check the Ethernet card.
Ethernet address
-25 Could not open network Check the Ethernet card.
device
-28 Error in registry for Ensure you have Administrator privileges on the computer. Re-
license file install the product.
-29 Error in registry for Ensure you have Administrator privileges on the computer. Re-
machine ID install the product.
56 3BUR002262R3
Appendix B Advant OCS Database
Requirements
You must configure a GENERICD object in the MOD 300 database to properly
represent the MOD OPC Server as a node on the Distributed Communications
Network (DCN). This object is a child of the AREA object and represents a
subsystem in the area. In addition, Version 1.1 of the OPC Server for MOD 300
supports alarm and event routing. Alarms and events to be routed to the OPC server
use the message routing configuration fields in the Area templet.
The GENERICD and AREA database objects are inserted into the MOD 300
database hierarchy and object attributes are defined in the following sections and as
described in the following books:
AdvaBuild Control Builder for Windows User’s Guide for AdvaBuild Control
Builder and Template Builder.
AdvaBuild Basic Functions User’s Guide for AdvaBuild Structure Builder and
Template Builder.
Configurator User’s Guide for Multibus-based Configurator/Data Processor
(uses GENERIC_DPSS).
3BUR002262R3 57
GENERICD Object Appendix B Advant OCS Database
GENERICD Object
The Template Builder view of the GENERICD object is shown in Figure 10.
Figure 10. GENERICD Object, Template Builder Window
The GENERICD object attributes are described below.
58 3BUR002262R3
Appendix B Advant OCS Database PHYSICAL DEVICE
PHYSICAL DEVICE
This is the DCN node address. This must be the same DCN address that was defined
for the MOD 300 OPC node during software loading. The address is expressed as a
decimal number. Any number from 1 to 255 is valid; however, addresses with a
lower order hexadecimal value of one are reserved for configurator/data processor
(CDP) nodes and should not be used for the MOD 300 OPC node, Table 10. Be sure
to enter a decimal number in the PHYSICAL DEVICE field.
Table 10. DCN Addresses for Nodes with Configurator Software
Address (Hex) Decimal Equivalent

01 1
11 17
21 33
31 49
41 65
51 81
61 97
71 113
81 129
91 145
A1 161
B1 177
C1 193
D1 209
E1 225
F1 241
3BUR002262R3 59
AUTO START Appendix B Advant OCS Database
AUTO START
This field determines whether or not the node starts automatically when the
software is downloaded. The only valid choice for a GENERICD node is YES.
SOFTWARE NAME
This field determines the functionality of a Multibus-based GENERICD node. This
field is not applicable for the node. Leave it at its default value.
DO RATE
This attribute is not applicable for MOD 300 OPC application.
SECONDARY DP, BACKUP ENABLE, and BACKUP OVERRIDE

These fields have not been implemented. Leave them at their default values.
DEFAULT ENVIRONMENT
This attribute is not applicable for MOD 300 OPC applications.
NODE TYPE
This field specifies the hardware platform for the GENERICD node. Use
ADVANT_STATN.
60 3BUR002262R3
Appendix B Advant OCS Database AREA Object
AREA Object
Version 1.1 of the OPC Server for MOD 300 supports alarm and event routing.
Do the following to set up the necessary structures. If this has not been done
already, you will need to recompile and install.
Alarms and events to be routed to the OPC server use the message routing
configuration fields in the Area templet. Scroll to display the MESSAGE CENTER
fields (AREA EDITORS fields are not applicable), Figure 11 (representative).
Figure 11. Message Center Fields for CONSLIB or Area Object
3BUR002262R3 61
Message Center Fields Appendix B Advant OCS Database
Message Center Fields

Message fields are used to specify the destinations of messages originating in this
configuration area. During runtime, the following types of messages can be
generated by the system: CCF event, CCF alarm, TCL event, TCL billboard and
system error (diagnostic).
Only the alarms that are absolutely necessary should be configured. The list of
message destinations set up in the system database has a direct bearing on the
communications load resulting from an alarm burst. Each destination for a
message adds to the load.
The destination and type of messages are defined by entries to the following fields:
MESSAGE CTR Use LOGGER as the object ID for the device to receive
messages. The ID must be the one assigned when the
object was inserted in the database.
MESSAGE TYPE Is the type of message. Valid entries for type are:
CCF_ALARM
CCF_EVENT
CCF_BOTH - This option designates both CCF alarm
messages and event messages.
TCL_EVENT
TCL_BILLBOARD - This option is used to designate TCL
unit messages that are generated by TCL MESG and
REPLY statements and programmable unit alarms
generated by TCL UNIT_ALARM statements.
TCL_BOTH - This option designates both TCL event
messages and billboard messages.
SYSTEM
BOTH - This option designates all message types
designated by CCF_BOTH and TCL_BOTH.
ALL - This option designates all message types.
REMOTE TYPE The entry specifies the object type and must be: LOGGER
62 3BUR002262R3
Appendix B Advant OCS Database Message Center Entries for Alarm/Event Loggers
Message Center Entries for Alarm/Event Loggers

Alarm/Event Loggers are software devices that log messages to printers and/or
disks. You must make an entry in the MESSAGE CTR and MESSAGE TYPE fields
for each type of message that you want to log on a specific logger. Any combination
of message types is valid. If a system has more than one configuration area, entries
must be made to the MESSAGE CTR and MESSAGE TYPE fields of each AREA
object.
In the following examples, LOGGER1 is the object ID assigned to the object
representing this Logger.
Example 1 - These entries send all CCF and SYSTEM messages to LOGGER1:
LOGGER1 CCF_BOTH
LOGGER1 SYSTEM
Example 2 - This entry sends all CCF and TCL messages to LOGGER1.
LOGGER1 BOTH
Example 3 - This entry sends all messages to LOGGER1.
LOGGER1 ALL
Message Routing from Operator Station

To route messages, enter the message destinations and the types of messages to be
routed in a MSG_ROUT object to the destinations in the MESSAGE CTR edit
window of the CONSLIB object. This object provides the means to configure how
console log on and/or alarm acknowledgment messages are routed
Indicate the message destination by entering the object ID of the destination
package. For message type enter any one of the following:
CONS_LOG_ONS Console log on
CONS_ACKS Console alarm acknowledgment
CONS_BOTH Both console log on and console alarm acknowledgment
There is a limit of 256 destinations for messages. Messages of a specific type from a
configuration area can be sent to no more than 40 destinations.
3BUR002262R3 63
Recommended Message Centers for Routing to A/E Server Appendix B Advant OCS Database
Recommended Message Centers for Routing to A/E Server

Route to the node: CCF_ALARM, TCL_BILLBOARD, SYSTEM
Route to Logger: CCF_EVENT, TCL_EVENT, CONS_ACK, CONS_LOG
Changes to Loop Type and UREL Tag Name

Whenever the following loop information changes, it causes OMF Object ID's to
change and not be picked up because the Object ID already exists.
• Changing the loop type such as when adding or deleting Auto/manual FCM's,
PID's or adaptive functions to a PID.
• Changing of a UREL tag name, (UREL and Unit name stay the same but the
physical tag is changed).
To maintain the OMF object resolution you must perform some maintenance on the
nb.store file located in the install path (default is c:\Program Files\ABB Industrial
IT\Data\SystemServices\OMF). Specifically, every node with System Service needs
to have the file deleted and then the node rebooted for the file to be rebuilt. This
may not be necessary if the you are not using the point for OPC access.
64 3BUR002262R3
Appendix C Syntax for Database References
Format of Expressions
This appendix describes the syntax of database references to process objects.
Database references to the following types of parameters are supported:
• loop parameters
• loop FCM parameters
• array element parameters
• recipe item parameters
• Taylor Ladder Logic (TLL) parameters
3BUR002262R3 65
Loop Parameter Reference (Tag Access) Format Appendix C Syntax for Database References
Loop Parameter Reference (Tag Access) Format

Loop parameter references are used when you are referencing a device or
continuous loop parameter that is unique in the loop. For instance, a continuous
control loop can have only one measured variable (MEASURE) and only one FCM
having a SETPOINT (PID controller).
Two elements are necessary to reference this kind of value: the name of the loop (the
tag), and the parameter's mnemonic. Loop accessible parameter mnemonics are
provided in instruction book 3BUR 000 239Rnn01, Data Base Tables.
The format for entering a loop parameter reference when creating an OPC Item ID
is:
tag.parameter
where
tag is the name (tag) of the loop defined on the Loop

Definition Templet or Device Loops Templet.
parameter is the parameter mnemonic
The following examples show the form of an OPC Item ID for loop parameter
references:
CV101.DEV_CMND
F125.MEASURE
FIC105.SETPOINT
The following are attributes that combine data quality and value. See the data
quality map attribute (Table 7) for the values that can be used in the "BadDQ_Map"
value in the registry.
MEASURE_COMP (DQ_MEAS and MEASURE),
*SETPOINT_COMP (SPT_ALM Bad Data Quality and SETPOINT),
*OUTPUT_COMP (OUTP_ALM Bad Data Quality and OUTPUT),
*DEV_STATE_COMP (DEV_ALRM Bad Data Quality and DEVICE_STAT)
*These require that Suppress Alarm be No (disabled) for the loop.
66 3BUR002262R3
Appendix C Syntax for Database ReferencesFCM Parameter Reference (Tag-FCM Access) Format
FCM Parameter Reference (Tag-FCM Access) Format

An FCM parameter reference is used when you are referencing a parameter that can
occur in more than one FCM of a continuous control loop. For instance, a loop can
have an input source in more than one of its FCMs, making it necessary to identify
the FCM for the desired value, as well as the loop's tag.
The concept of FCMs is explained in instruction book 3BUR 000 238Rnn01,
Configurable Control Functions (CCF) User’s Guide. A knowledge of the FCMs in
your system is necessary when using this type of database reference.
Three elements are required to reference this kind of value: the name of the loop
(the tag), the name of the appropriate FCM, and the parameter's mnemonic. FCM
parameter mnemonics are provided in instruction book 3BUR 000 239Rnn01, Data
Base Tables.
The format for entering an FCM parameter reference when creating an OPC Item ID
is:
tag.fcmname/parameter
where
tag is the name (tag) of the loop defined on the Loop

Definition Templet.
fcmname is the name of the FCM defined on the Loop Definition
Templet
parameter is the parameter mnemonic
The following examples show the form of an OPC Item ID for tag-FCM accessible
FCM parameter references:
F125.LKP/RESULT
TIC_10.AIN/RANGE_CK
3BUR002262R3 67
Array Element Parameter Reference Format Appendix C Syntax for Database References
Array Element Parameter Reference Format

Array element parameter references are used when you are referencing a particular
element of a TCL array.
Four items are necessary to reference this kind of value: the name of the unit where
the TCL array is loaded, the array's name, the location of the element within the
array, and the type of data stored in the array.
The format for entering an array element parameter reference when creating an OPC
Item ID is:
unitname.array/arrayname/index1/index2/parameter
where:
unitname is the name of unit where the array was loaded by a TCL
statement
array is a keyword that defines the reference format.
arrayname is the name of the array whose element value you want
to display
index1 is the location within the first dimension of the array,
expressed as an integer, for the element whose value
you want to display. The value is 0 to 32766 for REAL or
INTEGER types, or 0 to 1629 for STRING types.
index2 is the location within the second dimension of the array,
expressed as an integer, for the element whose value
you want to display. The value is 0 to 32766 for REAL or
INTEGER types, or 0 to 1629 for STRING types. This
location is only required when the array is two
dimensional.
parameter is the mnemonic for the value to display. The only valid
parameter for all data types (REAL, STRING, INTEGER,
BYTES, and TWO_BYTES) is:
VAL (value of item).
The data type is automatically determined from the array
data.
68 3BUR002262R3
Appendix C Syntax for Database References Array Element Parameter Reference Format
The location you specify for the element you want to display must be within the
array's declared size. For example, if you want to display the value for an element
of a single dimensional array containing 10 elements, you would enter an integer
from 1 to 10 for index1. If you enter a location larger than the number of
elements in the array, a bad quality error or graphic error will appear on the
runtime display instead of the element's value. This is because there is no such
location within the array from which to retrieve a value.
The following example shows the form of an OPC Item ID for array element
accessible array parameter references:
UNIT1DPSS.array/IARRAY/6/VAL
3BUR002262R3 69
Recipe Item Parameter Reference Format Appendix C Syntax for Database References
Recipe Item Parameter Reference Format

Recipe item parameter references are used when you are referencing a particular
recipe item.
Dependency checking for writes to Recipeitem/VAL has to be preformed by the

writing application. All Advant HSI applications perform this test before
allowing the write to the recipe item.
Four elements are necessary to reference this kind of value: the name of the unit
where the recipe is loaded, the recipe item, the type of data the item contains, and
the parameter.
The format for entering a recipe item parameter reference when creating an OPC
Item ID is:
unitname.recipe/recipeitem/datatype/parameter
where:
unitname is the name of unit where the recipe was loaded by a

TCL statement
recipe is a keyword that defines the reference format.
recipeitem is the name of the recipe item whose value you want to
display.
datatype is the type of data you want the recipe item's value
displayed as. Valid data types are REAL, INTEGER, and
STRING. The data type you specify must match the data
type specified when the recipe was created in TCL. If the
data types do not match, asterisks appear on the
runtime display instead of the item's value. This is
because no item of the specified type exists in the
recipe. For example, if you reference a real recipe item
and the recipe created in TCL contains integer or string
items, asterisks are displayed since no real items exist in
the recipe.
70 3BUR002262R3
Appendix C Syntax for Database References Recipe Item Parameter Reference Format
parameter is the mnemonic for the value to display. Valid

parameters for real and integer type recipe items are
VAL (value of item), HI (high limit for item), and LO (low
limit for item). Valid parameters for string type recipe
items are VAL (value of item), DES (descriptor for item),
and ENG (engineering units label for item).
The following example shows the form of an OPC Item ID for a recipe item
parameter reference:
UNIT1DPSS.recipe/COOKTEMP/REAL/VAL
3BUR002262R3 71
Taylor Ladder Logic (TLL) Parameters Reference Format Appendix C Syntax for Database
Taylor Ladder Logic (TLL) Parameters Reference Format

A Taylor Ladder Logic (TLL) parameter reference is used when you reference a
parameter of a TLL element.
Three components are required to reference this kind of value: the name of the TLL
element, the name of the TLL type, and the TLL parameter's mnemonic.
The format for entering a TLL parameter reference when creating an OPC Item ID
is:
tag.type/parameter
where
tag is the name of the TLL element defined in the TLL

Templet.
type is the name of the TLL element type as follows:
I_O Input/Output Points
TIM Timer
CNT Counter
REG Register
parameter is the TLL parameter mnemonic. TLL parameter
mnemonics are provided in instruction book 3BUR 000
243Rnn01, Taylor Ladder Logic (TLL).
The following examples show the form of an OPC Item ID for TLL parameter
references:
COUNT1.CNT/AC
TIMER1.TIM/AC
72 3BUR002262R3
Appendix C Syntax for Database References Alarm/Event OPC References
Alarm/Event OPC References

This section is for reference only. OPC clients should use the designed interfaces to
get this information programmatically.
Table 11. Event Categories, Types, Conditions and Subconditions
Event Category Event Type Condition Subcondition

CCF Condition "MEASURE" "HIHI" HiHi alarm
"HI" Hi alarm
"LO" Lo alarm
"LOLO" LoLo alarm
"RATE" Rate alarm
"BDDQ" Bad Data Quality alarm
"OUTPUT" "HI" Hi alarm
"LO" Lo alarm
"RATE" Rate alarm
"SETPOINT" "HI" Hi alarm
"LO" Lo alarm
"DEVIATION" "HI" Hi alarm
"LO" Lo alarm
"DEVICE" "STATE" State alarm
"TIMEOUT" Timeout alarm
3BUR002262R3 73
Alarm/Event OPC References Appendix C Syntax for Database References
Table 11. Event Categories, Types, Conditions and Subconditions (Continued)
Event Category Event Type Condition Subcondition

CCF Condition "DEVICE" "ABNORM_CHG" Abnormal Change
alarm
"ILLEGAL_ST" Illegal State alarm
"BAD_INP_DQ" Input Data Quality
"TCL_TIMEOUT" TCL Timeout alarm
"TCL_FAIL" TCLFail alarm
"CMD_LOCK" LockAl alarm
TCL BILLBOARD Tracking N/A N/A
TCL REPLY Condition <SEQUENCENAME> "REPLY"
TCL ERROR Tracking N/A N/A
TCL ALARM Condition <SEQUENCENAME | "UNIT_ALARM"
ALARM#>
DIAG Tracking N/A N/A
User Log Off Simple N/A N/A
User Tracking N/A N/A
Acknowledge
Parameter Tracking N/A N/A
Change
74 3BUR002262R3
Appendix C Syntax for Database References Alarm/Event OPC References
These vendor specific attributes are also for reference only.

• CCF
– Loop Descriptor
– Alarm Value
– Alarm Limit
The Alarm Limit value will only be High, Normal, or Low because it is not
updated while in alarm. For example, if an alarm occurs at the Low limit, then the
alarm limit value is the low alarm limit until it clears even though the actual
alarm value may be a high alarm. The limit will change after the alarm clears.
– Device State
– Device State Text
– Unit Name
• TCL BILLBOARD
– Sequence Name
– Sequence Number
– Message Number
• TCL REPLY
– Sequence Name
– Sequence Number
– Message Number
– Reply Type (0 = Integer, 1 = Float, 2 = String)
• TCL ERROR
– Sequence Name
– Sequence Number
– Message Number
• TCL ALARM
– Sequence Name
– Sequence Number
– Message Number
– Alarm Number
• DIAG
– Level (0 = Operator Level, 1 = Engineer Level)
– Code Message
3BUR002262R3 75
Alarm/Event OPC References Appendix C Syntax for Database References
• User Log Off

– Node Name
– Access Class
* Supported by AdvaCommand HP-UX systems: "Operator", "Engineer",
"Supervisor", "Environment" (Environment reports as Engineer)
* Not supported by AdvaCommand HP-UX systems: "Computer", "Super
User", "Program"
– On/Off ("User Logged On", "User Logged Off")
• User Acknowledge
– Description
– Attribute (Acked Attribute "MEASURE", "OUTPUT", "SETPOINT",
"DEVIATION", "DEVICE")
– User Name
• Parameter Change
– Description
– Old Value
– New Value
– User Name (this will be empty for TCL changes)
76 3BUR002262R3
Appendix D Upgrade
Introduction
This section describes how to install Version 1.1 of the OPC Server for MOD 300
over Version 1.0. If you are doing a new install, follow the instructions in Section 2,
Installation.
Upgrade Procedure
Follow these steps to perform a upgrade.
1. Save your current System Service settings as found on the Communications
Configuration Tool (see Figure 3).
2. Uninstall the previous version of the OPC Server for MOD 300
a. Select Start > Settings > Control Panel
b. Open Add/Remove Programs
c. Select ABB MOD 300 OPC Server
d. Select the Remove ... button
3. Uninstall the previous version of the ABB System Services
a. Select Start > Settings > Control Panel
b. Open Add/Remove Programs
c. Select ABB System Services
d. Select the Add/Remove ... button
4. Uninstalling ABB System Services will force a reboot.
3BUR002262R3 77
Upgrade Procedure Appendix D Upgrade
5. Follow the instructions in Section 2, Installation to install System Services and

the OPC Server for MOD 300.
78 3BUR002262R3
INDEX
A F
Administrator Privileges 30 FCM Parameter Reference Format 67
AdvaBuild 16 File Download Dialog 23
AdvaCommand 16
Advant OCS Control Network 23 G
Alarm/Event Loggers 63 GENERICD
Array Element Reference Format 68 Database 23
Auto Start, GENERICD Object 60 Object 29
GENERICD Object 57 to 58
B
BadDQ_Map 34, 66 I
Internet Information Services 17
C IP Address 22
CCF Require Ack for Clear Messages 33
COM 11 L
Control Network 28 License Entry Program 23
List Size (ListSize) 34
D ListSize 34
DCN 11, 15 Loop Parameter Reference Format 66
DCN Address 28 to 29, 59
DCN Loadings 18 M
DCOM 11, 30 Machine ID 44
Demand Lists 18 Machine Identifier 43
DO Rate, GENERICD Object 60 Master Timekeeper Node 36
Documentation, On-line 13 Message Center 61
Dongle 45 MESSAGE CTR 63
MESSAGE TYPE 63
E MOD 300 Database 57
eDCN 15 MOD 300 DCN 23
Environment, Default, GENERICD Object 60 MOD 300 System 16
Ethernet Address 45 MODOPC User Name 37
Event Category 73 MODOPC User Password 30
MSG_ROUT object 63
3BUR002262R3 79
Index
N REVERSED_SYNC_MODE 36
Network Address 29 RTAB 15
Node Type, GENERICD Object 60 RTAB watchdog(secs) 33
O S
OMF 30 Security Account 30
OMF Settings 28 Security Warning 23
On-line Documentation 13 Send Global Ack to LCP 34
OPC 12 Send Global Ack to MOD30 34
OPC Item ID Sentinel Driver 45
Array Element 68 Software Key 43
FCM Parameter 67 Software Keys 46
Loop Parameter 66 Software License Administration 43
Recipe Item 70 Software Name, GENERICD Object 60
TLL Parameter 72 Store Ack for Condition Events 33
OPC Server 15 Subscription Lists 18
OPC Server Item ID 40 System Services 9, 21, 26 to 27
OPC Server Program ID 39
T
P Template Builder 58
Password 30, 37 Time 23
PCI-type Realtime Accelerator Board 25 TLL Parameter Reference Format 72
Physical Device, GENERICD Object 59
U
R UseGlobalAck 33
RAM Memory 17 User Name 30
ReadOnlyServer 34
Real-time Accelerator Board (RTAB) W
Installation 25 Windows 2000 17
Requirements 21
Recipe Item Reference Format 70
Reference Formats
Array Element 68
FCM (Tag-FCM Access) 67
Loop Parameter 66
Recipe Item 70
TLL Parameter 72
Registry 32, 39 to 40
Reverse Time Synchronization Mode 36
Reversed Interval Variable 36
80 3BUR002262R3
3BUR002262R3 Litho in U.S.A. September 2002
Copyright © 2002 by ABB. All Rights Reserved
® Registered Trademark of ABB.
™ Trademark of ABB.
http://www.abb.com/control
Automation Technology Products Automation Technology Products Automation Technology Products

Wickliffe, Ohio, USA Västerås, Sweden Mannheim, Germany
www.abb.com/processautomation www.abb.com/processautomation www.abb.de/processautomation
email: industrialitsolutions@us.abb.com email: processautomation@se.abb.com email: marketing.control-products@de.abb.com

3BUR002262R3 - en OPC Server For MOD 300 Version 1 1 1 - Installation and Configuration

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3BUR002262R3 - en OPC Server For MOD 300 Version 1 1 1 - Installation and Configuration

Uploaded by

Copyright:

Available Formats

OPC Server for MOD 300

Installation and Configuration

Installation and Configuration

Copyright © 2002 ABB Inc.

Acrobat Registered trademark of Adobe Systems, Incorporated.

Adobe Registered trademark of Adobe Systems, Incorporated.

Industrial IT Trademark of ABB Inc.

Ethernet Trademark of Xerox Corporation

Microsoft Registered trademark of Microsoft Corporation.

OPC Trademark of the OPC Foundation

SentinelSuperPro Trademark of the Rainbow Technologies Inc.

About This Book

OPC Server Program ID and Class ID ............................................................................39

Appendix A - Software License Entry

Appendix B - Advant OCS Database

Message Routing from Operator Station ............................................................. 63

Appendix C - Syntax for Database References

Use of Warning, Caution, Information, and Tip

Information icon alerts the reader to pertinent facts and conditions.

Table 1. Related Documentation

Category Title Description

What You Can Do with OPC Server for MOD 300

What’s New in This Release

Product Release History

Table 2. Release History

Prerequisites and Requirements

Operating Software Requirements

Table 3. Computer Requirements

Description Recommended Minimums

Table 4. Software Requirements

Table 5. DCN Loadings

Number of DCN load

Table 5. DCN Loadings

Number of DCN load

Table 6. Classic Controller FBus loadings

Before You get Started

software installation is the Real-time Accelerator Board (used to connect to an

Start-up and Shut-down Procedures

File Download and Security Warning Dialogs

When to Re-start Your Computer

Figure 1. OPC Server for MOD 300 Install Screen

6. Install System Services Software, System Services on page 26.

Installing a PCI-type Real-time Accelerator Board

Prerequisite Support Software

• Internet Explorer can run during installation; however, it is strongly

System Services Installation

Figure 2. Launching the Communications Configuration Tool

This displays the Communications Configuration Tool, Figure 3.

Figure 3. Communications Configuration Tool

15. Configure the Network Address section.

For E-DCN connection, follow these guidelines to configure the E-DCN

Create MOD 300 OPC User

OPC Server for MOD 300 Installation

Figure 4. OPCServers for MOD 300 Security Setup

g. Set Reverse Time synchronization, if desired, as described in Reverse

Server Registry Controls for AdvOPCAEServer

CCF Require Acknowledge for Clear Messages

Use Global Acknowledge (UseGlobalAck)

Send Global Ack to LCP

Send Global Ack to MOD30

Server Registry Controls for AdvOPCDAServer

List Size (ListSize)

Bad Data quality Map (BadDQ_Map)