Release Notes - 3BDS007582D101 - Application Builder

Advant® OCS Application Builder
with Master software

Version 4.1/0
Release Notes
3BDS 007 582D101
Use of DANGER, WARNING, CAUTION, and NOTE
This publication includes, DANGER, WARNING, CAUTION, and NOTE information where appropriate to point out safety
related or other important information.
DANGER Hazards which could result in severe personal injury or death
WARNING Hazards which could result in personal injury
CAUTION Hazards which could result in equipment or property damage
NOTE Alerts user to pertinent facts and conditions
Although DANGER and WARNING hazards are related to personal injury, and CAUTION hazards are associated with
equipment or property damage, it should be understood that operation of damaged equipment could, under certain operational
conditions, result in degraded process performance leading to personal injury or death. Therefore, comply fully with all
DANGER, WARNING, and CAUTION notices.
TRADEMARKS
Adobe and Acrobat are trademarks of Adobe Systems Incorporated.
Advant, AdvaCommand, AdvaInform, and AdvaBuild are registered trademarks of ABB Asea Brown Boveri Ltd., Switzerland.
ABB Master, MasterPiece, MasterGate, MasterFieldbus, MasterNet, and MasterView are registered trademarks of ABB Asea
Brown Boveri Ltd., Switzerland.
AdvaSoft, Advant Station, AdvaBuild On-line Builder, Advant Controller, and Advant Fieldbus are trademarks of ABB Asea
Brown Boveri Ltd., Switzerland.
IBM and all IBM-products mentioned in this publication are registered trademarks of International Business Machines Corp.
Microsoft, MS-DOS, Windows, Windows NT and Windows 2000 are registered trademarks of Microsoft Corporation.
NOTICE
The information in this document is subject to change without notice and should not be construed as a commitment by ABB
Automation Products GmbH. ABB Automation Products GmbH assumes no responsibility for any errors that may appear in this
document.
In no event shall ABB Automation Products GmbH be liable for direct, indirect, special, incidental or consequential damages of
any nature or kind arising from the use of this document, nor shall ABB Automation Products GmbH be liable for incidental or
consequential damages arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without ABB Automation Products GmbH’s written
permission, and the contents thereof must not be imparted to a third party nor be used for any unauthorized purpose.
The software described in this document is furnished under a license and may be used, copied, or disclosed only in accordance
with the terms of such license.
Copyright © ABB Automation Products GmbH 2002.

3BSE001264/D
Template: 3BSE001286/E
3BDS 007 582D101

Application Builder Release Notes
Table of Contents
TABLE OF CONTENTS
Chapter 1 - Introduction
1.1 Executive Summary................................................................................................. 1-1
1.2 How to Use This Document..................................................................................... 1-1
1.3 Version Designation................................................................................................. 1-1
1.4 Revision Record....................................................................................................... 1-2
1.5 Compatibility ........................................................................................................... 1-3
1.6 Restrictions .............................................................................................................. 1-4
1.7 Related Documentation............................................................................................ 1-4
Chapter 2 - Functionality
2.1 New Functions ......................................................................................................... 2-1
2.1.1 Stand alone and Integrated...................................................................... 2-1
2.2 Discontinued and Replaced Functions and Units .................................................... 2-3
2.3 Fixed Problems ........................................................................................................ 2-3
2.3.1 Stand alone.............................................................................................. 2-3
2.3.1.1 Attach of existing Node, TC or CI ................................... 2-3
2.3.2 Integrated in Industrial IT ....................................................................... 2-3
2.3.2.1 Update FCB Version does not work for Node/CI/TC
if no ODB exist ................................................................ 2-3
2.3.2.2 APB loops in special situation after Modify Tool Version
with automatic Update Version ........................................ 2-4
2.3.2.3 Name of copied Node, TC or CI is not added to .DAT
file .................................................................................... 2-4
2.4 Known Problems and Work Arounds ...................................................................... 2-4
2.4.1 Stand alone.............................................................................................. 2-4
2.4.1.1 Editing .TIX or .TBX files with AS100-EDIT ................ 2-4
2.4.1.2 Update FCB Data of Nodes Containing Only DB or Only PC
Part ................................................................................... 2-4
2.4.2.1 Unexpected Termination of Plant Explorer...................... 2-5
2.4.3 Integrated in Advant Engineering Workplace......................................... 2-5
2.4.3.1 Generate Source in Generate DB or Update Parameter with
View Function Chart ........................................................ 2-5
2.4.3.2 Print / Print to File on Type Circuit and Circuit Aspect... 2-6
2.4.3.3 Terminate Structure Builder / Application Builder Stays in
Memory ............................................................................ 2-6
2.4.3.4 Generate DB / Function Chart Builder Stays in Memory 2-6
2.4.3.5 Progress Indication for Generate DB, Update Parameter and
Initialize ........................................................................... 2-6
3BDS 007 582D101 i

Table of Contents
2.4.3.6 Unnecessary Type Circuit Copies if Copying Objects

Between Projects (SR0058).............................................. 2-7
2.5 Recommendations .................................................................................................... 2-7
2.5.1 Installation............................................................................................... 2-7
2.5.1.1 Usage of Default Installation Directories ......................... 2-7
2.5.1.2 Environment Variable ADVABLDENV........................... 2-7
2.5.2 Stand Alone............................................................................................. 2-7
2.5.2.1 National Characters .......................................................... 2-7
2.5.3.1 National Characters .......................................................... 2-8
2.5.4 Integrated in Advant Engineering Workplace ......................................... 2-8
2.5.4.1 Environment Variable SWAP$DIR .................................. 2-8
2.5.4.2 Environment Variables TMP and TEMP.......................... 2-8
2.5.4.3 Environment Variables TC$LEV1 and TC$LEV2........... 2-8
2.5.4.4 Logfile / Unattended Operation for Update Parameter,
Generate DB, Initialize, Locate Circuit............................ 2-8
2.5.4.5 Configuring a Process Object for a Library ..................... 2-9
2.5.4.6 Configuring an Object for a Library to Create DB Elements
by Drag and Drop or Locate Circuit............................... 2-10
2.5.4.7 New Objects with DB Element or Circuit Aspects ........ 2-10
2.5.4.8 Configuring an Object for a Library to Create DB Elements
by Generate DB .............................................................. 2-11
2.5.4.9 Case Insensitive Instance Symbols................................. 2-11
2.5.4.10 Free Parameter Aspect Description ................................ 2-11
2.5.4.11 Parameter Reference to Absolute Reference Designation of
Function Structure .......................................................... 2-11
2.5.4.12 Setting Options for Bulk Copy From Library ................ 2-11
2.5.4.13 Prepare Generate DB...................................................... 2-12
2.5.4.14 Function Chart Builder Stays Visible During Commands2-12
2.5.4.15 Drag and Drop or Locate Circuit for Objects with
DB Circuit Aspects......................................................... 2-12
2.5.4.16 Drag and Drop Multiple Objects .................................... 2-13
2.5.4.17 Update of Dependent Symbols of TC Instances in
Node Mode ..................................................................... 2-13
2.5.4.18 Switch off Symbol Substitution in Function Chart Builder
Circuit Mode................................................................... 2-13
2.5.4.19 Options to Switch off Update of Symbols and
TC Connections .............................................................. 2-13
2.5.4.20 Unattended Operation..................................................... 2-14
2.5.4.21 DBElement Aspect Copied From Library...................... 2-15
2.5.4.22 Multiuser Operation - SR 9077 ...................................... 2-15
ii 3BDS 007 582D101

