Advant® OCS Function Chart Builder

with Master software

Version 6.2/0

Release Notes
3BDS 011 103D201
 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.
LON and LONWORKS are registered trademarks of Echelon 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 2003.

3BSE001264/E

Template: 3BSE001286/E

3BDS 011 103D201

 Function Chart 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-4
1.6 Restrictions .............................................................................................................. 1-6
1.7 Related Documentation............................................................................................ 1-6

Chapter 2 - Functionality
2.1 New and Changed Functions ................................................................................... 2-1
2.1.1 General.................................................................................................... 2-1
2.1.1.1 View Crossreference ........................................................ 2-1
2.1.1.2 Print DB Names ............................................................... 2-1
2.1.1.3 Print PC Names ................................................................ 2-1
2.1.1.4 Import DB Section ........................................................... 2-1
2.1.2 Support of AC 160 2.2............................................................................ 2-2
2.2 Fixed Problems Since FCB*6.1/0............................................................................ 2-3
2.2.1 Off-line Editing....................................................................................... 2-3
2.2.1.1 Wrong execution when Regional Settings "English
US"/Dec.symb.”,”/Dig.gr.symb.”.”, SR1162 ................... 2-3
2.2.1.2 PC Element Instance Name cleared after Edit Call
Parameters ........................................................................ 2-3
2.2.1.3 Minimum Range of Real Values of DB Terminal Values
are not checked................................................................. 2-4
2.2.1.4 Latest Entry in History List missing ................................ 2-4
2.2.1.5 Connect PC Terminal with Illegal Value.......................... 2-4
2.2.1.6 LON:TYPE not checked .................................................. 2-4
2.2.1.7 Missing PC Programs in Memory Calculation ................ 2-4
2.2.2 Source Code Generation and Backtranslation ........................................ 2-5
2.2.2.1 DB Sourcecode with Wildcard Itemdesignations ............ 2-5
2.2.2.2 Problems in TC Backtranslate with TTDLOG/TTDVAR 2-5
2.2.2.3 Replace Item Designation by Wildcard in DB Sourcecode2-5
2.2.2.4 Wrong Sourcecode for ONB with "DB MODIFY" ......... 2-6
2.2.3 Target Specific Functions ....................................................................... 2-7
2.2.3.1 No check for POSITION=2 in case Several not Redundant
AF100 CI.......................................................................... 2-7
2.2.3.2 Check POSITION of AF 100 Coupler ............................. 2-7
2.2.4 Test and Debug, Recording..................................................................... 2-7

3BDS 011 103D201 i

Function Chart Builder Release Notes
Table of Contents

2.2.5 Diagnostics .............................................................................................. 2-7

2.2.5.1 Old date in Module Diagnostics ....................................... 2-7
2.2.6 PROFIBUS Library Editor...................................................................... 2-7
2.2.6.1 Rename SLAVE PBS to Dummy ..................................... 2-7
2.2.7 BCB/BCI ................................................................................................. 2-8
2.2.8 COM Interface ........................................................................................ 2-8
2.3 Known Problems and Work Arounds....................................................................... 2-9
2.3.1 Circuits in Network Environment ........................................................... 2-9
2.3.2 Zooming .................................................................................................. 2-9
2.3.3 Printing .................................................................................................... 2-9
2.3.4 National Characters ................................................................................. 2-9
2.3.5 Special Characters in Source Code ......................................................... 2-9
2.3.6 DB Element NETWL.............................................................................. 2-9
2.3.7 DB Elements AX, CV, DX, and DCU in TCs......................................... 2-9
2.3.8 Backtranslate Connection to Text Constant Containing a Colon.......... 2-10
2.3.9 Backtranslate TCS, CIS, NSS Files Containing “Comments”.............. 2-10
2.3.10 Shutting Down Windows NT While Being On-line Connected ........... 2-10
2.3.11 Recognition of Variant Modules in GSD File, SR 9038 ....................... 2-11
2.3.12 Usage of Access 97 Database for PROFIBUS Library Editor.............. 2-11
2.3.13 DIS - DI880/DI885 not Correctly Recognized, SE2000026................. 2-12
2.3.14 Footer in "Edit Document Texts" unreadable small.............................. 2-12
2.3.15 Edit TIX- and TBX-files with AS100-Edit Editor ................................ 2-12
2.3.16 Error during Installation of Function Chart Builder ............................. 2-12
2.3.17 Message Box during Installation of Function Chart Builder ................ 2-13
2.4 Recommendations .................................................................................................. 2-14
2.4.1 Usage of Default Installation Directories.............................................. 2-14
2.4.2 Correspondence of Force Values to Conditions on Target .................... 2-14
2.4.3 Un-install Libraries Before Un-installation of FCB.............................. 2-14

Chapter 3 - Installation
3.1 Installation................................................................................................................ 3-1
3.1.1 Installation Procedure.............................................................................. 3-1
3.1.2 Start ......................................................................................................... 3-1
3.2 Upgrading................................................................................................................. 3-2
3.2.1 Upgrading of Function Chart Builder ..................................................... 3-2
3.2.2 Upgrading of PROFIBUS Library Editor Data....................................... 3-3
3.2.3 Upgrade of AC 160 1.1 Source Code to AC 160 1.2 .............................. 3-3
3.3 Backup and Restore.................................................................................................. 3-4
3.4 Un-install.................................................................................................................. 3-4

ii 3BDS 011 103D201

 Function Chart Builder Release Notes
Table of Contents

Chapter 4 - Miscellaneous
4.1 System Specification................................................................................................ 4-1

3BDS 011 103D201 iii

Function Chart Builder Release Notes
Table of Contents

iv 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 1.1Executive Summary

