Вы находитесь на странице: 1из 52

OperateIT

Process Portal A

Version 2.1/2

Release Notes
3BSE025721D212
NOTICE
The information in this document is subject to change without notice and should not be construed as a commitment by
ABB Automation Technology Products AB. ABB Automation Technology Products AB assumes no responsibility for any
errors that may appear in this document.
In no event shall ABB Automation Technology Products AB 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 Automation
Technology Products AB 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 ABB Automation Technology Products AB’s
written permission, and the contents thereof must not be imparted to a third party nor be used for any unauthorized
purpose.
The software 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.

TRADEMARKS
IndustrialIT and OperateIT are registered trademarks of ABB Ltd., Switzerland.
Process Portal A is a trademark of ABB Ltd., Switzerland.
Microsoft and Windows 2000 are registered trademarks of Microsoft Corporation.
Ghost is a registered trademark of Symantec Corporation.

Copyright © 2002 ABB Automation Technology Products AB.

3BSE025721D212
Process Portal A2.1/2, Release Notes
Table of Contents

TABLE OF CONTENTS
Chapter 1 - Introduction
1.1 Executive Summary ............................................................................................... 1
1.2 How to Use This Document................................................................................... 1
1.3 Version Designation ............................................................................................... 1
1.4 Revision Record..................................................................................................... 2
1.5 Restrictions ............................................................................................................ 2
1.5.1 Software Requirements for Windows 2000 .......................................... 2
1.6 Related Documentation.......................................................................................... 4
1.7 Possible Hazardous Situations .............................................................................. 5
1.7.1 Windows 2000 Domain time and Client time must be the same .......... 5
1.7.2 Do not use multiple processors in nodes .............................................. 5
1.7.3 High load on the server will prevent user from operation .................... 5
1.7.4 Full disk may crash the system ............................................................. 6

Chapter 2 - Functionality
2.1 Functions................................................................................................................ 7
2.2 New Functions in Process Portal A2.1/1 ............................................................... 8
2.2.1 New Category Handling for Alarm and Event ..................................... 8
2.2.2 New Columns in Alarm and Event Lists .............................................. 8
2.2.3 Redundant Network Routing Protocol (RNRP).................................... 8

Chapter 3 - Installation
3.1 Installation Preparations ........................................................................................ 9
3.2 Installation Procedures........................................................................................... 9
3.2.1 New installations................................................................................. 10
3.2.2 Upgrade of an Existing Installation Requiring a new
Create System ..................................................................................... 11
3.2.3 Security ............................................................................................... 13

Chapter 4 - Configuration
4.1 Alarm and Event changes in Process Portal A2.1/1 ............................................ 14

3BSE025721D212 i
Process Portal A2.1/2, Release Notes
Table of Contents

Chapter 5 - Remarks and Notes


5.1 Start-Up and Configuration.................................................................................. 15
5.1.1 Multiple Systems not supported ......................................................... 15
5.2 General................................................................................................................. 16
5.2.1 Large fonts on screens cause problems............................................... 16
5.2.2 Incorrect information in the ABB System Supervisor........................ 16
5.2.3 Restart a removed node before adding the node again ....................... 16
5.2.4 Export of objects placed in multiple structures .................................. 16
5.2.5 Wrong Message Boxes at Restore of
Redundant System ............................................................................. 16
5.2.6 Yellow Stop Light Appears When Creating System........................... 17
5.2.7 Permission to Remove Process Portal A Users ................................. 17
5.2.8 Translations Are Not Shown .............................................................. 17
5.2.9 Import/Export...................................................................................... 18
5.3 Alarm and Event .................................................................................................. 19
5.3.1 Alarm comment attached to wrong alarm........................................... 19
5.3.2 Using new created Alarm & Event List Configuration
template, may cause the Workplace to hang ....................................... 19
5.3.3 Alarm Logger Time ........................................................................... 19
5.4 Graphics ............................................................................................................... 20
5.4.1 Problem with Faceplate view-selector buttons ................................... 20
5.4.2 Graphic Display editor crashes when deselecting object.................... 20
5.4.3 Office installation starts when Graphics Builder is started................. 20
5.4.4 Unresolved Objects in Graphic Displays ........................................... 20
5.5 Historian & Trend ................................................................................................ 21
5.5.1 Limited object name syntax in Trend Table........................................ 21
5.5.2 Deleting Log Templates ...................................................................... 21
5.5.3 Secondary logs may not start in redundant connectivity server ......... 21
5.5.4 Drag and Drop Object to Trend Display ............................................ 21
5.5.5 No Update During Zoom or Move Scope .......................................... 21
5.5.6 Area Configuration in Trend Template may fail ................................ 22
5.5.7 Name changes of secondary logs ....................................................... 22
5.5.8 History OPC direct data logging......................................................... 22

ii 3BSE025721D212
Process Portal A2.1/2, Release Notes
Table of Contents

5.5.9 Trend Display on Composite Object ...................................................25