Table of Contents
2.5.4.23 Procedure for Alternating Use of Cooperating Mode and

Independent Mode
(SR 0075) ....................................................................... 2-15
Chapter 3 - Installation
3.1 Installation ............................................................................................................... 3-1
3.2 Upgrading ................................................................................................................ 3-1
3.3 Backup and Restore ................................................................................................. 3-2
3.4 Un-install ................................................................................................................. 3-2
Chapter 4 - Miscellaneous
4.1 System Specification................................................................................................ 4-1
3BDS 007 582D101 iii

Table of Contents
iv 3BDS 007 582D101

Section 1.1 Executive Summary
Chapter 1 Introduction
1.1 Executive Summary

This Release Note contains information about Application Builder (APB) running on
Windows NT 4.0 and Windows 2000. Application Builder creates and administers the
environment for the other control configuration tools Function Chart Builder, Bus Configuration
Builder, and On-line Builder.
Application Builder is used for Advant OCS project and data administration. It assists you when
working as a team on a project because you can store your data on a central server and the local
hard disk.
For more information about Application Builder refer to Section 2.1, New Functions.
For installation of Application Builder see Section 3.1, Installation.
1.2 How to Use This Document

It is recommended that you first read through this introduction and the installation procedure in
the Control Builder A Configuration Release Notes. Then perform the installation of
Application Builder.
1.3 Version Designation

Application Builder of version 4.1/0 is included in Control Builder A
of version 1.1/0.
3BDS 007 582D101 1-1

1.4 Revision Record

The following version has been produced:The following versions were produced earlier:
Table 1-1. Current Version
Version Release Date Remarks

APB*4.1/0 08-Mar-2002 32-bit version for Windows NT and
Windows 2000;
New functions:
- support of long Type Circuit and
Circuit names
Table 1-2. Earlier Versions

APB*2.0 31-Mar-1995 First Version of Application Builder
APB*2.1 15-Dec-1995 2nd Version of Application Builder
APB*2.2 15-Apr-1996 Changes in address handling for
nodes, some error corrections.
APB*2.3 14-Feb-1997 New functions (File | Concatenate,
Help | On Project, etc. ) and error
corrections.
APB*2.4/0 12-Dec-1997 First Windows NT version of
Application Builder. Integration of
Application Builder into Advant
Engineering Workplace.
APB*2.5/0 03-Apr-1998 2nd Windows NT based version of
Application Builder. Bus
Configuration Builder startup
changed, error corrections, some
other additions.
APB*2.6/0 26-Feb-1999 New functions: Support of right
mouse button, Retrieve Application,
Function Chart Builder Libraries
(export/import).
APB*2.7/0 14-JAN-2000 New functions: automatic upgrade of
FCB data; support of long project
root names and UNC path as root
1-2 3BDS 007 582D101

Section 1.5 Compatibility
Table 1-2. Earlier Versions

APB*3.0/0 11-Aug-2000 32-bit version for Windows NT and
Windows 2000, New functions:
extended view for ONB application
dumps (AD) and more options for
work in cooperating mode with
Advant Engineering Workplace
APB*4.0/0 09-Apr-2001 32-bit version for Windows NT and
Windows 2000;
New functions:
- Node-, TC- and CI-list with MS-
Explorer-like column configuration,
sorting, and sizing support,
- sort Source Code Files by name or
modification data,
- support for source code file
generated by FCB with long
filenames
1.5 Compatibility
Application Builder 4.1/0 supports:
• Function Chart Builder <= 6.1/0
• Bus Configuration Builder 3.0/0
• On-line Builder 3.0/0
Application Builder 4.1/0 requires Eingineering Studio 1.1/0 when running integrated in
Industrial IT.
Application Builder 4.1/0 requires Structure Builder 3.2/0 when running in integrated in Advant
Engineering Workplace.
Application Builder 4.1/0 is compatible with earlier versions of Application Builder when
working stand alone. Older versions of Function Chart Builder, Bus Configuration Builder, and
On-line Builder are also supported by this Application Builder version.
Application Builder 4.1/0, more exactly Bus Configuration Interface 3.0/1, automatically
converts and upgrades any Bus Configuration Database generated by Application Builder >=
2.6/0, Bus Configuration Builder >= 2.5/2, and Function Chart Builder >= 4.5/2.
• ACC 1.5/2 components (BCB 2.5/2, FCB 4.5/2) create BCD version 1.0.
• ACC 1.6/1 components (APB 2.6/0, BCB/BCI 2.6/0, FCB 4.6/1) create BCD version 1.1.
3BDS 007 582D101 1-3