Chapter 1 Introduction

1.1 Executive Summary

This Release Note contains information about Function Chart Builder (FCB) running on
Windows NT 4.0 and Windows 2000.
Function Chart Builder provides an easy-to-use environment for application programming of
Advant Controller 400 Series, MasterPiece 200/1, and Advant Controller 100 Series. It offers an
efficient method of function-oriented project engineering by supporting type circuit, circuit, and
node structure.
It can be used stand alone, integrated in Industrial IT or integrated in Advant Engineering
Workplace.
For more information about Function Chart Builder refer see Advant Engineering Products
Product Guide and Section 2.1, New and Changed Functions.
For installation of Function Chart Builder see Control Builder A Installation Guide.

1.2 How to Use This Document

It is recommended that you first read through this introduction and the installation procedure
(see Section 3.1, Installation). Then perform the installation of Function Chart Builder.
You will find this document on the CD-ROM labelled Advant Engineering Software CD1.
The Release Notes will also be copied during installation to the directory
drive:\AdvaBNT\FCB\61r0. You have access to them by
Start | Advant | Engineering | Release Notes | Function Chart Builder 6.1-0.

1.3 Version Designation

Function Chart Builder of version 6.2/0 is included in
Control Builder A of version 1.2/0.
The following utilities are attached to and delivered with Function Chart Builder 6.2/0:
• CI57x LON Interface Generator 6.2/0
(utility that generates external interface descriptions (XIF) file for the LON channels of the
CI572/CI573 reflecting the configuration of these channels in Function Chart Builder)
• PROFIBUS Library Editor 6.2/0
• Setup Add-Ons 6.2/0
• Upgrade S800 6.2/0
(utility for upgrading S800 I/O item designations from AC 160 1.1 to AC 160 1.2 AMPL
source code).
• MB300 Upload

3BDS 011 103D201 1-1

Function Chart Builder Release Notes
Chapter 1Introduction

1.4 Revision Record

The following revision has been produced:

Table 1-1. Current Revision

Revision Release Date Remarks

FCB*6.2/0 28-Mar-2003 32-bit version for Windows NT and Windows 2000;
New functions:
Support of AC 160 2.2
For new function for integrated in Industrial IT mode see
Control Builder A Interface Release Notes.

The following versions and revisions were produced earlier:

Table 1-2. Earlier Versions and Revisions

Version Release Date Remarks

FCE*1.0 15-OCT-1990 First version
FCE*1.1 07-AUG-1991 DOS version
FCE*2.0 17-JAN-1992 DOS version
FCE*2.1 16-APR-1992 DOS version
FCE*2.2 15-MAY-1992 DOS version
FCE*2.3 10-NOV-1992 DOS version
FCE*3.0 26-FEB-1993 DOS and Windows 3.11 version
FCE*3.0/1 15-JUL-1993 DOS and Windows 3.11 revision
FCE*3.0/2 12-JUN-1995 DOS and Windows 3.11 revision
FCE*3.0/3 02-APR-1996 DOS and Windows 3.11 revision
FCB*3.1 05-NOV-1994 Last DOS and Windows 3.11 version
FCB*4.0 31-MAR-1995 First true Windows 3.11 version
FCB*4.1 15-DEC-1995 Windows 3.11 version
FCB*4.2 15-APR-1996 Windows 3.11 version
FCB*4.3 14-FEB-1997 Windows 3.11 version
FCB*4.3/1 30-APR-1997 Windows 3.11 revision
FCB*4.4 12-Dec-1997 First 32-bit version for Windows NT, included in ACC
version 1.4 and 16-bit version for Windows 3.11 version

1-2 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 1.4Revision Record

Table 1-2. Earlier Versions and Revisions

Version Release Date Remarks

FCB*4.5 03-April-1998 32-bit version for Windows NT, included in ACC version
1.5 and 16-bit version for Windows 3.11 version
FCB*4.5/1 09-April-1998 32-bit version for Windows NT and 16-bit version for
Windows 3.11 version
FCB*4.5/2 15-May-1998 32-bit version for Windows NT and last 16-bit version for
Windows 3.11 version
FCB*4.6/0 05-Feb-1999 32-bit version for Windows NT. New functions added:
application retrieval from target, application protection,
on-line preparation mode, Connect assistant, DCOM
communication, extended PROFIBUS configuration, and
library handling.
FCB*4.6/1 26-April-1999 32-bit version for Windows NT. Miscellaneous bug fixes.
FCB*4.7/0 14-JAN-2000 32-bit version for Windows NT; location of CIs also in
node mode, create/delete TCs on-line, multilevel
undo/redo, context menu in PC Section, connect by
instance name, date and time preset on target, print this
page, and several bug fixes
FCB*5.0/0 11-AUG-2000 32-bit version for Windows NT and Windows 2000; S800
IO light, support of CI527, generate bus configuration
data for MB300 and GCOM, support of MB300
Connector, variable separator character for
automatically created DATs, DB general defaults in a
ONB like DBGENDEF.BAX file, virtual connections
improvements, renumber selected range of PC
elements, view cross-references in output window,
selective printout of DB section, edit TC/CI symbol
values with update of symbolic DB references, and
several bug fixes

3BDS 011 103D201 1-3

Function Chart Builder Release Notes
Chapter 1Introduction

Table 1-2. Earlier Versions and Revisions

Version Release Date Remarks