5.5.10 Inaccessible History Server Starts to Leak Memory ..........................25
5.5.11 Maxtime is needed in Log Configuration for a
Direct Log ..........................................................................................26
5.5.12 Do not change names on log templates after logs have
been created ........................................................................................27
5.5.13 Log Configuration doesn't work in Object Structure .........................27
5.6 System Status/System Supervision ......................................................................28
5.6.1 Delayed status update during large system changes ...........................28
5.7 Controller Integration via OPC ............................................................................29
5.7.1 Upload of large structures may fail .....................................................29
5.7.2 Upload is not working if Connectivity Server fails over ....................29
5.7.3 OPC Property Description not Displayed in Trend
Display Table ......................................................................................29
5.8 Redundancy..........................................................................................................30
5.8.1 Delete a redundant system via Configuration Wizard.........................30
5.8.2 Import large .afw-files in one Aspect Directory before adding
Redundant Aspect directories .............................................................30
5.8.3 Unnecessary Soft Alarm Service providers added..............................30
5.9 Dual Monitors ......................................................................................................31
5.9.1 Drop-down menus in Trend Table.......................................................31
5.9.2 Drop-down menus in Property Transfer Definition aspect .................31
5.9.3 Tool tips on windowless graphic elements are displayed
on primary screen when dual monitors are used. ................................31
5.10 Clock Synchronization .........................................................................................32
5.10.1 Check clock synchronization after a system restart ............................32
5.10.2 Deviation Limit must be greater than or equal to 1000 ms.................32
5.11 OLE DB Provider.................................................................................................33
5.11.1 Only one object per report in Crystal Reports ....................................33
5.12 File Viewer ...........................................................................................................34
5.12.1 File Viewer does not support redundancy ...........................................34
5.12.2 Check Out and Check in Can Be Made from Different Nodes ...........34
5.12.3 Preview Area May Fail to Redraw .....................................................34

3BSE025721D212 iii
Process Portal A2.1/2, Release Notes
Table of Contents

5.12.4 Agree to Acrobat Reader License Agreement Before Using


PDF Files ........................................................................................... 34
5.13 System Administration ........................................................................................ 35
5.13.1 Wrong TCP/IP number can cause server to fail restart ...................... 35
5.13.2 Backup the File SMData.dat .............................................................. 35
5.13.3 Configuration to See Nodes Going Up and Down ............................ 35
5.13.4 Domain server disconnect client when time
differs > 5minutes .............................................................................. 35
5.13.5 Corrupt Security Definition Aspect ................................................... 38
5.13.6 Stop Server before Removing It ........................................................ 38
5.14 Workplace ............................................................................................................ 39
5.14.1 Unconfigured Workplace Cannot be Opened .................................... 39
5.15 Maintenance......................................................................................................... 40
5.15.1 Some advice for a Maintenance Engineer .......................................... 40
5.16 User documentation ............................................................................................. 42
5.16.1 Where to find the User Documentation .............................................. 42
5.16.2 Alarm and Event ................................................................................ 42

Chapter 6 - How to Report Errors

iv 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 1.1 Executive Summary

Chapter 1 Introduction

1.1 Executive Summary


The Process Portal A2.1/2 contains the functionality that operators need for efficient
control and supervision of their process. Key functionality is the presentation of
process graphics, execution of process dialogs, presentation of trends and alarms. It
also contains the functionality engineers need for efficient and cost effective
engineering of the process graphics.

1.2 How to Use This Document


This document is intended for information that is not described in the ordinary
manuals, sales information, or in any other kind of product information.
It describes:
• Problems and errors in software or documentation that were found too late to
be included in the applicable user’s guide

1.3 Version Designation


The software for the Process Portal A2.1/2 has the following description and
designation:
Process Portal A
Version: 2.1/2
Art. No: 3BSE025721R212

3BSE025721D212 1
Process Portal A2.1/2, Release Notes
Chapter 1Introduction

1.4 Revision Record

Table 1-1. Revisions


Revision Release date Remarks
Process Portal A2.1/0 May 2002 Release
Process Portal A2.1/1 November 2002 Revision
Process Portal A2.1/2 April 2003 Revision

1.5 Restrictions

1.5.1 Software Requirements for Windows 2000


Mandatory:
• Windows 2000 Professional or Server. U.S. English version
• Windows 2000 Service Pack 3
• If you have a domain controller we recommend that you use Windows 2000
Server with Service Pack 3. If you have additional requirements on the Domain
Server, Windows 2000 Advanced Server with Service Pack 3 can also be used
for the Domain server.

If you have installed additional Windows 2000 components since you last installed
the revision Process Portal A 2.1/2, you have to reinstall Process Portal A 2.1/2

• Windows Installer 2.0


• DirectX 8.1

You can use the DirectX Diagnostic Tool to determine the version of DirectX
installed on your computer. Perform the following: Select the Start menu and
choose Run. Type dxdiag and click OK. Check the version of DirectX under the
System tab. Under the DirectX Files tab you can check the version for each DirectX
file. When finished checking version click Exit. If Windows can not find the dxdiag
program, DirectX version 5.0 or earlier is installed on your computer. If this is the
case, download and install DirectX 8.1

2 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 1.5.1 Software Requirements for Windows 2000

• Microsoft Internet Explorer 6.0 with Service Pack 1


• TCP/IP

3BSE025721D212 3
Process Portal A2.1/2, Release Notes
Chapter 1Introduction

1.6 Related Documentation


Table 1-2. Valid manuals

Document Ordering no.


IntegrateIT Aspect Integrator Platform Version 2.1 3BSE 025 993R401
Administrator’s Guide
OperateIT Process Portal A Version 2.1 Operator’s Guide 3BSE 025 996R201
OperateIT Process Portal A Version 2.1 Workplace and 3BSE 025 994R301
Plant Explorer User’s Guide
OperateIT Process Portal A Version 2.1 Graphics User’s 3BSE 025 997R201
Guide
OperateIT Process Portal A Version 2.1 Graphics Builder 3BSE 027 915R201
User’s Guide
OperateIT Process Portal A Version 2.1 Process Graphics 3BSE 027 916R101
Standard Building Blocks User’s Guide
OperateIT Process Portal A Version 2.1 Alarm and Event 3BSE 025 998R301
User’s Guide
OperateIT Process Portal A Version 2.1 Trends and Histo- 3BSE 025 999R301
rian User’s Guide
OperateIT Process Portal A Version 2.1Plant Engineering 3BSE 025 995R201
Methods Reference Manual
OperateIT Process Portal A Version 2.1 Installation Guide 3BSE 026 000R301
IntegrateIT Aspect Integrator Platform Version 2.0 Secu- 3BSE 024 545R101
rity User’s Guide
IntegrateIT Aspect Integrator Platform Version 2.0 Trans- 3BSE 025 113R201
lator’s Guide
System Release Notes 3BSE033034