• CBA 1.0/0 components (APB 4.0/0, BCB/BCI 3.0/0, FCB 6.0/0) create BCD version 1.2.
• CBA 1.1/0 components (APB 4.0/0, BCB 3.0/0/BCI 3.0/1, FCB 6.0/0) create BCD version
1.2.
As a consequence, if the Bus Configuration Database and/or the project is located on a network
drive and accessed by different client PCs, for example, an CBA 1.0/0 client, an ACC 1.6/1
client, and an Advant OPC Server for Advant Fieldbus 100 1.0 or 1.1 client, you may get
“Invalid BCD version” message after upgrading the BCD by access of APB, BCB, or FCB of
CBA 1.0, more exactly by access via Bus Configuration Interface 3.0/0 (BCI 3.0/0).
The reason for the error message is that ACC 1.6/1 and Advant OPC Server for Advant Fieldbus
100 1.0 and 1.1 use an older BCI and an older BCD version. So you have to upgrade also the
client PCs running ACC 1.6/1 and Advant OPC Server for Advant Fieldbus 100 1.0 and 1.1:
• Install CBA 1.1/0, but at least BCB 3.0/0 on them. This is the easy way.
• Or install at least BCI 3.0/1 on them.
At the same time, no upgrade of FCB 4.6/1, FCB 4.7/0, FCB 5.0/0 or FCB 6.0/0 nodes is
necessary to FCB 6.1/0: The Bus Configuration Database can contain bus configuration data
(nodes) generated by FCB 4.6/1, FCB 4.7/0, FCB 5.0/0, FCB 6.0/0 and FCB 6.1/0.
1.6 Restrictions
Not applicable.
1.7 Related Documentation
Table 1-3. Valid Manuals
Document Ordering no.

Application Builder User’s Guide 3BDS100560R301
Control Builder A Commands 3BDS100498R301
for Structure Builder User’s Guide
1-4 3BDS 007 582D101

Section 2.1 New Functions
Chapter 2 Functionality
2.1 New Functions

Application Builder can run in the following modes:
• Stand alone
Run Application Builder without Industrial IT or Advant Engineering Workplace. Creation
of Advant objects is not supported.
• Integrated in Industrial IT
Run Application Builder via Industrial IT. Engineering Studio Workplace is used for
navigation. Creation of Aspect objects is supported.
The functions available integrated in Industrial IT are described in the Control Builder A
Interface Book.
• Integrated in Advant Engineering Workplace
Run Application Builder via Advant Engineering Workplace. Structure Builder is used for
navigation. Creation of Advant objects is supported.
The functions available integrated in Advant Engineering Workplace are described in the
Control Builder A Commands for Structure Builder User’s Guide.
2.1.1 Stand alone and Integrated

Starting with APB 4.1 Type Circuit an Circuit names an have a length of 27 characters.
Type Circuit an Circuit with names longer than 8 character cannot be used in former versions of
APB and FCB.
During File > Convert the Type Circuit an Circuit names are shorten to 8 characters for use in
ONB.
3BDS 007 582D101 2-1

Figure 2-1. Convert of long Type Circuit names
2-2 3BDS 007 582D101

Section 2.2 Discontinued and Replaced Functions and Units
2.2 Discontinued and Replaced Functions and Units

There were no discontinued or replaced functions, nor such units.
2.3 Fixed Problems
2.3.1 Stand alone
2.3.1.1 Attach of existing Node, TC or CI

It’s possible to attach existing node, TC or CI to the Node List, Type Circuit List or Circuit List.
Example for Type Circuit:
• Copy an INI and a TCS file to the TCDATA directory
• Start APB New Type Circuit Dialog
• Specify the name of the TCS file as new Type Circuit and select OK
Result: The message “The name tcname already exists. Do you want attach?” appears. The TC
name can be attached and is added to Type Circuit List.
This is also the case for node and circuit.
This has been corrected.
2.3.2 Integrated in Industrial IT
2.3.2.1 Update FCB Version does not work for Node/CI/TC if no ODB exist
In case File > Update FCB data > Project.. or File > Update FCB data > Selected is
performed for Node/CI/TC this action don’t work if no ODB exists. The INI file is not changed
not changed.
The action will terminate is terminated with the message “successful, no errors no warnings”
but when you now check the INI files, the OLD FCB version is still stored there. Thus, when
you start FCB on this node you will the following message from APB:
“Starting Node/Circuit/TC was processed with FCB version, newer version available”
The error is independent whether the older FCB version is installed or not, and is independent
whether source code exists already or not.
Normally you will have ODB files for Node, Circuit and Type Circuit but for the CBA Object
Type Library only the TCS files and the INI files will be delivered. Thus, when you need to
upgrade the FCB version for an existing EngineerIT system you will run into trouble.
This can be circumvented by selecting "Modify Tool Version ..." for each Node/CI/TC and
select the new FCB version.
3BDS 007 582D101 2-3

2.3.2.2 APB loops in special station after Modify Tool Version with automatic Update
Version
APB loops when started out of CBA Interface to automatic update the FCB Version of a
Node/Circuit/TypeCircuit within the "More..." Dialog.
Situation when the problem occurs:
• Create object with Circuit Aspect in EngineerIT
• Select Circuit Aspect and Attach a Circuit
• Select Expert Page
• Press Summary Form --> More... -->Tool Versions --> Select FCB version
• --> Check Automatic Update of FCB Data --> OK --> OK ==> LOOP
2.3.2.3 Name of copied Node, TC or CI is not added to .DAT file

Case a "well-tested" TC shall be added to ABB Industrial IT Engineer IT System the following
steps has to be performed:
• Copy an INI and a TCS file to the TCDATA directory
• Start APB New Type Circuit Dialog
• Specify the name of the TCS file as new Type Circuit and select OK
Result: The new Circuit is not added to the the corresponding .DAT file.
This is also the case for node and circuit.
2.4 Known Problems and Work Arounds
2.4.1 Stand alone
2.4.1.1 Editing .TIX or .TBX files with AS100-EDIT

Such files should not be modified with an editor as they are generated by Function Chart
Builder. We recommend not to edit these files, as the syntax of generated files is subject to
change without notice. AS100-EDIT replaces CHAR(2) in TIX-files by CHAR(32) (blank).
Use NOTEPAD or another editor to edit these files.
2-4 3BDS 007 582D101

Section 2.4.2 Integrated in Industrial IT
2.4.1.2 Update FCB Data of Nodes Containing Only DB or Only PC Part

The automatic update of FCB data of nodes containing only DB or only PC part, for example,
an AdvaSoft node, fails in the following cases depending on the FCB version:
Table 2-1.
Update from => to FCB

Source Code Part OK/Fails
Version
only DB 4.6/1 => 4.7/0, 5.0/0, 6.0/0 fails
only DB 4.7/0 => 5.0/0, 6.0/0 ok
only DB 5.0/0 => 6.0/0 ok
only PC 4.6/1 => 4.7/0, 5.0/0, 6.0/0 fails
only PC 4.7/0 => 5.0/0, 6.0/0 fails
only PC 5.0/0 => 6.0/0 fails
Work Around
Upgrade manually, see Application Builder User’s Guide.
Or create a dummy PC or DB section, respectively, in Function Chart Builder before choosing
File | Update FCB Data | … command.
2.4.2.1 Unexpected Termination of Plant Explorer