FCB*6.0/0 09-Apr-2001 32-bit version for Windows NT and Windows 2000;
New functions:
- Support of AC 160 2.1 with new CPU PM665
- PARDATs with Unit terminal, PARDAT(T), (TR)
- Password protection for target control and read only
access,
- improvements for node source generation and
backtranslation
FCB*6.1/0 08-Mar-2002 32-bit version for Windows NT and Windows 2000;
New functions:
- FCB in english and german language
- DB Elements for S800 I/O with Advant Controller
160/110 via Profibus are now adapted to CI830 Version
1.3
For new function for integrated in Industrial IT mode see
Control Builder A Interface Release Notes.

1.5 Compatibility
Function Chart Builder 6.2/0 is based on Application Builder 4.1/0.
Function Chart Builder 6.2/0 supports Bus Configuration Builder 3.0/1.
Function Chart Builder 6.2/0 is compatible with PROFIBUS Library Editor 6.2/0 and Setup
Add-Ons 6.2/0 attached to and delivered with it.
Function Chart Builder 6.2/0 is AMPL source code compatible with earlier versions of
AdvaBuild Function Chart Builder, see below.

Compatibility integrated in Advant Engineering Workplace

Function Chart Builder 6.2/0 requires Structure Builder 3.2/0 when running integrated in
Advant Engineering Workplace.

Compatibility integrated in Industrial IT

Function Chart Builder 6.2/0 requires Engineering Studio 2.0/1 when running integrated in
Industrial IT.

1-4 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 1.5Compatibility

Supported Node Types

Function Chart Builder supports all the node types contained in the AMPL PC and DB Element
Libraries 3.2/0 and also other node types contained in other libraries.
The AMPL PC and DB Element Libraries 3.2/0 and the other libraries, if applicable, have to be
installed separately.

Compatibility of Binary Data

The internal data structure (*.ODB) has become incompatible to older versions.
For upgrading see Section 3.2, Upgrading.

Compatibility of AMPL Source Code