The manuals are available in .pdf format before installation, when browsing in the
Document directory.
The manuals are also available in .pdf format after the installation, in the directory
<install path> “ABB Industrial IT\Operate IT\Process Portal A\doc\” where <install
path> is the path you specified when you installed the Process Portal A product.

4 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 1.7 Possible Hazardous Situations

1.7 Possible Hazardous Situations


This chapter contains important information and descriptions of known problems
and workarounds. These problems can cause an hazardous situation and must be
extra considered.

1.7.1 Windows 2000 Domain time and Client time must be the
same

The Windows 2000 Domain controller time and the Windows 2000 Client time
must be the same. Otherwise a Process Portal A client, that at the same time is a
Windows 2000 client, will be disconnected from the network.

1.7.2 Do not use multiple processors in nodes

Do not use multiple processors in nodes with Process Portal A because timing
problems may occur. Use only single processor nodes where Process Portal A is
loaded.

1.7.3 High load on the server will prevent user from operation

When you are on the server performing the following operations the load of the
CPU can increase to 99% load:
• upload from OPC Server
• creating of hierarchical logs
• deleting many aspect objects (4000 objects ca. 2 min.) at the same time
• importing and exporting
• deploying of a new or modified display element for an object, with several
instances of that object
• deploying several displays with the Display Tool
• mirroring of controller object structures (by the AC 800 M/C Control Builder)

3BSE025721D212 5
Process Portal A2.1/2, Release Notes
Chapter 1Introduction

1.7.4 Full disk may crash the system

Since there is no warning given before the hard disk becomes full, you have to
monitor hard disk usage. A full disk may crash the system.

6 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 2.1 Functions

Chapter 2 Functionality

2.1 Functions
Process Portal A2.1/2 has the following main functions:
• Plant Explorer/Operator Workplace
• Graphics
• Historian
• Trends
• OPC (OLE for Process Control)
• Αlarm & Event
• Security
• Redundant Aspect Directory
• Parallel Connectivity Servers
• NLS (National Language Support)
• Dual screens
• Backup/Restore of configuration data (aspect directory)
• External Alarm
• Soft Alarm
• History and Trend Collector Link
• Improved 3rd party OPC - DCOM connection
• File Viewer

3BSE025721D212 7
Process Portal A2.1/2, Release Notes
Chapter 2 Functionality

2.2 New Functions in Process Portal A2.1/1

2.2.1 New Category Handling for Alarm and Event


System message categories (classes) have changed. All alarm categories exist in the
system message server as categories. This enables filtering of an event list with the
same categories as an alarm list. Prior to this revision, events from AE server
belonged to one of the three AE categories in system message (AE Condition Event,
AE Simple Event and AE Tracking Event) depending on its event type in the OPC
AE server. All events in the AE server belong to an alarm category, but when the
event was stored in the system message server, this category was not stored. See
Chapter 4.1

2.2.2 New Columns in Alarm and Event Lists


The standard Process Portal A2.1/2 alarm and event lists include the following new
viewable and sortable columns:
• Campaign ID
• Batch ID
• Unit ID
• Recipe Procedure Path

2.2.3 Redundant Network Routing Protocol (RNRP)


RNRP is the basic redundant protocol, and should be used in a redundant network
configuration. It can detect if a network/server goes down and perform a switch-
over to another redundant/parallel network/server. If RNRP is not used, it will take
up to 2 minutes for the system to notice the loss of the network/server and switch-
over to another network/server. This will affect clients that are communicating with
the lost server. RNRP is an option to the Process Portal A and must be installed on
all nodes in a configuration with redundant Aspect server or Connectivity server.
RNRP handles redundancy transparently by switching the IP addresses of the
primary and secondary nodes.
RNRP is also relevant for non redundant network.

8 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 3.1 Installation Preparations

Chapter 3 Installation

3.1 Installation Preparations


See the Installation Guide, 3BSE 026 000R301, for information about Installation.
Installation covering other IndustrialIT products will be available in System Release
Notes 3BSE033034.

You must have Process Portal A 2.1/1 installed before you can install
Process Portal A 2.1/2.

You must have Windows 2000 administrator privileges to install Process Portal A.
You do not get these privileges automatically as a Process Portal A administrator, it
has to be defined in Windows 2000.
Check for Status Reports of Process Portal A in the ABB library for information
about patches. If any patches exists, continue with installation of the patches. This
should be done before any configuration starts.
On the Process Portal A2.1/1 CD, you will find the file “RNRP_remove.bat” in the
“Uninstall of old RNRP” folder. Run this file (double click it) to remove RNRP
from the Windows registry. Then find the folder to which you have installed the
files for RNRP and manually remove them.
Check that RNRP is removed by looking in the Windows Services, Start -->
Settings --> Control Panel --> Administratives Tools --> Services. You should not
see the “ABB RNRP” service.

3.2 Installation Procedures

General
There are two different alternatives to install the revision of
Process Portal A 2.1/2:

3BSE025721D212 9
Process Portal A2.1/2, Release Notes
Chapter 3 Installation

• Chapter 3.2.1 New installations


• Chapter 3.2.2 Upgrade of an Existing Installation Requiring a new Create
System

3.2.1 New installations

General
There are some major error corrections in the Process Portal A. Some changes have
also been done in the Process Graphic function to reduce memory consumption and
to speed up the display exchange times substantially.
If any customer specific graphic elements, faceplates or displays from
Process Portal A2.1/1 are imported to the product, these have to be deployed again.
Follow the installation procedure described below.

Install Visual Basic Runtime on clients not including Visual Basic 6