If Plant Explorer crashes, the Application Builder and the Function Chart Builder may still be
locked in memory.
Work Around
Close all open Application Builder and Function Chart Builder instances. Use the Task
Manager’s button End Process of the Processes tab to terminate any APB32.EXE and
FCB32.EXE task that is still running.
2.4.3 Integrated in Advant Engineering Workplace
2.4.3.1 Generate Source in Generate DB or Update Parameter with View Function Chart
Generate circuit source code included into Generate DB or Update Parameter with view
Function Chart does not work if Function Chart Builder is started interactively via Open on
view Function Chart.
Work Around
3BDS 007 582D101 2-5

Either use File | Generate Source in Function Chart Builder or use Options | Preferences |
Generate Source Code on Exit in Function Chart Builder, or perform the commands without
having started Function Chart Builder interactively before.
2.4.3.2 Print / Print to File on Type Circuit and Circuit Aspect

The Print command with option Print to File on type circuit and circuit aspects tries to store
the print files erroneously in the <project>\NODES\PR_TC\TCDATA\LIST resp.
<project>\NODES\PR_CI\CIDATA\LIST subdirectory instead of the corresponding LIST
subdirectory in parallel to TCDATA resp. CIDATA. This don’t work and the error message
“<print filename> is not a valid filename” is displayed.
Work Around
Create the subdirectory <project>\NODES\PR_TC\TCDATA\LIST resp.
<project>\NODES\PR_CI\CIDATA\LIST and print again.
2.4.3.3 Terminate Structure Builder / Application Builder Stays in Memory

If Structure Builder has been terminated unexpectedly or manually via Task Manager and you
start it again then a message like “APB is started already. Please close this APB” may be
displayed even though Application Builder was not started explicitly when issuing certain
commands.
Work Around
Use the Task Manager’s button End Process of the Processes tab to terminate APB32.EXE and
repeat the command you tried to issue before.
2.4.3.4 Generate DB / Function Chart Builder Stays in Memory

If Generate DB is the very first command issued for a DBSection aspect of a node (View Node
Function Chart), which has no default page setup, then the Page Setup dialog of Function
Chart Builder pops up and a message box that states “FCB is locked. Please try again later”.
If the message box is confirmed before the Page Setup dialog is confirmed, Function Chart
Builder stays in memory and a next try to open View Node Function Chart leads to the error
message “Cannot run Function Chart Builder twice” even though Function Chart Builder is not
visibly started.
The Generate DB command is not performed even though a message states success.
The same behavior exists for Generate DB with View Function Chart.
Work Around
Either confirm the Page Setup dialog first or – if the situation described above is already there –
terminate FCB32.exe with Task Manager’s button End Process of the Processes tab.
After the node has got a default page setup, repeat the Generate DB command.
2-6 3BDS 007 582D101

Section 2.5 Recommendations
2.4.3.5 Progress Indication for Generate DB, Update Parameter and Initialize
The commands Generate DB, Update Parameter and Initialize regularly show a begin query
message and a final success message. In between only the wait cursor is shown.
Work Around
Perform these commands with Function Chart Builder started up and the corresponding
Function Chart Builder window opened. Then you can see that actions are going on. Further you
see in Function Chart Builder’s status bar that it processes OLE operations.
2.4.3.6 Unnecessary Type Circuit Copies if Copying Objects Between Projects (SR0058)
If you copy or import an Advant object having a Type Circuit aspect from a library project to a
work project, then the type circuit file of the corresponding aspect in the library project will be
copied instead of being referenced. In case that you copy or import such an Advant object a lot
of times you will get a lot of unnecessary type circuit file copies with new file names in the
project local TC-directory of the work project. Furthermore you become decoupled from type
circuit changes in the library project.
Work Around: None
2.5 Recommendations
2.5.1 Installation
2.5.1.1 Usage of Default Installation Directories

Prefer the installation root directories suggested at the installation.
Versions Suggested Installation Root Directory
Application Builder, drive:\AdvaBNT
Function Chart Builder,
and so on
where drive=C, D, …
2.5.1.2 Environment Variable ADVABLDENV

If you are not using the default directory C:\Advabldenv as a local configuration directory,
the setup program sets the ADVABLDENV environment variable as a system environment
variable. It is recommended not to change the value for that directory once set.
3BDS 007 582D101 2-7

2.5.2 Stand Alone
2.5.2.1 National Characters

When creating a project you can specify the national character setting. This setting cannot be
changed once the project is created. If you want to see which national characters you specified
for the project, use the Help | On Project dialog.
Work Around
If you want to change the national character setting create a new project. Then, copy the nodes,
circuits and type circuits – if there are any – from the old project to the new project.
2.5.3.1 National Characters

When loading the system extension for the Control Builder A, the Configuration Wizard will
popup the New Project dialog. Make sure to specify the correct national character settings. You
can not change the national character settings afterwards.
2.5.4 Integrated in Advant Engineering Workplace
2.5.4.1 Environment Variable SWAP$DIR

The SWAP$DIR environment variable allows to direct Function Chart Builder’s swap file to a
specific directory other than the node-, circuit- or type circuit directory on the server used by
default.
If used the SWAP$DIR environment variable must be a system environment variable.
It is recommended to set this environment variable to a local directory on the client PC to speed
up the Generate DB, Update Parameter and Initialize commands.
2.5.4.2 Environment Variables TMP and TEMP

The environment variables TMP and TEMP should be system environment variables. Otherwise
temporary files may be written to the WINNT directory.
2.5.4.3 Environment Variables TC$LEV1 and TC$LEV2

For using type circuits of the Advant Object Library for Advant Controllers (object library)
project the environment variable TC$LEV1 is set by the setup program of object library.
Example:
2-8 3BDS 007 582D101

