MOD 300 Engineering Displays

Version 1.0/1

Installation
MOD 300 Engineering Displays
Version 1.0/1

Installation
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 © 2003 ABB Inc.

All rights reserved.
Release: May 2003
Document number: 3BUR002374R1 Rev A

TRADEMARKS
Registrations and trademarks used in this document include:

Acrobat Registered trademark of Adobe Systems, Incorporated.

Adobe Registered trademark of Adobe Systems, Incorporated.

Advant Registered trademark of ABB Inc.

AdvaBuild Registered trademark of ABB Inc.

Ethernet Trademark of Xerox Corporation.

Industrial IT Trademark of ABB Inc.

Microsoft Registered trademark of Microsoft Corporation.

MOD 300 Trademark of ABB Inc.

Windows Registered trademark of Microsoft Corporation.

 TABLE OF CONTENTS

About This Book

General ..............................................................................................................................7
Use of Warning, Caution, Information, and Tip ................................................................7
Document Conventions .....................................................................................................8
Terminology.......................................................................................................................9
Related Documentation ...................................................................................................10
On-line Documentation ........................................................................................11
On-line Help.........................................................................................................11

Section 1 - Introduction
Product Overview ............................................................................................................13
Product Release History ..................................................................................................14
Prerequisites and Requirements ......................................................................................14
Server Hardware...................................................................................................14
Server Software ....................................................................................................14
Client Hardware ...................................................................................................15
Client Software.....................................................................................................15
Licensing .........................................................................................................................16
Security Settings ..............................................................................................................16
AdvaBuild User....................................................................................................16
Client User ...........................................................................................................17
DCOM Settings ....................................................................................................17

Section 2 - Installation
General Information ........................................................................................................19
Installation Procedure ......................................................................................................19

3BUR002374R1 Rev A 5
Table of Contents

Installing Software .......................................................................................................... 20

Completing License Entry............................................................................................... 20
Add Client Users to Server.............................................................................................. 21
Set DCOM....................................................................................................................... 22
Windows 2000 Servers and Clients ..................................................................... 22
Windows XP Clients ............................................................................................ 22
Set Permissions for Windows XP Client Users............................................................... 23
Shut-down and Start-up Procedures ................................................................................ 23
Product Verification......................................................................................................... 23

Appendix A - Software License Entry

Introduction ..................................................................................................................... 25
Obtaining the Machine ID............................................................................................... 26
Obtaining the Ethernet Address........................................................................... 27
Obtaining and Installing the Dongle.................................................................... 27
Installing Sentinel Driver .................................................................... 27
Requesting Software Keys .............................................................................................. 28
Entering Licenses ............................................................................................................ 33
File Installation .................................................................................................... 33
Manual Installation .............................................................................................. 34
Licensing Troubleshooting.............................................................................................. 36

INDEX

6 3BUR002374R1 Rev A
 About This Book

General
This book describes how to install the MOD 300 Engineering Display software to
support configuration activities with AdvaBuild for Windows 2000. Use this section
as a guide to the information presented. Related documentation references are also
provided.
Operation of the MOD 300 Engineering Display software is described in MOD 300
Engineering Displays Operation. Installation and configuration information for the
AdvaBuild product (required to run this product) is in AdvaBuild Administrator’s
Guide.

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 indicates the presence of a hazard which could result in
electrical shock.

Warning indicates the presence of a hazard which could result in personal injury.

Caution 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 alerts the reader to pertinent facts and conditions.

3BUR002374R1 Rev A 7
 Tip 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: choose File > New >
Type.
– 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 to 30.

8 3BUR002374R1 Rev A
 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 italic letters:
sequence name

Terminology
You should be familiar with the following list of terms used in this instruction.

