System 800xA

Upgrade
System Version 5.1

Power and productivity

TM
for a better world
System 800xA
Upgrade

System Version 5.1

NOTICE
This document contains information about one or more ABB products and may include a
description of or a reference to one or more standards that may be generally relevant to
the ABB products. The presence of any such description of a standard or reference to a
standard is not a representation that all of the ABB products referenced in this document
support all of the features of the described or referenced standard. In order to determine
the specific features supported by a particular ABB product, the reader should consult the
product specifications for the particular ABB product.

ABB may have one or more patents or pending patent applications protecting the intel-
lectual property in the ABB products described in this document.

The information in this document is subject to change without notice and should not be
construed as a commitment by ABB. ABB assumes no responsibility for any errors that
may appear in this document.

In no event shall ABB 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 be
liable for incidental or consequential damages arising from use of any software or hard-
ware described in this document.

This document and parts thereof must not be reproduced or copied without written per-
mission from ABB, 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 2004/108/EEC and in Low
Voltage Directive 2006/95/EEC.

TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respec-
tive owners.

Copyright © 2003-2011 by ABB.

All rights reserved.

Release: August 2011

Document number: 3BSE036342-510 C
 Table of Contents

About this User Manual

General ........................................................................................................................23
Version Described in this Document ...............................................................................24
Document Conventions ...................................................................................................24
Feature Pack .........................................................................................................24
Warning, Caution, Information, and Tip Icons................................................................24
Terminology.....................................................................................................................25
Related Documentation ...................................................................................................26

Section 1 - Introduction
Overview..........................................................................................................................27
Supported Upgrade Paths ................................................................................28
Graphics...........................................................................................................................29
Reference Instructions .....................................................................................................29
Online Upgrade ...............................................................................................................30
Supported Operating Systems .........................................................................................31
Planning for the Upgrade.................................................................................................33
System Installer ...............................................................................................................35
System Configuration Console........................................................................................35
System Language Package ..............................................................................................36
Precautions ......................................................................................................................36
Windows Hardening ........................................................................................................37
Firmware Memory Consumption ....................................................................................37

Section 2 - Upgrading Redundant Domain Controllers

Introduction .....................................................................................................................39

3BSE036342-510 C 5
Table of Contents

Prerequisites .................................................................................................................... 39
Upgrading Combined Domain Controllers/Aspect Servers ........................................... 40
Preparation ...................................................................................................................... 40
Preparing the Active Directory to Accept Windows Server 2008 ....................... 40
Preparing a Domain for Windows Server 2008 ................................................... 42
Preparing a Forest for a Read-Only Domain Controller...................................... 43
Removing the Redundant Domain Controller................................................................. 43
Installing an Additional Windows Server 2008 Domain Controller ............................... 45
Transferring the FSMO Roles to the Secondary Domain Controller.............................. 48
Transferring the Schema Master Role ................................................................. 49
Registering Schmmgmt.dll ................................................................. 49
Running the Active Directory Schema Master Snap-in...................... 49
Transferring the Domain Naming Master Role ................................................... 50
Transferring the RID Master, PDC Emulator, and Infrastructure Master Roles.. 51
Removing the Remaining Windows Server 2003 Domain Controller ............................ 53
Installing an Additional Windows Server 2008 Domain Controller ............................... 55
Required 800xA Software............................................................................................... 58

Section 3 - Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

Introduction ..................................................................................................................... 59
Control Builder M Compatibility Issues ......................................................................... 60
Considerations................................................................................................................. 60
Upgrade Flow .................................................................................................................. 60
Central Licensing System ............................................................................................... 61
Online Upgrade ............................................................................................................... 61
Redundant Aspect Server..................................................................................... 64
Redundant 800xA for Harmony and 800xA for AC 870P/Melody Servers .... 69
Redundant Connectivity Servers.......................................................................... 70
Redundant Aspect Server (2oo3 Redundancy Only) ....................................... 72
Clients ............................................................................................................ 73
Information Management Server ......................................................................... 74
Application Servers ......................................................................................... 76
Remaining Nodes................................................................................................. 77

6 3BSE036342-510 C
 Table of Contents

800xA 5.0 SP2 Primary Aspect Server ................................................................77

Remaining Steps...................................................................................................78
Pre-Upgrade Procedures ..................................................................................................79
Batch Management...............................................................................................79
Customized Alarm Priority Mapping Aspects .....................................................80
800xA for AC 800M ............................................................................................80
Structured Data Logger ........................................................................................81
Engineering Studio Function Designer System Extensions.................................81
Device Management FOUNDATION Fieldbus ...................................................82
User-Made Modifications to Library Objects Representing FF Standard
Blocks ...........................................................................82
Exporting Locally Stored Parameter Value Sets .................................83
800xA for Advant Master and 800xA for Safeguard ...........................................84
Save the Advant Master Controller Licenses.txt.................................85
Save the DATHR Files ........................................................................85
Document the RTA Board Control Aspect Settings............................86
800xA for Harmony .............................................................................................86
Disable Harmony Services on 800xA for Harmony Servers ..............86
Save 800xA for Harmony Information ...............................................87
800xA for AC 870P/Melody ........................................................................87
800xA for MOD 300 ............................................................................................88
IEC 61850 Connect ..............................................................................................88
PLC Connect ........................................................................................................88
Asset Optimization...............................................................................................89
PC, Network and Software Monitoring................................................................92
PC, Network and Software Monitoring Device Library ......................................93
SMS and e-mail Messaging .................................................................................94
Scheduler Service (Application Scheduler) .........................................................96
Calculations Service.............................................................................................96
Basic History Service Data ..............................................................................96
Process Engineering Tool Integration ..................................................................97
Requirements for VB Graphics Extension Software ...........................................97
Installing Visual BASIC 6.0 with SP6 .............................................................98

3BSE036342-510 C 7
Table of Contents

Installing the VB Graphics Extension Software .................................................. 98

Post Upgrade Procedures .............................................................................................. 101
Migrating the Structured Data Logger SQL Database....................................... 101
IEC 61850 Connect............................................................................................ 102
Customized Alarm Priority Mapping Aspects................................................... 102
Reconfiguring Group Displays .......................................................................... 102
Upgrading Faceplates......................................................................................... 102
800xA for AC 800M .......................................................................................... 103
Engineering Studio ............................................................................................ 103
Check and Repair AES Variable Table ............................................. 103
Upgrade Diagram References and Diagram Variables ..................... 104
Engineering Studio Function Designer System Extensions ............. 105
Deleting Engineering Base Service from the Service Structure ....... 105
Device Management and Fieldbuses.................................................................. 105
Restore Device Types........................................................................ 105
Device Management FOUNDATION Fieldbus ............................ 112
PROFINET IO Feature Pack 1.2........................................................................ 115
800xA for Advant Master and 800xA for Safeguard......................................... 116
Copy the Advant Master Controller Licenses.txt ............................. 116
Copy the DATHR Files ..................................................................... 116
Reconfigure RTA Board Control Aspect Settings ............................ 116
800xA for Harmony........................................................................................... 117
800xA for AC 870P/Melody .......................................................................... 118
Restore 800xA for AC 870P/Melody Information ........................... 118
Additional 800xA for AC 870P/Melody Configuration Steps.......... 119
800xA for MOD 300.......................................................................................... 120
PLC Connect...................................................................................................... 121
Modify Installation for IEC 60870 or Basic Project Objects............ 121
Restoring the Pretreat dll .................................................................. 121
Update the Sattbus Configuration ..................................................... 122
Redeploy the PLC Connect Configuration ....................................... 122
Asset Optimization ............................................................................................ 122
PC, Network and Software Monitoring ............................................................. 126

8 3BSE036342-510 C
 Table of Contents

PNSM Device Library Restore Procedure .........................................................127

SMS and e-mail Messaging ...............................................................................128
Batch Management.............................................................................................128
Selecting the Alarm Server ...............................................................129
Basic History Service .........................................................................................129
Calculations Service...........................................................................................130
Scheduling Service (Application Scheduler) .....................................................131
Process Engineering Tool Integration ................................................................131
Miscellaneous Procedures .............................................................................................132
Upgrade Control Builder M Projects .............................................................132
PC, Network and Software Monitoring..............................................................133
Add Autostart Shortcut ......................................................................................134
Online Upgrade of a Multisystem Integration System ..................................................135
System Backup ..............................................................................................................135

Section 4 - Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

Introduction .......................................................................................................137
Considerations ...............................................................................................................137
Control Builder M Compatibility Issues .......................................................................138
Upgrade Flow ................................................................................................................138
Central Licensing System..............................................................................................138
System Upgrade.............................................................................................................138
Pre-Upgrade Procedures ................................................................................................142
Customized Alarm Priority Mapping Aspects ...................................................142
800xA for AC 800M ..........................................................................................142
Structured Data Logger ......................................................................................143
Engineering Studio.............................................................................................144
Device Management FOUNDATION Fieldbus .................................................145
User-Made Modifications to Library Objects Representing FF Standard
Blocks .........................................................................145
Exporting Locally Stored Parameter Value Sets ...............................145
PROFINET IO Feature Pack 1.2 ........................................................................146
800xA for Advant Master and 800xA for Safeguard .........................................147

3BSE036342-510 C 9
Table of Contents

Save the Advant Master Controller Licenses.txt .............................. 147

Save the DATHR Files ...................................................................... 147
Document the RTA Board Control Aspect Settings.......................... 148
800xA for Harmony........................................................................................... 148
Disable Harmony Services on 800xA for Harmony Servers ............ 148
Save 800xA for Harmony Information ............................................. 149
800xA for AC 870P/Melody ...................................................................... 149
800xA for MOD 300.......................................................................................... 150
IEC 61850 Connect............................................................................................ 150
PLC Connect...................................................................................................... 150
Asset Optimization ............................................................................................ 151
PC, Network and Software Monitoring ............................................................. 154
PC, Network and Software Monitoring Device Library .................................... 155
SMS and e-mail Messaging ............................................................................... 155
Batch Management ............................................................................................ 157
Information Management .................................................................................. 158
Scheduler Service (Application Scheduler) ....................................................... 158
Calculations Service .......................................................................................... 159
Basic History Service Data ............................................................................ 159
Process Engineering Tool Integration ................................................................ 160
Requirements for VB Graphics Extension Software ......................................... 160
Installing Visual BASIC 6.0 with SP6 ........................................................... 160
Installing the VB Graphics Extension Software ................................................ 161
Post Upgrade Procedures .............................................................................................. 163
Migrating the Structured Data Logger SQL Database....................................... 163
IEC 61850 Connect............................................................................................ 164
800xA System Restore ............................................................................... 165
Consistency Check............................................................................................. 167
Loading the VB Graphics Extensions................................................................ 167
Customized Alarm Priority Mapping Aspects................................................... 169
Reconfiguring Group Displays .......................................................................... 169
Upgrading Faceplates......................................................................................... 170

10 3BSE036342-510 C
 Table of Contents

800xA for AC 800M ..........................................................................................170

Engineering Studio.............................................................................................170
Check and Repair AES Variable Table .............................................171
Upgrade Diagram References and Diagram Variables......................171
Engineering Studio Function Designer System Extensions..............172
Deleting Engineering Base Service from the Service Structure .......172
Device Management and Fieldbuses..................................................................173
Restore Device Types........................................................................173
Device Management PROFIBUS & HART ......................................178
Device Management FOUNDATION Fieldbus ................................179
800xA for Advant Master and 800xA for Safeguard .........................................182
Copy the Advant Master Controller Licenses.txt..............................182
Copy the DATHR Files .....................................................................183
Reconfigure RTA Board Control Aspect Settings.............................183
800xA for Harmony ...........................................................................................184
800xA for AC 870P/Melody ..........................................................................185
Restore 800xA for AC 870P/Melody Information............................185
Additional 800xA for AC 870P/Melody Configuration Steps..........186
800xA for MOD 300 ..........................................................................................186
PLC Connect ......................................................................................................187
Modify Installation for IEC 60870 or Basic Project Objects............187
Restoring the Pretreat dll...................................................................188
Update the Sattbus Configuration .....................................................188
Redeploy the PLC Connect Configuration........................................188
Asset Optimization.............................................................................................189
PC, Network and Software Monitoring..............................................................192
PNSM Device Library Restore Procedure .........................................................194
SMS and e-mail Messaging ...............................................................................194
Batch Management.............................................................................................194
Selecting the Alarm Server ...............................................................195
Basic History Service .........................................................................................196
Information Management...................................................................................197
Calculations Service...........................................................................................197

3BSE036342-510 C 11
Table of Contents

Scheduling Service (Application Scheduler) ..................................................... 198

Process Engineering Tool Integration ................................................................ 198
Miscellaneous Procedures ............................................................................................. 198
Upgrade Control Builder M Projects ............................................................. 199
PC, Network and Software Monitoring ............................................................. 199
Add Autostart Shortcut ...................................................................................... 201
System Backup.............................................................................................................. 201

Section 5 - Upgrading 800xA 4.1 to 800xA 5.1 Offline

Introduction ....................................................................................................... 203
Functional Area Naming ............................................................................................... 204
Considerations............................................................................................................... 204
Control Builder M Compatibility Issues ....................................................................... 205
Upgrade Flow ................................................................................................................ 205
Central Licensing System ............................................................................................. 205
System Upgrade ............................................................................................................ 205
Pre-Upgrade Procedures................................................................................................ 211
Control IT for AC 800M.................................................................................... 211
Device Management FOUNDATION Fieldbus ................................................. 212
User-Made Modifications to Library Objects Representing FF Standard
Blocks......................................................................... 212
Exporting Locally Stored Parameter Value Sets............................... 212
Device Management PROFIBUS & HART....................................................... 213
PROFIBUS Device Types.................................................................................. 214
800xA for Advant Master and 800xA for Safeguard......................................... 216
Save the Advant Master Controller Licenses.txt .............................. 216
Save the DATHR Files ...................................................................... 217
Document the RTA Board Control Aspect Settings.......................... 217
800xA for Harmony........................................................................................... 218
Save 800xA for Harmony Information ............................................. 218
800xA for AC 870P/Melody ...................................................................... 219
800xA for MOD 300.......................................................................................... 219
PLC Connect...................................................................................................... 220

12 3BSE036342-510 C
 Table of Contents

Asset Optimization.............................................................................................220
Record the Value of the OPC Group Update Rate ............................220
Back Up Data to Safe Media.............................................................221
PC, Network and Software Monitoring..............................................................223
PC, Network and Software Monitoring Device Library ....................................224
SMS and e-mail Messaging ...............................................................................225
Batch Management.............................................................................................227
Information Management...................................................................................228
Scheduler Service (Application Scheduler) .......................................................228
Calculations Service...........................................................................................228
Basic History Service Data ............................................................................229
Process Engineering Tool Integration ................................................................229
Requirements for VB Graphics Extension Software ........................................230
Installing Visual BASIC 6.0 with SP6 ...........................................................230
Installing the VB Graphics Extension Software ................................................230
Post Upgrade Procedures...............................................................................................233
800xA System Restore .......................................................................233
Consistency Check .............................................................................................235
Loading the VB Graphics Extensions ................................................................235
800xA Documentation Maintenance ..............................................................238
Composite Graphic Elements.............................................................................238
Graphic Overlap Displays ..................................................................................239
Reconfiguring Group Displays...........................................................................239
Device Management and Fieldbuses..................................................................239
Restore Device Types ....................................................................240
Device Management PROFIBUS & HART ......................................247
Device Management FOUNDATION Fieldbus ................................247
800xA for AC 800M ......................................................................................250
800xA for Advant Master and 800xA for Safeguard .........................................253
Copy the Advant Master Controller Licenses.txt..............................253
Copy the DATHR Files .....................................................................253
Reconfigure RTA Board Control Aspect Settings.............................254

3BSE036342-510 C 13
Table of Contents

800xA for Harmony........................................................................................... 254

Restore 800xA for Harmony Information......................................... 254
Synchronize the Aspect Directory .................................................... 255
Check Consistency of Harmony OPC Network Objects .................. 256
800xA for AC 870P/Melody .......................................................................... 256
Restore 800xA for AC 870P/Melody Information ........................... 257
Additional 800xA for AC 870P/Melody Configuration Steps.......... 257
800xA for MOD 300.......................................................................................... 258
PLC Connect...................................................................................................... 259
Modify Installation for IEC 60870 or Basic Project Objects............ 259
Restoring the Pretreat dll .................................................................. 259
Update the Sattbus Configuration ..................................................... 260
Redeploy the PLC Connect Configuration ....................................... 260
Engineering Studio ............................................................................................ 261
IO Allocation ............................................................................ 261
Engineering Templates for Bulk Data Manager (BDM)................... 262
Function Designer............................................................................. 262
Deleting Engineering Base Service from the Service Structure ....... 265
Asset Optimization ............................................................................................ 265
PC, Network and Software Monitoring ............................................................. 269
PNSM Device Library Restore Procedure ......................................................... 270
SMS and e-mail Messaging ............................................................................... 271
Batch Management ............................................................................................ 271
Selecting the Alarm Server ............................................................... 272
Basic History Service......................................................................................... 272
Information Management .................................................................................. 274
Calculations Service .......................................................................................... 274
Scheduling Service (Application Scheduler) ..................................................... 274
Process Engineering Tool Integration ................................................................ 275
Update VB Graphics with Newer Dependencies............................................... 275
Miscellaneous Procedures ............................................................................................. 275
Resigning Digital Signatures in 800xA 5.1 ....................................................... 275

14 3BSE036342-510 C
 Table of Contents

Restart the System..............................................................................................276

Reconfigure Event Collectors ............................................................................276
Reconfigure Alarm and Event List Configurations............................................277
Add Autostart Shortcut ......................................................................................277
System Backup ..............................................................................................................278

Section 6 - Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Introduction ..........................................................................................................279
Functional Area Naming ...............................................................................................279
Control Builder M Compatibility Issues .......................................................................280
Upgrade Flow ................................................................................................................280
Central Licensing System (Upgrade Flow A) ...............................................................283
Consistency Check ........................................................................................................283
Save Digital Signatures..................................................................................................284
External Alarm Service Group ......................................................................................284
Deploy all User Created Process Graphics....................................................................285
Backups .........................................................................................................................285
Hard Disk Backup ..............................................................................................285
800xA System Backup ...............................................................................285
Pre-Upgrade Procedures ................................................................................................287
Control IT for AC 800M ....................................................................................288
Device Management and Fieldbuses..................................................................288
Device Management FOUNDATION Fieldbus ................................288
Device Management PROFIBUS & HART ......................................289
PROFIBUS Device Types .................................................................289
AC 400 Connect and Safeguard Connect...........................................................291
PLC Connect ......................................................................................................292
Asset Optimization.............................................................................................293
Record Values for Post Upgrade .......................................................293
Back Up Data to Safe Media.............................................................294
PC, Network and Software Monitoring..............................................................295
SMS and e-mail Messaging ...............................................................................296
Batch Management.............................................................................................298

3BSE036342-510 C 15
Table of Contents

Information Management .................................................................................. 300

End Microsoft Excel Process via Windows Task Manager .............. 300
Recording Archive Group Associations ........................................... 300
ABB Process Administration Server (PAS)...................................... 301
Information Management Backup and Restore Utility..................... 301
Saving Other Information Management Related Files ..................... 303
Scheduler Service (Application Scheduler) ....................................................... 304
Calculations Service .......................................................................................... 305
Basic History Service Data ............................................................................ 305
Alarm and Event List Configurations ................................................................ 305
System Upgrade (Upgrade Flow B) .............................................................................. 306
Domain Controller Nodes .................................................................................. 306
Upgrading Domain Controller Node and OS without Formatting Hard
Disk ............................................................................ 306
Upgrading Domain Controller Node with Compatible OS .............. 307
Upgrading Domain Controller Node by Formatting Hard Disk ....... 309
800xA System Nodes......................................................................................... 310
Existing Operating System ........................................................... 311
New Operating System ..................................................................... 316
Disable Internet Explorer Enhanced Security ....................................................... 318
Group Policy Management for Upgrades...................................................................... 318
Domain Environment ..................................................................................... 318
Domain Controller Node .................................................................. 319
All Other 800xA System Nodes ....................................................... 322
Windows Workgroup Environment ................................................................ 323
Adding Privileges to the 800xA Service User............................................................... 324
Setting the PAS and IM Service Account and Password .............................................. 325
800xA System Restore (Upgrade Flow C) ............................................................ 325
800xA System Restore Procedure ..................................................................... 326
IT Control Connection Items in Log Configuration Aspects............................. 329
Consistency Check............................................................................................. 330
800xA Documentation Maintenance............................................................................. 330

16 3BSE036342-510 C
 Table of Contents

Base System Considerations..........................................................................................330

Connections between Alarm List and Alarm and Event OPC Server................330
Automatic Configuration....................................................................................332
Manual Configuration ........................................................................................332
Configure the Event Collector Service..............................................332
Organize the Library Objects ............................................................333
Check the Alarm Manager Service Configuration............................333
Add Redundancy For Alarm Manager ..............................................334
Restoring Application and Historical Data....................................................................335
Device Management and Fieldbuses ..............................................................335
Restore Fieldbus Device Types .................................................335
Update Fieldbus Device Types..........................................................340
Device Management FOUNDATION Fieldbus ................................340
800xA for AC 800M ......................................................................................343
800xA for Advant Master and 800xA for Safeguard .........................................345
PLC Connect ......................................................................................................346
Modify Installation for IEC60870 or Basic Project Objects .............346
Restoring PreTreat2.dll .....................................................................347
Restoring PreEvent.dll ......................................................................347
Redeploy the PLC Connect Configuration........................................347
Engineering Studio.............................................................................................348
IO Allocation .............................................................................348
Engineering Templates for Bulk Data Manager (BDM)...................349
Function Designer .............................................................................349
Asset Optimization.............................................................................................352
PC, Network and Software Monitoring ..........................................................357
SMS and e-mail Messaging ...............................................................................359
Batch Management.............................................................................................360
Restoring Batches..............................................................................361
Selecting the Alarm Server ...............................................................362
Basic History Service .........................................................................................362
Information Management...................................................................................363

3BSE036342-510 C 17
Table of Contents

Reconfiguring the IM Log Configuration......................................... 363

Information Management History Backup/Restore Utility .............. 364
Running the Information Management History Backup/Restore Utility365
Restoring Other Information Management Related Files................. 368
Complete the Information Management Post Install ........................ 370
Verify that all Information Management services are running. ........ 370
Restoring Archive Group Associations............................................. 370
Calculations Service .......................................................................................... 371
Scheduling Service (Application Scheduler) ..................................................... 371
Resigning Digital Signatures in 800xA 5.0 SP2 ........................................................... 372
Restart the System......................................................................................................... 372
Reconfigure Alarm and Event List Configurations....................................................... 372
Information Management Maintenance ........................................................................ 373
Configure Windows Services and Windows Firewall ................................................... 374
Add Autostart Shortcut ................................................................................................. 375
System Backup.............................................................................................................. 375

Appendix A - Warning and Error Messages

Failed to Serialize Aspect.............................................................................................. 377
ASO Object Class xxxx ................................................................................................ 377
UnplacedObjects.afw .................................................................................................... 378
The System Cannot Find the Path Specified ................................................................. 378
System Extension ´xxxx´ with ID ´Guid` is not Installed on this Node ....................... 379
Timeout by External Service ......................................................................................... 379
Graphic Aspect = xxx Cannot be Imported................................................................... 380
Too Many Aspects of Category..................................................................................... 380
Aspect Category is Missing........................................................................................... 381
Unknown Transaction Error .......................................................................................... 382

Appendix B - Control Builder M Compatibility Issues

Introduction ................................................................................................................... 383
800xA 5.0 SP2 to 800xA 5.1 Compatibility Issues ...................................................... 383
800xA 4.1 to 800xA 5.1 Compatibility Issues .............................................................. 385

18 3BSE036342-510 C
 Table of Contents

800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility Issues ...............................................396

Removed Project Constants...........................................................................................407
SupervisionBasicLib (cSinit.*) ..........................................................................407
BasicLib (cEnable.*) ......................................................................................407
SupervisionLib (cInit.*) .................................................................................407

Appendix C - Consistency Check

Introduction ...................................................................................................................413
Performing the Consistency Check ...............................................................................415
Returning to the Pre-Upgrade Procedures .....................................................................416
Returning to the Post Upgrade Procedures....................................................................416

Appendix D - Recording the Number of Aspects and Objects

Introduction ...................................................................................................................417
Recording the Number of Aspects and Objects in the System......................................417
Returning to the Pre-Upgrade Procedures .....................................................................419
Returning to the Post Upgrade Procedures....................................................................419

Appendix E - Information Management Upgrade

Information Management Pre-Upgrade Procedures ......................................................421
End Microsoft Excel Process via Windows Task Manager................................421
Recording Archive Group Associations .........................................................421
ABB Process Administration Service (PAS)......................................................421
Cleaning the History Database...........................................................................422
Information Management History Backup and Restore Utility .....................422
Saving Other Information Management Related Files.......................................424
Returning to the Pre-Upgrade Procedures .....................................................................425
Information Management Post Upgrade Procedures.....................................................426
Reconfiguring the IM Log Configuration ......................................................426
Information Management History Backup/Restore Utility................................427
Considerations...................................................................................427
Running the Information Management History Backup/Restore Utility428
Restoring Other Information Management Related Files ..................................431

3BSE036342-510 C 19
Table of Contents

Starting PAS....................................................................................................... 433

Restoring Archive Group Associations .......................................................... 433
Instance_config.txt File Creation....................................................................... 433
Updating Archive Logs...................................................................................... 434
Information Management Maintenance............................................................. 434
Running hsDBMaint -stagger ............................................................................ 436
Returning to the Post Upgrade Procedures ................................................................... 436

Appendix F - Mapping of Deprecated IT Asset Object Types

Mapping ........................................................................................................................ 437

Appendix G - Update to 800xA 5.1 Rev A

Introduction ................................................................................................................... 441
Affected Products .......................................................................................................... 441
Uninstallation ................................................................................................ 442
Installation..................................................................................................................... 445
800xA for AC 800M .......................................................................................... 449
AC 800M High Integrity Controller Update..................................... 449
AC 800M Connect ............................................................................ 450
OPC Server for AC 800M................................................................. 450
Control Builder M............................................................................. 451
Base Software for SoftControl.......................................................... 451
800xA for DCI ................................................................................................... 452
800xA for MOD 300.......................................................................................... 452
800xA for Harmony........................................................................................... 453
800xA for Melody ............................................................................................. 457
Device Library Wizard....................................................................................... 458
Device Management FOUNDATION Fieldbus ................................................ 458
Device Management PROFIBUS & HART....................................................... 458
Batch Management ............................................................................................ 459
Information Management .................................................................................. 459
Version Verification .......................................................................... 460
Migrating to Oracle 11gR2 ............................................................... 461

20 3BSE036342-510 C
 Table of Contents

Appendix H - Online Upgrade Controller Level

Introduction ...................................................................................................................465
Online Upgrade Controller Level ..................................................................................465
Flowchart for Upgrading Controller Level....................................................................466
Flowchart for Extending Controller Level.....................................................................468

Index

Revision History
Introduction ...................................................................................................................475
Revision History ............................................................................................................475
Updates in Revision Index A.........................................................................................476
Updates in Revision Index B .........................................................................................476
Updates in Revision Index C .........................................................................................478

3BSE036342-510 C 21
Table of Contents

22 3BSE036342-510 C
 About this User Manual

General
Any security measures described in this document, for example, for user access,
password security, network security, firewalls, virus protection, etc., represent
possible steps that a user of an 800xA System may want to consider based on a
risk assessment for a particular application and installation. This risk assessment,
as well as the proper implementation, configuration, installation, operation,
administration, and maintenance of all relevant security related equipment,
software, and procedures, are the responsibility of the user of the 800xA System.
This User Manual describes how to manually perform upgrade procedures for the
800xA Base System and Functional Area software. It does not include information
on site planning, engineering planning, software configuration, network design,
security measures, tools, maintenance, etc. that can be found in other 800xA User
Manuals.
All 800xA Base System and Functional Area software described in this User
Manual will be upgraded from latest revisions of System Version 5.0 Service Pack 2
or System Version 4.1 to the latest release of System Version 5.1.
Unless otherwise noted, the version of all 800xA Base System and Functional Area
software described in this instruction is the latest release of 800xA 5.1. The
procedures described require Windows Administrator privileges.
This User Manual does not include information on site planning, engineering
planning, software configuration, network design, security measures, tools,
maintenance, etc. that can be found in other 800xA User Manuals.

3BSE036342-510 C 23
Version Described in this Document About this User Manual

Version Described in this Document

All information and procedures described in this document are specific to the latest
release of 800xA 5.1.

Document Conventions
Microsoft Windows conventions are normally used for the standard presentation of
material when entering text, key sequences, prompts, messages, menu items, screen
elements, etc.

Feature Pack
The Feature Pack content (including text, tables, and figures) included in this
User Manual is distinguished from the existing content using the following
two separators:
Feature Pack Functionality

<Feature Pack Content>

Feature Pack functionality included in an existing table is indicated using a

table footnote (*) :
* Feature Pack Functionality

Unless noted, all other information in this User Manual applies to 800xA Systems
with or without a Feature Pack installed.

Warning, Caution, Information, and Tip Icons

This publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:
Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.

24 3BSE036342-510 C
About this User Manual Terminology

Warning icon indicates the presence of a hazard which could result in personal
injury.
Caution icon indicates important information or warning related to the concept
discussed in the text. It might indicate the presence of a hazard which could
result in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.

Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
fully comply with all Warning and Caution notices.

Terminology
A complete and comprehensive list of Terms is included in System 800xA System
Guide Functional Description (3BSE038018*). The listing includes terms and
definitions that apply to the 800xA System where the usage is different from
commonly accepted industry standard definitions and definitions given in standard

3BSE036342-510 C 25
Related Documentation About this User Manual

dictionaries such as Webster’s Dictionary of Computer Terms. Terms that uniquely

apply to this instruction are listed in the following table.

Term/Acronym Description
Backup 800xA Backup: Backup using the 800xA Backup Definition aspect.
Functional Area Backup: Backup via defined tools or copy of Functional Area
configuration and/or data to a safe media for items not covered by 800xA
Backup.
The specific operations called out for the Functional Area within the
Backup/Restore procedure in System 800xA Maintenance (3BSE046784*) for
same version to same version backup and restore.
Restore 800xA Restore: Restore via Configuration Wizard.
Functional Area Restore: Restore via defined tools or copy of Functional Area
configuration and/or data from a safe media for items not covered by 800xA
Backup.
The specific operations called out for the Functional Area within the
Backup/Restore procedure in System 800xA Maintenance (3BSE046784*) for
same version to same version backup and restore.
Upgrade Moving from one 800xA release to a later 800xA release, whether it be a major
or minor release.
Update Adding service packs, patches, hot fixes, or rollups to an existing 800xA System.

Related Documentation
A complete list of all documents applicable to the 800xA System is provided in
System 800xA Released User Documents, 3BUA000263*. This document lists
applicable Release Notes and User Instructions. It is provided in PDF format and is
included on the Release Notes/Documentation media provided with the system.
Released User Documents are updated with each release and a new file is provided
that contains all user documents applicable for that release with their applicable
document number. Whenever a reference to a specific instruction is made, the
instruction number is included in the reference.

26 3BSE036342-510 C
 Section 1 Introduction

Overview
This document reflects 800xA System and Functional Area software at the time
of release. All 800xA System and Functional Area Release Notes must be read
and understood before performing any automated or manual installation, post
installation, or upgrade procedures. The Release Notes contain any last minute
changes that must be performed when installing or upgrading the 800xA System.
All Release Notes can be found on the CD labeled System Version 5.1 Released
Documents.
This instruction describes how to upgrade to ABB Industrial IT 800xA 5.1. It covers
the following scenarios:
• Upgrading Redundant Domain Controllers.
• Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online.
• Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline.
• Upgrading 800xA 4.1 to 800xA 5.1 Offline.
• Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2.
The topics in this section briefly describe the prerequisite requirements, procedures,
and other considerations depending on the current software version. Review this
information before installing 800xA 5.1.
If virus checking software is installed on a node, disable it until after the 800xA
System is installed and configured (post installation).

3BSE036342-510 C 27
Supported Upgrade Paths Section 1 Introduction

Supported Upgrade Paths

Upgrading directly from 800xA 5.0 or 800xA 5.0 SP1a to 800xA 5.1 is not
supported. If running this version, it is necessary to upgrade to the latest revision
of 800xA 5.0 SP2 before upgrading to 800xA 5.1.
Upgrading directly from 800xA 4.0 to 800xA 5.1 is not supported. If running this
version, it is necessary to upgrade to the latest revision of 800xA 4.1 before
upgrading to 800xA 5.1.
Upgrading directly from 800xA 3.1 SP3 to 800xA 5.1 is a two-step process. It is
necessary to upgrade to 800xA 5.0 SP 2 before upgrading to 800xA 5.1. Perform
the procedures in Section 6, Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 and
then in Section 3, Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online or Section 4,
Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline.
Refer to System 800xA Upgrade (3BSE036342*) for information on upgrading a
SB 2.1/2 800xA System.
800xA for DCI was not included with the initial release of 800xA 5.1 and thus
800xA for DCI upgrade instructions are not documented in this user manual.
Refer to 800xA for DCI 5.1 Installation - Post Installation - Upgrade
Supplemental User Manual (3BUA001686*) for upgrade of 800xA for DCI 5.1.
Table 1 provides a tabular representation of the supported upgrade paths.

Table 1. Supported Upgrade Paths1,2

To System Version
3.1 SP1 3.1 SP2 3.1 SP3 4.0 4.1 5.0 5.0 SP1a 5.0 SP2 5.1
From System Version
3.1 OK OK NS NS NS NS NS NS NS
3.1 SP1 OK NS NS NS NS NS NS NS
3.1 SP2 OK OK OK NS NS NS NS
3.1 SP3 NS NS NS OK OK NS
4.0 OK NS NS NS NS
4.1 OK OK OK OK

28 3BSE036342-510 C
Section 1 Introduction Graphics

Table 1. Supported Upgrade Paths1,2

To System Version
3.1 SP1 3.1 SP2 3.1 SP3 4.0 4.1 5.0 5.0 SP1a 5.0 SP2 5.1
5.0 OK NS NS
5.0 SP1a OK NS
5.0 SP2 OK
NOTES:
1. All upgrade paths listed are from the latest revision to the latest revision.
2. OK = supported, NS = Not supported, blank = not possible.

Graphics
800xA 5.1 supports Process Graphics 2 as a default with optional VB Graphics
extensions that can be installed and loaded when upgrading. 800xA 5.0 SP2
supported VB Graphics as the default with Process Graphics 2 extensions that could
be installed and loaded. 800xA SV 5.0 SP1 and earlier supported VB Graphics as
the default with no option for Process Graphics 2.
Customers upgrading from previous 800xA versions can still view and modify their
VB Graphics, but they must install their previously licensed version of Visual
BASIC 6.0 with SP6 in order to do so. They must also install and load the VB
Graphics extensions.
New 800xA 5.1 customers should not install the VB Graphics extensions as they
will only have the VB runtime and will not be able to create and/or modify VB
graphics.

Reference Instructions
The following instructions are used in conjunction with this one. These instructions
are needed to perform the required installation, post installation, and backup/restore
procedures.
• If performing the upgrade manually:
– System 800xA Installation (3BSE034678*).

3BSE036342-510 C 29
Online Upgrade Section 1 Introduction

– System 800xA Post Installation (3BUA000156*).

– System 800xA Maintenance (3BSE046784*).
• If performing the upgrade using System Installer:
– System 800xA Automated Installation (3BSE034679*).

Online Upgrade
Online Upgrade makes it possible to upgrade an existing 800xA System (latest
revision of 800xA 5.0 SP2 or later) without a process shutdown. Plant operations are
not disturbed while upgrading server and client software, including OCS
connectivity services, and AC 800M Controllers (processor units and
communication interfaces (CI)). The 800xA System being upgraded must have
redundant Aspect and Connectivity Servers, and redundant AC 800M Controllers
consisting of two redundant processing units connected to I/O modules either
directly to the modulebus or via various CI modules.
Online Upgrade Controller Level allows AC 800M controllers to be upgraded with
new firmware versions online. Online upgrade is initiated from Control Builder by a
nine-step wizard.
This procedure is only applicable to the latest revision of 800xA 5.0 SP2 to
800xA 5.1 upgrade path with redundant Aspect and Connectivity Servers. Refer
to Section 3, Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online for more
information.
The OCS connectivity services are possible to upgrade online; however, the OCS
system itself is upgraded following the rules defined for the OCS system being
used.
• The nodes are upgraded in the following order:
– Domain Controller.
– One redundant Aspect Server.
– One redundant 800xA for Harmony Configuration Server for each
redundant 800xA for Harmony Configuration Server configuration.
– 800xA for AC 870P/Melody Configuration Server.

30 3BSE036342-510 C
Section 1 Introduction Supported Operating Systems

– One redundant Connectivity Server for each redundant Connectivity

Server configuration.
– Third Aspect Server (if 2oo3 redundancy).
– Some clients.
– IM Server.
– All other Application Servers (Batch, Asset Optimization, PC, Network
and Software Monitoring, etc.).
– All other nodes except Primary Aspect Server.
– Primary Aspect Server.
– The client and server level is upgraded and the plant is fully operable,
although the controllers are not upgraded. The controller level is upgraded
as follows:
This instruction does not contain procedures for upgrading the AC 800M
controller level. Refer to Appendix H, Online Upgrade Controller Level for a
general description.
– Some redundant Controller pairs (and CEX units if needed).
– Remaining redundant Controller pairs (if desired).
– Nonredundant controllers (no CEX units). Upgrading nonredundant
controllers will require minimal plant downtime.

Supported Operating Systems

800xA System software may be installed on the 32-bit (x86) US English version of
Windows Server 2008 Standard or Enterprise edition with Service Pack 2, or 32-bit
(x86) US English version of Windows 7 Professional or Enterprise edition with SP1.
Windows Server 2008 R2 is not supported. The following conditions affect the
decision on which operating system to use:
Windows Server 2008 and Windows 7 will be used throughout the remainder of
this document (service pack and edition info will not be repeated).
• Certain 800xA Server types can run on Windows 7 as well as on Windows
Server 2008. Windows Server 2008 must be used for the following
applications:

3BSE036342-510 C 31
Supported Operating Systems Section 1 Introduction

– Domain Server.
– Aspect Server when it runs the Domain Controller and Domain Name
System (DNS).
– Batch Server (except in a Single Node Engineering System).
– Information Management Server.
The IM Server can only be installed on a Single Node Engineering System if the
Operating System is Windows Server 2008.
– Servers that run Asset Optimization (except in a Single Node Engineering
System).
– 800xA for Harmony Connectivity Server, Configuration Server, and
Configuration Server with Connectivity Server.
– 800xA for AC 870P/Melody Connectivity Server and Configuration
Server.
– 800xA for MOD 300 Connectivity Server.
• Systems using Windows 7 for the Aspect Server nodes are limited to nine PC
nodes, not counting Domain Server nodes. Systems using Windows 7 for any
other server nodes, other than the Aspect Server nodes, are limited to 11 PC
nodes, not counting the Domain Server nodes. These limitations depend on
Microsoft licensing rules for Windows 7 and Internet Information Services
(IIS).
• Windows 7 may be used in most other instances, although some performance
benefits may be gained by using Windows Server 2008. If Windows Server
2008 is not required, then Windows 7 is generally recommended.
• The Windows operating system may be purchased from any Microsoft reseller.
• Preconfigured servers/clients that come from the server/client manufacturer
must be preconfigured by the server/client manufacturer to meet 800xA System
specifications. If they are not, they must be reconfigured by the user to meet
800xA System specifications.
• Existing nodes that are not running Windows 7 or Windows Server 2008 must
be reformatted and the compatible Operating System must be installed.

32 3BSE036342-510 C
Section 1 Introduction Planning for the Upgrade

• Click Advanced when installing Windows 7 or Windows Server 2008. This is

required to delete the existing partition and recreate a new one. Failure to
perform this step will leave old data on the hard drive.

Planning for the Upgrade

Planning for the upgrade can save time and resources. The upgrade paths in this
instruction are presented in sequential order; however, depending on the plant
performing the upgrade, some of the actions can be performed in advance or in
parallel. For example, the upgrade flows are written to reflect upgrading and using
existing servers and clients. If new servers and clients are being used, prepare those
before beginning the upgrade (load and configure the Windows Operating System,
third party software, etc.), or while performing the pre-upgrade procedures.
For optimal software prerequisites, refer to Third Party Software System 800xA
(3BUA000500*). The prerequisites depend on the functions installed in the system,
or on each node type. This document is accessible from ABB SolutionsBank.
For an upgrade, performance will be determined by the actual hardware of the
system. System performance after the upgrade is completed will be determined by
the hardware being upgraded. Memory size and processor speed have a direct
impact on system performance. Refer to System 800xA Verified Third Party
Products (3BSE046579*) for a list of hardware verified for use with the 800xA
System. This document is accessible from ABB SolutionsBank.
1. 800xA Licensing: Order the licenses required for the current system version
and revision. Licenses from previous versions will not work.
2. AC 800M Licensing: The licensing model for the AC 800M Control Software
Integration has changed beginning with 800xA 5.1. Licensing is now scaled on
installed controller capacity instead of licensing on connected signals and
devices to the controllers (CLPs).
Each installed controller or redundant pair in the plant requires a separate
Control Software license. Each controller type has its own license, where the
price of it depends on the capacity of the controller. Existing CLP-based
licenses must be converted to new licenses based on the installed controller
capacity.
ABB requires data from the existing system in order to perform the conversion.
The data is collected by running the License Report Tool in the existing system.

3BSE036342-510 C 33
Planning for the Upgrade Section 1 Introduction

a. Copy LicenseReport.exe from the following directory on 800xA

System Installation DVD 1 to a directory on any node in the old system.
Engineering & Development\Control Builder
M\Tools\LicenseReport

The LicenseReport.exe file can alternatively be downloaded from ABB

SolutionsBank (document identity 3BSE062832).
b. Verify the system is running.
c. Double-click LicenseReport.exe.
d. A file named LicenseReport.bin is created a few seconds later in the
newly created directory.
e. The file contains signature data unique for the actual system, and is in an
encrypted format. Provide this file while requesting an upgrade to the new
800xA 5.1 licenses.
3. If new servers and clients are being used, prepare those before beginning the
upgrade (load and configure the Windows Operating System, third party
software, etc.).
4. Consider other issues that are important prior to starting the upgrade, such
as:
The following considerations may vary depending on the system version being
upgraded and if the upgrade will be performed online or offline.
Concurrent access to the current 800xA System version and the 800xA 5.1
system is recommended until the upgrade has been performed. This makes it
possible to easily retrieve any data or files that have been missed. Concurrent
access depends upon many different factors, including:
– Configuration of the existing system.
– Desired configuration of the 800xA 5.1 system.
– Server and client use strategy.
– Configuration of user and user groups.
– Use of service accounts.
– Domain controllers.
– Redundancy.
– Logical and physical networks.

34 3BSE036342-510 C
Section 1 Introduction System Installer

One strategy is to leave a minimal part of the existing system intact, such as an
Aspect Server, while preparing a major part of the 800xA 5.1 System. Another
strategy is to prepare a minimal 800xA 5.1 System.
Retaining an Aspect Server from the existing system minimizes the time it
takes to retrieve data or files from it. A disk drive image provides a quick way
to recover, but often it requires no hardware upgrade. Try to delay the upgrade
of the hardware in one Aspect Server as long as possible.
If it is not necessary to do the complete upgrade in one process, it may be
possible to perform the upgrade in steps by stopping selected system functions
or by stopping some parts of the plant, or a combination of the two.
5. Prepare the Device Library (select the set of devices used at the customer site
and prepare the files on a transportable media, ready to install). The latest files
at the time of the 800xA 5.1 are available on DVD2, DVD3, and DVD4. Check
for newer version of Device Libraries in ABB SolutionsBank.
6. Refer to System Installer on page 35 and determine whether or not System
Installer can be used to perform the upgrade.

System Installer
Upgrades from the latest revisions of 800xA 5.0 SP2 to 800xA 5.1 and from
800xA 4.1 to 800xA 5.1 can be executed either semi-automatically using the
System Installer as described in System 800xA Automated Installation
(3BSE034679*), or manually as described in this instruction.
The System Installer is more efficient since it performs many of the time-consuming
and difficult tasks, and verifies that the software is installed in the correct order, the
desired configurations are supported, etc.

System Configuration Console

Some procedures described in this instruction use the 800xA System Configuration
Wizard. A new feature, the System Configuration Console, can also be used to
perform many of these procedures. Refer to System 800xA Tools (2PAA101088*) for
information and instructions on using the System Configuration Console.

3BSE036342-510 C 35
System Language Package Section 1 Introduction

System Language Package

The 800xA System includes support for US English only. Translations of the
operator interface (System 800xA Language Packages) are released separately after
the main release of the 800xA System. Upgrade of a system including a Language
Package requires an upgrade of the Language Package when it is released.
Refer to the Language Package release notes for information on upgrading a
Language Package to 800xA 5.1.

Precautions
There are third party backup/restore and disk imaging utilities that are useful when
software or data becomes corrupted to the point that the node will no longer
function correctly. A limited number of hardware failures can also be compensated
for by using these utilities. However, it is important to understand the limitations
and ramifications associated with these utilities. In some cases (such as corrupted
data, corrupted software, or hard disk failures) these utilities can be useful while in
other cases (such as replacing a node) these utilities may be of limited use.
It is recommended that a third party backup/restore and/or disk imaging utility be
used to save (and restore if necessary) an image of node hard disks after installation
of third party software and/or after installing all software.
The 800xA System import/export utility can be used to save 800xA System
information one portion at a time. However, the 800xA System backup utility is the
functional equivalent of exporting all 800xA System information at one time. The
critical difference between these utilities is that individually exported portions of
800xA System information can be imported back into the original system or into a
completely different system while backed up 800xA System information can only
be used to restore a specific system on specific nodes. The 800xA System allows for
scheduled 800xA System backups. Refer to System 800xA Maintenance
(3BSE046784*) for information on performing precautionary scheduled 800xA
System backups.

36 3BSE036342-510 C
Section 1 Introduction Windows Hardening

Windows Hardening
Use the stand-alone Windows Config Tool, which is part of the System Installer
package, to perform automated Windows hardening for the 800xA System. Refer to
System 800xA Post Installation (3BUA000156*) for more information.

Firmware Memory Consumption

When upgrading, consideration should be given to memory usage in the controller.
The firmware size has grown slightly, resulting in slightly less free memory for user
applications. However, this is offset by improvements in application and library
handling, and for most projects, the net difference in memory usage is insignificant.
If PM851, PM856, or PM860 controllers with a small amount of free memory in are
being used, refer to the instructions in System 800xA System Guide Technical Data
and Configuration (3BSE041434*) for information on memory requirements.

3BSE036342-510 C 37
Firmware Memory Consumption Section 1 Introduction

38 3BSE036342-510 C
 Section 2 Upgrading Redundant Domain
Controllers

Introduction
There may be some 800xA software on nodes (such as 800xA RNRP on the
Domain Controller node) that does not include Process Portal software. The
Operating System and 800xA software on these nodes also requires upgrading.
This section covers the following:
• Upgrading redundant Domain Controllers from Windows Server 2003 to
Windows Server 2008.
• Replacing server hardware without losing contact with the Active Directory
(AD) and Domain Name Service (DNS).

Prerequisites
The following is required before starting the Domain Controller upgrade procedure:
• Windows Server 2003 support tools must be installed.
• Must be logged on to the schema master as a member of the Enterprise
Admins, Schema Admins, and Domain Admins groups in the forest root
domain.
• Ensure that Windows 2003 Server or later is installed on all Domain
Controllers in the forest.
• ADPREP/forestprep must be run on the schema master.
• Ensure that replication is working throughout the entire forest. Ensure that all
Domain Controllers are up and running and that the schema master has been up
long enough for a complete replication cycle to occur for the Schema partition.

3BSE036342-510 C 39
Upgrading Combined Domain Controllers/Aspect Servers Section 2 Upgrading Redundant Domain

Upgrading Combined Domain Controllers/Aspect Servers

The information in this document is for information purposes only. It is strongly
recommended to contact ABB Product Management before attempting to
perform an online upgrade in 800xA Systems with combined Domain
Controllers/Aspect Servers.
The upgrade order described in this section must be changed when upgrading
800xA Systems with combined Domain Controllers/Aspect Servers. Rather than
upgrading both Domain Controllers before everything else in the 800xA System, the
first Domain Controller must stay a part of the 800xA 5.0 SP2 System until the end
of the upgrade where it will be upgraded with the 800xA 5.0 SP2 Primary Aspect
Server.

Preparation
Prepare for the upgrade by ensuring that the following are available:
• Windows Server 2008 Installation DVD media.
• New server hardware installed with Windows Server 2008.
• System 800xA Installation (3BSE034678*) for Domain Controller installation
procedures.
• IP addresses planned for the new servers.
• Domain name must adhere to Windows conventions for Windows Server 2008
Domain Controllers.
• Firewall disabled on new servers.
• Backups/disk images taken on both Windows Server 2003 Domain Controllers.
• Both Windows Server 2003 Domain Controllers up and running.

Preparing the Active Directory to Accept Windows Server 2008

Perform the following to prepare the existing Windows Server 2003 AD for
accepting Windows Server 2008 before running dcpromo on the secondary Domain
Controller.
• This procedure must be performed on the Domain Controller that holds the
schema master role.

40 3BSE036342-510 C
Section 2 Upgrading Redundant Domain Controllers Preparing the Active Directory to Accept

• Administrative credentials: An account that is a member of all of the following

groups is required to perform this procedure:
– Enterprise Admins.
– Schema Admins.
– Domain Admins for the domain that contains the schema master.
1. Log on to the schema master as a member of the Enterprise Admins, Schema
Admins, and Domain Admins groups in the forest root domain.
Run netdom query fsmo on any Domain Controller to ensure which Domain
Controller hosts the schema master role. Make a record of who has the different
roles.
2. Insert the Windows Server 2008 DVD into the CD or DVD drive.
a. Select:
Start > All Programs > Accessories
b. Right-click Command Prompt.
c. Select Run as Administrator.
d. Select The following user in the dialog box that appears.
e. Enter the administrator user name and password and click OK.
f. Type the following command, and then press ENTER:
CD or DVD drive letter:\sources\adprep\adprep
/forestprep C
g. A warning will appear stating that Window 2000 Server SP4 or later must
be running. Type C and press ENTER.
3. Allow the operation to complete (this can take several minutes to several
hours).
4. Allow the changes to replicate throughout the forest before preparing any
domains for a Windows Server 2008 Domain Controller.Waite 15 to 30
minutes, and then check the Windows Event Viewer for any related error or
warning messages.

3BSE036342-510 C 41
Preparing a Domain for Windows Server 2008 Section 2 Upgrading Redundant Domain Controllers

Preparing a Domain for Windows Server 2008

Perform the following to identify the domain infrastructure operations master (also
known as flexible single master operations or FSMO) role holder.
• This procedure must be performed on the Domain Controller that holds the
schema master role.
• Administrative credentials: An account that is a member of the Domain
Admins group is required to perform this procedure. Membership in the
Enterprise Admins group is not sufficient to perform this procedure.
1. Login as a member of the Domain Admins group to the Domain Controller
node that holds the schema master role.
2. Step f can only be run with the Domain Controller in Native Mode. Select:
Start > All Programs > Administrative Tools > Active Directory
Domains and Trusts
Right-click the domain name and select Raise Domain Functional
Level... from the menu
3. Select Windows Server 2003 in the Select an available domain functional
level drop-down list box.
4. Click OK.
5. Insert the Windows Server 2008 DVD into the CD or DVD drive.
a. Select:
Start > All Programs > Accessories
b. Right-click Command Prompt.
c. Select Run as Administrator.
d. Select The following user in the dialog box that appears.
e. Enter the administrator user name and password and click OK.
f. Type the following command, and then press ENTER:
CD or DVD drive letter:\sources\adprep\adprep /domainprep /gpprep
6. Allow the operation to complete (this can take several minutes).

42 3BSE036342-510 C
Section 2 Upgrading Redundant Domain Controllers Preparing a Forest for a Read-Only Domain

7. Allow the changes to replicate throughout the forest before installing a

Windows Server 2008 Domain Controller.

Preparing a Forest for a Read-Only Domain Controller

Perform the following to prepare a forest for a Read-Only Domain Controller
(RODC).
1. Login to any Domain Controller in the forest as a member of the Enterprise
Admins group.
2. Insert the Windows Server 2008 DVD into the CD or DVD drive.
a. Select:
Start > All Programs > Accessories
b. Right-click Command Prompt.
c. Select Run as Administrator.
d. Type the following command, and then press ENTER:
CD or DVD drive letter:\sources\adprep\adprep
/rodcprep
3. Allow the operation to complete.
4. Allow the changes to replicate throughout the forest before removing the
redundant Domain Controller.

Removing the Redundant Domain Controller

A redundant Windows Server 2003 Domain Controller can be removed using the
Windows interface.
Perform the following to remove the redundant Windows Server 2003 Domain
Controller by using the Windows interface.
• This procedure must be performed on the redundant Windows Server 2003
Domain Controller.
• Administrative credentials: An account that is a member of following group is
required to perform this procedure:
– Domain Admins.

3BSE036342-510 C 43
Removing the Redundant Domain Controller Section 2 Upgrading Redundant Domain Controllers

1. Verify that both Domain Controllers are global catalog servers.

a. Start AD Sites and Services.
b. Navigate to NTDS Settings of one Domain Controller in the left pane.
c. Right-click NTDS Settings and select Properties from the context
menu to open the NTDS Settings Properties dialog box.
d. Verify that the Global Catalog check box is selected under the General
tab.
e. Repeat for the other Domain Controller.
2. If the Domain Controller is a global catalog server, a message box appears
warning about the effect of removing a global catalog server from the
environment. Click OK to continue.
3. Select:
Start > Run
4. Enter dcpromo in the Run dialog box and click OK.
5. Click Next in the Welcome to the Active Directory Installation Wizard dialog
box.
6. Make no selection in the Remove Active Directory dialog box and click Next.
7. Type and confirm a secure password for the local Administrator account in the
Administrator Password dialog box and click Next.
8. Click Next in the Summary dialog box.
9. Click Finish in the Completing the Active Directory Installation Wizard dialog
box.
10. Click Restart Now in the Active Directory Installation Wizard dialog box.
11. Remove the server from the domain.
12. Select:
Start > All Programs > Administrative Tools
and launch the Manage Your Server Wizard.
13. Remove the DNS Role.

44 3BSE036342-510 C
Section 2 Upgrading Redundant Domain Controllers Installing an Additional Windows Server 2008

a. Click Add or remove a role in the Manage Your Server Wizard.

b. Read and follow the steps in the Preliminary Steps dialog box and click
Next.
c. Select DNS server in the Server Role dialog box and click Next.
d. Select the Remove the DNS server role check box in the Role Removal
Confirmation dialog box and click Next.
e. Click Finish in the DNS Server Role Removed dialog box.
14. Move to the remaining Windows Server 2003 Domain Controller node, select:
Start > All Programs > Administrative Tools
and launch the Manage Your Server Wizard.
a. Verify that the redundant Domain Controller node has been removed from
Active Directory Users and Computers. If it has not, remove it manually.
b. Verify that the redundant Domain Controller node has been removed from
Active Directory Sites and Services. If it has not, remove it manually.
c. Verify that the redundant Domain Controller node has been removed from
DNS. If it has not, clean all the traces in the Name Server Tab for both
Forward Lookup and Reverse Lookup Zones.

Installing an Additional Windows Server 2008 Domain

Controller
Perform the following to install an additional Windows Server 2008 Domain
Controller in an existing domain using the Windows interface.
• This procedure must be performed on the additional Windows Server 2008
Domain Controller.
• Login as a local administrator.
• Administrative credentials: Check that there is an account available that is a
member of Domain Admins in the domain in which the additional Domain
Controller is being installed. It is required to perform Step 14 of this procedure:
1. Open Windows Control Panel.

3BSE036342-510 C 45
Installing an Additional Windows Server 2008 Domain Controller Section 2 Upgrading Redundant

2. Double-click Administrative Tools.

3. Double-click Server Manager to launch the Server Manager.
4. Click Add Roles in the Roles Summary.
5. Review the information in the Before You Begin dialog box and click Next.
6. Click the Active Directory Domain Services check box in the Select Server
Roles dialog box and click Next.
7. Review the information in the Active Directory Domain Services dialog box
and click Next.
8. Click Install in the Confirm Installation Selections dialog box.
9. In the Installation Results dialog box click Close this Wizard and launch the
Active Directory Domain Services Installation Wizard (dcpromo.exe).
Ensure that all networks are disabled except networks that are used for the 800xA
System (Plant Network and/or Control Network).
10. Click Next in the Welcome to the Active Directory Domain Services
Installation Wizard dialog box.
11. Review the warning about the default security settings for Windows Server
2008 Domain Controllers in the Operating System Compatibility dialog box
and click Next.
12. Click Existing Forest and Add a Domain Controller to an Existing Domain
in the Choose a Deployment Configuration dialog box and click Next.
13. Type the name of any existing domain in the forest where it is planned to install
the additional Domain Controller in the Network Credentials dialog box.
14. Click My Current Logged On Credentials or Alternate Credentials under
Specify the Account Credentials to use to Perform the Installation and click
Set.
15. Provide the user name and password for an account that can install the
additional Domain Controller in the Windows Security dialog box.
The installer must be a member of the Domain Admins group to install an
additional Domain Controller.
16. Click Next when the credentials are provided.

46 3BSE036342-510 C
Section 2 Upgrading Redundant Domain Controllers Installing an Additional Windows Server 2008

17. Select the domain of the additional Domain Controller in the Select a Domain
dialog box and click Next.
18. Select a site from the list or select the option to install the Domain Controller in
the site that corresponds to its IP address in the Select a Site dialog box and
click Next.
19. Make the following selections in the Additional Domain Controller Options
dialog box and click Next.
– DNS Server: This option is selected by default so that the Domain
Controller can function as a Domain Name System (DNS) server.
– Global Catalog: This option is selected by default. It adds the global
catalog, read-only directory partitions to the Domain Controller, and
enables global catalog search functionality.
– Read-only Domain Controller: This option is not selected by default and
is not possible to select.
ABB recommends disabling the IPv6 protocol.

If static IPv4 and IPv6 addresses are not assigned to the network adapters, a
warning message box might appear advising the setting of static addresses for
both of these protocols before continuing. If static IPv4 address have been
assigned to the network adapter and the organization does not use IPv6, this
message can be ignored by clicking Yes, the computer will use a dynamically
assigned IP address (not recommended).
A message box may appear that indicates that a DNS delegation for the DNS
server could not be created, and that a DNS delegation to the DNS server to
ensure reliable name resolution should be manually created may appear if the
option to install a DNS server was selected. It is not required to create the DNS
delegation if the additional Domain Controller is being installed in either the
forest root domain or a tree root domain. Click Yes and disregard the message if
this is the case.
20. Type or browse to the volume and folder locations for the following in the
Location for Database, Log Files, and SYSVOL dialog box and click Next.
– Database file.

3BSE036342-510 C 47
Transferring the FSMO Roles to the Secondary Domain Controller Section 2 Upgrading Redundant

– Directory service log files.

– System volume (SYSVOL) files.
Windows Server Backup backs up the directory service by volume. For backup
and recovery efficiency, store these files on separate volumes that do not contain
applications or other nondirectory files.
21. Type and confirm the restore mode password in the Directory Services Restore
Mode Administrator Password dialog box and click Next. This password must
be used to start AD DS in Directory Service Restore Mode (DSRM) for tasks
that must be performed offline.
22. Review the selections in the Summary dialog box. Click Back to change any
selections. Click Next when the selections are accurate to install.
To save the selected settings to an answer file that can be used to automate
subsequent AD DS operations, click Export Settings, type the name for the
answer file, and click Save.
23. Click Next when the selections are accurate to install AD DS.
24. Click Finish in the Completing the Active Directory Domain Services
Installation Wizard dialog box.
Select either the Reboot on Completion check box to have the server restart
automatically, or restart the server to complete the AD DS installation when
prompted.

Transferring the FSMO Roles to the Secondary Domain

Controller
Perform the following to transfer the FSMO roles to the Secondary Domain
Controller:
• Transferring the Schema Master Role on page 49.
• Transferring the Domain Naming Master Role on page 50.
• Transferring the RID Master, PDC Emulator, and Infrastructure Master Roles
on page 51.

48 3BSE036342-510 C
Section 2 Upgrading Redundant Domain Controllers Transferring the Schema Master Role

Transferring the Schema Master Role

Perform the following to transfer the Schema Master Role.
• This procedure must be performed on the Windows Server 2003 Domain
Controller that is the Role Holder.
To transfer the Schema Master Role it is necessary to:
• Register the Schmmgmt.dll.
• Run the Active Directory Schema Master snap-in.

Registering Schmmgmt.dll
Perform the following to register Schmmgmt.dll.
1. Select:
Start > Run
2. Enter regsvr32 schmmgmt.dll in the Run dialog box and click OK.
3. Click OK when the message indicating that the operation succeeded appears.

Running the Active Directory Schema Master Snap-in

Perform the following to run the Active Directory Schema Master Snap-in.
1. Select:
Start > Run
2. Enter mmc in the Run dialog box and click OK.
3. Click Add/Remove Snap-in on the File menu.
4. Click Add.
5. Click Active Directory Schema.
6. Click Add.
7. Click Close.
8. Click OK.

3BSE036342-510 C 49
Transferring the Domain Naming Master Role Section 2 Upgrading Redundant Domain Controllers

9. Right-click Active Directory Schema in the console tree and select

Change Domain Controller to launch the Change Domain Controller dialog
box (Figure 1).

Figure 1. Change Domain Controller Dialog Box

10. Select Specify Name.

11. Type the name of the Domain Controller that will be the new role holder and
click OK.
12. Right-click Active Directory Schema in the console tree and select
Operations Master.
13. Click Change.
14. Click Yes to confirm the transferring of the role.
15. Accept the question that follows and click Close.

Transferring the Domain Naming Master Role

Perform the following to transfer the Domain Naming Master Role.
1. Open Active Directory Domains and Trusts from Administrative Tools.
Perform Step 2 and Step 3 only if not on the Domain Controller to which the role
will be transferred.

50 3BSE036342-510 C
Section 2 Upgrading Redundant Domain Controllers Transferring the RID Master, PDC Emulator,

2. Right-click Active Directory Domains and Trusts and select Connect to

Domain Controller to launch the Connect to Domain Controller dialog box
(Figure 2).

Figure 2. Connect to Domain Controller Dialog Box

3. Select an available Domain Controller list, click the Domain Controller that
will be the new role holder, and click OK.
4. Right-click Active Directory Domains and Trusts in the console tree
and select Operations Master.
5. Click Change.
6. Click Yes to confirm the transferring of the role.
7. Accept the question that follows and click Close.

Transferring the RID Master, PDC Emulator, and Infrastructure Master Roles
Perform the following to transfer the RID Master, PDC Emulator, and Infrastructure
Master Roles.
1. Open Active Directory Users and Computers from Administrative Tools.
Perform Step 2 and Step 3 only if not on the Domain Controller to which the role
will be transferred.

3BSE036342-510 C 51
Transferring the RID Master, PDC Emulator, and Infrastructure Master Roles Section 2 Upgrading

2. Right-click Active Directory Users and Computers and select Connect to

Domain Controller.
3. Perform one of the following:
– Type the name of the Domain Controller that will be the new role holder in
the Enter the Name of Another Domain Controller dialog box and click
OK.
-or-
– Select an available Domain Controller list, click the Domain Controller
that will be the new role holder, and click OK.
4. Right-click Active Directory Users and Computers in the console
tree.
5. Point to All Tasks.
6. Click Operations Masters to launch the Operations Masters dialog box
(Figure 3).

Figure 3. Operations Master Dialog Box

52 3BSE036342-510 C
Section 2 Upgrading Redundant Domain Controllers Removing the Remaining Windows Server

7. Click the appropriate tab for the master role to transfer (RID Master, PDC
Emulator, or Infrastructure), and then click Change.
8. Click OK to confirm transferring of the role and click Close.

Removing the Remaining Windows Server 2003 Domain

Controller
The remaining Windows Server 2003 Domain Controller can be removed using the
Windows interface.
Perform the following to remove the remaining Windows Server 2003 Domain
Controller by using the Windows interface.
• This procedure must be performed on the remaining Windows Server 2003
Domain Controller.
• Administrative credentials: An account that is a member of following group is
required to perform this procedure:
– Domain Admins.
1. Verify that both Domain Controllers are global catalog servers.
a. Start AD Sites and Services.
b. Navigate to NTDS Settings of one Domain Controller in the left pane.
c. Right-click NTDS Settings and select Properties from the context
menu to open the NTDS Settings Properties dialog box.
d. Verify that the Global Catalog check box is selected under the General
tab.
e. Repeat for the other Domain Controller.
2. If the Domain Controller is a global catalog server, a message box appears
warning about the effect of removing a global catalog server from the
environment. Click OK to continue.
3. Select:
Start > Run

3BSE036342-510 C 53
Removing the Remaining Windows Server 2003 Domain Controller Section 2 Upgrading

4. Enter dcpromo in the Run dialog box and click OK.

5. Click Next in the Welcome to the Active Directory Installation Wizard dialog
box.
6. Make no selection in the Remove Active Directory dialog box and click Next.
7. Type and confirm a secure password for the local Administrator account in the
Administrator Password dialog box and click Next.
8. Click Next in the Summary dialog box.
9. Click Finish in the Completing the Active Directory Installation Wizard dialog
box.
10. Click Restart Now in the Active Directory Installation Wizard dialog box.
11. Remove the server from the domain.
12. Select:
Start > All Programs > Administrative Tools
and launch the Manage Your Server Wizard.
13. Remove the DNS Role.
a. Click Add or remove a role in the Manage Your Server Wizard.
b. Read and follow the steps in the Preliminary Steps dialog box and click
Next.
c. Select DNS server in the Server Role dialog box and click Next.
d. Select the Remove the DNS server role check box in the Role Removal
Confirmation dialog box and click Next.
e. Click Finish in the DNS Server Role Removed dialog box.
14. Move to the Windows Server 2008 Domain Controller node, select:
Start > All Programs > Administrative Tools
and launch the Server Manage Wizard.
a. Verify that the remaining Windows Server 2003 Domain Controller node
has been removed from Active Directory Users and Computers. If it has
not, remove it manually.

54 3BSE036342-510 C
Section 2 Upgrading Redundant Domain Controllers Installing an Additional Windows Server 2008

b. Verify that the remaining Windows Server 2003 Domain Controller node
has been removed from Active Directory Sites and Services. If it has not,
remove it manually.
c. Verify that the remaining Windows Server 2003 Domain Controller node
has been removed from DNS. If it has not, clean all the traces in the Name
Server Tab for both Forward Lookup and Reverse Lookup Zones.

Installing an Additional Windows Server 2008 Domain

Controller
Perform the following to install an additional Windows Server 2008 Domain
Controller in an existing domain using the Windows interface.
• This procedure must be performed on the additional Windows Server 2008
Domain Controller.
• Login as a local administrator.
• Administrative credentials: Check that there is an account available that is a
member of following group as it is required to perform Step 14 of this
procedure:
– Domain Admins in the domain in which the additional Domain Controller
is being installed.
1. Open Windows Control Panel.
2. Double-click Administrative Tools.
3. Double-click Server Manager to launch the Server Manager.
4. Click Add Roles in the Roles Summary.
5. Review the information in the Before You Begin dialog box and click Next.
6. Click the Active Directory Domain Services check box in the Select Server
Roles dialog box and click Next.
7. Review the information in the Active Directory Domain Services dialog box
and click Next.
8. Click Install in the Confirm Installation Selections dialog box.

3BSE036342-510 C 55
Installing an Additional Windows Server 2008 Domain Controller Section 2 Upgrading Redundant

9. In the Installation Results dialog box click Close this Wizard and launch the
Active Directory Domain Services Installation Wizard (dcpromo.exe).
Ensure that all networks are disabled except networks that are used for the 800xA
System (Plant Network and/or Control Network).
10. Click Next in the Welcome to the Active Directory Domain Services
Installation Wizard dialog box.
11. Review the warning about the default security settings for Windows Server
2008 Domain Controllers in the Operating System Compatibility dialog box
and click Next.
12. Click Existing Forest and Add a Domain Controller to an Existing Domain
in the Choose a Deployment Configuration dialog box and click Next.
13. Type the name of any existing domain in the forest where it is planned to install
the additional Domain Controller in the Network Credentials dialog box.
14. Click My Current Logged On Credentials or Alternate Credentials under
Specify the Account Credentials to use to Perform the Installation and click
Set.
15. Provide the user name and password for an account that can install the
additional Domain Controller in the Windows Security dialog box.
The installer must be a member of the Enterprise Admins group or the Domain
Admins group to install an additional Domain Controller.
16. Click Next when the credentials are provided.
17. Select the domain of the additional Domain Controller in the Select a Domain
dialog box and click Next.
18. Select a site from the list or select the option to install the Domain Controller in
the site that corresponds to its IP address in the Select a Site dialog box and
click Next.
19. Make the following selections in the Additional Domain Controller Options
dialog box and click Next.
– DNS Server: This option is selected by default so that the Domain
Controller can function as a Domain Name System (DNS) server. Clear

56 3BSE036342-510 C
Section 2 Upgrading Redundant Domain Controllers Installing an Additional Windows Server 2008

the option if it is not desired to have the Domain Controller be a DNS

server.
– Global Catalog: This option is unselected by default. If selected, it adds
the global catalog, read-only directory partitions to the Domain Controller,
and enables global catalog search functionality.
– Read-only Domain Controller: This option is not selected by default and
is not possible to select.
ABB recommends disabling the IPv6 protocol.

If static IPv4 and IPv6 addresses are not assigned to the network adapters, a
warning message box might appear advising the setting of static addresses for
both of these protocols before continuing. If static IPv4 address have been
assigned to the network adapter and the organization does not use IPv6, this
message can be ignored by clicking Yes, the computer will use a dynamically
assigned IP address (not recommended).
A message box may appear that indicates that a DNS delegation for the DNS
server could not be created, and that a DNS delegation to the DNS server to
ensure reliable name resolution should be manually created may appear if the
option to install a DNS server was selected. It is not required to create the DNS
delegation if the additional Domain Controller is being installed in either the
forest root domain or a tree root domain. Click Yes and disregard the message if
this is the case.
20. Type or browse to the volume and folder locations for the following in the
Location for Database, Log Files, and SYSVOL dialog box and click Next.
– Database file.
– Directory service log files.
– System volume (SYSVOL) files.
Windows Server Backup backs up the directory service by volume. For backup
and recovery efficiency, store these files on separate volumes that do not contain
applications or other nondirectory files.
21. Type and confirm the restore mode password in the Directory Services Restore
Mode Administrator Password dialog box and click Next. This password must

3BSE036342-510 C 57
Required 800xA Software Section 2 Upgrading Redundant Domain Controllers

be used to start AD DS in Directory Service Restore Mode (DSRM) for tasks

that must be performed offline.
22. Review the selections in the Summary dialog box. Click Back to change any
selections. Click Next when the selections are accurate to install.
To save the selected settings to an answer file that can be used to automate
subsequent AD DS operations, click Export Settings, type the name for the
answer file, and click Save.
23. Click Next when the selections are accurate to install AD DS.
24. Click Finish in the Completing the Active Directory Domain Services
Installation Wizard dialog box.
Select either the Reboot on Completion check box to have the server restart
automatically, or restart the server to complete the AD DS installation when
prompted.

Required 800xA Software

The only 800xA software installed on a separate Domain Controller node is:
• Diagnostics Collection Tool.
• RNRP.
• 800xA Common Third Party Install Tool.

58 3BSE036342-510 C
 Section 3 Upgrading 800xA 5.0 SP2 to 800xA
5.1 Online

Introduction
Online Upgrade makes it possible to upgrade an existing 800xA System (800xA 5.0
SP2 or later) without a process shutdown. Plant operations are not disturbed while
upgrading server and client software, including OCS connectivity services, and
AC 800M Controllers (processor units and communication interfaces (CI)).
The 800xA System being upgraded must have redundant Aspect and Connectivity
Servers, and redundant AC 800M Controllers consisting of two redundant
processing units connected to I/O modules either directly to the modulebus or via
various CI modules. The client and server level can be upgraded without upgrading
the controllers.
Redundancy is not supported for the Batch Management and IM combined node
type.
The OCS connectivity services are possible to upgrade online. The OCS
controller level is upgraded following the rules defined for the OCS system being
upgraded.
This instruction addresses only the client and server level software. It does not
provide detailed instruction for upgrading the controller level; however, a high
level discussion about the controller level appears in Appendix H, Online
Upgrade Controller Level.
800xA Systems without redundant Aspect and Connectivity Servers require a
process shutdown (refer to Section 4, Upgrading 800xA 5.0 SP2 to 800xA 5.1
Offline).

3BSE036342-510 C 59
Control Builder M Compatibility Issues Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

Control Builder M Compatibility Issues

Refer to the compatibility issues detailed in Appendix B, Control Builder M
Compatibility Issues before beginning the upgrade.

Considerations
The following considerations must be taken into account before performing the
upgrade.
• Unless otherwise indicated, the person performing this upgrade must use the
same user account that was used during the installation of the 800xA System
software.
• To guarantee the functionality of the upgraded system, follow these
instructions carefully and perform them in a well defined order.
• It is recommended that a disk image be taken of all disks on each node before
beginning and after completing the upgrade.
• Backing up the aspect directory (800xA System Backup), reports, history data,
graphics, and other application data is required before performing the upgrade.
• Take an inventory of all software on all nodes in the 800xA System before
performing the upgrade.

Upgrade Flow
This section is organized so that the instructions are presented in the proper upgrade
order. Do not skip any steps that pertain to 800xA software being used in the current
or upgraded system. Refer to Planning for the Upgrade on page 33 for additional
information and ideas on how to streamline the upgrade process.
All paths require, after backup and before restore, installing the 800xA System
software and creating the system as if it were a new installation.

60 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Central Licensing System

Central Licensing System

Order the 800xA licenses required for the current system version and revision.
The 800xA 5.0 SP2 licenses will not work.

Online Upgrade
The following is the online upgrade procedure. The remainder of this section
provides detailed information and procedures and they will be referred to in this
procedure.
1. Document all Windows settings including the domain, DNS, policies, users,
etc.
2. Refer to the Diagnostics Collection Tool section in System 800xA Tools
(2PAA101888*) and run the Software Analyzer from the Primary Aspect
Server in the 800xA 5.0 SP2 System. This allows for an analysis of the
software installed on the different nodes in the 800xA System with an
opportunity to correct errors in the 800xA 5.0 SP2 System before upgrading.
This is especially helpful when using the System Installer to generate setup
packages based on the 800xA 5.0 SP2 System. If there is missing or incorrect
software in that version, the System Installer will duplicate that installation in
the 800xA 5.1 System.
3. Refer to Appendix C, Consistency Check and perform the necessary
consistency checks.
Perform a consistency check before performing the 800xA System backup.
Failure to do so could result in problems when restoring the system after the
upgrade.
4. Refer to Appendix D, Recording the Number of Aspects and Objects and
record the number of aspects and objects in the system before performing the
800xA System Backup.
5. It is important to create backups of node hard disks and the 800xA System
before starting the upgrade procedures. Valid backups ensure that the system
can be restored if necessary.
a. It is recommended that a third party backup/restore and/or disk imaging
utility be used to save (and restore if necessary) all disks on each node
before starting the upgrade procedures.

3BSE036342-510 C 61
Online Upgrade Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

b. This step only applies to installations with IEC 61850 Connect installed
that use a user-defined Graphic Library for applications. Ensure that
inheritance is enabled for all aspects in that library and an upload
operation is performed before taking the 800xA System backup.
c. This step only applies to installations using the Application Scheduler
and/or Calculations Services:
– Open a Plant Explorer Workplacet.
– Use the Structure Selector to open the Service Structure.
– Select the Scheduling Service Object (Calculations Service Object).
– Select the Service Definition aspect.
– Click the Configuration tab.
– Clear the Enabled check box and click Apply.
– The Schedules/Calculations will have to be manually enabled following
the upgrade.
d. Perform the 800xA System backup from the Maintenance Structure
(Aspect Directory backup type).
Avoid engineering or any other changes especially to the Aspect system during
the 800xA Backup process.
The 800xA Backup/Restore function makes it possible to make an online
backup of the Aspect Directory on the Primary Aspect Server in the
800xA 5.0 SP2 System and restore it to the new Primary Aspect Server in
the 800xA 5.1 System.
A full backup stores all aspect objects and aspect data (application data) in
the Aspect Directory.
Verify the Batch Management Servers are operating normally before and during
800xA System backups of systems containing Batch Management nodes. This
will ensure the backup of all batch data.
All system extensions that are part of the system must be installed and
loaded on the node where the backup will be taken (usually the primary
Aspect Server node).

62 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Online Upgrade

When backing up a system with Environments, both the Production and

Engineering Environments will be included in the backup. Only the
current version of each aspect will be included in the backup. This means
that all version history will be removed.
It is only possible to perform the 800xA System backup from the Production
Environment.
– Open a Plant Explorer Workplace.
– Use the Structure Selector to open the Maintenance Structure.
– Create a Full Backup Definition object.
– Configure the Scope and Storage tabs.
– Check the disk space and path in the Storage tab. A large configuration
could require a minimum of five gigabytes of free space.
– Start the backup process.

– Refer to the How to Make a Full Backup topic in System 800xA

Maintenance (3BSE046784*) for more detailed information on performing
the 800xA System Backup.
6. Place the process in a low level of production where the likelihood of process
upsets is minimized.
7. If Batch Management is installed and running, all batches must be in the
complete state (no running batches or active phases).
8. Refer to Pre-Upgrade Procedures on page 79 and perform the pre-upgrade
procedures that are applicable to the installed system.
Do not make any configuration changes such as modifying displays, modifying or
deleting objects, etc. as these changes to the 800xA 5.0 SP2 System will be lost
from this point forward.

3BSE036342-510 C 63
Redundant Aspect Server Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

Do not perform the pre-upgrade procedures for Information Management at this

point in the upgrade process. This must be performed immediately before
upgrading the IM Server to allow the history and event data to be stored, without
losing data, in the history and event storage in the Connectivity Servers while
upgrading the IM Server. History and event storage will not be able to collect all
of the data if the time period between disconnecting the IM Server from the
800xA 5.0 SP2 System and reconnecting it to the 800xA 5.1 System is too long.

Redundant Aspect Server

1. Remove a redundant Aspect Server from the 800xA 5.0 SP2 System via the
Remove Server feature in the Configuration Wizard. This server can be a stand-
alone Aspect Server or it can be combined with a redundant Connectivity
Server. If working in a domain this server needs to be removed from the
Domain Controller. When this server is upgraded it will become the Primary
Aspect Server in the 800xA 5.1 System.
The other redundant Aspect Server, if running 2oo3 redundancy, will be removed
from the 800xA 5.0 SP2 System later.
2. Reformat the hard drive.
3. Install the new operating system defined for the 800xA 5.1 System. Click
Advanced when installing Windows 7 or Windows Server 2008. This is
required to delete the existing partition and recreate a new one. Failure to
perform this step will leave old data on the hard drive.
4. Refer to Section 2 - Prerequisites in:
– Manual Upgrades - System 800xA Installation (3BSE034678*).
– Automated Upgrades using System Installer - System 800xA Automated
Installation (3BSE034679*).
and perform all procedures relating to operating system settings, Windows
service packs, miscellaneous Windows components installation, other third
party software, group policy, 800xA Service User privileges, and Windows
updates and hot fixes.
5. Refer to System 800xA Installation (3BSE034678*) and install the 800xA 5.1
Central Licensing System Server software and install the license file, as this

64 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Redundant Aspect Server

will be the Primary Aspect Server in the 800xA 5.1 System. This step is not
necessary if performing an automated upgrade using System Installer.
6. Refer to System 800xA Installation (3BSE034678*) and install all 800xA 5.1
System software per the software inventory taken earlier. This step is not
necessary if performing an automated upgrade using System Installer.
7. Refer to Requirements for VB Graphics Extension Software on page 97 to
install Visual BASIC 6.0 with SP6 and the VB Graphics extensions if required.
8. Perform the system update to the latest release:
• It is recommended to use the System Update Tool (SUT) to perform the update
as described in System 800xA System Update Tool (2PAA106938*). Refer to
Appendix G, Update to 800xA 5.1 Rev A to perform the update manually.
OR
Feature Pack Functionality

• Use the System Feature Pack Update Tool (FUT) to perform the update. Refer
to the System 800xA 5.1 System Feature Pack Update Tool (2PAA107435*) for
user instructions.

9. Perform the 800xA System Restore.

Refer to Requirements for VB Graphics Extension Software on page 97 before
performing the 800xA System Restore.

Perform this procedure only on the first Aspect Server connected to the 800xA
5.1 System.

The User Account that is used for 800xA System restore via the Configuration
Wizard must be a member of the following groups:
• IndustrialITUser.
• IndustrialITAdmin.
• Local Administrators.
The backup/restore utility supports the restoring of 800xA system information.
The following steps outline the 800xA system restore procedure.
Refer to System 800xA Maintenance (3BSE046784*) for more information on
restoring the system.

3BSE036342-510 C 65
Redundant Aspect Server Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

10. Start the restore procedure.

a. Select:
Start > All Programs > ABB Industrial IT 800xA > System >
Configuration Wizard
b. The Select Type of Configuration dialog box appears. Select Restore
System and click Next.
c. When a dialog box appears with the Generate new system id check box
available, select the check box. This is necessary because during online
upgrade there will be two systems in one network.
d. Enter a system name and click Next.
e. Change the first Aspect Server to the last Aspect Server (this is now going
to be the Primary Aspect Server) in the Node Configuration dialog box
under the Primary nodes frame.
f. Change the first Aspect Server to last Aspect Server in the Primary nodes
frame and click Next.
11. Check for messages in the log file (select the View Log check box in the
Configuration Wizard). Refer to Appendix A, Warning and Error Messages to
resolve any received warning or error messages.
Restart the node when advised during the restore procedure.

12. Check the CPU load in the node. The System Message service may generate a
high load (>90%). If this continues for longer than approximately 10 minutes,
restart the service.
If a message appears stating that a full deploy of the Generic Control Network is
needed, click OK.
13. Refer to Appendix D, Recording the Number of Aspects and Objects and
record the number of aspects and objects in the system. Compare these values
to those recorded when the system was backed up.
14. Verify the affinity settings to ensure best system performance. Refer to System
800xA Post Installation (3BUA000156*) for more information on how to
configure affinity.

66 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Redundant Aspect Server

15. Refer to Appendix C, Consistency Check and perform the necessary

consistency checks.
16. Load the VB Graphics Extensions.
Perform this procedure only if the restored system makes use of VB graphics.

a. Refer to Table 2 for a list of VB Graphics extensions available to be

loaded.

Table 2. VB Graphics Extensions

Directory Software
800xA Connectivities AC 800M Connect VB Graphics Extension
ABB 800xA for Advant Master VB Graphics Extension
5.1.0/0
ABB 800xA for Harmony VB Graphics Extension 5.1.00
ABB 800xA for IEC61850 VB Graphics Extension
ABB 800xA for MOD 300 VB Graphics Extension
ABB 800xA for Safeguard VB Graphics Extension 5.1.0/0
ABB PLC Connect VB Graphics Extension 5.1.00
Asset Optimization ABB Asset Optimization VB Graphics Extension 5.1
ABB PC, Network and Software Monitoring VB Graphics
Extension
Batch Management Batch VB Graphics Extension
Batch Advanced Templates VB Graphics Extension
Device Management & Fieldbuses ABB Device Management FOUNDATION Fieldbus VB
Graphics Extension

b. Start the Configuration Wizard from the primary Aspect Server node.
Select:
Start > All Programs > ABB Industrial IT 800xA > System >
Configuration Wizard

3BSE036342-510 C 67
Redundant Aspect Server Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

c. Open the System Extension Load dialog box by going to:

System Administration > Select System > System Extension Load
d. A view appears with the available VB Graphics extensions listed in the left
pane. Select the system extension to load in the list in the left pane and
move it to the list in the right pane by clicking >. To move all the system
extensions from the left pane to the right pane, click >>.
e. The red cross, green check mark, and warning icons indicate the status of
the dependency evaluation.
– The green check mark indicates that the system extension must be loaded
first.
– The red cross icon indicates that the system extension can not be loaded
until the one with the green check mark icon is loaded.
– The warning icon indicates that the system extension can be loaded, but
that there is additional information available in the Description frame in
the lower part of the dialog box. The additional information can, for
example, be that the system extension contains aspect types that are not
environment aware.
f. If the list in the right pane contains more than one system extension, click
Press header to autosort to sort the system extension load order with
regard to dependencies.
g. All system extensions in the right pane should be marked with the green
check mark or the warning icon.
h. Click Next and the Apply Settings dialog box appears.
i. Click Finish to load all system extensions.

68 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Redundant 800xA for Harmony and

j. A progress dialog box is shown during the load. Click View Log to view
log messages during load.
The load is aborted if:
• The user clicks Abort.
• An error occurs; for example, if the Configuration Wizard fails to load a file
into the system.
An aborted system extension load can be resumed from the System Extension
Maintenance dialog box.
k. When the load operation is finished, click Finished and view the
Configuration Wizard log to verify that no errors occurred during the load.
l. Close the Configuration Wizard.
m. Refer to Post Upgrade Procedures on page 101 and perform the applicable
post upgrade procedures for the upgraded server.
Operation and monitoring of the plant are only possible from clients in the
800xA 5.0 SP2 System at this point in the upgrade process.

Redundant 800xA for Harmony and 800xA for AC 870P/Melody Servers

Perform this procedure only if 800xA for Harmony or 800xA for
AC 870P/Melody are installed in the 800xA System.
1. Remove a redundant 800xA for Harmony Configuration Server, 800xA for
Harmony Configuration Server with Connectivity Server, or 800xA for AC
870P/Melody Configuration Server via the Remove Server feature in the
Configuration Wizard. If working in a domain this server needs to be removed
from the Domain Controller.
2. Reformat the hard drive.
3. Install the new operating system defined for the 800xA 5.1 System. Click
Advanced when installing Windows Server 2008. This is required to delete the
existing partition and recreate a new one. Failure to perform this step will leave
old data on the hard drive.
4. Refer to Section 2 - Prerequisites in:
– Manual Upgrades - System 800xA Installation (3BSE034678*).

3BSE036342-510 C 69
Redundant Connectivity Servers Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

– Automated Upgrades using System Installer - System 800xA Automated

Installation (3BSE034679*).
and perform all procedures relating to operating system settings, Windows
service packs, miscellaneous Windows components installation, other third
party software, group policy, 800xA Service User privileges, and Windows
updates and hot fixes.
5. Refer to System 800xA Installation (3BSE034678*) and install all 800xA 5.1
System software per the software inventory taken earlier. This step is not
necessary if performing an automated upgrade using System Installer.
6. Refer to Requirements for VB Graphics Extension Software on page 97 to
install Visual BASIC 6.0 with SP6 and the VB Graphics extensions if required.
7. Point the Central Licensing Client to the new 800xA 5.1 Central Licensing
Server.
8. Connect the server to the upgrade 800xA 5.1 System via the Connect Node
feature in the Configuration Wizard.
9. Refer to Post Upgrade Procedures on page 101 and perform the applicable post
upgrade procedures for the upgraded server.
10. Repeat this procedure for every redundant 800xA for Harmony Configuration
Server, 800xA for Harmony Configuration Server with Connectivity Server, or
800xA for AC 870P/Melody Configuration Server.
Upgrade the servers one-by-one in order to keep redundancy of the system as
long as possible.
Operation and monitoring of the plant are only possible from clients in the 800xA
5.0 SP2 System at this point in the upgrade process.

Redundant Connectivity Servers

1. Remove a redundant Connectivity Server from the 800xA 5.0 SP2 System via
the Remove Server feature in the Configuration Wizard. If working in a domain
this server needs to be removed from the Domain Controller.
2. Reformat the hard drive.
3. Install the new operating system defined for the 800xA 5.1 System. Click
Advanced when installing Windows 7 or Windows Server 2008. This is

70 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Redundant Connectivity Servers

required to delete the existing partition and recreate a new one. Failure to
perform this step will leave old data on the hard drive.
4. Refer to Section 2 - Prerequisites in:
– Manual Upgrades - System 800xA Installation (3BSE034678*).
– Automated Upgrades using System Installer - System 800xA Automated
Installation (3BSE034679*).
and perform all procedures relating to operating system settings, Windows
service packs, miscellaneous Windows components installation, other third
party software, group policy, 800xA Service User privileges, and Windows
updates and hot fixes.
5. Refer to System 800xA Installation (3BSE034678*) and install all 800xA 5.1
System software per the software inventory taken earlier. This step is not
necessary if performing an automated upgrade using System Installer.
6. Refer to Requirements for VB Graphics Extension Software on page 97 to
install Visual BASIC 6.0 with SP6 and the VB Graphics extensions if required.
7. Point the Central Licensing Client to the new 800xA 5.1 Central Licensing
Server.
8. Connect the server to the upgraded 800xA 5.1 System via the Connect Node
feature in the Configuration Wizard.
9. Refer to Post Upgrade Procedures on page 101 and perform the applicable post
upgrade procedures for the upgraded server.
10. Repeat this procedure for every redundant Connectivity Server.
Upgrade the servers one-by-one in order to keep redundancy of the system as
long as possible.
Operation and monitoring of the plant are only possible from clients in the 800xA
5.0 SP2 System at this point in the upgrade process.

3BSE036342-510 C 71
Redundant Aspect Server (2oo3 Redundancy Only) Section 3 Upgrading 800xA 5.0 SP2 to 800xA

Redundant Aspect Server (2oo3 Redundancy Only)

Perform this procedure only if the Aspect Servers in the 800xA System have
2oo3 redundancy.
1. Remove the other redundant Aspect Server (if 2oo3 redundant) from the 800xA
5.0 SP2 System via the Remove Server feature in the Configuration Wizard. If
working in a domain this server needs to be removed from the Domain
Controller.
2. Reformat the hard drive.
3. Install the new operating system defined for the 800xA 5.1 System. Click
Advanced when installing Windows 7 or Windows Server 2008. This is
required to delete the existing partition and recreate a new one. Failure to
perform this step will leave old data on the hard drive.
4. Refer to Section 2 - Prerequisites in:
– Manual Upgrades - System 800xA Installation (3BSE034678*).
– Automated Upgrades using System Installer - System 800xA Automated
Installation (3BSE034679*).
and perform all procedures relating to operating system settings, Windows
service packs, miscellaneous Windows components installation, other third
party software, group policy, 800xA Service User privileges, and Windows
updates and hot fixes.
5. Refer to System 800xA Installation (3BSE034678*) and install all 800xA 5.1
System software per the software inventory taken earlier. This step is not
necessary if performing an automated upgrade using System Installer.
6. Refer to Requirements for VB Graphics Extension Software on page 97 to
install Visual BASIC 6.0 with SP6 and the VB Graphics extensions if required.
7. Point the Central Licensing Client to the new 800xA 5.1 Central Licensing
Server.
8. Connect the server to the upgraded 800xA 5.1 System via the Connect Node
feature in the Configuration Wizard.

72 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Clients

9. Refer to Post Upgrade Procedures on page 101 and perform the applicable post
upgrade procedures for the upgraded server.
Operation and monitoring of the plant are only possible from clients in the
800xA 5.0 SP2 System at this point in the upgrade process.

Clients
1. Remove some clients from the 800xA 5.0 SP2 System via the Remove Client
feature in the Configuration Wizard. If working in a domain the clients need to
be removed from the Domain Controller.
Do not remove all of the clients from the 800xA 5.0 SP2 System at this point.
Keeping some clients in the 800xA 5.0 SP2 System will allow the operators to
continue to observe and control the process.
The procedure for the client nodes can be performed one-by-one or in a group.

2. Reformat the hard drive on each client.

3. Install the new operating system defined for the 800xA 5.1 System on each
client. Click Advanced when installing Windows 7. This is required to delete
the existing partition and recreate a new one. Failure to perform this step will
Refer to Section 2 - Prerequisites in:
– Manual Upgrades - System 800xA Installation (3BSE034678*).
– Automated Upgrades using System Installer - System 800xA Automated
Installation (3BSE034679*).
and perform all procedures relating to operating system settings, Windows
service packs, miscellaneous Windows components installation, other third
party software, group policy, 800xA Service User privileges, and Windows
updates and hot fixes.
4. Refer to System 800xA Installation (3BSE034678*) and install all 800xA 5.1
System software per the software inventory taken earlier. This step is not
necessary if performing an automated upgrade using System Installer.
5. Refer to Requirements for VB Graphics Extension Software on page 97 to
install Visual BASIC 6.0 with SP6 and the VB Graphics extensions if required.

3BSE036342-510 C 73
Information Management Server Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

6. Point the Central Licensing Client to the new 800xA 5.1 Central Licensing
Server on each client.
7. Connect each client to the upgraded 800xA 5.1 System via the Connect Node
feature in the Configuration Wizard.
8. Refer to Post Upgrade Procedures on page 101 and perform the applicable post
upgrade procedures for the upgraded server.
Operation and monitoring of the plant are only possible from clients in the 800xA
5.0 SP2 System at this point in the upgrade process.

Information Management Server

1. Check that history and event data storage is available in the Connectivity
Servers to overlap, with margin, the time it takes to upgrade the IM Server. This
includes time to:
– Reformat the hard drive.
– Load all required software.
– Connect the IM Server to the 800xA 5.1 System.
– Reboot the IM Server.
– Collect data from the Connectivity Servers from the time when the IM
Server was removed from the 800xA 5.0 SP2 System.
2. Perform the Information Management Pre-Upgrade Procedures on page 421 in
Appendix E, Information Management Upgrade.
3. Remove the IM Server from the 800xA 5.0 SP2 System via the Remove Server
feature in the Configuration Wizard. If working in a domain this server needs to
be removed from the Domain Controller.
4. Reformat the hard drive.
5. Install the new operating system defined for the 800xA 5.1 System. Click
Advanced when installing Windows Server 2008. This is required to delete the
existing partition and recreate a new one. Failure to perform this step will leave
old data on the hard drive.
6. Refer to Section 2 - Prerequisites in:

74 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Information Management Server

– Manual Upgrades - System 800xA Installation (3BSE034678*).

– Automated Upgrades using System Installer - System 800xA Automated
Installation (3BSE034679*).
and perform all procedures relating to operating system settings, Windows
service packs, miscellaneous Windows components installation, other third
party software, group policy, 800xA Service User privileges, and Windows
updates and hot fixes.
7. Refer to System 800xA Installation (3BSE034678*) and install all 800xA 5.1
System software per the software inventory taken earlier. This step is not
necessary if performing an automated upgrade using System Installer.
8. Refer to Requirements for VB Graphics Extension Software on page 97 to
install Visual BASIC 6.0 with SP6 and the VB Graphics extensions if required.
9. Point the Central Licensing Client to the new 800xA 5.1 Central Licensing
Server.
10. Verify that the ABB Process Administration Service (PAS) is set to manual in
the Services Control Panel (run Services.msc from the Run dialog box). Stop
the service if it is running.
11. Connect the server to the upgraded 800xA 5.1 System via the Connect Node
feature in the Configuration Wizard.
12. Reboot the node.
13. Refer to Information Management Post Upgrade Procedures on page 426 in
Appendix E, Information Management Upgrade and perform the applicable
post upgrade procedures for the upgraded server.
Operation and monitoring of the plant are only possible from clients in the 800xA
5.0 SP2 System at this point in the upgrade process.

3BSE036342-510 C 75
Application Servers Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

Application Servers
Perform the procedures for the Application Servers (Batch Management, Asset
Optimization, PC, Network and Software Monitoring, etc.) one at a time.

When upgrading redundant Batch Management Servers, the Primary Batch

Server must be upgraded first, followed by the Secondary Batch Server. Do not
upgrade the Secondary Batch Server followed by the Primary Batch Server.
1. Remove an Application Server from the 800xA 5.0 SP2 System via the
Remove Server feature in the Configuration Wizard. If working in a domain
this server needs to be removed from the Domain Controller.
2. Reformat the hard drive.
3. Install the new operating system defined for the 800xA 5.1 System. Click
Advanced when installing Windows Server 2008. This is required to delete the
existing partition and recreate a new one. Failure to perform this step will leave
old data on the hard drive.
4. Refer to Section 2 - Prerequisites in:
– Manual Upgrades - System 800xA Installation (3BSE034678*).
– Automated Upgrades using System Installer - System 800xA Automated
Installation (3BSE034679*).
and perform all procedures relating to operating system settings, Windows
service packs, miscellaneous Windows components installation, other third
party software, group policy, 800xA Service User privileges, and Windows
updates and hot fixes.
5. Refer to System 800xA Installation (3BSE034678*) and install all 800xA 5.1
System software per the software inventory taken earlier. This step is not
necessary if performing an automated upgrade using System Installer.
6. Refer to Requirements for VB Graphics Extension Software on page 97 and
install the required VB Graphics extension software.
7. Point the Central Licensing Client to the new 800xA 5.1 Central Licensing
Server.
8. Connect the server to the upgraded 800xA 5.1 System via the Connect Node
feature in the Configuration Wizard.

76 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Remaining Nodes

9. Refer to Post Upgrade Procedures on page 101 and perform the applicable post
upgrade procedures for the upgraded server.
10. Repeat this procedure for every Application Server.
The 800xA System is now running in nonredundant mode in both the
800xA 5.0 SP2 and the 800xA 5.1 systems. Operation and monitoring of the
plant are possible from clients in both systems at this point in the upgrade
process.
11. Operators should move to the 800xA 5.1 System to operate and control the
plant at this point in the upgrade process.

Remaining Nodes
1. Remove the remaining nodes in the 800xA 5.0 SP2 System and connect them
to the 800xA 5.1 System. If working in a domain these nodes need to be
removed from the Domain Controller.
2. Repeat the applicable procedures for the remaining nodes in the 800xA 5.0 SP2
System, except for the 800xA 5.0 SP2 Primary Aspect Server.
Operation and monitoring of the plant are only possible from clients in the
800xA 5.1 System at this point in the upgrade process.

800xA 5.0 SP2 Primary Aspect Server

Upgrade the 800xA 5.0 SP2 Primary Aspect Server.
1. Use the Configuration Wizard to stop the 800xA 5.0 SP2 System on the 800xA
5.0 SP2 Primary Aspect Server.
2. Use the Configuration Wizard to delete the system from the 800xA 5.0 SP2
Primary Aspect Server.
3. Reformat the hard drive.
4. Install the new operating system defined for the 800xA 5.1 System. Click
Advanced when installing Windows 7 or Windows Server 2008. This is
required to delete the existing partition and recreate a new one. Failure to
perform this step will leave old data on the hard drive.
5. Refer to Section 2 - Prerequisites in:

3BSE036342-510 C 77
Remaining Steps Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

– Manual Upgrades - System 800xA Installation (3BSE034678*).

– Automated Upgrades using System Installer - System 800xA Automated
Installation (3BSE034679*).
and perform all procedures relating to operating system settings, Windows
service packs, miscellaneous Windows components installation, other third
party software, group policy, 800xA Service User privileges, and Windows
updates and hot fixes.
6. Refer to System 800xA Installation (3BSE034678*) and install all 800xA 5.1
System software per the software inventory taken earlier. This step is not
necessary if performing an automated upgrade using System Installer.
7. Refer to Requirements for VB Graphics Extension Software on page 97 and
install the required VB Graphics extension software.
8. Point the Central Licensing Client to the new 800xA 5.1 Central Licensing
Server.
9. Connect the server to the upgraded 800xA 5.1 System via the Connect Node
feature in the Configuration Wizard.
10. Refer to Post Upgrade Procedures on page 101 and perform the applicable post
upgrade procedures for the upgraded server.
Operation and monitoring of the plant are only possible from clients in the
800xA 5.1 System at this point in the upgrade process.

Remaining Steps
1. Refer to System 800xA Post Installation (3BUA000156*) and configure
Windows Firewall and Windows Services on every node in the 800xA System.
2. It is important to create backups of node hard disks and the 800xA System after
completing the upgrade procedures. Valid backups insure that the system can
be restored if necessary.
a. It is recommended that a third party backup/restore and/or disk imaging
utility be used to save (and restore if necessary) all disks on each node
before starting the upgrade procedures.
b. Perform the 800xA full backup from the Maintenance Structure (Aspect
Directory backup type).

78 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Pre-Upgrade Procedures

Pre-Upgrade Procedures
The 800xA System and software require preparatory steps before performing the
online upgrade. Perform the applicable procedures in the order presented.

Batch Management
1. Verify all scheduled batches are completed or terminated.
2. Disable the Batch Alarm & Event Service Group and Batch Service Group
before proceeding. To disable the service groups:
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Service Structure.
c. Use the Object Browser to select:
Services > Event Collector, Service >
batch_group_name, Service Group
d. Select Service Group Definition in the Aspect List Area.
e. Select the Configuration tab in the Preview Area.
f. Clear the Enabled check box and click Apply.
g. Determine the name of the nodes that are currently Primary and
Secondary Batch Servers,
h. Use the Object Browser to select:
Services > Batch Service, Service > batch_group_name,
Service Group
i. Select Service Group Definition in the Aspect List Area.
j. Select the Configuration tab in the Preview Area.
k. Select the provider that is currently the Secondary Batch Server.
l. Clear the Enabled check box and click Apply.
m. Select the provider that is currently the Primary Batch Server.
n. Clear the Enabled check box and click Apply.

3BSE036342-510 C 79
Customized Alarm Priority Mapping Aspects Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1

Customized Alarm Priority Mapping Aspects

Some customized Alarm Priority Mapping Aspects may be overwritten during the
upgrade. Record all values in the Alarm Priority Mapping aspects before beginning
the upgrade so that they can be recreated after the upgrade.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Library Structure.
3. Use the Object Browser to navigate to:
Alarm & Event > Alarm Collector Definitions, Alarm
Collector Definitions
4. Select a Alarm Collector Definition object with customized Alarm Priority
Mapping Aspect.
5. Select Alarm Priority Mapping in the Aspect List Area.
6. Record the values in the Alarm Priority Mapping aspects.
7. Repeat for all customized Alarm Priority Mapping aspects.

800xA for AC 800M

Use the following procedure to prepare for the 800xA for AC 800M upgrade:
1. Record the service account settings in the OPC Server Setup Wizard.
2. Control Builder stores its settings (systemsetup.sys) on disk in the following
directory:
...\ABB Industrial IT Data\Engineer IT Data\Control
Builder M Professional
Copy this file to a safe media.
3. Save OPC configurations by selecting:
File > Save Configuration
in the OPC Server Panel.
4. The OPC Server stores configuration files (*.cfg) and settings
(systemsetup.sys) on disk. Copy these files to a safe media. The
systemsetup.sys file is located in:

80 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Structured Data Logger

...\ABB Industrial IT Data\Control IT Data\OPC Server

for AC 800M
The configuration files are stored in the Files folder in the same location.
5. If the system to be upgraded originates from System Baseline 2.1 and has been
upgraded in steps through system versions, verify that the Control Builder
projects do not use the old obsolete SB2 (System Baseline 2) libraries (libraries
of version 1.0-0. For example: ControlStandardLib 1.0/0.

Structured Data Logger

Use the following procedure to prepare for the Structured Data Logger (SDL)
upgrade.
1. Back up the SQL Server 2000 SDL Database.
a. Open SQL Server Enterprise Manager.
b. Right-click SDL data base and select All Tasks > Backup Database…
from the context menu.
c. Save the backup file (with .bak extension) to a safe location.

Engineering Studio Function Designer System Extensions

Use the following procedures to prepare for the Engineering Studio upgrade.
The Function Designer system extensions:
• Signal Extension for AC800M Connect
• Function Designer for AC800M Connect
• Topology Designer for AC800M Connect
• CI Extension for AC800M Connect
• Signal Extension for TRIO Connect
• Topology Designer for AC800M High Integrity
• Function Designer for AC 800M Classic
• Topology Designer for AC800M Classic
• Function Designer for Fieldbus Builder Profibus/Hart

3BSE036342-510 C 81
Device Management FOUNDATION Fieldbus Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1

• AC 800M Signal Extension Classic

mainly consist of:
• Functional Planning Object Types, including a Function Settings aspect at the
Settings Object Type Group.
• Extension Libraries that add Function Designer aspects to Object Types
(Control Modules, Function Blocks, etc.) created by basic libraries (AC800M
Connect, AC 800M Classic, etc.).
After loading any of the listed system extensions in the 800xA 5.0 SP2 System,
some of these aspects may be modified; for example, to adapt Function Settings, or
to change the color or layout of Function Blocks in Function Diagrams. During the
800xA System upgrade to 800xA 5.1 the system extensions of the new system are
loaded. To keep the information about modified aspects, all aspects that were
created by a Function Designer system extension, but modified later are listed in the
Configuration Wizard log, and are written to Afw files.
The only way to bring these modifications back into the 800xA 5.1 System is to
manually merge the changes. Do not import the listed Afw files into the 800xA 5.1
System, because some additional properties/data might get lost. In the case of
Function Settings aspects, record the property settings from the 800xA 5.0 SP2
System and perform the modifications again in the 800xA 5.1 System. In the case of
modified Function aspects (e.g. Diagram Template, Component Template), record
the modifications done in the 800xA 5.0 SP2 System and perform the modifications
again in the 800xA 5.1 System.

Device Management FOUNDATION Fieldbus

Perform the following to prepare for the Device Management FOUNDATION
Fieldbus upgrade.
• User-Made Modifications to Library Objects Representing FF Standard
Blocks.
• Exporting Locally Stored Parameter Value Sets.

User-Made Modifications to Library Objects Representing FF Standard Blocks

User-made modifications to library objects representing FF standard blocks (these
are blocks supported by the Device Type Standard FBs as indicated in the Block

82 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Device Management FOUNDATION

Info tab of the block class parameter dialog box) will be overwritten during
upgrade. If such changes have been made, they can be reconstructed manually.
Refer to Device Management FOUNDATION Fieldbus on page 112.

Exporting Locally Stored Parameter Value Sets

Export the locally stored parameter value sets as follows:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Object Type Structure.
3. Use the Object Browser to navigate to:
FF Libraries, Object Type Group
4. Select FF Upload in the Aspect List Area.
5. Click Open Library in Fieldbus Builder FF.
6. Select the Function Block from FF Block Library > Function Blocks
in the Library view.
7. Double-click on the Function Block to open the properties dialog box for the
chosen Function Block.

3BSE036342-510 C 83
800xA for Advant Master and 800xA for Safeguard Section 3 Upgrading 800xA 5.0 SP2 to 800xA

8. Right-click and select Export from the context menu (Figure 4).

Figure 4. Exporting Locally Stored Parameter Value Sets

9. Specify the name and location of the .csv file and Click OK.

800xA for Advant Master and 800xA for Safeguard

Perform the following to prepare for the 800xA for Advant Master and 800xA for
Safeguard upgrade.
• Save the Advant Master Controller Licenses.txt.

84 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online 800xA for Advant Master and 800xA for

• Save the DATHR Files.

• Document the RTA Board Control Aspect Settings.

Save the Advant Master Controller Licenses.txt

Perform the following on the Primary Aspect Server in the 800xA 5.0 SP2 System:
1. Save the following file to a safe location.
– Advant Master Controller Licenses.txt
The default location for the file is:
...\Program Files\ABB Industrial IT\Operate IT\AC 400
Connect\Licenses

Save the DATHR Files

Perform the following on each 800xA for Advant Master and 800xA for Safeguard
Connectivity Server node:
1. Save the following files to a safe location:
– DATHR1.CD
– DATHR2.CD
– DATHR3.CD
from the folder:
...\Program Files\ABB Industrial IT\OperateIT\AC 400
Connect\AdvantBase\Data\RTA\Init\
and record which files belong to which node.

3BSE036342-510 C 85
800xA for Harmony Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

Document the RTA Board Control Aspect Settings

Perform the following on each 800xA for Advant Master and 800xA for Safeguard
Connectivity Server node:
1. Document the following settings in the RTA Board Control aspect for
reconfiguration after the upgrade.
– MB300 node and network address.
– 800xA as Clock Master (REVERSED_SYNC_MODE) check box.

800xA for Harmony

Perform the following to prepare for the 800xA for Harmony upgrade.
• Disable Harmony Services on 800xA for Harmony Servers.
• Save 800xA for Harmony Information.

Disable Harmony Services on 800xA for Harmony Servers

Stop the following 800xA for Harmony services on the 800xA for Harmony Server
node being upgraded.
1. Select:
Start > Control Panel > Administrative Tools > Services
2. Disable the following services:
– Time synchronization daemon.
– SoapSymTagAtomSrv.
– EbDataSyncService.
– EbServerBroker.
– ABBDiagnosticService.
– DD_xxxx - Where xxxx identifies the semAPI or hAPI device being used
(this may or may not exist).
Perform the following steps to disable these services:
a. Locate the service in the Services list.
b. Double-click the service to open the Properties dialog box for that service.
c. Change the Startup type to Disabled.

86 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online 800xA for AC 870P/Melody

d. Click Apply and then OK.

e. Repeat for each of the services listed.
3. Restart the 800xA for Harmony Server node.

Save 800xA for Harmony Information

Use the following procedure to save 800xA for Harmony information:
1. Create a backup of the Configuration Server database.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for OCS
Systems > Harmony > Configuration > Backup Configuration
b. Click Connect.
c. Click Browse to name the backup file and choose a location to save it.
d. Click Backup.
e. Click Exit when the backup is complete.

800xA for AC 870P/Melody

Back up project specific changes (if applicable):
• DHCP Server Configuration.
• ETC Host files for Melody Connectivity Servers.
• Changes in the Default Object Types (e.g. manual changes for permissions
in Control Connection Aspects).
• ConvDB changes only on Configuration Server (change to the directory
...\Program Files\ABB Industrial IT\Configuration\Melody Tag Importer\.. and
backup the files MELCONVERTER.BAT, ConvDB.mdb and
ConvDB_<Hostname>.mdb.
ConfigServer node: Ensure that no Commissioning will be done from the
Melody Composer during this upgrade.
Use the following procedure to save 800xA for AC 870P/Melody information:
1. Log in to the 800xA Service account on the Configuration Server node.
a. Create a backup of the Configuration Server database.

3BSE036342-510 C 87
800xA for MOD 300 Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

b. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for Melody
> Configuration > Backup Configuration
c. Click Connect.
Save the backup file to a safe media like a network share or removable disk.
Otherwise, the file will be deleted once an upgrade occurs due to a reload of the
node.
d. Click Backup.
e. Click Exit when the backup is complete.

800xA for MOD 300

Ensure that the configuration data noted in the Customized Data for Backup
appendix in 800xA for MOD 300 Configuration (3BUR002417*) has been recorded.

IEC 61850 Connect

Make backups for the IEC 61850 CET OPC Server projects. Refer to Section 6 of
System 800xA IEC 61850 Configuration (9ARD171387*) to export CET OPC
Server projects.
Handling of IET/CCT projects and PCM 600 projects is not described here as
they are external tools contributing to the IEC 61850 workflow. They do not
reside on 800xA System nodes.

PLC Connect
Perform the following procedure to prepare for the PLC Connect upgrade.
1. If the PLC Connect IEC 60870 feature is installed and configured, the IEC
configuration must be saved. Refer to the section on configuring the IEC 60870
driver in System 800xA PLC Connect Configuration (3BSE035041*) for more
information.
2. If the PLC Connect Communication Server Pre Treatment function is being
used in the application (refer to System 800xA PLC Connect Configuration
(3BSE035041*) for more information), make a backup of the Pretreat dll

88 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Asset Optimization

(Pretreat3.dll or Pretreat4.dll, be sure to select the version used). The Pretreat

dll is located in the following folder on the PLC Connect Connectivity Server:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
The path is the default location of the file. If it has been placed somewhere else,
make a backup from that location.
3. Make a backup of the application project and source files for the Pretreat dll.

Engineering Studio IO Allocation

Deactivate the auto update mode in IO Allocation.
1. Start the Engineering Workplace.
2. Open the IO Allocation tool on any object by right-clicking on the object and
selecting Advanced > IO Allocation from the context menu that appears.
3. Verify that no check mark symbol is visible in the Options > Autoupdate
CBM menu item in the IO Allocation tool.

Asset Optimization
Preparing for the Asset Optimization upgrade requires backing up data to a safe
media.
Use the following procedure to back up Asset Optimization information (perform
only the steps applicable to the system):
1. Asset Monitoring:
Asset Monitoring directories will be found on every Asset Optimization Server
node and any other node defined as an Asset Monitoring Server.
a. If Runtime Asset Monitors are being used in the system, save the Runtime
Asset Monitor data directory (DeviceRunTimeMSLogicStore) to a safe
media. This directory stores the runtime information calculated by the
Runtime Asset Monitors running in this node. This directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin

3BSE036342-510 C 89
Asset Optimization Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

b. If XY Profile Deviation Asset Monitors are being used in the system, save
the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles) to a safe media. This directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
c. If Counter Check Asset Monitors are being used in the system, save the
Counter Check Asset Monitors data directory named:
{66E71F7B-90D6-4E62-9881-38388B24CBDF}
to safe media. This directory exists for each AO Server in the system.
These directories are located in:
<install drive>:\OperateITData\AoEng\<AO Server ID>\
AmCat\<Counter Check ID>
Where each <AO Server ID> directory represents one AO Server instance
running on the selected node. The <AO Server ID> directory name is
formatted as two consecutive GUIDs, for example:
{F9C150F5-2929-4A12-BC28-E00ED6DB1585}{B925E77F-2A82-
41C6-A981-FAB4386D5701}.
For correct system operation it is important that only the directories identified by
the Counter Check Asset Monitor category GUID be saved, as other data in the
tree structure above these directories will not be consistent with a restore.
2. Maximo Integration:
If using Maximo Integration, the Maximo Integration information (Maximo
Equipment ID and Maximo Credentials aspects) must be saved from all Asset
Optimization Server nodes. Refer the Service Structure for the name of the
Asset Optimization Server nodes.
a. The MxDef files provide the mapping between the 800xA System
environment and the Maximo system. If the MxDef files were customized
per the instructions in Industrial IT, 800xA - Asset Optimization,
Configuration (3BUA000118*), back up the customized MxDef files to
safe media.
– The customized MxDef Files for Maximo versions 4.1 and 4.1.1 are
located in the following directory:

90 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Asset Optimization

...\Program Files\ABB Industrial IT\Optimize IT\Asset

Optimization\ABBAO\Services\MOM\MxDefs\
– The customized MxDef files for Maximo version 5.1 and 5.2 are located
in the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\Maximo5\MxServer
– The customized MxDef files for Maximo version 6.2 are located in the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\MaximoDef
b. Back up the AOMaximoModel.xml file to a safe location. A backup of
AOMaximoModel.xml is necessary because the ECS model for Maximo
also needs to be modified if the MXDef files are customized.
The model file is available at the following location:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
The pending fault reports residing in the system are available in the following
directory structure:
...\OperateITData\OptaoACDs
Backup the entire OptaoACDs folder.
3. SAP/PM Integration:
If using SAP/PM Integration, the SAP/PM Integration information (SAP
Equipment ID and SAP Credentials aspects) must be saved from all Asset
Optimization Server nodes. Reference the Service Structure for the name of the
Asset Optimization Server nodes.
a. Although the SAP/PM system is separate from the 800xA System, it is a
good idea to back up the system in use. Follow SAP/PM standard
practices for SAP/PM system backup.
b. The SAPPMDef files provide the mapping between the 800xA System
environment and the SAP/PM system. If the SAPDef files were
customized per the instructions in Industrial IT, 800xA - Asset
Optimization, Configuration (3BUA000118*), back up the customized
SAPDef files to safe media.

3BSE036342-510 C 91
PC, Network and Software Monitoring Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

The customized SAPPMDef files for SAP version4.7 are located under:
...\Program Files\ABB Industrial IT\Optimize IT\
Asset Optimization\AOECSConnector\SAPPMDef
c. Back up the AOSAPModel.xml file to a safe location. A backup of
AOSAPModel.xml is necessary because the ECS model for SAP also
needs to be modified if the SAPPMDef files are customized.
The model file is available at the following location:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
The pending fault reports residing in the system are available in the following
directory structure. Backup the entire OptaoACDs folder.
...\OperateITData\OptaoACDs
4. DMS Calibration Integration:
The DMS Calibration Integration approach is changed in 800xA 5.1. Upgrade of
DMS Calibration Integration is not supported. Reconfigure the DMS Calibration
Integration based on an engineered solution.
Contact ABB technical support for more information.

PC, Network and Software Monitoring

Use the following procedure to prepare for the PC, Network and Software
Monitoring upgrade.
1. If there are user defined Script, Resource, and Assembly files they need to be
backed up. The user files are located in:
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Scripts\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Assemblies\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Resources\User directory

92 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online PC, Network and Software Monitoring

Copy the files in these directories to a safe location.

2. Shut down the PC, Network and Software Monitoring Server node.
a. Use the Structure Selector to open the Service Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to:
Services > OpcDA_Connector, Service > SG_IT Server,
Service Group > OPCDA_Provider_Node Name, Service
Provider
(where Node Name is the name of the PC, Network and Software
Monitoring Server node).
c. Select Service Provider Definition in the Aspect List Area.
d. Click the Configuration tab to produce a view in the Preview Area.
e. If the Enabled check box is selected, clear it and click Apply.

PC, Network and Software Monitoring Device Library

Use the following procedure to prepare PC, Network and Software Monitoring
Device Library upgrade:
1. Back up MOF files (if they exist) to a safe location. The MOF files are located
in:
...\Program Files\ABB Industrial IT\Optimize IT\PC,
Network and Software Monitoring\MOFS
2. Back up Process Health.dll to a safe location if Generic Computer Node V1.0
or higher versions are loaded. The dlls are located in:
...\Program Files\ABB Industrial IT\Optimize
IT\PC, Network and Software Monitoring\Asset
Monitoring\Bin

3BSE036342-510 C 93
SMS and e-mail Messaging Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

SMS and e-mail Messaging

Save all GSM Device hardware information. Record information for the GSM
device on the SMS and e-mail Messaging GSM Hardware Setup Worksheet shown
in Table 3.

Table 3. SMS and e-mail Messaging GSM Hardware Setup Worksheet

Item Setting/Value
Spooler Settings
Activate Outbox Spooler Checked (check and leave checked)
Activate Inbox Spooler Checked (check and leave checked)
Interval for Checking for Incoming Value: _____ Seconds Minutes (circle 1)
Messages
Port Settings
COM Port Value: COM _____
Baud Rate Value: _____
Data Bits Value: _____
Parity Value: _____
Stop Bits Value: _____
PIN and Properties
Query PIN Checked or Unchecked (circle one)
PIN (only if Query PIN is checked) Value: ___________________
Save PIN (only if Query PIN is Checked or Unchecked (circle one)
checked)
Own Number (telephone number of Value: ___________________
SIM card (including Country Code)
in GSM hardware)

94 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online SMS and e-mail Messaging

Table 3. SMS and e-mail Messaging GSM Hardware Setup Worksheet (Continued)

Item Setting/Value
Initialization String for GSM Hardware Value:
_______________________________
_______________________________
_______________________________
_______________________________
General Service Properties
Name (GSM service provider) Value: ___________________
Port Value: COM _____
SMSC Value: ___________________
Default Country Code Value: ___________________
Default Prefix Value: ___________________
Number of Attempts Value: ___________________
Splitting Service Properties
Splitting Checked or Unchecked (circle one)
Optimize Splitting Checked or Unchecked (circle one)
Enumerate Splitting Checked or Unchecked (circle one)
Narrowband Sockets Checked or Unchecked (circle one)
Messaging Service Properties
Add Before Message Blank (verify and do not change)
Use for Delivery Notification Only Unchecked (verify and do not change)
Default Option 0 (verify and do not change)
Message General Properties
Replace CR LF for Incoming Checked or Unchecked (circle one)
Messages

3BSE036342-510 C 95
Scheduler Service (Application Scheduler)Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

Scheduler Service (Application Scheduler)

Disable Schedules before stopping the servers and performing the upgrade. This is
performed only once and not on every node. The Schedules will need to be
manually enabled following the upgrade.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Scheduling Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Clear the Enabled check box and click Apply.

Calculations Service
Disable Calculations before stopping the servers and performing the upgrade. This
is performed only once and not on every node. The Calculations will need to be
manually enabled following the upgrade.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Calculations Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Clear the Enabled check box and click Apply.

Basic History Service Data

Back up the Basic History folder for each Basic History Service Provider in the
Service Structure. Depending on the system, the Basic History Service data can
be present on a number of different node types (Connectivity Servers, IM Servers,
AO Servers, etc.). It is best to search for the directory described in this procedure
on all nodes, and if there is data present, back up that data.

96 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Process Engineering Tool Integration

To save Basic History Service data:

1. Stop the Basic History Server from the Service Structure by the following
procedure:
a. Open a Plant Explorer Workplace.
b. Use the Structure Browser to open the Service Structure.
c. Select the Basic History, Service > Basic, Service Group.
d. Select the Service Group Definition aspect.
e. Click the Configuration tab.
f. Clear the Enabled check box and click Apply.
2. Use Windows Backup (not the 800xA Backup) to backup the files in the:
...\OperateITData\History\{provider ID}
directory.
3. Start the Basic History Server manually again from the Service Structure
following the upgrade.

Process Engineering Tool Integration

Back up Process Engineering Tool Integration information. The project data is
located in the following directory:
...\Program Files\ABB Industrial IT\Engineer
IT\Engineering Studio\Process Engineering Tool
Integration\Xml
Save the entire Xml data directory to a safe media such as a network share or
removable disk. The directory contains the default mapping files (*.dmf) modified
on the project, accelerator files (*.acc), and configuration files (*.pcf and *.fcf).

Requirements for VB Graphics Extension Software

Perform these procedures only if the restored system makes use of VB graphics.

3BSE036342-510 C 97
Installing Visual BASIC 6.0 with SP6 Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

• Installing Visual BASIC 6.0 with SP6 must be followed for all nodes that use
Graphics Builder and the Primary Aspect Server node. This must be done
before performing the procedures under Perform the 800xA System Restore.
• Installing the VB Graphics Extension Software must be followed for each VB
Graphics extension software package on all nodes in the 800xA 5.1 System,
if the base product was installed on the 800xA 5.0 SP2 System. This must
be done before performing the procedures under Perform the 800xA System
Restore.
To deploy VB Graphics, the user must belong to the Application Engineer
IndustrialIT user group and Windows Local Administrators.

Refer to System 800xA Engineering, Process Graphics Migration Tool for

information on migrating VB Graphics to Process Graphics 2.

Installing Visual BASIC 6.0 with SP6

Use of an Aero Theme with Windows 7 will lead to screen latency issues in the
VB Graphics Builder. This is because the Aero theme uses advanced rendering
schemes. Turn off the Windows Aero theme and switch to either none or
Windows Classic for use of VB Graphics. The behavior of VB IDE in Windows 7
will then be the same as that in Windows XP.
All nodes that use the Graphics Builder and the Primary Aspect Server node need a
Professional or Enterprise Edition of Microsoft Visual BASIC 6.0 with SP6. The
licensed copy used on the 800xA 5.0 SP2 System must be installed on the 800xA
5.1 System. Follow the installation procedure provided with Visual BASIC.

Installing the VB Graphics Extension Software

Perform the following procedure to install the VB Graphics extension software on
all nodes in the 800xA 5.1 System, if the base product was installed on the 800xA
5.0 SP2 System.
1. Insert System Installation DVD 1 into the drive.
2. Wait for the Installation AUTORUN screen to appear.
3. Select:
Manual Installation > VB Graphics Extensions
as shown in Figure 5.

98 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Installing the VB Graphics Extension

4. Select a VB Graphics extension to install (the installation of the Batch

Management VB Graphics extensions is described later in this procedure).
5. The Installation Wizard for the selected VB Graphics extension appears.
6. Follow the Installation Wizard to complete the installation. Choose Typical as
the installation type.
7. Repeat the procedure for each required VB Graphics extension that appears in
the Installation AUTORUN Screen.
8. This step only applies to the VB Graphics extensions for Batch Management
when using System Installer to upgrade the 800xA System. If Batch
Management was installed manually during the upgrade, the VB Graphics
extensions for Batch Management were installed at that time.
a. Select:
Manual Installation > Batch Management
b. The Installation Wizard for Batch Management appears.

3BSE036342-510 C 99
Installing the VB Graphics Extension Software Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1

c. Select Modify when the dialog box appears that offers that choice.

Figure 5. Installation AUTORUN Screen

d. Select to install the Batch Management VB Graphics extensions in the

Installation Type dialog box.
e. Follow the Installation Wizard to complete the installation.

100 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Post Upgrade Procedures

Post Upgrade Procedures

The remainder of this section describes how to:
• Migrate the Structured Data Logger SQL Database.
• Restore the backups of the IEC 61850 CET OPC Server projects.
• Restore historical data.
• Restore the necessary data for each Functional Area.

Migrating the Structured Data Logger SQL Database

Perform the following post upgrade procedure for Structured Data Logger (SDL).
Upgrading SDL from 800xA 5.0 SP2 to 800xA 5.1 involves transfer of database
data from SQL Server 2000 to SQL Server 2008.
1. Open Microsoft SQL Management Studio and connect to the
SDL_INSTANCE server.
2. Delete SDL database from SDL_INSTANCE if already created during the
installation.
3. Restore the SDL database using the .bak file (from SQL Server 2000) that was
stored to a safe location during the pre-upgrade process.
a. Right-click Databases and select Restore Database… from the context
menu.
b. Select the From Device option and browse for the .bak file that was stored
to a safe location during the pre-upgrade process.
c. Select/Enter SDL in To database and click OK.
4. Use Windows Explorer to navigate to:
...\Operate IT\Structured Data Logger\vbs
5. Double-click RunCreateScripts_SDL.vbs. This will upgrade the SDL
database schema.
6. Verify that the SDL Control Application exists in the system and that the SDL
Log aspects contain data.

3BSE036342-510 C 101
IEC 61850 Connect Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

IEC 61850 Connect

Restore the backups of the IEC 61850 CET OPC Server projects. Refer to Section 6
of System 800xA IEC 61850 Configuration (9ARD171387*).
Handling of IET/CCT projects and PCM 600 projects is not described here as
they are external tools contributing to the IEC 61850 workflow. They do not
reside on 800xA System nodes.

Customized Alarm Priority Mapping Aspects

Some customized Alarm Priority Mapping Aspects may have been overwritten
during the upgrade. Recreate the Alarm Priority Mapping Aspects using the data
recorded during Customized Alarm Priority Mapping Aspects on page 80.

Reconfiguring Group Displays

New Group Display aspects that are created and configured in the Object Type
Structure on the object types and instances in 800xA 5.1 will work correctly even if
there is more than one aspect with the same name but each aspect has a different
Aspect Category.
Configured Group Display aspects that existed in the Object Type Structure and
on the object types and instances in 800xA 5.0 SP2 should have their Aspect
Categories reconfigured for the aspects to display correctly. (This is required for the
reference to an aspect to be stored along with its Category ID.)

Upgrading Faceplates
The Faceplate aspects created in all versions prior to 800xA 5.1 use a different
method to identify the references to faceplate elements or other properties than
those in 800xA 5.1.
Upgrading a faceplate is optional, but is strongly recommended for the following
reasons:
• Better runtime performance, as no name server access is required when a
faceplate is opened.
• More reliable because the references continue to work even if the target object
is renamed.

102 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online 800xA for AC 800M

• Upgraded faceplates function efficiently with the Consistency Checker and

Reference Tool. This behaves similar to a Process Graphics 2 graphic aspect.
• The upgrade to new reference handling can also repair some broken references.
Refer to the Upgrading Faceplates appendix in System 800xA Engineering Process
Graphics (3BSE049230*) for the procedure to upgrade the faceplates.

800xA for AC 800M

Perform the following procedure to restore 800xA for AC 800M information:
1. Use the OPC Server Setup Wizard to enter the previously used and recorded
service account settings.
2. Control Builder stores its settings (systemsetup.sys) on disk in the following
directory:
...\ABB Industrial IT Data\Engineer IT Data\Control
Builder M Professional
Copy the previously saved file from the safe media to this folder.

Engineering Studio
Perform the following post upgrade procedures for Engineering Studio:
• Check and Repair AES Variable Table.
• Upgrade Diagram References and Diagram Variables.
• Engineering Studio Function Designer System Extensions
• Deleting Engineering Base Service from the Service Structure.

Check and Repair AES Variable Table

The Check and Repair AES Variable Table (Applications, Controllers,
Diagrams/SCMs, and Diagram (Cm) Types) function can be used to:
• Correct possible inconsistent data used for display of online values and external
cross references.
• Delete obsolete data and reduce aspect size.
Perform the following procedure to use this application.
1. Open a Plant Explorer Workplace.

3BSE036342-510 C 103
Engineering Studio Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

2. Use the Structure Selector to open the Object Type Structure.

3. Use the Object Browser to navigate to:
Object Types > Functional Planning > Settings
4. Select Function Upgrade in the Aspect List Area to open the Function
Upgrade aspect in the Preview Area.
5. Select the Check and Repair AES Variable Table (Applications,
Controllers, Diagrams/SCMs, and Diagram (Cm) Types) check box and
click Apply.
6. Click Run Upgrade to perform this upgrade.
Executing the Check and Repair AES Variable Table procedure makes the
environment support work for Function Designer.

Upgrade Diagram References and Diagram Variables

In the 800xA 5.1 System (opposite to the 800xA 5.0 SP2 System) Diagram
References and Diagram Variables are by default created as Symbol Objects. This is
not true for Diagram References and Diagram Variables created during upgrade
(restore) from 800xA 5.0 SP2 Systems. Convert them from Aspect Objects to
Symbol Objects by use of the conversion function described in the following
procedure.
Differences between Aspect Objects and Symbol Objects are described in
Industrial IT, 800xA -Engineering, Engineering Workplace, Function Designer
(3BDS011224*).
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Object Type Structure.
3. Use the Object Browser to navigate to:
Object Types > Functional Planning > Settings
4. Select Function Upgrade in the Aspect List Area to open the Function
Upgrade aspect in the Preview Area.
5. Select the Convert Diagram References/Variables from Aspect Objects to
Symbol Objects check box and click Apply.

104 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Device Management and Fieldbuses

6. Click Run Upgrade to perform the upgrade.

This function is not suitable in the case of additional aspects on input/output
references, e.g. Graphic Elements, for typical diagrams with input/output
references that will get copied and connected via the Bulk Data Manager.

Engineering Studio Function Designer System Extensions

Refer to Engineering Studio Function Designer System Extensions on page 81 and
recreate the configuration changes that were recorded before the upgrade.

Deleting Engineering Base Service from the Service Structure

When the 800xA System is running, delete the Engineering Base Service from the
Service Structure.
1. Use Windows Explorer to navigate to the following directory:
...\Program Files\ABB Industrial IT\Engineer IT\
Engineering Studio\DocumentParameterManager\
bin\support
2. Double-click EbServiceCleanUpUtil.exe to delete the service.

Device Management and Fieldbuses

Perform the post upgrade procedures for Device Management and fieldbuses.

Restore Device Types

Third party software, such as Device Type Managers for the Device Type must be
reinstalled since the hard drive of the 800xA System node has been reformatted.
The following steps for Fieldbus Device Types need to be carried out on every
800xA system node. Perform the System Restore Wizard procedure on the nodes in
the following sequence:
• Aspect Servers (including redundant Aspect Servers).
• Connectivity Servers (including redundant Connectivity Servers).
• Application Servers.

3BSE036342-510 C 105
Device Management and Fieldbuses Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

• Clients.
Restore the Device Types on the Primary Aspect Server node before starting to
install them on other system nodes. Do not run parallel installations of Device
Types on other system nodes unless all Device Types are restored on the Primary
Aspect Server node. Installation of Device Types on other system nodes can be
done in parallel after they are restored on the Primary Aspect Server node.
If the system contains FOUNDATION Fieldbus Device Types, check the
following before proceeding to the next step:
• Open a Plant Explorer Workplace.
• Use the Structure Selector to open the Object Type Structure > FF
Libraries.
• Check to see if there is more than one entry of FF H1 Device Library,
FF Object Type Group.
• If there is more than one entry, perform FF Upload once so there is only one
instance of FF H1 Device Library, FF Object Type Group
present. If there is only one entry, proceed to the next step using the Device
Library Wizard.
1. Start the Device Library Wizard. Select:
Start > All Programs > ABB Industrial IT 800xA > Device Mgmt >
Device Library Wizard
-or-
double-click the Device Library Wizard icon on the desktop.
If the Device Library Wizard - Client has not been connected to the Device
Library Wizard - Server, navigate first to:
Device Library Wizard Administration > Connect Client
and follow the Device Library Wizard Procedure

106 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Device Management and Fieldbuses

2. Select the Enable Trace File check box as shown in Figure 6.

Figure 6. Enabling the Trace File

3. Navigate to:
Device Type Administration > System Restore Wizard

3BSE036342-510 C 107
Device Management and Fieldbuses Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

4. Choose the second option in the System Restore Wizard as shown in Figure 7
and click Next.

Figure 7. System Restore Wizard (1)

5. Choose the first option as shown in Figure 8 and click Next.

Figure 8. System Restore Wizard (2)

108 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Device Management and Fieldbuses

6. Depending on which fieldbus protocol is used in the previous system version

environment, insert one of the delivered Device Library system DVDs in the
DVD drive (e.g. Device Library HART – DVD).
7. Click Browse and navigate to the DVD drive.
8. When the drive has been selected in the Browse for folder dialog box, click OK
in that dialog box and then Next in the ABB Device Library Wizard. This step
may take one or two minutes to complete.
9. The Device Library Wizard scans the 800xA System for fieldbus device types
that are already used and compares the results with the contents of the DVD.
Device Types available in the 800xA System and the DVD are shown in the
Extract tab of the Device Library Wizard (Figure 9).

Figure 9. Extract Device Type Files

10. Device Types available in the 800xA System but not on the DVD are displayed
in the Missing tab. If there are any Device Types showing in the Missing tab,
navigate to the Browse dialog box by clicking Back and inserting a new Device
Library DVD in the DVD drive.
11. Click Next to start the extraction process.
12. Repeat Step 6 to Step 11 for each fieldbus protocol if more than one fieldbus
protocol is used.

3BSE036342-510 C 109
Device Management and Fieldbuses Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

13. There may be some Object Types that are either customer created, or are the
latest Device Types downloaded from ABB SolutionsBank. These will not be
available on the DVDs. The Device Library Wizard will prepare a list for these
Device Types (Figure 10). Install these Device Types manually.

Figure 10. List of Files to be Manually Installed

14. Repeat this procedure until all Device Types are extracted to the 800xA System
node and the Missing tab does not list any device types.
During extraction, if a dialog box pops up asking for an overwrite, select No and
continue.
15. If the Device Library DVDs do not contain all Device Types used in the
previous system version, the missing Device Types must be downloaded from
ABB SolutionsBank.
It is only possible to complete the Wizard if all Device Types have been
successfully extracted.

110 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Device Management and Fieldbuses

16. When the extraction process is completed successfully, the Device Types need
to be re-installed on the 800xA System node. Click Next to launch the Re-
installation of Device Types dialog box shown in Figure 11.

Figure 11. Re-install Device Types Dialog Box

17. Follow the Device Library Wizard procedure to complete the installation. The
Device Library Wizard will automatically navigate to the main window after
the process is completed.
If, during installation the Device Library Wizard main window becomes hidden
in the background:
• Open Windows Task Manager.
• Select the Device Library Wizard in the Applications tab.
• Select: Windows > Bring to Front
18. Exit the Device Library Wizard and repeat the procedure on the other 800xA
System nodes, if applicable.
19. Perform the Configure OPC P/H Server on the 800xA 5.1 Primary Aspect
Server.

3BSE036342-510 C 111
Device Management and Fieldbuses Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

Device Management FOUNDATION Fieldbus

Do not change the IP address of the OPC server FF during the online plant
update. Changing the HSE IP address of the PC changes the HSE Default
Gateway entry in the HSE subnet network configuration dialog, which in turn
reboots all CI860 at subsequent configuration downloads.
Perform the following to complete updating Device Management FOUNDATION
Fieldbus.
1. Update LD 800HSE Linking Devices: Update all LD 800HSE linking devices
to the latest firmware version released for this system environment following
the update procedure described in the user instructions for the particular device.
Refer to Field IT, Foundation Fieldbus Linking Device, LD 800HSE, Version
Table (3BDS009910) in ABB SolutionsBank for the latest linking device
firmware released for this system environment.
From Downloads Explorer, navigate to:
Control Products and Systems/800xA/Device Management Foundation
Fieldbus/Foundation Fieldbus Linking Device LD800HSE
2. Check, Save, and Upload FF Libraries:
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Object Type Structure.
c. Use the Object Browser to navigate to:
FF Libraries, Object Type Group
d. Select FF Management in the Aspect List Area.
e. Click Open Project.
f. Check the libraries for plausibility.
g. Exit Fieldbus Builder FF and save changes if prompted to do so.
h. Return to the Plant Explorer Workplace and click the Library Upload tab
in the Preview Area.
i. If the traffic light symbol shows red, click Upload FF Library.
j. The green traffic light symbol indicates that the FF libraries have been
synchronized.

112 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Device Management and Fieldbuses

3. Optional: Reconstruct User-made Changes to Library Objects representing FF

Standard Blocks:
This step is only required if changes were made to library objects representing FF
standard blocks.
During upgrade, user-made changes to library objects representing FF
standard blocks have been overwritten. Important substitutions have been
logged.
a. If such changes were made, display the substitutions as follows:
– Open a Plant Explorer Workplace.
– Use the Structure Selector to open the Object Type Structure.
– Use the Object Browser to navigate to:
FF Libraries, Object Type Group
– Select FF Upload in the Aspect List Area.
– Select Warnings tab.
b. For reconstructing user-made changes, reapply the changes to the library
objects manually.
4. Check, Save, Commission, and Upload the HSE Subnet.
Perform the following procedure for each HSE Subnet.

a. Open a Plant Explorer Workplace.

b. Use the Structure Selector to open the Control Structure.
c. Use the Object Browser to navigate to:
HSE Subnet
d. Select FF Upload in the Aspect List Area.
e. Click the HSE Subnet Reference tab in the Preview Area.
f. Click Open Subnet in Fieldbus Builder FF.
g. Check to see if the configured HSE subnet ID is used for the OPC Server
FF configuration in FF Network > Properties and modify it if required.

3BSE036342-510 C 113
Device Management and Fieldbuses Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

h. Check whole project for plausibility.

i. If required, perform device assignment for all linking devices LD
800HSE. Typically, no device assignment is lost during the upgrade.
j. If required, perform precommissioning/commissioning for all objects for
which this is necessary (discernible from engineering status). A
precommissioning may be required if the firmware has been
changed.
To assign all H1 devices in one step, use the Assign all devices function from the
HSE Subnet context menu: Object > Assign all devices...
For downloading use the online dialog from the HSE Subnet context menu:
Object > Online Dialog...
k. Exit Fieldbus Builder FF and save changes if prompted to do so.
l. Return to the Plant Explorer Workplace and select FF Upload in the
Aspect List Area.
m. If the traffic light symbol shows red, click Upload HSE Subnet.
n. The green traffic light symbol indicates that the HSE Subnet has been
synchronized.
5. Check whether the blocks of used devices from 800xA 5.0 SP2 use the
datatype bitstring and that the value is uploaded into the configuration
database. Upload these parameters from the device to the configuration
database again.
Perform the following procedure for each HSE Subnet:
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Control Structure.
c. Use the Object Browser to navigate to HSE Subnet.
d. Select FF Management in the Aspect List Area.
e. Click Open Project to open the subnet in FBB FF.
f. Identify the devices containing Function Block with Parameter datatype as
bitstring.
g. Upload all parameters of datatype bitstring from the device to the
configuration database.

114 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online PROFINET IO Feature Pack 1.2

6. Import the locally stored parameter value sets as follows:

a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Object Type Structure.
c. Use the Object Browser to navigate to:
FF Libraries, Object Type Group
d. Select FF Management in the Aspect List Area.
e. Click Open Project to open the FF Libraries project in Fieldbus Builder
FF.
f. Open the block properties dialog for the Function Block where the
parameters were exported during the pre-upgrade procedure.
g. Right-click on the dialog box and select Import from the context menu.
h. Browse the .csv file and restore the value sets.
Ensure that the stored value sets are imported to the corresponding Function
Blocks.
i. Right-click and select Store parameter value set from the context menu.
j. Specify an appropriate name for the new value set and click OK.
k. Click Cancel. Do NOT overwrite the Initial Instance Parameters with the
imported parameters, and then close the block properties dialog box.

PROFINET IO Feature Pack 1.2

Some settings on CI871 are reset to default values when performing the upgrade of
PROFINET IO Feature Pack 1.2 to 800xA 5.1. The following are affected:
• Default Gateway.
• Red.Eth.recovery time.
• Watchdog factor.
Check the CI871 settings after upgrade and enter the previous values if the settings
are changed.

3BSE036342-510 C 115
800xA for Advant Master and 800xA for Safeguard Section 3 Upgrading 800xA 5.0 SP2 to 800xA

800xA for Advant Master and 800xA for Safeguard

Perform the following post upgrade procedures for 800xA for Advant Master and
800xA for Safeguard.
• Copy the Advant Master Controller Licenses.txt.
• Copy the DATHR Files.
• Reconfigure RTA Board Control Aspect Settings.

Copy the Advant Master Controller Licenses.txt

Perform the following on the Primary Aspect Server in the 800xA 5.1 System:
1. Copy the following updated file:
• Advant Master Controller Licenses.txt
The default location to copy the file in the 800xA 5.1 system:
...\Program Files\ABB Industrial IT\Operate IT\AC 400
Connect\Licenses

Copy the DATHR Files

Perform the following on each Connectivity Server node:
1. Copy the saved files:
– DATHR1.CD
– DATHR2.CD
– DATHR3.CD
to the folder:
...\ProgramData\ABB\AC400Connect\AdvantBase\Data\
RTA\Init\
to the node where they belong.

Reconfigure RTA Board Control Aspect Settings

1. Open the MB 300 RTA Settings dialog box in Configuration Wizard and
reconfigure:
– MB 300 Node and Network Numbers.

116 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online 800xA for Harmony

– Check 800xA as Clock Master (REVERSED_SYNC_MODE) in case

the time synchronization key REVERSED_SYNC_MODE was
previously enabled.
2. Always Restart the RTA board.
3. The Audible property must be 0 for events and 1 for alarms 800xA for Advant
Master version 4.1 SP1 RU6 and newer. Refer to System 800xA Configuration
(3BDS011222*) for configuration of audible alarms.
Safeguard standardevent 300 - 326 does not comply with this rule before
800xA for 800xA for Advant Master Version 5.0 SP2. The Event numbers
where the Audible property should be changed from 1 to 0 are:
– EVENT302.
– EVENT305.
– EVENT310.
– EVENT312.
– EVENT320.
– EVENT321.
– EVENT322.
– EVENT325.

800xA for Harmony

Use the following procedure to restore 800xA for Harmony information:
1. Log in to the 800xA Installing User account (or a local Administrator account)
on the Configuration Server or Configuration Server with Connectivity Server
node.
2. Restore the 800xA for Harmony Configuration information that was saved
during 800xA for Harmony on page 86.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for OCS
Systems > Harmony > Configuration > Restore Configuration
b. Click Connect in the Harmony Connect Configuration Backup/Restore
window.

3BSE036342-510 C 117
800xA for AC 870P/Melody Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

c. Enter the name of the Harmony Configuration Server database backup file
in the Backup File field.
d. Click Restore.
e. If a prompt appears indicating that the system version does not match the
backup version, click Yes.
f. If the message Services must be stopped, REBOOT system now
then restart this application! is displayed, restart the node and
repeat Step a through Step e.
g. The Backup/Restore program compares the old configuration in the
backup file to the current configuration of the newly installed system. If
the hosts of the Primary and Redundant Connectivity Servers do not
match, a dialog box will appear allowing the user to map the old
Connectivity Server node names to the new Connectivity Server node
names.
h. Leave the Create Missing Servers in Installed Configuration (Disaster
Recovery) check box disabled.
i. Click Exit when the restore operation is complete.

800xA for AC 870P/Melody

Restore existing backups for project specific changes (if available) for: (Refer
also to 800xA for AC 870P/Melody on page 87.)
• DHCP Server Configuration.
• ETC Host files for 800xA for AC 870P/Melody Connectivity Servers.
• Changes in the Default Object Types.
• ConvDB changes of the Configuration Server.
Perform the following post upgrade procedures for 800xA for AC 870P/Melody.
• Restore 800xA for AC 870P/Melody Information.
• Additional 800xA for AC 870P/Melody Configuration Steps.

Restore 800xA for AC 870P/Melody Information

Perform the following procedure to restore 800xA for AC 870P/Melody
information:

118 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online 800xA for AC 870P/Melody

1. Log in to the 800xA Installing User account (or a local Administrator account)
on the Configuration Server node.
2. Restore the 800xA for AC 870P/Melody Configuration information that was
saved during 800xA for AC 870P/Melody on page 87.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for Melody
> Configuration > Restore Configuration
b. Click Connect in the Melody Connect Configuration Backup/Restore
window.
c. Enter the name of the Melody Configuration Server database backup file
in the Backup File field.
d. Click Restore.
e. If a prompt appears indicating that the system version does not match the
backup version, click OK.
f. If the message Services must be stopped, REBOOT system now
then restart this application! is displayed, restart the node and
repeat Step a through Step e.
g. Click Exit when the restore operation is complete.
If there are specific faceplates in use (process industries or utilities), the
faceplates must also be upgraded. Refer to the faceplate related documents for
further instructions.

Additional 800xA for AC 870P/Melody Configuration Steps

Information on performing these additional configuration steps can be found in
800xA for AC 870P/Melody Configuration (3BDD011741*) and System 800xA Post
Installation (3BUA000156*).
Perform the following configuration steps after adding the 800xA for
AC 870P/Melody Configuration Server to the 800xA System.
1. Melody Executive Service Provider.
2. Tag Importer.

3BSE036342-510 C 119
800xA for MOD 300 Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

Perform the following configuration steps after adding each 800xA for AC
870P/Melody Connectivity Server to the 800xA System.
1. Melody Executive Service Provider.
2. OPC Data Source Definition.
3. Alarm and Event Provider Setup.

800xA for MOD 300

1. Re-initialize PAS System Services on the Connectivity Server.
The PAS System Services will not start until the communications settings are
initialized as described in the following steps.
2. Initialize the OMF settings to start system services. Use the Administrative
Tools in Windows Control Panel to select:
PAS > Settings
This displays the Communications Configuration Tool.
The message:
Would you like to revert back to saved settings?
is displayed if settings were previously saved. To restore the previous settings,
perform Step a through Step d.
a. Select Yes at the message
Would you like to revert back to saved settings?
This opens the Communication Settings display.
b. Select OK on the Communication Settings display to save the settings and
close the window.
c. Select OK to the message:
Settings have been saved . ...
d. Select OK when the message appears that indicates the settings have been
changed. A restart is always required if the Control Network Setting, OMF
Memory, or TCP/IP enabled setting are changed.
3. Restart Windows at this time.

120 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online PLC Connect

4. Reverse_Time synch will be disabled following the re-installation of PAS. If

the Connectivity Server node sets the time on the Real-Time Accelerator Board
(RTAB), Reverse_Time_Synch must be enabled. Refer to the 800xA for
MOD 300 section in System 800xA Post Installation (3BUA000156*).
5. If any objects were customized, those changes must be implemented again on
objects delivered with 800xA for MOD 300 Version 5.1.
6. Update the registry settings previously recorded. Refer to 800xA for MOD 300
Configuration (3BUR002417*).

PLC Connect
Perform the following post upgrade procedures for PLC Connect.

Modify Installation for IEC 60870 or Basic Project Objects

If either the IEC 60870 or Basic Project Objects features were installed:
1. Use standard Windows procedures to access Programs and Features in
Windows Control Panel.
2. Select ABB PLC Connect.
3. Select Change/Modify.
4. The InstallShield Wizard for PLC Connect appears. Refer to System 800xA
Installation to select and install the desired features.
5. If the IEC60870 feature is installed refer to System 800xA PLC Connect
Configuration (3BSE035041*) and reload the saved IEC configuration.

Restoring the Pretreat dll

To restore the Pretreat dll:
1. If the PLC Connect Communication Server Pre Treatment function is being
used in the application, copy the Pretreat dll file (Pretreat3.dll or Pretreat4.dll)
from the backup location to the same folder as it was backed up from on the
PLC Connect Connectivity Server. If the default folder is used, that location is:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin

3BSE036342-510 C 121
Asset Optimization Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

2. Register the Pretreat dll file (refer to System 800xA PLC Connect
Configuration (3BSE035041*) for more information).
3. Restart the PLC Connect Connectivity Server for the changes to take effect.
4. Restore the project and source files for the Pretreat dll.

Update the Sattbus Configuration

Perform the following if the Sattbus protocol is used for any of the controllers:
1. Select the PLC Controller Configuration aspect for the controller that uses
Sattbus protocol and click Edit Driver.
2. Configure the Common System Settings and click OK.
3. Restart the Connectivity Server.

Redeploy the PLC Connect Configuration

To redeploy the PLC Connect configuration:
1. Use the Structure Selector to open the Control Structure in the Plant Explorer
Workplace.
2. Use the Object Browser to navigate to the first Generic Control Network
object.
3. Select Deploy in the Aspect List Area.
4. Press the SHIFT key and click Deploy in the Preview Area to ensure that a full
deploy is done.
5. The deploy begins and the progress is displayed in the Preview Area. The
deploy is completed when Deploy ended is displayed.
6. Repeat the procedure for any additional Generic Control Network objects.

Asset Optimization
Use the following procedure after updating Asset Optimization. Perform only the
steps applicable to the system.

122 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Asset Optimization

1. Asset Monitoring:
Asset Monitoring directories must be restored on every Asset Optimization
Server node defined in the system.
a. If Runtime Asset Monitors are being used in the system, restore the
Runtime Asset Monitor data directory (DeviceRunTimeMSLogicStore) to
the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
The saved data contains the Runtime Asset Monitor data present at the time of the
save. Use the Runtime Asset Monitor faceplate to reset the Asset Monitors by
adding the lost time to their accumulated run time or with some known values
based on other records. Ignore any alarms occurring during the backup.
b. If XY Profile Deviation Asset Monitors are being used in the system,
restore the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles) to the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
c. If Counter Check Asset Monitors are being used in the system, restore the
Counter Check Asset Monitors data directory named:
{66E71F7B-90D6-4E62-9881-38388B24CBDF}
from safe media. This directory exists for each AO Server in the system.
These directories are located in:
<install drive>:\OperateITData\AoEng\<AO Server ID>\
AmCat
Where each <AO Server ID> directory represents one AO Server instance
from which the directory:
{66E71F7B-90D6-4E62-9881-38388B24CBDF}
was originally saved from. The <AO Server ID> directory name is
formatted as two consecutive GUIDs, for example:
{F9C150F5-2929-4A12-BC28-E00ED6DB1585}{B925E77F-2A82-
41C6-A981-FAB4386D5701}.

3BSE036342-510 C 123
Asset Optimization Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

2. Maximo Integration:
cpmPlus Enterprise Connectivity Version 4.0 (ECS 4.0) must be installed in order
to access Maximo Server Version 6.2.
The Maximo Integration information (Maximo Equipment ID and Maximo
Credentials aspects) must be restored on all Asset Optimization Server nodes.
Reference the Service Structure for the Asset Optimization Server.
a. Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
to configure ECS.
b. If the MxDef files were customized, restore the MxDef files to the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\MxDef\
Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
for more information on MxDef files.
c. Restore the AOMaximoModel file to the following location if the ECS
model was customized:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
d. Ensure that the ABB Maximo Connectivity system extension is loaded.
The pending fault reports residing in the system can be restored to the following
directory structure:
...\OperateITData\OptaoACDs
Restore the entire OptaoACDs folder.
3. SAP/PM Integration:
cpmPlus Enterprise Connectivity Version 4.0 (ECS 4.0) must be installed in order
to access SAP Server Version 4.7.
The SAP/PM Integration information (SAP Equipment ID and SAP Credentials
aspects) must be restored on all Asset Optimization Server nodes. Reference the
Service Structure for the Asset Optimization Server.
a. Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
to configure ECS.

124 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Asset Optimization

b. If the SAPDef files were customized, restore the SAPDef files to the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\SAPPMDef
c. Restore the AOSAPModel file to the following location if the ECS model
was customized:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
Refer to Industrial IT, 800xA - Asset Optimization, Configuration
(3BUA000118*) for more information on SAPDef files.
d. Ensure that the ABB SAP Connect system extension is loaded.
The pending fault reports residing in the system can be restored to the following
directory structure:
...\OperateITData\OptaoACDs
Restore the entire OptaoACDs folder.
4. DMS Calibration Integration.
The DMS Calibration Integration approach is changed in 800xA 5.1. Upgrade of
DMS Calibration Integration is not supported. Reconfigure the DMS Calibration
Integration based on an engineered solution.
Contact ABB technical support for more information.
5. Asset Monitors that are assigned (via the Configure option drop-down list box
on the Asset Monitor Instance on an Object) to a particular AO Server object
and Asset Optimization Server aspect (by Object name:Aspect name pair), will
not be correctly configured after the upgrade. The AOServer property will be
unconfigured and the following error message will appear:
Unable to resolve AO Server for this Asset Monitor
configuration
This must be resolved before the Asset Monitor Logic can be loaded into an
AO Server:Asset Optimization Server for execution. Refer to the Object Type
Structure for Asset Optimization, Object Type Group:AO Server, Object Type.

3BSE036342-510 C 125
PC, Network and Software Monitoring Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

6. After a restore of a 800xA 5.0 SP2 system, the Asset Optimization Server
(Monitor Server/Engine) is running. The AO Server tab of the Asset
Monitoring Server aspect will show a status of good: AM Engine running.
a. Clicking the Asset Monitors tab and selecting AMs assigned to this AO
Server will show that the values in the Status column are NOT Loaded,
enabled.
b. Click Load all AMs to reload all enabled Asset Monitors assigned to this
AO Server.
:The Enable Write Access check box must be selected in the Asset Monitor Data
Source aspect before loading Runtime Asset Monitors into the AO Server. Refer
to System 800xA Asset Optimization Configuration (3BUA000118*) for more
information.

PC, Network and Software Monitoring

In the 800xA 5.1 and later releases, a set of IT Asset type objects are deprecated.
The new enhancements, Process Graphics 2 and Native Language Support (NLS),
are not applied to deprecated IT Asset type objects. Replacements of deprecated IT
Asset type objects are delivered in PNSM Device Library. It is recommended to
migrate deprecated IT Asset type objects to PNSM Device Library in case the
system being upgraded has all Process Graphics 2 graphics and no VB graphics.
Refer to Appendix F, Mapping of Deprecated IT Asset Object Types.
Migration from deprecated IT Asset type objects to the PC, Network and
Software Monitoring Device Library is not mandatory in case the system being
upgraded already has VB graphics.
The following steps describe the migration procedure.
1. Download IT Asset type objects in PNSM Device Library that replaces the
deprecated IT Asset type objects which are used in the current configuration.
The download link is http://www.abb.com/controlsystems.
2. Migrate each deprecated IT Asset type object to its replacement IT Asset type
object in PNSM Device Library
a. Instantiate and configure PNSM Device Library objects.
b. Delete deprecated IT Asset type objects.
Reconfigure all applications referring to deprecated IT Asset type objects. For
example, Logging of OPC data into history archive.

126 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online PNSM Device Library Restore Procedure

3. To upgrade to a newer version of the Light Generic Computer Process object

type, it is required to delete all old instances and replace them with the newer
version of the Light Generic Computer Process object type. Refer to the
Process Monitoring section of System 800xA PC, Network and Software
Monitoring Configuration.
Perform the following post upgrade procedure for PC, Network and Software
Monitoring.
1. If user defined Script, Resource, and Assembly files were backed up, copy the
saved files from the safe media to the following directories:
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Scripts\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Assemblies\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Resources\User
There are more PC, Network and Software Monitoring steps that need to be
performed after the system extension maintenance has been performed. Refer to
PC, Network and Software Monitoring on page 133.

PNSM Device Library Restore Procedure

Perform the following post upgrade procedure for PNSM Device Library:
1. Copy the files from the safe location to the directory if MOF files were backed
up:
...\Program Files\ABB Industrial IT\Optimize IT\PC,
Network and Software Monitoring\MOFS
2. Copy the Process Health.dll from the safe location to the following location for
Generic Computer Node V1.0 or higher versions:
...\Program Files\ABB Industrial IT\Optimize
IT\PC, Network and Software Monitoring\Asset
Monitoring\Bin

3BSE036342-510 C 127
SMS and e-mail Messaging Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

Use the Register.dll bat file present in the Object Type to register this dll
automatically.

SMS and e-mail Messaging

Reconfigure the GSM Device hardware information recorded in the save operation
(refer to SMS and e-mail Messaging on page 94).
It may be necessary to stop and start the Messenger Server Service in the Service
Structure after the SMS and e-mail Messaging restore operation.

Batch Management
Verify that the primary Batch Server is in primary mode (P is displayed in the
Windows Task bar) and the secondary Batch Server is in secondary mode (S
displayed in the Windows Task bar). If the proper modes are not displayed, enable
the Batch Service Group before proceeding.
To enable the Batch Service Group:
1. Open a Plant Explorer Workplace.
2. Select the Service Structure.
3. Select the Services\Batch Service, Service\batch_group_name, Service
Group\Service Group Definition aspect.
4. Select the Configuration tab.
5. Select the provider that is currently the secondary Batch Server.
6. Select the Enabled check box and click Apply.
7. Select the provider that is currently the primary Batch Server.
8. Select the Enabled check box and click Apply.
Batch data can be reloaded to the batch database from wherever it was archived.
The Batch history archive and restore aspect has been removed in SV5.1.

Perform the following to view any Batch data archived from SV5.0 or previous
versions of the Batch product:

128 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Basic History Service

1. Create a Virtual Machine (VM) node with the existing system version and its
components.
2. Restore Batch data using the Batch Restore window onto this virtual machine.
Once the restored data is in the batch database, it can be viewed using the Batch
History Overview window.
Do not restore directly from CDs or DVDs. Restore from hard disk drives which can
be restored from CDs or DVDs using commercially available software.

Selecting the Alarm Server

To select the Alarm Server:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to select:
Services > Event Collector, Service >
Batch_AE_Service, Service Group
4. Select Service Group Definition in the Aspect List Area.
5. Select the Special Configuration tab in the Preview Area.
6. Select Produce IT Batch OPC AE Server in the Alarm Server field.
7. Click Apply.
Always perform the Toolbar configuration as described in System 800xA Batch
Management Configuration and shutdown script procedure as described in the
Batch Management section of System 800xA Post Installation (3BUA000156*).

Basic History Service

Restore the Basic History Service data as follows. Perform this procedure on every
node where the Basic History Service is running.
1. Stop the Basic History Server from the Service Structure by the following
procedure:
a. Open a Plant Explorer Workplace.

3BSE036342-510 C 129
Calculations Service Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

b. Use the Structure Browser to open the Service Structure.

c. Select the Basic History, Service > Basic, Service Group.
d. Select the Service Group Definition aspect.
e. Click the Configuration tab.
f. Clear the Enabled check box and click Apply.
2. If it is necessary to keep historical data for the time since the upgraded system
was started, copy the current Basic History log files in the following directory:
...\OperateITData\History\{provider ID}
to a temporary directory.
These files will be inserted by using the Archive Tool.
3. Delete all files under:
...\OperateITData\History\{provider ID}
4. Restore the files from the backup of Basic History Service Data to:
...\OperateITData\History\{provider ID}
5. Start the Basic History Service from the Service Structure.
6. If Step 2 was performed:
a. Open the AdvHtArchiveTool located by default in the following directory:
...\Program Files\ABB Industrial IT\Operate IT\Process
Portal A \bin
b. Use the File/Select/Open Archive command and browse to the directory
containing the history log files.
c. Open the Action/Insert Data into Logs command.
d. Accept the default values in the Time Selection dialog box.
e. Click OK to start the insertion of the saved data to the logs.

Calculations Service
Calculations that were disabled prior to the upgrade must be enabled by selecting
the Enabled check box in the Calculations dialog box. Refer to the section on

130 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Scheduling Service (Application

Calculations in Industrial IT, 800xA - Information Management, Operation

(3BUF001094*).
To enable the Calculations Service:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Calculations Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Select the Enabled check box and click Apply.

Scheduling Service (Application Scheduler)

Schedules that were disabled prior to the upgrade must be enabled by selecting the
Enabled check box in the Scheduling dialog box. Refer to the section on
Scheduling in Industrial IT, 800xA - Information Management, Operation
(3BUF001094*).
To enable the Scheduling Service:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Scheduling Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Select the Enabled check box and click Apply.

Process Engineering Tool Integration

Use the following procedure after updating Process Engineering Tool Integration:
Restore the backed up data directory (in preparation-step prior to upgrade) to the
installed directory of Process Engineering Tool Integration. Restore the entire Xml
directory contents to:

3BSE036342-510 C 131
Miscellaneous Procedures Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

...\Program Files\ABB Industrial IT\Engineer

IT\Engineering Studio\Process Engineering Tool
Integration\Xml

Miscellaneous Procedures
Perform the following procedures:
• Upgrade Control Builder M Projects.
• PC, Network and Software Monitoring.
• Add Autostart Shortcut.

Upgrade Control Builder M Projects

After upgrading a configuration containing one Engineering and one Production
system to 800xA 5.1, the Control Builder M projects in the two systems should
be made identical using the Import/Export tool, Engineering Repository, or by
recreating the Engineering System using Backup/Restore before engineering
work is restarted. Otherwise there will be a lot of false differences on the
AC 800M aspects reported in the import difference report when moving solutions
between the systems.
800xA 5.1 has introduced a new (major) version. The 800xA 5.0 SP2 version of
BasicHWlib (5.0-2) can coexist with the new version (5.1-0) in the 800xA System,
and it must be used if any controllers are going to stay with the firmware from
800xA 5.0 SP2.
The Control Builder project upgrade will be started automatically the first time the
project is opened. It can also be explicitly triggered by starting an empty Control
Builder and selecting:
Tools > Maintenance > Upgrade Project
During the upgrade Control Builder asks if the user wants to use the new (5.1-0) or
old (5.0-2) BasicHWLib version for the controllers in the project. If the intention is
to upgrade controller firmware the new version should be selected. If the intention is
to not upgrade controller firmware the old version must be selected.

132 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online PC, Network and Software Monitoring

PC, Network and Software Monitoring

1. Perform the following steps on the PC, Network and Software Monitoring
Server node.
a. Use the Structure Selector to open the Service Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to the:
Services > OpcDA_Connector, Service > SG_IT Server
object. If there is no object to navigate to, skip to Step l (letter l, not
number 1).
c. Open the OPCDA_Provider_<servername> object and double-click on the
Service Provider Definition aspect.
d. On the Configuration tab, clear and select the Enabled check box and
click Apply. The Current field should change to Service.
e. Use the Structure Selector to open the Control Structure.
f. Use the Object Browser to navigate to the IT Server object.
g. Double-click OPC Data Source Definition in the Aspect List Area.
h. Click on the Service Group drop-down menu and select the SG_IT
Server.
i. Click on the OPCDA_Provider_<servername> which was configured in
Step c.
j. Click Apply.
k. Skip to Migrate the IT Asset Monitors (Step 2).
l. Use the Structure Selector to open the Control Structure.
m. Use the Object Browser to navigate to the IT Server object.
n. Double-click OPC Data Source Definition in the Aspect List Area.
o. Select New.
p. Click Add and select the appropriate Service Provider from the list.
q. Click OK twice.

3BSE036342-510 C 133
Add Autostart Shortcut Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

r. Click Apply.
2. Migrate the IT Asset Monitors. If Asset Optimization and PC, Network and
Software Monitoring were installed on the 800xA 5.0 SP2 System, then the
following must be done for any existing IT Assets that had IT Asset Monitors
configured for them.
a. Use the Find Tool in the Plant Explorer Workplace to locate all the IT
Asset Monitor aspect instances in the Control Structure.
b. Right-click on each of the found aspects and select Goto Object.
c. Open the IT Device Manager aspect and click Generate to recreate the IT
Asset Monitor.
d. Repeat Step c for each object in the Find list.
e. Use the Object Browser to navigate to:
Root, Domain > Asset Optimization, Asset Optimization >
AO Server 1, AO Server
f. Select Asset Optimization Server in the Aspect List Area.
g. Select the Enabled check box in the AO Server tab and click Apply.
h. Click Load all AMs in the Asset Monitors tab.
Basic Computer Monitoring will not upgrade properly from a previous version to
the current version. Use the Basic Computer Monitoring Configuration Tool to
recreate the configuration.

Add Autostart Shortcut

If it is desired to enable the autostart of the Operator Workplace on client nodes,
perform the following:
1. Define a default workplace.
2. The shortcut must be created from the ABB Workplace login window.
3. The shortcut is located in:
...:\Documents and Settings\UserName\Start
Menu\Programs\Startup
4. Right-click the shortcut and select Properties from the context menu.

134 3BSE036342-510 C
Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online Online Upgrade of a Multisystem

5. Add the following to the shortcut target:

/WS
-or-
/WaitForSystem
6. Click OK.

Online Upgrade of a Multisystem Integration System

Perform the following to upgrade a Multisystem Integration 800xA System online.
1. Refer to Online Upgrade on page 61 and perform all steps for the Subscriber
System.
2. Refer to Online Upgrade on page 61 and perform all steps for each Provider
System where it is desired to perform an upgrade.

System Backup
Make complete hard disk and 800xA System backups of the upgraded system.

3BSE036342-510 C 135
System Backup Section 3 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Online

136 3BSE036342-510 C
 Section 4 Upgrading 800xA 5.0 SP2 to
800xA 5.1 Offline

Introduction
Upgrading the 800xA System from 800xA 5.0 SP2 to 800xA 5.1 for systems
without redundant Aspect and Connectivity Servers requires the plant to be shut
down. To guarantee the functionality of the upgraded system, follow the upgrade
instructions for the installed products and perform them in the order presented.
Refer to the 800xA for Harmony section of System 800xA Release Notes New
Functions and Known Problems (2PAA106188*) before upgrading an 800xA 4.1
System if 800xA for Harmony is installed on any node in the system.
Unless otherwise indicated, the person performing this upgrade must use the same
user account that was used during the installation of the 800xA System software.

Considerations
The following considerations must be taken into account before performing the
upgrade.
• Unless otherwise indicated, the person performing this upgrade must use the
same user account that was used during the installation of the 800xA System
software.
• To guarantee the functionality of the upgraded system, follow these
instructions carefully and perform them in a well defined order.
• It is recommended that a disk image be taken of all disks on each node before
beginning and after completing the upgrade.
• Backing up the aspect directory (800xA System Backup), reports, history data,
graphics, and other application data is required before performing the upgrade.

3BSE036342-510 C 137
Control Builder M Compatibility Issues Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

• Take an inventory of all software on all nodes in the 800xA System before
performing the upgrade.

Control Builder M Compatibility Issues

Refer to the compatibility issues detailed in Appendix B, Control Builder M
Compatibility Issues before beginning the upgrade.

Upgrade Flow
This section is organized so that the instructions are presented in the proper upgrade
order. Do not skip any steps that pertain to 800xA software being used in the current
or upgraded system. Refer to Planning for the Upgrade on page 33 for additional
information and ideas on how to streamline the upgrade process.

Central Licensing System

Order the 800xA licenses required for the current system version and revision.
The 800xA 5.0 SP2 licenses will not work.

System Upgrade
Perform the following to upgrade the 800xA System.
1. Document all Windows settings including the domain, DNS, policies, users,
etc.
2. Refer to the Diagnostics Collection Tool section in System 800xA Tools
(2PAA101888*) and run the Software Analyzer from the Primary Aspect
Server in the 800xA 5.0 SP2 System. This allows for an analysis of the
software installed on the different nodes in the 800xA System with an
opportunity to correct errors in the 800xA 5.0 SP2 System before upgrading.
This is especially helpful when using the System Installer to generate setup
packages based on the 800xA 5.0 SP2 System. If there is missing or incorrect
software in that version, the System Installer will duplicate that installation in
the 800xA 5.1 System.

138 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline System Upgrade

3. Refer to Appendix C, Consistency Check and perform the necessary

consistency checks.
Perform a consistency check before performing the 800xA System backup.
Failure to do so could result in problems when restoring the system after the
upgrade.
4. Refer to Appendix D, Recording the Number of Aspects and Objects and
record the number of aspects and objects in the system before performing the
800xA System Backup.
5. It is important to create backups of node hard disks and the 800xA System
before starting the upgrade procedures. Valid backups insure that the system
can be restored if necessary.
a. It is recommended that a third party backup/restore and/or disk imaging
utility be used to save (and restore if necessary) all disks on each node
before starting the upgrade procedures.
b. This step only applies to installations with IEC 61850 Connect installed
that use a user-defined Graphic Library for applications. Ensure that
inheritance is enabled for all aspects in that library and an upload
operation is performed before taking the 800xA System backup.
c. Perform the 800xA full backup from the Maintenance Structure (Aspect
Directory backup type).
Avoid engineering or any other changes especially to the Aspect system during
the 800xA Backup process.
The 800xA Backup/Restore function makes it possible to make an online
backup of a node and perform an offline restore of the same node. A full
backup stores all aspect objects and aspect data (application data) in the
Aspect Directory.
Verify the Batch Management Servers are operating normally before and during
800xA System backups of systems containing Batch Management nodes. This
will ensure the backup of all batch data.
All system extensions that are part of the system must be installed and
loaded on the node where the backup will be taken (usually the primary
Aspect Server node). No changes can be made (especially to the Aspect
directory) during the 800xA Backup process.

3BSE036342-510 C 139
System Upgrade Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

When backing up a system with Environments, both the Production and

Engineering Environments will be included in the backup. Only the
current version of each aspect will be included in the backup. This means
that all version history will be removed.
It is only possible to perform the 800xA System backup from the Production
Environment.
– Open a Plant Explorer Workplace.
– Use the Structure Selector to open the Maintenance Structure.
– Create a Full Backup Definition object.
– Configure the Scope and Storage tabs.
– Check the disk space and path in the Storage tab. A large configuration
could require a minimum of five gigabytes of free space.
– Start the backup process.

– Refer to the How to Make a Full Backup topic in System 800xA

Maintenance (3BSE046784*) for more detailed information on performing
the 800xA System Backup.
If using the System Installer to perform the upgrade, generate the setup packages
before shutting down services.
6. Refer to Pre-Upgrade Procedures on page 142 and perform the pre-upgrade
procedures that are applicable to the installed system.
7. Perform the following procedure to shut down the 800xA System:
a. Stop all external clients to the 800xA System (OPC DA, HDA, and AE
clients that access the 800xA System) before a system shutdown.
b. From the Configuration Wizard, select System Administration and click
Next.
c. Select the system to stop and click Next.
d. Select Systems and click Next.
e. From the Systems dialog box, select Stop and click Next.

140 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline System Upgrade

f. From the Apply Settings dialog box, click Finish.

The 800xA System will shut down within a couple of minutes. The time it takes
to shut down may be more or less depending on the size of the 800xA System.
8. Reformat the hard drives of all 800xA System nodes.
9. Install the new operating system defined for the 800xA 5.1 System on all
800xA System nodes. Click Advanced when installing Windows 7 or
Windows Server 2008. This is required to delete the existing partition and
recreate a new one. Failure to perform this step will leave old data on the hard
drive.
10. Refer to Section 2 - Prerequisites in:
– Manual Upgrades - System 800xA Installation (3BSE034678*).
– Automated Upgrades using System Installer - System 800xA Automated
Installation (3BSE034679*).
and perform all procedures relating to operating system settings, Windows
service packs, miscellaneous Windows components installation, other third
party software, group policy, 800xA Service User privileges, and Windows
updates and hot fixes.
11. Refer to System 800xA Installation (3BSE034678*) and install the 800xA 5.1
Central Licensing System Server software and install the license file, as this
will be the Primary Aspect Server in the 800xA 5.1 System. This step is not
necessary if performing an automated upgrade using System Installer.
12. Refer to System 800xA Installation (3BSE034678*) and install all 800xA 5.1
System software per the software inventory taken earlier. This step is not
necessary if performing an automated upgrade using System Installer.
13. Refer to Installing the VB Graphics Extension Software on page 161 to install
Visual BASIC 6.0 with SP6 and the VB Graphics extensions if required.
14. Perform the system update to the latest release:
• It is recommended to use the System Update Tool (SUT) to perform the update
as described in System 800xA System Update Tool (2PAA106938*). Refer to
Appendix G, Update to 800xA 5.1 Rev A to perform the update manually.
OR

3BSE036342-510 C 141
Pre-Upgrade Procedures Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

Feature Pack Functionality

• Use the System Feature Pack Update Tool (FUT) to perform the update. Refer
to the System 800xA 5.1 System Feature Pack Update Tool (2PAA107435*) for
user instructions.

15. Refer to Post Upgrade Procedures on page 163 of this instruction and perform
all necessary steps.
16. Perform all of the procedures described in Miscellaneous Procedures on page
198.
17. Refer to System 800xA Post Installation (3BUA000156*) and configure
Windows Services and Windows Firewall.
18. It is important to create backups of node hard disks and the 800xA System after
completing the upgrade procedures. Valid backups insure that the system can
be restored if necessary.
a. It is recommended that a third party backup/restore and/or disk imaging
utility be used to save (and restore if necessary) all disks on each node
before starting the upgrade procedures.
b. Perform the 800xA full backup from the Maintenance Structure (Aspect
Directory backup type).

Pre-Upgrade Procedures
Some 800xA System software requires preparatory steps before shutting down
800xA System processes. Perform the applicable procedures in the order presented.

Customized Alarm Priority Mapping Aspects

Some customized Alarm Priority Mapping Aspects may be overwritten during the
upgrade. Record all values in the Alarm Priority Mapping Aspects before beginning
the upgrade so that they can be recreated after the upgrade.

800xA for AC 800M

Use the following procedure to prepare for the 800xA for AC 800M upgrade:

142 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Structured Data Logger

1. Record the service account settings in the OPC Server Setup Wizard.
2. Control Builder stores its settings (systemsetup.sys) on disk in the following
directory:
...\ABB Industrial IT Data\Engineer IT Data\Control
Builder M Professional
Copy this file to a safe media.
3. Save OPC configurations by selecting:
File > Save Configuration
in the OPC Server Panel.
4. The OPC Server stores configuration files (*.cfg) and settings
(systemsetup.sys) on disk. Copy these files to a safe media. The
systemsetup.sys file is located in:
...\ABB Industrial IT Data\Control IT Data\OPC Server
for AC 800M
The configuration files are stored in the Files folder in the same location.
5. If the system to be upgraded originates from System Baseline 2.1 and has been
upgraded in steps through system versions, verify that the Control Builder
projects do not use the old obsolete SB2 (System Baseline 2) libraries (libraries
of version 1.0-0. For example: ControlStandardLib 1.0/0.

Structured Data Logger

Use the following procedure to prepare for the Structured Data Logger (SDL)
upgrade.
1. Back up the SQL Server 2000 SDL Database.
a. Open SQL Server Enterprise Manager.
b. Right-click SDL data base and select All Tasks > Backup Database…
from the context menu.
c. Save the backup file (with .bak extension) to a safe location.

3BSE036342-510 C 143
Engineering Studio Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

Engineering Studio
Use the following procedures to prepare for the Engineering Studio upgrade.
The Function Designer system extensions:
• Signal Extension for AC800M Connect
• Function Designer for AC800M Connect
• Topology Designer for AC800M Connect
• CI Extension for AC800M Connect
• Signal Extension for TRIO Connect
• Topology Designer for AC800M High Integrity
• Function Designer for AC 800M Classic
• Topology Designer for AC800M Classic
• Function Designer for Fieldbus Builder Profibus/Hart
• AC 800M Signal Extension Classic
mainly consist of:
• Functional Planning Object Types, including a Function Settings aspect at the
Settings Object Type Group.
• Extension Libraries that add Function Designer aspects to Object Types
(Control Modules, Function Blocks, etc.) created by basic libraries (AC800M
Connect, AC 800M Classic, etc.).
After having loaded such a system extension in the 800xA 5.0 SP2 System, some of
these aspects may have been modified; for example, to adapt Function Settings, or
to change the color or layout of Function Blocks in Function Diagrams. During the
800xA System upgrade to 800xA 5.1 the system extensions of the new system are
loaded. To keep the information about modified aspects, all aspects that were
created by a Function Designer system extension, but later on modified are listed in
the Configuration Wizard log, and are written to Afw files.
The only way to bring these modifications back into the 800xA 5.1 System is to
manually merge the changes. Do not import the listed Afw files into the 800xA 5.1
System, because some additional properties/data might get lost. In the case of

144 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Device Management FOUNDATION

Function Settings, look for each settings property in the 800xA 5.0 SP2 System and
perform the modifications again in the 800xA 5.1 System. In the case of modified
Function Aspects (e.g. Diagram Template, Component Template), check the
modifications done in the 800xA 5.0 SP2 System and perform the modifications
again in the 800xA 5.1 System.

Device Management FOUNDATION Fieldbus

Perform the following to prepare for the Device Management FOUNDATION
Fieldbus upgrade.
• User-Made Modifications to Library Objects Representing FF Standard
Blocks.
• Exporting Locally Stored Parameter Value Sets.

User-Made Modifications to Library Objects Representing FF Standard Blocks

User-made modifications to library objects representing FF standard blocks (these
are blocks supported by the Device Type Standard FBs as indicated in the Block
Info tab of the block class parameter dialog box) will be overwritten during
upgrade. If such changes have been made, they can be reconstructed manually.
Refer to Device Management FOUNDATION Fieldbus on page 179.

Exporting Locally Stored Parameter Value Sets

Export the locally stored parameter value sets as follows:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Object Type Structure.
3. Use the Object Browser to navigate to:
FF Libraries, Object Type Group
4. Select FF Upload in the Aspect List Area.
5. Click Open Library in Fieldbus Builder FF.
6. Select the Function Block from FF Block Library > Function Blocks
in the Library view.
7. Double-click on the Function Block to open the properties dialog box for the
chosen Function Block.

3BSE036342-510 C 145
PROFINET IO Feature Pack 1.2 Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

8. Right-click and select Export from the context menu (Figure 12).

Figure 12. Exporting Locally Stored Parameter Value Sets

9. Specify the name and location of the .csv file and Click OK.

PROFINET IO Feature Pack 1.2

Some settings on CI871 are reset to default values when performing the upgrade of
PROFINET IO Feature Pack 1.2 to 800xA 5.1. The following are affected:
• Default Gateway.
• Red.Eth.recovery time.
• Watchdog factor.

146 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline 800xA for Advant Master and 800xA for

Check the CI871 settings after upgrade and enter the previous values if the settings
are changed.

800xA for Advant Master and 800xA for Safeguard

Perform the following to prepare for the 800xA for Advant Master and 800xA for
Safeguard upgrade.
• Save the Advant Master Controller Licenses.txt.
• Save the DATHR Files.
• Document the RTA Board Control Aspect Settings.

Save the Advant Master Controller Licenses.txt

Perform the following on the Primary Aspect Server in the 800xA 5.0 SP2 System:
1. Save the following file to a safe location.
– Advant Master Controller Licenses.txt
The default location for the file is:
...\Program Files\ABB Industrial IT\Operate IT\AC 400
Connect\Licenses

Save the DATHR Files

Perform the following on each 800xA for Advant Master and 800xA for Safeguard
Connectivity Server node:
1. Save the following files to a safe location:
– DATHR1.CD
– DATHR2.CD
– DATHR3.CD
from the folder:
...\Program Files\ABB Industrial IT\OperateIT\AC 400
Connect\AdvantBase\Data\RTA\Init\
and record which files belong to which node.

3BSE036342-510 C 147
800xA for Harmony Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

Document the RTA Board Control Aspect Settings

Perform the following on each 800xA for Advant Master and 800xA for Safeguard
Connectivity Server node:
1. Document the following settings in the RTA Board Control aspect for
reconfiguration after the upgrade.
– MB300 node and network address.
– 800xA as Clock Master (REVERSED_SYNC_MODE) check box.

800xA for Harmony

Perform the following to prepare for the 800xA for Harmony upgrade.

Disable Harmony Services on 800xA for Harmony Servers

Stop the following 800xA for Harmony services on the 800xA for Harmony Server
node being upgraded.
1. Select:
Start > Control Panel > Administrative Tools > Services
2. Disable the following services:
– Time synchronization daemon.
– SoapSymTagAtomSrv.
– EbDataSyncService.
– EbServerBroker.
– ABBDiagnosticService.
– DD_xxxx - Where xxxx identifies the semAPI or hAPI device being used
(this may or may not exist).
Perform the following steps to disable these services:
a. Locate the service in the Services list.
b. Double-click the service to open the Properties dialog box for that service.
c. Change the Startup type to Disabled.
d. Click Apply and then OK.
e. Repeat for each of the services listed.
3. Restart the 800xA for Harmony Server node.

148 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline 800xA for AC 870P/Melody

Save 800xA for Harmony Information

Use the following procedure to save 800xA for Harmony information:
1. Create a backup of the Configuration Server database.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for OCS
Systems > Harmony > Configuration > Backup Configuration
b. Click Connect.
c. Click Browse to name the backup file and choose a location to save it.
d. Click Backup.
e. Click Exit when the backup is complete.

800xA for AC 870P/Melody

Back up project specific changes (if applicable):
• DHCP Server Configuration.
• ETC Host files for Melody Connectivity Servers.
• Changes in the Default Object Types (e.g. manual changes for permissions
in Control Connection Aspects).
• ConvDB changes only on Configuration Server (change to the directory
...\Program Files\ABB Industrial IT\Configuration\Melody Tag Importer\.. and
backup the files MELCONVERTER.BAT, ConvDB.mdb and
ConvDB_<Hostname>.mdb.
ConfigServer node: Ensure that no Commissioning will be done from the
Melody Composer during this upgrade.
Use the following procedure to save 800xA for AC 870P/Melody information:
1. Log in to the 800xA Service account on the Configuration Server node.
a. Create a backup of the Configuration Server database.
b. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for Melody
> Configuration > Backup Configuration

3BSE036342-510 C 149
800xA for MOD 300 Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

c. Click Connect.
Save the backup file to a safe media like a network share or removable disk.
Otherwise, the file will be deleted once an upgrade occurs due to a reload of the
node.
d. Click Backup.
e. Click Exit when the backup is complete.

800xA for MOD 300

Ensure that the configuration data noted in the Customized Data for Backup
appendix in 800xA for MOD 300 Configuration (3BUR002417*) has been recorded.

IEC 61850 Connect

Make backups for the IEC 61850 CET OPC Server projects. Refer to Section 6 of
System 800xA IEC 61850 Configuration (9ARD171387*) to export CET OPC
Server projects.
Handling of IET/CCT projects and PCM 600 projects is not described here as
they are external tools contributing to the IEC 61850 workflow. They do not
reside on 800xA System nodes.

PLC Connect
1. If the PLC Connect IEC 60870 feature is installed and configured, the IEC
configuration must be saved. Refer to the section on configuring the IEC 60870
driver in System 800xA PLC Connect Configuration (3BSE035041*) for more
information.
2. If the PLC Connect Communication Server Pre Treatment function is being
used in the application (refer to System 800xA PLC Connect Configuration
(3BSE035041*) for more information), make a backup of the Pretreat dll
(Pretreat3.dll or Pretreat4.dll, be sure to select the version used). The Pretreat
dll is located in the following folder on the PLC Connect Connectivity Server:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
The path is the default location of the file. If it has been placed somewhere else,
make a backup from that location.

150 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Asset Optimization

3. Make a backup of the application project and source files for the Pretreat dll.

Engineering Studio IO Allocation

Deactivate the auto update mode in IO Allocation.
1. Start the Engineering Workplace.
2. Open the IO Allocation tool on any object by right-clicking on the object and
selecting Advanced > IO Allocation from the context menu that appears.
3. Verify that no check mark symbol is visible in the Options > Autoupdate
CBM menu item in the IO Allocation tool.

Asset Optimization
Preparing for the Asset Optimization upgrade requires backing up data to a safe
media.
Use the following procedure to back up Asset Optimization information (perform
only the steps applicable to the system):
1. Asset Monitoring:
Asset Monitoring directories will be found on every Asset Optimization Server
node and any other node defined as an Asset Monitoring Server.
a. If Runtime Asset Monitors are being used in the system, save the Runtime
Asset Monitor data directory (DeviceRunTimeMSLogicStore) to a safe
media. This directory stores the runtime information calculated by the
Runtime Asset Monitors running in this node. This directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
b. If XY Profile Deviation Asset Monitors are being used in the system, save
the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles) to a safe media. This directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
c. If Counter Check Asset Monitors are being used in the system, save the
Counter Check Asset Monitors data directory named:

3BSE036342-510 C 151
Asset Optimization Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

{66E71F7B-90D6-4E62-9881-38388B24CBDF}
to safe media. This directory exists for each AO Server in the system.
These directories are located in:
<install drive>:\OperateITData\AoEng\<AO Server ID>\
AmCat\<Counter Check ID>
Where each <AO Server ID> directory represents one AO Server instance
running on the selected node. The <AO Server ID> directory name is
formatted as two consecutive GUIDs, for example:
{F9C150F5-2929-4A12-BC28-E00ED6DB1585}{B925E77F-2A82-
41C6-A981-FAB4386D5701}.
For correct system operation it is important that only the directories identified by
the Counter Check Asset Monitor category GUID be saved, as other data in the
tree structure above these directories will not be consistent with a restore.
2. Maximo Integration:
If using Maximo Integration, the Maximo Integration information (Maximo
Equipment ID and Maximo Credentials aspects) must be saved from all Asset
Optimization Server nodes. Refer the Service Structure for the name of the
Asset Optimization Server nodes.
a. The MxDef files provide the mapping between the 800xA System
environment and the Maximo system. If the MxDef files were customized
per the instructions in Industrial IT, 800xA - Asset Optimization,
Configuration (3BUA000118*), back up the customized MxDef files to
safe media.
– The customized MxDef Files for Maximo versions 4.1 and 4.1.1 are
located in the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\
– The customized MxDef files for Maximo version 5.1 and 5.2 are located
in the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\Maximo5\MxServer

152 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Asset Optimization

– The customized MxDef files for Maximo version 6.2 are located in the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\MaximoDef
b. Back up the AOMaximoModel.xml file to a safe location. A backup of
AOMaximoModel.xml is necessary because the ECS model for Maximo
also needs to be modified if the MXDef files are customized.
The model file is available at the following location:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
The pending fault reports residing in the system are available in the following
directory structure:
...\OperateITData\OptaoACDs
Backup the entire OptaoACDs folder.
3. SAP/PM Integration:
If using SAP/PM Integration, the SAP/PM Integration information (SAP
Equipment ID and SAP Credentials aspects) must be saved from all Asset
Optimization Server nodes. Reference the Service Structure for the name of the
Asset Optimization Server nodes.
a. Although the SAP/PM system is separate from the 800xA System, it is a
good idea to back up the system in use. Follow SAP/PM standard
practices for SAP/PM system backup.
b. The SAPPMDef files provide the mapping between the 800xA System
environment and the SAP/PM system. If the SAPDef files were
customized per the instructions in Industrial IT, 800xA - Asset
Optimization, Configuration (3BUA000118*), back up the customized
SAPDef files to safe media.
The customized SAPPMDef files for SAP version4.7 are located under:
...\Program Files\ABB Industrial IT\Optimize IT\
Asset Optimization\AOECSConnector\SAPPMDef
c. Back up the AOSAPModel.xml file to a safe location. A backup of
AOSAPModel.xml is necessary because the ECS model for SAP also
needs to be modified if the SAPPMDef files are customized.

3BSE036342-510 C 153
PC, Network and Software Monitoring Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

The model file is available at the following location:

...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
The pending fault reports residing in the system are available in the following
directory structure. Backup the entire OptaoACDs folder.
...\OperateITData\OptaoACDs
4. DMS Calibration Integration:
The DMS Calibration Integration approach is changed in 800xA 5.1. Upgrade of
DMS Calibration Integration is not supported. Reconfigure the DMS Calibration
Integration based on an engineered solution.
Contact ABB technical support for more information.

PC, Network and Software Monitoring

Use the following procedure to prepare for the PC, Network and Software
Monitoring upgrade.
1. If there are user defined Script, Resource, and Assembly files they need to be
backed up. The user files are located in:
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Scripts\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Assemblies\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Resources\User directory
Copy the files in these directories to a safe location.
2. Shut down the PC, Network and Software Monitoring Server node.
a. Use the Structure Selector to open the Service Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to:

154 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline PC, Network and Software Monitoring

Services > OpcDA_Connector, Service > SG_IT Server,

Service Group > OPCDA_Provider_Node Name, Service
Provider
(where Node Name is the name of the PC, Network and Software
Monitoring Server node).
c. Select Service Provider Definition in the Aspect List Area.
d. Click the Configuration tab to produce a view in the Preview Area.
e. If the Enabled check box is selected, clear it and click Apply.

PC, Network and Software Monitoring Device Library

Use the following procedure to prepare PC, Network and Software Monitoring
Device Library upgrade:
1. Back up MOF files (if they exist) to a safe location. The MOF files are located
in:
...\Program Files\ABB Industrial IT\Optimize IT\PC,
Network and Software Monitoring\MOFS
2. Back up Process Health.dll to a safe location if Generic Computer Node V1.0
or higher versions are loaded. The dlls are located in:
...\Program Files\ABB Industrial IT\Optimize
IT\PC, Network and Software Monitoring\Asset
Monitoring\Bin

SMS and e-mail Messaging

Save all GSM Device hardware information. Record information for the GSM
device on the SMS and e-mail Messaging GSM Hardware Setup Worksheet shown
in Table 4.

Table 4. SMS and e-mail Messaging GSM Hardware Setup Worksheet

Item Setting/Value
Spooler Settings
Activate Outbox Spooler Checked (check and leave checked)

3BSE036342-510 C 155
SMS and e-mail Messaging Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

Table 4. SMS and e-mail Messaging GSM Hardware Setup Worksheet (Continued)

Item Setting/Value
Activate Inbox Spooler Checked (check and leave checked)
Interval for Checking for Incoming Value: _____ Seconds Minutes (circle 1)
Messages
Port Settings
COM Port Value: COM _____
Baud Rate Value: _____
Data Bits Value: _____
Parity Value: _____
Stop Bits Value: _____
PIN and Properties
Query PIN Checked or Unchecked (circle one)
PIN (only if Query PIN is checked) Value: ___________________
Save PIN (only if Query PIN is Checked or Unchecked (circle one)
checked)
Own Number (telephone number of Value: ___________________
SIM card (including Country Code)
in GSM hardware)
Initialization String for GSM Hardware Value:
_______________________________
_______________________________
_______________________________
_______________________________

156 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Batch Management

Table 4. SMS and e-mail Messaging GSM Hardware Setup Worksheet (Continued)

Item Setting/Value
General Service Properties
Name (GSM service provider) Value: ___________________
Port Value: COM _____
SMSC Value: ___________________
Default Country Code Value: ___________________
Default Prefix Value: ___________________
Number of Attempts Value: ___________________
Splitting Service Properties
Splitting Checked or Unchecked (circle one)
Optimize Splitting Checked or Unchecked (circle one)
Enumerate Splitting Checked or Unchecked (circle one)
Narrowband Sockets Checked or Unchecked (circle one)
Messaging Service Properties
Add Before Message Blank (verify and do not change)
Use for Delivery Notification Only Unchecked (verify and do not change)
Default Option 0 (verify and do not change)
Message General Properties
Replace CR LF for Incoming Checked or Unchecked (circle one)
Messages

Batch Management
1. Verify all scheduled batches are completed or terminated.
2. Disable the Batch Alarm & Event Service Group and Batch Service Group
before proceeding. To disable the service groups:

3BSE036342-510 C 157
Information Management Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

a. Open a Plant Explorer Workplace.

b. Use the Structure Selector to open the Service Structure.
c. Use the Object Browser to select:
Services > Event Collector, Service >
batch_group_name, Service Group
d. Select Service Group Definition in the Aspect List Area.
e. Select the Configuration tab in the Preview Area.
f. Clear the Enabled check box and click Apply.
g. Determine the name of the nodes that are currently Primary and
Secondary Batch Servers,
h. Use the Object Browser to select:
Services > Batch Service, Service > batch_group_name,
Service Group
i. Select Service Group Definition in the Aspect List Area.
j. Select the Configuration tab in the Preview Area.
k. Select the provider that is currently the Secondary Batch Server.
l. Clear the Enabled check box and click Apply.
m. Select the provider that is currently the Primary Batch Server.
n. Clear the Enabled check box and click Apply.

Information Management
Refer to Information Management Pre-Upgrade Procedures on page 421 in
Appendix E, Information Management Upgrade to perform the Information
Management pre-upgrade procedures.

Scheduler Service (Application Scheduler)

Disable Schedules before stopping the servers and performing the upgrade. This is
performed only once and not on every node. The Schedules will need to be
manually enabled following the upgrade.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.

158 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Calculations Service

3. Select the Scheduling Service Object.

4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Clear the Enabled check box and click Apply.

Calculations Service
Disable Calculations before stopping the servers and performing the upgrade. This
is performed only once and not on every node. The Calculations will need to be
manually enabled following the upgrade.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Calculations Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Clear the Enabled check box and click Apply.

Basic History Service Data

Back up the Basic History folder for each Basic History Service Provider in the
Service Structure. Depending on the system, the Basic History Service data can
be present on a number of different node types (Connectivity Servers, IM Servers,
AO Servers, etc.). It is best to search for the directory described in this procedure
on all nodes, and if there is data present, back up that data.
To save Basic History Service data:
1. Stop the Basic History Server from the Service Structure.
2. Use Windows Backup (not the 800xA Backup) to backup the files in the:
...\OperateITData\History\{provider ID}
directory.
3. Start the Basic History Server again from the Service Structure.

3BSE036342-510 C 159
Process Engineering Tool Integration Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

Process Engineering Tool Integration

Back up Process Engineering Tool Integration information. The project data is
located in the following directory:
...\Program Files\ABB Industrial IT\Engineer
IT\Engineering Studio\Process Engineering Tool
Integration\Xml
Save the entire Xml data directory to a safe media such as a network share or
removable disk. The directory contains the default mapping files (*.dmf) modified
on the project, accelerator files (*.acc), and configuration files (*.pcf and *.fcf).

Requirements for VB Graphics Extension Software

Perform these procedures only if the restored system makes use of VB graphics.

• Installing Visual BASIC 6.0 with SP6 must be followed for all nodes that use
Graphics Builder and the Primary Aspect Server node. This must be done
before performing the procedures under 800xA System Restore
• Installing the VB Graphics Extension Software must be followed for each VB
Graphics extension software package on all nodes in the 800xA 5.1 System,
if the base product was installed on the 800xA 5.0 SP2 System. This must
be done before performing the procedures under 800xA System Restore
To deploy VB Graphics, the user must belong to the Application Engineer
IndustrialIT user group and Windows Local Administrators.

Refer to System 800xA Engineering, Process Graphics Migration Tool for

information on migrating VB Graphics to Process Graphics 2.

Installing Visual BASIC 6.0 with SP6

Use of an Aero Theme with Windows 7 will lead to screen latency issues in the
VB Graphics Builder. This is because the Aero theme uses advanced rendering
schemes. Turn off the Windows Aero theme and switch to either none or
Windows Classic for use of VB Graphics. The behavior of VB IDE in Windows 7
will then be the same as that in Windows XP.
All nodes that use the Graphics Builder and the Primary Aspect Server node need a
Professional or Enterprise Edition of Visual BASIC 6.0 with SP6. The licensed copy

160 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Installing the VB Graphics Extension

used on the 800xA 5.0 SP2 System must be installed on the 800xA 5.1 System.
Follow the installation procedure provided with Visual BASIC.

Installing the VB Graphics Extension Software

Perform the following procedure to install the VB Graphics extension software on
all nodes in the 800xA 5.1 System, if the base product was installed on the 800xA
5.0 SP2 System.
1. Insert System Installation DVD 1 into the drive.
2. Wait for the Installation AUTORUN screen to appear.
3. Select:
Manual Installation > VB Graphics Extensions

3BSE036342-510 C 161
Installing the VB Graphics Extension Software Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1

as shown in Figure 13.

Figure 13. Installation AUTORUN Screen

4. Select a VB Graphics extension to install (the installation of the Batch

Management VB Graphics extensions is described later in this procedure).
5. The Installation Wizard for the selected VB Graphics extension appears.
6. Follow the Installation Wizard to complete the installation. Choose Typical as
the installation type.
7. Repeat the procedure for each required VB Graphics extension that appears in
the Installation AUTORUN Screen.

162 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Post Upgrade Procedures

8. This step only applies to the VB Graphics extensions for Batch Management
when using System Installer to upgrade the 800xA System. If Batch
Management was installed manually during the upgrade, the VB Graphics
extensions for Batch Management were installed at that time.
a. Select:
Manual Installation > Batch Management
b. The Installation Wizard for Batch Management appears.
c. Select Modify when the dialog box appears that offers that choice.
d. Select to install the Batch Management VB Graphics extensions in the
Installation Type dialog box.
e. Follow the Installation Wizard to complete the installation.

Post Upgrade Procedures

The remainder of this section describes how to:
• Migrate the Structured Data Logger SQL Database.
• Restore the backups of the IEC 61850 CET OPC Server projects.
• Perform the 800xA Restore procedure.
• Perform a consistency check.
• Load the VB Graphics extensions on the Primary Aspect Server.
• Restore historical data.
• Restore the necessary data for each Functional Area.

Migrating the Structured Data Logger SQL Database

Perform the following post upgrade procedure for Structured Data Logger (SDL).
Upgrading SDL from 800xA 5.0 SP2 to 800xA 5.1 involves transfer of database
data from SQL Server 2000 to SQL Server 2008.
1. Open Microsoft SQL Management Studio and connect to the
SDL_INSTANCE server.
2. Delete SDL database from SDL_INSTANCE if already created during the
installation.

3BSE036342-510 C 163
IEC 61850 Connect Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

3. Restore the SDL database using the .bak file (from SQL Server 2000) that was
stored to a safe location during the pre-upgrade process.
a. Right-click Databases and select Restore Database… from the context
menu.
b. Select the From Device option and browse for the .bak file that was stored
to a safe location during the pre-upgrade process.
c. Select/Enter SDL in To database and click OK.
4. Use Windows Explorer to navigate to:
...\Operate IT\Structured Data Logger\vbs
5. Double-click RunCreateScripts_SDL.vbs. This will upgrade the SDL
database schema.
6. After performing the 800xA System Restore on page 165, verify that the SDL
Control Application exists in the system and that the SDL Log aspects contain
data.

IEC 61850 Connect

Restore the backups of the IEC 61850 CET OPC Server projects. Refer to Section 6
of System 800xA IEC 61850 Configuration (9ARD171387*).
Handling of IET/CCT projects and PCM 600 projects is not described here as
they are external tools contributing to the IEC 61850 workflow. They do not
reside on 800xA System nodes.

164 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline 800xA System Restore

800xA System Restore

Refer to Requirements for VB Graphics Extension Software on page 160 before
performing the 800xA System Restore.

The User Account that is used for 800xA System restore via the Configuration
Wizard must be a member of the following groups:
• IndustrialITUser.
• IndustrialITAdmin.
• Local Administrators.
The backup/restore utility supports the restoring of 800xA system information. The
following steps outline the 800xA system restore procedure.
Refer to System 800xA Maintenance (3BSE046784*) for more information on
restoring the system.
1. Start the restore procedure.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > System >
Configuration Wizard
b. The Select Type of Configuration dialog box appears. Select Restore
System and click Next.
Restart the node when advised during the restore procedure.

2. Check for messages in the log file (enable the View Log check box in the
Configuration Wizard). Refer to Appendix A, Warning and Error Messages to
resolve any received warning or error messages.
3. Check the CPU load in the node. The System Message service may generate a
high load (>90%). If this continues for longer than approximately 10 minutes,
restart the service.
If a message stating that a full deploy of the Generic Control Network is needed,
click OK.
4. One node at a time, start up and connect all nodes to the 800xA System in the
following order:

3BSE036342-510 C 165
800xA System Restore Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

– Aspect Server nodes.

– Connectivity Server nodes.
– Application Server nodes.
– Client nodes.
a. Use the following guidelines while connecting nodes, using the
Configuration Wizard. This must be performed on the node that is going to
be connected, not on the node on which the restore was performed.
b. Select the Primary Aspect Server (the server on which the system will run)
in the Connect to another System on Node drop down-list box, in the
Connect to System dialog box.
c. If the node is an IM Server, verify that the ABB Process Administration
Service (PAS) is set to manual in the Services Control Panel (run
Services.msc from the Run dialog box). Stop the service if it is running.
d. Select Connect Node from the Select Type of Configuration dialog box.
e. Set the current system as the default system when connecting nodes to the
system.
– In some cases, problems may be encountered when connecting nodes to
the system. Verify that the system software user settings are correct using
the Configuration Wizard. Restarting the node again may also solve the
problem.
– Wait until all services in the newly connected node are up and running
before connecting the next node. Select the Node Administration
Structure\connected_node_name\System Status Viewer aspect to monitor
the status of services. If some services will not start up, restarting the node
may help.
Do not include services that were stopped manually as part of the pre-upgrade
procedures. These will be manually restarted later in the post upgrade procedures.
f. Restart each node after it has been connected to the system.
Run the System Software User Settings until OK. Restart if it is not working and
if the message:
Invalid User
appears.

166 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Consistency Check

5. Refer to Appendix D, Recording the Number of Aspects and Objects and

record the number of aspects and objects in the system. Compare these values
to those recorded when the system was backed up.
6. Verify the affinity settings to ensure best system performance. Refer to System
800xA Post Installation (3BUA000156*) for more information on how to
configure affinity.

Consistency Check
Refer to Appendix C, Consistency Check and perform the necessary consistency
checks.

Loading the VB Graphics Extensions

Perform this procedure only if the restored system makes use of VB graphics.

Perform the following procedure on the Primary Aspect Server to load the VB
Graphics extensions:
1. Refer to Table 5 for a list of VB Graphics extensions available to be loaded.

Table 5. VB Graphics Extensions

Directory Software
800xA Connectivities AC 800M Connect VB Graphics Extension
ABB 800xA for Advant Master VB Graphics Extension
5.1.0/0
ABB 800xA for Harmony VB Graphics Extension 5.1.00
ABB 800xA for IEC61850 VB Graphics Extension
ABB 800xA for MOD 300 VB Graphics Extension
ABB 800xA for Safeguard VB Graphics Extension 5.1.0/0
ABB PLC Connect VB Graphics Extension 5.1.00

3BSE036342-510 C 167
Loading the VB Graphics Extensions Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

Table 5. VB Graphics Extensions (Continued)

Directory Software
Asset Optimization ABB Asset Optimization VB Graphics Extension 5.1
ABB PC, Network and Software Monitoring VB Graphics
Extension
Batch Management Batch VB Graphics Extension
Batch Advanced Templates VB Graphics Extension
Device Management & Fieldbuses ABB Device Management FOUNDATION Fieldbus VB
Graphics Extension

2. Start the Configuration Wizard from the primary Aspect Server node. Select:
Start > All Programs > ABB Industrial IT 800xA > System >
Configuration Wizard
3. Open the System Extension Load dialog box by going to:
System Administration > Select System > System Extension Load
4. A view appears with the available VB Graphics extensions listed in the left
pane. Select the system extension to load in the list in the left pane and move it
to the list in the right pane by clicking >. To move all the system extensions
from the left pane to the right pane, click >>.
5. The red cross, green check mark, and warning icons indicate the status of the
dependency evaluation.
– The green check mark indicates that the system extension must be loaded
first.
– The red cross icon indicates that the system extension can not be loaded
until the one with the green check mark icon is loaded.
– The warning icon indicates that the system extension can be loaded, but
that there is additional information available in the Description frame in
the lower part of the dialog box. The additional information can, for
example, be that the system extension contains aspect types that are not
environment aware.

168 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Customized Alarm Priority Mapping

6. If the list in the right pane contains more than one system extension, click
Press header to autosort to sort the system extension load order with regard to
dependencies.
7. All system extensions in the right pane should be marked with the green check
mark or the warning icon.
8. Click Next and the Apply Settings dialog box appears.
9. Click Finish to load all system extensions.
10. A progress dialog box is shown during the load. Click View Log to view log
messages during load.
The load is aborted if:
• The user clicks Abort.
• An error occurs; for example, if the Configuration Wizard fails to load a file
into the system.
An aborted system extension load can be resumed from the System Extension
Maintenance dialog box.
11. When the load operation is finished, click Finished and view the Configuration
Wizard log to verify that no errors occurred during the load.
12. Close the Configuration Wizard.

Customized Alarm Priority Mapping Aspects

Some customized Alarm Priority Mapping Aspects may have been overwritten
during the upgrade. Recreate the Alarm Priority Mapping Aspects using the data
recorded during Customized Alarm Priority Mapping Aspects on page 142.

Reconfiguring Group Displays

New Group Display aspects that are created and configured in the Object Type
Structure on the object types and instances in 800xA 5.1 will work correctly even if
there is more than one aspect with the same name but each aspect has a different
Aspect Category.
Configured Group Display aspects that existed in the Object Type Structure and
on the object types and instances in 800xA 5.0 SP2 should have their Aspect
Categories reconfigured for the aspects to display correctly. (This is required for the
reference to an aspect to be stored along with its Category ID.)

3BSE036342-510 C 169
Upgrading Faceplates Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

Upgrading Faceplates
The Faceplate aspects created in all versions prior to 800xA 5.1 use a different
method to identify the references to faceplate elements or other properties than
those in 800xA 5.1.
Upgrading a faceplate is optional, but is strongly recommended for the following
reasons:
• Better runtime performance, as no name server access is required when a
faceplate is opened.
• More reliable because the references continue to work even if the target object
is renamed.
• Upgraded faceplates function efficiently with the Consistency Checker and
Reference Tool. This behaves similar to a Process Graphics 2 graphic aspect.
• The upgrade to new reference handling can also repair some broken references.
Refer to the Upgrading Faceplates appendix in System 800xA Engineering Process
Graphics (3BSE049230*) for the procedure to upgrade the faceplates.

800xA for AC 800M

Use the following procedure to restore 800xA for AC 800M information:
1. Use the OPC Server Setup Wizard to enter the previously used and recorded
service account settings.
2. Control Builder stores its settings (systemsetup.sys) on disk in the following
directory:
...\ABB Industrial IT Data\Engineer IT Data\Control
Builder M Professional
Copy the previously saved file from the safe media to this folder.

Engineering Studio
Perform the following post upgrade procedures for Engineering Studio:
• Check and Repair AES Variable Table.
• Engineering Studio Function Designer System Extensions

170 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Engineering Studio

• Deleting Engineering Base Service from the Service Structure.

Check and Repair AES Variable Table

The Check and Repair AES Variable Table (Applications, Controllers,
Diagrams/SCMs, and Diagram (Cm) Types) function can be used to:
• Correct possible inconsistent data used for display of online values and external
cross references.
• Delete obsolete data and reduce aspect size.
Perform the following procedure to use this application.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Object Type Structure.
3. Use the Object Browser to navigate to:
Object Types > Functional Planning > Settings
4. Select Function Upgrade in the Aspect List Area to open the Function
Upgrade aspect in the Preview Area.
5. Select the Check and Repair AES Variable Table (Applications,
Controllers, Diagrams/SCMs, and Diagram (Cm) Types) check box and
click Apply.
6. Click Run Upgrade to perform this upgrade.
Executing the Check and Repair AES Variable Table procedure makes the
environment support work for Function Designer.

Upgrade Diagram References and Diagram Variables

In the 800xA 5.1 System (opposite to the 800xA 5.0 SP2 System) Diagram
References and Diagram Variables are by default created as Symbol Objects. This is
not true for Diagram References and Diagram Variables created during upgrade
(restore) from 800xA 5.0 SP2 Systems. Convert them from Aspect Objects to

3BSE036342-510 C 171
Engineering Studio Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

Symbol Objects by use of the conversion function described in the following

procedure.
Differences between Aspect Objects and Symbol Objects are described in
Industrial IT, 800xA -Engineering, Engineering Workplace, Function Designer
(3BDS011224*).
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Object Type Structure.
3. Use the Object Browser to navigate to:
Object Types > Functional Planning > Settings
4. Select Function Upgrade in the Aspect List Area to open the Function
Upgrade aspect in the Preview Area.
5. Select the Convert Diagram References/Variables from Aspect Objects to
Symbol Objects check box and click Apply.
6. Click Run Upgrade to perform the upgrade.
This function is not suitable in the case of additional aspects on input/output
references, e.g. Graphic Elements, for typical diagrams with input/output
references that will get copied and connected via the Bulk Data Manager.

Engineering Studio Function Designer System Extensions

Refer to Engineering Studio on page 144 and recreate the configuration changes that
were recorded before the upgrade.

Deleting Engineering Base Service from the Service Structure

When the 800xA System is running, delete the Engineering Base Service from the
Service Structure.
1. Use Windows Explorer to navigate to the following directory:
...\Program Files\ABB Industrial IT\Engineer IT\
Engineering Studio\DocumentParameterManager\
bin\support
2. Double-click EbServiceCleanUpUtil.exe to delete the service.

172 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Device Management and Fieldbuses

Device Management and Fieldbuses

Perform the post upgrade procedures for Device Management and fieldbuses.

Restore Device Types

Third party software, such as Device Type Managers for the Device Type must be
reinstalled since the hard drive of the 800xA System node has been reformatted.
The following steps for Fieldbus Device Types need to be carried out on every
800xA system node. Perform the System Restore Wizard procedure on the nodes in
the following sequence:
• Aspect Servers (including redundant Aspect Servers).
• Connectivity Servers (including redundant Connectivity Servers).
• Application Servers.
• Clients.
Restore the Device Types on the Primary Aspect Server node before starting to
install them on other system nodes. Do not run parallel installations of Device
Types on other system nodes unless all Device Types are restored on the Primary
Aspect Server node. Installation of Device Types on other system nodes can be
done in parallel after they are restored on the Primary Aspect Server node.
If the system contains FOUNDATION Fieldbus Device Types, check the
following before proceeding to the next step:
• Open a Plant Explorer Workplace.
• Use the Structure Selector to open the Object Type Structure > FF
Libraries.
• Check to see if there is more than one entry of FF H1 Device Library,
FF Object Type Group.
• If there is more than one entry, perform FF Upload once so there is only one
instance of FF H1 Device Library, FF Object Type Group
present. If there is only one entry, proceed to the next step using the Device
Library Wizard.
1. Start the Device Library Wizard. Select:
Start > All Programs > ABB Industrial IT 800xA > Device Mgmt >
Device Library Wizard
-or-

3BSE036342-510 C 173
Device Management and Fieldbuses Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

double-click the Device Library Wizard icon on the desktop.

If the Device Library Wizard - Client has not been connected to the Device
Library Wizard - Server, navigate first to:
Device Library Wizard Administration > Connect Client
and follow the Device Library Wizard Procedure
2. Select the Enable Trace File check box as shown in Figure 14.

Figure 14. Enabling the Trace File

3. Navigate to:
Device Type Administration > System Restore Wizard

174 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Device Management and Fieldbuses

4. Choose the second option in the System Restore Wizard as shown in Figure 15
and click Next.

Figure 15. System Restore Wizard (1)

5. Choose the first option as shown in Figure 16 and click Next.

Figure 16. System Restore Wizard (2)

3BSE036342-510 C 175
Device Management and Fieldbuses Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

6. Depending on which fieldbus protocol is used in the previous system version

environment, insert one of the delivered Device Library system DVDs in the
DVD drive (e.g. Device Library HART – DVD).
7. Click Browse and navigate to the DVD drive.
8. When the drive has been selected in the Browse for folder dialog box, click OK
in that dialog box and then Next in the ABB Device Library Wizard. This step
may take one or two minutes to complete.
9. The Device Library Wizard scans the 800xA System for fieldbus device types
that are already used and compares the results with the contents of the DVD.
Device Types available in the 800xA System and the DVD are shown in the
Extract tab of the Device Library Wizard (Figure 17).

Figure 17. Extract Device Type Files

10. Device Types available in the 800xA System but not on the DVD are displayed
in the Missing tab. If there are any Device Types showing in the Missing tab,
navigate to the Browse dialog box by clicking Back and inserting a new Device
Library DVD in the DVD drive.
11. Click Next to start the extraction process.
12. Repeat Step 6 to Step 11 for each fieldbus protocol if more than one fieldbus
protocol is used.

176 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Device Management and Fieldbuses

13. There may be some Object Types that are either customer created, or are the
latest Device Types downloaded from ABB SolutionsBank. These will not be
available on the DVDs. The Device Library Wizard will prepare a list for these
Device Types (Figure 18). Install these Device Types manually.

Figure 18. List of Files to be Manually Installed

14. Repeat this procedure until all Device Types are extracted to the 800xA System
node and the Missing tab does not list any device types.
During extraction, if a dialog box pops up asking for an overwrite, select No and
continue.
15. If the Device Library DVDs do not contain all Device Types used in the
previous system version, the missing Device Types must be downloaded from
ABB SolutionsBank.
It is only possible to complete the Wizard if all Device Types have been
successfully extracted.

3BSE036342-510 C 177
Device Management and Fieldbuses Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

16. When the extraction process is completed successfully, the Device Types need
to be re-installed on the 800xA System node. Click Next to launch the Re-
installation of Device Types dialog box shown in Figure 19.

Figure 19. Re-install Device Types Dialog Box

17. Follow the Device Library Wizard procedure to complete the installation. The
Device Library Wizard will automatically navigate to the main window after
the process is completed.
If, during installation the Device Library Wizard main window becomes hidden
in the background:
• Open Windows Task Manager.
• Select the Device Library Wizard in the Applications tab.
• Select: Windows > Bring to Front
18. Exit the Device Library Wizard and repeat the procedure on the other 800xA
System nodes, if applicable.

Device Management PROFIBUS & HART

Perform the Configure OPC P/H Server on the Primary Aspect Server.

178 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Device Management and Fieldbuses

Device Management FOUNDATION Fieldbus

Perform the following to complete updating Device Management FOUNDATION
Fieldbus.
1. Update LD 800HSE Linking Devices: Update all LD 800HSE linking devices
to the latest firmware version released for this system environment following
the update procedure described in the user instructions for the particular device.
Refer to Field IT, Foundation Fieldbus Linking Device, LD 800HSE, Version
Table (3BDS009910) in ABB SolutionsBank at for the latest linking device
firmware released for this system environment.
From Downloads Explorer, navigate to:
Control Products and Systems/800xA/Device Management Foundation
Fieldbus/Foundation Fieldbus Linking Device LD800HSE
2. Check, Save, and Upload FF Libraries:
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Object Type Structure.
c. Use the Object Browser to navigate to:
FF Libraries Object Type Group
d. Select FF Management in the Aspect List Area.
e. Click Open Project.
f. Check the libraries for plausibility.
g. Exit Fieldbus Builder FF and save changes if prompted to do so.
h. Return to the Plant Explorer Workplace and click the Library Upload tab
in the Preview Area.
i. If the traffic light symbol shows red, click Upload FF Library.
j. The green traffic light symbol indicates that the FF libraries have been
synchronized.
3. Optional: Reconstruct User-made Changes to Library Objects representing FF
Standard Blocks:
This step is only required if changes were made to library objects representing FF
standard blocks.

3BSE036342-510 C 179
Device Management and Fieldbuses Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

During upgrade, user-made changes to library objects representing FF

standard blocks have been overwritten. Important substitutions have been
logged.
a. If such changes were made, display the substitutions as follows:
– Open a Plant Explorer Workplace.
– Use the Structure Selector to open the Object Type Structure.
– Use the Object Browser to navigate to:
FF Libraries Object Type Group
– Select FF Upload in the Aspect List Area.
– Select Warnings tab.
b. For reconstructing user-made changes, reapply the changes to the library
objects manually.
4. Check, Save, Commission, and Upload the HSE Subnet.
Perform the following procedure for each HSE Subnet.

a. Open a Plant Explorer Workplace.

b. Use the Structure Selector to open the Control Structure.
c. Use the Object Browser to navigate to:
HSE Subnet
d. Select FF Upload in the Aspect List Area.
e. Click the HSE Subnet Reference tab in the Preview Area.
f. Click Open Subnet in Fieldbus Builder FF.
g. Check to see if the configured HSE subnet ID is used for the OPC Server
FF configuration in FF Network > Properties and modify it if required.
h. Check whole project for plausibility.
i. If required, perform device assignment for all linking devices LD
800HSE. Typically, no device assignment is lost during the upgrade.

180 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Device Management and Fieldbuses

j. If required, perform precommissioning/commissioning for all objects for

which this is necessary (discernible from engineering status). A
precommissioning may be required if the firmware has been
changed.
To assign all H1 devices in one step, use the Assign all devices function from the
HSE Subnet context menu: Object > Assign all devices...
For downloading use the online dialog from the HSE Subnet context menu:
Object > Online Dialog...
k. Exit Fieldbus Builder FF and save changes if prompted to do so.
l. Return to the Plant Explorer Workplace and select FF Upload in the
Aspect List Area.
m. If the traffic light symbol shows red, click Upload HSE Subnet.
n. The green traffic light symbol indicates that the HSE Subnet has been
synchronized.
5. Check whether the blocks of used devices from 800xA 5.0 SP2 use the
datatype bitstring and that the value is uploaded into the configuration
database. Upload these parameters from the device to the configuration
database again.
Perform the following procedure for each HSE Subnet:
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Control Structure.
c. Use the Object Browser to navigate to HSE Subnet.
d. Select FF Management in the Aspect List Area.
e. Click Open Project to open the subnet in FBB FF.
f. Identify the devices containing Function Block with Parameter datatype as
bitstring.
g. Upload all parameters of datatype bitstring from the device to the
configuration database.
6. Import the locally stored parameter value sets as follows:
a. Open a Plant Explorer Workplace.

3BSE036342-510 C 181
800xA for Advant Master and 800xA for Safeguard Section 4 Upgrading 800xA 5.0 SP2 to

b. Use the Structure Selector to open the Object Type Structure.

c. Use the Object Browser to navigate to:
FF Libraries, Object Type Group
d. Select FF Management in the Aspect List Area.
e. Click Open Project to open the FF Libraries project in Fieldbus Builder
FF.
f. Open the block properties dialog for the Function Block where the
parameters were exported during the pre-upgrade procedure.
g. Right-click on the dialog box and select Import from the context menu.
h. Browse the .csv file and restore the value sets.
Ensure that the stored value sets are imported to the corresponding Function
Blocks.
i. Right-click and select Store parameter value set from the context menu.
j. Specify an appropriate name for the new value set and click OK.
k. Click Cancel. Do NOT overwrite the Initial Instance Parameters with the
imported parameters, and then close the block properties dialog box.

800xA for Advant Master and 800xA for Safeguard

Perform the following post upgrade procedures for 800xA for Advant Master and
800xA for Safeguard.
• Copy the Advant Master Controller Licenses.txt.
• Copy the DATHR Files.
• Reconfigure RTA Board Control Aspect Settings.

Copy the Advant Master Controller Licenses.txt

Perform the following on the Primary Aspect Server in the 800xA 5.1 System:
1. Copy the following updated file:
• Advant Master Controller Licenses.txt
The default location to copy the file in the 800xA 5.1 system:

182 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline 800xA for Advant Master and 800xA for

...\Program Files\ABB Industrial IT\Operate IT\AC 400

Connect\Licenses

Copy the DATHR Files

Perform the following on each Connectivity Server node:
1. Copy the saved files:
– DATHR1.CD
– DATHR2.CD
– DATHR3.CD
to the folder:
...\ProgramData\ABB\AC400Connect\AdvantBase\Data\
RTA\Init\
to the node where they belong.

Reconfigure RTA Board Control Aspect Settings

1. Open the MB 300 RTA Settings dialog box in Configuration Wizard and
reconfigure:
– MB 300 Node and Network Numbers.
– Check 800xA as Clock Master (REVERSED_SYNC_MODE) in case
the time synchronization key REVERSED_SYNC_MODE was
previously enabled.
2. Always Restart the RTA board.
3. The Audible property must be 0 for events and 1 for alarms 800xA for Advant
Master version 4.1 SP1 RU6 and newer. Refer to System 800xA Configuration
(3BDS011222*) for configuration of audible alarms.
Safeguard standardevent 300 - 326 does not comply with this rule before
800xA for 800xA for Advant Master Version 5.0 SP2. The Event numbers
where the Audible property should be changed from 1 to 0 are:
– EVENT302.
– EVENT305.
– EVENT310.

3BSE036342-510 C 183
800xA for Harmony Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

– EVENT312.
– EVENT320.
– EVENT321.
– EVENT322.
– EVENT325.

800xA for Harmony

Use the following procedure to restore 800xA for Harmony information:
1. Log in to the 800xA Installing User account (or a local Administrator account)
on the Configuration Server or Configuration Server with Connectivity Server
node.
2. Restore the 800xA for Harmony Configuration information that was saved
during 800xA for Harmony on page 148.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for OCS
Systems > Harmony > Configuration > Restore Configuration
b. Click Connect in the Harmony Connect Configuration Backup/Restore
window.
c. Enter the name of the Harmony Configuration Server database backup file
in the Backup File field.
d. Click Restore.
e. If a prompt appears indicating that the system version does not match the
backup version, click Yes.
f. If the message Services must be stopped, REBOOT system now
then restart this application! is displayed, restart the node and
repeat Step a through Step e.
g. The Backup/Restore program compares the old configuration in the
backup file to the current configuration of the newly installed system. If
the hosts of the Primary and Redundant Connectivity Servers do not
match, a dialog box will appear allowing the user to map the old
Connectivity Server node names to the new Connectivity Server node
names.

184 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline 800xA for AC 870P/Melody

h. Leave the Create Missing Servers in Installed Configuration (Disaster

Recovery) check box disabled.
i. Click Exit when the restore operation is complete.

800xA for AC 870P/Melody

Restore existing backups for project specific changes (if available) for: (Refer
also to 800xA for AC 870P/Melody on page 149.)
• DHCP Server Configuration.
• ETC Host files for 800xA for AC 870P/Melody Connectivity Servers.
• Changes in the Default Object Types.
• ConvDB changes of the Configuration Server.
Perform the following post upgrade procedures for 800xA for AC 870P/Melody.
• Restore 800xA for AC 870P/Melody Information.
• Additional 800xA for AC 870P/Melody Configuration Steps.

Restore 800xA for AC 870P/Melody Information

Perform the following procedure to restore 800xA for AC 870P/Melody
information:
1. Log in to the 800xA Installing User account (or a local Administrator account)
on the Configuration Server node.
2. Restore the 800xA for AC 870P/Melody Configuration information that was
saved during 800xA for AC 870P/Melody on page 149.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for Melody
> Configuration > Restore Configuration
b. Click Connect in the Melody Connect Configuration Backup/Restore
window.
c. Enter the name of the Melody Configuration Server database backup file
in the Backup File field.
d. Click Restore.

3BSE036342-510 C 185
800xA for MOD 300 Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

e. If a prompt appears indicating that the system version does not match the
backup version, click OK.
f. If the message Services must be stopped, REBOOT system now
then restart this application! is displayed, restart the node and
repeat Step a through Step e.
g. Click Exit when the restore operation is complete.
If there are specific faceplates in use (process industries or utilities), the
faceplates must also be upgraded. Refer to the faceplate related documents for
further instructions.

Additional 800xA for AC 870P/Melody Configuration Steps

Information on performing these additional configuration steps can be found in
800xA for AC 870P/Melody Configuration (3BDD011741*) and System 800xA Post
Installation (3BUA000156*).
Perform the following configuration steps after adding the 800xA for
AC 870P/Melody Configuration Server to the 800xA System.
1. Melody Executive Service Provider.
2. Tag Importer.
Perform the following configuration steps after adding each 800xA for AC
870P/Melody Connectivity Server to the 800xA System.
1. Melody Executive Service Provider.
2. OPC Data Source Definition.
3. Alarm and Event Provider Setup.

800xA for MOD 300

1. Re-initialize PAS System Services on the Connectivity Server.
The PAS System Services will not start until the communications settings are
initialized as described in the following steps.
2. Initialize the OMF settings to start system services. Use the Administrative
Tools in Windows Control Panel to select:
PAS > Settings

186 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline PLC Connect

This displays the Communications Configuration Tool.

The message:
Would you like to revert back to saved settings?
is displayed if settings were previously saved. To restore the previous settings,
perform Step a through Step d.
a. Select Yes at the message
Would you like to revert back to saved settings?
This opens the Communication Settings display.
b. Select OK on the Communication Settings display to save the settings and
close the window.
c. Select OK to the message:
Settings have been saved . ...
d. Select OK when the message appears that indicates the settings have been
changed. A restart is always required if the Control Network Setting, OMF
Memory, or TCP/IP enabled setting are changed.
3. Restart Windows at this time.
4. Reverse_Time synch will be disabled following the re-installation of PAS. If
the Connectivity Server node sets the time on the Real-Time Accelerator Board
(RTAB), Reverse_Time_Synch must be enabled. Refer to the 800xA for
MOD 300 section in System 800xA Post Installation (3BUA000156*).
5. If any objects were customized, those changes must be implemented again on
objects delivered with 800xA for MOD 300 Version 5.1.
6. Update the registry settings previously recorded. Refer to 800xA for MOD 300
Configuration (3BUR002417*).

PLC Connect
Perform the following post upgrade procedures for PLC Connect.

Modify Installation for IEC 60870 or Basic Project Objects

If either the IEC 60870 or Basic Project Objects features were installed:

3BSE036342-510 C 187
PLC Connect Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

1. Use standard Windows procedures to access Programs and Features in

Windows Control Panel.
2. Select ABB PLC Connect.
3. Select Change/Modify.
4. The InstallShield Wizard for PLC Connect appears. Refer to System 800xA
Installation to select and install the desired features.
5. If the IEC60870 feature is installed refer to System 800xA PLC Connect
Configuration (3BSE035041*) and reload the saved IEC configuration.

Restoring the Pretreat dll

To restore the Pretreat dll:
1. If the PLC Connect Communication Server Pre Treatment function is being
used in the application, copy the Pretreat dll file (Pretreat3.dll or Pretreat4.dll)
from the backup location to the same folder as it was backed up from on the
PLC Connect Connectivity Server. If the default folder is used, that location is:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
2. Register the Pretreat dll file (refer to System 800xA PLC Connect
Configuration (3BSE035041*) for more information).
3. Restart the PLC Connect Connectivity Server for the changes to take effect.
4. Restore the project and source files for the Pretreat dll.

Update the Sattbus Configuration

Perform the following if the Sattbus protocol is used for any of the controllers:
1. Select the PLC Controller Configuration aspect for the controller that uses
Sattbus protocol and click Edit Driver.
2. Configure the Common System Settings and click OK.
3. Restart the Connectivity Server.

Redeploy the PLC Connect Configuration

To redeploy the PLC Connect configuration:

188 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Asset Optimization

1. Use the Structure Selector to open the Control Structure in the Plant Explorer
Workplace.
2. Use the Object Browser to navigate to the first Generic Control Network
object.
3. Select Deploy in the Aspect List Area.
4. Press the SHIFT key and click Deploy in the Preview Area to ensure that a full
deploy is done.
5. The deploy begins and the progress is displayed in the Preview Area. The
deploy is completed when Deploy ended is displayed.
6. Repeat the procedure for any additional Generic Control Network objects.

Asset Optimization
Use the following procedure after updating Asset Optimization. Perform only the
steps applicable to the system.
1. Asset Monitoring:
Asset Monitoring directories must be restored on every Asset Optimization
Server node defined in the system.
a. If Runtime Asset Monitors are being used in the system, restore the
Runtime Asset Monitor data directory (DeviceRunTimeMSLogicStore) to
the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
The saved data contains the Runtime Asset Monitor data present at the time of the
save. Use the Runtime Asset Monitor faceplate to reset the Asset Monitors by
adding the lost time to their accumulated run time or with some known values
based on other records. Ignore any alarms occurring during the backup.
b. If XY Profile Deviation Asset Monitors are being used in the system,
restore the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles) to the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin

3BSE036342-510 C 189
Asset Optimization Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

c. If Counter Check Asset Monitors are being used in the system, restore the
Counter Check Asset Monitors data directory named:
{66E71F7B-90D6-4E62-9881-38388B24CBDF}
from safe media. This directory exists for each AO Server in the system.
These directories are located in:
<install drive>:\OperateITData\AoEng\<AO Server ID>\
AmCat
Where each <AO Server ID> directory represents one AO Server instance
from which the directory:
{66E71F7B-90D6-4E62-9881-38388B24CBDF}
was originally saved from. The <AO Server ID> directory name is
formatted as two consecutive GUIDs, for example:
{F9C150F5-2929-4A12-BC28-E00ED6DB1585}{B925E77F-2A82-
41C6-A981-FAB4386D5701}.
2. Maximo Integration:
cpmPlus Enterprise Connectivity Version 4.0 (ECS 4.0) must be installed in order
to access Maximo Server Version 6.2.
The Maximo Integration information (Maximo Equipment ID and Maximo
Credentials aspects) must be restored on all Asset Optimization Server nodes.
Reference the Service Structure for the Asset Optimization Server.
a. Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
to configure ECS.
b. If the MxDef files were customized, restore the MxDef files to the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\MxDef\
Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
for more information on MxDef files.
c. Restore the AOMaximoModel file to the following location if the ECS
model was customized:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions

190 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Asset Optimization

d. Ensure that the ABB Maximo Connectivity system extension is loaded.

The pending fault reports residing in the system can be restored to the following
directory structure:
...\OperateITData\OptaoACDs
Restore the entire OptaoACDs folder.
3. SAP/PM Integration:
cpmPlus Enterprise Connectivity Version 4.0 (ECS 4.0) must be installed in order
to access SAP Server Version 4.7.
The SAP/PM Integration information (SAP Equipment ID and SAP Credentials
aspects) must be restored on all Asset Optimization Server nodes. Reference the
Service Structure for the Asset Optimization Server.
a. Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
to configure ECS.
b. If the SAPDef files were customized, restore the SAPDef files to the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\SAPPMDef
c. Restore the AOSAPModel file to the following location if the ECS model
was customized:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
Refer to Industrial IT, 800xA - Asset Optimization, Configuration
(3BUA000118*) for more information on SAPDef files.
d. Ensure that the ABB SAP Connect system extension is loaded.
The pending fault reports residing in the system can be restored to the following
directory structure:
...\OperateITData\OptaoACDs
Restore the entire OptaoACDs folder.

3BSE036342-510 C 191
PC, Network and Software Monitoring Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

4. DMS Calibration Integration.

The DMS Calibration Integration approach is changed in 800xA 5.1. Upgrade of
DMS Calibration Integration is not supported. Reconfigure the DMS Calibration
Integration based on an engineered solution.
Contact ABB technical support for more information.
5. Asset Monitors that are assigned (via the Configure option drop-down list box
on the Asset Monitor Instance on an Object) to a particular AO Server object
and Asset Optimization Server aspect (by Object name:Aspect name pair), will
not be correctly configured after the upgrade. The AOServer property will be
unconfigured and the following error message will appear:
Unable to resolve AO Server for this Asset Monitor
configuration
This must be resolved before the Asset Monitor Logic can be loaded into an
AO Server:Asset Optimization Server for execution. Refer to the Object Type
Structure for Asset Optimization, Object Type Group:AO Server, Object Type.
6. After a restore of a 800xA 5.0 SP2 system, the Asset Optimization Server
(Monitor Server/Engine) is running. The AO Server tab of the Asset
Monitoring Server aspect will show a status of good: AM Engine running.
a. Clicking the Asset Monitors tab and selecting AMs assigned to this AO
Server will show that the values in the Status column are NOT Loaded,
enabled.
b. Click Load all AMs to reload all enabled Asset Monitors assigned to this
AO Server.
:The Enable Write Access check box must be selected in the Asset Monitor Data
Source aspect before loading Runtime Asset Monitors into the AO Server. Refer
to System 800xA Asset Optimization Configuration (3BUA000118*) for more
information.

PC, Network and Software Monitoring

In the 800xA 5.1 and later releases, a set of IT Asset type objects are deprecated.
The new enhancements, Process Graphics 2 and Native Language Support (NLS),
are not applied to deprecated IT Asset type objects. Replacements of deprecated IT
Asset type objects are delivered in PNSM Device Library. It is recommended to
migrate deprecated IT Asset type objects to PNSM Device Library in case the

192 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline PC, Network and Software Monitoring

system being upgraded has all Process Graphics 2 graphics and no VB graphics.
Refer to Appendix F, Mapping of Deprecated IT Asset Object Types.
Migration from deprecated IT Asset type objects to the PC, Network and
Software Monitoring Device Library is not mandatory in case the system being
upgraded already has VB graphics.
The following steps describe the migration procedure.
1. Download IT Asset type objects in PNSM Device Library that replaces the
deprecated IT Asset type objects which are used in the current configuration.
The download link is http://www.abb.com/controlsystems.
2. Migrate each deprecated IT Asset type object to its replacement IT Asset type
object in PNSM Device Library
a. Instantiate and configure PNSM Device Library objects.
b. Delete deprecated IT Asset type objects.
Reconfigure all applications referring to deprecated IT Asset type objects. For
example, Logging of OPC data into history archive.
3. To upgrade to a newer version of the Light Generic Computer Process object
type, it is required to delete all old instances and replace them with the newer
version of the Light Generic Computer Process object type. Refer to the
Process Monitoring section of System 800xA PC, Network and Software
Monitoring Configuration.
Perform the following post upgrade procedure for PC, Network and Software
Monitoring.
1. If user defined Script, Resource, and Assembly files were backed up, copy the
saved files from the safe media to the following directories:
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Scripts\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Assemblies\User

3BSE036342-510 C 193
PNSM Device Library Restore Procedure Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

...\Program Files\ABB Industrial IT\Optimize IT\

PC, Network and Software Monitoring\bin\Configuration\
Resources\User
There are more PC, Network and Software Monitoring steps that need to be
performed after the system extension maintenance has been performed. Refer to
PC, Network and Software Monitoring on page 199.

PNSM Device Library Restore Procedure

Perform the following post upgrade procedure for PNSM Device Library:
1. Copy the files from the safe location to the directory if MOF files were backed
up:
...\Program Files\ABB Industrial IT\Optimize IT\PC,
Network and Software Monitoring\MOFS
2. Copy the Process Health.dll from the safe location to the following location for
Generic Computer Node V1.0 or higher versions:
...\Program Files\ABB Industrial IT\Optimize
IT\PC, Network and Software Monitoring\Asset
Monitoring\Bin
Use the Register.dll bat file present in the Object Type to register this dll
automatically.

SMS and e-mail Messaging

Reconfigure the GSM Device hardware information recorded in the save operation
(refer to SMS and e-mail Messaging on page 155).
It may be necessary to stop and start the Messenger Server Service in the Service
Structure after the SMS and e-mail Messaging restore operation.

Batch Management
Verify that the primary Batch Server is in primary mode (P is displayed in the
Windows Task bar) and the secondary Batch Server is in secondary mode (S
displayed in the Windows Task bar). If the proper modes are not displayed, enable
the Batch Service Group before proceeding.
To enable the Batch Service Group:

194 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Batch Management

1. Open a Plant Explorer Workplace.

2. Select the Service Structure.
3. Select the Services\Batch Service, Service\batch_group_name, Service
Group\Service Group Definition aspect.
4. Select the Configuration tab.
5. Select the provider that is currently the secondary Batch Server.
6. Select the Enabled check box and click Apply.
7. Select the provider that is currently the primary Batch Server.
8. Select the Enabled check box and click Apply.
Batch data can be reloaded to the batch database from wherever it was archived.
The Batch history archive and restore aspect has been removed in SV5.1.

Perform the following to view any Batch data archived from SV5.0 or previous
versions of the Batch product:
1. Create a Virtual Machine (VM) node with the existing system version and its
components.
2. Restore Batch data using the Batch Restore window onto this virtual machine.
Once the restored data is in the batch database, it can be viewed using the Batch
History Overview window.
Do not restore directly from CDs or DVDs. Restore from hard disk drives which can
be restored from CDs or DVDs using commercially available software.

Selecting the Alarm Server

To select the Alarm Server:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to select:

3BSE036342-510 C 195
Basic History Service Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

Services > Event Collector, Service >

Batch_AE_Service, Service Group
4. Select Service Group Definition in the Aspect List Area.
5. Select the Special Configuration tab in the Preview Area.
6. Select Produce IT Batch OPC AE Server in the Alarm Server field.
7. Click Apply.
Always perform the Toolbar configuration as described in System 800xA Batch
Management Configuration and shutdown script procedure as described in the
Batch Management section of System 800xA Post Installation (3BUA000156*).

Basic History Service

Restore the Basic History Service data as follows. Perform this procedure on every
node where the Basic History Service is running.
1. Stop the Basic History Server from the Service Structure by the following
procedure:
a. Open a Plant Explorer Workplace.
b. Use the Structure Browser to open the Service Structure.
c. Select the Basic History, Service > Basic, Service Group.
d. Select the Service Group Definition aspect.
e. Click the Configuration tab.
f. Clear the Enabled check box and click Apply.
2. If it is necessary to keep historical data for the time since the upgraded system
was started, copy the current Basic History log files in the following directory:
...\OperateITData\History\{provider ID}
to a temporary directory.
These files will be inserted by using the Archive Tool.
3. Delete all files under:
...\OperateITData\History\{provider ID}

196 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Information Management

4. Restore the files from the backup of Basic History Service Data to:
...\OperateITData\History\{provider ID}
5. Start the Basic History Service from the Service Structure.
6. If Step 2 was performed:
a. Open the AdvHtArchiveTool located by default in the following directory:
...\Program Files\ABB Industrial IT\Operate IT\Process
Portal A \bin
b. Use the File/Select/Open Archive command and browse to the directory
containing the history log files.
c. Open the Action/Insert Data into Logs command.
d. Accept the default values in the Time Selection dialog box.
e. Click OK to start the insertion of the saved data to the logs.

Information Management
Refer to Information Management Post Upgrade Procedures on page 426 in
Appendix E, Information Management Upgrade to perform the Information
Management post upgrade procedures.

Calculations Service
Calculations that were disabled prior to the upgrade must be enabled by selecting
the Enabled check box in the Calculations dialog box. Refer to the section on
Calculations in Industrial IT, 800xA - Information Management, Operation
(3BUF001094*).
To enable the Calculations Service:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Calculations Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.

3BSE036342-510 C 197
Scheduling Service (Application Scheduler) Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1

6. Select the Enabled check box and click Apply.

Scheduling Service (Application Scheduler)

Schedules that were disabled prior to the upgrade must be enabled by selecting the
Enabled check box in the Scheduling dialog box. Refer to the section on
Scheduling in Industrial IT, 800xA - Information Management, Operation
(3BUF001094*).
To enable the Scheduling Service:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Scheduling Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Select the Enabled check box and click Apply.

Process Engineering Tool Integration

Use the following procedure after updating Process Engineering Tool Integration:
Restore the backed up data directory (in preparation-step prior to upgrade) to the
installed directory of Process Engineering Tool Integration. Restore the entire Xml
directory contents to:
...\Program Files\ABB Industrial IT\Engineer
IT\Engineering Studio\Process Engineering Tool
Integration\Xml

Miscellaneous Procedures
Perform the following procedures:
• Upgrade Control Builder M Projects.
• PC, Network and Software Monitoring.
• Add Autostart Shortcut.

198 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Upgrade Control Builder M Projects

Upgrade Control Builder M Projects

After upgrading a configuration containing one Engineering and one Production
system to 800xA 5.1, the Control Builder M projects in the two systems should
be made identical using the Import/Export tool, Engineering Repository, or by
recreating the Engineering System using Backup/Restore before engineering
work is restarted. Otherwise there will be a lot of false differences on the
AC 800M aspects reported in the import difference report when moving solutions
between the systems.
800xA 5.1 has introduced a new (major) version. The 800xA 5.0 SP2 version of
BasicHWlib (5.0-2) can coexist with the new version (5.1-0) in the 800xA System,
and it must be used if any controllers are going to stay with the firmware from
800xA 5.0 SP2.
The Control Builder project upgrade will be started automatically the first time the
project is opened. It can also be explicitly triggered by starting an empty Control
Builder and selecting:
Tools > Maintenance > Upgrade Project
During the upgrade Control Builder asks if the user wants to use the new (5.1-0) or
old (5.0-2) BasicHWLib version for the controllers in the project. If the intention is
to upgrade controller firmware the new version should be selected. If the intention is
to not upgrade controller firmware the old version must be selected.

PC, Network and Software Monitoring

1. Perform the following steps on the PC, Network and Software Monitoring
Server node.
a. Use the Structure Selector to open the Service Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to the:
Services > OpcDA_Connector, Service > SG_IT Server
object. If there is no object to navigate to, skip to Step l (letter l, not
number 1).
c. Open the OPCDA_Provider_<servername> object and double-click on the
Service Provider Definition aspect.

3BSE036342-510 C 199
PC, Network and Software Monitoring Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

d. On the Configuration tab, clear and select Enabled check box and click
Apply. The Current field should change to Service.
e. Use the Structure Selector to open the Control Structure.
f. Use the Object Browser to navigate to the IT Server object.
g. Double-click OPC Data Source Definition in the Aspect List Area.
h. Click on the Service Group drop-down menu and select the SG_IT
Server.
i. Click on the OPCDA_Provider_<servername> which was configured in
Step c.
j. Click Apply.
k. Skip to Migrate the IT Asset Monitors (Step 2).
l. Use the Structure Selector to open the Control Structure.
m. Use the Object Browser to navigate to the IT Server object.
n. Double-click OPC Data Source Definition in the Aspect List Area.
o. Select New.
p. Click Add and select the appropriate Service Provider from the list.
q. Click OK twice.
r. Click Apply.
2. Migrate the IT Asset Monitors. If Asset Optimization and PC, Network and
Software Monitoring were installed on the 800xA 5.0 SP2 System, then the
following must be done for any existing IT Assets that had IT Asset Monitors
configured for them.
a. Use the Find Tool in the Plant Explorer Workplace to locate all the IT
Asset Monitor aspect instances in the Control Structure.
b. Right-click on each of the found aspects and select Goto Object.
c. Open the IT Device Manager aspect and click Generate to recreate the IT
Asset Monitor.
d. Repeat Step c for each object in the Find list.

200 3BSE036342-510 C
Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline Add Autostart Shortcut

e. Use the Object Browser to navigate to:

Root, Domain > Asset Optimization, Asset Optimization >
AO Server 1, AO Server
f. Select Asset Optimization Server in the Aspect List Area.
g. Select the Enabled check box in the AO Server tab and click Apply.
h. Click Load all AMs in the Asset Monitors tab.
Basic Computer Monitoring will not upgrade properly from a previous version to
the current version. Use the Basic Computer Monitoring Configuration Tool to
recreate the configuration.

Add Autostart Shortcut

If it is desired to enable the autostart of the Operator Workplace on client nodes,
perform the following:
1. Define a default workplace.
2. The shortcut must be created from the ABB Workplace login window.
3. The shortcut is located in:
...:\Documents and Settings\UserName\Start
Menu\Programs\Startup
4. Right-click the shortcut and select Properties from the context menu.
5. Add the following to the shortcut target:
/WS
-or-
/WaitForSystem
6. Click OK.

System Backup
Make complete hard disk and 800xA System backups of the upgraded system.

3BSE036342-510 C 201
System Backup Section 4 Upgrading 800xA 5.0 SP2 to 800xA 5.1 Offline

202 3BSE036342-510 C
 Section 5 Upgrading 800xA 4.1 to 800xA 5.1
Offline

Introduction
Upgrading the 800xA System from 800xA 4.1 to 800xA 5.1 requires the plant to
be shut down. To guarantee the functionality of the upgraded system, follow the
upgrade instructions for the installed products and perform them in the order
presented.
Upgrading from 800xA 4.1 to 800xA 5.1 requires that ABB Industrial IT 800xA
Core 4.0.0-1 SP1 Rollup 5d (December 2006) or later be installed. If ABB
Industrial IT 800xA Core 4.0.0-1 SP1 Rollup 5d (December 2006) or later is not
installed, the backup/restore functionality will fail.
Refer to the 800xA for Harmony section of System 800xA Release Notes New
Functions and Known Problems (2PAA106188*) before upgrading an 800xA 4.1
System if 800xA for Harmony is installed on any node in the system.
Unless otherwise indicated, the person performing this upgrade must use the same
user account that was used during the installation of the 800xA System software.

3BSE036342-510 C 203
Functional Area Naming Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Functional Area Naming

Some 800xA Functional Area names have been changed since the 800xA 4.1
release. Table 6 lists the Functional Area names before and after the upgrade.

Table 6. Functional Area Naming

Name in 800xA 4.1 Name in 800xA 5.1

800xA for Melody 800xA for AC 870P/Melody
Control IT for AC 800M 800xA for AC 800M
FOUNDATION Fieldbus Device Integration Device Management FOUNDATION Fieldbus
HART Device Integration Device Management PROFIBUS & HART
PROFIBUS Device Integration

Considerations
The following considerations must be taken into account before performing the
upgrade.
• Unless otherwise indicated, the person performing this upgrade must use the
same user account that was used during the installation of the 800xA System
software.
• To guarantee the functionality of the upgraded system, follow these
instructions carefully and perform them in a well defined order.
• It is recommended that a disk image be taken of all disks on each node before
beginning and after completing the upgrade.
• Backing up the aspect directory (800xA System Backup), reports, history data,
graphics, and other application data is required before performing the upgrade.
• Take an inventory of all software on all nodes in the 800xA System before
performing the upgrade.

204 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Control Builder M Compatibility Issues

Control Builder M Compatibility Issues

Refer to the compatibility issues detailed in Appendix B, Control Builder M
Compatibility Issues before beginning the upgrade.

Upgrade Flow
This section is organized so that the instructions are presented in the proper upgrade
order. Do not skip any steps that pertain to 800xA software being used in the current
or upgraded system. Refer to Planning for the Upgrade on page 33 for additional
information and ideas on how to streamline the upgrade process.

Central Licensing System

Order the licenses required for the current system version and revision. The
800xA 4.1 licenses will not work.

System Upgrade
Perform the following to upgrade the 800xA System.
1. Document all Windows settings including the domain, DNS, policies, users,
etc.
2. Refer to the Diagnostics Collection Tool section in System 800xA Tools
(2PAA101888*) and run the Software Analyzer from the Primary Aspect
Server in the 800xA 5.0 SP2 System. This allows for an analysis of the
software installed on the different nodes in the 800xA System with an
opportunity to correct errors in the 800xA 5.0 SP2 System before upgrading.
This is especially helpful when using the System Installer to generate setup
packages based on the 800xA 5.0 SP2 System. If there is missing or incorrect
software in that version, the System Installer will duplicate that installation in
the 800xA 5.1 System.
3. If 800xA for MOD 300 is installed, check and delete the MOD Message Class
object before performing the 800xA System backup.

3BSE036342-510 C 205
System Upgrade Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Delete all MOD Message Class objects below the Message Classes object
located in:
Library Structure > System Messages > Message Classes
A convenient way to delete the Message Class objects is to export the Message
Classes object, delete it and its descendants, and then import the Message Classes
object back again.
4. Refer to Appendix C, Consistency Check and perform the necessary
consistency checks.
Perform a consistency check before performing the 800xA System backup.
Failure to do so could result in problems when restoring the system after the
upgrade.
5. The new support for version handling of aspect data will make all digital
signatures in 800xA 4.1 invalid when upgrading to 800xA 5.1. To simplify the
upgrade, two applications have been developed to support the re-signing of
aspects in 800xA 5.1:
• AfwSignatureReport: Used to create a report with information about signed
aspects in 800xA 4.1.
• AfwSignatureManager: Used in 800xA 5.1 to re-sign these aspects.
Perform the following before upgrading from 800xA 4.1 to 800xA 5.1.
a. Insert 800xA System Installation DVD 1 (for 800xA 5.1) into the drive on
a client in the 800xA 4.1 800xA System.
b. Copy the AfwSignatureReport.exe from the following directory on 800xA
System Installation DVD 1 to a directory on the client.
Engineering & Development\Accessories\Digital
Signatures Upgrade Tools\SV4
c. Open a Windows Command Prompt.
d. Change to the directory where AfwSignatureReport.exe was copied.
e. Run the following command:
f. AfwSignatureReport <filename>.xml

206 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline System Upgrade

g. Save the signature report file <fileName>.xml on an external media during

the upgrade.
The digital signature must be valid before saving to the report file.

6. Check that there is only one External Alarm Service Group and that their
providers run on Aspect Servers only (not on any Connectivity Server). If not
(i.e. there is more than one group and/or there are providers running on
Connectivity Servers), keep only one External Alarm Service Group and move
all providers to that group. Also make sure the providers run on the Aspect
Servers with a maximum of one provider per Aspect Server.
7. 800xA System backups containing undeployed user created process graphics
will result in warning and error messages later in the upgrade process. To avoid
these messages, refer to Industrial IT, 800xA - Engineering, Graphics
(3BSE030335*) and use the Display Tool to deploy all user created process
graphics before beginning the 800xA System backup.
8. Refer to Appendix D, Recording the Number of Aspects and Objects and
record the number of aspects and objects in the system before performing the
800xA System Backup.
9. It is important to create backups of node hard disks and the 800xA System
before starting the upgrade procedures. Valid backups insure that the system
can be restored if necessary.
a. It is recommended that a third party backup/restore and/or disk imaging
utility be used to save (and restore if necessary) all disks on each node
before starting the upgrade procedures.
b. Perform the 800xA full backup from the Maintenance Structure (Aspect
Directory backup type).
Ensure that the Post Installation Procedure for Engineering Studio 4.1.0/0
Rollup 4 (refer to Release Notes 3BDS011656R4101) has been performed. Refer
also to Technical Description - Industrial IT System 800xA SV 4.x System
Software Versions (3BSE037782* (latest revision)).
For background information refer to Product Bulletin - 800xA Eng.Workplace
Eng. Studio SV 3.1-SV 4.0, Aspect Types falsely reset (3BDS100999).

3BSE036342-510 C 207
System Upgrade Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Avoid engineering or any other changes especially to the Aspect system during
the 800xA Backup process.
The 800xA Backup/Restore function makes it possible to make an online
backup of a node and perform an offline restore of the same node. A full
backup stores all aspect objects and aspect data (application data) in the
Aspect Directory.
Verify the Batch Management Servers are operating normally before and during
800xA System backups of systems containing Batch Management nodes. This
will ensure the backup of all batch data.
All system extensions that are part of the system must be installed and
loaded on the node where the backup will be taken (usually the primary
Aspect Server node). No changes can be made (especially to the Aspect
directory) during the 800xA Backup process.
When backing up a system with Environments, both the Production and
Engineering Environments will be included in the backup. Only the
current version of each aspect will be included in the backup. This means
that all version history will be removed.
It is only possible to perform the 800xA System backup from the Production
Environment.
– Open a Plant Explorer Workplace.
– Use the Structure Selector to open the Maintenance Structure.
– Create a Full Backup Definition object.
– Configure the Scope and Storage tabs.
– Check the disk space and path in the Storage tab. A large configuration
could require a minimum of five gigabytes of free space.
– Start the backup process.

208 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline System Upgrade

– Refer to the How to Make a Full Backup topic in System 800xA

Maintenance (3BSE046784*) for more detailed information on performing
the 800xA System Backup.
If EBService timeout issues occur while taking a backup of the 800xA 4.1
System, there is a probability that the DM/PM aspects may be corrupted in the
backup files. Restoring the corrupted backup files to the 800xA 5.1 System
results in the following error message:
Import/Export Error: RestoreFromStream failed.
10. Refer to Pre-Upgrade Procedures on page 211 and perform the pre-upgrade
procedures that are applicable to the installed system.
11. Perform the following procedure to shut down the 800xA System:
a. Stop all external clients to the 800xA System (OPC DA, HDA, and AE
clients that access the 800xA System) before a system shutdown.
b. From the Configuration Wizard, select System Administration and click
Next.
c. Select the system to stop and click Next.
d. Select Systems and click Next.
e. From the Systems dialog box, select Stop and click Next.
f. From the Apply Settings dialog box, click Finish.
The 800xA System will shut down within a couple of minutes. The time it takes
to shut down may be more or less depending on the size of the 800xA System.
12. Reformat the hard drives of all 800xA System nodes.
13. Install the new operating system defined for the 800xA 5.1 System on all
800xA System nodes. Click Advanced when installing Windows 7 or
Windows Server 2008. This is required to delete the existing partition and
recreate a new one. Failure to perform this step will leave old data on the hard
drive.
14. Refer to Section 2 - Prerequisites in:
– Manual Upgrades - System 800xA Installation (3BSE034678*).

3BSE036342-510 C 209
System Upgrade Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

– Automated Upgrades using System Installer - System 800xA Automated

Installation (3BSE034679*).
and perform all procedures relating to operating system settings, Windows
service packs, miscellaneous Windows components installation, other third
party software, group policy, 800xA Service User privileges, and Windows
updates and hot fixes.
15. Refer to System 800xA Installation (3BSE034678*) and install the 800xA 5.1
Central Licensing System Server software and install the license file, as this
will be the Primary Aspect Server in the 800xA 5.1 System. This step is not
necessary if performing an automated upgrade using System Installer.
16. Refer to System 800xA Installation (3BSE034678*) and install all 800xA 5.1
System software per the software inventory taken earlier. This step is not
necessary if performing an automated upgrade using System Installer.
17. Refer to Requirements for VB Graphics Extension Software on page 230 to
install Visual BASIC 6.0 with SP6 (if required) and the VB Graphics
extensions.
18. Perform the system update to the latest release:
• It is recommended to use the System Update Tool (SUT) to perform the update
as described in System 800xA System Update Tool (2PAA106938*). Refer to
Appendix G, Update to 800xA 5.1 Rev A to perform the update manually.
OR
Feature Pack Functionality

• Use the System Feature Pack Update Tool (FUT) to perform the update. Refer
to the System 800xA 5.1 System Feature Pack Update Tool (2PAA107435*) for
user instructions.

19. Refer to Post Upgrade Procedures on page 233 of this instruction and perform
all necessary steps.
20. Perform all of the procedures described in Miscellaneous Procedures on page
275.
21. Refer to System 800xA Post Installation (3BUA000156*) and configure
Windows Services and Windows Firewall.

210 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Pre-Upgrade Procedures

22. It is important to create backups of node hard disks and the 800xA System after
completing the upgrade procedures. Valid backups insure that the system can
be restored if necessary.
a. It is recommended that a third party backup/restore and/or disk imaging
utility be used to save (and restore if necessary) all disks on each node
before starting the upgrade procedures.
b. Perform the 800xA full backup from the Maintenance Structure (Aspect
Directory backup type).

Pre-Upgrade Procedures
Some 800xA System software requires preparatory steps before shutting down
800xA System processes. Perform the applicable procedures in the order presented.

Control IT for AC 800M

Use the following procedure to prepare for the Control IT for AC 800M upgrade:
1. Control Builder stores its settings (systemsetup.sys) on disk in the following
directory:
...\ABB Industrial IT Data\Engineer IT Data\Control
Builder M Professional
Copy this file to a safe media.
2. Save OPC configurations by selecting:
File > Save Configuration
in the OPC Server Panel.
3. The OPC Server stores configuration files (*.cfg) and settings
(systemsetup.sys) on disk. Copy these files to a safe media. The
systemsetup.sys file is located in:
...\ABB Industrial IT Data\Control IT Data\OPC Server
for AC 800M
The configuration files are stored in the Files folder in the same location.

3BSE036342-510 C 211
Device Management FOUNDATION Fieldbus Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

4. If the system to be upgraded originates from System Baseline 2.1 and has been
upgraded in steps through system versions, verify that the Control Builder
projects do not use the old obsolete SB2 (System Baseline 2) libraries (libraries
of version 1.0-0. For example: ControlStandardLib 1.0/0.

Device Management FOUNDATION Fieldbus

Perform the following to prepare for the Device Management FOUNDATION
Fieldbus upgrade.
• User-Made Modifications to Library Objects Representing FF Standard
Blocks.
• Exporting Locally Stored Parameter Value Sets.

User-Made Modifications to Library Objects Representing FF Standard Blocks

User-made modifications to library objects representing FF standard blocks (these
are blocks supported by the Device Type Standard FBs as indicated in the Block
Info tab of the block class parameter dialog box) will be overwritten during
upgrade. If such changes have been made, they can be reconstructed manually.
Refer to Device Management and Fieldbuses on page 239.

Exporting Locally Stored Parameter Value Sets

Export the locally stored parameter value sets as follows:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Object Type Structure.
3. Use the Object Browser to navigate to:
FF Libraries, Object Type Group
4. Select FF Upload in the Aspect List Area.
5. Click Open Library in Fieldbus Builder FF.
6. Select the Function Block from FF Block Library > Function Blocks
in the Library view.
7. Double-click on the Function Block to open the properties dialog box for the
chosen Function Block.

212 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Device Management PROFIBUS & HART

8. Right-click and select Export from the context menu (Figure 20).

Figure 20. Exporting Locally Stored Parameter Value Sets

9. Specify the name and location of the .csv file and Click OK.

Device Management PROFIBUS & HART

Historical data sets of Device Type Manager (DTM), exported via the Fieldbus
Management aspect, along with device specific DTM files are stored as files on the
Primary Aspect Server node. These files and the PROFIBUS/HART OPC Server

3BSE036342-510 C 213
PROFIBUS Device Types Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

configuration are stored after successful 800xA System backup. The path to this
folder can be found as follows:
1. Open the Plant Explorer Workplace on the Primary Aspect Server node.
2. Use the Structure Selector to select the Control Structure.
3. Use the Object Browser to select the Root Object type.
4. Select the FBB PH Settings aspect.
5. Record the path information for the Primary Aspect Server found in the FBB
PH Settings aspect.
6. Use Windows Explorer to copy the folder (default: Fieldbus Builder PH)
containing device specific configuration files (in the path recorded in Step 5) to
the 800xA System backup folder, created as described in System 800xA
Maintenance (3BSE046784*).
7. If the folder name of the copied folder is not Fieldbus Builder PH, it must be
renamed to the default folder name (Fieldbus Builder PH) in the 800xA System
backup folder.

PROFIBUS Device Types

PROFIBUS Device Types in 800xA 5.0 and later are based on Hardware Libraries
(HWLib). This is different from previous system versions, where these Device
Types were based on Hardware Definitions (HWD). As a result, the PROFIBUS
Device Types used in connection with the Device Integration software must be
linked to new delivered Hardware Libraries to ensure system and upgrade
compatibility.
Perform the following procedure only if the exact PROFIBUS Device Type
described is used. Otherwise, this procedure can be skipped.

If the ABB_TZIDC_110-220_SP_Short module type is used in the Control Structure

of the Plant Explorer, a special upgrade procedure must be performed to ensure
upgrade compatibility in 800xA 5.0 and later. This module is delivered with the
PROFIBUS Device Integration package and its system extensions and is supported
by the ABB_TZIDC_110-220_YP0_v1_0 PROFIBUS Device Type.
The following steps requires Bulk Data Manager (BDM) (Engineering Platform)
to be installed. Perform the described steps on an Engineering system node.

214 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline PROFIBUS Device Types

1. Open the Engineering Workplace and select the Control Structure.

2. Open the Find Tool.
3. In the <Add attribute> selection box select Structure.
4. In the <Structure> selection box select Control Structure.
5. In the <Add attribute> selection box select Object Type. This displays all
instances available in the Control Structure.
6. Select the ABB_TZIDC_110-210_SP_Short module from the displayed list
and click Search. If the module type is not available, this section can be
skipped.
7. Open Bulk Data Manager in the Control Structure (right-click on the Root
node and select Advanced > Bulk Data Manager).
8. Verify that the valid system is selected in the BDM sheet.
9. Search for and select the ABB_TZIDC_110-220_SP_Short module in the
Control Structure.
10. Select Control Properties in the Aspect List Area and move it via the drag
and drop function to the BDM sheet on cell A1 in the Preview Area.
11. A new window will open in which all parameters will be selected. Confirm the
Complete selection by clicking OK.
12. Select cell A2 in the BDM sheet and enter the text Filter:Control
Structure.
13. Select the project containing the ABB_TZIDC_110-210_SP_Short module in
the Control Structure and move it via the drag and drop function into the
BDM sheet on cell A3.
If the module is used in different projects, the steps must be repeated for the other
projects.

14. Select the Auto filter option in the Excel sheet (select Data > Filter >
AutoFilter in the menu bar).
15. Select in line A in the BDM sheet, the column named Source Object (normally
cell C1) and click Filter.

3BSE036342-510 C 215
800xA for Advant Master and 800xA for Safeguard Section 5 Upgrading 800xA 4.1 to 800xA 5.1

16. Search for and select the ABB_TZIDC_110-210_SP_Short module. This will
now be the only module shown.
17. Enter the text delete for each listed module in the column named Command
(normally cell A1). The Optional selection function can be used.
18. Save the changes to the 800xA System by clicking Save All Objects. The
modules will be deleted in the Control Structure.
19. Remove the text delete for each listed module in the column named
Command.
20. The captions Short will be exchanged to Long for all listed modules in the
column named Source Object. The name will now be ABB_TZIDC_110-
210_SP_Long for all listed modules.
21. Save the changes to the 800xA System by clicking Save All Objects. The
modules will be created in the Control Structure.

800xA for Advant Master and 800xA for Safeguard

Perform the following to prepare for the 800xA for Advant Master and 800xA for
Safeguard upgrade.
• Save the Advant Master Controller Licenses.txt.
• Save the DATHR Files.
• Document the RTA Board Control Aspect Settings.

Save the Advant Master Controller Licenses.txt

Perform the following on the Primary Aspect server in the 800xA 5.0 SP2 System:
1. Save the following file to a safe location.
– Advant Master Controller Licenses.txt
The default location for the file is:
...\Program Files\ABB Industrial IT\Operate IT\AC 400
Connect\Licenses

216 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline 800xA for Advant Master and 800xA for

Save the DATHR Files

Perform the following on each 800xA for Advant Master and 800xA for Safeguard
Connectivity Server node:
1. Save the following files to a safe location:
– DATHR1.CD
– DATHR2.CD
– DATHR3.CD
from the folder:
...\Program Files\ABB Industrial IT\OperateIT\AC 400
Connect\AdvantBase\Data\RTA\Init\
and record which files belong to which node.

Document the RTA Board Control Aspect Settings

Perform the following on each 800xA for Advant Master and 800xA for Safeguard
Connectivity Server node:
1. Document the following settings in the RTA Board Control aspect for
reconfiguration after the upgrade.
– MB300 node and network address.
– Time synchronization registry key (REVERSED_SYNC_MODE):
HKEY_LOCAL_MACHINE\SOFTWARE\ABB\AFW\SystemModules\
AfwTimeServerAdaptor\1.0-0\Private

3BSE036342-510 C 217
800xA for Harmony Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

800xA for Harmony

Perform the following to prepare for the 800xA for Harmony upgrade.
When upgrading an existing 800xA 4.1 system to 800xA 5.1 using System
Installer, verify that the Firewall is turned on and then execute the 800xA for
Harmony 5.0 SP2 HarmonyVerifyHelper.exe file (accepting all defaults) on all
Harmony Servers and Aspect Servers BEFORE using the System Planner tool or
performing any other upgrade or update procedure. This file is located on 800xA
System Installation DVD 1 in the following folder:
System Installer\Installation Tools\Upgrade\
HarmonyVerifyHelper

Save 800xA for Harmony Information

Use the following procedure to save 800xA for Harmony information:
1. Log in to the 800xA for Harmony local service account on the Configuration
Server or Configuration Server with Connectivity Server node.
2. Create a backup of the Configuration Server database.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for OCS
Systems > Harmony > Configuration > Backup Configuration
b. Click Connect.
Save the backup file to a safe media like a network share or removable disk.
Otherwise, the file will be deleted once an upgrade occurs due to a reload of the
node.
c. Click Browse to name the backup file and choose a location to save it.
d. Click Backup.
e. Click Exit when the backup is complete.

218 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline 800xA for AC 870P/Melody

800xA for AC 870P/Melody

Back up project specific changes (if applicable):
• DHCP Server Configuration.
• ETC Host files for Melody Connectivity Servers.
• Changes in the Default Object Types (e.g. manual changes for permissions
in Control Connection Aspects).
• ConvDB changes only on Configuration Server (change to the directory
...\Program Files\ABB Industrial IT\Configuration\Melody Tag Importer\.. and
backup the files MELCONVERTER.BAT, ConvDB.mdb and
ConvDB_<Hostname>.mdb.
ConfigServer node: Ensure that no Commissioning will be done from the
Melody Composer during this upgrade.
Use the following procedure to save 800xA for AC 870P/Melody information:
1. Log in to the 800xA Service account on the Configuration Server node.
a. Create a backup of the Configuration Server database.
b. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for Melody
> Configuration > Backup Configuration
c. Click Connect.
Save the backup file to a safe media like a network share or removable disk.
Otherwise, the file will be deleted once an upgrade occurs due to a reload of the
node.
d. Click Backup.
e. Click Exit when the backup is complete.

800xA for MOD 300

Ensure that the configuration data noted in the Customized Data for Backup
appendix in 800xA for MOD 300 Configuration (3BUR002417*) has been recorded.

3BSE036342-510 C 219
PLC Connect Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

PLC Connect
1. If the PLC Connect IEC 60870 feature is installed and configured, the IEC
configuration must be saved. Refer to the section on configuring the IEC 60870
driver in System 800xA PLC Connect Configuration (3BSE035041*) for more
information.
2. If the PLC Connect Communication Server Pre Treatment function is being
used in the application (refer to System 800xA PLC Connect Configuration
(3BSE035041*) for more information), make a backup of the Pretreat dll
(Pretreat3.dll or Pretreat4.dll, be sure to select the version used). The Pretreat
dll is located in the following folder on the PLC Connect Connectivity Server:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
The path is the default location of the file. If it has been placed somewhere else,
make a backup from that location.
3. Make a backup of the application project and source files for the Pretreat dll.

Engineering Studio IO Allocation

Deactivate the auto update mode in IO Allocation.
1. Start the Engineering Workplace.
2. Open the IO Allocation tool on any object by right-clicking on the object and
selecting Advanced > IO Allocation from the context menu that appears.
3. Verify that no check mark symbol is visible in the Options > Autoupdate
CBM menu item in the IO Allocation tool.

Asset Optimization
Preparing for the Asset Optimization upgrade requires recording the value of the
OPC Group Update Rate and backing up data to a safe media.

Record the Value of the OPC Group Update Rate

Use the following procedure to record the value of the OPC Group Update Rate.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Control Structure.

220 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Asset Optimization

3. Use the Object Browser to navigate to:

Root > Asset Optimization
4. Select Afw OPC-DA Asset Monitor Data Source in the Aspect List
Area.
5. Record the value of OPC Group Update Rate (ms) shown in the Preview
Area. This value must be reconfigured after the upgrade.

Back Up Data to Safe Media

Use the following procedure to back up Asset Optimization information (perform
only the steps applicable to the system):
1. Asset Monitoring:
Asset Monitoring directories will be found on every Asset Optimization Server
node and any other node defined as an Asset Monitoring Server.
a. If Runtime Asset Monitors are being used in the system, save the Runtime
Asset Monitor data directory (DeviceRunTimeMSLogicStore) to a safe
media. This directory stores the runtime information calculated by the
Runtime Asset Monitors running in this node. This directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
b. If XY Profile Deviation Asset Monitors are being used in the system, save
the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles) to a safe media. This directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
2. Maximo Integration:
If using Maximo Integration, the Maximo Integration information (Maximo
Equipment ID and Maximo Credentials aspects) must be saved from all Asset
Optimization Server nodes. Refer the Service Structure for the name of the
Asset Optimization Server nodes.
a. The MxDef files provide the mapping between the 800xA System
environment and the Maximo system. If the MxDef files were customized
per the instructions in Industrial IT, 800xA - Asset Optimization,

3BSE036342-510 C 221
Asset Optimization Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Configuration (3BUA000118*), back up the customized MxDef files to

safe media.
– The customized MxDef Files for Maximo versions 4.1 and 4.1.1 are
located in the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\
– The customized MxDef files for Maximo version 5.1 and 5.2 are located
in the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\Maximo5\MxServer
– The customized MxDef files for Maximo version 6.2 are located in the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\MaximoDef
b. Back up the AOMaximoModel.xml file to a safe location. A backup of
AOMaximoModel.xml is necessary because the ECS model for Maximo
also needs to be modified if the MXDef files are customized.
The model file is available at the following location:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
The pending fault reports residing in the system are available in the following
directory structure:
...\OperateITData\OptaoACDs
Backup the entire OptaoACDs folder.
3. SAP/PM Integration:
If using SAP/PM Integration, the SAP/PM Integration information (SAP
Equipment ID and SAP Credentials aspects) must be saved from all Asset
Optimization Server nodes. Reference the Service Structure for the name of the
Asset Optimization Server nodes.
a. Although the SAP/PM system is separate from the 800xA System, it is a
good idea to back up the system in use. Follow SAP/PM standard
practices for SAP/PM system backup.

222 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline PC, Network and Software Monitoring

b. The SAPPMDef files provide the mapping between the 800xA System
environment and the SAP/PM system. If the SAPDef files were
customized per the instructions in Industrial IT, 800xA - Asset
Optimization, Configuration (3BUA000118*), back up the customized
SAPDef files to safe media.
The customized SAPPMDef files for SAP version4.7 are located under:
...\Program Files\ABB Industrial IT\Optimize IT\
Asset Optimization\AOECSConnector\SAPPMDef
c. Back up the AOSAPModel.xml file to a safe location. A backup of
AOSAPModel.xml is necessary because the ECS model for SAP also
needs to be modified if the SAPPMDef files are customized.
The model file is available at the following location:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
The pending fault reports residing in the system are available in the following
directory structure. Backup the entire OptaoACDs folder.
...\OperateITData\OptaoACDs
4. DMS Calibration Integration:
The DMS Calibration Integration approach is changed in 800xA 5.1. Upgrade of
DMS Calibration Integration is not supported. Reconfigure the DMS Calibration
Integration based on an engineered solution.
Contact ABB technical support for more information.

PC, Network and Software Monitoring

Use the following procedure to prepare for the PC, Network and Software
Monitoring upgrade.
1. If there are user defined Script, Resource, and Assembly files they need to be
backed up. The user files are located in:
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Scripts\User

3BSE036342-510 C 223
PC, Network and Software Monitoring Device Library Section 5 Upgrading 800xA 4.1 to 800xA 5.1

...\Program Files\ABB Industrial IT\Optimize IT\

PC, Network and Software Monitoring\bin\Configuration\
Assemblies\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Resources\User directory
Copy the files in these directories to a safe location.
2. Shut down the PC, Network and Software Monitoring Server node.
a. Use the Structure Selector to open the Service Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to:
Services > OpcDA_Connector, Service > SG_IT Server,
Service Group > OPCDA_Provider_Node Name, Service
Provider
(where Node Name is the name of the PC, Network and Software
Monitoring Server node).
c. Select Service Provider Definition in the Aspect List Area.
d. Click the Configuration tab to produce a view in the Preview Area.
e. If the Enabled check box is selected, clear it and click Apply.

PC, Network and Software Monitoring Device Library

Use the following procedure to prepare PC, Network and Software Monitoring
Device Library upgrade:
1. Back up MOF files (if they exist) to a safe location. The MOF files are located
in:
...\Program Files\ABB Industrial IT\Optimize IT\PC,
Network and Software Monitoring\MOFS
2. Back up Process Health.dll to a safe location if Generic Computer Node V1.0
or higher versions are loaded. The dlls are located in:

224 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline SMS and e-mail Messaging

...\Program Files\ABB Industrial IT\Optimize

IT\PC, Network and Software Monitoring\Asset
Monitoring\Bin

SMS and e-mail Messaging

Save all GSM Device hardware information. Record information for the GSM
device on the SMS and e-mail Messaging GSM Hardware Setup Worksheet shown
in Table 7.

Table 7. SMS and e-mail Messaging GSM Hardware Setup Worksheet

Item Setting/Value
Spooler Settings
Activate Outbox Spooler Checked (check and leave checked)
Activate Inbox Spooler Checked (check and leave checked)
Interval for Checking for Incoming Value: _____ Seconds Minutes (circle 1)
Messages
Port Settings
COM Port Value: COM _____
Baud Rate Value: _____
Data Bits Value: _____
Parity Value: _____
Stop Bits Value: _____
PIN and Properties
Query PIN Checked or Unchecked (circle one)
PIN (only if Query PIN is checked) Value: ___________________
Save PIN (only if Query PIN is Checked or Unchecked (circle one)
checked)

3BSE036342-510 C 225
SMS and e-mail Messaging Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Table 7. SMS and e-mail Messaging GSM Hardware Setup Worksheet (Continued)

Item Setting/Value
Own Number (telephone number of Value: ___________________
SIM card (including Country Code)
in GSM hardware)
Initialization String for GSM Hardware Value:
_______________________________
_______________________________
_______________________________
_______________________________
General Service Properties
Name (GSM service provider) Value: ___________________
Port Value: COM _____
SMSC Value: ___________________
Default Country Code Value: ___________________
Default Prefix Value: ___________________
Number of Attempts Value: ___________________
Splitting Service Properties
Splitting Checked or Unchecked (circle one)
Optimize Splitting Checked or Unchecked (circle one)
Enumerate Splitting Checked or Unchecked (circle one)
Narrowband Sockets Checked or Unchecked (circle one)
Messaging Service Properties
Add Before Message Blank (verify and do not change)
Use for Delivery Notification Only Unchecked (verify and do not change)
Default Option 0 (verify and do not change)

226 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Batch Management

Table 7. SMS and e-mail Messaging GSM Hardware Setup Worksheet (Continued)

Item Setting/Value
Message General Properties
Replace CR LF for Incoming Checked or Unchecked (circle one)
Messages

Batch Management
1. Verify all scheduled batches are completed or terminated.
2. Disable the Batch Alarm & Event Service Group and Batch Service Group
before proceeding. To disable the service groups:
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Service Structure.
c. Use the Object Browser to select:
Services > Event Collector, Service >
batch_group_name, Service Group
d. Select Service Group Definition in the Aspect List Area.
e. Select the Configuration tab in the Preview Area.
f. Clear the Enabled check box and click Apply.
g. Determine the name of the nodes that are currently Primary and
Secondary Batch Servers,
h. Use the Object Browser to select:
Services > Batch Service, Service > batch_group_name,
Service Group
i. Select Service Group Definition in the Aspect List Area.
j. Select the Configuration tab in the Preview Area.
k. Select the provider that is currently the Secondary Batch Server.
l. Clear the Enabled check box and click Apply.

3BSE036342-510 C 227
Information Management Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

m. Select the provider that is currently the Primary Batch Server.

n. Clear the Enabled check box and click Apply.

Information Management
Refer to Information Management Pre-Upgrade Procedures on page 421 in
Appendix E, Information Management Upgrade to perform the Information
Management pre-upgrade procedures.

Scheduler Service (Application Scheduler)

Disable Schedules before stopping the servers and performing the upgrade. The
Schedules will need to be manually enabled again following the upgrade.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Scheduling Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Clear the Enabled check box and click Apply.

Calculations Service
Disable Calculations before stopping the servers and performing the upgrade.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Calculations Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Clear the Enabled check box and click Apply.

228 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Basic History Service Data

Basic History Service Data

Back up the Basic History folder for each Basic History Service Provider in the
Service Structure. Depending on the system, the Basic History Service data can
be present on a number of different node types (Connectivity Servers, IM Servers,
AO Servers, etc.). It is best to search for the directory described in this procedure
on all nodes, and if there is data present, back up that data.
To save Basic History Service data:
1. Stop the Basic History Server from the Service Structure.
2. Use Windows Backup (not the 800xA Backup) to backup the files in the:
...\OperateITData\History\{provider ID}
directory.
3. Start the Basic History Server again from the Service Structure.

Process Engineering Tool Integration

Back up Process Engineering Tool Integration information. The project data is
located in the following directory:
...\Program Files\ABB Industrial IT\Engineer
IT\Engineering Studio\Process Engineering Tool
Integration\Xml
Save the entire Xml data directory to a safe media such as a network share or
removable disk. The directory contains the default mapping files (*.dmf) modified
on the project, accelerator files (*.acc), and configuration files (*.pcf and *.fcf).

3BSE036342-510 C 229
Requirements for VB Graphics Extension Software Section 5 Upgrading 800xA 4.1 to 800xA 5.1

Requirements for VB Graphics Extension Software

These procedures are applicable to all 800xA Systems.

• Installing Visual BASIC 6.0 with SP6 must be followed for all nodes that use
Graphics Builder and the Primary Aspect Server node. This must be done
before performing the 800xA System Restore.
• Installing the VB Graphics Extension Software must be followed for each VB
Graphics extension software package on all nodes in the 800xA 5.1 System,
if the base product was installed on the 800xA 4.1 System. This must be
done before performing the 800xA System Restore.
To deploy VB Graphics, the user must belong to the Application Engineer
IndustrialIT user group and Windows Local Administrators.

Refer to System 800xA Engineering, Process Graphics Migration Tool for

information on migrating VB Graphics to Process Graphics 2.

Installing Visual BASIC 6.0 with SP6

Use of an Aero Theme with Windows 7 will lead to screen latency issues in the
VB Graphics Builder. This is because the Aero theme uses advanced rendering
schemes. Turn off the Windows Aero theme and switch to either none or
Windows Classic for use of VB Graphics. The behavior of VB IDE in Windows 7
will then be the same as that in Windows XP.
All nodes that use the Graphics Builder and the Primary Aspect Server node need a
Professional or Enterprise Edition of Visual BASIC 6.0 with SP6. The licensed copy
used on the 800xA 4.1 System must be installed on the 800xA 5.1 System. Follow
the installation procedure provided with Visual BASIC.

Installing the VB Graphics Extension Software

Perform the following procedure to install the VB Graphics extension software on
all nodes in the 800xA 5.1 System, if the base product was installed on the 800xA
4.1 System.
1. Insert System Installation DVD 1 into the drive.
2. Wait for the Installation AUTORUN screen to appear.

230 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Installing the VB Graphics Extension Software

3. Select:
Manual Installation > VB Graphics Extensions
as shown in Figure 21.

Figure 21. Installation AUTORUN Screen

4. Select a VB Graphics extension to install (the installation of the Batch

Management VB Graphics extensions is described later in this procedure).
5. The Installation Wizard for the selected VB Graphics extension appears.

3BSE036342-510 C 231
Installing the VB Graphics Extension Software Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

6. Follow the Installation Wizard to complete the installation. Choose Typical as

the installation type.
7. Repeat the procedure for each required VB Graphics extension that appears in
the Installation AUTORUN Screen.
8. This step only applies to the VB Graphics extensions for Batch Management
when using System Installer to upgrade the 800xA System. If Batch
Management was installed manually during the upgrade, the VB Graphics
extensions for Batch Management were installed at that time.
a. Select:
Manual Installation > Batch Management
b. The Installation Wizard for Batch Management appears.
c. Select Modify when the dialog box appears that offers that choice.
d. Select to install the Batch Management VB Graphics extensions in the
Installation Type dialog box.
e. Follow the Installation Wizard to complete the installation.

232 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Post Upgrade Procedures

Post Upgrade Procedures

The remainder of this section describes how to:
• Perform the 800xA Restore procedure.
• Load the VB Graphics extensions on the Primary Aspect Server.
• Restore historical data.
• Restore the necessary data for each Functional Area.

800xA System Restore

Refer to Requirements for VB Graphics Extension Software on page 230 before
performing the 800xA System Restore.

Perform this procedure only on the Primary Aspect Server.

The User Account that is used for 800xA System restore via the Configuration
Wizard must be a member of the following groups:
• IndustrialITUser.
• IndustrialITAdmin.
• Local Administrators.
Click Yes if during restore a message box appears stating:
A required system extension is not installed Name :
System_Instruction
The backup/restore utility supports the restoring of 800xA system information. The
following steps outline the 800xA system restore procedure.
Refer to System 800xA Maintenance (3BSE046784*) for more information on
restoring the system.
1. Start the restore procedure.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > System >
Configuration Wizard

3BSE036342-510 C 233
800xA System Restore Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

b. The Select Type of Configuration dialog box appears. Select Restore

System and click Next.
Restart the node when advised during the restore procedure.

2. Check for messages in the log file (select the View Log check box in the
Configuration Wizard). Refer to Appendix A, Warning and Error Messages to
resolve any received warning or error messages.
3. Check the CPU load in the node. The System Message service may generate a
high load (>90%). If this continues for longer than approximately 10 minutes,
restart the service.
If a message stating that a full deploy of the Generic Control Network is needed,
click OK.
4. One node at a time, start up and connect all nodes to the 800xA System in the
following order:
– Aspect Server nodes.
– 800xA for Harmony Configuration Server nodes.
– Connectivity Server nodes.
– Application Server nodes.
– Client nodes.
a. Use the following guidelines while connecting nodes, using the
Configuration Wizard. This must be performed on the node that is going to
be connected, not on the node on which the restore was performed.
b. Select the Primary Aspect Server (the server on which the system will run)
in the Connect to another System on Node drop down-list box, in the
Connect to System dialog box.
c. If the node is an IM Server, verify that the ABB Process Administration
Service (PAS) is set to manual in the Services Control Panel (run
Services.msc from the Run dialog box). Stop the service if it is running.
d. Select Connect Node from the Select Type of Configuration dialog box.
e. Set the current system as the default system when connecting nodes to the
system.

234 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Consistency Check

– In some cases, problems may be encountered when connecting nodes to

the system. Verify that the system software user settings are correct using
the Configuration Wizard. Restarting the node again may also solve the
problem.
– Wait until all services in the newly connected node are up and running
before connecting the next node. Select the Node Administration
Structure\connected_node_name\System Status Viewer aspect to monitor
the status of services. If some services will not start up, restarting the node
may help.
Do not include services that were stopped manually as part of the pre-upgrade
procedures. These will be manually restarted later in the post upgrade procedures.
f. Restart each node after it has been connected to the system.
Run the System Software User Settings until OK. Restart if it is not working and
if the message:
Invalid User
appears.
5. Refer to Appendix D, Recording the Number of Aspects and Objects and
record the number of aspects and objects in the system. Compare these values
to those recorded when the system was backed up.
6. Verify the affinity settings to ensure best system performance. Refer to System
800xA Post Installation (3BUA000156*) for more information on how to
configure affinity.

Consistency Check
Refer to Appendix C, Consistency Check and perform the necessary consistency
checks.

Loading the VB Graphics Extensions

Perform the following procedure on the Primary Aspect Server to load the VB
Graphics extensions:
1. Refer to Table 8 for a list of VB Graphics extensions available to be loaded.
2. Start the Configuration Wizard from the primary Aspect Server node. Select:

3BSE036342-510 C 235
Loading the VB Graphics Extensions Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Table 8. VB Graphics Extensions

Directory Software
800xA Connectivities AC 800M Connect VB Graphics Extension
ABB 800xA for Advant Master VB Graphics Extension
5.1.0/0n
ABB 800xA for Harmony VB Graphics Extension 5.1.00
ABB 800xA for IEC61850 VB Graphics Extension
ABB 800xA for MOD 300 VB Graphics Extension
ABB 800xA for Safeguard VB Graphics Extension 5.1.0/0
ABB PLC Connect VB Graphics Extension 5.1.00
Asset Optimization ABB Asset Optimization VB Graphics Extension 5.1
ABB PC, Network and Software Monitoring VB Graphics
Extension
Batch Management Batch VB Graphics Extension
Batch Advanced Templates VB Graphics Extension
Device Management & Fieldbuses ABB Device Management FOUNDATION Fieldbus VB
Graphics Extension

Start > All Programs > ABB Industrial IT 800xA > System >
Configuration Wizard
3. Open the System Extension Load dialog box by going to:
System Administration > Select System > System Extension Load
4. A view appears with the available VB Graphics extensions listed in the left
pane. Select the system extension to load in the list in the left pane and move it
to the list in the right pane by clicking >. To move all the system extensions
from the left pane to the right pane, click >>.
5. The red cross, green check mark, and warning icons indicate the status of the
dependency evaluation.
– The green check mark indicates that the system extension must be loaded
first.

236 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Loading the VB Graphics Extensions

– The red cross icon indicates that the system extension can not be loaded
until the one with the green check mark icon is loaded.
– The warning icon indicates that the system extension can be loaded, but
that there is additional information available in the Description frame in
the lower part of the dialog box. The additional information can, for
example, be that the system extension contains aspect types that are not
environment aware.
6. If the list in the right pane contains more than one system extension, click
Press header to autosort to sort the system extension load order with regard to
dependencies.
7. All system extensions in the right pane should be marked with the green check
mark or the warning icon.
8. Click Next and the Apply Settings dialog box appears.
9. Click Finish to load all system extensions.
10. A progress dialog box is shown during the load. Click View Log to view log
messages during load.
The load is aborted if:
• The user clicks Abort.
• An error occurs; for example, if the Configuration Wizard fails to load a file
into the system.
An aborted system extension load can be resumed from the System Extension
Maintenance dialog box.
11. When the load operation is finished, click Finished and view the Configuration
Wizard log to verify that no errors occurred during the load.
12. Close the Configuration Wizard.

3BSE036342-510 C 237
800xA Documentation Maintenance Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

800xA Documentation Maintenance

Previous versions of the 800xA System (800xA 5.0 SP1 and earlier) included a
system extension for 800xA Documentation. This system extension is no longer
included.
Delete all documentation aspects (denoted by an open book icon) with a category
name of Application Manual, Operating Manual, Installation Manual, or Technical
Reference Manual found in the Product Type Structure.
If any customer-specific documentation aspects have been added, it is necessary
to browse through the Product Type Structure and delete the 800xA
documentation aspects individually so that customer-specific documentation will
not be accidentally deleted.
Use the Find Tool in the Plant Explorer Workplace to find the documentation
aspects.
The System Instructions system extension must be removed (unregistered). To
unregister the System Instructions system extension from the 800xA system:
1. Use Windows Explorer to navigate to:
...:\Program File\ABB Industrial IT\Operate IT\Process
Portal A\bin
2. Double-click AfwRemoveSystemInstructions.exe to execute the
program.

Composite Graphic Elements

There may be a problem accessing objects in composite graphic elements with
EnableInput set to false after upgrading to 800xA 5.0 SP1 or later.
Refer to Product Bulletin 3BSE052342 for more information.

238 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Graphic Overlap Displays

Graphic Overlap Displays

After upgrading from 800xA 4.1 to 800xA 5.1, a graphic overlap display can be
brought up one time, but not twice. Perform the following so that graphic overlap
displays can be brought up more than one time.
Be extremely careful when making changes in the registry. Do not make any
changes in the registry without first making a backup copy of the registry. Refer
to the online help for the registry editor on how to create a backup.
Set the following:
• ApartmentCacheSize = 0
Registry Location:
HKEY_LOCAL_MACHINE\SOFTWARE\ABB\AFW\SystemModules\
WorkplaceApplication\1.0-0\private\WPApartment\ApartmentCacheSize

Reconfiguring Group Displays

New Group Display aspects that are created and configured in the Object Type
Structure on the object types and instances will work correctly even if there is more
than one aspect with the same name but each aspect has a different Aspect Category.
Configured Group Display aspects that already exist in the Object Type Structure
and on the object types and instances should be reconfigured for the aspects to
display correctly. (This is required for the reference to an aspect to be stored along
with its Category ID.)

Device Management and Fieldbuses

After installation of 800xA 5.1 software all third party software for Device Type
Objects used in the previous system version must be reinstalled. Additionally
PROFIBUS Device Type Objects used in the Control Builder M project must be
adapted to new delivered Hardware Libraries.

3BSE036342-510 C 239
Device Management and Fieldbuses Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Restore Device Types

The procedures in the System Restore Wizard function in the Device Library
Wizard must be performed for Fieldbus Device Types before restoring the
Control Builder M project, otherwise the upgrade will fail. The Control
Builder M upgrade can only be performed once.
The following steps for Fieldbus Device Types need to be carried out on every
800xA system node. Perform the System Restore Wizard procedure on the nodes in
the following sequence:
• Aspect Servers (including redundant Aspect Servers).
• Connectivity Servers (including redundant Connectivity Servers).
• Application Servers.
• Clients.
Restore the Device Types on the Primary Aspect Server node before starting to
install them on other system nodes. Do not run parallel installations of Device
Types on other system nodes unless all Device Types are restored on the Primary
Aspect Server node. Installation of Device Types on other system nodes can be
done in parallel after they are restored on the Primary Aspect Server node.

If the system contains FOUNDATION Fieldbus Device Types, check the

following before proceeding to the next step:
• Open a Plant Explorer Workplace.
• Use the Structure Selector to open the Object Type Structure > FF
Libraries.
• Check to see if there is more than one entry of FF H1 Device Library,
FF Object Type Group.
• If there is more than one entry, perform FF Upload once so there is only one
instance of FF H1 Device Library, FF Object Type Group
present. If there is only one entry, proceed to the next step using the Device
Library Wizard.
1. Start the Device Library Wizard. Select:
Start > All Programs > ABB Industrial IT 800xA > Device Mgmt >
Device Library Wizard
-or-
double-click the Device Library Wizard icon on the desktop.
2. Navigate to:

240 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Device Management and Fieldbuses

Device Type Administration > System Restore Wizard

and choose the first option in the System Restore Wizard as shown in Figure 22
and click Next.

Figure 22. System Restore Wizard (1)

3BSE036342-510 C 241
Device Management and Fieldbuses Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

3. Choose whether or not this system node has been reformatted as shown in
Figure 23 and click Next.

Figure 23. System Restore Wizard (2)

4. Depending on which fieldbus protocol is used in the previous system version

environment, insert one of the delivered Device Library system DVDs in the
DVD drive (e.g. Device Library HART – DVD).
5. Click Browse and navigate to the DVD drive.
6. When the drive has been selected in the Browse for folder dialog box, click OK
in that dialog box and then Next in the ABB Device Library Wizard.
7. The Device Library Wizard scans the 800xA System for fieldbus device types
that are already used and compares the results with the contents of the DVD.

242 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Device Management and Fieldbuses

Device Types available in the 800xA System and the DVD are shown in the
Extract tab of the Device Library Wizard (Figure 24).

Figure 24. Extract Device Type Files

8. Click Next to start the extraction process.

9. Device Types available in the 800xA System but not on the DVD are displayed
in the Missing tab. If there are any Device Types showing in the Missing tab,
Next in the Device Library Wizard is disabled. Navigate to the Browse dialog
box by clicking Back and inserting a new Device Library DVD in the DVD
drive.
10. There may be some Object Types that are either customer created, or are the
latest Device Types downloaded from ABB SolutionsBank. These will not be

3BSE036342-510 C 243
Device Management and Fieldbuses Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

available on the DVDs. The Device Library Wizard will prepare a list for these
Device Types (Figure 25). Install these Device Types manually.

Figure 25. List of Files to be Manually Installed

11. Repeat this procedure until all Device Types are extracted to the 800xA System
node and the Missing tab does not list any device types.
12. If the Device Library DVDs do not contain all Device Types used in the
previous system version, the missing Device Types must be downloaded from
ABB SolutionsBank.
It is only possible to complete the Wizard if all Device Types have been
successfully extracted.

244 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Device Management and Fieldbuses

13. When the extraction process is completed successfully, the Device Types need
to be re-installed on the 800xA System node. Click Next to launch the Re-
installation of Device Types dialog box shown in Figure 26.

Figure 26. Re-install Device Types Dialog Box

14. Follow the Device Library Wizard procedure to complete the installation. If
Control Builder M is installed on the node, the Device Library Wizard will
open Control Builder M and decide which device instances are linked to
Standard Hardware Libraries from Device Integration. If some Device Types
are custom created or modified then these instances will be linked to custom

3BSE036342-510 C 245
Device Management and Fieldbuses Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Hardware Libraries at the time of the Control Builder M project upgrade

(Figure 27).

Figure 27. Linking to Custom Hardware Libraries

If Control Builder M is not installed on the node, the error message shown in will
If
appear. Ignore the message and continue.

246 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Device Management and Fieldbuses

Figure 28. Error Message

15. The Device Library Wizard will automatically navigate to the main window
after the process is completed.
16. Exit the Device Library Wizard and repeat the procedure on the other 800xA
System nodes, if applicable.

Device Management PROFIBUS & HART

Perform the Configure OPC P/H Server on the Primary Aspect Server.

Device Management FOUNDATION Fieldbus

Perform the following to complete upgrading Device Management FOUNDATION
Fieldbus.
1. Update LD 800HSE Linking Devices: Update all LD 800HSE linking devices
to the latest firmware version released for this system environment following
the update procedure described in the user instructions for the particular device.
Refer to Field IT, Foundation Fieldbus Linking Device, LD 800HSE, Version
Table (3BDS009910) in ABB SolutionsBank for the latest linking device
firmware released for this system environment.
From Downloads Explorer, navigate to:
Control Products and Systems/800xA/Device Management Foundation
Fieldbus/Foundation Fieldbus Linking Device LD800HSE
2. Check, Save, and Upload FF Libraries:
a. Open a Plant Explorer Workplace.

3BSE036342-510 C 247
Device Management and Fieldbuses Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

b. Use the Structure Selector to open the Object Type Structure.

c. Use the Object Browser to navigate to:
FF Libraries Object Type Group
d. Select FF Management in the Aspect List Area.
e. Click Open Project.
f. Check the libraries for plausibility.
g. Exit Fieldbus Builder FF and save changes if prompted to do so.
h. Return to the Plant Explorer Workplace and click the Library Upload tab
in the Preview Area.
i. If the traffic light symbol shows red, click Upload FF Library.
j. The green traffic light symbol indicates that the FF libraries have been
synchronized.
3. Optional: Reconstruct User-made Changes to Library Objects representing FF
Standard Blocks:
This step is only required if changes were made to library objects representing FF
standard blocks.
During upgrade, user-made changes to library objects representing FF
standard blocks have been overwritten. Important substitutions have been
logged.
a. If such changes were made, display the substitutions as follows:
– Open a Plant Explorer Workplace.
– Use the Structure Selector to open the Object Type Structure.
– Use the Object Browser to navigate to:
FF Libraries Object Type Group
– Select FF Upload in the Aspect List Area.
– Select Warnings tab.
b. For reconstructing user-made changes, reapply the changes to the library
objects manually.

248 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Device Management and Fieldbuses

4. Check, Save, Commission, and Upload the HSE Subnet.

Perform the following procedure for each HSE Subnet.

a. Open a Plant Explorer Workplace.

b. Use the Structure Selector to open the Control Structure.
c. Use the Object Browser to navigate to:
HSE Subnet
d. Select FF Upload in the Aspect List Area.
e. Click the HSE Subnet Reference tab in the Preview Area.
f. Click Open Subnet in Fieldbus Builder FF.
g. Check to see if the configured HSE subnet ID is used for the OPC Server
FF configuration in FF Network > Properties and modify it if required.
h. Check whole project for plausibility.
i. Perform device assignment for all linking devices LD 800HSE.
j. Perform precommissioning/commissioning for all objects for which this is
necessary (discernible from engineering status).
To assign all H1 devices in one step, use the Assign all devices function from the
HSE Subnet context menu: Object > Assign all devices...
For downloading use the online dialog from the HSE Subnet context menu:
Object > Online Dialog...
k. Exit Fieldbus Builder FF and save changes if prompted to do so.
l. Return to the Plant Explorer Workplace and select FF Upload in the
Aspect List Area.
m. If the traffic light symbol shows red, click Upload HSE Subnet.
n. The green traffic light symbol indicates that the HSE Subnet has been
synchronized.
5. Import the locally stored parameter value sets as follows:
a. Open a Plant Explorer Workplace.

3BSE036342-510 C 249
800xA for AC 800M Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

b. Use the Structure Selector to open the Object Type Structure.

c. Use the Object Browser to navigate to:
FF Libraries, Object Type Group
d. Select FF Management in the Aspect List Area.
e. Click Open Project to open the FF Libraries project in Fieldbus Builder
FF.
f. Open the block properties dialog for the Function Block where the
parameters were exported during the pre-upgrade procedure.
g. Right-click on the dialog box and select Import from the context menu.
h. Browse the .csv file and restore the value sets.
Ensure that the stored value sets are imported to the corresponding Function
Blocks.
i. Right-click and select Store parameter value set from the context menu.
j. Specify an appropriate name for the new value set and click OK.
k. Click Cancel. Do NOT overwrite the Initial Instance Parameters with the
imported parameters, and then close the block properties dialog box.

800xA for AC 800M

After upgrading a configuration containing one Engineering and one Production
system to 800xA 5.1, the Control Builder M projects in the two systems should
be made identical using the Import/Export tool, Engineering Repository, or by
recreating the Engineering System using Backup/Restore before engineering
work is restarted. Otherwise there will be a lot of false differences on the
AC 800M aspects reported in the import difference report when moving solutions
between the systems.
There may be Control Builder M compatibility issues when upgrading from
800xA 4.1 to 800xA 5.1. Review the issues detailed in 800xA 4.1 to 800xA 5.1
Compatibility Issues on page 385 before proceeding.
Use the following procedure to restore 800xA for AC 800M information:

250 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline 800xA for AC 800M

1. Control Builder stores its settings (systemsetup.sys) on disk in the following

directory:
...\ABB Industrial IT Data\Engineer IT Data\Control
Builder M Professional
Copy the previously saved file from the safe media to this folder.
2. New handling for Hardware Types was introduced in 800xA 5.0. All hardware
types are now packaged in libraries. Because of this all Control Builder
projects must be upgraded according to the following steps.
If the application contains FOUNDATION Fieldbus, HART, or PROFIBUS
specific configurations, perform post upgrade procedures for Device Types via
the Device Library Wizard (refer to Device Management and Fieldbuses on page
239) before upgrading the project in Control Builder M.
a. Start an empty Control Builder M.
b. Select:
Tools > Maintenance > Upgrade Project
c. Select the Control Builder project to upgrade. This step will take a while.
All hardware objects in the Control Structure are redirected by Control
Builder to use hardware types from libraries. If the project contained
custom hardware definition files, libraries with corresponding hardware
types are automatically created by Control Builder.
d. Repeat Step a through Step c for all Control Builder projects.
During the project upgrade there may be information messages with the
following text:
"Copy of aspect(s) of category 'Object Type Extension Definition' from the
type xxxxxx to Hardware Libraries yyyyyy must be performed manually in
PPA'.
Ignore these messages if the Device Types in use are provided by the ABB
Device Integration Center and have not been modified by the user.
Otherwise copy the missing aspects manually if it is a user defined device type.

3BSE036342-510 C 251
800xA for AC 800M Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

The following additional messages may appear:

Warning in input file at line XX. SubUnits,
LogicalNumbers and DiscreteNumbers are mutually
exclusive.
Warning in input file at line XX. The positions defined
must match SubUnits, Logical-, or DiscreteNumbers
Ignore these warning messages.
e. When all Control Builder Projects are upgraded the old hardware types
should be deleted from the Object Type Structure.
In the Plant Explorer Workplace, navigate to the Object Type Structure
and browse to:
Object Types > Control System > AC800M/C Connect -
Controller Hardware
Right-click the Controller Hardware object and select Delete.
3. Modify the application program according to applicable issues in 800xA 4.1 to
800xA 5.1 Compatibility Issues on page 385.
4. Load the controllers with their firmware and applications. Change Analysis
Mismatches may be shown for objects in the Standard Libraries during the first
download after the upgrade. Possible mismatches are:
Mismatch: Variable has changed data type.
Mismatch: Variable not found.
Mismatch: Control Module not found.
The mismatches reflect internal changes in the Standard Libraries. No Cold
Retain Values will be lost. Click Next Mismatch to continue.
5. The OPC Server stores configuration files (*.cfg) and settings
(systemsetup.sys) on disk. Add the files saved on the safe media to the system.
The systemsetup.sys file is located in:
...\ABB Industrial IT Data\Control IT Data\OPC Server
for AC 800M
The configuration files are stored in the Files folder in the same location.

252 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline 800xA for Advant Master and 800xA for

6. Restore OPC configurations by selecting File > Load Configuration in the

OPC Server Panel.
Remember to enable autoloading of the configuration and provide the correct
path to the file.

800xA for Advant Master and 800xA for Safeguard

Perform the following post upgrade procedures for 800xA for Advant Master and
800xA for Safeguard.
• Copy the Advant Master Controller Licenses.txt.
• Copy the DATHR Files.
• Reconfigure RTA Board Control Aspect Settings.

Copy the Advant Master Controller Licenses.txt

Perform the following on the Primary Aspect Server in the 800xA 5.1 System:
1. Copy the following updated file:
• Advant Master Controller Licenses.txt
The default location to copy the file in the 800xA 5.1 system:
...\Program Files\ABB Industrial IT\Operate IT\AC 400
Connect\Licenses

Copy the DATHR Files

Perform the following on each Connectivity Server node:
1. Copy the saved files:
– DATHR1.CD
– DATHR2.CD
– DATHR3.CD
to the folder:
...\ProgramData\ABB\AC400Connect\AdvantBase\Data\
RTA\Init\
to the node where they belong.

3BSE036342-510 C 253
800xA for Harmony Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Reconfigure RTA Board Control Aspect Settings

1. Open the MB 300 RTA Settings dialog box in Configuration Wizard and
reconfigure:
– MB 300 Node and Network Numbers.
– Check 800xA as Clock Master (REVERSED_SYNC_MODE) in case
the time synchronization key REVERSED_SYNC_MODE was
previously enabled.
2. Always Restart the RTA board.
3. The Audible property must be 0 for events and 1 for alarms 800xA for Advant
Master version 4.1 SP1 RU6 and newer. Refer to System 800xA Configuration
(3BDS011222*) for configuration of audible alarms.
Safeguard standardevent 300 - 326 does not comply with this rule before
800xA for 800xA for Advant Master Version 5.0 SP2. The Event numbers
where the Audible property should be changed from 1 to 0 are:
– EVENT302.
– EVENT305.
– EVENT310.
– EVENT312.
– EVENT320.
– EVENT321.
– EVENT322.
– EVENT325.

800xA for Harmony

Perform the following post upgrade procedures for 800xA for Harmony.

Restore 800xA for Harmony Information

Use the following procedure to restore 800xA for Harmony information:
1. Log in to the 800xA Installing User account (or a local Administrator account)
on the Configuration Server or Configuration Server with Connectivity Server
node.

254 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline 800xA for Harmony

2. Restore the 800xA for Harmony Configuration information that was saved
during 800xA for Harmony on page 218.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for OCS
Systems > Harmony > Configuration > Restore Configuration
b. Click Connect in the Harmony Connect Configuration Backup/Restore
window.
c. Enter the name of the Harmony Configuration Server database backup file
in the Backup File field.
d. Click Restore.
e. If a prompt appears indicating that the system version does not match the
backup version, click Yes.
f. If the message Services must be stopped, REBOOT system now
then restart this application! is displayed, restart the node and
repeat Step a through Step e.
g. The Backup/Restore program compares the old configuration in the
backup file to the current configuration of the newly installed system. If
the hosts of the Primary and Redundant Connectivity Servers do not
match, a dialog box will appear allowing the user to map the old
Connectivity Server node names to the new Connectivity Server node
names.
h. Leave the Create Missing Servers in Installed Configuration (Disaster
Recovery) check box disabled.
i. Click Exit when the restore operation is complete.

Synchronize the Aspect Directory

Synchronize the Aspect directory with the Harmony Configuration Server using the
Harmony Synchronizer Aspect, which is part of the Harmony OPC Server network.
Refer to 800xA for Harmony Configuration (3BUA000157*) for more detailed
information on how to synchronize.

3BSE036342-510 C 255
800xA for AC 870P/Melody Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Check Consistency of Harmony OPC Network Objects

Inherited and copied aspects are inconsistent after upgrading from 800xA 4.1 to
800xA 5.1. Using the Consistency Check Tool on all Harmony OPC Server
Network objects will correct this issue.
1. Open a Plant Explorer Workplace.
2. Click the Consistency Check Tool icon at the top of the Plant Explorer
Workplace to launch the Consistency Check dialog box.
3. Click Add Item to launch the Select Item dialog box.
4. Browse to the root of the Control Structure.
5. Select all of the Harmony OPC Server Network objects (use Ctrl+Click or
Shift+Click to select multiple objects).
The Consistency Check Tool can take a long period of time to run depending on
the quantity of data contained within the Aspect System. It is recommended that
the tool be run on a subset of data (a node (PCU) within the Control Structure)
to evaluate the time needed prior to selecting the entire OPC Network.
6. Click Add and Close.
7. Click Check.

800xA for AC 870P/Melody

Restore existing backups for project specific changes (if available) for: (Refer
also to 800xA for AC 870P/Melody on page 219.)
• DHCP Server Configuration.
• ETC Host files for 800xA for AC 870P/Melody Connectivity Servers.
• Changes in the Default Object Types.
• ConvDB changes of the Configuration Server.
Perform the following post upgrade procedures for 800xA for AC 870P/Melody.
• Restore 800xA for AC 870P/Melody Information.
• Additional 800xA for AC 870P/Melody Configuration Steps.

256 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline 800xA for AC 870P/Melody

Restore 800xA for AC 870P/Melody Information

Perform the following procedure to restore 800xA for AC 870P/Melody
information:
1. Log in to the 800xA Installing User account (or a local Administrator account)
on the Configuration Server node.
2. Restore the 800xA for AC 870P/Melody Configuration information that was
saved during 800xA for AC 870P/Melody on page 219.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > 800xA for Melody
> Configuration > Restore Configuration
b. Click Connect in the Melody Connect Configuration Backup/Restore
window.
c. Enter the name of the Melody Configuration Server database backup file
in the Backup File field.
d. Click Restore.
e. If a prompt appears indicating that the system version does not match the
backup version, click OK.
f. If the message Services must be stopped, REBOOT system now
then restart this application! is displayed, restart the node and
repeat Step a through Step e.
g. Click Exit when the restore operation is complete.
If there are specific faceplates in use (process industries or utilities), the
faceplates must also be upgraded. Refer to the faceplate related documents for
further instructions.

Additional 800xA for AC 870P/Melody Configuration Steps

Information on performing these additional configuration steps can be found in
800xA for AC 870P/Melody, Configuration (3BDD011741*) and System 800xA Post
Installation (3BUA000156*).
Perform the following configuration steps after adding the 800xA for
AC 870P/Melody Configuration Server to the 800xA System.

3BSE036342-510 C 257
800xA for MOD 300 Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

1. Melody Executive Service Provider.

2. Tag Importer.
Perform the following configuration steps after adding each 800xA for AC
870P/Melody Connectivity Server to the 800xA System.
1. Melody Executive Service Provider.
2. OPC Data Source Definition.
3. Alarm and Event Provider Setup.

800xA for MOD 300

1. Re-initialize PAS System Services on the Connectivity Server.
The PAS System Services will not start until the communications settings are
initialized as described in the following steps.
2. Initialize the OMF settings to start system services. Use the Administrative
Tools in Windows Control Panel to select:
PAS > Settings.
This displays the Communications Configuration Tool.
The message:
Would you like to revert back to saved settings?
is displayed if settings were previously saved. To restore the previous settings,
perform Step a through Step d.
a. Select Yes at the message:
Would you like to revert back to saved settings?
This opens the Communication Settings display.
b. Select OK on the Communication Settings display to save the settings and
close the window.
c. Select OK to the message:
Settings have been saved . ...

258 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline PLC Connect

d. Select OK when the message appears that indicates the settings have been
changed. A restart is always required if the Control Network Setting, OMF
Memory, or TCP/IP enabled setting are changed.
3. Restart Windows at this time.
4. Reverse_Time synch will be disabled following the re-installation of PAS. If
the Connectivity Server node sets the time on the Real-Time Accelerator Board
(RTAB), Reverse_Time_Synch must be enabled. Refer to the 800xA for
MOD 300 section in System 800xA Post Installation (3BUA000156*).
5. If any objects were customized, those changes must be implemented again on
objects delivered with 800xA for MOD 300 Version 5.1.
6. Update the registry settings previously recorded. Refer to 800xA for MOD 300
Configuration (3BUR002417*).

PLC Connect
Perform the following post upgrade procedures for PLC Connect.

Modify Installation for IEC 60870 or Basic Project Objects

If either the IEC 60870 or Basic Project Objects features were installed:
1. Use standard Windows procedures to access Programs and Features in
Windows Control Panel.
2. Select ABB PLC Connect.
3. Select Change/Modify.
4. The InstallShield Wizard for PLC Connect appears. Refer to System 800xA
Installation (3BSE034678*) to select and install the desired features.
5. If the IEC60870 feature is installed refer to System 800xA PLC Connect
Configuration (3BSE035041*) and reload the saved IEC configuration.

Restoring the Pretreat dll

To restore the Pretreat dll:

3BSE036342-510 C 259
PLC Connect Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

1. If the PLC Connect Communication Server Pre Treatment function is being

used in the application, copy the Pretreat dll file (Pretreat3.dll or Pretreat4.dll)
from the backup location to the same folder as it was backed up from on the
PLC Connect Connectivity Server. If the default folder is used, that location is:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
2. Register the Pretreat dll file (refer to System 800xA PLC Connect
Configuration (3BSE035041*) for more information).
3. Restart the PLC Connect Connectivity Server for the changes to take effect.
4. Restore the project and source files for the Pretreat dll.

Update the Sattbus Configuration

Perform the following if the Sattbus protocol is used for any of the controllers:
1. Select the PLC Controller Configuration aspect for the controller that uses
Sattbus protocol and click Edit Driver.
2. Configure the Common System Settings and click OK.
3. Restart the Connectivity Server.

Redeploy the PLC Connect Configuration

To redeploy the PLC Connect configuration:
1. Use the Structure Selector to open the Control Structure in the Plant Explorer
Workplace.
2. Use the Object Browser to navigate to the first Generic Control Network
object.
3. Select Deploy in the Aspect List Area.
4. Press the SHIFT key and click Deploy in the Preview Area to ensure that a full
deploy is done.
5. The deploy begins and the progress is displayed in the Preview Area. The
deploy is completed when Deploy ended is displayed.
6. Repeat the procedure for any additional Generic Control Network objects.

260 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Engineering Studio

Engineering Studio
Post upgrade procedures for Engineering Studio include those for IO Allocation,
Engineering Templates, and Function Designer.

IO Allocation
Before working with the IO Allocation function in an upgraded system, check all
Control Builder Name aspects of CBM_Signal instances to see if they contain a
valid name.
All Control Builder Name aspects having an empty name or a name not
introduced by synchronization from the Name aspect must be corrected
accordingly. This can be performed using a Bulk Data Manager worksheet that
reads out Name and Control Builder Name. The same worksheet can be used to
write back the Name.
The following procedure is only required if HART devices and IO signals will be
merged into one object.
800xA 5.1 supports merging of Hart devices and IO signals within one object. If
Hart devices and IO signals will be merged into one object refer to Industrial IT,
800xA - Engineering, Engineering Workplace, Basic Engineering Functions
(3BDS011223*).
The following procedure is only required when working with IO Allocation and if
properties of IO boards have been changed directly in Control Builder M.
IO Allocation has enabled new properties (e.g. Inverted) to be accessible for
CBM_SignalParameter/CBM_PulseSignalParameter. These properties are
initialized with a default value. If properties have been changed directly in the
Hardware Editor of Control Builder M (as they were not supported by IO
Allocation) these changes are not reflected in
CBM_SignalParameter/CBM_PulseSignalParameter aspects after the upgrade.
Therefore, when the menu write Allocation into CBM is performed, values may be
overwritten with their default value. After upgrading, select controller by controller
and perform the menu Read Allocation from CBM, which reads the property
values from Control Builder M and updates the signal objects.

3BSE036342-510 C 261
Engineering Studio Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Engineering Templates for Bulk Data Manager (BDM)

Engineering Templates are typically used from scratch, meaning data is dropped
into the templates. The result is used for information or documentation. In this case
no upgrade is required, because the installation of Engineering Studio 5.1 exchanges
the Engineering Templates in:
...\Documents and Settings\All Users\Desktop
However, if a worksheet containing data has been saved in the file system for
writing back to the 800xA System after upgrade, either:
• Newly create the worksheet based on an Engineering Template delivered with
Engineering Studio 5.1.
-or-
• Update the worksheet according to the description in:
...\Documents and Settings\All Users\Desktop\
Engineering Templates\ Upgrade Description Engineering
Templates.doc

Function Designer

Modified Aspects of Function Designer System Extension. The Function

Designer system extensions:
• Signal Extension for AC800M Connect
• Function Designer for AC800M Connect
• Topology Designer for AC800M Connect
• CI Extension for AC800M Connect
• Signal Extension for TRIO Connect
• Topology Designer for AC800M High Integrity
• Function Designer for AC 800M Classic
• Topology Designer for AC800M Classic
• Function Designer for Fieldbus Builder Profibus/Hart

262 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Engineering Studio

• AC 800M Signal Extension Classic

mainly consist of:
• Functional Planning Object Types, including a Function Settings aspect at the
Settings Object Type Group.
• Extension Libraries that add Function Designer Aspects to Object Types
(Control Modules, Function Blocks, ...) created by basic libraries (AC 800M
Connect, AC 800M Classic, etc.).
After having loaded such a system extension in the 800xA 4.1 800xA System some
of these aspects may have been modified; for example, to adapt Function Settings,
or to change the color or layout of Function Blocks in Function Diagrams.
During the 800xA System upgrade to 800xA 5.1 the system extensions of the new
system are loaded. To keep the information about modified aspects, all aspects that
had been created by a Function Designer system extension, but later on modified are
listed in the Configuration Wizard log, and are written to Afw files, e.g.:
...\Function Designer\bin\Upgrade\410To501\Function Designer.afw
...\Function Designer\bin\Upgrade\410To501\Function Designer for
Ac800M Connect.afw
...\Function Designer\bin\Upgrade\410To501\Function Designer for FB
P/H.afw
The only way to bring these modifications back into the 800xA 5.1 System is to
manually merge the changes. Do not import the listed Afw files into the 800xA 5.1
System, because some additional properties/data might get lost. In the case of
Function Settings, look for each settings property in the 800xA 4.1 System and do
the modifications again in the 800xA 5.1 System. In the case of modified Function
Aspects (e.g. Diagram Template, Component Template), check the modifications
done in the 800xA 4.1 System and do the modifications again in the 800xA 5.1
System.

Upgrade Diagram References and Diagram Variables. In the 800xA 5.1 System
(opposite to the 800xA 4.1 System) Diagram References and Diagram Variables are
by default created as Symbol Objects. This is not true for Diagram References and
Diagram Variables created during upgrade (restore) from 800xA 4.1 Systems.

3BSE036342-510 C 263
Engineering Studio Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Convert them from Aspect Objects to Symbol Objects by use of the conversion
function described in the following procedure.
Differences between Aspect Objects and Symbol Objects are described in
Industrial IT, 800xA -Engineering, Engineering Workplace, Function Designer
(3BDS011224*).
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Object Type Structure.
3. Use the Object Browser to navigate to:
Object Types > Functional Planning > Settings
4. Select Function Upgrade in the Aspect List Area to open the Function
Upgrade aspect in the Preview Area.
5. Select the Convert Diagram References/Variables from Aspect Objects to
Symbol Objects check box and click Apply.
6. Click Run Upgrade to perform the upgrade.
This function is not suitable in the case of additional aspects on input/output
references, e.g. Graphic Elements, for typical diagrams with input/output
references that will get copied and connected via the Bulk Data Manager.

Check and Repair AES Variable Table (Applications, Controllers,

Diagrams/SCMs, and Diagram (Cm) Types). This function can be used to:
• Correct possible inconsistent data used for display of online values and external
cross references.
• Delete obsolete data and reduce aspect size.
Perform the following procedure to use this application.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Object Type Structure.
3. Use the Object Browser to navigate to:
Object Types > Functional Planning > Settings
4. Select Function Upgrade in the Aspect List Area to open the Function
Upgrade aspect in the Preview Area.

264 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Asset Optimization

5. Select the Check and Repair AES Variable Table (Applications,

Controllers, Diagrams/SCMs, and Diagram (Cm) Types) check box and
click Apply.
6. Click Run Upgrade to perform this upgrade.
Execute Check and Repair AES Variable Table in order to make the environment
support work for Function Designer.

Deleting Engineering Base Service from the Service Structure

When the 800xA System is running, delete the Engineering Base Service from the
Service Structure.
1. Use Windows Explorer to navigate to the following directory:
...\Program Files\ABB Industrial IT\Engineer IT\
Engineering Studio\DocumentParameterManager\
bin\support
2. Double-click EbServiceCleanUpUtil.exe to delete the service.

Asset Optimization
Use the following procedure after upgrading Asset Optimization. Perform only the
steps applicable to the system.
1. Asset Monitoring:
Asset Monitoring directories must be restored on every Asset Optimization
Server node defined in the system.
a. Reconfigure the value of the OPC Group Update Rate:
– Open a Plant Explorer Workplace.
– Use the Structure Selector to open the Control Structure.
– Use the Object Browser to navigate to:
Root > Asset Optimization
– Select Afw OPC-DA Asset Monitor Data Source in the Aspect List
Area.

3BSE036342-510 C 265
Asset Optimization Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

– Update the value of OPC Group Update Rate (ms) in the Preview Area
with the value recorded under Record the Value of the OPC Group Update
Rate on page 220 and click Apply.
b. If Runtime Asset Monitors are being used in the system, restore the
Runtime Asset Monitor data directory (DeviceRunTimeMSLogicStore) to
the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
The saved data contains the Runtime Asset Monitor data present at the time of the
save. Use the Runtime Asset Monitor faceplate to reset the Asset Monitors by
adding the lost time to their accumulated run time or with some known values
based on other records. Ignore any alarms occurring during the backup.
The Runtime Properties aspect on the Runtime Asset Monitor object type has
been replaced with Runtime Asset Monitor Faceplate Inputs. If any configuration
changes were made to the Runtime Properties aspect on instances of the object
prior to taking the 800xA System Backup, the aspect will not be automatically
deleted. In this case, the Runtime Asset Monitor will fail to load with an Add Item
error for the Reset Signal. In order to complete the upgrade, search for all
instances of the Runtime Properties aspect on the Runtime Asset Monitor objects
and apply any configuration changes made to the new Runtime Asset Monitor
Faceplate inputs, and then delete the Runtime Properties aspect.
c. If XY Profile Deviation Asset Monitors are being used in the system,
restore the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles) to the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
2. Maximo Integration:
cpmPlus Enterprise Connectivity Version 4.0 (ECS 4.0) must be installed in order
to access Maximo Server Version 6.2.
The Maximo Integration information (Maximo Equipment ID and Maximo
Credentials aspects) must be restored on all Asset Optimization Server nodes.
Reference the Service Structure for the Asset Optimization Server.
a. Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
to configure ECS.

266 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Asset Optimization

b. If the MxDef files were customized, restore the MxDef files to the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\MxDef\
Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
for more information on MxDef files.
c. Restore the AOMaximoModel file to the following location if the ECS
model was customized:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
d. Ensure that the ABB Maximo Connectivity system extension is loaded.
The pending fault reports residing in the system can be restored to the following
directory structure:
...\OperateITData\OptaoACDs
Restore the entire OptaoACDs folder.
3. SAP/PM Integration:
cpmPlus Enterprise Connectivity Version 4.0 (ECS 4.0) must be installed in order
to access SAP Server Version 4.7.
The SAP/PM Integration information (SAP Equipment ID and SAP Credentials
aspects) must be restored on all Asset Optimization Server nodes. Reference the
Service Structure for the Asset Optimization Server.
a. Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
to configure ECS.
b. If the SAPDef files were customized, restore the SAPDef files to the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\SAPPMDef
c. Restore the AOSAPModel file to the following location if the ECS model
was customized:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions

3BSE036342-510 C 267
Asset Optimization Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Refer to Industrial IT, 800xA - Asset Optimization, Configuration

(3BUA000118*) for more information on SAPDef files.
d. Ensure that the ABB SAP Connect system extension is loaded.
The pending fault reports residing in the system can be restored to the following
directory structure:
...\OperateITData\OptaoACDs
Restore the entire OptaoACDs folder.
4. DMS Calibration Integration.
The DMS Calibration Integration approach is changed in 800xA 5.1. Upgrade of
DMS Calibration Integration is not supported. Reconfigure the DMS Calibration
Integration based on an engineered solution.
Contact ABB technical support for more information.
5. Asset Monitors that are assigned (via the Configure option drop-down list box
on the Asset Monitor Instance on an Object) to a particular AO Server object
and Asset Optimization Server aspect (by Object name:Aspect name pair), will
not be correctly configured after the upgrade. The AOServer property will be
unconfigured and the following error message will appear:
Unable to resolve AO Server for this Asset Monitor
configuration
This must be resolved before the Asset Monitor Logic can be loaded into an
AO Server:Asset Optimization Server for execution. Refer to the Object Type
Structure for Asset Optimization, Object Type Group:AO Server, Object Type.
6. After a restore of a 800xA 5.0 SP2 system, the Asset Optimization Server
(Monitor Server/Engine) is running. The AO Server tab of the Asset
Monitoring Server aspect will show a status of good: AM Engine running.
a. Clicking the Asset Monitors tab and selecting AMs assigned to this AO
Server will show that the values in the Status column are NOT Loaded,
enabled.

268 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline PC, Network and Software Monitoring

b. Click Load all AMs to reload all enabled Asset Monitors assigned to this
AO Server.
:The Enable Write Access check box must be selected in the Asset Monitor Data
Source aspect before loading Runtime Asset Monitors into the AO Server. Refer
to System 800xA Asset Optimization Configuration (3BUA000118*) for more
information.

PC, Network and Software Monitoring

In the 800xA 5.1 and later releases, a set of IT Asset type objects are deprecated.
The new enhancements, Process Graphics 2 and Native Language Support (NLS),
are not applied to deprecated IT Asset type objects. Replacements of deprecated IT
Asset type objects are delivered in PNSM Device Library. It is recommended to
migrate deprecated IT Asset type objects to PNSM Device Library in case the
system being upgraded has all Process Graphics 2 graphics and no VB graphics.
Refer to Appendix F, Mapping of Deprecated IT Asset Object Types.
Migration from deprecated IT Asset type objects to the PC, Network and
Software Monitoring Device Library is not mandatory in case the system being
upgraded already has VB graphics.
The following steps describe the migration procedure.
1. Download IT Asset type objects in PNSM Device Library that replaces the
deprecated IT Asset type objects which are used in the current configuration.
The download link is http://www.abb.com/controlsystems.
2. Migrate each deprecated IT Asset type object to its replacement IT Asset type
object in PNSM Device Library
a. Instantiate and configure PNSM Device Library objects.
b. Delete deprecated IT Asset type objects.
Reconfigure all applications referring to deprecated IT Asset type objects. For
example, Logging of OPC data into history archive.
3. To upgrade to a newer version of the Light Generic Computer Process object
type, it is required to delete all old instances and replace them with the newer
version of the Light Generic Computer Process object type. Refer to the
Process Monitoring section of System 800xA PC, Network and Software
Monitoring Configuration.

3BSE036342-510 C 269
PNSM Device Library Restore Procedure Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Perform the following post upgrade procedure for PC, Network and Software
Monitoring.
1. If user defined Script, Resource, and Assembly files were backed up, copy the
saved files from the safe media to the following directories:
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Scripts\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Assemblies\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Resources\User

PNSM Device Library Restore Procedure

Perform the following post upgrade procedure for PNSM Device Library:
1. Copy the files from the safe location to the directory if MOF files were backed
up:
...\Program Files\ABB Industrial IT\Optimize IT\PC,
Network and Software Monitoring\MOFS
2. Copy the Process Health.dll from the safe location to the following location for
Generic Computer Node V1.0 or higher versions:
...\Program Files\ABB Industrial IT\Optimize
IT\PC, Network and Software Monitoring\Asset
Monitoring\Bin
Use the Register.dll bat file present in the Object Type to register this dll
automatically.

270 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline SMS and e-mail Messaging

SMS and e-mail Messaging

Reconfigure the GSM Device hardware information recorded in the save operation
(refer to SMS and e-mail Messaging on page 225).
It may be necessary to stop and start the Messenger Server Service in the Service
Structure after the SMS and e-mail Messaging restore operation.
During the upgrade, a second Messenger Service Group and Messenger Service
Provider will be created in the Service Structure. For instance:
Messenger SG_1, Service Group
Messenger SP_1, Service Provider
If there is already a Messenger Service Group and Messenger Service Provider
configured, the new one may be deleted.

Batch Management
Verify that the primary Batch Server is in primary mode (P is displayed in the
Windows Task bar) and the secondary Batch Server is in secondary mode (S
displayed in the Windows Task bar). If the proper modes are not displayed, enable
the Batch Service Group before proceeding.
To enable the Batch Service Group:
1. Open a Plant Explorer Workplace.
2. Select the Service Structure.
3. Select the Services\Batch Service, Service\batch_group_name, Service
Group\Service Group Definition aspect.
4. Select the Configuration tab.
5. Select the provider that is currently the secondary Batch Server.
6. Select the Enabled check box and click Apply.
7. Select the provider that is currently the primary Batch Server.
8. Select the Enabled check box and click Apply.
Batch data can be reloaded to the batch database from wherever it was archived.
The Batch history archive and restore aspect has been removed in SV5.1.

3BSE036342-510 C 271
Basic History Service Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Perform the following to view any Batch data archived from SV5.0 or previous
versions of the Batch product:
1. Create a Virtual Machine (VM) node with the existing system version and its
components.
2. Restore Batch data using the Batch Restore window onto this virtual machine.
Once the restored data is in the batch database, it can be viewed using the Batch
History Overview window.
Do not restore directly from CDs or DVDs. Restore from hard disk drives which can
be restored from CDs or DVDs using commercially available software.

Selecting the Alarm Server

To select the Alarm Server:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to select:
Services > Event Collector, Service >
Batch_AE_Service, Service Group
4. Select Service Group Definition in the Aspect List Area.
5. Select the Special Configuration tab in the Preview Area.
6. Select Produce IT Batch OPC AE Server in the Alarm Server field.
7. Click Apply.
Always perform the Toolbar configuration as described in System 800xA Batch
Management Configuration and shutdown script procedure as described in the
Batch Management section of System 800xA Post Installation (3BUA000156*).

Basic History Service

Restore the Basic History Service data as follows. Perform this procedure on every
node where the Basic History Service is running.
1. Stop the Basic History Server from the Service Structure by the following
procedure:

272 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Basic History Service

a. Open a Plant Explorer Workplace.

b. Use the Structure Browser to open the Service Structure.
c. Select the Basic History, Service > Basic, Service Group.
d. Select the Service Group Definition aspect.
e. Click the Configuration tab.
f. Clear the Enabled check box and click Apply.
2. If it is necessary to keep historical data for the time since the upgraded system
was started, copy the current Basic History log files in the following directory:
...\OperateITData\History\{provider ID}
to a temporary directory.
These files will be inserted by using the Archive Tool.
3. Delete all files under:
...\OperateITData\History\{provider ID}
4. Restore the files from the backup of Basic History Service Data to:
...\OperateITData\History\{provider ID}
5. Start the Basic History Service from the Service Structure.
6. If Step 2 was performed:
a. Open the AdvHtArchiveTool located by default in the following directory:
...\Program Files\ABB Industrial IT\Operate IT\Process
Portal A \bin
b. Use the File/Select/Open Archive command and browse to the directory
containing the history log files.
c. Open the Action/Insert Data into Logs command.
d. Accept the default values in the Time Selection dialog box.
e. Click OK to start the insertion of the saved data to the logs.

3BSE036342-510 C 273
Information Management Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

Information Management
Refer to Information Management Post Upgrade Procedures on page 426 in
Appendix E, Information Management Upgrade to perform the Information
Management post upgrade procedures.

Calculations Service
Calculations that were disabled prior to the upgrade must be enabled by selecting
the Enabled check box in the Calculations dialog box. Refer to the section on
Calculations in Industrial IT, 800xA - Information Management, Operation
(3BUF001094*).
To enable the Calculations Service:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Calculations Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Select the Enabled check box and click Apply.

Scheduling Service (Application Scheduler)

Schedules that were disabled prior to the upgrade must be enabled by selecting the
Enabled check box in the Scheduling dialog box. Refer to the section on
Scheduling in Industrial IT, 800xA - Information Management, Operation
(3BUF001094*).
To enable the Scheduling Service:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Scheduling Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.

274 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Process Engineering Tool Integration

6. Select the Enabled check box and click Apply.

Process Engineering Tool Integration

Use the following procedure after upgrading Process Engineering Tool Integration:
Restore the backed up data directory (in preparation-step prior to upgrade) to the
installed directory of Process Engineering Tool Integration. Restore the entire Xml
directory contents to:
...\Program Files\ABB Industrial IT\Engineer
IT\Engineering Studio\Process Engineering Tool
Integration\Xml

Update VB Graphics with Newer Dependencies

Use the Display Tool to search for VB graphics with newer dependencies. Use the
following selections when searching:
• Search in all structures.
• Deploy needed.
Perform a deploy with the auto resolve action on all VB graphics with newer
dependencies.

Miscellaneous Procedures
Perform the following procedures:
• Resigning Digital Signatures in 800xA 5.1.
• Restart the System.
• Reconfigure Event Collectors.
• Reconfigure Alarm and Event List Configurations.
• Add Autostart Shortcut.

Resigning Digital Signatures in 800xA 5.1

To resign digital signatures in 800xA 5.1:
1. Use Windows Explorer to locate AfwSignatureManager.exe in the
following directory:

3BSE036342-510 C 275
Restart the System Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

...\<Base System install directory>/bin

2. Double-click AfwSignatureManager.exe to launch the Signature Manager.
3. Use the File menu to open the Signature Report file saved before the upgrade.
4. When a signer is selected in the Signer column, the Aspects Signed table will
show all aspects signed by this signer and information indicating whether the
signature was valid in the 800xA 4.1 System or not.
5. Select the aspects to re-sign and click Sign.
6. A Signature dialog box will appear in which to validate the signature.
Use Ctrl+Shift+Click to select multiple aspects to sign in one operation.

Restart the System

Restart the system after performing all post upgrade procedures.

Reconfigure Event Collectors

When upgrading from 800xA 4.1 to 800xA 5.1, the Event Collectors that were
configured to use a special Collection Definition object are obsolete. Reconfigure
the Event Collectors to use the Collection Definitions objects with the 800xA 5.1
System.
The Configuration Wizard log shows which Event Collectors need to be
reconfigured with a message such as:
Objects “(SV4) ABB Hs OPC Alarm Event Server” and “ABB
Hs OPC Alarm Event Server” represent the same A&E
Server. Please configure the EventCollector to user the
new definition.
All Collection Definition objects that come from the backup system have the prefix
(SV4). These objects are located in:
Library Structure > Alarm & Event > Alarm Collection
Definitions

276 3BSE036342-510 C
Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline Reconfigure Alarm and Event List

Reconfigure Alarm and Event List Configurations

In 800xA 5.1, in most cases, the SourceName column contains GUIDs. The
recommendation in 800xA 5.1 is to reconfigure the Alarm and Event List
configurations to use the ObjectName column instead of the SourceName column.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Library Structure.
3. Use the Object browser to navigate to and select an Alarm and Event List
Configuration aspect.
4. Select Alarm and Event List Configuration in the Aspect List Area.
5. Select the Columns tab in the Preview Area.
6. Clear the SourceName check box and select the ObjectName check box.
7. Click Apply.
8. Repeat the procedure for all Alarm and Event List Configuration aspects.

Add Autostart Shortcut

It it is desired to enable the autostart of the Operator Workplace on client nodes,
perform the following:
1. Define a default workplace.
2. The shortcut must be created from the ABB Workplace login window.
3. The shortcut is located in:
...:\Documents and Settings\UserName\Start
Menu\Programs\Startup
4. Right-click the shortcut and select Properties from the context menu.
5. Add the following to the shortcut target:
/WS
-or-
/WaitForSystem
6. Click OK.

3BSE036342-510 C 277
System Backup Section 5 Upgrading 800xA 4.1 to 800xA 5.1 Offline

System Backup
Make complete hard disk and 800xA System backups of the upgraded system.

278 3BSE036342-510 C
 Section 6 Upgrading 800xA 3.1 SP3 to 800xA
5.0 SP2

Introduction
Upgrading the 800xA System requires the plant to be shut down. To guarantee
the functionality of the upgraded system, follow these upgrade instructions
carefully and perform them in the order presented.
Upgrading directly from 800xA 3.1 SP3 to 800xA 5.1 is a two-step process. It is
necessary to upgrade to 800xA 5.0 SP 2 before upgrading to 800xA 5.1. When
the procedures in this section are complete, refer to Section 3, Upgrading 800xA
5.0 SP2 to 800xA 5.1 Online or Section 4, Upgrading 800xA 5.0 SP2 to
800xA 5.1 Offline in this instruction to upgrade from 800xA 5.0 SP2 to 800xA
5.1.
Upgrading an 800xA 3.1 System with 800xA for Harmony installed on any node
in the system is a two-step process. Refer to 800xA for Harmony Release Notes
(3BUA000112*) for detailed information.
The person performing this upgrade must use the same user account that was used
during the installation of the 800xA System software, unless otherwise indicated in
these instructions.

Functional Area Naming

Some 800xA Functional Area names have been changed since the 800xA 3.1 SP3
release. Table 9 lists the Functional Area names before and after the upgrade. The
800xA 3.1 SP3 Functional Area names will be used in this section up to, but not
including System Upgrade (Upgrade Flow B) on page 306. The 800xA 5.0 SP2

3BSE036342-510 C 279
Control Builder M Compatibility Issues Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Functional Areas names will be used from that point through the remainder of the
section.

Table 9. Functional Area Naming

Name in 800xA 3.1 SP3 Name in 800xA 5.0 SP2

Control IT for AC 800M 800xA for AC 800M
FOUNDATION Fieldbus Device Device Management FOUNDATION
Integration Fieldbus
HART Device Integration Device Management PROFIBUS &
HART
PROFIBUS Device Integration
AC 400 Connect 800xA for Advant Master
Safeguard Connect 800xA for Safeguard

Control Builder M Compatibility Issues

Refer to the compatibility issues detailed in Appendix B, Control Builder M
Compatibility Issues before beginning the upgrade.

Upgrade Flow
This section is organized so that the instructions are presented in the proper upgrade
order. Do not skip any steps that pertain to 800xA software being used in the current
or upgraded system. Refer to Planning for the Upgrade on page 33 for additional
information and ideas on how to streamline the upgrade process.
Figure 29 shows a high level flow of the upgrade paths.
The upgrade process is broken down into three processes:
• Preparation (Figure 30).
• Operating system and third party software upgrade (Figure 31).
• 800xA System software and configuration data upgrade (Figure 32).
Each flow chart has active links, indicated by blue text, to help navigate through the
document (if viewing it online). Clicking in a flow element with blue text will
advance the document to the related procedure.

280 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Upgrade Flow

All paths require, after backup and before restore, installing the 800xA System
software and creating the system as if it were a new installation.

Figure 29. High Level Upgrade Flow

Figure 30. Upgrade Preparation Flow

3BSE036342-510 C 281
Upgrade Flow Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Figure 31. Operating System, Third Party, and 800xA Software Upgrade Flow

282 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Central Licensing System (Upgrade Flow A)

Figure 32. System Restore and Post Upgrade Flow

Central Licensing System (Upgrade Flow A)

Order new licenses for 800xA 5.0 SP2. The 800xA 3.1 SP3 licenses will not
work.

Consistency Check
Refer to Appendix C, Consistency Check and perform the necessary consistency
checks.
Perform a consistency check before performing the 800xA System backup.
Failure to do so could result in problems when restoring the system after the
upgrade.

3BSE036342-510 C 283
Save Digital Signatures Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Save Digital Signatures

The new support for version handling of aspect data will make all digital signatures
in 800xA 3.1 SP3 invalid when upgrading to 800xA 5.0 SP2. To simplify the
upgrade, two applications have been developed to support the re-signing of aspects
in 800xA 5.0 SP2:
• AfwSignatureReport: Used to create a report with information about signed
aspects in 800xA 3.1 SP3.
• AfwSignatureManager: Used in 800xA 5.0 SP2 to re-sign these aspects.
Perform the following before upgrading from 800xA 3.1 SP3 to 800xA 5.0 SP2.
1. Insert 800xA System Installation DVD 1 into the drive on a client in the
800xA 3.1 SP3 800xA System.
2. Copy the AfwSignatureReport.exe from the following directory on 800xA
System Installation DVD 1 to a directory on the client.
Engineering & Development\Accessories\Digital
Signatures Upgrade Tools\SV3
3. Open a Windows Command Prompt.
4. Change to the directory where AfwSignatureReport.exe was copied.
5. Run the following command:
AfwSignatureReport <filename>.xml
6. Save the signature report file <fileName>.xml on an external media during the
upgrade.
The digital signature must be valid before saving to the report file.

External Alarm Service Group

Keep only one External Alarm Service Group and move the provider or providers to
the Aspect Servers.

284 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Deploy all User Created Process Graphics

Deploy all User Created Process Graphics

800xA System backups containing undeployed user created process graphics will
result in warning and error messages later in the upgrade process. To avoid these
messages, refer to Industrial IT, 800xA - Engineering, Graphics (3BSE030335*)
and use the Display Tool to deploy all user created process graphics before
beginning the 800xA System backup.

Backups
It is important to create backups of node hard disks and the 800xA System before
starting the upgrade procedures. Valid backups insure that the system can be
restored if necessary.

Hard Disk Backup

It is recommended that a third party backup/restore and/or disk imaging utility be
used to save (and restore if necessary) hard disks before starting the upgrade
procedures.

800xA System Backup

Refer to Appendix C, Consistency Check and perform a consistency check before
performing the 800xA System backup. Failure to do so could result in problems
when restoring the system after the upgrade.
Avoid engineering or any other changes especially to the Aspect system during
the 800xA Backup process.
The Backup/Restore function makes it possible to make an online backup of a node
and perform an offline restore of the same node. A full backup stores all aspect
objects and aspect data (application data) in the Aspect Directory.
Verify the Batch Management Servers are operating normally before and during
800xA System backups (or usage of the Import/Export tool) of systems
containing Batch Management nodes. This will ensure the backup of all batch
data.
All system extensions that are part of the system must be installed and added on the
node where the backup will be taken (usually the primary Aspect Server node). No

3BSE036342-510 C 285
800xA System Backup Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

changes can be made (especially to the Aspect directory) during the online backup
process.
The following steps outline the 800xA system backup procedure. Refer to System
800xA Maintenance (3BSE046784*) for more detailed information.
Ensure that the Post Installation Procedure for Engineering Studio 3.1.0/2
Rollup 2 (refer to Release Notes 3BDS011626R3101) has been performed. Refer
also to Technical Description - Industrial IT System 800xA SV 3.x System
Software Versions (3BSE037782* (latest revision)).
For background information, refer to Product Bulletin 800xA Eng.Workplace
Eng.Studio SV3.1-SV4.0, Aspect Types falsely reset (3BDS100999).
1. Create a Full Backup Definition object in the Maintenance Structure.
2. Configure the Scope and the Storage tabs. Disable the History and System
Messages check boxes in the Scope tab.
3. Check the disk space and path in the Storage tab of the Backup Definition
aspect. A large configuration could require a minimum of five gigabytes of free
space.
4. Start the backup process.
5. In case of any warning or error messages (refer to Appendix A, Warning and
Error Messages), take the appropriate measure and create a new backup.
6. Record the number of aspects and objects in the system.
a. Select the Admin Structure\Adminstrative
Objects\Domains\system_name, Domain\Domain Definition aspect.
b. Record the number of objects and aspects listed in the System Size
Information area of the window.
c. Right-click the Control Structure\control_network_name, Control
Network\Control Structure aspect of one of the control networks
contained in the system.
d. Select Properties from the context menu.
e. Select the Statistics tab.
f. Record the number of objects listed.

286 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Pre-Upgrade Procedures

g. Right-click the Control Structure aspect within a controller project of the

control network selected in Step c.
h. Select Properties from the context menu.
i. Record the number of objects listed.
j. Repeat Step g through Step i for all the controller projects within the
control network.
k. Repeat Step c through Step j for every control network in the system.
l. Right-click the Control Structure\HSE_Subnet name, HSE Subnet\Control
Structure aspect of one of the HSE Subnets contained in the system.
m. Select Properties from the context menu.
n. Select the Statistics tab.
o. Record the number of objects listed.
p. Repeat Step l through Step o for every HSE Subnet in the system.
q. Right-click the Control Structure\MB300_name, MB300
Network\Control Structure aspect of one of the MB300 Networks
contained in the system.
r. Select Properties from the context menu.
s. Select the Statistics tab.
t. Record the number of objects listed.
u. Repeat Step q through Step t for every MB300 network in the system.
Do not manually import or edit any information in backup files.

Pre-Upgrade Procedures
Some 800xA System software requires preparatory steps before shutting down
800xA System processes. Perform the applicable procedures in the order presented.

3BSE036342-510 C 287
Control IT for AC 800M Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Control IT for AC 800M

Use the following procedure to prepare for the Control IT for AC 800M upgrade:
1. Record the memory setting for OPC Server and Control Builder found in the
Setup Wizard for each product.
2. Control Builder stores its settings (systemsetup.sys) on disk in the following
directory:
...\ABB Industrial IT Data\Engineer IT Data\Control
Builder M Professional
Copy this file to a safe media.
3. Save OPC configurations by selecting:
File > Save Configuration
in the OPC Server Panel.
4. The OPC Server stores configuration files (*.cfg) and settings
(systemsetup.sys) on disk. Copy these files to a safe media. The
systemsetup.sys file is located in:
...\ABB Industrial IT Data\Control IT Data\OPC Server
for AC 800M
The configuration files are stored in the Files folder in the same location.

Device Management and Fieldbuses

Device Management FOUNDATION Fieldbus

Verify that the FOUNDATION Fieldbus Device Integration Version 3.1.0/2
Rollup 1 and Rollup 2 have been installed before starting to save information. In
this special case, Rollup 2 does not contain the contents of Rollup 1, so make sure
that Rollup 1 has been installed before installing Rollup 2. If necessary, download
the rollups from ABB SolutionsBank (document numbers: 3BDS009928 and
3BDS009947).
User-made modifications to library objects representing FF standard blocks (these
are blocks supported by the Device Type Standard FBs as indicated in the Block
Info tab of the block class parameter dialog box) will be overwritten during

288 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Device Management and Fieldbuses

upgrade. If such changes have been made, they can be reconstructed manually.
Refer to Device Management FOUNDATION Fieldbus on page 340.

Device Management PROFIBUS & HART

Historical data sets of Device Type Manager (DTM), exported via the Fieldbus
Management aspect, along with device specific DTM files are stored as files on the
Primary Aspect Server node. These files and the PROFIBUS/HART OPC Server
configuration are stored after a successful 800xA System backup. The path to this
folder can be found as follows:
1. Open the Plant Explorer Workplace on the Primary Aspect Server node.
2. Use the Structure Selector to select the Control Structure.
3. Use the Object Browser to select the Root Object type.
4. Select the FBB PH Settings aspect.
5. Record the path information for the Primary Aspect Server found in the FBB
PH Settings aspect.
6. Use Windows Explorer to copy the folder (default: Fieldbus Builder PH)
containing device specific configuration files (in the path recorded in Step 5) to
the 800xA System backup folder, created as described in 800xA System
Backup on page 285.
7. If the folder name of the copied folder is not Fieldbus Builder PH, it must be
renamed to the default folder name (Fieldbus Builder PH) in the 800xA System
backup folder.

PROFIBUS Device Types

PROFIBUS Device Types in 800xA 5.0 and later are based on Hardware Libraries
(HWLib). This is different from previous system versions, where these Device
Types were based on Hardware Definitions (HWD). As a result, the PROFIBUS
Device Types used in connection with the Device Integration software must be

3BSE036342-510 C 289
Device Management and Fieldbuses Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

linked to new delivered Hardware Libraries to ensure system and upgrade

compatibility.
Perform the following procedure only if the exact PROFIBUS Device Type
described is used. Otherwise, this procedure can be skipped.

If the ABB_TZIDC_110-220_SP_Short module type is used in the Control Structure

of the Plant Explorer, a special upgrade procedure must be performed to ensure
upgrade compatibility in 800xA 5.0 and later. This module is delivered with the
PROFIBUS Device Integration package and its system extensions and is supported
by the ABB_TZIDC_110-220_YP0_v1_0 PROFIBUS Device Type.
The following steps requires Bulk Data Manager (BDM) (Engineering Platform)
to be installed. Perform the described steps on an Engineering system node.
1. Open the Engineering Workplace and select the Control Structure.
2. Open the Find Tool.
3. In the <Add attribute> selection box select Structure.
4. In the <Structure> selection box select Control Structure.
5. In the <Add attribute> selection box select Object Type. This displays all
instances available in the Control Structure.
6. Select the ABB_TZIDC_110-210_SP_Short module from the displayed list
and click Search. If the module type is not available, this section can be
skipped.
7. Open Bulk Data Manager in the Control Structure (right-click on the Root
node and select Advanced > Bulk Data Manager).
8. Verify that the valid system is selected in the BDM sheet.
9. Search for and select the ABB_TZIDC_110-220_SP_Short module in the
Control Structure.
10. Select Control Properties in the Aspect List Area and move it via the drag
and drop function to the BDM sheet on cell A1 in the Preview Area.
11. A new window will open in which all parameters will be selected. Confirm the
Complete selection by clicking OK.

290 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 AC 400 Connect and Safeguard Connect

12. Select cell A2 in the BDM sheet and enter the text Filter:Control
Structure.
13. Select the project containing the ABB_TZIDC_110-210_SP_Short module in
the Control Structure and move it via the drag and drop function into the
BDM sheet on cell A3.
If the module is used in different projects, the steps must be repeated for the
other projects.

14. Select the Auto filter option in the Excel sheet (select Data > Filter >
AutoFilter in the menu bar).
15. Select in line A in the BDM sheet, the column named Source Object (normally
cell C1) and click Filter.
16. Search for and select the ABB_TZIDC_110-210_SP_Short module. This will
now be the only module shown.
17. Enter the text delete for each listed module in the column named Command
(normally cell A1). The Optional selection function can be used.
18. Save the changes to the 800xA System by clicking Save All Objects. The
modules will be deleted in the Control Structure.
19. Remove the text delete for each listed module in the column named
Command.
20. The captions Short will be exchanged to Long for all listed modules in the
column named Source Object. The name will now be ABB_TZIDC_110-
210_SP_Long for all listed modules.
21. Save the changes to the 800xA System by clicking Save All Objects. The
modules will be created in the Control Structure.

AC 400 Connect and Safeguard Connect

Perform the following on each Connectivity Server node.
1. Make an RTA Board backup. Save the files:
• DATHR1.CD
• DATHR2.CD

3BSE036342-510 C 291
PLC Connect Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

• DATHR3.CD
from the folder:
...\Program Files\ABB Industrial IT\OperateIT\AC 400
Connect\AdvantBase\Data\RTA\Init\
and record which files belong to which node.
2. The following settings must be documented for reconfiguration.
– Time synchronization registry key (REVERSED_SYNC_MODE):
HKEY_LOCAL_MACHINE\SOFTWARE\ABB\AFW\SystemModules\
AfwTimeServerAdaptor\1.0-0\Private
– MB300 node and network address for RTA board in RTA board
Configuration aspect.

PLC Connect
1. If the PLC Connect IEC 60870 feature is installed and configured, the IEC
configuration must be saved. Refer to the section on configuring the IEC 60870
driver in System 800xA PLC Connect Configuration (3BSE035041*) for more
information.
2. If the PLC Connect Communication Server Pre Treatment function is being
used in the application (refer to System 800xA PLC Connect Configuration
(3BSE035041*) for more information), make a backup of PreTreat2.dll.
Pretreat2.dll is located in the following folder on the PLC Connect
Connectivity Server:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
The path is the default location of the file. If it has been placed somewhere else,
make a backup from that location.
3. Make a backup of the VB application projects for PreTreat2.dll.
4. If the Event Server Pre Treatment function is being used in the application
(refer to System 800xA PLC Connect Configuration (3BSE035041*) for more
information), make a backup of PreEvent.dll. PreEvent.dll is located in the
following folder on the PLC Connect Connectivity Server:

292 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Asset Optimization

...\ABB Industrial IT\Operate IT\PLC Connect\Bin

The path is the default location of the file. If it has been placed somewhere else,
make a backup from that location.
5. Make a backup of the VB application projects for PreEvent.dll.

Engineering Studio IO Allocation

Deactivate the auto update mode in IO Allocation.
1. Start the Engineering Workplace.
2. Open the IO Allocation tool on any object by right-clicking on the object and
selecting Advanced > IO Allocation from the context menu that appears.
3. Verify that no check mark symbol is visible in the Options > Automatic Write
Allocation to CBM menu item in the IO Allocation tool.

Asset Optimization
Preparing for the Asset Optimization upgrade requires recording some values for
post upgrade and backing up data to a safe media.

Record Values for Post Upgrade

1. Use the following procedure to record the value of the OPC Group Update
Rate.
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Control Structure.
c. Use the Object Browser to navigate to:
Root > Asset Optimization
d. Select Afw OPC-DA Asset Monitor Data Source in the Aspect List
Area.
e. Record the value of OPC Group Update Rate (ms) shown in the Preview
Area. This value must be reconfigured after the upgrade.
2. If using Maximo Integration, it is necessary to record the values of the Maximo
Equipment ID Provider Properties, as these values will not be upgraded. Refer

3BSE036342-510 C 293
Asset Optimization Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

to Maximo Server Connection Properties in the System Setup section of

Industrial IT, 800xA - Asset Optimization, Configuration (3BUA000118*) to
access these values.

Back Up Data to Safe Media

Use the following procedure to back up Asset Optimization information (perform
only the steps applicable to the system):
1. Asset Monitoring:
Asset Monitoring directories will be found on the Asset Optimization Server
node.
a. If Runtime Asset Monitors are being used in the system, save the Runtime
Asset Monitor data directory (DeviceRunTimeMSLogicStore) to a safe
media. The Runtime Asset Monitor data directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
b. If XY Profile Deviation Asset Monitors are being used in the system, save
the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles) to a safe media. The XY_Reference_Profiles
directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
2. Save Maximo Integration:
If using Maximo Integration, the Maximo Integration information must be saved
from all Asset Optimization Server nodes. Reference the Service Structure for
the name of the Asset Optimization Server nodes.
a. Although the Maximo system is separate from the 800xA System, it is a
good idea to back up the system in use. Follow Maximo standard practices
for Maximo system backup.
b. If the MxDef files were customized per the instructions in Industrial IT,
800xA - Asset Optimization, Configuration (3BUA000118*), back up the
customized MxDef files to safe media.
The customized MxDef files are located in the following directory:

294 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 PC, Network and Software Monitoring

...\Program Files\ABB Industrial IT\Optimize IT\Asset

Optimization\ABBAO\Services\MOM\MxDefs\server_name\
app_server
Where:
<server_name>\<app_server> is the combination of the MRO
Server Name and the MRO Application Server Name fields from the
Maximo Equipment ID aspect. These fields are configured in the Aspect
System Structure in the Maximo Equipment ID aspect. These fields
allow for customization of MxDef files on the Maximo Server level as
well as on the Maximo Application Server level. Refer to the Maximo
documentation for an explanation of Maximo Application Servers.
For example, the resultant path to the customized MxDef files will look
like:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\Maximo5\
MxServer
3. DMS Calibration Integration. If DMS Calibration Integration is used:
Restore DMS Calibration Integration information. Refer to the Meriam Process
Technologies Device Management System User’s Guide for information about
restoring DMS Server data.
Asset Optimization DMS Calibration Integration 800xA 5.0 SP2 functions with
DMS software Version 2.6.

PC, Network and Software Monitoring

Use the following procedure to prepare for the PC, Network and Software
Monitoring upgrade.
1. If there are user defined Script, Resource, and Assembly files they need to be
backed up. The user files are located in:
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Scripts\User

3BSE036342-510 C 295
SMS and e-mail Messaging Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

...\Program Files\ABB Industrial IT\Optimize IT\

PC, Network and Software Monitoring\bin\Configuration\
Assemblies\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Resources\User directory
Copy the files in these directories to a safe location.
2. Shut down the PC, Network and Software Monitoring Server node.
a. Use the Structure Selector to open the Service Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to:
Services > OpcDA_Connector, Service > SG_IT Server, Service Group
> OPCDA_Provider_Node Name, Service Provider
(where Node Name is the name of the PC, Network and Software
Monitoring Server node).
c. Select Service Provider Definition in the Aspect List Area.
d. Click the Configuration tab to produce a view in the Preview Area.
e. If the Enabled check box is selected, disable it and click Apply.

SMS and e-mail Messaging

Save all GSM Device hardware information. Record information for the GSM
device on the SMS and e-mail Messaging GSM Hardware Setup Worksheet shown
in Table 10.

Table 10. SMS and e-mail Messaging GSM Hardware Setup Worksheet

Item Setting/Value
Spooler Settings
Activate Outbox Spooler Checked (check and leave checked)
Activate Inbox Spooler Checked (check and leave checked)

296 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 SMS and e-mail Messaging

Table 10. SMS and e-mail Messaging GSM Hardware Setup Worksheet (Continued)

Item Setting/Value
Interval for Checking for Incoming Value: _____ Seconds Minutes (circle 1)
Messages
Port Settings
COM Port Value: COM _____
Baud Rate Value: _____
Data Bits Value: _____
Parity Value: _____
Stop Bits Value: _____
PIN and Properties
Query PIN Checked or Unchecked (circle one)
PIN (only if Query PIN is checked) Value: ___________________
Save PIN (only if Query PIN is Checked or Unchecked (circle one)
checked)
Own Number (telephone number of Value: ___________________
SIM card (including Country Code)
in GSM hardware)
Initialization String for GSM Hardware Value:
_______________________________
_______________________________
_______________________________
_______________________________

3BSE036342-510 C 297
Batch Management Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Table 10. SMS and e-mail Messaging GSM Hardware Setup Worksheet (Continued)

Item Setting/Value
General Service Properties
Name (GSM service provider) Value: ___________________
Port Value: COM _____
SMSC Value: ___________________
Default Country Code Value: ___________________
Default Prefix Value: ___________________
Number of Attempts Value: ___________________
Splitting Service Properties
Splitting Checked or Unchecked (circle one)
Optimize Splitting Checked or Unchecked (circle one)
Enumerate Splitting Checked or Unchecked (circle one)
Narrowband Sockets Checked or Unchecked (circle one)
Messaging Service Properties
Add Before Message Blank (verify and do not change)
Use for Delivery Notification Only Unchecked (verify and do not change)
Default Option 0 (verify and do not change)
Message General Properties
Replace CR LF for Incoming Checked or Unchecked (circle one)
Messages

Batch Management
1. Verify all scheduled batches are completed or terminated.
2. To archive batch history, select the batch history archive aspect. By default a
Batch History Archive aspect is located in:

298 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Batch Management

Library Structure > Batch Management, Overviews

The Batch History Archive window contains the Batch Selection and Archive
Destination tabs. However, this aspect can be added to any 800xA system
object.
During the course of each batch process run, data that documents details about
that specific batch is gathered and stored by the system in the batch database
until manually removed. Data that has been archived can still be retained in the
batch database. However, once data associated with a batch has been archived
and placed in a safe place, the data for that batch should be removed from the
batch database.
Archiving batch data has no effect on the uniqueness of the batch ID. Even
after data associated with a batch ID has been removed from the system, a
record of the batch ID will be retained on the system. The batch ID can never
be reused.
Do not archive directly to or restore directly from CDs or DVDs. Archive to or
restore from hard disk drives which can be backed up to CDs or DVDs using
commercially available software.
3. Use the Batch Management backup/restore utility to back up and PFC color
configuration information and batch IDs. Access this utility by selecting:
Start > Programs > ABB Industrial IT > 800xA System >
Batch Management > Backup Restore
Selecting any of the options listed in the backup/restore utility enables the
Backup and Restore buttons.
The options are:
– PFC color configuration.
– Batch IDs.
When Backup is selected, a standard Open File window that allows browsing
to any desired folder is presented. A confirmation window provides the chance
to cancel before the backup file is written.
4. Disable the Batch Alarm & Event Service Group and Batch Service Group
before proceeding. To disable the service groups:
a. Open a Plant Explorer Workplace.

3BSE036342-510 C 299
Information Management Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

b. Use the Structure Selector to open the Service Structure.

c. Use the Object Browser to select:
Services\Alarm & Event, Service\batch_group_name,
Service Group
d. Select Service Group Definition in the Aspect List Area.
e. Select the Configuration tab in the Preview Area.
f. Clear the Enabled check box and click Apply.
g. Determine the name of the nodes that are currently Primary and
Secondary Batch Servers,
h. Use the Object Browser to select:
Services\Batch Service, Service\batch_group_name,
Service Group
i. Select Service Group Definition in the Aspect List Area.
j. Select the Configuration tab in the Preview Area.
k. Select the provider that is currently the Secondary Batch Server.
l. Clear the Enabled check box and click Apply.
m. Select the provider that is currently the Primary Batch Server.
n. Clear the Enabled check box and click Apply.

Information Management
Perform the following procedures to prepare for the Information Management
upgrade.

End Microsoft Excel Process via Windows Task Manager

Use Windows Task Manager to manually end the EXCEL.EXE process.

Recording Archive Group Associations

Archive Groups are associated with Profile, Message, and Report logs.

300 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Information Management

1. Record these associations so that after the upgrade, these logs can be
reassociated with their respective Archive Groups. Refer to the Reading and
Managing Archive Data section in Industrial IT, 800xA - Information
Management, Data Access and Reports (3BUF001094*) to access the Archive
Groups and record the information.
2. Back up the path to Archive Group Numeric Log Entry and IM Objects Entry.

ABB Process Administration Server (PAS)

Perform the following procedure to run the PAS utility.
1. Run the Process Administration Service (PAS) utility on the Information
Management Application Server node. From the Windows Taskbar select:
Start > Settings > Control Panel > Administrative Tools > PAS >
Process Administration
This opens the Process Administration Service dialog box.
2. Click Stop All to stop all processes under PAS supervision.
3. Click Close when the dialog box indicates that all processes are stopped.
4. Use standard Windows procedures, via the Services selection from
Administrative Tools in Windows Control Panel, to place the ABB Process
Administration Service into manual and insure that it is stopped.

Information Management Backup and Restore Utility

Use the Information Management History Backup/Restore utility, via:
Start > Programs > ABB Industrial IT 800xA > Information Mgmt >
History > Backup and Restore
to create all the backup files that are required to completely back up the Information
Management History database. This includes all configuration data, log data from
both file-based and ORACLE-based logs, and the Aspect System definition file.
During a backup operation, all data in the Oracle database owned by the Oracle
History user is exported to the specified destination and compressed into a zipped
archive, along with any files that have been created to store file-based property log
entries (called flat files).

3BSE036342-510 C 301
Information Management Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

The History database can be backed up to any drive, including any mapped network
drives. The disk type should be NTFS for the backups.
To avoid any ambiguity, the backup operation produces a zipped archive of
compressed History database files for each drive that contains at least some portion
of the database, where each archive contains only the database files that are stored
on the corresponding drive. The backup utility uses the naming convention name-
drive.zip for the zipped archives that it produces. For example, if the History
database is located entirely on the C:\ drive and you wish to back up the database to
a zipped archive called hist, the backup operation will compress the database files
into a zipped archive named histDB-C.zip.
If the data files exceed two gigabytes, or if there are more than 25,000 files, then
multiple zip files will be created using the following naming convention:
• First File name-drive.zip
• Next File name-drive0001.zip
• Next File name-drive0002.zip
When backing up the History database, make sure the disk is ready and available on
the workstation on which the procedure is to occur. The log file should be checked
after the backup operation to make sure that the backup operation completed
successfully.
It is recommended that the history database be cleaned before making the backup.
Open a Windows Command Prompt window and enter hsDBMaint -clean.
Make sure the system Archive is not getting full. Temp space is required to make the
backup. If the log file indicates that the Oracle export failed, use the option to export
to a disk with more space.
To make a backup:
1. Select:
Start > Programs > ABB Industrial IT 800xA > Information Mgmt >
History > Backup and Restore
2. Verify the Create Backup Files of Current Configuration option is enabled
in the IM Historian Backup/Restore Utility window.
3. Click Next. A window for setting up the backup operation is displayed.
4. Specify the location where the backup files are to be created in the New
Directory Path for the Backup field. This path must already exist and the

302 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Information Management

directory must be empty. If necessary, click Browse to create a new directory.

Add a D:\HSDATA\History as an additional option.
The backup of the History data must be in a directory of its own, not the
D:\HSDATA\History directory. If the data is put into the D:\HSDATA\History
directory, it will get lost.
5. Verify the Only Generate Aspect Definition File option is disabled.
6. Click Next. The HsBAR Output Window is displayed.
7. Select the Automatically Close Upon Completion option.
8. After the HsBAR Output Window closes, monitor the progress in the Progress
Status area of the IM Historian Backup/Restore Utility window and click
Finish when the backup is complete.
If a message appears stating that there are inconsistencies between the log
configurations in the Aspect System and the log configurations in Oracle, it may
be because the database was not cleaned before running the backup. Use the
hsDBMaint -Clean function to clean the database and then rerun the backup. If
this does not fix the problem, contact ABB Technical Support for further
assistance.

Saving Other Information Management Related Files

There are several other files related to Information Management to be saved as part
of a total system backup.
• History Archive Data: For each archive device, go to the location specified by
the Device Filename and copy the folders under that directory to a safe
location. Do this even if automatic backup is configured.
• History Archive State Information: The folder that holds the last archive
time and other archive state information must be copied to a safe location. The
folder name is Archive and it is located in:
...\Documents and Settings\All Users\
Application Data\ABB\IM\Archive
Copy the entire folder.
• Reports: Save any report template files created in Microsoft Excel,
DataDirect, and/or Crystal Reports ®. Also save report output files created as a
result of running these reports via the Scheduling Services.

3BSE036342-510 C 303
Scheduler Service (Application Scheduler) Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

• Desktop Trends: Back up trend display, ticker display, and tag explorer files.
– Ticker files are located in:
...\My Documents\ABB Industrial IT\Inform IT\Desktop
Trends\Ticker Files
– Trend Files are located in:
...\My Documents\ABB Industrial IT\Inform IT\Desktop
Trends\HTML
– Tag Explorer files are located in:
...\Documents and Settings\~username\Application
Data\ABB Industrial IT\Inform IT\Desktop Trends
• Display Services: Back up the directories for custom users, as well as display
and user element definitions. The files are located in:
...\Program Files\ABB Industrial IT\Inform IT\Display
Services\Server\Data
Save the user-built svg and vet files.
• DataDirect: Back up custom text files for object, object type, and attribute
menus used on the DataDirect windows. The files are located in:
...\Program Files\ABB Industrial IT\Inform IT\Data
Direct\etc.
Save the user-built text files.

Scheduler Service (Application Scheduler)

Disable Schedules before stopping the servers and performing the upgrade. The
Schedules will need to be manually enabled again following the upgrade.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Scheduling Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.

304 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Calculations Service

6. Clear the Enabled check box and click Apply.

Calculations Service
Disable Calculations before stopping the servers and performing the upgrade.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Calculations Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Clear the Enabled check box and click Apply.

Basic History Service Data

Back up the Basic History folder for each Basic History Service Provider in the
Service Structure. Depending on the system, the Basic History Service data can
be present on a number of different node types (Connectivity Servers, IM Servers,
AO Servers, etc.). It is best to search for the directory described in this procedure
on all nodes, and if there is data present, back up that data.
To save Basic History Service data:
1. Stop the Basic History Server from the Service Structure.
2. Use Windows Backup (not the 800xA Backup) to backup the files in the
following directory:
...\OperateITData\History\{provider ID}
3. Start the Basic History Server again from the Service Structure.

Alarm and Event List Configurations

Alarm and Event handling has changed significantly from 800xA 3.1 SP3 to 800xA
5.0 SP2 (refer to Alarm and Event List Configurations on page 305). Document list
configurations in the 800xA 3.1 SP3 system, so they can be checked against the list
configurations in the 800xA 5.0 SP2 system.

3BSE036342-510 C 305
System Upgrade (Upgrade Flow B) Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

System Upgrade (Upgrade Flow B)

The upgrade procedures differ if upgrading a Domain Controller node or if
upgrading any other type of 800xA System node.

Domain Controller Nodes

The Microsoft Windows Operating Systems supported for Domain Controller nodes
in 800xA 5.0 SP2 are:
• Windows Server 2003 R1 with SP2.
• Windows Server 2003 R2 with SP2.
If using Windows Server 2003 R2 with SP2, unless otherwise specified, do not
enable any Windows components that are not enabled in the default installation.

The following procedures detail how to manually upgrade a Domain Controller

node. There are three different scenarios:
• Upgrading Domain Controller Node and OS without Formatting Hard Disk.
• Upgrading Domain Controller Node with Compatible OS.
• Upgrading Domain Controller Node by Formatting Hard Disk.

Upgrading Domain Controller Node and OS without Formatting Hard Disk

To upgrade a Domain Controller node and its Operating System from
Windows 2000 Server to Windows Server 2003 without disturbing the Active
Directory, follow the instructions in the following Microsoft KB Article:
http://support.microsoft.com/kb/325379
After upgrading the Operating System, perform the following procedure on the
Domain Controller node:
1. Use Add/Remove Programs via Windows Control panel to uninstall
800xA System software.
800xA System software can be identified by items that mention ABB or 800xA in
Add/Remove Programs.
2. Install Windows Server 2003 SP2 on Windows Server 2003 nodes. Follow the
procedures provided by Microsoft to install the Windows Operating System
service packs.

306 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Domain Controller Nodes

3. Install Internet Explorer. Follow the procedures provided by Microsoft to

install Internet Explorer.
4. Disable Internet Explorer Enhanced Security on Windows Server 2003 nodes
(including the Domain Controller nodes) that are using Internet Explorer 7.0
(refer to Disable Internet Explorer Enhanced Security on page 318).
5. Disable Windows Firewall.
6. Refer to Third Party Software System 800xA (3BUA000500*) and install
additional third party software, updates, and service packs for this release
approved by ABB. This document is accessible from ABB SolutionsBank.
The System Checker Tool is a standalone tool delivered with the 800xA System.
It is designed for the purpose of checking, verifying, documenting, and trouble-
shooting an 800xA System, including third party software. The installation and
use of the System Checker is described in System 800xA Tools
(2PAA101888R5021). The installation program is accessible from the Manual
Installation AUTORUN screen via Base Functionalities > Diagnostic Tools >
System Checker Tool.
7. Refer to Group Policy Management for Upgrades on page 318 and configure
the Group Policy Object.
8. Refer to Third Party Software System 800xA (3BUA000500*) and apply
updates and hot fixes approved by ABB to the existing Operating System. This
document is accessible from ABB SolutionsBank.
9. Refer to System 800xA Installation (3BSE034678*) and install all required
800xA System software.
– ABB RNRP.
– ABB Diagnostic Collection Tools.
– ABB System Checker Tool.
10. Refer to System 800xA Post Installation (3BUA000156*) and configure
Windows Firewall.

Upgrading Domain Controller Node with Compatible OS

Perform the following procedure when upgrading a Domain Controller node with a
compatible Operating System (Windows 2003 Server):

3BSE036342-510 C 307
Domain Controller Nodes Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

1. Disjoin all 800xA System nodes from the Domain Controller by joining them
to a Windows Workgroup.
2. Use Add/Remove Programs via Windows Control panel to uninstall
800xA System software.
800xA System software can be identified by items that mention ABB or 800xA in
Add/Remove Programs.
3. Install Windows Server 2003 SP2 on Windows Server 2003 nodes. Follow the
procedures provided by Microsoft to install the Windows Operating System
service packs.
4. Install Internet Explorer. Follow the procedures provided by Microsoft to
install Internet Explorer.
5. Disable Internet Explorer Enhanced Security on Windows Server 2003 nodes
(including the Domain Controller nodes) that are using Internet Explorer 7.0
(refer to Disable Internet Explorer Enhanced Security on page 318).
6. Disable Windows Firewall.
7. Refer to Third Party Software System 800xA (3BUA000500*) and install
additional third party software, updates, and service packs for this release
approved by ABB. This document is accessible from ABB SolutionsBank.
The System Checker Tool is a standalone tool delivered with the 800xA System.
It is designed for the purpose of checking, verifying, documenting, and trouble-
shooting an 800xA System, including third party software. The installation and
use of the System Checker is described in System 800xA Tools
(2PAA101888R5021). The installation program is accessible from the Manual
Installation AUTORUN screen via Base Functionalities > Diagnostic Tools >
System Checker Tool.
8. Refer to Group Policy Management for Upgrades on page 318 and configure
the Group Policy Object.
9. Refer to Third Party Software System 800xA (3BUA000500*) and apply
updates and hot fixes approved by ABB to the existing Operating System. This
document is accessible from ABB SolutionsBank.
10. Refer to System 800xA Installation (3BSE034678*) and install all required
800xA System software.

308 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Domain Controller Nodes

– ABB RNRP.
– ABB Diagnostic Collection Tools.
– ABB System Checker Tool.
11. Refer to System 800xA Post Installation (3BUA000156*) and configure
Windows Firewall.

Upgrading Domain Controller Node by Formatting Hard Disk

Perform the following procedure when upgrading a Domain Controller node by
formatting the hard disk:
Perform the procedures detailed under the following topics in Section 2 -
Prerequisites of System 800xA Installation (3BSE034678R5021) to create the
Active Directory:
• Domain Controller and DNS Server.
• Users and Groups.
• Adding Nodes to a Domain.
• Adding 800xA Domain Users to the Local Administrator Group.
Precautions:
• Disjoin all 800xA System nodes from the Domain Controller by joining them
to a Windows Workgroup.
• The IP address of the original domain must be used when configuring the new
Domain Controller.
• The Domain Name of the original domain must be used when configuring the
new Domain Controller.
• The User and Group names of the original domain must be used when
configuring the New Domain controller.
Perform the following procedure after creating the active directory:
1. Install Windows Server 2003 SP2 on Windows Server 2003 nodes. Follow the
procedures provided by Microsoft to install the Windows Operating System
service packs.
2. Install Internet Explorer. Follow the procedures provided by Microsoft to
install Internet Explorer.

3BSE036342-510 C 309
800xA System Nodes Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

3. Disable Internet Explorer Enhanced Security on Windows Server 2003 nodes

(including the Domain Controller nodes) that are using Internet Explorer 7.0
(refer to Disable Internet Explorer Enhanced Security on page 318).
4. Disable Windows Firewall.
5. Refer to Third Party Software System 800xA (3BUA000500*) and install
additional third party software, updates, and service packs for this release
approved by ABB. This document is accessible from ABB SolutionsBank.
The System Checker Tool is a standalone tool delivered with the 800xA System.
It is designed for the purpose of checking, verifying, documenting, and trouble-
shooting an 800xA System, including third party software. The installation and
use of the System Checker is described in System 800xA Tools
(2PAA101888R5021). The installation program is accessible from the Manual
Installation AUTORUN screen via Base Functionalities > Diagnostic Tools >
System Checker Tool.
6. Refer to Group Policy Management for Upgrades on page 318 and configure
the Group Policy Object.
7. Refer to Third Party Software System 800xA (3BUA000500*) and apply
updates and hot fixes approved by ABB to the existing Operating System. This
document is accessible from ABB SolutionsBank.
8. Refer to System 800xA Installation (3BSE034678*) and install all required
800xA System software.
– ABB RNRP.
– ABB Diagnostic Collection Tools.
– ABB System Checker Tool.
Refer to System 800xA Post Installation (3BUA000156*) and configure Windows
Firewall.

800xA System Nodes

The Microsoft Windows Operating Systems supported in 800xA 5.0 SP2 are:
Refer to System 800xA System Guide Technical Data and Configuration
(3BSE041434*) for specific information on what node types can be installed on
each Operating System.
• Windows XP Professional with SP2.
• Windows Server 2003 R1 with SP2.

310 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 800xA System Nodes

• Windows Server 2003 R2 with SP2.

If using Windows Server 2003 R2 with SP2, unless otherwise specified, do not
enable any Windows components that are not enabled in the default installation.

The following rules apply:

• Any existing nodes that do not have one of these Operating Systems must be
reformatted and the compatible Operating System must be installed.
• All IM (Information Management) and 800xA for AC 870P/Melody Server
nodes being upgraded must be reformatted and the Operating System installed,
even if the existing Operating System is compatible.
• All nodes being upgraded, that are not IM or 800xA for AC 870P/Melody
Server nodes, with a compatible Operating System require that the existing
Operating System be updated.
• If PROFIBUS/HART Device Integration functionality is installed in the 800xA
System, all nodes being upgraded must be reformatted and the Operating
System installed.
Refer to Upgrade Flow on page 280 for more information.

Existing Operating System

The installation will fail unless all Information Management Server, and 800xA
for AC 870P/Melody Connectivity and Configuration Server nodes being
upgraded are reformatted and the Operating System installed. This is true even if
the existing Operating System is compatible. Refer to New Operating System on
page 316.
If upgrading using an existing Operating System:
1. Close all open Windows.
2. Use Configuration Wizard to disconnect each client from the 800xA System.
This task is only visible in the Configuration Wizard on a client node when the
client node is connected to the 800xA System.
a. Launch the Configuration Wizard.
b. Select Disconnect Client and click Next.

3BSE036342-510 C 311
800xA System Nodes Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

c. Choose the 800xA System from which to disconnect the client node and
click Next.
d. Click Finish. The client node is now disconnected from the 800xA
System.
3. Use Configuration Wizard from one of the server nodes to stop the 800xA
System.
a. Launch the Configuration Wizard.
b. Select System Administration and click Next.
c. Select the 800xA System to stop and click Next.
d. Select Systems and click Next.
e. Select Stop in the Systems dialog box and click Next.
f. Click Finish in the Apply Settings dialog box.
4. Exit the Batch Redundancy Status by right-clicking the Batch Redundancy
Status icon in the Windows tray (P, S, or C) and choosing Exit from the context
menu (Figure 33).

Figure 33. Stopping the Batch Redundancy Status

5. Delete the system on each node.

a. Launch the Configuration Wizard.
b. Select System Administration and click Next.
c. Select the 800xA System to delete and click Next.
d. Select Systems and click Next.
e. Select Delete in the Systems dialog box and click Next.
f. Click Finish in the Apply Settings dialog box.

312 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 800xA System Nodes

g. Wait a few minutes. When the Configuration Wizard appears with the
Systems dialog box the deletion of the system is complete.
h. Click Exit.
6. The System Services listed must be stopped at each individual 800xA System
node. Stop these services in a controlled manner in the following sequence:
– 800xA System Clients.
– 800xA System Connectivity Servers.
– 800xA System Aspect Servers.
a. Use standard Windows procedures, via the Services selection from
Administrative Tools in Windows Control Panel, to place the following
services into manual and insure that they are stopped.
–ABB Application logger.
–ABB Client License Provider.
–ABB MMS Server for AC 800M.
–ABB OPC Server for AC 800M.
–ABB ServiceManager.
–ABB System Notification Icon.
–ABB Tool Routing Service for AC 800M.
b. Use the afwkill utility (Figure 34) to make sure all processes related to the
800xA System are stopped. From the Windows Taskbar select:

3BSE036342-510 C 313
800xA System Nodes Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Start > Programs > Accessories > Command Prompt

Figure 34. Running the afwkill Utility

c. In the Command Prompt window enter afwkill.

d. The afwkill window should be empty, indicating that all processes are
stopped. In this case click OK to close.
If processes are listed in this window, click kill all, then click OK when
the window indicates all processes are stopped (empty window).
7. Use Add/Remove Programs via Windows Control panel to uninstall
800xA System and Functional Area software. Remove the application software
before the base system software.
There may be some 800xA software on nodes (such as 800xA RNRP on the
Domain Controller node) that does not include Process Portal software. The
800xA software on these nodes also requires upgrading.
800xA System and Functional Area software can be identified by items that
mention ABB or 800xA in Add/Remove Programs.
8. Manually delete the following folder:
...:\Documents and Settings\All Users\Start Menu\
Programs\ABB Industrial IT 800xA\System\Network

314 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 800xA System Nodes

9. Reboot the workstation after all 800xA System and Functional Area software
has been removed.
10. Install Windows Server 2003 SP2 on Windows Server 2003 nodes. Follow the
procedures provided by Microsoft to install the Windows Operating System
service packs.
11. Install Internet Explorer. Follow the procedures provided by Microsoft to
install Internet Explorer.
12. Disable Internet Explorer Enhanced Security on Windows Server 2003 nodes
(including the Domain Controller nodes) that are using Internet Explorer 7.0
(refer to Disable Internet Explorer Enhanced Security on page 318).
13. Disable Windows Firewall on every node in the 800xA System.
14. Refer to Third Party Software System 800xA (3BUA000500*) and install
additional third party software, updates, and service packs for this release
approved by ABB. This document is accessible from ABB SolutionsBank.
The System Checker Tool is a standalone tool delivered with the 800xA System.
It is designed for the purpose of checking, verifying, documenting, and
troubleshooting an 800xA System, including third party software. The
installation and use of the System Checker is described in System 800xA Tools
(2PAA101888R5021). The installation program is accessible from the Manual
Installation AUTORUN screen via Base Functionalities > Diagnostic Tools >
System Checker Tool.
15. Refer to Group Policy Management for Upgrades on page 318.
16. Refer to Adding Privileges to the 800xA Service User on page 324.
17. Refer to Third Party Software System 800xA (3BUA000500*) and apply
updates and hot fixes approved by ABB to the existing Operating System. This
document is accessible from ABB SolutionsBank.
18. Refer to System 800xA Installation (3BSE034678*) and install the License
Server on the primary Aspect Server node and install the license file.

3BSE036342-510 C 315
800xA System Nodes Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

19. Refer to System 800xA Installation (3BSE034678*) and install all required
800xA System software.
If Production Management - Batch Management software is being installed,
initialize the Batch database during installation of the Production Management -
Batch Management software.
20. Refer to Setting the PAS and IM Service Account and Password on page 325
and perform that procedure before performing the 800xA System restore.
21. Refer to 800xA System Restore (Upgrade Flow C) on page 325 of this
instruction and perform all necessary steps.
22. Perform all steps that pertain to the installed applications from 800xA
Documentation Maintenance on page 330 through the remainder of this section
in the order presented.
23. Refer to System 800xA Post Installation (3BUA000156*) and configure
Windows Services and Windows Firewall.
24. Refer to Backups on page 285 and perform precautionary backups.

New Operating System

If upgrading using a new Operating System:
If formatting the Domain Controller node, disconnect all 800xA System nodes
from the Domain by joining them to a Windows workgroup before formatting the
Domain Controller node.
There may be some 800xA software on nodes (such as 800xA RNRP on the
Domain Controller node) that does not include Process Portal software. The
Operating System and 800xA software on these nodes also requires upgrading.
1. Reformat the drive.
2. Refer to System 800xA Installation (3BSE034678*) and install the new
Operating System.
3. Install Windows Server 2003 SP2 on Windows Server 2003 nodes. Follow the
procedures provided by Microsoft to install the Windows Operating System
service packs.
4. Install Internet Explorer. Follow the procedures provided by Microsoft to
install Internet Explorer.

316 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 800xA System Nodes

5. Disable Internet Explorer Enhanced Security on Windows Server 2003 nodes

(including the Domain Controller nodes) that are using Internet Explorer 7.0
(refer to Disable Internet Explorer Enhanced Security on page 318).
6. Disable Windows Firewall on every node in the 800xA System.
7. Refer to Third Party Software System 800xA (3BUA000500*) and install
additional third party software, updates, and service packs for this release
approved by ABB. This document is accessible from ABB SolutionsBank.
The System Checker Tool is a standalone tool delivered with the 800xA System.
It is designed for the purpose of checking, verifying, documenting, and
troubleshooting an 800xA System, including third party software. The
installation and use of the System Checker is described in System 800xA Tools
(2PAA101888R5021). The installation program is accessible from the Manual
Installation AUTORUN screen via Base Functionalities > Diagnostic Tools >
System Checker Tool.
8. Refer to Group Policy Management for Upgrades on page 318.
9. Refer to Adding Privileges to the 800xA Service User on page 324.
10. Refer to Third Party Software System 800xA (3BUA000500*) and apply
updates and hot fixes approved by ABB to the existing Operating System. This
document is accessible from ABB SolutionsBank.
11. Refer to System 800xA Installation (3BSE034678*) and install the License
Server on the primary Aspect Server node and install the license file.
12. Refer to System 800xA Installation (3BSE034678*) and install all required
800xA System software.
13. Refer to Setting the PAS and IM Service Account and Password on page 325
and perform that procedure before performing the 800xA System restore.
14. Refer to 800xA System Restore (Upgrade Flow C) on page 325 of this
instruction and perform all necessary steps.
15. Perform all steps that pertain to the installed applications from 800xA
Documentation Maintenance on page 330 through the remainder of this section
in the order presented.
16. Refer to System 800xA Post Installation (3BUA000156*) and configure
Windows Services and Windows Firewall.

3BSE036342-510 C 317
Disable Internet Explorer Enhanced SecuritySection 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

17. Refer to Backups on page 285 and perform precautionary backups.

Disable Internet Explorer Enhanced Security

This procedure only applies to Windows Server 2003 installations using Internet
Explorer 7.0.
Windows Server 2003 with SP2 and Internet Explorer 7.0 must be installed prior
to performing the following procedure.
The Internet Explorer Enhanced Security component must be disabled on all
Windows Server 2003 with SP2 nodes in the 800xA System that are using Internet
Explorer 7.0.
1. Select:
Start > Control Panel
2. Double-click Add/Remove Programs to launch the Add or Remove Programs
utility.
3. Click Add/Remove Windows Components to open the Windows
Components Wizard.
4. In the Components list, disable the Internet Explorer Enhanced Security
Configuration check box.
5. Click Next and then Finish.

Group Policy Management for Upgrades

The procedures differ depending on the environment (domain or Windows
Workgroup).

Domain Environment
Perform this procedure before installing 800xA System and Functional Area
software.

When upgrading from 800xA 3.1 SP3 to 800xA 5.0 SP2, it is necessary to add the
800xA 5.0 SP2 Group Policy on the Domain Controller node. It is also necessary to

318 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Domain Environment

run a command on every other 800xA System node to force the new Group Policy
Object from the Domain Controller down to each node.

Domain Controller Node

1. Insert 800xA System Installation DVD 1 into the drive.
2. Use Windows Explorer to locate gpmc.msi in the following directory:
3rd_Party_SW\Microsoft
3. Double-click gpmc.msi to install the Group Policy Management Console
with SP2. Follow the instructions in the Installation Wizard to complete the
installation.
4. When the Group Management Console with SP 1 installation is complete, from
the Windows Taskbar, select:
Start > Run
5. Enter dsa.msc in the Run dialog box and click OK to open the Active
Directory Users and Computers dialog box.
6. In the left pane of the Active Directory Users and Computers dialog box, right-
click the domain name and select Properties from the context menu to open
the Domain Properties dialog box.
7. Select the Group Policy tab in the Domain Properties dialog box.
8. Click Open to open the Group Policy Management Console.
Do not modify the default Group Policy Object itself. Create, link and modify a
new Group Policy Object.

9. In the left pane of the Group Policy Management Console, right-click the
domain name and select Create and Link a GPO Here... from the context
menu to open the New GPO dialog box.
10. Type in a name for the new Group Policy Object in the New GPO dialog box;
for example, IntranetName and click OK to return to the Group Policy
Management Console.
11. In the right pane of the Group Policy Management Console, right-click on the
new Group Policy Object and select Edit from the context menu to open the
Group Policy Object Editor.

3BSE036342-510 C 319
Domain Environment Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

12. In the left pane of the Group Policy Object Editor, navigate to:
User Configuration > Windows Settings > Internet
Explorer Maintenance > Security
13. In the right pane of the Group Policy Object Editor, double-click:
Security Zones and Content Ratings
to open the Security Zones and Content Ratings dialog box (Figure 35).

Figure 35. Security Zones and Content Ratings Dialog Box

14. Select Import the current security zones and privacy settings in the Security
Zones and Privacy frame. Since Internet Explorer Enhanced Security was
disabled under Disable Internet Explorer Enhanced Security on page 318,

320 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Domain Environment

making this selection will open the Internet Explorer Enhanced Security
Configuration dialog box shown in Figure 36.

Figure 36. Internet Explorer Enhanced Security Configuration Dialog Box

15. Click Continue in the Internet Explorer Enhanced Security Configuration

dialog box to close the dialog box and return to the Security Zones and Content
Ratings dialog box (Figure 35).
16. Click Modify Settings in the Security Zones and Content Ratings dialog box to
open the Internet Properties dialog box.
17. Click the Security tab.
18. Select the Local Intranet icon.

3BSE036342-510 C 321
Domain Environment Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

19. Click Sites to open the Local Intranet dialog box (Figure 37).

Figure 37. Local Intranet Dialog Box

20. Disable the Automatically detect intranet network check box.

21. Select the Include all local (intranet) sites not listed in other zones check
box.
22. Verify that all other check boxes are disabled.
23. Click OK three times to close all open dialog boxes.
24. Close the Group Policy Object Editor.
25. Reboot the node.
26. Return to Adding Privileges to the 800xA Service User on page 324.

All Other 800xA System Nodes

1. From the Windows Taskbar, select:
Start > Run
2. Enter gpupdate /force in the Run dialog box and click OK. This forces the
new Group Policy Object from the Domain Controller down to this node.

322 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Windows Workgroup Environment

3. Return to Adding Privileges to the 800xA Service User on page 324.

If the system is expanded at a later time, this procedure must be performed on
each node added during the expansion.

Windows Workgroup Environment

Perform this procedure before installing 800xA System and Functional Area
software.

This procedure must be performed on every node in the Windows Workgroup. If the
system is expanded at a later time, this procedure must be performed on each node
added during the expansion.
1. From the Windows Taskbar, select:
Start > Run
2. Enter gpedit.msc in the Run dialog box and click OK to open the Group
Policy Object Editor.
3. In the left pane of the Group Policy Object Editor, navigate to:
User Configuration > Windows Settings > Internet
Explorer Maintenance > Security
4. In the right pane of the Group Policy Object Editor, double-click:
Security Zones and Content Ratings
to open the Security Zones and Content Ratings dialog box (Figure 35).
5. Select Import the current security zones and privacy settings in the Security
Zones and Privacy frame. Since Internet Explorer Enhanced Security was
disabled under Disable Internet Explorer Enhanced Security on page 318,
making this selection will open the Internet Explorer Enhanced Security
Configuration dialog box shown in Figure 36.
6. Click Continue in the Internet Explorer Enhanced Security Configuration
dialog box to close the dialog box and return to the Security Zones and Content
Ratings dialog box (Figure 35).
7. Click Modify Settings in the Security Zones and Content Ratings dialog box to
open the Internet Properties dialog box.

3BSE036342-510 C 323
Adding Privileges to the 800xA Service UserSection 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

8. Click the Security tab.

9. Select the Local Intranet icon.
10. Click Sites to open the Local Intranet dialog box (Figure 37).
11. Disable the Automatically detect intranet network check box.
12. Select the Include all local (intranet) sites not listed in other zones check
box.
13. Verify that all other check boxes are disabled.
14. Click OK three times to close all open dialog boxes.
15. Close the Group Policy Object Editor.
16. Reboot the node.
17. Return to Adding Privileges to the 800xA Service User on page 324.

Adding Privileges to the 800xA Service User

This procedure only applies to the following node types. If these node types are not
present in the system this procedure can be skipped.
• 800xA for AC 870P/Melody Configuration Server nodes.
• 800xA for AC 870P/Melody Connectivity Server nodes.
• AO Server nodes for Asset Optimization.
There are some services that run under the 800xA Service User account for the
listed node types. Perform the following procedure to add the proper privileges to
the 800xA Service User account.
1. Log off the 800xA Installing User account.
2. Log on the 800xA Service User account.
3. Log off the 800xA Service User account.
4. Log on the 800xA Installing User account.

324 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2Setting the PAS and IM Service Account and

Setting the PAS and IM Service Account and Password

This procedure is only necessary if Information Management is installed in the
800xA System.
The PAS and Information Management (IM) service account and password must be
set, via the Information Management Configuration Assistant, before performing
the 800xA System restore.
1. To launch the configuration assistant, select:
Start > All Programs > ABB Industrial IT 800xA >
Information Mgmt > Configuration Assistant
2. Select the first row, Item 1.0 Set PAS and IM Service Account and
Password and click Run Selected Configuration Tool.
3. Perform the indicated actions and click Close in the Information Management
Configuration Assistant.
Close the Information Management Configuration Assistant after performing
Item 1.0 Set PAS and IM Service Account and Password. The rest
of the configuration steps will be performed during post installation procedures
after completing the software upgrade.

800xA System Restore (Upgrade Flow C)

The User Account that is used for 800xA System restore via the Configuration
Wizard must be a member of the following groups:
• IndustrialITUser.
• IndustrialITAdmin.
• Local Administrators.
Click Yes if during restore a message box appears stating:
A required system extension is not installed Name :
System_Instruction
The backup/restore utility supports the restoring of 800xA system information. The
following steps outline the 800xA system restore procedure.
Refer to System 800xA Maintenance (3BSE046784*) for more information on
restoring the system.

3BSE036342-510 C 325
800xA System Restore Procedure Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

800xA System Restore Procedure

Perform the following procedure to use the 800xA System Restore function on the
Primary Aspect Server node.
1. Start the restore procedure.
a. Select:
Start > All Programs > ABB Industrial IT 800xA > System >
Configuration Wizard
b. The Select Type of Configuration dialog box appears. Select Restore
System and click Next.
Restart the node when advised during the restore procedure.

2. Check for messages in the log file (select the View Log check box in the
Configuration Wizard). Refer to Appendix A, Warning and Error Messages to
resolve any received warning or error messages.
3. Check the CPU load in the workstation. The System Message service may
generate a high load (>90%). If this continues for longer than approximately
10 minutes, restart the service.
If a message stating that a full deploy of the Generic Control Network is needed,
click OK.
4. One node at a time, start up all nodes again and connect them to the 800xA
system in the following order:
– Aspect Server nodes.
– Connectivity Server nodes.
– Application Server nodes.
– Client nodes.
a. Use the following guidelines while connecting nodes, using the
Configuration Wizard. This must be performed on the node that is going to
be connected, not on the node on which the restore was performed.
b. If the node is an IM Server, verify that the ABB Process Administration
Service (PAS) is set to manual in the Services Control Panel (run
Services.msc from the Run dialog box). Stop the service if it is running.

326 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 800xA System Restore Procedure

c. Select Connect Node from the Select Type of Configuration dialog box.
d. Select the Primary Aspect Server (the server on which the system will run)
in the Connect to another System on Node drop down-list box, in the
Connect to System dialog box.
e. Set the current system as the default system when connecting nodes to the
system.
– In some cases, problems may be encountered when connecting nodes to
the system. Verify that the system software user settings are correct using
the Configuration Wizard. Restarting the node again may also solve the
problem.
– Wait until all services in the newly connected node are up and running
before connecting the next node. Select the Node Administration
Structure\connected_node_name\System Status Viewer aspect to monitor
the status of services. If some services will not start up, restarting the node
may help.
Do not include services that were stopped manually as part of the pre-upgrade
procedures. These will be manually restarted later in the post upgrade procedures.
f. Restart each node after it has been connected to the system.
Run the System Software User Settings until OK. Restart if it is not working and
if the message:
Invalid User
appears.
5. Record the number of aspects and objects in the system and compare these
values to those recorded when the system was backed up.
a. Select the Admin Structure\Adminstrative
Objects\Domains\system_name, Domain\Domain Definition
aspect.
b. Record the number of objects and aspects listed in the System Size
Information area of the window.
c. Right-click the Control Structure\control_network_name,
Control Network\Control Structure aspect of one of the control
networks contained in the system.

3BSE036342-510 C 327
800xA System Restore Procedure Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

d. Select Properties on the context menu.

e. Select the Statistics tab.
f. Record the number of objects listed.
g. Right-click the Control Structure aspect within a controller project of the
control network selected in Step c.
h. Select Properties on the context menu.
i. Record the number of objects listed.
j. Repeat Step g through Step i for all the controller projects within the
control network.
k. Repeat Step c through Step j for every control network in the system.
The number of aspects and objects after system restoration should be in the same
range as those recorded during system backup, although there will likely be more.
l. Right-click the Control Structure\HSE_Subnet name, HSE Subnet\Control
Structure aspect of one of the HSE Subnets contained in the system.
m. Select Properties from the context menu.
n. Select the Statistics tab.
o. Record the number of objects listed.
p. Repeat Step l through Step o for every HSE Subnet in the system.
q. Right-click the Control Structure\MB300_name, MB300
Network\Control Structure aspect of one of the MB300 Networks
contained in the system.
r. Select Properties from the context menu.
s. Select the Statistics tab.
t. Record the number of objects listed.
u. Repeat Step q through Step t for every MB300 network in the system.
The number of aspects and objects after system restoration should be in the same
range as those recorded during system backup, although there will likely be more.

328 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 IT Control Connection Items in Log

IT Control Connection Items in Log Configuration Aspects

The Process Portal log will display the following error message after completing the
800xA System Restore if there are IT Control Connection items in the Log
Configuration aspect.
E_ADV_HT_NO_LOG (ox8abb1c19)No Log
This error occurs because the IT Control Connection aspects are recreated during
the 800xA System Restore process.
Perform the following procedure to resolve the error:
1. Navigate to and locate AfwConsistencyCheck.exe in the following
directory on the installation drive:
\Program Files\ABB Industrial IT\Operate IT\Process
Portal A\bin
2. Double-click AfwConsistencyCheck.exe to launch the Consistency Check
Tool.
3. Click Add Item to open the Select Item dialog box.
4. Select the Log Configuration aspects with the error message.
5. Click Add and then Close.
6. Click Check in the Consistency Check dialog box to perform the consistency
check.
7. Select the row or rows with Repairable error messages (look in the
Repairable column).
8. Right-click and select Repair Aspect from the context menu.
9. Click Yes in the Repair dialog box. The consistency check will repair the
problem and update the Consistency Report.
10. Click the Check button again to perform a new consistency check.
11. Verify the Log Configuration aspect in the Plant Explorer Workplace.
Other warnings may appear during system upgrade. These warnings can be
ignored.

3BSE036342-510 C 329
Consistency Check Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Consistency Check
Refer to Appendix C, Consistency Check and perform the necessary consistency
checks.

800xA Documentation Maintenance

Delete all documentation aspects (denoted by an open book icon) with a category
name of Application Manual, Operating Manual, Installation Manual, or Technical
Reference Manual found in the Product Type Structure.
If any customer-specific documentation aspects have been added, it is necessary
to browse through the Product Type Structure and delete the 800xA
documentation aspects individually so that customer-specific documentation will
not be accidentally deleted.
Use the Find Tool in the Plant Explorer Workplace to find the documentation
aspects.
The System Instructions system extension must be removed (unregistered). To
unregister the System Instructions system extension from the 800xA system:
1. Use Windows Explorer to navigate to:
...:\Program File\ABB Industrial IT\Operate IT\Process
Portal A\bin
2. Double-click AfwRemoveSystemInstructions.exe to execute the
program.

Base System Considerations

There are considerations that must be taken into account with respect to alarms and
events when working with the 800xA 5.0 SP2 System. It is important to read and
understand the information about Alarm Categories in System 800xA Administration
and Security (3BSE037410*).

Connections between Alarm List and Alarm and Event OPC Server
This connection is valid only for upgrading of Alarms and Events.

330 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Connections between Alarm List and Alarm

800xA 3.1 SP3 has one layer between the clients (e.g. an alarm list) and the OPC
Alarm and Event Server that provides the alarms. This layer is realized by the Alarm
and Event Service, as shown in Figure 38.

ALARM LIST

ALARM AND ALARM AND ALARM AND

EVENT SERVICE EVENT SERVICE EVENT SERVICE

OPC ALARM AND OPC ALARM AND OPC ALARM AND

EVENT SERVER EVENT SERVER EVENT SERVER

T05252B

Figure 38. Alarm and Event Service Layer for 800xA 3.1 SP3

800xA 5.0 SP2 has two layers, realized by the Alarm Manager which is on top of
the Event Collector as shown in Figure 39.

Figure 39. Alarm Manager and Event Collector Layers for 800xA 5.0 SP2

3BSE036342-510 C 331
Automatic Configuration Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Automatic Configuration
The object tree below the Alarm and Event Service is recreated below the Event
Collector Service. The required library objects are also created.
The Alarm Manager Service is automatically configured. Some manual
configuration is also required.

Manual Configuration
Manual configuration consists of several actions.

Configure the Event Collector Service

Manual configuration is required for Event Collectors connected to Connectivity
Servers (such as, but not limited to, AC 800M).
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to navigate to:
Services > Event Collector, Service Group
and expand the tree.
4. Select a Service Group for a Connectivity Server.
5. Select Service Group Definition in the Aspect List Area.
6. Select the Special Configuration tab in the Preview Area.
7. Check to see if the item in the Collection Definition drop-down list box is the
the new one that is to be used with 800xA 5.0 SP2. (The name should not end
with (SV3)).
8. If the Collection Definition is not the new one that is to be used with 800xA 5.0
SP2, change the value so that it is and click Apply.
9. Select the Configuration tab.
10. Clear the Enabled check box and click Apply.
11. Select the Enabled check box and click Apply. This will restart the Service
Group.

332 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Manual Configuration

12. Repeat this procedure for all Connectivity Server Service Groups.

Organize the Library Objects

The upgrade code creates one library object per Alarm and Event Service Group
that was found in the backup. The library objects are located below the Alarm
Collection Definitions object in Library Structure. The intention, however, is that
there should be one library object per OPC Alarm and Event Server type that exists
in the system, because the library object describes the capabilities of an OPC Alarm
and Event Server. All groups working towards a specific OPC Alarm and Event
Server type can share one library object.
After an upgrade, the structure should be organized so that it complies with this
intention. Do not forget to update the settings that refer to the library object in the
Event Collector Service Groups, in the Special Configuration tab of the Service
Group Definition aspect.

Check the Alarm Manager Service Configuration

In 800xA 3.1 SP3, it is possible to have a number of Alarm and Event Service
groups, all with individual configurations. In 800xA 5.0 SP2, these groups are
replaced with one group. Consequently, the individual configurations are replaced
with one configuration. This common configuration is automatically generated from
the individual configurations and should be checked, because:
• There are one or more new parameters that should be configured.
• Backed up data may be ambiguous. One Alarm and Event Service group might
have another configuration than another group in the backed up system.
• Modifications might need to be made.

3BSE036342-510 C 333
Manual Configuration Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

The configuration is found in the Special Configuration tab of the Service Group
Definition aspect of the Alarm Manager Service group (Figure 40).

TC07437B

Figure 40. Service Group Definition Aspect (Special Configuration Tab)

Add Redundancy For Alarm Manager

The upgrade creates one service provider for the Alarm Manager, configured to
execute in the node in which the upgrade takes place. If the backed up system had
redundant Aspect Servers, it is recommended to add service providers for the Alarm
Manager according to the same configuration as for other services that execute in
Aspect Servers. However, this should be done after the server nodes have been
connected to the system.

334 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Restoring Application and Historical Data

Restoring Application and Historical Data

The remainder of this section describes how to restore historical data and the
necessary data for each Functional Area.

Device Management and Fieldbuses

If the system contains Fieldbus devices, the Restore Device Types procedures
must be performed before restoring the Control Builder M project or the upgrade
will fail. The Control Builder M upgrade can be done only once.
After installation of 800xA 5.0 SP2 software all third party software for Device
Type Objects used in the previous system version must be reinstalled. Additionally
PROFIBUS Device Type Objects used in the Control Builder M project must be
adapted to new delivered Hardware Libraries. Check that all licenses are valid for
the restore, even for third party devices.

Restore Fieldbus Device Types

Restore the Device Types on the Primary Aspect Server node before starting to
install them on other system nodes. Do not run parallel installations of Device
Types on other system nodes unless all Device Types are restored on the Primary
Aspect Server node. Installation of Device Types on other system nodes can be
done in parallel after they are restored on the Primary Aspect Server node.
The procedures in the System Restore Wizard function in the Device Library
Wizard must be performed for Fieldbus Device Types before restoring the
Control Builder M project, otherwise the upgrade will fail. The Control
Builder M upgrade can only be performed once.
The following steps for Fieldbus Device Types need to be carried out on every
800xA system node. Perform the System Restore Wizard procedure on the nodes in
the following sequence:
• Aspect Servers (including redundant Aspect Servers).
• Connectivity Servers (including redundant Connectivity Servers).
• Application Servers.
• Clients.
1. Start the Device Library Wizard. Select:

3BSE036342-510 C 335
Device Management and Fieldbuses Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Start > All Programs > ABB Industrial IT 800xA > Device Mgmt >
Device Library Wizard
-or-
double-click the Device Library Wizard icon on the desktop.
2. Navigate to:
Device Type Administration > System Restore Wizard
and choose the first option in the System Restore Wizard as shown in Figure 41
and click Next.

Figure 41. System Restore Wizard (1)

336 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Device Management and Fieldbuses

3. Choose whether or not this system node has been reformatted as shown in
Figure 42 and click Next.

Figure 42. System Restore Wizard (2)

If the system node has not been reformatted (second option), the following steps
are not necessary when PROFIBUS Device Types are not present in the system
node. In this case, the Device Library Wizard will perform an update of Fieldbus
Device Types (refer to Update Fieldbus Device Types on page 340).
4. Depending on which fieldbus protocol is used in the previous system version
environment, insert one of the delivered Device Library system DVDs in the
DVD drive (e.g. Device Library HART – DVD).
5. Click Browse and navigate to the DVD drive.
6. When the drive has been selected in the Browse for folder dialog box, click OK
in that dialog box and then Next in the ABB Device Library Wizard.
7. The Device Library Wizard scans the 800xA System for fieldbus device types
that are already used and compares the results with the contents of the DVD.

3BSE036342-510 C 337
Device Management and Fieldbuses Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Device Types available in the 800xA System and the DVD are shown in the
Extract tab of the Device Library Wizard (Figure 43).

Figure 43. Extract Device Type Files

8. Click Next to start the extraction process.

9. Device Types available in the 800xA System but not on the DVD are displayed
in the Missing tab. If there are any Device Types showing in the Missing tab,
Next in the Device Library Wizard is disabled. Navigate to the Browse dialog
box by clicking Back and inserting a new Device Library DVD in the DVD
drive.
10. Repeat this procedure until all Device Types are extracted to the 800xA System
node and the Missing tab does not list any device types.
11. If the Device Library DVDs do not contain all Device Types used in the
previous system version, the missing Device Types must be downloaded from
ABB SolutionsBank.
It is only possible to complete the Wizard if all Device Types have been
successfully extracted.

338 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Device Management and Fieldbuses

12. When the extraction process is completed successfully, the Device Types need
to be re-installed on the 800xA System node. Click Next to launch the Re-
installation of Device Types dialog box shown in Figure 44.

Figure 44. Re-install Device Types Dialog Box

13. Follow the Device Library Wizard procedure to complete the installation. The
Device Library Wizard will automatically navigate to the main window after
the process is completed.
14. Exit the Device Library Wizard and repeat the procedure on the other 800xA
System nodes, if applicable.

3BSE036342-510 C 339
Device Management and Fieldbuses Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Update Fieldbus Device Types

If the system node has not been reformatted (second option in Figure 42), all Device
Types that exist in the 800xA System node and need updated are displayed in the
Update tab (Figure 45).

Figure 45. Update of Device Types Dialog Box

1. Click Next to launch the update.

2. The Selection Summary dialog box will appear showing the Device Types to be
updated. Click Next to continue.
3. Follow the Device Library Wizard procedure to complete the installation. The
Device Library Wizard will automatically navigate to the main window after
the process is completed.

Device Management FOUNDATION Fieldbus

Perform the following to complete upgrading Device Management FOUNDATION
Fieldbus.

340 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Device Management and Fieldbuses

1. Update LD 800HSE Linking Devices: Update all LD 800HSE linking devices

to the latest firmware version released for this system environment following
the update procedure described in the user instructions for the particular device.
Refer to Field IT, Foundation Fieldbus Linking Device, LD 800HSE, Version
Table (3BDS009910) in ABB SolutionsBank for the latest linking device
firmware released for this system environment.
From Downloads Explorer, navigate to:
Control Products and Systems/800xA/Device Management Foundation
Fieldbus/Foundation Fieldbus Linking Device LD800HSE
2. Check, Save, and Upload FF Libraries:
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Object Type Structure.
c. Use the Object Browser to navigate to:
FF Libraries Object Type Group
d. Select FF Upload in the Aspect List Area.
e. Click Open Library in Fieldbus Builder FF.
f. Open the library in Fieldbus Builder FF.
g. Click Edit Library.
h. Right-click FF H1 Device Library in the Libraries dialog box of the
Fieldbus Builder FF.
i. In the Parameter dialog box, click Reload Standard Dictionary and
browse to the following directory:
j. ...\Fieldbus Builder FF\ff
k. Select STANDARD.DCT and click Open and then OK.
l. Check the libraries for plausibility and store them in Fieldbus Builder FF.
m. Exit Fieldbus Builder FF.
n. Return to the Plant Explorer Workplace and click the Library Upload tab
in the Preview Area.
o. Click Upload FF Library.

3BSE036342-510 C 341
Device Management and Fieldbuses Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

p. After a successful upload, the green traffic light symbol indicates that the
FF libraries have been synchronized.
3. Optional: Reconstruct User-made Changes to Library Objects representing FF
Standard Blocks:
This step is only required if changes were made to library objects representing FF
standard blocks.
During upgrade, user-made changes to library objects representing FF
standard blocks have been overwritten. Important substitutions have been
logged.
a. If such changes were made, display the substitutions as follows:
– Open a Plant Explorer Workplace.
– Use the Structure Selector to open the Object Type Structure.
– Use the Object Browser to navigate to:
FF Libraries Object Type Group
– Select FF Upload in the Aspect List Area.
– Select Warnings tab.
b. For reconstructing user-made changes, reapply the changes to the library
objects manually.
4. Check, Save, Commission, and Upload the HSE Subnet.
Perform the following procedure for each HSE Subnet.

a. Open a Plant Explorer Workplace.

b. Use the Structure Selector to open the Control Structure.
c. Use the Object Browser to navigate to:
HSE Subnet
d. Select FF Upload in the Aspect List Area.
e. Click the HSE Subnet Reference tab in the Preview Area.
f. Click Open Subnet in Fieldbus Builder FF.

342 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 800xA for AC 800M

g. Check to see if the configured HSE subnet ID is used for the OPC Server
FF configuration in FF Network > Properties and modify it if required.
h. Check whole project for plausibility and save the configuration in
Fieldbus Builder FF.
i. Perform device assignment for all linking devices LD 800HSE.
j. Perform precommissioning/commissioning for all objects for which this is
necessary (discernible from engineering status).
To assign all H1 devices in one step, use the Assign all devices function from the
HSE Subnet context menu: Object > Assign all devices...
For downloading use the online dialog from the HSE Subnet context menu:
Object > Online Dialog...
k. Exit Fieldbus Builder FF and save changes if prompted to do so.
l. Return to the Plant Explorer Workplace and select FF Upload in the
Aspect List Area.
m. The green traffic light symbol indicates that the HSE Subnet has been
synchronized.

800xA for AC 800M

After upgrading a configuration containing one Engineering and one Production
system to 800xA 5.0 SP2, the Control Builder M projects in the two systems
should be made identical using the Import/Export tool, Engineering Repository,
or by recreating the Engineering System using Backup/Restore before
engineering work is restarted. Otherwise there will be a lot of false differences on
the AC 800M aspects reported in the import difference report when moving
solutions between the systems.
There may be Control Builder M compatibility issues when upgrading from
800xA 3.1 SP3 to 800xA 5.0 SP2. Review the issues detailed in 800xA 3.1 SP3 to
800xA 5.0 SP2 Compatibility Issues on page 396 before proceeding
Use the following procedure to restore 800xA for AC 800M information:
1. Configure the memory setting for OPC Server and Control Builder (found in
the Setup Wizard for each product) to the saved and recorded values.
2. Control Builder stores its settings (systemsetup.sys) on disk in the following
directory:

3BSE036342-510 C 343
800xA for AC 800M Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

...\ABB Industrial IT Data\Engineer IT Data\Control

Builder M Professional
Copy the previously saved file from the safe media to this folder.
3. New handling for Hardware Types was introduced in 800xA 5.0. All hardware
types are now packaged in libraries. Because of this all Control Builder
projects must be upgraded according to the following steps.
If the application contains FOUNDATION Fieldbus, HART, or PROFIBUS
specific configurations, perform post upgrade procedures for Device Types via
the Device Library Wizard (refer to Device Management and Fieldbuses on page
335) before upgrading the project in Control Builder M.
a. Start an empty Control Builder M .
b. Select:
Tools > Maintenance > Upgrade Project > from Control Builder
Professional 3.4 or later
c. Select the Control Builder project to upgrade. This step will take a while.
All hardware objects in the Control Structure are redirected by Control
Builder to use hardware types from libraries. If the project contained
custom hardware definition files, libraries with corresponding hardware
types are automatically created by Control Builder.
d. Repeat Step a through Step c for all Control Builder projects in the
system.
e. When all Control Builder Projects are upgraded the old hardware types
should be deleted from the Object Type Structure.
In the Plant Explorer Workplace, navigate to the Object Type Structure
and browse to:
Object Types > Control System > AC800M/C Connect -
Controller Hardware
Right-click the Controller Hardware object and select Delete.
4. Modify the application program according to applicable issues in 800xA 3.1
SP3 to 800xA 5.0 SP2 Compatibility Issues on page 396.

344 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 800xA for Advant Master and 800xA for

5. Load the controllers with their firmware and applications. Change Analysis
Mismatches may be shown for objects in the Standard Libraries during the first
download after the upgrade. Possible mismatches are:
Mismatch: Variable has changed data type.
Mismatch: Variable not found.
Mismatch: Control Module not found.
The mismatches reflect internal changes in the Standard Libraries. No Cold
Retain Values will be lost. Click Next Mismatch to continue.
6. The OPC Server stores configuration files (*.cfg) and settings
(systemsetup.sys) on disk. Add the files saved on the safe media to the system.
The systemsetup.sys file is located in:
...\ABB Industrial IT Data\Control IT Data\OPC Server
for AC 800M
The configuration files are stored in the Files folder in the same location.
7. Restore OPC configurations by selecting File > Load Configuration in the
OPC Server Panel.
Remember to enable autoloading of the configuration and provide the correct
path to the file.

800xA for Advant Master and 800xA for Safeguard

Perform the following on each Connectivity Server node:
1. Copy the saved files:
– DATHR1.CD
– DATHR2.CD
– DATHR3.CD
to the folder:
...\Program Files\ABB Industrial IT\OperateIT\AC 400
Connect\AdvantBase\Data\RTA\Init\
to the node where they belong.
2. Open the MB 300 RTA Settings dialog box in Configuration Wizard and
reconfigure:
– MB 300 Node and Network Numbers.

3BSE036342-510 C 345
PLC Connect Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

– Check 800xA as Clock Master in case the time synchronization key

REVERSED_SYNC_MODE was enabled before.
3. Always Restart the RTA board.
4. The Audible property must be 0 for events and 1 for alarms 800xA for Advant
Master version 4.1 SP1 RU6 and newer. Refer to System 800xA Configuration
(3BDS011222*) for configuration of audible alarms.
Safeguard standardevent 300 - 326 does not comply with this rule before
800xA for 800xA for Advant Master Version 5.0 SP2. The Event numbers
where the Audible property should be changed from 1 to 0 are:
– EVENT302.
– EVENT305.
– EVENT310.
– EVENT312.
– EVENT320.
– EVENT321.
– EVENT322.
– EVENT325.

PLC Connect
Perform the following post upgrade procedures for PLC Connect.

Modify Installation for IEC60870 or Basic Project Objects

If either the IEC60870 or Basic Project Objects features were installed:
1. Use standard Windows procedures to access Add/Remove Programs in
Windows Control Panel.
2. Select ABB PLC Connect.
3. Select Change/Modify.
4. The InstallShield Wizard for PLC Connect appears. Refer to System 800xA
Installation (3BSE034678*) to select and install the desired features.
5. If the IEC60870 feature is installed refer to System 800xA PLC Connect
Configuration (3BSE035041*) and reload the saved IEC configuration.

346 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 PLC Connect

Restoring PreTreat2.dll
To restore PreTreat2.dll:
1. If the PLC Connect Communication Server Pre Treatment function is being
used in the application, copy PreTreat2.dll from the backup location to the
same folder as it was backed up from on the PLC Connect Connectivity Server.
If the default folder is used, that location is:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
2. Register the PreTreat2.dll file (refer to System 800xA PLC Connect
Configuration (3BSE035041*) for more information).
3. Restart the PLC Connect Connectivity Server for the changes to take effect.
4. Restore the VB project for PreTreat2.dll.

Restoring PreEvent.dll
To restore PreEvent.dll:
1. If the PLC Connect Event Server Pre Treatment function is being used in the
application, copy PreEvent.dll from the backup location to the same folder
as it was backed up from on the PLC Connect Connectivity Server. If the
default folder is used, that location is:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
2. Register the PreEvent.dll file (refer to System 800xA PLC Connect
Configuration (3BSE035041*) for more information).
3. Restart the PLC Connect Connectivity Server for the changes to take effect.
4. Restore the VB application project for PreEvent.dll.

Redeploy the PLC Connect Configuration

To redeploy the PLC Connect configuration:
1. Use the Structure Selector to open the Control Structure in the Plant Explorer
Workplace.
2. Use the Object Browser to navigate to the first Generic Control Network
object.

3BSE036342-510 C 347
Engineering Studio Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

3. Select Deploy in the Aspect List Area.

4. Press the SHIFT key and click Deploy in the Preview Area to ensure that a full
deploy is done.
5. The deploy begins and the progress is displayed in the Preview Area. The
deploy is completed when Deploy ended is displayed.
6. Repeat the procedure for any additional Generic Control Network objects.

Engineering Studio
Post upgrade procedures for Engineering Studio include those for IO Allocation,
Engineering Templates, and Function Designer.

IO Allocation
Before working with the IO Allocation function in an upgraded system, check all
Control Builder Name aspects of CBM_Signal instances to see if they contain a
valid name.
All Control Builder Name aspects having an empty name or a name not
introduced by synchronization from the Name aspect must be corrected
accordingly. This can be performed using a Bulk Data Manager worksheet that
reads out Name and Control Builder Name. The same worksheet can be used to
write back the Name.
The following procedure is only required if HART devices and IO signals will be
merged into one object.
800xA 5.0 SP2 supports merging of Hart devices and IO signals within one object.
If Hart devices and IO signals will be merged into one object refer to Industrial IT,
800xA - Engineering, Engineering Workplace, Basic Engineering Functions
(3BDS011223*).
The following procedure is only required when working with IO Allocation and if
properties of IO boards have been changed directly in Control Builder M.
IO Allocation has enabled new properties (e.g. Inverted) to be accessible for
CBM_SignalParameter/CBM_PulseSignalParameter. These properties are
initialized with a default value. If properties have been changed directly in the
Hardware Editor of Control Builder M (as they were not supported by IO

348 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Engineering Studio

Allocation) these changes are not reflected in

CBM_SignalParameter/CBM_PulseSignalParameter aspects after the upgrade.
Therefore, when the menu write Allocation into CBM is performed, values may be
overwritten with their default value. After upgrading, select controller by controller
and perform the menu Read Allocation from CBM, which reads the property
values from Control Builder M and updates the signal objects.

Engineering Templates for Bulk Data Manager (BDM)

Engineering Templates are typically used from scratch, meaning data is dropped
into the templates. The result is used for information or documentation. In this case
no upgrade is required, because the installation of Engineering Studio 5.0 SP2
exchanges the Engineering Templates in:
...\Documents and Settings\All Users\Desktop
However, if a worksheet containing data has been saved in the file system for
writing back to the 800xA System after upgrade, either:
• Newly create the worksheet based on an Engineering Template delivered with
Engineering Studio 5.0 SP2.
-or-
• Update the worksheet according to the description in:
...\Documents and Settings\All Users\Desktop\
Engineering Templates\ Upgrade Description Engineering
Templates.doc

Function Designer

Modified Aspects of Function Designer System Extension. The Function

Designer system extensions:
The Function Designer system extensions:
• Function Designer.
• Function Designer for AC800M Connect.
• Function Designer for AC 800M SB2 Libraries.
• Function Designer for Fieldbus Builder PROFIBUS/HART.

3BSE036342-510 C 349
Engineering Studio Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

mainly consist of:

• Functional Planning Object Types, including a Function Settings aspect at the
Settings Object Type Group.
• Extension Libraries that add Function Designer Aspects to Object Types
(Control Modules, Function Blocks, ...) created by basic libraries (AC 800M
Connect, AC 800M SB2 Libraries, etc.).
After having loaded such a system extension in the 800xA 4.1 800xA System some
of these aspects may have been modified; for example, to adapt Function Settings,
or to change the color or layout of Function Blocks in Function Diagrams.
During the 800xA System upgrade to 800xA 5.0 SP2 the system extensions of the
new system are loaded. To keep the information about modified aspects, all aspects
that had been created by a Function Designer system extension, but later on
modified are listed in the Configuration Wizard log, and are written to Afw files,
e.g.:
...\Function Designer\bin\Upgrade\313To501\Function Designer.afw
...\Function Designer\bin\Upgrade\313To501\Function Designer for
Ac800M Connect.afw
...\Function Designer\bin\Upgrade\313To501\Function Designer for
Ac800M SB2Libs.afw
...\Function Designer\bin\Upgrade\313To501\Function Designer for FB
P/H.afw
The only way to bring these modifications back into the 800xA 5.0 SP2 System is to
manually merge the changes. Do not import the Afw files above into the 800xA 5.0
SP2 System, because some additional properties/data might get lost. In the case of
Function Settings, look for each settings property in the 800xA 4.1 System and do
the modifications again in the 800xA 5.0 SP2 System. In the case of modified
Function Aspects (e.g. Diagram Template, Component Template), check the
modifications done in the 800xA 4.1 System and do the modifications again in the
800xA 5.0 SP2 System.

Upgrade Diagram References and Diagram Variables. In the 800xA 5.0 SP2
System (opposite to the 800xA 3.1 SP3 800xA System) Diagram References and
Diagram Variables are by default created as Symbol Objects. This is not true for
Diagram References and Diagram Variables created during upgrade (restore) from

350 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Engineering Studio

800xA 3.1 SP3 800xA Systems. Convert them from Aspect Objects to Symbol
Objects by use of the conversion function described in the following procedure.
Differences between Aspect Objects and Symbol Objects are described in
Industrial IT, 800xA -Engineering, Engineering Workplace, Function Designer
(3BDS011224*).
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Object Type Structure.
3. Use the Object Browser to navigate to:
Object Types > Functional Planning > Settings
4. Select Function Upgrade in the Aspect List Area to open the Function
Upgrade aspect in the Preview Area.
5. Select the Convert Diagram References/Variables from Aspect Objects to
Symbol Objects check box and click Apply.
6. Click Run Upgrade to perform the upgrade.
This function is not suitable in the case of additional aspects on input/output
references, e.g. Graphic Elements, for typical diagrams with input/output
references that will get copied and connected via the Bulk Data Manager.

Check and Repair AES Variable Table (Applications, Controllers

Diagrams/SCMs, and Diagram (Cm) Types). This function can be used to:
• Correct possible inconsistent data used for display of online values and external
cross references.
• Delete obsolete data and reduce aspect size.
Perform the following procedure to use this application.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Object Type Structure.
3. Use the Object Browser to navigate to:
Object Types > Functional Planning > Settings
4. Select Function Upgrade in the Aspect List Area to open the Function
Upgrade aspect in the Preview Area.

3BSE036342-510 C 351
Asset Optimization Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

5. Select the Check and Repair AES Variable Table (Applications,

Controllers, Diagrams/SCMs, and Diagram (Cm) Types) check box and
click Apply.
6. Click Run Upgrade to perform this upgrade.
Execute Check and Repair AES Variable Table in order to make the environment
support work for Function Designer.

Asset Optimization
Use the following procedure after upgrading Asset Optimization. Perform the steps
applicable to the system.
1. Asset Monitoring:
Asset Monitoring directories must be restored on the Asset Optimization Server
node.
a. Reconfigure the value of the OPC Group Update Rate:
– Open a Plant Explorer Workplace.
– Use the Structure Selector to open the Control Structure.
– Use the Object Browser to navigate to:
Root > Asset Optimization
– Select Afw OPC-DA Asset Monitor Data Source in the Aspect List
Area.
– Update the value of OPC Group Update Rate (ms) in the Preview Area
with the value recorded under Record Values for Post Upgrade on page
293 and click Apply.
b. If Runtime Asset Monitors are being used in the system, restore the
Runtime Asset Monitor data directory (DeviceRunTimeMSLogicStore).
The Runtime Asset Monitor data directory is located in:

352 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Asset Optimization

...\Program Files\ABB Industrial IT\Optimize IT\Asset

Optimization\AssetMonitorEnvironment\Bin
The saved data contains the Runtime Asset Monitor data present at the time of the
save. Use the Runtime Asset Monitor faceplate to reset the asset monitors by
adding the lost time to their accumulated run time or with some known values
based on other records. Any alarms that were occurring during the backup should
be ignored.

The Runtime Properties aspect on the Runtime Asset Monitor object type has
been replaced with Runtime Asset Monitor Faceplate Inputs. If any configuration
changes were made to the Runtime Properties aspect on instances of the object
prior to taking the 800xA System Backup, the aspect will not be automatically
deleted. In this case, the Runtime Asset Monitor will fail to load with an Add Item
error for the Reset Signal. In order to complete the upgrade, search for all
instances of the Runtime Properties aspect on the Runtime Asset Monitor objects
and apply any configuration changes made to the new Runtime Asset Monitor
Faceplate inputs, and then delete the Runtime Properties aspect.
c. If XY Profile Deviation Asset Monitors are being used in the system,
restore the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles). The XY_Reference_Profiles directory is
located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
2. Maximo Integration:
If using Maximo Integration, the Maximo Integration information must be
restored on all Asset Optimization Server nodes. Reference the Service
Structure for the Asset Optimization Server.
a. If the MxDef files were customized, restore the MxDef files to the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\ MOM\MxDefs\
server_name\app_server
Where:
<server_name>\<app_server> is the combination of the MRO
Server Name and the MRO Application Server Name fields from the

3BSE036342-510 C 353
Asset Optimization Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Maximo Equipment ID aspect. These fields are configured in the Aspect

System Structure in the Maximo Equipment ID aspect. These fields
allow for customization of MxDef files on the Maximo Server level as
well as on the Maximo Application Server level. Refer to Maximo
documentation for an explanation of Maximo Application Servers.
For example, the resultant path to the customized MxDef files will look
like:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\Maximo5\
MxServer
Refer to Industrial IT, 800xA - Asset Optimization, Configuration
(3BUA000118*) for more information on MxDef files.
b. It is necessary to configure the values of the Maximo Equipment ID
Provider Properties, as these values are not upgraded. These values should
have been recorded in Step 2 under Record Values for Post Upgrade on
page 293. Refer to Maximo Server Connection Properties in the System
Setup section of Industrial IT, 800xA - Asset Optimization, Configuration
(3BUA000118*) to configure these values.
3. DMS Calibration Integration. If using DMS Calibration Integration:
Asset Optimization DMS Calibration Integration 800xA 5.0 SP2 functions with
DMS software Version 2.6.
a. Restore DMS Calibration Integration information. Refer to the Meriam
Process Technologies Device Management System User’s Guide for
information about restoring DMS Server data.
b. Perform an 800xA > DMS synchronization to insure that the 800xA
objects correctly map to the Devices within DMS.
4. Asset Monitors that are assigned (via the Configure option drop-down list box
on the Asset Monitor Instance on an Object) to a particular AO Server object
and Asset Optimization Server aspect (by Object name:Aspect name pair), will
not be correctly configured after the upgrade. The AOServer property will be
unconfigured and the following error message will appear:
Unable to resolve AO Server for this Asset Monitor
configuration

354 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Asset Optimization

This must be resolved before the Asset Monitor Logic can be loaded into an
AO Server:Asset Optimization Server for execution. Refer to the Object Type
Structure for Asset Optimization, Object Type Group:AO Server, Object Type.
5. In the Control Structure, open the AOServer1, AOServer object, Asset
Optimization Server aspect.
a. Service Hostname MUST be configured. It may be necessary to navigate
into the Service Structure to the AssetMonitoring Service Provider to set
the Node and enable the service. There is a navigation button for
convenience.
b. Target State should be Service, i.e. Engine is running.
c. On all objects that have Asset Monitor aspects, check the Asset Monitor
tab in the Config View of the aspect for the Server Assignment and
Assigned to. These fields may upgrade as blank or unassigned.
6. After a restore of a 800xA 5.0 SP2 system, the Asset Optimization Server
(Monitor Server/Engine) is running. The AO Server tab of the Asset
Monitoring Server aspect will show a status of good: AM Engine running.
a. Clicking the Asset Monitors tab and selecting AMs assigned to this AO
Server will show that the values in the Status column are NOT Loaded,
enabled.
b. Click Load all AMs to reload all enabled Asset Monitors assigned to this
AO Server.
7. In earlier versions of Asset Optimization, all Asset Optimization alarms were
written as alarm category soft alarm. Starting with Asset Optimization 800xA
5.0, these soft alarms are replaced with two new categories: Asset Condition
Alarm and Asset Monitoring Status Alarm. Therefore, any existing Alarm and
Event Lists that filtered on soft alarms for the purpose of viewing Asset
Optimization alarms, must have their filters changed.
8. Starting with Asset Optimization 800xA 5.0, Object Type Inheritance is
supported. That is, an Asset Monitor on the Object Instance will inherit its
configuration from the Asset Monitor in the Object Type if it was created via
the Copy to all instances property check in the Type Definition aspect. When

3BSE036342-510 C 355
Asset Optimization Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

importing an 800xA 3.1 SP3 configuration, the configuration inheritance

changes shown in Table 11 will be made:

Table 11. Configuration Inheritance Changes

Type Change
Asset Monitor is on the Object Type. This Asset Monitor will be set to inherit from the
Asset Monitor category.
For each of the 4 configuration tabs (Asset
Monitor, Conditions, Asset Parameters, and
Input Records) the configuration inheritance
values will be set to their pre 800xA 5.0 SP2
values.
Asset Monitor is on the instance of the generic This Asset Monitor will be set to inherit from the
object. Asset Monitor category.
Asset Monitor in the instance that has Object For each of the 4 configuration tabs (Asset
Type. Monitor, Conditions, Asset Parameters, and
Corresponding Asset Monitor does not exist in Input Records) the configuration inheritance
the Object Type. values will be set to their pre 800xA 5.0 SP2
values.
Asset Monitor in the instance that has Object
Type.
Corresponding Asset Monitor exists in the object
type and the Copy to all instances check box is
disabled in the Aspect Control tab of the Object
Type Definition aspect.
Asset Monitor in the instance that has Object This Asset Monitor will be set to inherit from the
Type. Asset Monitor of the Object Type.
Corresponding Asset Monitor exists in the object For each of the 4 configuration tabs (Asset
type and the Copy to all instances check box is Monitor, Conditions, Asset Parameters, and
selected in the Aspect Control tab of the Object Input Records) if the configuration matches the
Type Definition aspect. configuration in Object Type, inheritance values
will be set to TRUE, else to FALSE.

9. 800xA 3.1 SP3 supported assigning Asset Monitors on the same object to the
different Asset Monitoring Servers. 800xA 5.0 SP2 requires that all Asset
Monitors on the object be assigned to the same AO Server. When upgrading

356 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 PC, Network and Software Monitoring

from 800xA 3.1 SP3 to 800xA 5.0 SP2, the AO Server for all Asset Monitors
will be set to Default. All Asset Monitors that were assigned to None in 800xA
3.1 SP3 will be marked as disabled in 800xA 5.0 SP2. If the user needs to load
balance Asset Monitors between two different AO Servers, this should be done
via the Assign Asset Monitors to this AO Srv context menu item in the AO
Server aspect. Refer to Industrial IT, 800xA - Asset Optimization,
Configuration (3BUA000118*) for more information.

PC, Network and Software Monitoring

Warnings may appear during system upgrade. These warnings can be ignored.

1. If user defined Script, Resource, and Assembly files were backed up, copy the
saved files from the safe media to the following directories:
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Scripts\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Assemblies\User
...\Program Files\ABB Industrial IT\Optimize IT\
PC, Network and Software Monitoring\bin\Configuration\
Resources\User
2. Perform the following steps on the PC, Network and Software Monitoring
Server node.
The following steps assume that the required system extensions were loaded on
the primary Aspect Server node.
a. Use the Structure Selector to open the Service Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to the:
Services > OpcDA_Connector, Service > SG_IT Server
object. If there is no object to navigate to, skip to Step l (letter l, not
number 1).

3BSE036342-510 C 357
PC, Network and Software Monitoring Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

c. Open the OPCDA_Provider_<servername> object and double-click on the

Service Provider Definition aspect.
d. On the Configuration tab, clear and select the Enabled check box and
click Apply. The Current field should change to Service.
e. Use the Structure Selector to open the Control Structure.
f. Use the Object Browser to navigate to the IT Server object.
g. Double-click OPC Data Source Definition in the Aspect List Area.
h. Click on the Service Group drop-down menu and select the SG_IT
Server.
i. Click on the OPCDA_Provider_<servername> which was configured in
step Step c.
j. Click Apply.
k. Skip to Step 3.
l. Use the Structure Selector to open the Control Structure.
m. Use the Object Browser to navigate to the IT Server object.
n. Double-click OPC Data Source Definition in the Aspect List Area.
o. Select New.
p. Click Add and select the appropriate Service Provider from the list.
q. Click OK twice.
r. Click Apply.
3. The IT General Setup aspect is used to point the IT OPC Server Network
Object to the Asset Optimization Server for Asset Optimization, and the Asset
Monitor Data Source. If Asset Optimization software is installed and loaded,
then the following configuration is required:
a. Use the Structure Selector to open the Control Structure.
b. Use the Object Browser to navigate to:
IT Server, IT OPC Server Network
c. Select IT General Setup in the Aspect List Area.

358 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 SMS and e-mail Messaging

d. Refer to the IT General Setup Aspect topic in Industrial IT, Asset

Optimization - PC, Network and Software Monitoring - Configuration
(3BUA000447*) and configure the Asset Optimization Server and Asset
Optimization Data Source.
e. Click Apply.
4. Migrate the IT Asset Monitors. If Asset Optimization and PC, Network and
Software Monitoring were installed on the 800xA 3.1 SP3 System, then the
following must be done for any existing IT Assets that had IT Asset Monitors
configured for them.
a. Use the Find Tool in the Plant Explorer Workplace to locate all the IT
Asset Monitor aspect instances in the Control Structure.
b. Right-click on each of the found aspects and select Goto Object.
c. Delete the IT Asset Monitor aspect.
d. Open the IT Device Manager aspect and click Generate to recreate the IT
Asset Monitor.
e. Repeat Step c and Step d for each object in the Find list.
f. Use the Object Browser to navigate to:
Root, Domain > Asset Optimization, Asset Optimization >
AO Server 1, AO Server
g. Select Asset Optimization Server in the Aspect List Area.
h. Enable the Enabled check box in the AO Server tab and click Apply.
i. Click Load all AMs in the Asset Monitors tab.

SMS and e-mail Messaging

Reconfigure the GSM Device hardware information recorded in the save operation
(refer to SMS and e-mail Messaging on page 296).
It may be necessary to stop and start the Messenger Server Service in the Service
Structure after the SMS and e-mail Messaging restore operation.

3BSE036342-510 C 359
Batch Management Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

During the upgrade, a second Messenger Service Group and Messenger Service
Provider will be created in the Service Structure. For instance:
Messenger SG_1, Service Group
Messenger SP_1, Service Provider
If there is already a Messenger Service Group and Messenger Service Provider
configured, the new one may be deleted.

Batch Management
Verify that the primary Batch Server is in primary mode (P is displayed in the
Windows Taskbar) and the secondary Batch Server is in secondary mode (S
displayed in the Windows Taskbar). If the proper modes are not displayed, enable
the Batch Service Group before proceeding.
To enable the Batch Service Group:
1. Open a Plant Explorer Workplace.
2. Select the Service Structure.
3. Select the Services\Batch Service, Service\batch_group_name, Service
Group\Service Group Definition aspect.
4. Select the Configuration tab.
5. Select the provider that is currently the secondary Batch Server.
6. Select the Enabled check box and click Apply.
7. Select the provider that is currently the primary Batch Server.
8. Select the Enabled check box and click Apply.
Batch data can be reloaded to the batch database from wherever it was archived.
The Batch history archive and restore aspect has been removed in SV5.1.

Perform the following to view any Batch data archived from SV5.0 or previous
versions of the Batch product:
1. Create a Virtual Machine (VM) node with the existing system version and its
components.
2. Restore Batch data using the Batch Restore window onto this virtual machine.

360 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Batch Management

Once the restored data is in the batch database, it can be viewed using the Batch
History Overview window.
Do not restore directly from CDs or DVDs. Restore from hard disk drives which can
be restored from CDs or DVDs using commercially available software.

Restoring Batches
To restore batch history, select the batch history restore aspect. By default a Batch
History Restore aspect is located in Library Structure\Batch
Management\Overviews. However, this aspect can be added to any 800xA System
object. The Batch History Restore window is displayed.
To restore batches:
1. Click Pick Files.
2. Select the batch files to be restored in the standard Windows Open window.
3. Click OK.
4. Repeat Step 1 through Step 3 until all the desired batch files are selected.
5. Click Restore.
Use the Remove from List and Clear All buttons to delete the selected batch or all
the batches from the list.
Click View Log to view a record of the actions taken during the last restore
operation.
Use the Batch Management backup restore utility to restore PFC color configuration
information and batch IDs. Access this utility by selecting:
Start > All Programs > ABB Industrial IT 800xA >
Production Mgmt - Batch > Restore Utility
Selecting any of the check boxes listed in the Restore Utility enables Restore.
The labeled check boxes are:
• PFC color configuration.
• Batch IDs.

3BSE036342-510 C 361
Basic History Service Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

When Restore is clicked, a warning is presented that states that the restore operation
will overwrite the selected parts of the configuration database. The parts of the
database that are overwritten are dependent on the option selections. A standard
Windows open file window that allows browsing to any desired folder is presented.
A configuration window provides the chance to cancel before the file is restored.

Selecting the Alarm Server

To select the Alarm Server:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to select:
Services > Event Collector, Service >
Batch_AE_Service, Service Group
4. Select Service Group Definition in the Aspect List Area.
5. Select the Special Configuration tab in the Preview Area.
6. Select Produce IT Batch OPC AE Server in the Alarm Server field.
7. Click Apply.
Always perform the Toolbar configuration as described in System 800xA Batch
Management Configuration and shutdown script procedure as described in the
Batch Management section of System 800xA Post Installation (3BUA000156*).

Basic History Service

Restore the Basic History Service data as follows. Perform this procedure on every
node where the Basic History Service is running.
1. Stop the Basic History Server from the Service Structure.
2. Read {Provider ID} from the properties of the Basic History Server. This
information may be needed when matching servers.
3. If it is necessary to keep historical data for the time since the system was
started after the upgrade, move the Basic History log files in the following
directory to a temporary directory:

362 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Information Management

...\OperateITData\History\{provider ID}
These files will be inserted by using the Archive Tool as described in Step 7.
4. Delete all files under:
...\OperateITData\History\{provider ID}
5. Restore the files from the backup of Basic History Service Data to:
...\OperateITData\History\{provider ID}
6. Start the Basic History Service from the Service Structure.
7. If Step 3 was performed:
a. Open the AdvHtArchiveTool located by default in the following directory:
...\Program Files\ABB Industrial IT\Operate IT\Process
Portal A \bin
b. Use the File/Select/Open Archive command and browse to the directory
containing the history log files.

Information Management
Perform the following post upgrade procedures for Information Management.
When creating the Oracle instance, select I am upgrading from SV3.x or SV4.x
in the Configuration File Options dialog box to prevent the wizard from creating
a history database. This will prevent History from starting until after the History
Database is restored.

Reconfiguring the IM Log Configuration

After restoring a system containing IM logs, the Service Group for the IM log
template configuration might be missing. The IM log templates must be checked,
and if the Service Group is missing, a new Service Group must be selected and
saved.
When the correct procedures are followed, no Log Templates should need to be
modified, this is only a verification step.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Library Structure.

3BSE036342-510 C 363
Information Management Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

3. Use the Object Browser to navigate to:

History Log Templates, History Log Template Library >
Default Log Templates, History Log Template Library
4. Select a log template.
5. Select Log Template in the Aspect List Area.
6. Select the Log Definition tab in the Preview Area.
7. If the Service Group in the Service Group drop-down list box is missing, it
must be reconfigured. The Service Group drop-down list box contains all
History servers defined in the system. Use this list to specify the server where
this log will reside.
8. Repeat this procedure for all of the log templates.

Information Management History Backup/Restore Utility

Use the Information Management History Backup/Restore utility, via:
Start > ABB Industrial IT 800xA > Information Mgmt > History >
Backup and Restore
to restore the Information Management History database and synchronize the
Aspect Directory contents with the current Information Management History
database configuration.
During the restore, the existing database is dropped, and a new one is created.
Mount points and additional table spaces are created based on the database being
restored. Oracle data is imported, and the file-based property logs are copied back
into the system. Unless a different mount point is specified, the History database
will be restored to its original location (its location prior to being backed up).
The History database can be restored from any drive on the workstation, including
any mapped network drives. The restore utility will first search a specified location
for zipped archives matching a specific name and fitting the form name-drive.zip
(such as histDB-C.zip, histDB-A.zip, and histDB-D.zip), and will then
restore the compressed database files contained within the archives to their
respective original locations (their locations prior to being backed up).

364 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Information Management

Considerations. When restoring the History database, make sure the disk is ready
and available on the node on which the procedure is to occur. Also, ensure that no
applications are accessing the Oracle database. The log file should be checked after
the restore operation to make sure that the restore operation completed successfully.

Running the Information Management History Backup/Restore Utility

To restore a backed up History database:
The path to PAS now changed to Control Panel > Administrative Tools.

This procedure can also be performed by using the pasgui command in the Run
dialog box (Start > Run).
1. Verify that the ABB Process Administration Service (PAS) is set to manual in
the Services Control Panel (run Services.msc from the Run dialog box). Stop
the service if it is running.
If it is suspected that the Inform IT History Service Provider has not stopped, it
can be stopped now by selecting the Inform IT History Service Provider for this
node in the Service Structure, selecting the Configuration tab on the Service
Provider Definition aspect, disabling Enabled, and clicking Apply.
2. Ensure that no third party applications access the Oracle database during the
restore operation.
3. Select:
Start > All Programs > ABB Industrial IT 800xA > Information
Mgmt > History > Backup and Restore.
4. Verify Restore configuration from a backup file(s) is enabled in the
Welcome to IM Historian Backup and Restore Utility dialog box.

3BSE036342-510 C 365
Information Management Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

5. Click Next. IM Historian Database Restore dialog box appears as shown in

Figure 46.

TC08390A

Figure 46. IM Historian Database Restore Dialog Box

6. Specify the location of the backup files in the Path of IM historian backup:
field (Figure 46).
If new mount points need to be specified for file-based logs and/or a new Oracle
tablespace definition file, click Browse.
7. Click Next. The HsBAR Output Window appears.
8. Select the Automatically close upon completion check box.
9. Monitor the progress in the Progress Status area of the IM Historian
Backup/Restore Utility window. Ignore the error messages indicating errors
deleting aspect.
Shortly after the message indicating the import is complete, the database
conversion tool will run automatically. Feedback will be provided in the
HsBAR window.

366 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Information Management

Shortly after the message indicating the database conversion is complete, the
history synchronization tool will run automatically. Again, feedback will be
provided in the HsBAR window.
The restore of the system requires an instance that matches the size of the
database being restored. When creating the instance, be sure to select Small,
Medium, or Large based on the size of the message log in the backup being
restored. Select Large if the size is not known. If the wrong size is selected, the
restore operation may fail with the Oracle Error Message 1652 - Unable to
extend tmp segment in tablespace temp. Repeat the restore with the
correct instance settings if the error occurs.
10. Click Finish when a message stating the execution is complete is displayed as
shown in Figure 47.

TC08391A

Figure 47. Execution is Complete Message

If the Progress Status dialog box has warning messages with possible solutions as
indicated in Figure 48, read the possible solutions carefully, then click Finish and

3BSE036342-510 C 367
Information Management Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

proceed with the solution that best fits your problem. Refer to the Information
Management Release Notes for further guidelines.

TC08392A

Figure 48. Progress Status Dialog Box

Restoring Other Information Management Related Files

There are several other files related to Information Management that need to be
restored as part of total system restore.
Refer to Saving Other Information Management Related Files on page 303 for
Desktop Trends, Display Services, and DataDirect file locations.
• History Archive Data: For each archive device, copy the appropriate folders
from the safe media to the location specified by the Device Filename.
• History Archive State Information: Stop the Industrial IT Archive service in
the Service Structure. Copy the folder that holds the last archive time and
other archive state information from the safe media to:
...\Documents and Settings\All Users\Application
Data\ABB\IM\Archive

368 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Information Management

• Reports: Restore any report template files created in Microsoft Excel,

DataDirect, and/or Crystal Reports. Also restore report output files created as a
result of running these reports via the Scheduling Services.
• Desktop Trends: Restore trend display, ticker display, and tag explorer files.
• Display Services: Restore the directories for custom users, as well as display
and user element definitions.
• DataDirect: Restore custom text files for object, object type, and attribute
menus used on the DataDirect windows.
• Check Archive Path Specifications: If the disk configuration has changed
from the previous system to the new system (i.e. letter designations for disks
have changed: C, D, E, etc.), check the archive device configurations to make
sure the Archive Path specification points to the correct disk drive and
directory, as shown in Figure 49.

TC08388A

Figure 49. Checking the Archive Path Specification

3BSE036342-510 C 369
Information Management Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

Complete the Information Management Post Install

1. Start all processes under PAS supervision. This will start the Inform IT History
Service Provider.
If it is suspected that the Inform IT History Service Provider has not started, it can
be started now by selecting the Inform IT History Service Provider for this node
in the Service Structure, selecting the Configuration tab on the Service
Provider Definition aspect, selecting Enabled, and clicking Apply.
2. Restart the Basic History Service Provider for this node:
a. Select the Basic History Service Provider object for the Information
Management node in the Service Structure in the Plant Explorer.
b. Select the Service Provider Definition aspect.
c. Select the Configuration tab.
d. Clear the Enabled option.
e. Click Apply.
f. Select the Enabled option.
g. Click Apply.
h. Open the Services Control Panel (run Services.msc from the Run dialog
box), set the ABB Process Administration Service (PAS) to Automatic
and start it.
i. Open the Information Management Configuration Assistant (Start >
Programs > ABB Industrial IT > Information Mgmt > Configuration
Assistant) and perform any incomplete steps.

Verify that all Information Management services are running.

Restoring Archive Group Associations

Profile, Message, and Report logs must be reassociated with their respective
Archive Groups. This information was recorded before beginning the upgrade.
Refer to Industrial IT, 800xA - Information Management, Configuration

370 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Calculations Service

(3BUF001092*) to access the Archive Groups and restore the Archive Group
associations.

Calculations Service
The Const keyword is no longer allowed within the VBScript source code of the
calculation; therefore, edit Calculations that use the Const Statement.
Calculations that were disabled prior to the upgrade must be enabled by selecting
the Enabled check box in the Calculations dialog box. Refer to the section on
Calculations in Industrial IT, 800xA - Information Management, Operation
(3BUF001094*).
To enable the Calculations Service:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Calculations Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Select the Enabled check box and click Apply.

Scheduling Service (Application Scheduler)

Schedules that were disabled prior to the upgrade must be enabled by selecting the
Enabled check box in the Scheduling dialog box. Refer to the section on
Scheduling in Industrial IT, 800xA - Information Management, Operation
(3BUF001094*).
To enable the Scheduling Service:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Scheduling Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.

3BSE036342-510 C 371
Resigning Digital Signatures in 800xA 5.0 SP2 Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0

6. Select the Enabled check box and click Apply.

Resigning Digital Signatures in 800xA 5.0 SP2

To resign digital signatures in 800xA 5.0 SP2:
1. Use Windows Explorer to locate AfwSignatureManager.exe in the
following directory:
...\<Base System install directory>/bin
2. Double-click AfwSignatureManager.exe to launch the Signature Manager.
3. Use the File menu to open the Signature Report file saved before the upgrade.
4. When a signer is selected in the Signer column, the Aspects Signed table will
show all aspects signed by this signer and information indicating whether the
signature was valid in the 800xA 3.1 SP3 System or not.
5. Select the aspects to re-sign and click Sign.
6. A Signature dialog box will appear in which to validate the signature.
Use Ctrl+Shift+Click to select multiple aspects to sign in one operation.

Restart the System

Restart the system after performing all post upgrade procedures.

Reconfigure Alarm and Event List Configurations

In 800xA 5.0 SP2, in most cases, the SourceName column contains GUIDs. The
recommendation in 800xA 5.0 SP2 is to reconfigure the Alarm and Event List
configurations to use the ObjectName column instead of the SourceName column.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Library Structure.
3. Use the Object browser to navigate to and select an Alarm and Event List
Configuration aspect.

372 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Information Management Maintenance

4. Select Alarm and Event List Configuration in the Aspect List.

5. Select the Columns tab in the Preview Area.
6. Clear the SourceName check box and select the ObjectName check box.
7. Click Apply.
Alarm and Event handling has changed significantly from 800xA 3.1 SP3 to 800xA
5.0 SP2 (refer to Alarm and Event List Configurations on page 305). Check the list
configurations in the 800xA 5.0 SP2 system against those recorded for the 800xA
3.1 SP3 system under Alarm and Event List Configurations on page 305.

Information Management Maintenance

Perform this procedure on all Information Management Server nodes.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Node Administration Structure.
3. Use the Object Browser to navigate to:
All Nodes, Node Group > IM Node > Inform IT History_IM
Node, Service Provider > Inform IT History Object,
Inform IT History Object
4. Select Inform IT History Control in the Aspect List Area.

3BSE036342-510 C 373
Configure Windows Services and Windows Firewall Section 6 Upgrading 800xA 3.1 SP3 to 800xA

5. Expand the Maintenance tree in the Preview Area and select

Synchronization. The Inform IT History Manager shown in Figure 50
appears in the Preview Area.

Figure 50. Inform IT HIstory Manager

6. Click Check Names.

7. A blank dialog box should appear. If it does, click OK. If it does not click
Resynchronize Names.
8. Click Check Synchronization.
9. A blank dialog box should appear. If it does, click OK. If it does not click
Force Synchronization.

Configure Windows Services and Windows Firewall

Perform all applicable post installation steps in System 800xA Post Installation
(3BUA000156*), including configuring Windows Services and Windows Firewall.

374 3BSE036342-510 C
Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 Add Autostart Shortcut

Add Autostart Shortcut

It it is desired to enable the autostart of the Operator Workplace on client nodes,
perform the following:
1. Define a default workplace.
2. The shortcut must be created from the ABB Workplace login window.
3. The shortcut is located in:
...:\Documents and Settings\UserName\Start
Menu\Programs\Startup
4. Right-click the shortcut and select Properties from the context menu.
5. Add the following to the shortcut target:
/WS
-or-
/WaitForSystem
6. Click OK.

System Backup
Make a complete backup of the upgraded system as described in Backups on page
285.

3BSE036342-510 C 375
System Backup Section 6 Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2

376 3BSE036342-510 C
 Appendix A Warning and Error Messages

The warning and error messages that can be generated by the 800xA backup/restore
function are described in the following topics. Suggested solutions are also
provided.

Failed to Serialize Aspect

Example
Tue Jul 01 08:41:03 2003 [Error]: Failed to serialize aspect 'Operator Messages
Link Display' on object 'Web System Workplace'
Reason
It is not possible for the Backup function to save the aspect data.
Solution
Check in the system for the behavior of this aspect.

ASO Object Class xxxx

did not Implement IAfwAspectSystemObject. Failed to Create ASO. Forgot to
Register dll?
Example
Tue Jun 10 19:02:17 2003 [Error]: ASO object class {7B7A13B3-8BB4-42A3-
8289-987C579797C2}did not implement IAfwAspectSystemObject Failed to create
ASO. Forgot to register dll?

3BSE036342-510 C 377
UnplacedObjects.afw Appendix A Warning and Error Messages

Reason
This often occurs when a system extension is used, but not installed on the node
from where the backup is taken. It can also happen if an update of a system
extension has been installed, but not added to the system.
Solution
Install all system extensions on the node from where the backup is taken. Make sure
that the correct version of the system extension is installed.

UnplacedObjects.afw
Example
[Warning] c:\PPABackup\MyBackup\UnplacedObjects.afw created
Reason
During backup process, the backup tool goes through all structures, if there is an
object that doesn't exist in any structure, it will be placed in UnplacedObjects.afw
and write a warning in the backup log, therefore, UnplacedObjects.afw is used for
all objects which miss the structure.
Solution
Check if there is any important object in UnplacedObjects.afw. If there is an
important object in UnplacedObjects.afw, your backup is considered to be not
complete. In such case, investigate what kind of object it is, and try to repair the
system. One solution could be to add the object into the structure it should belong
to. Take another backup.

The System Cannot Find the Path Specified

Example
Error detected for aspect 'Empty A3P' of object 'Document Manager
Templates/Document Manager File Templates/Drawings'
Tue Jun 08 00:43:30 2004 The system cannot find the path specified.

378 3BSE036342-510 C
Appendix A Warning and Error MessagesSystem Extension ´xxxx´ with ID ´Guid` is not Installed on

EbServiceHandler: Object Id = {9AFACBA5-6B6A-462A-9EDF-78765740CD52},

Aspect Id = {89F8A8C4-10F7-4874-B77D-A8E6445D5C93}
EbServiceHandler: Failed to load document into stream!
Reason
When the backup was taken, the FSD cache was set too low. All data has NOT been
backed up. There should be warnings in the System Event list about overflow in the
Fsd cache.
Solution
Increase the Fsd Cache size (for all nodes).

System Extension ´xxxx´ with ID ´Guid` is not Installed on

this Node
Example
System extension 'Engineering Base' with id {B775BEA4-7859-4649-AE16-
901790822886} is not installed on this node.
System extension 'AC800M Con 31SP1' with id {6F388AEC-E4FF-4614-AF80-
1D37EC3B141F} is not installed on this node.
Reason
There is a system extension, which is not available in the node where the backup is
taken, or which is not properly removed. The latter can be the case if AC800
Connect has been upgraded and the old version is still registered in Industrial IT
800xA.
Solution
Use a backup node where all system extensions are installed.

Timeout by External Service

Example
Thu Mar 04 02:34:55 2004 #1: Receiving files

3BSE036342-510 C 379
Graphic Aspect = xxx Cannot be Imported. Appendix A Warning and Error Messages

Thu Mar 04 02:34:56 2004 #1: Receiving files

Thu Mar 04 02:34:57 2004 #1: Receiving files
Thu Mar 04 02:34:57 2004 #1: Finishing
Thu Mar 04 02:34:58 2004
Thu Mar 04 02:35:08 2004 TimeOut by External Service
Reason
History or System Message data was backed up using the backup/restore function.
This functionality is not yet supported.
Solution
History and System Message data has to be saved manually, as described in
reference [2] Release Notes. Create a new backup, without including History or
System Message data.

Graphic Aspect = xxx Cannot be Imported.

Example
Mon Mar 29 19:52:32 2004 [Error]: Object = WI Mezzanine Deck, graphic aspect =
Page Prev cannot be imported. Source directory =
d:\OperateITData\Temp\ActiveGraphics\{800BA917-3D7F-44B6-B647-
90C4B06A98FA}.restore.2.
Reason
Could be different reasons.
Solution
Check the source directory specified in the error message. The log file in this
directory should give some hints of what caused the problem.

Too Many Aspects of Category

Example
Sat Jun 05 17:04:33 2004: Too many aspects of category 'Name' on object
'{82416BDF-5464-4422-A443-35E08E1065BE}'

380 3BSE036342-510 C
Appendix A Warning and Error Messages Aspect Category is Missing

Sat Jun 05 17:04:34 2004: Import/Export Error: Object {82416BDF-5464-4422-

A443-35E08E1065BE} ({82416BDF-5464-4422-A443-35E08E1065BE}) -
E_AFW_AD_TOO_MANY_ASPECTS (0x8abb081b) To many aspect of a specific
type.
Sat Jun 05 17:04:34 2004: Failed to restore file C:\BWSC\BWSC Full Backup;
2004-06-03; 03-00\Control Structure28.afw. The importer returned hr =
0x8abb081b
Reason
The system was inconsistent at backup time (there were more than one aspect of
category 'Name' on an object). The backup does not react on this, but restore will
fail. The restore part will be fixed in a later release (it will be possible to import such
an object, but a warning will be granted).
Solution
Open the file (in this case Control Structure28.afw) with the old import/export
utility (<Install path>\bin\AfwImportExport_obsolete.exe), search for the aspect
category and manually remove one of the two aspect categories.

Aspect Category is Missing

Example
Sat Jun 05 16:41:27 2004: Aspect '{506D9D24-E22A-4EDB-AFB0-
0753B6DB6990}' on object 'SoftPoint Object Types' cannot be restored because the
aspect category is missing
Sat Jun 05 16:41:27 2004: ObjectId: {9574CC3B-0E5E-4B14-A83E-
F483CCDE6E44}
Sat Jun 05 16:41:27 2004: AspectId: {506D9D24-E22A-4EDB-AFB0-
0753B6DB6990}
Reason
One or more aspect categories have been removed, while there are aspects of that
category still in the system. This inconsistency was present in the system when the
backup was taken.

3BSE036342-510 C 381
Unknown Transaction Error Appendix A Warning and Error Messages

Solution
If the aspect category has been removed then these aspects may not be of interest
any more. Check if the aspects are needed. If not, ignore this message.

Unknown Transaction Error

Example 1
Mon Apr 19 13:39:40 2004: Unknown transaction error
Reason
If this is the only error message, there is probably a problem with some windows
resources.
Solution
Check your windows resources.
Example 2
Mon Jun 28 08:37:08 2004: Loading C:\BACKUP\Full Backup; 2004-06-23; 10-
39\Aspect System Structure0.afw ...
Mon Jun 28 08:37:09 2004: Aspect 'Batch Management Operation' on object 'Batch
Management Documents' failed to unserialize itself.
Mon Jun 28 08:37:09 2004: ObjectId: {814786F8-E6CC-44B0-9A2A-
1787FADDFE6F}
Mon Jun 28 08:37:09 2004: AspectId: {2CE41978-DE94-44AC-9D38-
B216FBA93C3A}
Reason
It is not possible for the Restore function to restore the aspect data.
Solution
No solution available.

382 3BSE036342-510 C
 Appendix B Control Builder M Compatibility
Issues

Introduction
This appendix lists the compatibility issues when upgrading from the various
system versions to 800xA 5.1.

800xA 5.0 SP2 to 800xA 5.1 Compatibility Issues

Table 12 lists and describes Control Builder M compatibility issues, including
solutions to the issues, when upgrading from 800xA 5.0 SP2 to 800xA 5.1.

Table 12. 800xA 5.0 SP2 to 800xA 5.1 Control Builder M Compatibility Issues

Application Issue Solution

Upgrading from The signal configuration After upgrading the Hardware libraries for
800xA 5.0 SP2 to for CI860 must be CI860 the UnitStatus signals must be moved
800xA 5.1 and later. checked and changed from IW10.6510 to IW10.6518. Otherwise the
when UnitStatus is application will not display the correct values or
accessed by the in addition a succeeding download will be
application. stopped with an error or OLU (Online Upgrade)
will fail in Step 7 (Refer Appendix H, Online
Upgrade Controller Level). The change must be
done before first download, after normal
firmware upgrade or before starting OLU.

3BSE036342-510 C 383
800xA 5.0 SP2 to 800xA 5.1 Compatibility Issues Appendix B Control Builder M Compatibility

Table 12. 800xA 5.0 SP2 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Mixing formal and Prior to 800xA 5.1 it was Correct the code to use either formal or informal
informal parameter allowed to mix formal and parameter passing for all parameters in the
passing in a function informal parameter function call.
call is not allowed. passing in a function call.
The Control Builder
compiler in 800xA 5.1
gives a compile error for
mixed parameter passing.
Allowed:
AddSuffix( String :=
StrVar, Suffix := StrSuffix
);
or
AddSuffix( StrVar,
StrSuffix );
Not allowed:
AddSuffix( String :=
StrVar, StrSuffix );
Writing to If a function block has a Correct the code to not use this illegal
components of a parameter p1 with construction.
structured function direction [in] of a
block parameter with structured data type, it
direction [in] via was possible to write to its
control module components by
parameter is connecting it to a control
prohibited. module that writes to the
parameter. This is
prohibited in 800xA 5.1

384 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 4.1 to 800xA 5.1 Compatibility Issues

Table 12. 800xA 5.0 SP2 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

New attributes for Some new attributes have For detailed information on the new attributes
function block, control been introduced in 800xA and their consequences refer to System 800xA
module, and data 5.1 that affect function Control AC 800M Configuration.
types have been block, control module, and
introduced. data types.
For example:
- Direction attribute on
control module
parameters.
- Reverse and ISP
attribute on datatype
components.
Upgrade of 800xA 5.0 The hardware libraries for When Upgrade Project is performed in Control
SP2 projects CI851 and CI852 do not Builder the user must select to not upgrade to
containing CI851 and work together with 800xA 800xA 5.1 firmware in the controllers.This is not
CI852 units. 5.1 controller firmware. compatible with the hardware libraries for CI851
and CI852.
After Upgrade Project is performed, verify that
the controller is using BasicHWLib 5.0-2 and
the hardware libraries for CI851 and CI852 as
applicable.

800xA 4.1 to 800xA 5.1 Compatibility Issues

Table 13 lists and describes Control Builder M compatibility issues, including
solutions to the issues, when upgrading from 800xA 4.1 to 800xA 5.1.

3BSE036342-510 C 385
800xA 4.1 to 800xA 5.1 Compatibility Issues Appendix B Control Builder M Compatibility Issues

Table 13. 800xA 4.1 to 800xA 5.1 Control Builder M Compatibility Issues

Application Issue Solution

Upgrading from The signal configuration After upgrading the Hardware libraries for
800xA 4.1 to 800xA for CI860 must be CI860 the UnitStatus signals must be moved
5.1 and later. checked and changed from IW10.6510 to IW10.6518. Otherwise the
when UnitStatus is application will not display the correct values or
accessed by the in addition a succeeding download will be
application. stopped with an error or OLU (Online Upgrade)
will fail in Step 7 (Refer Appendix H, Online
Upgrade Controller Level). The change must be
done before first download, after normal
firmware upgrade or before starting OLU.
Mixing formal and Prior to 800xA 5.1 it was Correct the code to use either formal or informal
informal parameter allowed to mix formal and parameter passing for all parameters in the
passing in a function informal parameter function call.
call is not allowed. passing in a function call.
The Control Builder
compiler in 800xA 5.1
gives a compile error for
mixed parameter passing.
Allowed:
AddSuffix( String :=
StrVar, Suffix := StrSuffix
);
or
AddSuffix( StrVar,
StrSuffix );
Not allowed:
AddSuffix( String :=
StrVar, StrSuffix );

386 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 4.1 to 800xA 5.1 Compatibility Issues

Table 13. 800xA 4.1 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Writing to If a function block has a Correct the code to not use this illegal
components of a parameter p1 with construction.
structured function direction [in] of a
block parameter with structured data type, it
direction [in] via was possible to write to its
control module components by
parameter is connecting it to a control
prohibited. module that writes to the
parameter. This is
prohibited in 800xA 5.1
New attributes for Some new attributes have For detailed information on the new attributes
function block, control been introduced in 800xA and their consequences refer to System 800xA
module, and data 5.1 that affect function Control AC 800M Configuration.
types have been block, control module, and
introduced. data types.
For example:
- Direction attribute on
control module
parameters.
- Reverse and ISP
attribute on datatype
components.

3BSE036342-510 C 387
800xA 4.1 to 800xA 5.1 Compatibility Issues Appendix B Control Builder M Compatibility Issues

Table 13. 800xA 4.1 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Upgrade of 800xA 4.1 The hardware libraries for To upgrade a Control Builder Project from
projects containing CI851 and CI852 are not 800xA 4.1 that has controllers containing CI851
CI851 and CI852 part of AC 800M Connect or CI852 units, the following system extensions
units. in 800xA 5.1 and does not must be installed and loaded after the restore to
work together with 800xA the 800xA 5.1 System is performed, but before
5.1 controller firmware. Upgrade Project is performed in Control
Builder:
- AC800M Classic system extension (contains
the hardware libraries for CI851 and CI852).
-AC800 SV5.0 SP2 Coexistencesystem
extension (contains BasicHWLib 5.0-2).
After Upgrade Project is performed, verify that
the controller is using BasicHWLib 5.0-2 and
the hardware libraries for CI851 and CI852 as
applicable.
Force I/O from SIL2 In order to better enforce The only possibility to force I/O in a SIL
applications the counting of maximum application will be via the Safe Online Write
prohibited number of forces in High function (confirmed write) from operator
Integrity Controllers, the graphics.This restriction will also improve the
possibility to force I/O response time when resetting forces in the
signals directly from code controller.The reset of individual forced signals
has been removed. This from code will still be possible by using the new
means that no writing will firmware function ResetForcedValue(), which is
be allowed to the .Forced introduced in 800xA 5.0 SP2. This implies that
component of an IO data constructions where variables of IO data type
type in a SIL1-2 or SIL3 (i.e. BoolIO, RealIO, DWordIO, or DintIO) are
application. It will result in copied or connected via out parameters in
a compile error. function blocks, will no longer work. However,
parameter passing via in or in_out parameters
is not affected.

388 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 4.1 to 800xA 5.1 Compatibility Issues

Table 13. 800xA 4.1 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Discontinued Due to the restriction In SIL applications it is recommended to
functions for Safe described in Force I/O replace the MMSRead4xxxxIO with the
MMS communication from SIL2 applications MMSRead4xxxx function blocks and only
(function blocks) prohibited, the SIL2 transfer the .Value component of the IO data
marking of function blocks type.
writing to IO data types
has been removed. The
affected function blocks
are:
• MMSRead4BoolIO.
• MMSRead4DintIO.
• MMSRead4RealIO.
Consequently, these
function blocks can not be
used in SIL applications
but will still be available for
use in non-SIL
applications.
The corresponding
definition function blocks
(MMSdef4xxxxIO) will still
be available from SIL
applications and
consequently reading IO
from SIL to non-SIL
applications will still be
possible.
Safety Operator User An operator must be a Make the operator a member of the Safety
Group member of the Safety Operator User Group.
Operator User Group to
be able to write data to
objects running in a SIL
application in the
controller.

3BSE036342-510 C 389
800xA 4.1 to 800xA 5.1 Compatibility Issues Appendix B Control Builder M Compatibility Issues

Table 13. 800xA 4.1 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

No Time Sync Some controllers might Set the CS Protocol Type for controllers that are
warning in controller get a No time sync not intended to be synchronized No Synch in
warning in the controller order to avoid the warning.
log after upgrade to
800xA 5.0 SP2.
Accessing Local It has been possible to Correct any such warnings before performing
Variables in Function access local variables in the download. Local variables used in this
Blocks. Function Blocks from fashion need to be changed to parameters
surrounding code. instead.
According to the IEC
61131-3 standard, local
variables shall only be
accessible within the
containing software
element.
A compilation error is
given if local variables are
accessed from the
outside.
Code sorting loops Code sorting loops in First, try to correct the sorting loops. Refer to
treated as errors. applications are by default Interpret and Correct Code Loop Errors in
considered as errors in Industrial IT, 800xA - Control and I/O,
800xA 5.0 SP2. Application Programming, Introduction and
It is not possible to Design (3BSE043723*).
compile and download an Another alternative is to change the compiler
application if it contains switch for Code Sorting Loops:
code sorting loops. 1. Mark the project in Project Explorer.
2. Right-click and select Settings > Compiler
Switch.
3. Set the global Loops in Control Modules
switch to Warning.

390 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 4.1 to 800xA 5.1 Compatibility Issues

Table 13. 800xA 4.1 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Applications having Compile error 1040 might Correct the compile error.
integer literal values appear in Control Builder e.g. by entering a smaller, legal value on the
too large as initial projects that previously literal.
values. did not contain any
compile errors.
Control Builder now
makes more stringent
compiler checks on initial
values for variables. It
previously allowed illegal
(too large) integer literal
values as initial values.
The actual used value
was zero.

3BSE036342-510 C 391
800xA 4.1 to 800xA 5.1 Compatibility Issues Appendix B Control Builder M Compatibility Issues

Table 13. 800xA 4.1 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Self defined serial The Serial Use of firmware functions:
communication using Communication Library Firmware functions used for serial
the Serial has undergone a major communication handling are no longer
Communication internal redesign that in supported.
Library. some cases may lead to
This means that user-built libraries where these
compatibility issues.
firmware functions have been used, can no
longer be used.
The no longer supported firmware functions
are:
• OpenDevice
• UpdateDeviceSetup,
• SetDeviceClearRead
• CloseDevice.
• ReadStringDevice
• ReadLineDevice
• WriteStringDevice
Improvement were made in the following
areas:
• Clear buffer when entering the listen
operation of the SerialListen function
block.
• If the SerialWriteWait function block is
triggered when the timeout has elapsed,
the read/listen buffer is cleared in between
the retry operations in connection to the
write operation.
• Behavior of the SerialWriteWait
function block in previous versions: If
the function block is triggered after the
application stopping phase is entered, the
function block propagates the status code -
15 via the Status -parameter.

392 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 4.1 to 800xA 5.1 Compatibility Issues

Table 13. 800xA 4.1 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Self defined serial The Serial If the power fails, and a function block was in a
communication using Communication Library pending state, the Status -5331 is derived from
the Serial has undergone a major it after the controller is powered up again.
Communication internal redesign that in • Behavior of the SerialWriteWait
Library. some cases may lead to function block in previous versions: If
(continued) compatibility issues. the function block was triggered after the
(continued) application stopping phase was entered,
the function block should normally
propagate status code -15. But this was
masked, and instead, after the finished
application change, the function block
automatically retriggered the write
operation.
The Serial Printing a string longer than 140 characters:
Communication Library The behavior of the SerialWrite operation is no
has undergone a major longer synchronous. Therefore, the possibility
internal redesign that in to call one and the same function block time
some cases may lead to after time to print a longer string than 140
compatibility issues. characters is no longer supported.
(continued) Instead, do like the following:
To be able to print a string longer than the
maximum length of 140 characters, call
subsequent function blocks in order:
Write1( Req := TRUE,
Id := Id,
EndChar := EndChar_Write1,
Done => Done_Write1,
Error => Error_Write1,
Status => Status_Write1,
Sd := Sd_Write1 );
Write2( Req := TRUE,
Id := Id,
EndChar := EndChar_Write2,
Done => Done_Write2,
Error => Error_Write2,
3BSE036342-510 C Status => Status_Write2, 393
Sd := Sd_Write2 );
Printing the two strings Sd_Write1 + Sd_Write2
by calling the two function blocks will be queued
up, and it will be printed in a series.
800xA 4.1 to 800xA 5.1 Compatibility Issues Appendix B Control Builder M Compatibility Issues

Table 13. 800xA 4.1 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Compiler warnings If there is a risk that tasks Apply proper task offsets so that the tasks can
occur if there is a risk can collide in the no longer collide.
for task collisions. controller, a warning will
be displayed during
compilation. The
compilation warning will
look like:
Warning 9155:
Controller_1:HW
Task Normal and
Fast may have
colliding start
times
Applications using SattBus on TCP/IP will not Change the application to use function blocks
SattBus on TCP/IP. work after the upgrade. and data types from SattBusCommLib as
The COMLI follows:
communication function Function Blocks
blocks have been used Before After
also for SattBus on
COMLIConnect ComliSBConnect
TCP/IP, but this is no
longer the case. A new COMLIRead ComliSBRead
library including a set of COMLIReadCyc ComliSBReadCyc
new function blocks COMLIReadPhys ComliSBReadPhys
should be used instead.
COMLIWrite ComliSBWrite
COMLIWriteDT ComliSBWriteDT
Data Types
Before After
Comm_Channel_COMLI
Comm_Channel_ComliSB

394 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 4.1 to 800xA 5.1 Compatibility Issues

Table 13. 800xA 4.1 to 800xA 5.1 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Some project 1. If these project 1. Change to the correct literal value in the
constants have been constants have been used places where the project constants are used.
removed from in code there will be 2. Check if the value of the removed project
SupervisionBasicLib compile errors after constant was changed in the project in 800xA
(cSinit.*), BasicLib upgrading the project. 5.0 SP1a. This can be done by opening the
(cEnable.*), and 2. If the value of the Project Constants dialog box after the upgrade
SupervisionLib project constants was and seeing if the project constants are listed.
(cInit.*). Refer to changed in the project in In that case the parameters previously using
Removed Project 800xA 5.0 SP1a, it will the project constant as a default value must be
Constants on page lead to changed behavior manually connected to a literal with the
407 for a list of the of the code after the corresponding value.
removed project upgrade, because these
constants. project constants have
been used as default
values on parameters.

3BSE036342-510 C 395
800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility Issues Appendix B Control Builder M Compatibility

800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility Issues

Table 14 lists and describes Control Builder M compatibility issues, including
solutions to the issues, when upgrading from 800xA 3.1 SP3 to 800xA 5.0 SP2.

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues

Application Issue Solution

No Time Sync Some controllers might Set the CS Protocol Type for controllers that are
warning in controller get a No time sync not intended to be synchronized No Synch in
warning in the controller order to avoid the warning.
log after upgrade to
800xA 5.0 SP2.
Valid for users that The Visual BASIC ® resize Remove the source comments around the
have copied a code of the Display UserControl_Resize method before deploying
template object from, Element Reduced Icon the Display Element Reduced Icon.
for example, a becomes corrupt after Edit the Display Element Reduced Icon,
Process Object deploy in Graphics removing the comments, and then deploy the
Library, and are using Builder. Display Element Reduced Icon.
its Display Element
The source comments are:
Reduced Icon.
‘
$$ABB_BEGIN_USERCONTROL_RESIZ
E
---
‘ $$ABB_END_USERCONTROL_RESIZE
NOTE: Delete only the comment lines. Do not
delete the source code between the comment
lines.
Internal MMS The behavior of internal This kind of communication is now
Communication communication between asynchronous; all data may no longer always
between applications two applications in the be received in the same scan.
residing in the same same controller has
controller. changed.

396 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

User-Defined The behavior has been The behavior is redefined as follows:
Hardware Definition undefined when the 1131- • The hardware unit will be written with the
Files when 1131- variable has a very large largest, which is different depending on
application variables value (larger than the hardware, possible value if 1131-variable
of type dInt and maximum value possible has a very large positive value.
dWord are written to write on a specific
• The hardware unit will be written with the
from the application hardware unit). The very
largest, which is different depending on
to I/O-channels. large value has really
hardware, negative value if 1131-variable
been truncated, a
has a very large negative value.
hardware unit receiving 8-
bit data has received the 8
lowest bits in the dInt or
dWord.
FF HSE input I/O The mapping of FF-status Previously, the FF-status of in-channels has
channels. in input I/O channels been mapped into both the MSB and the LSB of
(BoolIO, RealIO, etc.) the status word. This has changed so that the
connected to CI860 LSB now is remapped into OPC-status (since
channels has been this byte now is sent to the OPC-server).
changed. Example:
The FF status 16#80 was previously mapped
as 16#80000080 into the status word in the I/O
data type. It is from now mapped as
16#800000C0. The result is that the OPC
Server sends 16#C0 to its OPC clients.

3BSE036342-510 C 397
800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility Issues Appendix B Control Builder M Compatibility

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Accessing Local It has been possible to Correct any such warnings before performing
Variables in Function access local variables in the download. Local variables used in this
Blocks. Function Blocks from fashion need to be changed to parameters
surrounding code. instead.
According to the IEC
61131-3 standard, local
variables shall only be
accessible within the
containing software
element.
A compilation error is
given if local variables are
accessed from the
outside.

398 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Standard libraries 800xA 5.0 SP2 includes SupervisionLib
included in AC 800M the new library versions 1. Parameters for the Inhibit function in the
Connect. as well as the old library detector modules are modified. Parameter
NOTE: These issues versions in order to names are changed; e.g. from
are only valid for handle the upgrade for GTHAndNotInhibited to GTHAct. Parameters
users that have used those who have used are modified to comply with connected
either them. The use of the old SignalLib library. The Inhibit logic is now placed
SupervisionLib or versions is, however, not inside the Function Blocks defined in SignalLib.
FireGasLib. Other supported. Users must
2. Parameters are added for the enable
users will not be reconnect to the new
function; e.g. EnableH, GTHStat, and
affected by these library versions and
HEnabled. Parameters are added to comply
issues. modify applications before
with the connected SignalLib library. The
they go into supported
Enable function was earlier limited to
operation.
alarm/event, but is now controlling the
activation signals (GTHStat and GTHAct) as
well.
3. In Detector1Real and DetectorRemote, LevelH is
used instead of LevelHHH. In Detector2Real,
LevelH and LevelHH are used instead of LevelHH
and LevelHHH. All affected parameter names are
thus altered.
4. The CommonOutput control module is
removed from the SupervisionLib library. The
handling of common outputs is simplified and
improved. The module OutputOrder shall be
used instead of CommonOutput, for both
common outputs and area outputs. This
enables feedback supervision for both types of
outputs.
5. One parameter is added on the OutputOrder
control module; OrderIn. The OrderIn
parameter enables connection to OrderOr
modules, for common outputs activation logic.
6. On the OutputOrder module, parameters for
activation due to connected protection systems
are removed.

3BSE036342-510 C 399
800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility Issues Appendix B Control Builder M Compatibility

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Standard libraries 800xA 5.0 SP2 includes 7. The control modules DetectionSite,
included in AC 800M the new library versions DetectionAreaGroup, DetectionArea are
Connect. as well as the old library removed from the SupervisionLib library. These
NOTE: These issues versions in order to 'example modules' gave a misleading guideline
are only valid for handle the upgrade for and was difficult to use because they had to be
users that have used those who have used copied (instead of instantiated like other control
either them. The use of the old module types).
SupervisionLib or versions is, however, not An example project is delivered with Control
FireGasLib. Other supported. Users must Builder (instead of the removed modules),
users will not be reconnect to the new similar to other standard libraries.
affected by these library versions and
issues. (continued) modify applications before
they go into supported
operation. (continued)
800xA 5.0 SP2 includes FireGasLib
the new library versions 1. A new control module type, FGOutputOrder,
as well as the old library is added in FireGasLib. This is similar to the
versions in order to OutputOrder module in SupervisionLib, but with
handle the upgrade for the parameters for activation due to connected
those who have used protection systems (i.e. connected Co2,
them. The use of the old Deluge, Sprinkler modules).
versions is, however, not
2. The control modules FGSite, FireAreaGroup,
supported. Users must
FireArea are removed from the FireGasLib
reconnect to the new
library. These example modules gave a
library versions and
misleading guideline and were difficult to use
modify applications before
because they had to be copied (instead of
they go into supported
instanciated like other control module types).
operation.

400 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Code sorting loops Code sorting loops in First, try to correct the sorting loops. Refer to
treated as errors. applications are by default Interpret and Correct Code Loop Errors in
considered as errors in Industrial IT, 800xA - Control and I/O,
800xA 5.0 SP2. Application Programming, Introduction and
It is not possible to Design (3BSE043723*).
compile and download an Another alternative is to change the compiler
application if it contains switch for Code Sorting Loops:
code sorting loops. 1. Mark the project in Project Explorer.
2. Right-click and select Settings > Compiler
Switch.
3. Set the global Loops in Control Modules
switch to Warning.
Applications having Compile error 1040 might Correct the compile error.
integer literal values appear in Control Builder e.g. by entering a smaller, legal value on the
too large as initial projects that previously literal.
values. did not contain any
compile errors.
Control Builder now
makes more stringent
compiler checks on initial
values for variables. It
previously allowed illegal
(too large) integer literal
values as initial values.
The actual used value
was zero.

3BSE036342-510 C 401
800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility Issues Appendix B Control Builder M Compatibility

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Applications using SattBus on TCP/IP will not Change the application to use function blocks
SattBus on TCP/IP. work after the upgrade. and data types from SattBusCommLib as
The COMLI follows:
communication function Function Blocks
blocks have been used Before After
also for SattBus on
COMLIConnect ComliSBConnect
TCP/IP, but this is no
longer the case. A new COMLIRead ComliSBRead
library including a set of COMLIReadCyc ComliSBReadCyc
new function blocks COMLIReadPhys ComliSBReadPhys
should be used instead.
COMLIWrite ComliSBWrite
COMLIWriteDT ComliSBWriteDT
Data Types
Before After
Comm_Channel_COMLI
Comm_Channel_ComliSB
Compiler warnings If there is a risk that tasks Apply proper task offsets so that the tasks can
occur if there is a risk can collide in the no longer collide.
for task collisions. controller, a warning will
be displayed during
compilation. The
compilation warning will
look like:
Warning 9155:
Controller_1:HW
Task Normal and
Fast may have
colliding start
times

402 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Self defined serial The Serial Use of firmware functions:
communication using Communication Library Firmware functions used for serial
the Serial has undergone a major communication handling are no longer
Communication internal redesign that in supported.
Library. some cases may lead to
This means that user-built libraries where these
compatibility issues.
firmware functions have been used, can no
longer be used.
The no longer supported firmware functions
are:
• OpenDevice
• UpdateDeviceSetup,
• SetDeviceClearRead
• CloseDevice.
• ReadStringDevice
• ReadLineDevice
• WriteStringDevice
Improvement were made in the following
areas:
• Clear buffer when entering the listen
operation of the SerialListen function
block.
• If the SerialWriteWait function block is
triggered when the timeout has elapsed,
the read/listen buffer is cleared in between
the retry operations in connection to the
write operation.

3BSE036342-510 C 403
800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility Issues Appendix B Control Builder M Compatibility

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Self defined serial The Serial • Behavior of the SerialWriteWait
communication using Communication Library function block in previous versions: If
the Serial has undergone a major the function block was triggered after the
Communication internal redesign that in application stopping phase was entered,
Library. some cases may lead to the function block should normally
(continued) compatibility issues. propagate status code -15. But this was
(continued) masked, and instead, after the finished
application change, the function block
automatically retriggered the write
operation.
• Behavior of the SerialWriteWait
function block in previous versions: If
the function block is triggered after the
application stopping phase is entered, the
function block propagates the status code -
15 via the Status -parameter.
If the power fails, and a function block was in a
pending state, the Status -5331 is derived from
it after the controller is powered up again.

404 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues 800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

Self defined serial The Serial Printing a string longer than 140 characters:
communication using Communication Library The behavior of the SerialWrite operation is no
the Serial has undergone a major longer synchronous. Therefore, the possibility
Communication internal redesign that in to call one and the same function block time
Library. some cases may lead to after time to print a longer string than 140
(continued) compatibility issues. characters is no longer supported.
(continued) Instead, do like the following:
To be able to print a string longer than the
maximum length of 140 characters, call
subsequent function blocks in order:
Write1( Req := TRUE,
Id := Id,
EndChar := EndChar_Write1,
Done => Done_Write1,
Error => Error_Write1,
Status => Status_Write1,
Sd := Sd_Write1 );
Write2( Req := TRUE,
Id := Id,
EndChar := EndChar_Write2,
Done => Done_Write2,
Error => Error_Write2,
Status => Status_Write2,
Sd := Sd_Write2 );
Printing the two strings Sd_Write1 + Sd_Write2
by calling the two function blocks will be queued
up, and it will be printed in a series.

3BSE036342-510 C 405
800xA 3.1 SP3 to 800xA 5.0 SP2 Compatibility Issues Appendix B Control Builder M Compatibility

Table 14. 800xA 3.1 SP3 to 800xA 5.0 SP2 Control Builder M Compatibility Issues (Continued)

Application Issue Solution

ProcessObjectAE The Name parameter on Applications using this Function Block need to
Function block the ProcessObjectAE be changed to use the CondNameObjErr
parameter name Function Block in parameter instead.
change AlarmEventLib has a
changed name. The
parameter is now called
CondNameObjErr.
This means that
applications using the
ProcessObjectAE will not
be able to be downloaded
after the upgrade. There
will be compilation errors
for unknown parameter
names.
Some project 1. If these project 1. Change to the correct literal value in the
constants have been constants have been used places where the project constants are used.
removed from in code there will be 2. Check if the value of the removed project
SupervisionBasicLib compile errors after constant was changed in the project in 800xA
(cSinit.*), BasicLib upgrading the project. 5.0 SP1a. This can be done by opening the
(cEnable.*), and 2. If the value of the Project Constants dialog box after the upgrade
SupervisionLib project constants was and seeing if the project constants are listed.
(cInit.*). Refer to changed in the project in In that case the parameters previously using
Removed Project 800xA 5.0 SP1a, it will the project constant as a default value must be
Constants on page lead to changed behavior manually connected to a literal with the
407 for a list of the of the code after the corresponding value.
removed project upgrade, because these
constants. project constants have
been used as default
values on parameters.

406 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues Removed Project Constants

Removed Project Constants

Some project constants have been removed from SupervisionBasicLib (cSinit.*),
BasicLib (cEnable.*), and SupervisionLib (cInit.*).

SupervisionBasicLib (cSinit.*)
• cSinit.Latch shall be replaced by ‘true’.
• cSinit.LevelHH shall be replaced by ’80.0’.
• cSinit.LevelH shall be replaced by ’60.0’.
• cSinit.LevelL shall be replaced by ’40.0’.
• cSinit.LevelLL shall be replaced by ’20.0’.

BasicLib (cEnable.*)
Table 15. BasicLib (cEnable)

cEnable.InputOverUnderRange bool Default value in library BasicLib 1.4-11 (bool):

false
cEnable.OutputOverUnderRan bool Default value in library BasicLib 1.4-11 (bool):
ge false

SupervisionLib (cInit.*)
Table 16. SupervisionLib (cInit.*)

cInit.AckreqAtErr bool Default value in library SupervisionLib 2.3-7 (bool):

false
cInit.AckReqToReset bool Default value in library SupervisionLib 2.3-7 (bool):
false
cInit.ActOnError bool Default value in library SupervisionLib 2.3-7 (bool):
false
cInit.AEClass dint Default value in library SupervisionLib 2.3-7 (dint):
1

3BSE036342-510 C 407
SupervisionLib (cInit.*) Appendix B Control Builder M Compatibility Issues

Table 16. SupervisionLib (cInit.*) (Continued)

cInit.AEConfigCableBreak dint Default value in library SupervisionLib 2.3-7 (dint):

0
cInit.AEConfigDetectorFaul dint Default value in library SupervisionLib 2.3-7 (dint):
t 0
cInit.AEConfigDiffInput dint Default value in library SupervisionLib 2.3-7 (dint):
1
cInit.AEConfigDiffOutput dint Default value in library SupervisionLib 2.3-7 (dint):
3
cInit.AEConfigErr dint Default value in library SupervisionLib 2.3-7 (dint):
1
cInit.AEConfigH dint Default value in library SupervisionLib 2.3-7 (dint):
1
cInit.AEConfigHH dint Default value in library SupervisionLib 2.3-7 (dint):
1
cInit.AEConfigL dint Default value in library SupervisionLib 2.3-7 (dint):
0
cInit.AEConfigLoopFault dint Default value in library SupervisionLib 2.3-7 (dint):
0
cInit.AEConfigMaintenanc dint Default value in library SupervisionLib 2.3-7 (dint):
e 0
cInit.AEConfigPrewarn dint Default value in library SupervisionLib 2.3-7 (dint):
1
cInit.AEConfigShortCircuit dint Default value in library SupervisionLib 2.3-7 (dint):
0
cInit.AESevCableBreak dint Default value in library SupervisionLib 2.3-7 (dint):
800
cInit.AESevDetectorFault dint Default value in library SupervisionLib 2.3-7 (dint):
800

408 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues SupervisionLib (cInit.*)

Table 16. SupervisionLib (cInit.*) (Continued)

cInit.AESevDiffInput dint Default value in library SupervisionLib 2.3-7 (dint):

800
cInit.AESevDiffOutput dint Default value in library SupervisionLib 2.3-7 (dint):
300
cInit.AESevErr dint Default value in library SupervisionLib 2.3-7 (dint):
800
cInit.AESevFeedback dint Default value in library SupervisionLib 2.3-7 (dint):
300
cInit.AESevH dint Default value in library SupervisionLib 2.3-7 (dint):
800
cInit.AESevHH dint Default value in library SupervisionLib 2.3-7 (dint):
800
cInit.AESevL dint Default value in library SupervisionLib 2.3-7 (dint):
800
cInit.AESevLoopFault dint Default value in library SupervisionLib 2.3-7 (dint):
800
cInit.AESevMaintenance dint Default value in library SupervisionLib 2.3-7 (dint):
800
cInit.AESevPrewarn dint Default value in library SupervisionLib 2.3-7 (dint):
800
cInit.AESevReleased dint Default value in library SupervisionLib 2.3-7 (dint):
300
cInit.AESevShortCircuit dint Default value in library SupervisionLib 2.3-7 (dint):
800
cInit.AlarmLimit real Default value in library SupervisionLib 2.3-7 (real):
40.0
cInit.ConfirmedLimitH dint Default value in library SupervisionLib 2.3-7 (dint):
2

3BSE036342-510 C 409
SupervisionLib (cInit.*) Appendix B Control Builder M Compatibility Issues

Table 16. SupervisionLib (cInit.*) (Continued)

cInit.ConfirmedLimitHH dint Default value in library SupervisionLib 2.3-7 (dint):

0
cInit.ConfirmedLimitOr bool Default value in library SupervisionLib 2.3-7 (bool):
true
cInit.DelayTime time Default value in library SupervisionLib 2.3-7 (time):
TIME#10s
cInit.EnableCommonReset bool Default value in library SupervisionLib 2.3-7 (bool):
true
cInit.EnableRangeConvers bool Default value in library SupervisionLib 2.3-7 (bool):
ion false
cInit.Latch bool Default value in library SupervisionLib 2.3-7 (bool):
true
cInit.LevelCableBreak real Default value in library SupervisionLib 2.3-7 (real):
1.0
cInit.LevelDetectorFault real Default value in library SupervisionLib 2.3-7 (real):
3.0
cInit.LevelDiff real Default value in library SupervisionLib 2.3-7 (real):
10.0
cInit.LevelLoopFault real Default value in library SupervisionLib 2.3-7 (real):
3.5
cInit.LevelMaintenance real Default value in library SupervisionLib 2.3-7 (real):
2.5
cInit.LevelShortCircuit real Default value in library SupervisionLib 2.3-7 (real):
19.0
cInit.OneLevelH real Default value in library SupervisionLib 2.3-7 (real):
10.0
cInit.OneLevelL real Default value in library SupervisionLib 2.3-7 (real):
5.0

410 3BSE036342-510 C
Appendix B Control Builder M Compatibility Issues SupervisionLib (cInit.*)

Table 16. SupervisionLib (cInit.*) (Continued)

cInit.OutputResetDelay time Default value in library SupervisionLib 2.3-7 (time):

TIME#1s
cInit.PrewarningLimit real Default value in library SupervisionLib 2.3-7 (real):
5.0
cInit.RedIncDecLim real Default value in library SupervisionLib 2.3-7 (real):
10.0
cInit.ResetTime time Default value in library SupervisionLib 2.3-7 (time):
TIME#5s
cInit.ResponseTime time Default value in library SupervisionLib 2.3-7 (time):
TIME#5s
cInit.RText string Default value in library SupervisionLib 2.3-7
(string): 'R'
cInit.TwoLevelH real Default value in library SupervisionLib 2.3-7 (real):
20.0
cInit.TwoLevelHH real Default value in library SupervisionLib 2.3-7 (real):
60.0
cInit.UseLevelPar bool Default value in library SupervisionLib 2.3-7 (bool):
True

3BSE036342-510 C 411
SupervisionLib (cInit.*) Appendix B Control Builder M Compatibility Issues

412 3BSE036342-510 C
 Appendix C Consistency Check

Introduction
The following is an overview of the consistency check functionality in the
800xA System.
• Perform consistency checks both before and after the upgrade.
• The consistency check is continuously improved between releases. If a
consistency error is detected after the upgrade, it does not necessarily mean that
the error was introduced by the upgrade process. It might have been there from
the beginning, but went undetected.
• Try to correct all consistency errors before the upgrade. This will make the
upgrade process easier. Consistency errors may cause the upgrade to either fail,
or continue, but without having done exactly what was intended. Since it is
very difficult to know where the upgrade handling will do changes, it is
desirable to make the system as consistent as possible before the upgrade. It is
also good to keep a system with the old version running so it is possible to go
back and do more corrections in the old system if problems occur during the
upgrade.
– However, the upgrade will often work even though there are some
remaining consistency errors. In some cases it is easiest to correct the
errors after the upgrade (because the repair functionality has been
improved in the new release), so it may be worth an attempt at continuing

3BSE036342-510 C 413
Introduction Appendix C Consistency Check

with the upgrade. It is recommended to keep a list of the detected

consistency errors for future reference.
During the consistency check the following error messages might come from
PROFIBUS Hardware Libraries in system version 5.0 and later:
[Error] Library key must not be used on
'ABB_TFx12_PA 1.2-0:Aspect Category
Definition'. ... : Library Version Definition
[Error] Aspect 'ABB_TFx12_PA 1.2-
0:Hardware Library' contains multiple library
keys. ... : Library Version Definition
[Error] Library key must not be used on
'ABB_TFx12_PA 1.2-0:Object Type
Structure'. ... : Library Version Definition
3 error(s) reported by 1 aspect(s).
1 aspect(s) can be repaired
This will have no impact on system upgrade.
• In 800xA 5.0 and later, perform the consistency check with the Consistency
Check tool (started by clicking the question mark icon in top right corner of
Plant Explorer Workplace). In 800xA 4.1 the Consistency Checker aspect must
be used.
• Perform consistency checks on the user-defined libraries in the Object Type
Structure or Library Structure, the Control Project in Control Structure,
and the Functional Structure.
• The general part of the upgrade process consists of importing new versions of
standard libraries, and propagating object type changes to user libraries and
user applications. It is only necessary to correct consistency errors regarding
object type, object type references, and similar configurations for the general
part of the upgrade process to work. Other inconsistencies such as unresolved
references should normally not lead to problems.
– However, special upgrade handling designed by the Functional Areas may
also update the references of aspects, so it is best to correct also broken
references before the upgrade.
– In the Library structure, navigate to Library Version Definition aspect
present in the user defined libraries. Select the Consistency tab and click

414 3BSE036342-510 C
Appendix C Consistency Check Performing the Consistency Check

Check Consistency. Correct any errors that may appear during the
consistency check (This is valid for 800xA 4.1 and 800xA 5.0 systems).

Performing the Consistency Check

In 800xA 5.0 and later, perform the consistency check with the Consistency Check
tool (started by clicking the question mark icon in top right corner of Plant Explorer
Workplace). In 800xA 4.1 the Consistency Checker aspect must be used. This
instruction only includes the 800xA 5.0 and later procedure. Refer to System 800xA
Tools (2PAA101088*) for more detailed information on running the 800xA 5.1
consistency check. The 800xA 4.1 procedure can be found in 800xA 4.1 specific
documentation.
Perform a consistency check before performing the 800xA System backup.
Failure to do so could result in problems when restoring the system after the
upgrade.
If using Asset Optimization, be sure to run the Consistency Check tool and delete
any inconsistent Asset Monitor Control Connection Properties aspects.
Perform the following to perform a consistency check:
1. Open a Plant Explorer Workplace.
2. Click the Consistency Check Tool icon at the top of the Plant Explorer
Workplace to launch the Consistency Check Tool.
Rather than performing Step 3 through Step 6 it is also possible to drag the
desired items to the Consistency Check Tool.
3. Click Add Item to launch the Select Item dialog box.
4. Browse to the desired location.
5. Select the desired items (use Ctrl+Click or Shift+Click to select multiple
items). If a subtree is selected, all objects and aspects in the subtree will be
selected. If a library or application is selected, everything in this entity will be
selected.
6. Click Add and Close.
7. Click Check.
8. If errors are found, and they are marked Repairable, perform an automatic
repair by selecting Repair Aspect in the context menu.

3BSE036342-510 C 415
Returning to the Pre-Upgrade Procedures Appendix C Consistency Check

9. If errors are found that are not automatically repairable, try to manually
reconfigure the aspects to repair the consistency errors.

Returning to the Pre-Upgrade Procedures

These links are designed for online viewing. If using a hard copy, go back to the
point in the procedure that referred to this appendix.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Online Upgrade.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Offline Upgrade.
Click here to return to 800xA 4.1 to 800xA 5.1 Offline Upgrade.
Click here to return to 800xA 3.1 SP3 to 800xA 5.0 SP2 Upgrade.

Returning to the Post Upgrade Procedures

These links are designed for online viewing. If using a hard copy, go back to the
point in the procedure that referred to this appendix.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Online Upgrade.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Offline Upgrade.
Click here to return to 800xA 4.1 to 800xA 5.1 Offline Upgrade.
Click here to return to 800xA 3.1 SP3 to 800xA 5.0 SP2 Upgrade.

416 3BSE036342-510 C
 Appendix D Recording the Number of
Aspects and Objects

Introduction
Record the number of aspects and objects in the system in order to compare the
number before the 800xA System Backup and after the 800xA System Restore.

Recording the Number of Aspects and Objects in the

System
Perform the following procedure to record the number of aspect and objects in the
system.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Admin Structure.
3. Use the Object Browser to navigate to:
Administrative Objects\Domains\system_name, Domain
4. Select Domain Definition in the Aspect List Area.
5. Record the number of objects and aspects listed in the System Size Information
frame in the Preview Area.
6. Use the Structure Selector to open the Control Structure.
7. Use the Object Browser to navigate to:
control_network_name, Control Network
of one of the control networks contained in the system.

3BSE036342-510 C 417
Recording the Number of Aspects and Objects in the System Appendix D Recording the Number of

8. Right-click the Control Structure aspect and select Details from the context
menu.
9. Select the Statistics tab.
10. Record the number of objects listed.
Step 11 through Step 15 are not applicable to systems with only 800xA for
Harmony.
11. Right-click the Control Structure aspect within a controller project of the
control network selected in Step 7.
12. Select Details from the context menu.
13. Record the number of objects listed.
14. Repeat Step 11 through Step 14 for all the controller projects within the control
network.
15. Repeat Step 7 through Step 14 for every control network in the system.
The number of aspects and objects after system restoration should be in the same
range as those recorded during system backup, although there will likely be more.
16. Use the Object Browser to navigate to:
HSE_Subnet name, HSE Subnet
of one of the HSE Subnets contained in the system.
17. Right-click the Control Structure aspect and select Details from the context
menu.
18. Select the Statistics tab.
19. Record the number of objects listed.
20. Repeat Step 16 through Step 19 for every HSE Subnet in the system.
21. Use the Object Browser to navigate to:
MB300 name, MB300 Network
of one of the MB 300 Networks contained in the system.
22. Right-click the Control Structure aspect and select Details from the context
menu.

418 3BSE036342-510 C
Appendix D Recording the Number of Aspects and Objects Returning to the Pre-Upgrade

23. Select the Statistics tab.

24. Record the number of objects listed.
25. Repeat Step 21 through Step 24 for every MB300 network in the system.
The number of aspects and objects after system restoration should be in the same
range as those recorded during system backup, although there will likely be more.

Returning to the Pre-Upgrade Procedures

These links are designed for online viewing. If using a hard copy, go back to the
point in the procedure that referred to this appendix.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Online Upgrade.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Offline Upgrade.
Click here to return to 800xA 4.1 to 800xA 5.1 Offline Upgrade.

Returning to the Post Upgrade Procedures

These links are designed for online viewing. If using a hard copy, go back to the
point in the procedure that referred to this appendix.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Online Upgrade.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Offline Upgrade.
Click here to return to 800xA 4.1 to 800xA 5.1 Offline Upgrade.

3BSE036342-510 C 419
Returning to the Post Upgrade Procedures Appendix D Recording the Number of Aspects and

420 3BSE036342-510 C
 Appendix E Information Management
Upgrade

Information Management Pre-Upgrade Procedures

Perform the following procedures to prepare for the Information Management
upgrade.
This appendix is not applicable to the 800xA 3.1 SP3 to 800xA 5.0 SP2 upgrade
path. Refer to Section 6, Upgrading 800xA 3.1 SP3 to 800xA 5.0 SP2 for more
information.

End Microsoft Excel Process via Windows Task Manager

Use Windows Task Manager to manually end the EXCEL.EXE process.

Recording Archive Group Associations

Recording archive group associations only applies to 800xA 4.1 to 800xA 5.1
upgrades.
Archive Groups are associated with Profile, Message, and Report logs.
1. Record these associations so that after the upgrade, these logs can be
reassociated with their respective Archive Groups. Refer to the Reading and
Managing Archive Data section in Industrial IT, 800xA - Information
Management, Data Access and Reports (3BUF001094*) to access the Archive
Groups and record the information.
2. Back up the path to Archive Group Numeric Log Entry and IM Objects Entry.

ABB Process Administration Service (PAS)

Perform the following procedure to run the PAS utility.

3BSE036342-510 C 421
Cleaning the History Database Appendix E Information Management Upgrade

1. Run the Process Administration Service (PAS) utility on the Information

Management Application Server node. From the Windows Taskbar select:
Start > Settings > Control Panel > Administrative Tools > PAS >
Process Administration
This opens the Process Administration Service dialog box.
2. Click Stop All to stop all processes under PAS supervision.
3. Click Close when the dialog box indicates that all processes are stopped.
4. Use standard Windows procedures, via the Services selection from
Administrative Tools in Windows Control Panel, to place the ABB Process
Administration Service into manual and insure that it is stopped.

Cleaning the History Database

It is recommended that the history database be cleaned before making the backup.
1. Open a Windows Command Prompt and enter hsDBMaint -checkDB.
2. If any problems are found, enter hsDBMaint -clean to fix them.

Information Management History Backup and Restore Utility

The IM Server must be connected to an active aspect system at this time. The
following steps require acesss to the aspect directory.
Use the Information Management History Backup/Restore utility to create all the
backup files that are required to completely back up the Information Management
History database. This includes all configuration data, log data from both file-based
and ORACLE-based logs, and the Aspect System definition file.
During a backup operation, all data in the Oracle database owned by the Oracle
History user is exported to the specified destination and compressed into a zipped
archive, along with any files that have been created to store file-based property log
entries (called flat files).
The History database can be backed up to any drive, including any mapped network
drives. The disk type should be NTFS for the backups.
To avoid any ambiguity, the backup operation produces a zipped archive of
compressed History database files for each drive that contains at least some portion

422 3BSE036342-510 C
Appendix E Information Management Upgrade Information Management History Backup and

of the database, where each archive contains only the database files that are stored
on the corresponding drive. The backup utility uses the naming convention
name-drive.zip for the zipped archives that it produces. For example, if the
History database is located entirely on the C:\ drive and you wish to back up the
database to a zipped archive called hist, the backup operation will compress the
database files into a zipped archive named histDB-C.zip.
If the data files exceed two gigabytes, or if there are more than 25,000 files, then
multiple zip files will be created using the following naming convention:
• First File name-drive.zip
• Next File name-drive0001.zip
• Next File name-drive0002.zip
When backing up the History database, make sure the disk is ready and available on
the node on which the procedure is to occur. The log file should be checked after the
backup operation to make sure that the backup operation completed successfully.
Make sure the system drive is not getting full. Temp space is required to make the
backup. If the log file indicates that the Oracle export failed, additional options can
be passed to hsBAR to use another disk for the Oracle export.
To make a backup:
1. Select:
Start > All Programs > ABB Industrial IT 800xA > Information
Mgmt > History > Backup and Restore
2. Verify the Create Backup Files of Current Configuration option is enabled
in the IM Historian Backup/Restore Utility window.
3. Click Next. A window for setting up the backup operation is displayed.
4. Specify the location where the backup files are to be created in the New
Directory Path for the Backup field. Create a new directory such as
E:\IMbackupSV5SP2.
The backup of the History data must be in a directory of its own, not the
D:\HSDATA\History directory. If the data is put into the D:\HSDATA\History
directory, it will get lost.
a. Specify additional hsBAR options if needed. When the system drive is low
on space, it is typical to specify:

3BSE036342-510 C 423
Saving Other Information Management Related Files Appendix E Information Management

-a D:\Export
The -a option enables an alternate location for temporary and Oracle DB
export files during the backup process. The folder should be created ahead
of time and the files system must be NTFS. Use this option to specify a
different folder for the oracle export file.
5. Verify the Only Generate Aspect Definition File option is disabled.
6. Click Next. The HsBAR Output Window is displayed.
7. Select the Automatically Close Upon Completion option.
8. After the HsBAR Output Window closes, monitor the progress in the Progress
Status area of the IM Historian Backup/Restore Utility window and click
Finish when the backup is complete.
If a message appears stating that there are inconsistencies between the log
configurations in the Aspect System and the log configurations in Oracle, it may
be because the database was not cleaned before running the backup. Use the
hsDBMaint -clean function to clean the database and then rerun the backup. If
this does not fix the problem, contact ABB Technical Support for further
assistance.

Saving Other Information Management Related Files

There are several other files related to Information Management to be saved as part
of a total system backup.
• History Archive Data: For each archive device, go to the location specified by
the Device Filename and copy the folders under that directory to a safe
location. Do this even if automatic backup is configured. If the automatic
backups are on local disks, locate these folders and back them up to a safe
location.
• History Archive State Information: The folder that holds the last archive
time and other archive state information must be copied to a safe location. The
folder name is Archive and it is located in:
...\Documents and Settings\All Users\
Application Data\ABB\IM\Archive
Copy the entire folder.

424 3BSE036342-510 C
Appendix E Information Management Upgrade Returning to the Pre-Upgrade Procedures

• Reports: Save any report template files created in Microsoft Excel,

DataDirect, and/or Crystal Reports ®. Also save report output files created as a
result of running these reports via the Scheduling Services.
• Desktop Trends: Back up trend display, ticker display, and tag explorer files.
– Ticker files are located in:
...\My Documents\ABB Industrial IT\Inform IT\Desktop
Trends\Ticker Files
– Trend Files are located in:
...\My Documents\ABB Industrial IT\Inform IT\Desktop
Trends\HTML
– Tag Explorer files are located in:
...\Documents and Settings\~username\Application
Data\ABB Industrial IT\Inform IT\Desktop Trends
• Display Services: Back up the directories for custom users, as well as display
and user element definitions. The files are located in:
...\Program Files\ABB Industrial IT\Inform IT\Display
Services\Server\Data
Save the user-built svg and vet files.
• DataDirect: Back up custom text files for object, object type, and attribute
menus used on the DataDirect windows. The files are located in:
...\Program Files\ABB Industrial IT\Inform IT\Data
Direct\etc.
Save the user-built text files.

Returning to the Pre-Upgrade Procedures

These links are designed for online viewing. If using a hard copy, go back to the
point in the procedure that referred to this appendix.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Online Upgrade.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Offline Upgrade.

3BSE036342-510 C 425
Information Management Post Upgrade Procedures Appendix E Information Management Upgrade

Click here to return to 800xA 4.1 to 800xA 5.1 Offline Upgrade.

Information Management Post Upgrade Procedures

Perform the following post upgrade procedures for Information Management. Files
only have to be restored when a new node is being loaded from backups. The Oracle
upgrade and database conversion procedure will upgrade existing or restored
files.
When creating the Oracle instance, select I am upgrading from SV3.x or SV4.x
or newer system in the Configuration File Options dialog box to prevent the
wizard from creating a history database. This will prevent History from starting
until after the History Database is restored.
The procedures presented here are different than those in System 800xA Post
Installation (3BUA000156*). Unless otherwise noted, perform the procedures
presented here.
When creating the database, it is possible to select small, medium, or large for the
database size. If it is not known what the size of the database will be, select large.
PAS is not initialized at this point in the process, and it should not be.

Reconfiguring the IM Log Configuration

When the procedure is followed, the IM service group is preserved and all Log
Configurations should have a valid setting. If there is not a valid setting, a
previous step was not followed and this procedure will correct the problem.
After restoring a system containing IM logs, the Service Group for the IM log
template configuration might be missing. The IM log templates must be checked,
and if the Service Group is missing, a new Service Group must be configured.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Library Structure.
3. Use the Object Browser to navigate to:
History Log Templates, History Log Template Library >
Default Log Templates, History Log Template Library

426 3BSE036342-510 C
Appendix E Information Management Upgrade Information Management History Backup/Restore

4. Select a log template.

5. Select Log Template in the Aspect List Area.
6. Select the Log Definition tab in the Preview Area.
7. If the Service Group in the Service Group drop-down list box is missing, it
must be reconfigured. The Service Group drop-down list box contains all
History servers defined in the system. Use this list to specify the server where
this log will reside.
8. Repeat this procedure for all of the log templates.

Information Management History Backup/Restore Utility

Use the Information Management History Backup/Restore utility, via:
Start > ABB Industrial IT 800xA > Information Mgmt > History >
Backup and Restore
to restore the Information Management History database and synchronize the
Aspect Directory contents with the current Information Management History
database configuration.
During the restore, the existing database is dropped, and a new one is created.
Mount points and additional table spaces are created based on the database being
restored. Oracle data is imported, and the file-based property logs are copied back
into the system. Unless a different mount point is specified, the History database
will be restored to its original location (its location prior to being backed up).
The History database can be restored from any drive, including any mapped network
drives. The restore utility will first search a specified location for zipped archives
matching a specific name and fitting the form name-drive.zip (such as histDB-
C.zip, histDB-A.zip, and histDB-D.zip), and will then restore the
compressed database files contained within the archives to their respective original
locations (their locations prior to being backed up).

Considerations
When restoring the History database, make sure the disk is ready and available on
the node on which the procedure is to occur. Also, ensure that no applications are

3BSE036342-510 C 427
Information Management History Backup/Restore Utility Appendix E Information Management

accessing the Oracle database. The log file should be checked after the restore
operation to make sure that the restore operation completed successfully.

Running the Information Management History Backup/Restore Utility

To restore a backed up History database:
This procedure can also be performed by using the pasgui command in the Run
dialog box (Start > Run).
1. Verify that the ABB Process Administration Service (PAS) is set to manual in
the Services Control Panel (run Services.msc from the Run dialog box). Stop
the service if it is running.
If PAS is not in the manual mode, it is possible the log configuration has been
modified and will not match the IM backup. If this is the case, the 800xA System
Restore may have to be repeated to correct the problem.
2. If it is suspected that the Inform IT History Service Provider has not stopped, it
can be stopped now by selecting the Inform IT History Service Provider for this
node in the Service Structure, selecting the Configuration tab on the Service
Provider Definition aspect, disabling Enabled, and clicking Apply.
3. Ensure that no third party applications access the Oracle database during the
restore operation.
4. Before restoring the database, it is necessary to create an Oracle database to
restore the backup.
a. Start the Oracle Instance wizard using:
Start > Programs > ABB Industrial IT > Information Mgmt > History
> Oracle Instance Wizard
b. Create a database to restore an 800xA 3.x, 800xA 4.1 or 800xA 5.x
system. Be sure to select the correct size for the database. If the previous
system had more than four million entry message logs, select large, for
one to four million select medium, and for less than one million select
small.
If a database previously existed, drop it and create the correctly sized database.

428 3BSE036342-510 C
Appendix E Information Management Upgrade Information Management History Backup/Restore

5. Restore the database. Select:

Start > All Programs > ABB Industrial IT 800xA > Information
Mgmt > History > Backup and Restore.
6. Verify Restore configuration from a backup file(s) is enabled in the
Welcome to IM Historian Backup and Restore Utility dialog box.
7. Click Next. IM Historian Database Restore dialog box appears (Figure 51).

TC08390A

Figure 51. IM Historian Database Restore Dialog Box

8. Specify the location of the backup files in the Path of IM historian backup:
field (Figure 51).
If new mount points need to be specified for file-based logs and/or a new Oracle
tablespace definition file, click Browse. This will be required if the partition
letters where the IM data is stored have changed.
9. Click Next. The HsBAR Output Window appears.
10. Select the Automatically close upon completion check box.

3BSE036342-510 C 429
Information Management History Backup/Restore Utility Appendix E Information Management

11. Monitor the progress in the Progress Status area of the IM Historian
Backup/Restore Utility window. Ignore the error messages indicating errors
deleting aspect.
Shortly after the message indicating the import is complete, the database
conversion tool will run automatically. Feedback will be provided in the
HsBAR window.
Shortly after the message indicating the database conversion is complete, the
history synchronization tool will run automatically. Again, feedback will be
provided in the HsBAR window.
The restore of the system requires an instance that matches the size of the
database being restored. When creating the instance, be sure to select Small,
Medium, or Large based on the size of the message log in the backup being
restored. Select Large if the size is not known. If the wrong size is selected, the
restore operation may fail with the Oracle Error Message 1652 - Unable to
extend tmp segment in tablespace temp. Repeat the restore with the
correct instance settings if the error occurs. This will not happen if the correct
database for upgrade is selected. For example, if the database is using a 12
million entry OPC message log, the large option should be selected. This will
insure that enough TEMP and rollback are created.
12. Click Finish when a message stating the execution is complete is displayed as
shown in Figure 52.

TC08391A

Figure 52. Execution is Complete Message

If the Progress Status dialog box has warning messages with possible solutions as
indicated in Figure 53, read the possible solutions carefully, then click Finish and

430 3BSE036342-510 C
Appendix E Information Management Upgrade Restoring Other Information Management Related

proceed with the solution that best fits your problem. Refer to the Information
Management Release Notes for further guidelines.

TC08392A

Figure 53. Progress Status Dialog Box

Restoring Other Information Management Related Files

There are several other files related to Information Management that need to be
restored as part of total system restore.
• History Archive Data: For each archive device, copy the appropriate folders
from the safe media to the location specified by the Device Filename. If the
disk configuration has changed from the previous system to the new system
(i.e. letter designations for disks have changed: C, D, E, etc.), check the archive
device configurations to make sure the Archive Path specification points to the

3BSE036342-510 C 431
Restoring Other Information Management Related Files Appendix E Information Management

correct disk drive and directory, as shown in Figure 54. Repeat for the backup
archive path if configured.

TC08388A

Figure 54. Checking the Archive Path Specification

• History Archive State Information: Stop the Industrial IT Archive service in

the Service Structure. Copy the folder that holds the last archive time and
other archive state information from the safe media to:
c:\programData\ABB\IM\Archive
• Reports: Restore any report template files created in Microsoft Excel,
DataDirect, and/or Crystal Reports. Also restore report output files created as a
result of running these reports via the Scheduling Services.
Refer to Saving Other Information Management Related Files on page 424 for
Desktop Trends, Display Services, and DataDirect file locations.
• Desktop Trends: Restore trend display, ticker display, and tag explorer files.
• Display Services: Restore the directories for custom users, as well as display
and user element definitions.
• DataDirect: Restore custom text files for object, object type, and attribute
menus used on the DataDirect windows.

432 3BSE036342-510 C
Appendix E Information Management Upgrade Starting PAS

Starting PAS
1. Open the Services Control Panel (run Services.msc from the Run dialog box),
set the ABB Process Administration Service (PAS) to Automatic and start it.
2. Open the Information Management Configuration Assistant (Start >
Programs > ABB Industrial IT > Information Mgmt > Configuration
Assistant) and perform any incomplete steps.
3. Select the Basic History Service Provider object for the Information
Management node in the Service Structure in the Plant Explorer.
4. Select the Service Provider Definition aspect.
5. Select the Configuration tab.
6. Clear the Enabled option.
7. Click Apply.
8. Select the Enabled option.
9. Click Apply.

Restoring Archive Group Associations

Restoring archive group associations only applies to 800xA 4.1 to 800xA 5.1
upgrades.
Profile, Message, and Report logs must be reassociated with their respective
Archive Groups. This information was recorded before beginning the upgrade.
Refer to Industrial IT, 800xA - Information Management, Configuration
(3BUF001092*) to access the Archive Groups and restore the Archive Group
associations.

Instance_config.txt File Creation

The instance_config.txt file needs to be recreated (using the following procedure) if
both of the following conditions are met:
• An existing database has not been restored.
• The node is using the Windows 2008 Server Operating System.
To create the instance_config.txt file:

3BSE036342-510 C 433
Updating Archive Logs Appendix E Information Management Upgrade

1. Select:
Start > Programs > ABB Industrial IT 800xA > Information Mgmt >
History > Oracle Instance Wizard
2. Click Apply. The instance_config.txt file will be created in the following
directory:
c:\programData\ABB\IM\History
This folder is defined as %HS_DATA% environment variable.

Updating Archive Logs

Absolute names are now included as part of the archive storage. Archive links now
use an absolute reference that is independent of the name of the log. Run the archive
maintenance to update the _RST log references to use the absolute log
reference.
This procedure is not necessary if archives are not being used.

This procedure only needs to be performed one time no matter how many
Information Management nodes are in the system.
1. Open a Plant Explorer Workplace.
2. Use the Object Browser to navigate to:
IM Node > Archive Service Provider
3. Click Archive Service Aspect in the Aspect List Area.
4. Click Maintenance in the Preview Area to launch the Maintain Archive
References dialog box.
5. Click Validate Archive Logs.
6. Run a consistency check on all log configurations.

Information Management Maintenance

Perform this procedure on all Information Management Server nodes.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Node Administration Structure.

434 3BSE036342-510 C
Appendix E Information Management Upgrade Information Management Maintenance

3. Use the Object Browser to navigate to:

All Nodes, Node Group > IM Node > Inform IT History_IM
Node, Service Provider > Inform IT History Object,
Inform IT History Object
4. Select Inform IT History Control in the Aspect List Area.
5. Expand the Maintenance tree in the Preview Area and select
Synchronization. The Inform IT History Manager shown in Figure 55
appears in the Preview Area.

Figure 55. Inform IT HIstory Manager

6. Click Check Names.

7. A blank dialog box should appear. If it does, click OK. If it does not click
Resynchronize Names.
8. Click Check Synchronization.
9. A blank dialog box should appear. If it does, click OK. If it does not click
Force Synchronization.

3BSE036342-510 C 435
Running hsDBMaint -stagger Appendix E Information Management Upgrade

Running hsDBMaint -stagger

It is recommended to run hsDBMaint -stagger for all IM configurations. The
defaults are adequate for most configurations. If the average request rate is near or
over 1,000 per minute, refer to System 800xA Information Management
Configuration (3BUF001092) for hsDBMaint -stagger recommendations.
1. Open a Windows Command Prompt and enter hsDBMaint -stagger.
2. When the operation is complete run the Process Administration Service (PAS)
utility on the Information Management Application Server node. From the
Windows Taskbar select:
Start > Settings > Control Panel > Administrative Tools > PAS >
Process Administration
This opens the Process Administration Service dialog box.
3. Click Restart All to restart all processes under PAS supervision.
4. Click Close when the dialog box indicates that all processes are restarted.

Returning to the Post Upgrade Procedures

These links are designed for online viewing. If using a hard copy, go back to the
point in the procedure that referred to this appendix.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Online Upgrade.
Click here to return to 800xA 5.0 SP2 to 800xA 5.1 Offline Upgrade.
Click here to return to 800xA 4.1 to 800xA 5.1 Offline Upgrade.

436 3BSE036342-510 C
 Appendix F Mapping of Deprecated IT Asset
Object Types

Mapping
This section describes the mapping of deprecated IT Asset object types with their
replacements available in the PNSM device library. The supported PNSM device
library object types are listed in Table 17.

Table 17. Mapping Deprecated IT Asset object types with replacements in PNSM Device Library

Deprecated IT Asset Object Types Replacement in PNSM Device Library

Cisco 12-port Switch Cisco 12_24_48_Port Switch_v1_0
Cisco 24-port Switch
Cisco 48-port Switch
Batch Nodes Generic_Computer_Node_v1_1
Batch Client
Batch Primary Server with Client
Batch Secondary Server with Client
Generic Computer Node
Inform IT Nodes

3BSE036342-510 C 437
Mapping Appendix F Mapping of Deprecated IT Asset Object Types

Table 17. Mapping Deprecated IT Asset object types with replacements in PNSM Device Library

Deprecated IT Asset Object Types Replacement in PNSM Device Library

PPA Nodes
800xA AS (Tertiary)
800xA AS
800xA Client
800xA Combined AS-CS
800xA CS
PPB Nodes
PPB Client
PPB Config Server
PPB Harmony RTDS with Client
PPB Historian
PPB Melody RTDS with Client
PPB OPC RTDS with Client
Hirschmann RS2 Switch Hirschmann_RS2_v1_0
Hirschmann Mach 3000 Switch(1) 1.Hirschmann_RS20_RS30_v1_2
2.Hirschmann_RS40_v1_2
3.Hirschmann_MS20_MS30_v1_2
4.Hirschmann_MS4128_v1_2
5.Hirschmann_MACH_4000_v1_2
6.Hirschmann_MACH_1000_v1_1
7.Hirschmann_RSR20_RSR30_v1_1
Generic Network Interface Generic_Network_Interface_v1_0
Generic Printer Node Printer_v1_0
Network Monitoring
• Network Utilization Network_Utilization_v1_0
• Node to Node Utilization Node_to_Node_Utilization_v1_0
• Single Node Utilization Single_Node_Utilization_v1_0

438 3BSE036342-510 C
Appendix F Mapping of Deprecated IT Asset Object Types Mapping

Table 17. Mapping Deprecated IT Asset object types with replacements in PNSM Device Library

Deprecated IT Asset Object Types Replacement in PNSM Device Library

IM Performance Assets Not supported
hsMsgServer Messages In per Minute
hsMsgServer Messages in Queue
hsMsgServer Messages Out per Minute
PDL Messages In per Minute
PDL Messages in Queue
PDL Messages Out per Minute
Disk Free
Failures
DA Collection
HDA Collection
Storages
Inform IT Calculations
Inform IT Complete
Inform IT Display
Inform IT History
Inform IT ODA
Inform IT Scheduler
Inform IT SoftPoint Server
Symmetricom XLi Clock Not supported
(1) Hirschmann Mach 3000 switch is obsolete. The replacement object type in
PNSM is not available.

3BSE036342-510 C 439
Mapping Appendix F Mapping of Deprecated IT Asset Object Types

440 3BSE036342-510 C
 Appendix G Update to 800xA 5.1 Rev A

Introduction
This section is only intended for use when manually upgrading from the latest
revision of a previous 800xA System Version to the latest revision of 800xA 5.1. It
is not intended for use when updating an existing 800xA System, or when installing
a new 800xA System.
The preferred and recommended method for installing system revisions is to use the
System Update Tool (SUT). Refer to 800xA System Update Tool User Instruction
(2PAA106938*) for instructions on automatically installing the revision using the
System Update Tool.

Affected Products
This document covers the following products:
• 800xA Base.
• 800xA for AC 800M.
• Structured Data Logger.
• 800xA for Advant Master.
• 800xA for Safeguard.
• 800xA for DCI.
• 800xA for MOD 300.
• TRIO Integration.
• 800xA for Harmony.
• 800xA for Melody.
• Softpoint Server.
• PLC Connect.
• Asset Optimization.
• SMS and e-mail Messaging.

3BSE036342-510 C 441
Uninstallation Appendix G Update to 800xA 5.1 Rev A

• PC, Network and Software Monitoring.

• Multisystem Integration.
• SFC Viewer.
• Engineering Studio.
• Device Library Wizard.
• Device Management FOUNDATION Fieldbus.
• Device Management PROFIBUS & HART.
• Batch Management.
• Central Licensing System (CLS).
• Process Engineering Tool Integration.
• Information Management.
• RNRP (only Domain Controller).
• IEC 61850 Connect.
• 800xA Documentation.
• Snapshot Reports.
• System Installer.

Uninstallation
Uninstall the products listed in Table 18 only if they are part of the System
Revision (the set of rollups) about to be installed. Refer to System 800xA 5.1
System Software Versions (3BSE056732*), Rollups column, for more information
on which rollups are included in the System Revision.
Allow one uninstallation to fully complete before starting the next one. Running
the uninstallations in parallel may harm the System. It may take time (several
seconds) between a mouse click and the corresponding user interface to appear.
Make one click at a time and let the uninstallation software respond to the first
click before making the next.
Do not restart the node after the uninstallation as this will damage the system.

Products that are not listed here will be uninstalled automatically (or a prompt
may appear) when necessary during the installation.
Uninstall the products in the order presented in Table 18. Any special instructions
required when uninstalling a product are listed in Table 18. If there are no special

442 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A Uninstallation

instructions use Programs and Features from Windows Control Panel to uninstall
the product.
It is imperative that the Special Instructions and the order listed in Table 18 be
followed, otherwise the update will fail and leave the system inoperable.

Table 18. Uninstallation Order and Instructions

Product Special Instructions

800xA for MOD 300 Perform the uninstallation on the backup Connectivity Server node first.
Once the backup Connectivity Server node is reinstalled and online,
proceed with the uninstallation on the primary Connectivity Server
node. Repeat this for all Connectivity Server node pairs in the system.
ABB PAS System ABB PAS System Services exists on Information Management Servers
Services for 800xA for and MOD 300 Connectivity servers. Uninstall ABB PAS System
MOD 300 Services only on the MOD 300 Connectivity servers. Do not uninstall
ABB PAS System Services on the Information Management Servers.
PLC Connect and Both PLC Connect and SoftPoint Server need to be uninstalled even if
SoftPoint Server only one of them is going to be installed as part of the new System
Revision.
Batch Management All actions performed on one Batch Server (stopping, uninstalling, and
installing for example) must be performed on the other Batch Servers in
the system at the same time.
The Batch Client applications must also be uninstalled.
Process Engineering Tool None
Integration
Asset Optimization None
Snapshot Reports None
800xA for Harmony None
IEC 61850 Connect Uninstall ABB IEC 61850 OPC Server from the IEC 61850 Connectivity
Server node.
1. Clear the Uninstall MSDE (PCMSERVER) check box for the
Microsoft SQL Server Desktop Engine when uninstalling ABB IEC
61850 OPC Server.
2. Proceed with the uninstall.

3BSE036342-510 C 443
Uninstallation Appendix G Update to 800xA 5.1 Rev A

Table 18. Uninstallation Order and Instructions (Continued)

Product Special Instructions

CLS and CLS Extension Perform the following on the CLS Server:
1. Open Windows Control Panel.
2. Click Administrative Tools.
3. Click Services. The Services page appears.
4. Locate and right-click World Wide Web Publishing.
5. Select Stop from the context menu to stop the service.
Perform the following on the AO Server, where ECS software is
installed:
1. Open Windows Control Panel.
2. Click Administrative Tools.
3. Click Services. The Services page appears.
4. Locate and right-click ABB cpmPlus Enterprise Connectivity.
5. Select Stop from the context menu to stop the service.
Perform the following on the CLS Server Node:
NOTE: The following steps are not applicable for the node with internet
connection.
1. Open Windows Control Panel.
2. Click Internet Options to open the Internet Properties dialog box.
3. Select the Advanced tab.
4. Navigate to the Security section.
5. Clear the Check for publisher’s certificate revocation check
box.
NOTE: After the maintenance shutdown on the CLS Server node, a
CLS Communication Failure message appears on all CLS Client
nodes. Click OK when the dialog appears.
Uninstall CLS and CLS extension using Programs and Features in
Windows Control Panel.

444 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A Installation

Installation
Required uninstallations for any of the products should be complete prior to
starting the installation. Refer to the Uninstallation on page 442 before installing.

Allow one installation to fully complete before starting the next one. Running the
installations in parallel may harm the system. It may take time (several seconds)
between a mouse click and the corresponding user interface to appear. Make one
click at a time and let the installation software respond to the first click before
making the next.

Do not restart at anytime during the installation even if prompted to do so.

1. The revision consists of the rollups listed in the Software column in Table 19.
Install them in the order listed in Table 19 if the base product is currently
installed.
2. Double-click the executable files from the rollup folders to start each
installation (the path to each executable file is shown the Path column in
Table 19). Refer to the appropriate section for special information or
instructions for the indicated product as indicated in the Special Instructions
column in Table 19.

Table 19. Rollup Installation Information (Install in the Order Listed)

Special
Software Path Executable
Instructions
800xA Base 800xA Core Functionalities\ Setup.exe
Process Portal A\
800xA Snapshot Additional Products\ABB setup.exe
Reports Snapshot Reports for 800xA
5.1.0-1
CLS 800xA Core Functionalities\ setup.exe
Licensing\CLS

3BSE036342-510 C 445
Installation Appendix G Update to 800xA 5.1 Rev A

Table 19. Rollup Installation Information (Install in the Order Listed) (Continued)

Special
Software Path Executable
Instructions
CLS Extension 800xA Core Functionalities\ setup.exe
Licensing\CLS Extension
AC 800M HI 800xA Connectivities\ Installer.exe AC 800M High
Extension 800xA for AC 800M\ Integrity Controller
AC 800M HI Extension Update on page 449.
AC 800M Connect VB 800xA Connectivities\800xA for Installer.exe
Graphics Extension AC 800M\AC 800M VB Graphics
Extension
AC 800M Connect 800xA Connectivities\ Installer.exe AC 800M Connect
800xA for AC 800M\ on page 450.
AC 800M Connect
OPC Server for 800xA Connectivities\ Installer.exe OPC Server for AC
AC 800M 800xA for AC 800M\ 800M on page 450.
OPC Server for AC 800M
Control Builder M Engineering & Development\ Installer.exe Control Builder M on
Control Builder M page 451.
Base Software for Engineering & Development\ Installer.exe Base Software for
Soft Control Base Software for Soft Control SoftControl on page
451.
Structured Data Information Management\ Setup.exe
Logger Structured Data Logger
800xA for Advant 800xA Connectivities\ Setup.exe
Master 800xA for Advant Master
800xA for SafeGuard 800xA Connectivities\ Setup.exe
800xA for SafeGuard

446 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A Installation

Table 19. Rollup Installation Information (Install in the Order Listed) (Continued)

Special
Software Path Executable
Instructions
800xA for DCI 800xA Connectivities\ ABB 800xA for 800xA for DCI on
800xA for DCI\800xA for DCI DCI 5.1.01.msi page 452.
800xA Batch for DCI 800xA Connectivities\ ABB 800xA Batch
800xA for DCI\ for DCI 5.1.01.msi
800xA Batch for DCI
800xA for DCI VB 800xA Connectivities\ ABB 800xA for
Graphics Extension 800xA for DCI\ DCI VB6
800xA for DCI Graphics Graphics
Extension 5.1.01.msi
ABB PAS - System 800xA Connectivities\800xA for ABB PAS - 800xA for MOD 300
Services MOD\ABB PAS - System System on page 452.
Services Services.msi
800xA for MOD 300 800xA Connectivities\800xA for ABB MOD300
MOD\ABB MOD300 Connect Connect.msi
ABB 800xA for MOD 800xA Connectivities\800xA for ABB 800xA for
300 VB Graphics MOD\ABB 800xA for MOD 300 MOD 300 VB
Extension VB Graphics Extension Graphics
Extension.msi
TRIO Integration Additional Products\TRIO setup.exe
800xA for Harmony 800xA Connectivities\ ABB 800xA for 800xA for Harmony
800xA for Harmony Harmony 5.1.0 on page 453.
RU1.msi
800xA for Melody 800xA Connectivities\ setup.exe 800xA for Melody on
800xA for Melody page 457.
SoftPoint Server Information Management\ setup.exe
SoftPoint Server
PLC Connect 800xA Connectivities\ setup.exe
PLC Connect\PLC Connect

3BSE036342-510 C 447
Installation Appendix G Update to 800xA 5.1 Rev A

Table 19. Rollup Installation Information (Install in the Order Listed) (Continued)

Special
Software Path Executable
Instructions
IEC 61850 Connect 800xA Connectivities\ setup.exe
800xA for IEC 61850
Asset Optimization Asset Optimization\ setup.exe
Asset Optimization Server &
Client
SMS and e-mail 800xA Core Functionalities\ setup.exe
Messaging SMS and e-mail Messaging
PC, Network and Asset Optimization\ setup.exe
Software Monitoring PC, Network and Software
Monitoring
Multisystem 800xA Core Functionalities\ Setup.exe
Integration Multisystem Integration
SFC Viewer 800xA Core Functionalities\ setup.exe
SFC Viewer
Engineering Studio Engineering & Development\ setup.exe
Engineering Studio
Device Library Device Management & setup.exe Device Library
Wizard Fieldbuses\ Wizard on page 458.
Device Library Wizard
Device Management Device Management & Setup.exe Device Management
FOUNDATION Fieldbuses\ FOUNDATION
Fieldbus FOUNDATION Fieldbus Fieldbus on page
458.
Device Management Device Management & setup.exe
PROFIBUS & HART Fieldbuses\
PROFIBUS & HART
Batch Management Production setup.exe Batch Management
Batch Management on page 459.

448 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A 800xA for AC 800M

Table 19. Rollup Installation Information (Install in the Order Listed) (Continued)

Special
Software Path Executable
Instructions
Process Engineering Engineering & Development\ setup.exe
Tool Integration Process Engineering Tool
Integration
Information Information Management\ Launch.exe Information
Management IM\Autorun Management on
page 459.
RNRP 800xA Core Functionalities\ Setup.exe
RNRP
800xA 800xA Documentation\ABB setup.exe
Documentation1 800xA Instructions for 5.0 SP2
Revision D
System Installer2 System Installer Setup.exe2 Refer to Note 2.
NOTES:
1. Domain Controller nodes only.
2. Applies only to new installations of System Installer. System Installer rollup must be copied to local drive. Setup.exe
only modifies files for the System Verifier Tool.

800xA for AC 800M

Perform the following steps to install the products.

AC 800M High Integrity Controller Update

Firmware for PM865, SM810, and SM811 is available in the system extension
AC800MHIExtension. This extension has to be installed and loaded into the system
using the extension load.
1. Use Windows Explorer to navigate to the path shown in Table 19.
2. Double-click Installer.exe to begin the installation. The Welcome dialog
box appears.

3BSE036342-510 C 449
800xA for AC 800M Appendix G Update to 800xA 5.1 Rev A

3. Read the text in each dialog box for important information concerning steps to
be taken during installation. For normal use, the suggested default settings are
recommended.
4. Click Finish to exit out of the installation.
The versions PM865, SM810, and SM811 in AC 800M Connect must be verified
to be in conformance with the list of certified software combinations mentioned
in Annex 2 of the TÜV Certificate Report (3BSE054960).

AC 800M Connect
1. Use Windows Explorer to navigate to the path shown in Table 19.
2. Double-click Installer.exe to begin the installation. The Welcome dialog
box appears.
3. Read the text in each dialog box for important information concerning steps to
be taken during installation. For normal use, the suggested default settings are
recommended.
4. Click Yes to use the previous product settings instead of the default settings.
(This question only appears when an existing installation exists.)
If 800xA for Advant Master is the clock master in the system, the settings must
be manually entered. Otherwise, the old settings will be lost. Use the Custom
installation and deselect the Time Adapter.
5. Click Finish to exit out of the installation.

OPC Server for AC 800M

1. Record the service account settings in the OPC Server Setup Wizard.
2. Use Windows Explorer to navigate to the path shown in Table 19.
3. Double-click Installer.exe to begin the installation. The Welcome dialog
box appears.
4. Read the text in each dialog box for important information concerning steps to
be taken during installation. For normal use, the suggested default settings are
recommended.

450 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A 800xA for AC 800M

5. Click Yes to use the previous product settings instead of the default settings.
(This question only appears when an existing installation exists.)
6. Click Finish to exit out of the installation.
7. Use the OPC Server Setup Wizard to re-enter the previously used service
account settings.

Control Builder M
1. Use Windows Explorer to navigate to the path shown in Table 19.
2. Double-click Installer.exe to begin the installation. The Welcome dialog
box appears.
3. Read the text in each dialog box for important information concerning steps to
be taken during installation. For normal use, the suggested default settings are
recommended.
4. Click Yes to use the previous product settings instead of the default settings.
(This question only appears when an existing installation exists.)
5. Click Finish to exit out of the installation.

Base Software for SoftControl

1. Use Windows Explorer to navigate to the path shown in Table 19.
2. Double-click Installer.exe to begin the installation. The Welcome dialog
box appears.
3. Read the text in each dialog box for important information concerning steps to
be taken during installation. For normal use, the suggested default settings are
recommended.
4. Click Yes to use the previous product settings instead of the default settings.
(This question only appears when an existing installation exists.)
5. Click Finish to exit out of the installation.

3BSE036342-510 C 451
800xA for DCI Appendix G Update to 800xA 5.1 Rev A

800xA for DCI

If required to update 800xA Batch for DCI along with 800xA for DCI, always
install 800xA for DCI first followed by 800xA Batch for DCI. Do not install
800xA Batch for DCI first or it will be removed when 800xA for DCI is installed.
1. Install 800xA for DCI software rollup.
a. Use Windows Explorer to navigate to the path shown in Table 19.
b. Double-click ABB 800xA for DCI 5.1.01.msi to begin the
installation.
c. Follow instructions as shown in the dialog box to install the 800xA for
DCI.
2. Install 800xA Batch for DCI software rollup.
a. Use Windows Explorer to navigate to the path shown in Table 19.
b. Double-click ABB 800xA Batch for DCI 5.1.01.msi to begin the
installation.
c. Follow instructions as shown in the dialog box to install the 800xA Batch
for DCI.

800xA for MOD 300

1. Install ABB PAS System Services on 800xA for MOD Connectivity Servers:
Perform Step b through Step f on the backup Connectivity Server node first and
then on the primary Connectivity Server node for all Connectivity Server pairs if
ABB PAS System Services was uninstalled as part of the System Revision.
Otherwise, proceed to Step 2.
a. Use Windows Explorer to navigate to the path shown in Table 19.
b. Double-click ABB PAS - System Services.msi to begin the
installation.
c. Select MOD300 Connection for the required installation type.
d. Click Install Now.
e. Click Continue Anyway when the Hardware Installation dialog box
appears.

452 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A 800xA for Harmony

f. Click Finish.
2. Install the 800xA for MOD 300 software with rollup:
Perform Step b through Step f on the backup Connectivity Server first and then
on the primary Connectivity Server for all Connectivity Server pairs.

a. Use Windows Explorer to navigate to the path shown in Table 19.

b. Double-click ABBMOD 300 Connect.msi to begin the installation.
c. The ABB MOD300 Setup dialog box appears. Choose required
installation type (Client or Client/Connectivity Server).
d. Click Install Now. Client is preselected for all nodes types unless PAS
System Services is installed. In that case the MOD 300 Client/Server
install is the default.
e. When the MOD 300 Server Security Setup dialog box appears, enter the
domain\user name and password of the service account (password is case
sensitive) and click OK.
f. Click Finish.
3. Set the passwords for PAS.
a. Open the run prompt and type pasPwdAdmin.exe.
b. Click OK.
c. Enter the domain\user id and password for the service account (password
is case sensitive).
d. Click OK.

800xA for Harmony

Perform the installation on the backup 800xA for Harmony Connectivity Server
node first followed by the primary 800xA for Harmony Connectivity Server node,
and repeat for all 800xA for Harmony Connectivity Server node pairs. Finish by
installing on the Aspect Server and 800xA Client nodes.
1. Stop the following 800xA for Harmony services on the Harmony Server nodes
being updated:

3BSE036342-510 C 453
800xA for Harmony Appendix G Update to 800xA 5.1 Rev A

a. Select:
Start > Control Panel > Administrative Tools > Services
b. Disable the following services:
– Time synchronization daemon.
– SoapSymTagAtomSrv.
– EbDataSyncService.
– EbServerBroker.
– ABBDiagnosticService.
– DD_xxxx - Where xxxx identifies the semAPI or hAPI device being used
(this may or may not exist).
Perform the following steps to disable these services:
– Locate the service in the Services list.
– Double-click the service to open the Properties dialog box of the
corresponding service.
– Change the Startup type to Disabled.
– Click Apply.
– Click OK.
Repeat these steps for each of the services mentioned in Step b.
2. Open Windows Task Manager. Use End Process to stop any of the following
processes that are still running:
– EbDataSyncService
– EbEventConServer
– EbI90Server
– EbServerBroker
– SymOpcServer
– tsyncdd
3. If the 800xA 5.1 post installation step to configure semAPI was executed, this
service needs to be removed to avoid errors when updating system to the latest
revision of 800xA 5.1, as 800xA for Harmony now uses the ABB Automation
hAPI runtime service.

454 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A 800xA for Harmony

a. Execute the following command from Run on the Windows Start Menu or
from a Command Window:
"C:\Program Files\ABB Industrial
IT\SemAPI\EXE\WINNT\DeviceAsServiceU.exe" -u dd_xxxx
Replace the xxxx portion with the text used during Step 4 of the ICI Device
Configuration section of the System 800xA Post Installation (3BUA000156*).
If semAPI was configured, then xxxx represents the semAPI device. If hAPI
was configured, then xxxx represents the hAPI device.
4. Perform this step only on Harmony Connectivity or combined Harmony
Connectivity/Configuration Server nodes.:
a. Uninstall ABB Automation semAPI Runtime using the Programs and
Features application in Windows Control Panel.
b. If ABB Automation hAPI Runtime was previously installed, uninstall it
using the Programs and Features application in Windows Control Panel.
– After uninstallation completes, use Windows Explorer and navigate to the
Program Files\ABB Symphony Plus folder.
– Delete the ABB Symphony Plus folder and its contents.
5. Perform this step only on Harmony Connectivity Server and Harmony
Configuration Server nodes.
a. Use Windows Explorer to navigate to the path shown in Table 19.
b. Double-click InstallSQL2008SP2.bat to install SQL Server 2008
SP2.
6. Use Windows Explorer to navigate to the path shown in Table 19.
7. Double-click ABB 800xA for Harmony 5.1.0 RU1.msi to begin the
installation. The Welcome dialog box appears. Click Next to continue the
installation.
8. Click Next in the following dialog box and then Finish when the installation is
complete.
9. Repeat Step 1 through Step 8 for all Connectivity Server, Configuration Server,
and Aspect Server nodes in the System.

3BSE036342-510 C 455
800xA for Harmony Appendix G Update to 800xA 5.1 Rev A

10. Perform the following on the Connectivity Servers and Configuration Servers
only.
a. Navigate to the following folder using Windows Explorer:
\ABB Industrial IT\OperateIT\Base
b. Double-click SetTimeSyncDACL.bat file on the machine that must be
updated in 800xA System.
11. Perform the following on the Connectivity Servers or Configuration Server
with Connectivity Server nodes only.
a. Install the HarmonyAPI (hAP) runtime service. From a command window,
type the following and then press enter:
ABB-HarmonyAPI30-RuntimeSetup
Click Next to install the HarmonyAPI.
b. Accept the License Agreement and click Next.
c. Ensure to configure Setup Type as Complete and click Next.
d. Once the installation is complete a message appears to restart the machine.
12. Perform this step only on Harmony Connectivity or Harmony Configuration
Server with Connectivity Server nodes:
a. Run the following program via the Windows Start Menu:
Start/ABB Symphony Plus/Engineering/HarmonyAPI/ ABB
Harmony System Configuration Utility.
b. A dialog appears saying a configuration file was not found and one will be
created.
c. Select the Physical ICI Device corresponding to the SCSI device (or Serial
port) that was in use in the running 800xA 5.1 system.
d. Click Apply and then Quit.
13. Start the following 800xA for Harmony services on the Harmony Server nodes
being updated:
a. Select:
Start > Control Panel > Administrative Tools > Services

456 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A 800xA for Melody

b. Enable the following services:

– Time synchronization daemon
– SoapSymTagAtomSrv
– EbDataSyncService
– EbServerBroker
– ABBDiagnosticService
Perform the following steps to enable these services:
– Locate the service in the Services list.
– Double-click the service to open Properties dialog box of the
corresponding service.
– Change the Startup type to Manual.
– Click Apply.
– Click OK.
Repeat these steps for each of the services mentioned in Step b.
14. On one machine that has been updated in the 800xA System, Import the
following afw files:
– HarmonyConnect_6.afw
– HarmonyConnect_7.afw
located in the following path:
Program Files\ABB Industrial
IT\OperateIT\HarmonyConnect\import folder
Ignore any missing dependency or missing aspect warnings encountered.

800xA for Melody

1. Install the software on the 800xA nodes.
a. Use Windows Explorer to navigate to the path shown in Table 19.
b. Double-click startup.exe to begin the installation.
2. Shut down the Melody Tag Importer on the Configuration Server node (Config
Server):

3BSE036342-510 C 457
Device Library Wizard Appendix G Update to 800xA 5.1 Rev A

a. Right-click the Tag Importer icon (traffic light in the notification area on
the far right side of the Taskbar).
b. Select Shutdown Melody Tag Importer.
c. Confirm the shutdown of the Melody Tag Importer by waiting for the
dialog box to appear.
3. Install the software on the Configuration Server node (Config Server).

Device Library Wizard

In the Welcome dialog box, the ABB Device Library Wizard Client check box is
selected by default:
• Leave the Install Device Library Wizard - Client check box selected on all
800xA System nodes.
• Select the Install Device Library Wizard - Server check box on all Aspect
Server nodes only (including redundant Aspect Server nodes).

Device Management FOUNDATION Fieldbus

Click Keep Blocked when the dialog box for the Firewall appears.

Device Management PROFIBUS & HART

When updating from any previous version:
• Select all products except the following:
– ABB PROFIBUS Device Integration Library.
– ABB FDT Base Container.
– ABB HART Device Integration Library.
• Select ABB HART Multiplexer Connect only if it was installed in previous
releases.

458 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A Batch Management

Batch Management
Use this procedure to install Batch Servers (primary and if applicable, secondary),
and Batch Clients. Any differences in the procedures will be noted.
The Batch Primary Server and Batch Secondary Server (if present) must be updated
as a pair with the Batch Primary Server being installed first and then the Batch
Secondary Server.
Install Batch Clients on all nodes in the 800xA System other than the primary and
secondary Batch Server nodes as the Batch Servers already have the Batch Client
installed (by default).
Do not initialize the Batch Runtime database when asked to do so.

The folder containing the setup.exe file must have a path shorter than 115
characters.
1. Use Windows Explorer to navigate to the path mentioned in the Table 19.
2. Double-click setup.exe to begin the installation.
3. Follow the Installation Wizard to complete the installation.

Information Management
Detailed instructions for installing the Information Management rollup are
described as follows:
1. Use Windows Explorer to navigate to the path shown in Table 19.
2. Double-click Launch.exe to begin the installation.
3. Select the Upgrade option. This displays the list of Information Management
components for the selected node type. Components that have checks in both
columns will be removed and then reinstalled by the wizard.
4. Click Upgrade when ready to begin the rollup installation. The wizard will
perform the entire update without requiring any operator input.
5. When the software installation is complete, the Set PAS Service Account
dialog box is displayed. Enter the Service account username and password (and
confirm password) as specified in the Wizard System Software User Settings
dialog box. Click OK.

3BSE036342-510 C 459
Information Management Appendix G Update to 800xA 5.1 Rev A

6. Click Exit when the Install Complete message appears.

7. Click the Close Window button (X) in the top right hand corner of the Restart
Windows dialog box.
DO NOT click Restart Now.

8. Click Exit.

Version Verification
Use the Information Management Version Info tool to verify that the applicable
components have been replaced.
1. To launch the Information Management Version Info tool, select:
Start > Programs > ABB Industrial IT 800xA > Information Mgmt >
Version Info
2. Verify that the component versions shown in the Information Management
Version Info tool for the following components are the same as those shown in
System 800xA 5.1 System Software Versions (3BSE056732*). If the version of
any component does not match, continue to Step 3.
• Application Scheduler
• Calculations
• DataDirect
• Desktop Trends
• Desktop Trends/Client (and /Server)
• Display Services
• History
• ODA Provider
3. Use Windows Explorer to navigate to the path shown in the Table 19 to execute
the IM installation wizard.
4. Double-click Launch.exe to launch the Information Management Installation
Wizard.
5. Click on the installation type that corresponds to the missing component(s) in
this rollup.

460 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A Information Management

6. Continue as necessary to install all components.

Migrating to Oracle 11gR2

Oracle 11gR2 Server software is required for the Information Management
historical services. This procedure is only for IM history servers.
Perform the following procedure to migrate to Oracle 11gR2:
1. Insert the System 800xA 5.1 Revision A Installation Revision DVD into the
DVD drive.
2. Use Windows Explorer to locate and run OracleInstaller.exe in the
following location:
\3rd_Party_SW\Oracle\Oracle11R2
3. If a Windows Security Warning - Open File dialog box appears, click Run to
continue.
4. The Oracle Installer Wizard (Figure 56) containing the following components
appears:
– Oracle (11.2.0.2).
– Oracle CPU Patch 1.
– TNS Listener.

3BSE036342-510 C 461
Information Management Appendix G Update to 800xA 5.1 Rev A

TNS Listener.

Figure 56. Oracle Installer Wizard

The Oracle Server, CPU, and TNS Listener are enabled for installation, by default.
The status for the Oracle components is displayed as shown in Figure 56 for
migrating Oracle 11gR1 to 11gR2.
5. Select the path to install the Oracle Server.
6. Click Migrate to migrate the oracle components.
7. The Prepare for Migration dialog box appears with the following message:
Stop PAS service and PPA to start oracle migration.
Stop the PAS service and PPA to start the Oracle migration.
Click OK to continue.
8. A dialog box appears with the following message:

462 3BSE036342-510 C
Appendix G Update to 800xA 5.1 Rev A Information Management

Are you sure you would like to install the following

Components?
Migrate Oracle 11R1 to 11R2
Critical Patch Update
Oracle TNS Listener
Click Yes to continue.
9. An Information dialog box (Figure 57) appears explaining the actions to be
taken in the following steps. Click OK to continue.

Figure 57. Information Dialog Box

10. The Oracle Installer performs the pre-migration steps and starts to uninstall the
Oracle 11gR1.
11. A Console Window appears with information about uninstallation of
Oracle 11gR1. When the Console Window indicates that the Oracle
uninstallation is complete and displays the message Please press Enter
to exit, press Enter to exit.
12. The Installer starts to install Oracle 11gR2.
13. When the Console Window indicates that the Oracle installation is complete
and displays the message Please press Enter to exit, press Enter to
exit.
14. The CPU installation starts in a Console Window and asks for the following
inputs:

3BSE036342-510 C 463
Information Management Appendix G Update to 800xA 5.1 Rev A

a. E-mail Address/User Name: Enter a Blank address and then Enter to

continue.
b. Do you wish to remain uninformed of Security issues ( [Y] es, [N]o):
Press Y and then Enter to continue.
Perform the actions described in Figure 57.
15. The Console Window indicates Is local system ready for patching.
Press y and then Enter to continue.
The Oracle Database Status indicates that the Oracle 11gR1 database exists.

16. The Installer starts to configure the TNS Listener. The TNS Listener is
configured and running.
17. The Installer runs the post migration steps to migrate the database.
18. A dialog box appears with the following reboot message:
The machine requires a reboot after migration.
Click Reboot Now to reboot the node.
The system must be rebooted manually if Cancel is chosen.

464 3BSE036342-510 C
 Appendix H Online Upgrade Controller Level

Introduction
The information in this appendix is intended only as a high level introduction to the
online upgrade of the controller level. Detailed information appears in the controller
and control software instructions.

Online Upgrade Controller Level

Redundant AC 800M controllers can be upgraded with new firmware versions
online. Online upgrade is initiated from Control Builder by a nine-step wizard.
Refer to the Maintenance and Troubleshooting section in 800xA - Control and I/O,
Basic Control Software, Introduction and Configuration (3BSE035980R*) for more
information.
In order to use online upgrade for the controller level:
• Refer to the Control and I/O, Control Software for AC 800M section of System
800xA Release Notes New Functions and Known Problems (2PAA106188*) for
the controller versions that support online upgrade.
• AC 800M Controllers require the client and server level to be of the same or
higher 800xA System version/revision.
• AC 800M Controllers must be redundant. A redundant controller consists of
two redundant processing units connected to I/O modules or CI modules.
• AC 800M Controller firmware and its CI modules can be upgraded
independently.
– AC 800M controller firmware and the SM810 (safety) CI module must be
upgraded simultaneously.

3BSE036342-510 C 465
Flowchart for Upgrading Controller Level Appendix H Online Upgrade Controller Level

• Different AC 800M Controllers with different 800xA System

versions/revisions can coexist. This allows for extensions of an 800xA System
with new AC 800M Controllers or other new 800xA System functionality
without having to upgrade all existing controllers.
– Starting from 800xA 5.0, upgrading to newer versions of Control Builder
and/or OPC Server does not require a controller upgrade. Controllers with
different firmware versions can coexist in the same network, and newer
versions of Control Builder and OPC Server can connect to controllers of
older versions (not older than 800xA 5.0). Refer to the Control and I/O,
Control Software for AC 800M section of System 800xA Release Notes
New Functions and Known Problems (2PAA106188*) for the controller
versions that support coexistence.
– Hardware types can coexist in different 800xA System versions/revisions
in the same 800xA System.
– Controllers that need to take advantage of new functionality are the only
ones that have to be upgraded. Other controllers can remain untouched.
This backwards compatibility is typically kept for two previous system
versions.
• Upgrading nonredundant AC 800M Controllers is accomplished with
minimized plant disturbance by stopping and upgrading one controller at a
time. The client and server level can still be upgraded online, as long as the
conditions are met for performing an online upgrade on the client and server
level.
Hot swap is the method to be used for a nonredundant AC 800M controller with
redundant CI modules and unchanged controller firmware.

Flowchart for Upgrading Controller Level

Figure 58 shows the upgrade flow for the controller level.

466 3BSE036342-510 C
Appendix H Online Upgrade Controller Level Flowchart for Upgrading Controller Level

T05263A

Figure 58. Online Upgrade Flowchart for Controller Level

3BSE036342-510 C 467
Flowchart for Extending Controller Level Appendix H Online Upgrade Controller Level

Flowchart for Extending Controller Level

Figure 59 shows the flow for extending the controller level to add new AC 800M
Controllers with the latest 800xA System version/revision to an existing plant with
or without upgrading the existing AC 800M Controllers.

T05264A

Figure 59. Flowchart for Extending Plant with New Controllers

468 3BSE036342-510 C
 Index

INDEX
Index
Numerics Archive group associations 300, 421
800xA for AC 870P/Melody Asset optimization
Preparation 87, 149, 219 Post upgrade 122, 189, 265, 352
800xA for Harmony Preparation 89, 151, 221, 293
Preparation 87, 149, 218 Autostart shortcut 134, 201, 277, 375
800xA for MOD 300
Communications configuration tool 120, 187, B
258 Backups 285
OMF 120, 186, 258 Pre-upgrade 61, 78, 139, 142, 207, 211
Preparation 88, 150, 219 Base functions
800xA service user Post upgrade 330
Adding privileges 324 Basic history service
800xA system backup Post upgrade 129, 196, 272, 362
Pre-upgrade 62, 139, 208 Basic history service data
Preparation 97, 159, 229, 305
A Batch
About this book 23 Post update 195
AC 800M Post upgrade 128, 271, 360
Post update 170 Batch management
Post upgrade 103, 250, 343 Preparation 79, 157, 227, 298
Preparation 142, 211, 288 Before 800xA backup
Pre-upgrade 80 External alarm service group 207, 284
Adding privileges to 800xA service user 324
Advant master C
Post upgrade 116, 183, 253, 345 Calculation service
Preparation 291 Preparation 62, 96, 159, 228, 305
Pre-upgrade 84, 86, 116, 147, 148, 182, 216, Calculations
217, 253 Post update 197
Alarm and event handling Post upgrade 130, 274, 371
Preparation 305 Central Licensing System 61, 138, 205, 283
Alarm and event list configurations 277, 372 Communications configuration tool 120, 187, 258
Alarm priority mapping aspects Composite graphic elements 238
Post upgrade 102, 169 Consistency check 285
Pre-upgrade 80 Pre-upgrade 61, 67, 139, 167, 206, 235, 283,
System preparation 142 330, 415

3BSE036342-510 C 469
Control Builder M 132, 199 H
Controller online upgrade 465 Hard disk backup
Pre-upgrade 61, 78, 139, 142, 207, 211
D Harmony
Deploy all user created process graphics 207, 285 Post upgrade 254
Device library wizard 240, 335
Device management and fieldbuses I
Device library wizard 240, 335 IE enhanced security configuration 318
Post upgrade 239, 335 Information Management 325
System preparation 145, 212 Setup 325
System preparation and shutdown 288 Information management
Digital signatures 275, 372 Post upgrade 363, 426
Saving 206, 284 Preparation 158, 197, 228, 274, 300, 421
Display tool 207, 285 Information management maintenance 373, 434
Domain controller 306 Installation
Prerequisites
E Adding privileges to 800xA service user
Engineering Studio 324
Post upgrade 103, 170 IO allocation 261, 348
Engineering studio IT control connection aspects 329
Function designer system extensions
Preparation 81 M
Preparation 89, 144, 151, 220, 293 Melody
Engineering templates 262, 349 Post upgrade 118, 185, 257
Event collectors 276 Memory consumption 37
External alarm service group Minimum hardware requirements 33
Before 800xA backup 207, 284
O
F OMF 120, 186, 258
Firmware memory consumption 37 Online upgrade 59
FOUNDATION fieldbus Online upgrade controller level 465
Post update 179
Post upgrade 112, 247, 340 P
Pre-upgrade 82, 145, 212 PC, network and software monitoring
System preparation and shutdown 288 Post upgrade 127, 193, 270, 357
Function designer 262, 349 Preparation 92, 154, 223, 295
Planning 33
G PLC connect
Group policy management 318 Post update 187

3BSE036342-510 C 470
 Post upgrade 121, 259, 346 PreEvent.dll 292, 347
PreEvent.dll 292, 347 Preparation
Preparation 88, 150, 220, 292 Alarm priority and mapping aspects 142
PreTreat2.dll 88, 150, 220, 292, 347 PreTreat2.dll 88, 150, 220, 292, 347
Post update 163 Pre-upgrade 79
AC 800M 170 800xA system backup 62, 139, 208
Batch 195 AC 800M 80
Calculations 197 Alarm priority mapping aspects 80
FOUNDATION fieldbus 179 Backups 61, 78, 139, 142, 207, 211
PLC connect 187 Consistency check 61, 67, 139, 167, 206, 235,
Process engineering tool integration 198 283, 330, 415
PROFIBUS & HART 178 Engineering studio
Scheduling 198 Function designer system extensions 81
SMS and e-mail messaging 194 FOUNDATION fieldbus 82, 145, 212
Post upgrade 101, 233 Hard disk backup 61, 78, 139, 142, 207, 211
AC 800M 103, 250, 343 Structured data logger 81, 143
Advant master 116, 183, 253, 345 Process engineering tool integration
Alarm priority mapping aspects 102, 169 Post update 198
Asset optimization 122, 189, 352 Post upgrade 131, 275
Asset optimization 265 Preparation 97, 160, 229
Base functions 330 PROFIBUS & HART
Basic history service 129, 196, 272, 362 Post update 178
Batch 128, 271, 360 System preparation 213
Calculations 130, 274, 371 System preparation and shutdown 289
Composite graphic elements 238 PROFIBUS device types
Device management and fieldbuses 239, 335 System preparation 214
Engineering Studio 103, 170 System preparation and shutdown 289
FOUNDATION fieldbus 112, 247, 340
Harmony 254 R
Information management 363, 426 Reconfiguring group displays 102, 169, 239
Melody 118, 185, 257 Reverse Time Synchronization Mode 239
PC, network and software monitoring 127, 193, RTA board
270, 357 Post upgrade 116, 183, 253, 345
PLC connect 121, 259, 346
Process engineering tool integration 131, 275 S
Reconfiguring group displays 102, 169, 239 Safeguard
RTA board 116, 183, 253, 345 Post upgrade 116, 183, 253, 345
Safeguard 116, 183, 253, 345 Preparation 291
Scheduling 131, 274, 371 Pre-upgrade 84, 86, 116, 147, 148, 182, 216,
SMS and e-mail messaging 128, 271, 359 217, 253

3BSE036342-510 C 471
Scheduler service SMS and e-mail messaging 94, 155, 225
Preparation 62, 96, 158, 228, 304 System preparation and shutdown 287
Scheduling AC 800M 288
Post update 198 Advant master 291
Post upgrade 131, 274, 371 Alarm and event list configurations 305
SMS and e-mail messaging Asset optimization 293
Post update 194 Basic history service data 305
Post upgrade 128, 271, 359 Batch management 298
Preparation 94, 155, 225, 296 Calculation service 305
Structured data logger Central Licensing System 283
Pre-upgrade 81, 143 Device management and fieldbuses 288
System backup 135, 201, 278, 285, 375 Engineering studio 293
System checker 307, 308, 310, 315, 317 FOUNDATION fieldbus 288
System configuration console 35 Information management 300
System installer 35 PC, network and software monitoring 295
System language package 36 PLC connect 292
System preparation 142, 211 PROFIBUS & HART 289
800xA for AC 870P/Melody 87, 149, 219 PROFIBUS device types 289
800xA for Harmony 87, 149, 218 RTA board 291
800xA for MOD 300 88, 150, 219 Safeguard 291
AC 800M 142, 211 Scheduler service 304
Alarm priority mapping aspects 142 SMS and e-mail messaging 296
Asset optimization 89, 151, 220 Stopping system services 313
Basic history service data 97, 159, 229 System restore 65, 165, 233, 325
Batch management 79, 157, 227 IT control connection aspects 329
Calculation service 62, 96, 159 System upgrade 138, 205, 306
Calculations service 228
Central Licensing System 61, 138, 205 U
Device management and fieldbuses 145, 212 Upgrade
Engineering studio 144 Prerequisites
Engineering studio IO allocation 89, 151, 220 Group policy management 318
Information management 158, 228, 421 Upgrade Control Builder M projects 132, 199
PC, network and software monitoring 92, 154, Upgrade order 60, 138, 205, 280
223
PLC connect 88, 150, 220 W
Process engineering tool integration 97, 160, Warning and error messages 377
229 Windows firewall 78, 374
PROFIBUS & HART 213 Windows services 374
PROFIBUS device types 214
Scheduler service 62, 96, 158, 228

3BSE036342-510 C 472
3BSE036342-510 C 473
Index

474 3BSE036342-510 C
 Revision History

Introduction
This section provides information on the revision history of this User Manual.
The revision index of this User Manual is not related to the 800xA 5.1 System
Revision.

Revision History
The following table lists the revision history of this User Manual.

Revision
Description Date
Index
- First version published for 800xA 5.1 June 2010
A Updated for Windows 7 Versions Feb 2011
B Updated for 800xA 5.1 Rev A May 2011
C Updated for 800xA 5.1 Feature Pack Aug 2011

3BSE036342-510 C 475
Updates in Revision Index A

Updates in Revision Index A

The following table shows the updates made in this User Manual that were made to
correct supported versions of Windows 7.

Updated Section/Sub-section Description of Update

Section 2, Selecting the Windows Changed the following statement
Operating System from:
800xA System software may be installed on the 32-
bit (x86) US English version of Windows Server 2008
Standard edition with Service Pack 2, or 32-bit (x86)
US English version of Windows 7 Business or
Enterprise edition.
to:
800xA 5.1 System software may be installed on the
32-bit (x86) US English version of Windows Server
2008 Standard or Enterprise edition with Service
Pack 2, or the 32-bit (x86) US English version of
Windows 7 Professional or Enterprise edition.
Windows Server 2008 R2 is not supported.

Updates in Revision Index B

The following table shows the updates made in this User Manual for 800xA 5.1
Rev A.

Updated Section/Sub-section Description of Update

About this User Manual Added the Password Caution in the sub-section
General.
Section 3 Changes updated in the sub-section Redundant
Upgrading 800xA 5.0 SP2 to 800xA 5.1 Aspect Server.
Online

476 3BSE036342-510 C
 Updates in Revision Index B

Updated Section/Sub-section Description of Update

Section 3 Changes updated in the sub-section Information
Upgrading 800xA 5.0 SP2 to 800xA 5.1 Management Server and Central Licensing System.
Online
Section 3 Changes updated in the sub-section Batch
Upgrading 800xA 5.0 SP2 to 800xA 5.1 Management and 800xA for Harmony.
Online
Section 4 Changes updated in the sub-section System
Upgrading 800xA 5.0 SP2 to 800xA 5.1 Upgrade and Central Licensing System.
Offline
Section 4 Changes updated in the sub-section Loading the VB
Upgrading 800xA 5.0 SP2 to 800xA 5.1 Graphics Extensions and 800xA for Harmony.
Offline
Section 4 Changes updated in the sub-section Batch
Upgrading 800xA 5.0 SP2 to 800xA 5.1 Management.
Offline
Appendix B Added new issues.
Control Builder M Compatibility Issues
Appendix H Added the new section.
Update to 800xA 5.1 Rev A
Section 1 Changes done in the sub-section Planning for the
Introduction Upgrade.

Section 5 Changes updated in the sub-section Central

Upgrading 800xA 4.1 to 800xA 5.1 Licensing System.
Offline

3BSE036342-510 C 477
Updates in Revision Index C

Updates in Revision Index C

The following table shows the updates made in this User Manual for 800xA 5.1
Feature Pack.

Updated Section/Sub-section Description of Update

About the User Manual Added a new section Feature Pack describing the
user manual conventions used for indicating the
Feature Pack content.
Minor changes are made in the section.
Section 3 Added the Feature Pack upgrading steps in the sub-
Upgrading 800xA 5.0 SP2 to 800xA 5.1 section Redundant Aspect Server.
Online Feature Pack Icon added.
Section 4 Added the Feature Pack upgrading steps in the sub-
Upgrading 800xA 5.0 SP2 to 800xA 5.1 section System Upgrade.
Offline Removed the Point no.2 (Batch History Archive and
restore) in the sub-section Batch Management.
Feature Pack Icon added.
Section 5 Added the Feature Pack upgrading steps in the sub-
Upgrading 800xA 4.1 to 800xA 5.1 section System Upgrade.
Offline Feature Pack Icon added.

478 3BSE036342-510 C
Contact us

3BSE036342-510 C
ABB AB Copyright © 2003-2011 by ABB.
Control Systems All Rights Reserved
Västerås, Sweden
Phone: +46 (0) 21 32 50 00
Fax: +46 (0) 21 13 78 45
E-Mail: [email protected]
www.abb.com/controlsystems

ABB Inc.
Control Systems
Wickliffe, Ohio, USA
Phone: +1 440 585 8500
Fax: +1 440 585 8756
E-Mail: [email protected]
www.abb.com/controlsystems

ABB Industry Pte Ltd

Control Systems
Singapore
Phone: +65 6776 5711
Fax: +65 6778 0222
E-Mail: [email protected]
www.abb.com/controlsystems

ABB Automation GmbH

Control Systems
Mannheim, Germany
Phone: +49 1805 26 67 76
Fax: +49 1805 77 63 29
E-Mail: [email protected]
www.abb.de/controlsystems

Power and productivity

TM
for a better world