The correct version of Visual Basic Runtime library is needed on all clients which
do not include a Visual Basic 6 installation. Otherwise, displays may flicker on
these clients.
Install this library by browsing to the folder VB RunTime Update on the Process
Portal A CD and launching the file VBRun60sp5.exe.

Remove RNRP if installed from PPA 2.1/0 CD before installing PPA 2.1/1
If you have installed RNRP from Process Portal A2.1/0, you shall remove this older
RNRP version before installing RNRP available in the option menu in the Process
Portal A2.1/1.

Installation Procedure
1. Use the same installation procedure as described in the OperateIT Process
Portal A 2.1/1 Installation Guide. When the CD is inserted you will get two
check boxes (Process Portal A and Process Portal A 2.1/2) in the Installation
Display. you must mark both boxes to install Process Portal A 2.1/2.
2. Install Process Portal A 2.1/2 on all nodes.

10 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 3.2.2 Upgrade of an Existing Installation Requiring a new Create System

3. Run the script: CopyAfwFiles_PPA212.bat on all nodes. This script can be


found in the folder Install Scripts on the CD.
4. Proceed according to the Installation Guide.
5. Install the Add-on Products according to their installation instructions (e.g. AC
800 M/C Connect).
6. Proceed with create system etc. according to IntegrateIT Administrator’s
Guide.

3.2.2 Upgrade of an Existing Installation Requiring a new


Create System

General
This procedure is used to upgrade an existing installation. To use this procedure it is
an advantage if there exist a Ghost dump with the Process Portal A2.1/1 and
eventually connect product(s).
There have been some major error corrections made in the Process Portal A. Some
changes have also been done in the Process Graphic function to reduce memory
consumption and, not at least to speed up the display exchange times substantially.
Unfortunately the changes had to be done so radically that all graphic elements,
faceplates, and displays in an existing system, has to be redeployed to make use of
the changes.
All additions, in previous Process Portal A:s, related to graphic aspects, done by
ABB BU or by Customer, have to be redeployed. To do this you have to use the
respective corrected products.
Before starting the upgrade, it is recommended that you test your export-files in
another PC to verify that your application was exported and imported successfully.

Installation Procedure
1. Use the Backup function to backup your system. If any error(s) at backup
occur, correct the error and repeat until there are no errors remaining. For
further instructions and details see the Backup function in the IntegrateIT
Administrator’s Guide.

3BSE025721D212 11
Process Portal A2.1/2, Release Notes
Chapter 3 Installation

2. Save existing application data by using the Import/Export tool.


For further instructions and details see The Import/Export Function in the
IntegrateIT Administrator’s Guide.
3. The affinity configuration can not be exported. Please note down your affinity
definitions in any Affinity Definition aspects created and in the Service
Definition aspects concerned (Configuration tab) and recreate after upgrade.
4. Export any security definition aspects that you have modified in admin
structure or aspect system structure. The same Windows domain is required to
be able to import and use this backup. Also generate and save a Security Report
which lists all security definitions made in the system (See IntegrateIT Security
Reference Manual for instructions).
5. For all Servers and Clients, do the following:
a. If no Ghost dump Exist, start with a new installation, see Chapter 3.2.1
New installations, and then continue with Step 6, else go to Step b

Note! The Ghost dump must include Windows 2000, required third party
software and Process Portal A2.1/1 without a system created (See
OperateIT Process portal A Installation Guide).
b. Insert the CD, and you will get two check boxes (Process Portal A and
Process Portal A 2.1/2) in the Installation Display, where you have to
mark Process Portal A 2.1/2 to install Process Portal A 2.1/2.
c. On all the PC’s, run the script: CopyAfwFiles_PPA212.bat. This script can
be found in the folder Install Scripts on the CD.
d. Upgrade, if needed, any Add-on Product (e.g. AC 400 Connect) according
to its own installation procedure.
6. Create a new system. See IntegrateIT Administrator’s Guide for more
information.
7. Restore application data from Process Portal A2.1/1, see
IntegrateIT Administrator’s Guide for more information. Only import your own
application data, i.e. non standard Process Portal A aspect objects.

12 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 3.2.3 Security

8. If any additions are made in the Graphical Structure, use the Display Tool and
deploy the graphic aspects that you have added. Select Radio Button All, mark
Auto Resolve, select the aspect to deploy and press Deploy Selected.
9. Use the Display Tool to deploy the structures defined below. Select Radio
Button All, mark Auto Resolve and press Deploy All In List for each structure
stated below.
- Object Type Structure
- Functional Structure
10. Deploy additions in any other structure where you have added user defined
graphic aspects.
Select Radio Button All, mark Auto Resolve, select the aspect to deploy and
press Deploy Selected.
11. Make another full backup (if possible) of your computer(s) according to
Backup and Restore Function in the IntegrateIT Administrator’s Guide.

3.2.3 Security
After the installation of Process Portal A, the system is open regarding access rights.
Therefore, it is recommended that the Security configuration is made. This is
described in the Security User’s Guide, 3BSE 024 545R101.

3BSE025721D212 13
Process Portal A2.1/2, Release Notes
Chapter 4 Configuration

Chapter 4 Configuration

See the Administrator’s Guide, 3BSE 025 993R401, for information about
Configuration.

4.1 Alarm and Event changes in Process Portal A2.1/1


System message categories (classes) have changed as described in New Functions
in Chapter 2.2.1 . The Default Event List configuration will not show any new
events, because it has a filter that only shows messages belonging to one of the three
old Alarm and Event categories in system message. Update the Default Event List
configuration so it shows the dynamically added categories in the filter, see
Integrate IT Alarm and Event Reference Manual, 3BSE 028 306R201.

Which alarm categories that exist, depends on which OPC AE server