Term Description
AC410, AC460 Advant Controller 410 and 460
AdvaBuild Configuration package for MOD 300 systems. The
Engineering Station for this product requires the
Windows 2000 operating system.
Advant OCS Advant Open Control System or MOD 300 control
system
CCF Configurable Control Functions
Client Computer used as a client to server.
DCN Distributed Communication Network. Connects MOD
300 control system nodes.
FCM Function Class Module
HSI Human System Interface
Node A point of interconnection to a network. Every physical
PC box with its own host name is considered a node.
Node level objects CNTRLLER, CONSOLE, GENERICD, AC410,
AC460MOD, BUC, DCN_DCN, ADVANT_D2D
Object Any configurable entity whose data is associated with
some real object such as a valve or transmitter.
PLC Programmable Controller Interface.

3BUR002374R1 Rev A 9
 Term Description
RDP Remote Display Protocol. Certain MOD 300 engineering
displays are accessed using RDP. These include Auto
Tune and PLC, TRIO, Serial Port Configuration.
TCL Taylor Control Language (sequence control)
TLL Taylor Ladder Logic
TRIO Taylor Remote I/O
Windows Microsoft Windows 2000 Operating System (as used in
this book).

Related Documentation
This instruction provides information only for installation of the MOD 300
Engineering Display software. The following 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 installation of PC
Installation AdvaBuild Version 3.3/x for Windows Installation and project administration for
2000 Administrator’s Guide AdvaBuild suite of software products.
MOD 300 Engineering Displays, Refer to the release notes for current
Release Notes release information, known problems,
fixed problems and update instructions.
Microsoft Windows Administrator’s Install, uninstall, administration, and
Guide registry of Windows operating system.
Operation MOD 300 Engineering Displays, Describes how to use the MOD 300
Operation Engineering Displays workplace for
runtime views of CCF, TCL, TLL, RDP
displays and FCM templates.

10 3BUR002374R1 Rev A
On-line Documentation
On-line documentation for MOD 300 Engineering Display software is accessible
via the Start menu on the Windows task bar. The path is Start > Programs > ABB
Industrial IT > Control IT > MOD 300 Engineering Displays > help.
Documentation is also 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. Locate the MOD 300 Engineering Display books as listed in
Table 2.
.
Table 2. On-line Documentation

To Open this Document Go to this location

MOD 300 Engineering Display Installation At the root of the Installation CD.
(3BUR002374R_)
MOD 300 Engineering Display Release Notes At the root of the Installation CD
(3BUR002376R_) (MODEngDisplayV1.0_0ReleaseNotes.html)
MOD 300 Engineering Display Operation In the installation directory:
(3BUR002375R_) Program Files/ABB Industrial IT/MOD 300
Engineering Displays/help

On-line Help
Comprehensive on-line help is available for the software. Access to the complete
help files is available via the Help menu in the main menu bar. Specific topics
within the help file are also accessible using context-sensitive help (F1).

3BUR002374R1 Rev A 11
12 3BUR002374R1 Rev A
 Section 1 Introduction

Product Overview
MOD 300 Engineering Display software gives you engineering display access to the
MOD 300 control network (DCN) through the AdvaBuild for Windows Engineering
Station. The capability of having engineering display support available with the
Advabuild configuration software allows you to easily complete integration of the
control system. An additional benefit is that the displays provide access to many
tags within the MOD 300 system that are not necessary for normal operations.
MOD 300 Engineering Displays allow engineering control of Configurable Control
Functions (CCF), Taylor Control Language (TCL), Taylor Ladder Logic (TLL) and
select Remote Display Protocol (RDP) functions. In addition, the MOD 300
Engineer can tune fields of loop and FCM templates. The engineering displays
feature the standard operations look found on the Process Portal with MOD 300
Connect and the Advant OCS system. This product does not support alarms and
events, graphics, historical trends, and messages.
The MOD 300 Engineering Display software is a client server product. The server
software needs to be installed and run on the AdvaBuild server. Multiple client
machines are supported by one server and can be installed on a Windows
workstation. The MOD 300 Engineer client user needs to be set up as a user on the
AdvaBuild server as part of the User group.
The AdvaBuild server requires System Services, AdvaBuild Administration,
Control Builder and Oracle. In addition, TCL Builder and TLL Builder options may
be included. System Services requires a PCI RTAB board to connect to the Advant
OCS Control Network (MOD 300 DCN). System Services software supports basic
services including network communications, object handling, process supervision,
and system messaging. The Administration software allows the Administrator to
manage projects and the users assigned to each project, manage the journal, and
manage object name reuse.