AMPL source code produced by the versions FCB*6.1/0, FCB*6.0/0, FCB*5.0/0, FCB*4.7/0,
FCB*4.6/*, FCB*4.5/*, FCB*4.4/*, FCB*4.3/*, FCB*4.2/0, FCB*4.1/0, and FCB*4.0/0 is
compatible to this FCB version.
AMPL source code produced by the latest DOS version FCE*3.1/0 is compatible to FCB*6.2/0.
If you intend to upgrade project data containing type circuits or circuits generated by an FCE
version < 3.1 to FCB*6.2/0, you should upgrade it to FCE*3.1/0 first.
Since Function Chart Builder 6.1/0 the type circuits and circuit can have long names > 8
characters. Such type circuits and circuit cannot be used in earlier versions of Function Chart
Builder.

Compatibility of Bus Configuration Database

Function Chart Builder 6.2/0, more exactly Bus Configuration Interface 3.0/1, automatically
converts and upgrades any Bus Configuration Database (BCD) 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.
• ACC 1.7/0 components (APB 2.7/0, BCB/BCI 2.7/0, FCB 4.7/0) create BCD version 1.2.
• ACC 2.0/0 components (APB 3.0/0, BCB/BCI 3.0/0, FCB 5.0/0) create BCD version 1.2.
• 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.1/0, BCB 3.0/0/BCI 3.0/1, FCB 6.1/0) create BCD version
1.2.
• CBA 1.2/0 components (APB 4.1/0, BCB 3.0/0/BCI 3.0/1, FCB 6.2/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.1/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).

3BDS 011 103D201 1-5

Function Chart Builder Release Notes
Chapter 1Introduction

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.2/0, but at least BCB 3.0/1 on them. This is the easy way.
• Or install at least BCI 3.0/1 on them, see Section 3.1.1, Installation Procedure.
At the same time, no upgrade of FCB 4.6/1, FCB 4.7/0, ... FCB 6.1/0 nodes is necessary to FCB
6.2/0: The Bus Configuration Database can contain bus configuration data (nodes) generated by
FCB 4.6/1, FCB 4.7/0, ... FCB 6.2/0.

1.6 Restrictions
Function Chart Builder is a 32-bit Windows application which can be run on Windows NT 4.0
and Windows 2000 platforms.
As Function Chart Builder is a Windows application, the ANSI character set is used. Files
created with an MS-DOS editor use the OEM (IBM 8 bit) character set. Such files should not be
used in Windows environment without converting them to the ANSI character set. You can
convert such files using AS100-EDIT and the Edit | Convert | OEM to ANSI command.
Source code produced by FCB*6.2/0 is not downward compatible to FCB versions earlier than
4.5/0 or FCE if you use instance names for instantiated PC elements, instantiated type circuits,
and located circuits.
Source code produced by FCB*6.2/0 is not downward compatible to FCE versions < 4.0 if you
use layout templates other than “Standard Master”. Only “Standard Master” layout templates
are downward compatible.
If you intend to exchange source code with AS 500ES, you should use “Standard Master” layout
templates.

1.7 Related Documentation

The manuals related to Control Builder A are listed in the following manual:

Table 1-3. Control Builder A Manuals

Document Ordering No.

Control Builder A Installation Guide 3BDS011136R101
Advant Engineering Products 3BSE 014 966R1001
Product Guide

PC and DB Elements Reference Manuals are listed in the AMPL PC and DB Element Libraries
3.2/0 release notes.

1-6 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 2.1New and Changed Functions

Chapter 2 Functionality

2.1 New and Changed Functions

For new function for Control Builder A integrated in Industrial IT mode see Control Builder A
Interface 1.2/0 Release Notes.

2.1.1 General

2.1.1.1 View Crossreference

New menu entries View > Cross Ref. of sel. PC Elem. and View > Cross Ref. of sel. DB
Elem. provide the possibility to view all crossreferences of the selected PC or DB element. In
case of multi selection of PC elements all crossreferences of the selected PC elements are
shown.

NOTE
Filters defined in View > Cross Reference ... are overwritten by the functions
View > Cross Ref. of sel. PC Elem. and View > Cross Ref. of sel. DB Elem. .
The filters have to be set again.

2.1.1.2 Print DB Names

The function File > Print > Document > DB Names prints all instance names of DB elements.
Filters can be defined.

2.1.1.3 Print PC Names

The function File > Print > Document > PC Names prints all defined names of PC elements
and terminals (Name Table). PC Programs and Filters can be defined.

2.1.1.4 Import DB Section

The function File > Import DB Section can be used to import files former exported with File
>Export DB Section. The import file can have any extension.
The function can be used to import DB section created or modified with help of excel lists.
Existing DB Elements can be modified or new DB Elements can be created.
This function makes sense in node mode, not in type circuit or circuit mode.

3BDS 011 103D201 2-1

Function Chart Builder Release Notes
Chapter 2Functionality

2.1.2 Support of AC 160 2.2

New Node Types
• AC 160 with PM64x 2.2
• AC 160 with PM66x 2.2
are available in Application Builder and can be used in Function Chart Builder.
The new /changed functions of AC 160 2.2 in comparison with AC 160 2.1 are:
– Support of Terminal BIOB_SPD for DB Elements PM*
– New Option “OPT 8: Warm Start 2.2”.
– Support of Terminal SINGLE for DB Elements PM*
– Increase number of DB Elements MDAT
– DP640 Safety Relevant Parameters
– Support of DI830
– Support Master Fieldbus Coupler CI671 in AC 160
– Support of Terminal AST_OFFS for DB Element PM665
– Support of Terminals TIM_SYNC for DB Element CI810
– Support new Terminals for SYSL PC Element
– Support PC Element SYSLCON
– Support Terminal FORCESWO for the DB Elements CI630/CI631
– Support Terminal PRIMARY for the DB Elements CI630/CI631
– Support Terminal BL_CSWO for the DB Elements CI630/CI631
– Support Terminal BL_INIT for the DB Elements CI630/CI631
– Support Intrinsic Safety modules AI890, AI895, AO890, AO895, DI890, DO890
For detailed information about new and changed PC and DB Elements see PC and DB element
reference manuals.

2-2 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 2.2Fixed Problems Since FCB*6.1/0

2.2 Fixed Problems Since FCB*6.1/0

Wrong execution when Regional Settings "English US"/Dec.symb.”,”/Dig.gr.symb.”.”

2.2.1 Off-line Editing

2.2.1.1 Wrong execution when Regional Settings "English

US"/Dec.symb.”,”/Dig.gr.symb.”.”, SR1162
If Regional Settings (Win NT)/Regional Options (Win 2000) are set to:
Regional Settings (Win NT)/General (Win 2000):
English (United States)
Number(s): Decimal symbol ","
Digit grouping symbol "."
(Default values are
Number(s): Decimal symbol "."
Digit grouping symbol ",")
then constants entered in exponential notation lose their exponent and the decimal digits.
The application works with wrong constants.
The problem is not visible in offline mode or AMPL Source Code. Wrong values can be seen in
online mode when a value containing exponent and/or decimal digits is selected for display.
To correct the problem the default regional settings for English (United States) (see above) have
to be set and new target code has to be created and downloaded.

There is no problem when Regional Settings/Regional Options are set to:

Regional Settings (Win NT)/General (Win 2000):
German (Standard)/German (Germany)
Number(s): Decimal symbol ","
Digit grouping symbol "."
These are the default settings.
This problem exists in Function Chart Builder, version 4.7, 4.8, 5.0, 6.0 and 6.1.
This has been corrected.

2.2.1.2 PC Element Instance Name cleared after Edit Call Parameters

In the PC section a name can be used as instance name.
Case such an instance name has been used and File > Edit Call Parameter is used for this PC
Element the instance name is cleared thereafter.
This has been corrected.

3BDS 011 103D201 2-3

Function Chart Builder Release Notes
Chapter 2Functionality

2.2.1.3 Minimum Range of Real Values of DB Terminal Values are not checked
In DB Section the minimum range of real values of DB terminal values are not checked in case
the minimum and maximum value of the allowed range are positive values.
e.g. DPS640:MEAS_PER range 1 to 100
A value outside this range can be entered without error e.g. 0.5
This has been corrected.

2.2.1.4 Latest Entry in History List missing

History lists are available e.g. in PC Terminal Connect dialog or in Create / Edit Table Entry
dialog of Test Table.
After changing to another PC program, the latest entry in the history list is missing e.g. in PC
Terminal Connect dialog in Combo Box “Item Designation” and "To". Every change of the PC
program leads to a shortened history list.
This has been corrected.

2.2.1.5 Connect PC Terminal with Illegal Value

In the following case the FCB crashes:
Enter a name for a PC output terminal e.g. "otto",
Select an unconnected input of same type,
Select PC-Terminal > Connect... ,
Enter otto:err as connection string and choose OK.
Result: data corrupted : class <> pcElement.
Beginning with FCB 6.2/0 the message “Name is not a PC Element name” is displayed in the
case above.
This has been corrected.

2.2.1.6 LON:TYPE not checked

It is possible to change the value of the DB Terminals LON:TYPE values other than CI572 and
CI573. This is wrong.
Beginning with FCB 6.2/0 only the values CI572 and CI573 can be entered.
This has been corrected.

2.2.1.7 Missing PC Programs in Memory Calculation

The function PC-Section > Memory Calculation > For Node lists all PC programs, if they are
created or backtranslated in ascending order, i.e. PC1, PC5, PC7, ... .

2-4 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 2.2.2Source Code Generation and Backtranslation

In case a PC program with a higher number has been created first e.g. PC21, only PC programs
>= PC21 are listed.
This has been corrected.

2.2.2 Source Code Generation and Backtranslation

2.2.2.1 DB Sourcecode with Wildcard Itemdesignations

DB source code can be generated with wildcard itemdesignations. Backtranslating this source
code (in node mode) does not work for e.g. S800 IO.
FCB crashes with Fatal Error "No ’nr’ in MFDBCreateDBElement".
This has been corrected.

2.2.2.2 Problems in TC Backtranslate with TTDLOG/TTDVAR

TC/CI DB source code containing TTDLOG / TTDVAR elements backtranslated in TC/CI
mode. The source code has been generated by FCB.
This has been corrected.

2.2.2.3 Replace Item Designation by Wildcard in DB Sourcecode

1st Problem:
DAT1, DAT2,DAT3 created manually, without an explicit name,
DAT3 connected to PC part,
Delete DAT1,
Create source,
Backtranslate source.
Result: DAT2 and DAT3 become DAT1 and DAT2, connection to DAT3 is missing
The problem does not occur, if the DB element has a name
2nd Problem:
DAT1, DAT2, DAT3 created manually
Instantiate a TC that creates 3 DATs (DAT4, DAT5, DAT6),
Delete DAT1,
Create source,
Backtranslate source.
Result: DAT2 ... DAT6 become DAT1 ... DAT5, TC is expanded, because itemdesignation
DAT6 (in .TIX file) cannot be found

3BDS 011 103D201 2-5

Function Chart Builder Release Notes
Chapter 2Functionality

Generate DB source code with "Replace Item Designation by Wildcard" should not be used
when there are connections to PC elements/terminals from DB item designations. These
connections cannot be restored correctly when backtranslating the source code because the PC
source code contains DB item designations and in the DB source code there are wildcards
instead of the itemdesignations.
Beginning with FCB 6.2/0 the DB source code generator with "Replace Item Designation by
Wildcard" generates warnings in the output window for connections to PC elements/terminals
from DB item designations.

2.2.2.4 Wrong Sourcecode for ONB with "DB MODIFY"

The function File > Generate Target Code include the option “Prefix DB Elements by
MODIFY”.
The source code generated by FCB looks like:
MODIFY AI800_1 AI820
:NAME AI800_1

MODIFY AI800_1.1
:NAME AI800_1.1
:CONV_PAR 4..20mA

MODIFY AI800_1.2
:NAME AI800_1.2
:CONV_PAR 4..20mA
...

FCB can backtranslate its own source code but the ONB don’t.
Beginning with FCB 6.2/0 the source code generated by FCB looks like:
MODIFY AI800_1 AI820
:NAME AI800_1

AI800_1.1
:NAME AI800_1.1
:CONV_PAR 4..20mA

AI800_1.2
:NAME AI800_1.2
:CONV_PAR 4..20mA

This souce code is accepted by the ONB.

This has been corrected.

2-6 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 2.2.3Target Specific Functions

2.2.3 Target Specific Functions

2.2.3.1 No check for POSITION=2 in case Several not Redundant AF100 CI

The check for POSITION=2 in case several not redundant AF100 CI don’t work.
In such a configuration e.g. AF100 coupler on position = 4 and = 5 the CI don’t work correct on
the target.
Case PM:SINGLE=1 (new terminal for AC 160 2.2) POSITION = 2 is not required.
This applies to AC 160 all versions.
This has been corrected.

2.2.3.2 Check POSITION of AF 100 Coupler

AF 100 coupler e.g. CI626/30/31 are not allowed with POSITION 3..8. AF 100 coupler don’t
work correct on this positions.
This is checked during File > Generate Target Code ... . Existing source code including AF
100 coupler with POSITION [3..8] can be backtranslated but no target code can be generated.
This applies to AC 160 1.0 .. AC 160 2.1 and AC 166.
This has been corrected.

2.2.4 Test and Debug, Recording

no fixed problems.

2.2.5 Diagnostics

2.2.5.1 Old date in Module Diagnostics

In case of error it can happen that the module diagnostics display the date "02/01/1993" as date
when the window was opened.
This is a real default value which has been replace by --/--/---.

2.2.6 PROFIBUS Library Editor

2.2.6.1 Rename SLAVE PBS to Dummy

The function File -> New in PROFIBUS Library Editor brings up one Compact Slave. This
slave was named PBS until PROFIBUS Library Editor 6.1. Beginning with PROFIBUS Library
Editor 6.2 this slave is named Dummy.
This is done in order not to overwrite or modify existing DB Element PBS included in base
library of AC 160 1.1, 1.2 to 2.2 and AC 110 2.2 and 2.3.
In case the DB Element PBS shall be used in Function Chart Builder and PROFIBUS Library
Editor is used to generate Slave DB Elements add this in PROFIBUS Library Editor.

3BDS 011 103D201 2-7

Function Chart Builder Release Notes
Chapter 2Functionality

2.2.7 BCB/BCI
no fixed problems.

2.2.8 COM Interface

no fixed problems.

2-8 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 2.3Known Problems and Work Arounds

2.3 Known Problems and Work Arounds

2.3.1 Circuits in Network Environment

If in a network environment more than one user is locating circuits at a certain time in a node
structure, it is possible that the same circuit is located twice (as the information of located
circuits is determined when starting FCB and kept up to date per session). When a user later
starts FCB, he will be warned that some circuit is located twice.

2.3.2 Zooming
In certain combinations of monitor resolution and zoom factor there will be a mismatch between
text and graphics within function chart representation. In such a situation the Windows font
mapper could not find a font, which exactly matches the required size. Use a different zoom
factor in such cases.

2.3.3 Printing
In some cases part of the footer is missing in your printed documentation. This depends on the
selected printer and the installed printer driver. We have seen that problem using HP DeskJet
using the printer driver delivered by HP. The HP printer driver limits the printable area on paper.
In this case use the standard Windows printer driver instead. This problem is common for all
Windows applications, for example, Word and Excel. In general you should look for updates of
printer drivers.

2.3.4 National Characters

National characters can not be used within names of circuits and type circuits.

2.3.5 Special Characters in Source Code

Source code files containing special characters like ^Z, SPACE, TAB after the end statement
may cause error messages during backtranslation. Such trailing characters may be created when
transferring files via network or when using certain editors. Remove these characters using an
appropriate text editor.

2.3.6 DB Element NETWL

DB source code (*.BAX) for AC 410 or AC 450 including the system DB element NETWL
may report errors during TRDBS command of On-line Builder.
If the specified network parameters do not match the actual values on the node, an error is
reported because these network parameters can not be modified via source code.

2.3.7 DB Elements AX, CV, DX, and DCU in TCs

The item designation calculation of DB elements AX, CV, DX, and DCU does not work
correctly in some cases if they are used within type circuits.

3BDS 011 103D201 2-9

Function Chart Builder Release Notes
Chapter 2Functionality

2.3.8 Backtranslate Connection to Text Constant Containing a Colon

Source code containing PC terminal connections to text constants like
:ACTTEXT1 CD=’ABC :XYZ’
or DB terminal descriptions like
:DESCR string1 :string2
cannot be backtranslated correctly.
Avoid using the sequence space - colon in the connection string and terminal description.
Use, for example, the sequence underline - colon instead.

2.3.9 Backtranslate TCS, CIS, NSS Files Containing “Comments”

Source code containing PC terminal connections to text constants like
:ACTTEXT1 CD=’ABC--XYZ’
or
:ACTTEXT2 D=’ABC(*XYZ*)’
cannot be backtranslated correctly.
Avoid using the sequence -- in text constants because this sequence is reserved for designate
the start of a comment line in the source code.
Avoid using the sequences (* and *) in text constants because they are reserved for designate
the start and end of a comment in the source code.
Use, for example, the sequence underline - underline instead.

2.3.10 Shutting Down Windows NT While Being On-line Connected

Always disconnect the Function Chart Builder from the target (by Target | Disconnect
command) before shutting down Windows.
During shutting down Windows NT the Function Chart Builder cannot disconnect properly
even if you answer Yes in response to the query
Do you want to disconnect ...?

2-10 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 2.3.11Recognition of Variant Modules in GSD File, SR 9038

2.3.11 Recognition of Variant Modules in GSD File, SR 9038

This problem concerns usage of the Edit | Create … | From GSD function of the Profibus
Library Editor 6.0/*.
In GSD files the entry Modular_Station=0 specifies a compact PROFIBUS device.
The GSD file of a Compact Profibus Device can include more than one module definition:
Module="CFG data 1" hexadecimal_values1
EndModule
Module="CFG data 2" hexadecimal_values2
EndModule
...
This kind of module definition can mean
1. The description of the device is divided into several modules, for example, for attachment
of texts. This is used, for example, in GSDs created by Softing and Bosch.
2. Every module describes one possible variant of the device. Only one module definition
must be selected. This is used, for example, in GSDs created by Siemens.
While the Profibus Library Editor works fine in case 1, it does not support case 2.
To recognize case 2 inspect the GSD file via a text editor or the Profibus Library Editor. When
you use the Edit | Create … | From GSD function, the Profibus Library Editor detects whether
a GSD file of a compact PROFIBUS device read.
Accordingly, it shows a “Compact Slave” or “Modular Slave” in the Preview window. In due
case, select the View GSD button and inspect the module definition(s) to see if case 2 is
included in GSD. Read especially comments in the GSD file and read the documentation of the
PROFIBUS Device.
Workaround:
1. Prepare a backup copy of the original GSD file.
2. Rename the GSD file, for example, in the way that the used variant is included in the
filename.
3. Rename the name of the slave element type after the Model_Name keyword in the GSD
file, for example, in the way that the used variant is included.
4. Remove all module definitions except the used variant from the GSD file.
If more than one variant included in the GSD file has to be used, then create different GSD
files as described above.
5. Create DB element types on the basis of these GSD files.

2.3.12 Usage of Access 97 Database for PROFIBUS Library Editor

The PROFIBUS Library Editor use an MS Access 97 database for storage of data.
In case an experienced user of PROFIBUS Library Editor want to edit this database this can
only be done with MS Access 97. Be aware not to convert this database to a newer version of
MS Access. PROFIBUS Library Editor cannot work with a converted database.

3BDS 011 103D201 2-11

Function Chart Builder Release Notes
Chapter 2Functionality

2.3.13 DIS - DI880/DI885 not Correctly Recognized, SE2000026

In case more than one DI885 is used having same cluster and position address e.g.
DI885 2,1,206,0
DI885 3,1,206,0
Events form the SOE device might run under the wrong EVS.
The problem exist for AC 160 1.2, 2.0 and 2.1.

2.3.14 Footer in "Edit Document Texts" unreadable small

It may happen that the footer texts in Edit Document Texts are unreadable small.
The reason is the display driver.
Display drivers with problems:
Display driver S3 Graphics Savage/IX IBM
Date 25.10.2001
Version 5.12.1.7075
The problem may occur also with other display drivers.
Display drivers working properly:
Display driver S3 Graphics Savage/IX Display Driver
Date 11.05.2001
Version 5.12.1.7065
Display driver S3 Graphics Savage/IX IBM
Date 25.10.2001
Version 5.12.1.7080

2.3.15 Edit TIX- and TBX-files with AS100-Edit Editor

File types *.TIX and *.TBX cannot be edited with AS100-Edit Editor. This destroys this type of
files for usage in FCB.
Workaround: Use e.g. NOTEPAD instead.

2.3.16 Error during Installation of Function Chart Builder

It may happen that the Function Chart Builder Installation process starts immediately without
require a license. In this case during the data move process the error -145 occur. The Function
Chart Builder is not installed correctly.
How to proceed:
Delete log file located on folder drive:\Winnt.
Restart the installation process.

2-12 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 2.3.17Message Box during Installation of Function Chart Builder

2.3.17 Message Box during Installation of Function Chart Builder

During the installation of Function Chart Builder probably the following message box appears:

Figure 2-1. HTML Help update

This is correct.
Check this message box.

3BDS 011 103D201 2-13

Function Chart Builder Release Notes
Chapter 2Functionality

2.4 Recommendations
2.4.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,
Bus Configuration Builder
and so on,
(32-bit version components running under Windows NT and Windows 2000)

2.4.2 Correspondence of Force Values to Conditions on Target

The values of the Test Table, first of all in the Values on Target column, and the test values in
the PC Section windows reflect the conditions on the target at the last transfer of values from
the target to the AS 100ES. The date and time of the recent transfer is shown by the time stamp.
The transfer is triggered explicitly by Test | Single Display and Test | Cyclic Display
commands or implicitly after forcing if defined so.
To ensure that values reflect conditions on the target and to avoid getting confused by old
values, either do not select Force Only in the Activate Force Values dialog box when forcing,
or execute also a Test | Single Display (or Test | Cyclic Display) after forcing.

NOTE
A missing time stamp in the Test Table window is a sign for lack of
correspondence of values to the ones on the target.

2.4.3 Un-install Libraries Before Un-installation of FCB

Before un-installing a Function Chart Builder version, it is recommended to un-install the
libraries that are used exclusively by it. For example, un-install AMPL PC and DB Element
Libraries 2.0/0 before un-installing Function Chart Builder 5.0/0.

NOTE
If you un-install a Function Chart Builder version before the un-installation of the
corresponding libraries, also the directories and files will be deleted that were
created at the installation of corresponding libraries.
Though this is not a full un-installation of the libraries: they remain apparently as
installed and registered software.

2-14 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 3.1Installation

Chapter 3 Installation

3.1 Installation
NOTES
Every locally installed Function Chart 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.

3.1.1 Installation Procedure

The installation procedure Function Chart Builder of is described in the Control Builder A
Installation Guide.

3.1.2 Start
You can start the Function Chart Builder from the Application Builder for a given node, circuit,
or type circuit by the following Application Builder menu command:
Tools > Function Chart Builder
You can start the Function Chart Builder from the Application Builder for a given node
structure by the following Application Builder menu command:
Tools > Node Structure Function Chart Builder
If initialization data are available for the Function Chart Builder, you can start it also from the
Windows NT start menu by the following command:
Programs > ABB Industrial IT > Product Suite > Engineer IT > Control Builder A >
Function Chart Builder 6.2
You can open the release notes by the following Windows NT start menu command:
Programs > ABB Industrial IT > Product Suite > Engineer IT > Control Builder A >
Documentation > Function Chart Builder 6.2-0 Release Notes
You can start the utility programs attached to the Function Chart Builder from the Start menu
of Windows NT.
Choose the corresponding commands:
• Programs > ABB Industrial IT > Product Suite > Engineer IT > Control Builder A >
Utilities >PROFIBUS Library Editor 6.2-0
• Programs > ABB Industrial IT > Product Suite > Engineer IT > Control Builder A >
Utilities >Setup Add-Ons 6.2-0
• Programs > ABB Industrial IT > Product Suite > Engineer IT > Control Builder A >
Utilities >CI57x LON Interface Generator 6.2-0
• Programs > ABB Industrial IT > Product Suite > Engineer IT > Control Builder A

3BDS 011 103D201 3-1

Function Chart Builder Release Notes
Chapter 3Installation

>Utilities >MB300 Upload | Uploader FCB

(Windows 2000 only)

3.2 Upgrading
3.2.1 Upgrading of Function Chart Builder

Introduction
If you have older versions of Function Chart Builder installed, the new version will be installed
in parallel.
The objects are processed by Function Chart Builder in internal data representation, in form of
*.ODB files. The internal data representation is FCB version specific.
The exchange format is the source code, which is stable over a large range of FCB versions.
Source code produced by FCB*6.1/0, FCB*5.0/0, ... FCB*4.1/0, and FCB*4.0/0 is compatible
with this version of FCB.

CAUTION
Before you start upgrading you should backup all your application data!
This is for safety reasons.

If you upgrade the Function Chart Builder to a new version and you want to continue working
on “old” objects, it is mandatory to update their internal data representation.

Manual Method for Updating Internal Data Representation

1. Start Function Chart Builder of the current (older) version.
2. Generate source code to convert the data of the current object from the internal data
representation into the exchange format.
3. Exit the (old) Function Chart Builder.
4. Select the corresponding object in the Node, Circuit, or Type Circuit List.
Modify the tool version for it by one of the following commands:
– Click the right mouse button and choose the Modify Tool Versions command in the
context menu.
– Choose the File | Modify command, activate the More… button, and use the Tool
Versions dialog to modify the tool version.
5. Select the (new) Function Chart Builder version you want to work with.
6. Start Function Chart Builder (the version selected in step 5 is started).
7. Initialize the node/circuit/type circuit and backtranslate the source code generated in
step 2.
8. Exit the (new) Function Chart Builder.

3-2 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 3.2.2Upgrading of PROFIBUS Library Editor Data

Automatic Method for Updating Internal Data Representation in APB

In Application Builder, choose the File | Update FCB Data | Project command to update the
internal data representation of all objects of a project.
Or select the one or more objects of a kind of a project and choose the File | Update FCB Data
| Selected command
Also these commands execute the steps suggested for the manual method.

Additional Steps for Advant Controller 100 Series Nodes

To accomplish the—manual or automatic—updating procedure for an application running on an
Advant Controller 100 Series system, you have to:
1. Generate target code.
2. Connect to your controller.
3. Block the application.
4. Load the newly generated application.
5. Deblock the application.
CAUTION
A bumpless on-line change is not supported by this upgrade procedure!

3.2.2 Upgrading of PROFIBUS Library Editor Data

CAUTION
The un-installation of FCB >=4.5/* also deletes data (*.MDB files) generated by
PROFIBUS Library Editor, attached to and delivered with the former.

To preserve these files, copy all *.MDB files from

drive:\AdvaBNT\version\FCB\BIN32\DB_LIB to C:\PB_LIB.
When you open the *.MDB files with PROFIBUS Library Editor 6.2/0, they will be
automatically converted from the old data structure of PROFIBUS Library Editor 1.0 and 2.6/*,
respectively, to the new data structure of PROFIBUS Library Editor 6.2/0.
It is recommended to work with the export file format *.ple in order to store data and update to
new data structure of PROFIBUS Library Editor 6.2/0. Use command File > Export in
PROFIBUS Library Editor to store the files and File > Import to import them in PROFIBUS
Library Editor 6.2/0.

3.2.3 Upgrade of AC 160 1.1 Source Code to AC 160 1.2

Suggested procedure:
1. If it is not started yet, start APB.
2. Create a backup project using File | Copy command of APB.
3. Convert AC 160 1.1 node(s):
a. Select the AC 160 1.1 node to be converted in APB.
b. If not yet existent, generate a new unique pair of DB and PC source code in FCB.

3BDS 011 103D201 3-3

Function Chart Builder Release Notes
Chapter 3Installation

c. If it is not started yet, start the UpgradeS800 tool, for example, by opening the FCB
release directory by the Windows NT Explorer, and double-clicking on the
drive\AdvaBNT\Fcb\62r0\Bin32\UpgradeS800.exe file.
d. Select File | Open of the UpgradeS800 tool and search for the corresponding
node.INI file representing the node, that is, select the
projectroot\project\NODES\node\node.INI file.
e. Select a single pair of DB and PC source code file to be converted. If your node uses
TCs, CIs, or a node structure, you can convert their source code together with the
node’s DB and PC source code.
f. If there are other AC 160 1.1 nodes to be converted, go to step 3.a.
4. Convert AC 160 1.1 circuit(s) on project level:
a. Select File | Open of the UpgradeS800 tool and search for the corresponding CIS file
representing the circuit, that is, select the
projectroot\project\NODES\PR_CI\CIDATA\circuit.CIS file.
b. If there are other AC 160 1.1 circuits to be converted, go to step 4.a.
5. Convert AC 160 1.1 type circuit(s) on project level:
a. Select File | Open of the UpgradeS800 tool and search for the corresponding TCS
file representing the type circuit, that is, select the
fileprojectroot\project\NODES\PR_TC\TCDATA\typecircuit.TCS
b. If there are other AC 160 1.1 type circuits to be converted, got step 5.a.
6. Exit the UpgradeS800 tool by its File | Exit command.
Exit APB by its File | Exit command.

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
Before un-installing a Function Chart Builder version, it is recommended to un-install the
libraries that are used exclusively by it. For example, un-install AMPL PC and DB Element
Libraries 3.1/0 before un-installing Function Chart Builder 6.1/0.
Un-install is provided via the Add/Remove Programs icon in the Control Panel.
To un-install Function Chart Builder, select the Install/Uninstall tab, select the Function Chart
Builder version you want to un-install, e.g., Function Chart Builder 6.1/0 and click
Add/Remove to un-install it.

NOTE
If you un-install Function Chart Builder before the un-installation of the
corresponding AMPL PC and DB Element Libraries, also the directories and files

3-4 3BDS 011 103D201

 Function Chart Builder Release Notes
Section 3.4Un-install

will be deleted that were created at the installation of latter.

e.g.
If you un-install Function Chart Builder 4.5/2 before the un-installation of the
corresponding AMPL PC and DB Element Libraries 1.1/2, also the directories
and files will be deleted that were created at the installation of latter.
If you un-install Function Chart Builder 6.1/0 before the un-installation of the
corresponding AMPL PC and DB Element Libraries 3.1/0, also the directories
and files will be deleted that were created at the installation of latter
Though these are not full un-installations of the corresponding AMPL PC and DB
Element Libraries: the latter remain as installed items in the Install/Uninstall tab
of the Add/Remove Programs Properties dialog of Control Panel.

If you performed a server installation, the entry is called, e.g., Function Chart Builder 6.1/0
Server.
During un-install, Windows NT may present the Remove Shared File? dialog and prompt you
to remove or leave files presumably no longer used by any programs.

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, MSVCP60.DLL, and
ATL.DLL. These file are core components needed by Windows NT or Windows
2000 to run properly. Other files may be deleted as they are used by Control
Builder A components.

3BDS 011 103D201 3-5

Function Chart Builder Release Notes
Chapter 4Miscellaneous

Chapter 4 Miscellaneous

4.1 System Specification

All requirements, prerequisites, and system settings to run Function Chart Builder are described
in the Control Builder A Installation Giude.

4-1 3BDS 011 103D201