(connectivity) that is connected to the system. Therefore alarm categories are
added (as system message categories) when an OPC AE server is connected to
the system for the first time.

14 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.1 Start-Up and Configuration

Chapter 5 Remarks and Notes

The remarks and notes below describe the main problems or hints that are known in
the system. If further issues exist, please contact ABB as described in Chapter 6
below for more information.

5.1 Start-Up and Configuration

5.1.1 Multiple Systems not supported


Do not create multiple systems in the Configuration Wizard as it is not tested.

3BSE025721D212 15
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5.2 General

5.2.1 Large fonts on screens cause problems


If you use Windows Large Fonts to make displays more readable, some dialog and
menus in PPA will be truncated.

5.2.2 Incorrect information in the ABB System Supervisor


The ABB System Supervisor window can sometimes show incorrect information.

5.2.3 Restart a removed node before adding the node again


If you remove a server or client node from your system (with the Configuration
Wizard) and you intend to add it again, restart that node before adding the node
again.

5.2.4 Export of objects placed in multiple structures


If an object is a member of more than one structure, you must do an export of that
object for each structure.

5.2.5 Wrong Message Boxes at Restore of


Redundant System
The message boxes below pop up when choosing Connect Node after a successful
restore. They can be ignored. Just press the OK buttons.

16 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.2.6 Yellow Stop Light Appears When Creating System

5.2.6 Yellow Stop Light Appears When Creating System


During the creation of a system, a yellow traffic light will be shown for a minute or
so. This is normal and there is no need to abort the creation.

5.2.7 Permission to Remove Process Portal A Users


Removing Process Portal A users can only be done by a user who has both System
Engineer and Application Engineer roles.

5.2.8 Translations Are Not Shown


If translations of application data have been made but cannot be seen, the problem
can be that there is a language defined as Neutral that causes problem. For a self-
created .afw file this can be solved by removing Neutral as follows:
1. Open the Import/Export application by selecting Start > Programs >
ABB Industrial IT > Process Portal A > Import Export.
2. Open the .afw file with File > Open.
3. Select Translations > Reduce Translations.
4. Move Neutral to the Exclude column and click OK.

3BSE025721D212 17
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5. Import the .afw file with Action > Import.-

Note: Your local (location) must always be set to English (United States) in
Regional Options if you make application development (e.g. Graphic elements) and
generate your own .afw-files.

5.2.9 Import/Export
In some cases the .afw-files in Process Portal A may contain errors regarding
linking between parent and child objects (only seen when composite object types
are used). These errors do not affect the operation of the Process Portal but might
cause problems during engineering changes.
In order ensure that users are aware of possible errors in the .afw-files, we have
introduced strict control when importing aspect objects.
If any errors are detected they will be shown as warnings in the message area of the
import/export tool when importing the files into a new system. The two messages
relevant in this case are:
• Structure Key between instance and formal instance does not match.
• Can not move an instance of a formal instance from its defined location.
You can increase the Import/Export message area in the import/export tool in order
to see more messages simultaneously.

18 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.3 Alarm and Event

5.3 Alarm and Event

5.3.1 Alarm comment attached to wrong alarm


When you write a comment and new alarms appear before you close the comment
window, the comment is connected to the latest alarm.

5.3.2 Using new created Alarm & Event List Configuration


template, may cause the Workplace to hang
When you create a new Alarm & Event List Configuration template in the Library
Structure you must change at least one parameter, e.g. choose one of the Categories
in the Filter tab. Otherwise the Workplace will hang when you present an alarm or
event list, configured with this new created Alarm & Event List Configuration
template.

5.3.3 Alarm Logger Time


When an alarm comes on it gets a certain time in the alarm log. When the alarm
later goes off, it gets the same time as when it came on. This can be very confusing
in the alarm log. To avoid this it is better to set up the logger as an Event Logger,
then you will get the right time on coming and going alarms.

3BSE025721D212 19
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5.4 Graphics

5.4.1 Problem with Faceplate view-selector buttons


Enable/disable of faceplate view button selectors in the configuration view require
restart of the Plant Explorer.

5.4.2 Graphic Display editor crashes when deselecting object


If you have selected a number of graphical objects in the graphic display editor and
then deselect one of the objects, the graphic display editor may crash. To avoid a
crash, open the Property window before you deselect an object.

5.4.3 Office installation starts when Graphics Builder is started


If you have Microsoft Office 2000 installed and start the Graphics Builder, the
Windows Installer sometimes starts. To avoid this, browse to the file Data1.msi on
the MS Office Installation disk and install the file to avoid this problem.

5.4.4 Unresolved Objects in Graphic Displays


Check that you do not have references to unresolved objects in graphic displays. To
do this, go to the Element Browser, Expression Builder and open the tab Object
property. Check that there are no objects in the Resolved column.

20 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.5 Historian & Trend

5.5 Historian & Trend

5.5.1 Limited object name syntax in Trend Table


The object name syntax “<Object Name>[:<Aspect>]:<property>[,<Log Name>]”
for the Trend Table object name can not be used. This syntax is intended to be used
if the Property column is not part of the Trend Table, as described in the Trends and
Historian User’s Guide.

5.5.2 Deleting Log Templates


Do not delete Log Templates actually being used by active Log Configuration
aspects. This is not protected today.

5.5.3 Secondary logs may not start in redundant connectivity


server
When adding a redundant connectivity server, the secondary logs in that server may
not start automatically. If that is the case, disable and enable the Basic History
Service Provider server and the logs will start.

5.5.4 Drag and Drop Object to Trend Display


When seamless is selected in the trend display and an object is dragged and dropped
to the trend display, nothing is shown. Select something else, such as the Trim
Curve, and then select seamless again to get the trend display.

5.5.5 No Update During Zoom or Move Scope


When zooming or moving the scope of the trend display, update of the trend curve is
stopped. To resume the update, go back to the present scope without zoom by
clicking on the Block/Unblock button.