3BUR002374R1 Rev A 13
Product Release History Section 1 Introduction

Product Release History

Table 3 lists the release history for the MOD 300 Engineering Display software.

Table 3. Release History

Version Description
1.0/1 This release includes the following changes:
• Unit Overview display for TCL
• Font size selections for the Sequence Debug and Diagnostic
Message displays.
• Print to file selection when printing diagnostic messages
1.0/0 Initial release of the MOD 300 Engineering Display software for
the Windows 2000 platform.

Prerequisites and Requirements

Server Hardware
The following hardware is required to support the server installation. These
requirements are the same as for the AdvaBuild server:
• Intel Pentium CPU, minimum 500 MHz clock frequency.
• 512 MByte primary memory for a client/server machine.
• Installation drive must be 4 GByte or larger with 1.5 GByte of free space
recommended.
• At least 19” screen is recommended. More than 256 display colors is
recommended.

Server Software
Install AdvaBuild 3.3/2 for Windows 2000 before installing the MOD 300
Engineering Displays 1.0/1 software. See the MOD 300 Engineering Displays
Release Notes for restrictions when using AdvaBuild 3.3/0 and 3.3/1.

14 3BUR002374R1 Rev A
Section 1 Introduction Client Hardware

AdvaBuild 3.3/2 software requires the following software (see the AdvaBuild
Version 3.3/x for Windows 2000 Administrator’s Guide for specific requirements):
• Microsoft Windows 2000 Professional or Server with Service Pack 3
• Microsoft Internet Explorer 5.01 or greater must be installed (supports required
level of Windows Script Host)
• Valid static IP address. The software will not function properly without a valid
static IP address. DO NOT use DHCP.

Client Hardware
The following hardware is required to support the client installation.
• Intel Pentium CPU, minimum 500 MHz clock frequency.
• 256 MByte primary memory.
• At least 19” screen is recommended. More than 256 display colors is
recommended.

Client Software
The following software must be installed, before you install the MOD 300
Engineering Display software:
• Microsoft Windows 2000 Professional or Server with Service Pack 3
(Clients can run on Windows XP)
• Valid static IP address. The software will not function properly without a valid
static IP address. DO NOT use DHCP.

3BUR002374R1 Rev A 15
Licensing Section 1 Introduction

Licensing
Licensing MOD 300 Engineering Display software is enforced at the server (same
as AdvaBuild). The licenses are part of the AdvaBuild License Group The license
features available for MOD 300 Engineering Display software are:
• ABMEDU - CCF, Diagnostic, I/O, RDP (requires ABNTSU and ABNTSC)
• ABMEDT - TCL client option (requires the ABNTST - TCL client option)
• ABMEDL - TLL client option (requires the ABNTSL - TLL client option)
Client licenses are regulated by quantity based upon the number of MOD 300
Engineering Display users which can be connected to a server. The license is per
user per machine. If a user has multiple sessions open at once on one machine, only
one license is required.
TCL and TLL licenses are options to the ABMEDU license, not quantities. This
means that the quantity associated with ABMEDU is the implicit quantity for TCL
and for TLL. If you have four ABMEDU licenses and the TCL option, you can
connect four MOD 300 Engineering Display users with TCL options to the server.
Checking for client license is done at the time of server connection.

Security Settings
The AdvaBuild administrative user is added during the AdvaBuild installation and
is used to control allowed connections by the clients to the AdvaBuild server using
DCOM. A client user still needs to be listed on the server; however, the user can be
part of the Users Group.