Section 2.5.4 Integrated in Advant Engineering Workplace
TC$LEV1=L:\DATA\LIB11R0\NODES\PR_TC\TCDATA
If you want to reference type circuits in a second library project, set TC$LEV2 accordingly as a
system variable written in uppercase letters.
Example:
TC$LEV2=L:\DATA\EX_LIB2\NODES\PR_TC\TCDATA
2.5.4.4 Logfile / Unattended Operation for Update Parameter, Generate DB, Initialize,
Locate Circuit
To trace results of parameter references and to control unattended operation of the Update
Parameter, Generate DB, Locate Circuit and the Initialize command and the Update
Parameter sequence included into Drag & Drop, two options can be switched on or off by
editing the apb.ini file stored in the ADVABLDENV directory:
...
[SetApbMessage]
PrintLogFile=1 (to write logfile information for one command execution)
or
PrintLogFile=2 (to append logfile information for all following command
executions)
or
PrintLogFile=0 (to switch off)
The logfile is named parfcb.log and was stored in the ADVABLDENV directory in former
versions of APB, beginning with APB 2.7 it is stored on the TEMP directory.
In case of errors the commands show intermediate error message boxes that pause operation as
they have to be confirmed.
To switch off these messages the option
BatchMode=1 has to be set.
To switch off batch mode set BatchMode=0
Beginning with APB 2.7, the options are set by default as follows:
PrintLogFile=2
BatchMode=1
So in most cases there is no need to edit the file.
2.5.4.5 Configuring a Process Object for a Library

1. Configure the type circuit. Use allowed parameter references.
3BDS 007 582D101 2-9

Make sure that the actual values of symbols are supplied either by default values or by
parameter references.(Actual values supplied during instantiation into the circuit or by
editing symbol values in the TC instances will get lost in Drop and Update Parameter).
For symbol controlled default connections of output terminals to DB element terminals
make sure that the = sign is outside of any symbol used in the default connection
specification.
2. Configure the circuit aspect.
a. Introduce the circuit instance symbol finstance
b. Begin the circuit of this aspect with a FUNCM (or another structure element) and
give this element an instance name defined by the circuit’s instance symbol finstance
(INAME <finstance>).
c. Into the circuit below the structure element instantiate the type circuit(s). Make sure
before you instantiate that the symbol substitution in Function Chart Builder circuit
mode is switched off.
Note that the TC instances do not need to get an instance name. Instance names are given to the
TC instances below the structure element automatically.
Note that the declaration length of the finstance symbol must fit to the length of its contents
generated from basic property name of category Customer ID concatenated with _ (underscore)
and the aspect description of the Circuit aspect.
Note that you can also configure a circuit without using a structure element. Then only one TC
instance is allowed and this TC instance has to get the instance name <finstance>.
If the process object shall be used with the Locate Circuit command, then it must be placed in
the OCS Structure below the node object it will be inserted into, and the relative reference
designation entry in the OCS Structure aspect of the process object must contain the PC item
designation of the insertion point PC element in the node.
2.5.4.6 Configuring an Object for a Library to Create DB Elements by Drag and Drop or
Locate Circuit
1. Configure the DB type circuit. For rules, except the connection-related ones (DB and PC
connections), see Section 2.5.4.5, Configuring a Process Object for a Library.
2. Configure the Circuit aspect.
a. Introduce the circuit instance symbol finstance.
b. Instantiate the DB type circuit into the circuit using an instance name defined by the
circuit’s instance symbol finstance (INAME <finstance>).
Note that only one DB type circuit instance is supported regarding parameter update.
2.5.4.7 New Objects with DB Element or Circuit Aspects

Before new objects with DBElement aspects or Circuit aspects can be inserted into a node
object using Generate DB, Drag and Drop, or Locate Circuit, Function Chart Builder has to be
started once on the Node Control Software aspect with the Open command and View Node
2-10 3BDS 007 582D101

Function Chart, so that Function Chart Builder recognizes the new items. Or, you can use the
Function Chart Builder menu item File | Rebuild Element Types before starting to insert.
Otherwise error messages like “Symbol context for circuit ... cannot be built. Make sure that a
correct circuit file exists.” occur.
Generate DB can be used without having started Function Chart Builder interactively before, as
Function Chart Builder is started invisibly and ended automatically by this command.
2.5.4.8 Configuring an Object for a Library to Create DB Elements by Generate DB

1. Configure the DB type circuit. For rules, except the connection-related ones (DB and PC
connections), see Section 2.5.4.5, Configuring a Process Object for a Library.
2. Configure the DBElement aspect by attaching the type circuit or/and editing it.
Note that instance naming for the DB type circuit instance is done automatically when using the
DBelement aspect.
2.5.4.9 Case Insensitive Instance Symbols

The predefined instance symbols finstance, binstance, sinstance can be written in upper or lower
or mixed case in the type circuit definition.
2.5.4.10 Free Parameter Aspect Description

A Parameter aspect’s description does not need to end with the string “Parameter” as the default
parameter aspect type descriptions do. Therefore a free description is possible. Of course when
used in a parameter reference in a type circuit the aspect description part of the reference
specification must exactly match the description contents of the parameter aspect description.
2.5.4.11 Parameter Reference to Absolute Reference Designation of Function Structure

An additional parameter reference to the absolute reference designation of the Function
Structure is supported to be used in type circuits.
Syntax: $$REF.= Function Structure.ABS
The absolute reference designation string is supplied without prefix and without separators. It
can, for example, be used for naming DB elements.
2.5.4.12 Setting Options for Bulk Copy From Library

Before doing a bulk copy of objects from library project to another destination project (e.g.
before import or before performing manually a copy with multiple selection), set the following
options for the target project by using the Set Options command on the destination project’s
Project OCS Defaults aspect:
• Bulk Data
• Generate TC Name
• Generate CI Name
3BDS 007 582D101 2-11

• Generate Node Name.

This switches off the Copy dialog for the aspects owned by Application Builder during the bulk
copy process and generates file names automatically.
Switching on the Generate Name options is only needed if the destination project already
contains instances with the same file names as in the source project.
If you copied between projects without having switched on the corresponding Generate Name
option, you should not copy the same objects again without either switching off the Bulk Data
option or switching on additionally the Generate Name option. Otherwise an error message is
displayed, caused by the fact that the objects already exist in your project. The same applies to
trying to copy within the project with only the Bulk Data option switched on.
2.5.4.13 Prepare Generate DB

Generate DB takes a certain time, e.g. about 5 minutes for 100 DBElement aspects.
In order to reduce the time, check that in the OCS Structure all the following conditions are
fulfilled before executing the Generate DB command:
• The relative reference designations for the OCS Structure aspect of all objects including
the node object are set.
• The == prefix is set in the OCS Structure aspect for all objects.
• For all channel objects the < control for the relative reference designation is set in the OCS
Structure aspect.
• The relative reference designation entered into the OCS Structure aspect of the board and
channel (and other DB element related) objects result in valid item designations for the DB
elements.
Note that the relative reference designation entries used to construct the item designation must
not contain dots. The separating dots are supplied by the generation mechanism for the absolute
reference designation in Structure Builder.
For board objects copied from the Advant Object Library for Advant Controllers the channels
already contain the right entries.
2.5.4.14 Function Chart Builder Stays Visible During Commands