3BSE025721D212 21
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5.5.6 Area Configuration in Trend Template may fail


If a trend template is configured to have two areas with a few trends in each area,
the configuration may fail and all trends end up in the first area. The work around is
to configure the trend display instead of the trend template.

5.5.7 Name changes of secondary logs


Do not change names for logs in templates after logs has been created.

5.5.8 History OPC direct data logging


History OPC direct data logging has a parameter for wait-time with a default value
of 5 minutes to compensate for time synchronization differences. This wait-time is
used when the data value has not changed before data is stored or drawn on the
screen. As an effect, the requested cyclic data update is stored and drawn 5 minutes
after the current time. Each received data change will directly trigger data storage
and presentation on the screen, i.e. no data is lost in either case.
The wait-time can be changed in the Windows registry where the Connectivity
Server is installed as follows:
• Run regedit.
• Go to HKEY_LOCAL_MACHINE\SOFTWARE\ABB\Sigma\
System Modules\History Server\1.0-0\private.

22 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.5.8 History OPC direct data logging

• Double click on the key TimeSkewExtrapolate. Change it to a suitable value.


Preferably 15 seconds. This parameter is measured in milliseconds, which
means decimal value = 15000 gives 15 seconds wait-time.
• Close the registry editor.
To make this parameter change accessible for the History Server you have to restart
this service. Follow the steps below:
• Close all trend displays in all clients in the system. Important!
• Go to the Basic History Service provider in the Service Structure.

3BSE025721D212 23
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

• Open the Service Provider Definition aspect and select the configuration tab.

• Disable Basic History Service provider, press Apply and wait for
approximately 2 minutes (or until the Task Manager shows low CPU activity
again).
Enable Basic History Service and press Apply.

24 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.5.9 Trend Display on Composite Object

5.5.9 Trend Display on Composite Object


Trends on composite objects (or any object type) will not work, unless a relative
name is typed in the object name column (for example “./MMT”). The object
browser can not be used in this case.
If a trend is configured in a “wrong way” on an object type and a number of
instances have been created, it is not enough to correct the trend on the object type,
but all instances has to be recreated as well.

5.5.10 Inaccessible History Server Starts to Leak Memory


If a Connectivity Server becomes inaccessible to History, the History Server
(AfwHistory Service) starts to leak memory. The memory leakage is due to
AddItems failure, i.e. when data subscription requests can not be successfully set up
(via AddItems), memory leaks.
To correct this problem:
Increase the value of the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\ABB\Sigma\SystemModules\HistorySe
rver\1.0-0\private\CollectorStartPeriod
from the default value 60000 (ms) to 600000.
This key controls the poll cyclicity on collectors i.e. the time it may take to adopt a
Controller that has been lost.
Perform the following:
• Run regedit
• Go to HKEY_LOCAL_MACHINE\SOFTWARE\ABB\Sigma\
System Modules\History Server\1.0-0\private.

3BSE025721D212 25
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

CollectorStartPeriod

60000

• Double click on the key CollectorStartPeriod. Change the default value 60000
to a suitable value. Preferably 600000 ms.
Close the registry editor.

5.5.11 Maxtime is needed in Log Configuration for a


Direct Log
If the direct log only have one data point and no maxtime is set, the Hierarchical log
will remain empty. The maxtime in the Log Configuration must be defined.

26 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.5.12 Do not change names on log templates after logs have been created

5.5.12 Do not change names on log templates after logs have


been created
After creation of logs referring to a log template, do not change the log template
name. Changes will result in nonworking logs.

5.5.13 Log Configuration doesn't work in Object Structure


Do not add an aspect of the type Log Configuration on a Control Module Type in
the Object Type Structure. Even if you make the necessary settings, and then add the
logged variable in a TrendDisplay, and open it in an instance in the Control
Structure, the logging will not work.
This behavior is configurable. Go to the service structure, select Basic History
aspect “Service Definition”. Choose the Special Configuration tab. There decide
which structures you want supported.
Another way is to create the Log Configuration in the Control Structure and then it
will work.

3BSE025721D212 27
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5.6 System Status/System Supervision

5.6.1 Delayed status update during large system changes


If the System Status Viewer is open during large system changes (e.g. start/stop of
servers), a delay of status updating may occur. To be sure about the current status,
change to another aspect and open the System Status Viewer aspect again.

28 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.7 Controller Integration via OPC

5.7 Controller Integration via OPC

5.7.1 Upload of large structures may fail


When uploading a large amount of objects (i.e., approximately > 50000), the
Uploader may fail. If the Workplace application hangs, restart it and do the Upload
again. If the retrieve of objects was successful before the failure, you can run
“Append Objects” in the Advanced tab in the Uploader aspect.

5.7.2 Upload is not working if Connectivity Server fails over


An Upload that is active during a Connectivity Server fail-over will stop with
failure, because there is no data access redundancy during an Upload.

5.7.3 OPC Property Description not Displayed in Trend


Display Table
At upload from the OPC server, only one object is created in the PPA, which
contains references to all alien variables. The process operators do not know which
objects they see in the trend display since there is no OPC property description
presented.
A new column, property description have been added. By default, the new column
is not displayed. You have to enable it in the trend template.

3BSE025721D212 29
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5.8 Redundancy

5.8.1 Delete a redundant system via Configuration Wizard


If redundant aspect directories are used, do not use delete system. If you want to
remove a node containing a redundant aspect directory, use the Configuration
Wizard’s remove node. After this, when you have a single aspect directory system,
delete the system in that node and then delete the OperateITData-directory.

5.8.2 Import large .afw-files in one Aspect Directory before adding


Redundant Aspect directories
When a new system is created, and large import-files will be loaded, it is
recommended to import before redundant aspect directories are created.