AdvaBuild User
The AdvaBuild user account is added during installation of the Control Builder
client/server and assigned a password during the installation. This user is given
membership in the Administrators and ORA_DBA groups. The ability to “Log on
Locally” is granted in the security settings for “Local Security Policy” and should
be restricted to this user and specified administrative users (not client users) to
maintain the server security. The password can be changed by an administrative user
from the Users and Passwords window and by executing dcomsettings.exe in
AdvaBuild\Install\DCOM. If you fail to connect, you can check the Event Viewer

16 3BUR002374R1 Rev A
Section 1 Introduction Client User

(Start > Settings > Control Panel > Administrative Tools > Event Viewer) for a
“Logon failure: ...” message and see if it was password related.

Never create a user name that is the same as the host name of the machine (the
full computer name). This will cause a licensing error message when you try to
use the program.

Client User
Every client user needs to be added as a user on the server as a member of the User
group. Client users have their own access privileges and do not require the
administration rights of the AdvaBuild user account. The client user can be part of a
domain or workgroup. The domain user must be part of the domain and a member
of the Users group on the server.

DCOM Settings
Security settings are enforced independently and the AdvaBuild user becomes the
specified user account for process administration using DCOM on the server (see
Identity tab on DCOM application properties). In addition, custom access
permissions are enforced (see Security tab) and the following names are allowed
access: INTERACTIVE, NETWORK and SYSTEM. There is no need to change or
verify these settings.

3BUR002374R1 Rev A 17
DCOM Settings Section 1 Introduction

18 3BUR002374R1 Rev A
 Section 2 Installation

General Information
These instructions describe how to install the MOD 300 Engineering Displays
software on the Windows 2000 platform or Windows XP (client only). The software
is delivered on CD along with the applicable documentation.

Installation Procedure
The following installation procedure guides you through either a client/server
installation on an AdvaBuild server or a client only installation on a Windows 2000
or Windows XP workstation. Make sure your computer can support the applications
that you are installing. See Prerequisites and Requirements on page 14.
1. Start with the client server installation of the MOD 300 Engineering Display
software by inserting the installation CD on a completely installed AdvaBuild
client/server machine.

The logged on user must have Administration privileges to load software. The
user name must be defined local to the PC where you install the software. Do not
use a domain-defined user name.

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.

2. Load the MOD 300 Engineering Display software as described in Installing

Software on page 20.
3. Complete the license entry program, Appendix A, Software License Entry.
4. Set up users as described in Add Client Users to Server on page 21.

3BUR002374R1 Rev A 19
Installing Software Section 2 Installation

Installing Software
To install the MOD 300 Engineering Display software,
1. Use Windows Explorer and select the drive where the CD was inserted and run
the setup.exe. The installation prepares the install.
2. Welcome. Select Next > at the Welcome to the Installshield wizard for MOD
300 Engineering Displays Setup install screen.
3. 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 not allow you to continue the installation.
4. Destination Folder. Select Next > unless you wish to change the default
installation path. Select the Change... button to install to a different path.
5. Setup Type. Choose either a Client or a Client and Server setup and then
select Next > to continue. The Client and Server setup requires that an
AdvaBuild server with System Services be installed.
6. Installing MOD 300 Engineering Displays. Wait for the program to install.
7. Login ... (Server installs only). Enter the user name and password for the
AdvaBuild user. The password can be changed by an administrative user as
described in “Changing AdvaBuild User Security Settings” in the AdvaBuild
Administrator’s Guide.
8. InstallShield Wizard Complete. Select Finish.
9. Click on the Yes button to restart your PC if this is a server installation.
10. After the PC reboots, log back into the PC.

Completing License Entry

License software is already installed on the AdvaBuild client/server. To finish the
installation, obtain and enter the license strings as described in Appendix A,
Software License Entry.

20 3BUR002374R1 Rev A
Section 2 Installation Add Client Users to Server

Add Client Users to Server