During execution of Generate DB, Update Parameter and Initialize commands the Function
Chart Builder can stay visible on the screen if it is started on the node or circuit, that is, the
destination for these commands.
While the command is executed, the Function Chart Builder’s menus cannot be used, but
Function Chart Builder’s windows are updated with the command results.
2.5.4.15 Drag and Drop or Locate Circuit for Objects with DB Circuit Aspects
Besides drag and drop for circuits that have a PC part, drag and drop for circuits that have a DB
part only is supported, too.
2-12 3BDS 007 582D101

Parameter update for such circuits is supported if they have one DB type circuit instance that
gets its instance name via a circuit symbol named finstance (INAME <finstance>).
Allowed drop destination for DB circuits currently is a PC element in the Tree or the Function
Chart window of Function Chart Builder.
If the object shall be used with the Locate Circuit command, then it must be placed in the OCS
Structure below the node object it will be inserted into, and the relative reference designation
entry in the OCS Structure aspect of the process object must contain a PC item designation of a
PC element of the node.
2.5.4.16 Drag and Drop Multiple Objects

You can select multiple objects containing a Circuit aspect and drag and drop them in one action
into the node in Function Chart Builder.
Objects not having a Circuit aspect can be included into the selection. They are skipped during
drop automatically.
If the selection includes objects with Circuit aspect that already have been dropped (inserted)
insertion stops with the first already inserted object.
2.5.4.17 Update of Dependent Symbols of TC Instances in Node Mode

The Update Parameter command by default updates dependent symbols, too.
As this is done by switching the symbol values of the type circuit instance to default values and
then updating the parameters, the designer of the type circuit has to take care that all symbols,
a dependent symbol depends on, get their values from valid default values or constants or
parameter references.
Note that
• symbol values entered during type circuit instantiation into the circuit,
• edited symbol values of the instantiated type circuit,
• values of symbols that have parameter references that cannot be executed,
• values of symbols that have parameter references that point to empty attributes of
parameter aspects
are overwritten during update via the Update Parameter command.
See Section 2.5.4.18, Switch off Symbol Substitution in Function Chart Builder Circuit Mode
for a possibility to switch off update dependent symbols.
2.5.4.18 Switch off Symbol Substitution in Function Chart Builder Circuit Mode
If you check Substitute Symbols in Default Connections of TC/CI Terminals via the
Function Chart Builder’s Options | Preferences menu command, the symbol substitution for
type circuit instantiation in circuit mode is switched off. This enables the configuration of
3BDS 007 582D101 2-13

circuits especially for library objects without the need to re-introduce the original symbol values
of instantiated type circuits in circuits.
2.5.4.19 Options to Switch off Update of Symbols and TC Connections

By default the Update Parameter command supports the update of
• Dependent symbols and
• Default TC connections and DB References created by TC.
It is possible to switch off for a project the update of dependent symbols and the update of TC
connections and DB References created by TC in the Update Parameter command using the
More | Set Options | Defaults command with the Set Options dialog.
This allows to avoid on project level that
• Changes done on circuit level for symbol values of TC symbols without parameter
references or having parameter references, that cannot be executed or point to empty
parameter aspect attributes, are overwritten with default values by Update Parameter and
• Manually created TC connections and DB References are overwritten by the Update
Parameter command.
Before performing updates the Update Parameter command displays the current settings and
allows to cancel if the settings do not fit to the current needs.
The settings can be changed
• either (this is recommended) via the Set Options dialog
• or in the [EOOptions] section of the <projectname>.ini file:
NotUpdateDependentSymbols=0; Default, update of dependent symbols switched on
or
NotUpdateDependentSymbols=1 ;Update of dependent symbols switched off
and
NotUpdateTCConnections=0; Default, update of TC connections switched on
or
NotUpdateTCConnections=1;Update of TC connections switched off
Starting with ACC 1.7 (FCB 4.7) switching off update of TC terminal connections to prevent
overwriting manually done connections is no longer needed. FCB 4.7 by default keeps manually
modified TC connections. FCB 5.0 by default keeps manually modified TC connections and
DB references.
2.5.4.20 Unattended Operation

In case of errors the Update Parameter, Generate DB and Initialize commands show
intermediate error message boxes that stop operation as they have to be confirmed.
To switch off these messages and just write them into a logfile edit the apb.ini file in the
ADVABLDENV directory:
[SetApbMessage]
2-14 3BDS 007 582D101

PrintLogFile=1 (to write logfile information for one command execution)