5.8.3 Unnecessary Soft Alarm Service providers added


On creation of redundant Aspect Servers, one extra Soft Alarm Service provider is
added in the Alarm & Event Service for each aspect server. You have to remove
them manually.

30 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.9 Dual Monitors

5.9 Dual Monitors

5.9.1 Drop-down menus in Trend Table


Drop-down menus for columns “Log Name”, “Style”, etc., do not work in the Trend
Table for a Trend Display, if opened on the second monitor.

5.9.2 Drop-down menus in Property Transfer Definition aspect


Drop-down menus for columns “Aspect” and “Property” do not work in the
Property Transfer Definition aspect, if opened on the second monitor.

5.9.3 Tool tips on windowless graphic elements are displayed


on primary screen when dual monitors are used.
The tool tip showing the object name in graphic displays is always shown in the
rightmost position on the primary monitor in a dual monitor solution. The
windowless function on graphic elements can be disabled by changing the property
WindowLess to false and BackStyle to opaque which also disables the background
transparency of the element.

3BSE025721D212 31
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5.10 Clock Synchronization

5.10.1 Check clock synchronization after a system restart


If you have a node (i.e., an AC 400 controller) in the control network as time source
for the clock synchronization and have restarted the system, clock synchronization
may not work. The work around is to restart the Time Server running in the
corresponding connectivity server node (i.e., Disable and then Enable of the Time
Server service provider).
If the time settings from the Process Portal A fails, restart the Time Server in the
same way as described above.

5.10.2 Deviation Limit must be greater than or equal to 1000 ms


The “Deviation Limit” in the TimeServerHandler configuration for a Time Client
must be set to a value of 1000 msec or greater.

32 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.11 OLE DB Provider

5.11 OLE DB Provider

5.11.1 Only one object per report in Crystal Reports


If you are using Crystal Reports as a report generating tool, it is possible to include
only data from one object (i.e., one log or one object for data access) in the same
report. Crystal Reports crashes (or shows data for only one object) if you try to
include more than one object in the report.

3BSE025721D212 33
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5.12 File Viewer

5.12.1 File Viewer does not support redundancy


The File Viewer uses functions that do not support redundancy. This means that the
files may not be available if an Aspect Directory Server stops.

5.12.2 Check Out and Check in Can Be Made from Different Nodes
If a document is checked out on one computer, the same user can bring the
document to another computer and check it in there. This requires that the user
tracks document versions if he works on several nodes.

5.12.3 Preview Area May Fail to Redraw


For document types other than .pdf, the preview area in File Viewer sometimes fails
to redraw the document and looks all grey.
Right click on an object and select the document, it will still appear correctly.

5.12.4 Agree to Acrobat Reader License Agreement Before Using


PDF Files
If Acrobat Reader is installed without agreeing to the license agreement, pdf files
can not be used in File Viewer.
To ensure that pdf files will work in File Viewer, open a pdf file in Windows. If that
works, then it will work in File Viewer.

34 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.13 System Administration

5.13 System Administration

5.13.1 Wrong TCP/IP number can cause server to fail restart


If you enter the wrong TCP/IP number in the Node Administration structure the
server will not restart when you try to restart that node.

5.13.2 Backup the File SMData.dat


As a security measure, it is recommended to backup the file:
<Installation disk>:\OperateITData\ServiceManager\SMData.dat,
since this is an important file for the configuration of the system.
If the system cannot be restarted due to a corrupt SMData.dat file, restore the file to
the folder:
<Installation disk>:\OperateITData\ServiceManager\SMData.dat,
and restart the system.

5.13.3 Configuration to See Nodes Going Up and Down


To be able to see messages about nodes going up and nodes going down in a
configuration that has installed the RNRP option, you must add the category System
Condition Event to the System Event List. Without RNRP no messages are
generated.

5.13.4 Domain server disconnect client when time


differs > 5minutes
By default the Window Time Service on the first Domain Controller promoted is
appointed to be the primary time server. The Window operating system implements
Kerberos V5 as the primary protocol for network authentication. One requirement
of the protocol is that system clocks must be synchronized. The Window Time
Service is used to achieve the degree of clock synchronization that Kerberos
requires.
When a Domain Controller is placed outside a PPA system the Domain Controller
still needs to be synchronized with the PPA. If this is not the case the Domain

3BSE025721D212 35
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

Controller will, when the time differs more then 5 minutes, throw out the clients
(PPA system) of the domain, which will stop the PPA.
Solution
There exist at least two different solutions using the existing Window Time Service
(Win32Time). Both solutions use the PPA time synchronization, and on all nodes
not involved in the description below, the Win32Time has to be disabled.
Alternative 1:
Change the Win32Time on the Domain Controller so it acts as client, and activate
the Win32Time on the servers appointed as possible PPA Time Servers, and set the
Win32Time to act as server. For more description on this subject, see Window
documentation.
Alternative 2:
Leave the Domain Controller as Win 32 time server, and set the possible PPA Time
Servers as time source for it. On the appointed PPA Time Servers the Win32Time
has to be activated and set as server.
The recommendation is not to use a connectivity server, and to disable the
possibility for setting time on that node. This is described below:
• On the PPA Time Server nodes appointed as time source for the Domain
Controller, Enable the Win32Time and set it as server:
– Create a new DWORD value or modify the existing value, called
LocalNTP and set the value to 1 in the Window registry.
Registry settings
System Key:
• [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\P
arameters]
• Value Name: LocalNTP
• Data Type: REG_DWORD
• Value Data: 0 = disabled, 1 = enabled
Run the following command in the command prompt to start the Win32Time:

36 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.13.4 Domain server disconnect client when time differs > 5minutes

• Net start w32time