Every client user needs to be added as a user on the server. Client users have their
own access privileges and do not require the administration rights of the AdvaBuild
user account. The client user can be part of a domain or workgroup. The domain
user must be part of the domain and a member of the Users group on the server.
Since the client user is also added to the server, do not allow the password to be
changed here.
1. Select Start > Settings > Control Panel > Administrative Tools > Computer
Management
2. From the Computer Management window expand System Tools > Local
Users and Groups.
3. Select Users and right click on New User... to open the New User window and
add additional users.
a. Enter User name: User1
A user name cannot be identical to any other user or group name of the
computer being administered. It can contain up to 20 uppercase or
lowercase characters (0-9, A-Z, a-z) The following are illegal:
# % & ‘ ( ) . { } " / \ [ ] : ; , * ? | = < >
A user name cannot start or end with: ! + - _ or space.
b. Enter Full name: User One
c. Enter Description: User Description
d. Enter case sensitive Password of up to 14 characters (for example): abb
e. Confirm Password (for example): abb
f. Click to select the check boxes for User Cannot Change Password and
Password Never Expires, and clear the boxes for User Must Change
Password at Next Logon, and Account Disabled.
g. Select Create to the New User menu.
4. This step is optional. Select Groups and right click on New Group... to open
the New Local Group window. If you are running this PC in a domain it should
be a user group in that domain; otherwise, you need to create the user group on
every PC.

3BUR002374R1 Rev A 21
Set DCOM Section 2 Installation

a. Enter Group Name: ClientGroup1

b. Enter Description: Client Group Description
c. Select Add... to add users to the group and then select OK
d. Select Create to create the New Local Group.

Set DCOM
All machines require that the DCOM security setting for Default Access
Permissions be set to Allow Access to EVERYONE and NETWORK. In addition,
the XP client needs the Default Authentication Level set to (None).

Windows 2000 Servers and Clients

1. Select Start > Run.
2. Enter dcomcnfg and select OK to open the Distributed COM Configuration
Properties window.
3. Select the Default Security tab and then the Edit Default button for the Default
Access Permissions.
4. If not already present, Add Allow Access to Everyone and NETWORK and
select OK.
5. On the Default Properties tab, set the Default Authentication Level to None.
6. Select OK to close the window.

Windows XP Clients
1. Select Start > Run.
2. Enter dcomcnfg and select OK to open the Component Services window.
3. Select Component Services > Computers > My Computer
4. Use the My Computer context menu to select Properties.
5. On the Default Communication Security tab select the Edit Default button for
the Default Access Permissions.

22 3BUR002374R1 Rev A
Section 2 Installation Set Permissions for Windows XP Client Users

6. If not already present, Add Allow Access to EVERYONE and NETWORK and
select OK.
7. On the Default Properties tab, set the Default Authentication Level to None.
8. Select OK to close the window.

Set Permissions for Windows XP Client Users

Client machines running on Windows XP require a permissions change to get
certain message boxes to work. These messages are DCOM calls from the server to
the client and by default, any DCOM requests coming into a Windows XP box will
be denied because Windows XP removed anonymous from the everyone group. To
fix this, make this change on Windows XP.
1. Select Start > Settings > Control Panel > Administrative Tools > Local
Security Policy.
2. Under Security Settings, open Local Policies > Security Options.
3. Change the policy “Network access: Let Everyone permissions apply to
anonymous users” from disabled to enable.
4. Reboot the computer. Windows XP will not work correctly if you change local
security settings, but do not reboot the computer.

Shut-down and Start-up Procedures

Follow the procedures provided in the AdvaBuild documentation to stop and start
System Services and an AdvaBuild server.

Product Verification
Refer to the PC manufacturer’s documentation to determine if your PC is working
properly when powered up.
To verify that the correct software is installed on your Windows-based Engineering
Station, choose Help > About from the menu bar of the application.

3BUR002374R1 Rev A 23
Product Verification Section 2 Installation

24 3BUR002374R1 Rev A
 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 1.

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 1. 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

3BUR002374R1 Rev A 25
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 27 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 27 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.

26 3BUR002374R1 Rev A
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, do the following 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 28 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 28 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 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 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:
…\SPRO\Win_NT\setupx86.exe