BatchMode=1
or
PrintLogFile=2 (to append logfile information for all following command
BatchMode=1
To switch off batch mode set BatchMode=0.
2.5.4.21 DBElement Aspect Copied From Library

In the target project this aspect cannot be opened as it contains a reference to a library TC on the
directory specified by the TC$LEV1 or TC$LEV2 environment variable. A corresponding
message is displayed if you try to do so.
Note that such aspects can be copied nevertheless.
If you need the TC project specific in your target project you have to copy all files for this TC
from the project specific TC directory of the library project to the project specific TC directory
of your target project manually after having copied the object containing the DBElement aspect.
2.5.4.22 Multiuser Operation - SR 9077

Depending on the concrete timing concurrent multiuser operations against one and the same
project may result in different types of message boxes that
• Either can be acknowledged positively to perform a retry or negatively to perform a
termination of the current command
• Or to perform a retry only (to avoid inconsistencies)
• Or to perform a termination only (to avoid inconsistencies).
Because of the message boxes, unattended operation is not recommended.
It is not recommended to perform commands such as
• (Copy) / Paste
• Delete
• Import for creation of objects and aspects
• Import for copying objects from library
the concurrent multiuser way.
It is recommended to do them coordinated (serialized) between the different users.
2.5.4.23 Procedure for Alternating Use of Cooperating Mode and Independent Mode
(SR 0075)
Documents describing integration of ACC 1.7/0, ACC 2.0/0 and CBA 1.0 into AEW 1.2
are:
• AMPL Control Configuration Commands for Structure Builder Version 2.7 User’s Guide
3BSE 013 931R301.
3BDS 007 582D101 2-15

• AMPL Control Configuration Commands for Structure Builder Version 3.0 User’s Guide
3BDS 100498R101.
• Control Builder A Commands for Structure Builder Version 1.0 User’s Guide
3BDS 100498R201.
In contrast to the latter, the first document does not describe the application procedures to
be followed on the client PCs of an engineering system configuration for alternating use
of
• the cooperating mode while working with an AEW client PC connected to an
AEW server PC and
• the independent mode while working with the same AEW client PC disconnected
from the AEW server PC.
This scenario applies if you have an inhouse engineering system configuration with AEW and
ACC resp. CBA and you want to extract the ACC resp. CBA part of your project to work with
your AEW client PC disconnected from the AEW server PC out in the plant with ACC resp.
CBA in independent mode for commissioning tasks.
Working With ACC resp. CBA in Cooperating Mode

You work with ACC 1.7/0, ACC 2.0/0 or CBA 1.0 via the STB 3.2/0 user interface using the
commands described in see above.
You can consider the aspect data handled by ACC resp. CBA in the AEW project you work on
as being stored in a sub-project of this project.
This sub-project is treated via the APB user interface in independent mode as the project for
ACC resp. CBA.
Switching to ACC resp. CBA in Independent Mode

If you want to take an ACC resp. CBA project out to the plant for commissioning work that you
want to do with ACC resp. CBA in independent mode and disconnected from the AEW server
PC you have to perform the following steps on your AEW client PC:
1. Exit STB
2. Start APB directly using the Start | Advant | Engineering | Application Builder 2.7-0
(or 3.0-0 or 4.0-0) menu command
3. If you do not already have a local project root directory for ACC resp. CBA on your AEW
client PC, create one as follows:
a. Use APB menu command File | New Project … .
b. Enter the new local project root and a dummy project name into the New Project
dialog.
c. Press the OK button.
d. Answer the query message box “Cannot find project root … . Do you want to create
it?” with the Yes button.
2-16 3BDS 007 582D101

4. Copy your ACC resp. CBA sub-project from the project root on the AEW server PC to the
local ACC resp. CBA project root on the AEW client PC by using the APB menu
command File | Copy … and its Copy dialog with the scope projects.
Figure 2-2. Copy ACC resp. CBA Project From Server Project Root to Local Client Project
Root
After you have selected scope, “From”- project root, - project name, and “To”-project root
and entered “To”-project name, you press the OK button or the arrow button to perform
the copy operation.
5. If you have used project local type circuits, these are already copied by step 4.
If you have used type circuits stored on a directory pointed to by the system environment
variables TC$LEV1 or TC$LEV2, then you have to take care to make them available also
for work with ACC resp. CBA in independent mode disconnected from the AEW server
PC.
Copy the type circuits with the Windows NT Explorer from the corresponding directory on
the AEW server PC to a local directory on your AEW client PC and set the corresponding
system environment variable on the AEW client PC to that directory using the Start |
Settings | Control Panel | System | Environment tab.
6. On the AEW client PC disconnect the mapped network drives mapped to the shares
abtool1 and advabld1, typically drives J: and L: .
3BDS 007 582D101 2-17

7. Shut down and disconnect the AEW client PC from network.
CAUTION
Make sure that regarding changes you have an agreement with the project
members that might still work at the AEW project inhouse while you do
commissioning either to do no changes to the ACC resp. CBA -part or that
changes are logged carefully and in detail in a list of changes.
It is highly recommended to define the proceeding in a project team for all typical
change cases inhouse and out in the plant before doing the commissioning work.
Remark
For extracting only parts of the ACC resp. CBA project for commissioning (for example, a
node) the same steps apply, except the following:
• A local project on the AEW client PC has to be created as container for the parts.
• The parts have to be copied into this project using the APB Copy dialog on each part using
the corresponding scope (nodes, circuits, or type circuits).
Working With ACC resp. CBA in Independent Mode

During commissioning you work via APB started the Start | Advant | Engineering |
Application Builder 2.7-0 (or 3.0-0 or 4.0-0) menu command.
It is highly recommended to follow rule 1:
Rule 1
All controller software parts and their parameter values that have been inserted into nodes
in FCB in cooperating mode using the commands Generate DB, Locate Circuit / drag
and drop (object with circuit aspect) and Update Parameter must not be changed in
independent mode.
These parts typically originate from a well tested library:

Advant objects with DB Element aspects (representing instantiated type circuits) and
Parameter aspects and Advant objects with Circuit aspects (representing instantiated type
circuits) and Parameter aspects.
All these parts start with an element that shows an automatically generated instance name in
FCB and ONB.
Other parts such as PC Elements and DB elements directly inserted into a node in FCB
separated from the parts stated above can be changed.
If you follow this rule, it will be easy to bring back the commissioned project into AEW
cooperating mode.
If there should be the need to do changes to these parts during commissioning, follow rule 2:
Rule 2
2-18 3BDS 007 582D101

Make sure that all your changes are logged carefully and in detail in a list of changes.
Depending on the changes done there will be some additional effort to bring back the
commissioned project into AEW cooperating mode.
In any case use the File | Copy (for project, nodes, type circuits, and circuits) command of APB
and back-up/restore functionality of Windows NT to save project data before changing.
Switching Back to ACC resp. CBA in Cooperating Mode

Make sure that the original project on the AEW server PC has been back-upped with the STB
Project | Administration function.
To prepare for cooperating mode again, you have to perform the following steps on the AEW
client PC:
1. Connect to network and start up the AEW client PC
2. Map network drives (typically L: and J:) as they had been mapped before switching to
independent mode.
3. Make sure that the system environment variables TC$LEV1 and TC$LEV2 are set
according to your current requirements.
4. Start STB on the original AEW project.
Depending on the changes you have made during commissioning the next steps differ:
You could follow Rule 1:

1. Attach all changed nodes in the local ACC resp. CBA project to the corresponding nodes
in the original AEW project by using the menu command More … | Attach | Node
Function Chart and its Copy dialog with the scope nodes on the Node Control Software
aspect of each corresponding node object (Figure 2-3).
Press the OK button to perform the Attach/Copy operation.
3BDS 007 582D101 2-19

Figure 2-3. Attach Node of Local Project to Node Control Software

Aspect of Corresponding Node Object in AEW Project
2. Now the node objects in the original AEW project contain the changes of the
commissioned project and you can work on in the AEW project.
You only could follow Rule 2:

1. Do all changes you have made during commissioning against the AEW project again.
Follow your change log.
The new detail solutions found during commissioning have to be implemented in AEW
environment to be able to reuse them next time easily using the Advant object bulk data
handling and instantiation functionality of AEW.
2. Work on in the AEW project.
Remark
Due to the flexibility of the AEW/ACC resp. CBA environment expert users will be able to find
procedures to transfer the changes to the AEW project with reduced effort.
Examples are:
• FCB File | Export DB Section and MS Excel to produce an import list for boards and
signals for STB Project | Import …
• FCB Edit | Copy and FCB Edit | Paste to create an updated circuit or type circuit from
AMPL code parts entered during commissioning.
2-20 3BDS 007 582D101

Section 3.1 Installation
Chapter 3 Installation
3.1 Installation
NOTES
Every locally installed Application Builder requires one license.
In case of network installation with multi-user access, the required number of

licenses must correspond to the number of established users of the product.
This corresponds to the number of client installations.
The complete Application Builder setup is described in the Control Builder A Release Notes.
Application Builder 4.1/0 needs BCI (Bus Configuration Interface) >= 3.0/1. It will silently
install BCI 3.0/1. In due case, if BCI exceptions, like “Invalid BCD version” occur, you can
manually install BCI 3.0/1 there, for example, by opening the installation disk CD1 by the
Windows NT Explorer, and double-clicking on the \AdvaBld\apb\40r0\bci\disk1\setup.exe
file, and confirming the dialog boxes appropriately. You can check installation of BCI by
a. Searching for files ..\program files\common files\advabld shared\bci.dll and
bci30.dll
b. Checking its properties and its version. Version should >= 3.0/1.
BCI needs Data Access Object utility (DAO 3.5). It will silently install the newest DAO 3.5.
In due case, if DAO exceptions occur, you can install DAO 3.5 manually, see Control Builder A
Release Notes.
3.2 Upgrading
If you have older versions of Application Builder installed, the new version will be installed in
parallel.
Projects created with the 16-bit version of Application Builder may contain a file named
foot001.tpx. The file applies to the 16-bit version of Application Builder. The file you have
selected in the File | New | Project dialog will be copied from the ADVABLDENV directory to
the project as foot001.tpx during creation of a project. If you want to print out data of projects
created with the 16-bit version of Application Builder, copy the foot001.tpx file from the
ADVABLDENV directory to the project.
If you do not copy the new file to the project created with the 16-bit version of Application
Builder it may happen, that the logo is missing, or is drawn in an extraordinary size. If you
created your own logo file, you may need to modify your own *.tpx and *.wmf file, so that your
logo is drawn correctly.
3BDS 007 582D101 3-1

Chapter 3 Installation
3.3 Backup and Restore

For a description of backup and restore see
• The Control Builder A Release Notes or the
• Advant Engineering Workplace Release Notes if you are working in cooperating mode.
3.4 Un-install
Un-install is provided via the Add/Remove Programs icon in the Control Panel. To uninstall
Application Builder, select the Install/Uninstall tab, select the Application Builder version you
want to uninstall, e.g. Application Builder 3.0/0, and click Add/Remove to uninstall it.
If you performed a server installation, the entry is called e.g. Application Builder 3.0/0 Server.
During Un-install you may be asked a question like the following:
Figure 3-1. Remove Shared File Dialog
NOTE
Be sure to answer the question with NO for the following files:
MFC42.DLL
MFC42U.DLL
MSVCIRT.DLL
MSVCRT.DLL
MSVCRT20.DLL
MSVCRT40.DLL
ATL.DLL
These file are core components needed by Windows NT to run properly. Other
files may be deleted as they are used by Control Builder A components.
3-2 3BDS 007 582D101

Section 4.1 System Specification
Chapter 4 Miscellaneous
4.1 System Specification

All requirements, prerequisites, and system settings to run Application Builder are described in
the Control Builder A Release Notes.
3BDS 007 582D101 4-1

Release Notes - 3BDS007582D101 - Application Builder

Uploaded by

Copyright:

Available Formats

You might also like

Release Notes - 3BDS007582D101 - Application Builder

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Release Notes - 3BDS007582D101 - Application Builder

Uploaded by

Copyright:

Available Formats

Advant® OCS Application Builder

with Master software

Copyright © ABB Automation Products GmbH 2002.

3BDS 007 582D101

3BDS 007 582D101 i

2.4.3.6 Unnecessary Type Circuit Copies if Copying Objects

ii 3BDS 007 582D101

2.5.4.23 Procedure for Alternating Use of Cooperating Mode and

3BDS 007 582D101 iii

iv 3BDS 007 582D101

1.1 Executive Summary

1.2 How to Use This Document

1.3 Version Designation

3BDS 007 582D101 1-1

1.4 Revision Record

Table 1-1. Current Version

Version Release Date Remarks

Table 1-2. Earlier Versions

Version Release Date Remarks

1-2 3BDS 007 582D101

Table 1-2. Earlier Versions

Version Release Date Remarks

3BDS 007 582D101 1-3

1.7 Related Documentation

Table 1-3. Valid Manuals

Document Ordering no.

1-4 3BDS 007 582D101

2.1 New Functions

2.1.1 Stand alone and Integrated

3BDS 007 582D101 2-1

Figure 2-1. Convert of long Type Circuit names

2-2 3BDS 007 582D101

2.2 Discontinued and Replaced Functions and Units

2.3 Fixed Problems

2.3.1 Stand alone

2.3.1.1 Attach of existing Node, TC or CI

2.3.2 Integrated in Industrial IT

3BDS 007 582D101 2-3

This has been corrected.

2.3.2.3 Name of copied Node, TC or CI is not added to .DAT file

2.4 Known Problems and Work Arounds

2.4.1 Stand alone

2.4.1.1 Editing .TIX or .TBX files with AS100-EDIT

2-4 3BDS 007 582D101

2.4.1.2 Update FCB Data of Nodes Containing Only DB or Only PC Part

Update from => to FCB

2.4.2 Integrated in Industrial IT

2.4.2.1 Unexpected Termination of Plant Explorer

2.4.3 Integrated in Advant Engineering Workplace

3BDS 007 582D101 2-5

2.4.3.2 Print / Print to File on Type Circuit and Circuit Aspect

2.4.3.3 Terminate Structure Builder / Application Builder Stays in Memory

2.4.3.4 Generate DB / Function Chart Builder Stays in Memory

2-6 3BDS 007 582D101

2.5.1.1 Usage of Default Installation Directories

2.5.1.2 Environment Variable ADVABLDENV

3BDS 007 582D101 2-7

2.5.2 Stand Alone