Or use Computer Management to restart the Win32Time.
To prevent the node from setting time:
1. Start the Plant Explorer Workplace.
2. Select Plant Explorer.
3. Go to the Node Administrators Structure and select the appointed time source
node.
4. Select the TimeServerHandler aspect.
5. Uncheck the “Allowed To Set Time” check box.
6. Press Apply.
On the Domain Controller set the time source to the appointed PPA Time Servers.
For Win 2000:
Run the following commands in the command prompt:
• Net stop w32time
• Net time /setsntp:AIPserver_list
• Net start w32time
For Win XP:
Run the following command in the command prompt:
• w32tm /config /syncfromflags:manual /manualpeerlist:AIPserver_list
Followed by the command:
• w32tm /config /update
You may need to restart or logout of the computer for the changes to take effect.

3BSE025721D212 37
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5.13.5 Corrupt Security Definition Aspect


Security Definition aspects containing security configuration for a specific client
node may become corrupt if the client nodes are removed and then added using the
Configuration Wizard. The Security Definition aspects containing a security
configuration for a client that no longer exists will be shown empty.
The security system treats a client node as a new node, if it is removed and added
again, even if it has the same name. The security system uses a unique identifier for
the client node, not its name.
To avoid the problem remove all node specific security configuration, before the
client node is removed. However, if some node specific security configuration, for a
removed client node, still exists after the node is removed it can be corrected as
follows:
To fix the problem, delete the Security Definition aspects containing client specific
configuration and add a new one with the added client node.
After all Security Definition aspects are corrected, the complete system should be
restarted to ensure the security system to work correctly.

5.13.6 Stop Server before Removing It


When using the Configuration Wizard for removing a server, you have to stop the
server. Otherwise you will get some objects left in the control structure on the root
level.

38 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.14 Workplace

5.14 Workplace

5.14.1 Unconfigured Workplace Cannot be Opened


When a workplace is created, it cannot be opened until it has been configured. If just
any thing in the workplace is configured, the workplace can be opened.

3BSE025721D212 39
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5.15 Maintenance

5.15.1 Some advice for a Maintenance Engineer


In order to get full effect of the system especially regarding the redundancy it is
recommended that you on a regular basis inspect the system. Below you find some
useful hints on what you can do to get a feeling on how the system is performing.
On a PPA Workplace:
• glance at the system event list(s) for information from the PPA system
• open the System Status Viewer for the "service structure" or the "Node
Administration Structure" to see if any PPA service are not in service or
standby state
On all nodes:
• open the RNRP Network Event Monitor (R symbol) in the Task Bar and check
that all nodes and communication paths are up
• open the Task Manager and add following processes columns to the default
(Peak Memory Usage, USER Objects, Virtual Memory Size, Handle Count,
Thread Count and GDI Objects). Take a dump of the Task Manager Processes
when the system is started and use this dump as reference to compare with,
later on to see if there are any significant deviations
• open (Start-Settings-Control Panel-Administrative Tools) the Event Viewer
and check for "Errors Messages" in the Application Log and the System Log
• open (Start-Settings-Control Panel-Administrative Tools-Computer
Management) the Disk Defragmenter to see if defragmentation is required
• open (Start-Settings-Control Panel-Administrative Tools-Computer
Management) the Device Manager and check that no hardware errors are
indicated
• open the Windows Explorer and search for PPA crash dump files
(*exception.txt)
If you see any inconsistency or strange behavior in the system you may have to
close and reopen a Workplace, restart a service and in worst case restart a whole
node.

40 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.15.1 Some advice for a Maintenance Engineer

It is also very important that you do these inspections after a major disturbance in
the system (lost main part of the communication, many servers has been down
(power, restart…)). After a disturbance you should especially check the Workplaces
if you have red crosses over alarm lists, event lists or alarm bands, suspect that the
alarm and event list not updates properly, red crosses in process displays or that
trend displays not updating. In these cases you normally come back to operation by
closing and reopen the Workplace.

3BSE025721D212 41
Process Portal A2.1/2, Release Notes
Chapter 5 Remarks and Notes

5.16 User documentation


This chapter describes additions, late changes and errors in the user documentation.

5.16.1 Where to find the User Documentation


The manuals are available in .pdf format before installation, when browsing in the
Document directory.
User documentation (in .pdf format) can be found after the installation, under
“<Install path>\ABB Industrial IT\Operate IT\Process Portal A\doc”, e.g.
“C:\Program Files\ABB Industrial IT\Operate IT\Process Portal A\doc”.
In this directory you find a number of folders representing the product and
additional functions related to it, the documentation can be found inside these
folders.
If a File Download dialog is opened, choose the radio button “Open this file from its
current location”. The book will be opened in Acrobat Reader.

5.16.2 Alarm and Event


How to set Colors for Alarm and Event lists.
In the priorities tab for Alarm and Event List Configuration it is possible to set color
for alarm and events. The connection between the Logical Color and Alarm List
Priorities Tab need some explanation:
UnAck Text column
This color is used both for the alarm text and the Ack. column. The text itself will
not flash. The color for the text will be the first color in the flashing sequence
configured by the Logical Color definition.

42 3BSE025721D212
Process Portal A2.1/2, Release Notes
Section 5.16.2 Alarm and Event

Chapter 6 How to Report Errors

Please contact your local ABB representative for reporting errors and to get
information and updates.

3BSE025721D212 43
Process Portal A2.1/2, Release Notes
Chapter 6 How to Report Errors

44 3BSE025721D212
3BSE 025 721D212 April 2003

Regional Center Americas Regional Center Sweden Regional Center Germany


Wickliffe, Ohio, USA Västerås, Sweden Mannheim, Germany
Phone: +1 440 585 8500 Phone: +46 (0) 21 34 20 00 Phone: +49 (0)1805 266776
Fax: +1 440 585 8756 Fax: +46 (0) 21 13 78 45 Fax: +49 (0)1805 776329