3BUR002374R1 Rev A 27
Requesting Software Keys Appendix A Software License Entry

Requesting Software Keys

The client and node licenses to run the MOD 300 Engineering Display software
with the TCL, and/or TLL options 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 33.
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 2.

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 2.
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

28 3BUR002374R1 Rev A
Appendix A Software License Entry Requesting Software Keys

Figure 2. 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 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 4.

Table 4. Device Settings for Dongle

Device Status Startup

Sentinel Started Automatic

3BUR002374R1 Rev A 29
Requesting Software Keys Appendix A Software License Entry

If an entry for the settings listed in Table 4 is not shown in the Devices
window, you must install the Sentinel driver as described in Installing
Sentinel Driver on page 27.
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 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.
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 27 or

30 3BUR002374R1 Rev A
Appendix A Software License Entry Requesting Software Keys

Obtaining and Installing the Dongle on page 27 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 3.

Figure 3. Licenses Tab of License Entry Program Window

b. Select one of the AdvaBuild license groups (ABMEDU, ABMEDT,

ABMEDL) as described in Licensing on page 16.

If the AdvaBuild license group does not exist, then add a new license group (File
> Add License Group) using a valid license name.

c. Click on the Request SWKey button.

3BUR002374R1 Rev A 31
Requesting Software Keys Appendix A Software License Entry

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.

32 3BUR002374R1 Rev A
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 3.
3. Select the AdvaBuild license group (ABMEDU, ABMEDT, ABMEDL) as
described in Licensing on page 16. If the group is not there, then use File >
Add License Group to specify a name.
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 33. If the software key is to be installed manually, follow
the instructions in Manual Installation on page 34.

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.

3BUR002374R1 Rev A 33
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 4. 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 strings for AdvaBuild are, described in Licensing on page 16. The
features are: ABMEDU (MOD 300 Engineering Displays), ABMEDT (TCL
option), and ABMEDL (TLL option).

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.

34 3BUR002374R1 Rev A
Appendix A Software License Entry Manual Installation

Figure 4. 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.

3BUR002374R1 Rev A 35
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 33 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 5 lists and describes the error codes and messages generated by the License
Entry Program.

Table 5. 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

36 3BUR002374R1 Rev A
Appendix A Software License Entry Licensing Troubleshooting

Table 5. Error Codes and Messages of License Entry Program

Code Message Description

-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 of
wrong version 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.

3BUR002374R1 Rev A 37
Licensing Troubleshooting Appendix A Software License Entry

Table 5. Error Codes and Messages of License Entry Program

Code Message Description

-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.

38 3BUR002374R1 Rev A
 INDEX

A I
ABMEDU, T ,L License Strings 16 IP Address 15, 19
About (Product Verification) 23
Administration Privileges 19 L
AdvaBuild Administration 13 License Strings 16
AdvaBuild Server 13
AdvaBuild User 16 M
Advant OCS Control Network 13 Machine ID 26
Machine Identifier 25
C MOD 300 DCN 13
CCF 13
Client User 17 N
Control Builder 13 New User 21

D O
DCOM Settings 17 On-Line Documentation 11
Documentation On-Line Help 11
On-Line 11 Oracle 13
Dongle 27
P
E Password 21
Ethernet Address 27 PCI RTAB 13

F R
FCM Templates 13 RDP 13
Requirements
G Hardware 14 to 15
Group Name 22 Software 15
RTAB 13
H
Hardware Requirements 14 to 15 S
Help 11 Security Settings 17

3BUR002374R1 Rev A 39
Index

Sentinel Driver 27
Software
Requirements 15
Software Key 25
Software Keys 28
Software License Administration 25
System Services 13

T
TCL 13
TCL Builder 13
TLL 13
TLL Builder 13

U
User, New 21
User, System
AdvaBuild 16
Client 17
Username 21
Users, Additional 21

40 3BUR002374R1 Rev A
3BUR002374R1 Rev A Litho in U.S.A. May 2003
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: [email protected] email: [email protected] email: [email protected]