Advant® OCS Function Chart Builder

with Master software

Version 6.2

User’s Guide
3BDS 100 595R401
 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
ABB Master and MasterPiece are registered trademarks of ABB Asea Brown Boveri Ltd. Switzerland.
Advant, AdvaBuild, AdvaCommand, and AdvaInform 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.
IndustrialIT, ControlIT, EngineerIT, OperateIT, and Aspect Object are trademarks of ABB Ltd., Switzerland.
Adobe and Acrobat are trademarks of Adobe Systems Incorporated.
IBM and IBM PC are registered trademarks of International Business Machines Corporation.
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 2003

3BSE001264/E

Template: 3BSE001286/E

3BDS 100 595R401

 Function Chart Builder User’s Guide
Table of Contents

TABLE OF CONTENTS
Chapter 1 - Introduction
1.1 General Information................................................................................................. 1-1
1.2 Equipment Requirements......................................................................................... 1-1
1.3 Manual Organization ............................................................................................... 1-2
1.4 Conventions ............................................................................................................. 1-4
1.4.1 General.................................................................................................... 1-4
1.4.2 Keys ........................................................................................................ 1-4
1.4.3 Commands and Menus............................................................................ 1-4
1.5 Related Documentation............................................................................................ 1-5
1.6 Release History ........................................................................................................ 1-8
1.7 Terminology........................................................................................................... 1-10
1.8 Product Overview .................................................................................................. 1-12
1.9 User Interface......................................................................................................... 1-13

Chapter 2 - Installation
2.1 Site Planning Environment ...................................................................................... 2-1
2.2 Setup ........................................................................................................................ 2-1
2.2.1 Software Installation ............................................................................... 2-1
2.2.2 Compatibility of Software and Source Code .......................................... 2-1
2.2.3 Support of Additional Node Types and Options..................................... 2-2
2.3 Shut-down and Start-up Procedures ........................................................................ 2-2
2.4 Product Verification ................................................................................................. 2-2

Chapter 3 - Configuration/Application Building

3.1 Design Considerations - General Working Method................................................. 3-1
3.2 Capacity and Performance ....................................................................................... 3-5
3.3 Application Start-up................................................................................................. 3-6
3.3.1 Start-up of the Function Chart Builder ................................................... 3-6
3.3.2 Start-up of Diagnostics ........................................................................... 3-8
3.3.3 Start-up of Utilities ................................................................................. 3-8

Chapter 4 - Runtime Operation

4.1 Product Operation .................................................................................................... 4-1
4.2 Operating Overview................................................................................................. 4-2
4.2.1 Interaction of Objects.............................................................................. 4-2
4.2.2 Structure of Objects ................................................................................ 4-3
4.2.3 Editors..................................................................................................... 4-3
4.3 Runtime Tutorial...................................................................................................... 4-4

3BDS 100 595R401 i

Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.3.1 Preparations in the Application Builder .................................................. 4-4
4.3.2 Starting the Function Chart Builder ........................................................ 4-5
4.3.3 Using Commands and Help .................................................................... 4-7
4.3.4 Creating the PC Section and a PC Program ............................................ 4-9
4.3.5 Adding PC Elements to PC Program .................................................... 4-11
4.3.6 Inspecting the Function Chart and the Tree Diagram ........................... 4-14
4.3.7 Creating the DB Section and DB Elements .......................................... 4-16
4.3.8 Editing DB Terminal Values ................................................................. 4-18
4.3.9 Deleting DB Elements........................................................................... 4-19
4.3.10 Saving Your Work ................................................................................. 4-19
4.3.11 Working with Type Circuits .................................................................. 4-19
4.3.12 How to Create Type Circuits................................................................. 4-20
4.3.13 Declaring Symbols ................................................................................ 4-20
4.3.14 Using Symbols ...................................................................................... 4-22
4.3.15 Defining Type Circuit Terminals........................................................... 4-23
4.3.16 Connecting PC Terminals ..................................................................... 4-25
4.3.17 Generating Source Code ....................................................................... 4-27
4.3.18 Instantiating a Type Circuit .................................................................. 4-28
4.3.19 Completing the Application Program ................................................... 4-30
4.3.20 Preparing Documentation...................................................................... 4-31
4.3.21 Printing Documentation ........................................................................ 4-33
4.3.22 Working with Node Structures and Circuits ......................................... 4-35
4.3.23 How to Structure Your Application ...................................................... 4-35
4.3.24 Preparing Type Circuits......................................................................... 4-37
4.3.25 Preparing Circuits.................................................................................. 4-38
4.3.26 Completing Node Structure by Circuits................................................ 4-40
4.3.27 Expanding Node Data and Producing Source Code ............................. 4-42
4.3.28 Working On-line with an Application ................................................... 4-43
4.3.29 Preparing an Advant Controller 100 Series Application Off-line......... 4-44
4.3.30 Generating Target Code ........................................................................ 4-45
4.3.31 Preparing the Connection ...................................................................... 4-46
4.3.32 Connecting to the Target ....................................................................... 4-47
4.3.33 Synchronizing the Target ...................................................................... 4-49
4.3.34 Downloading the Target Code............................................................... 4-50
4.3.35 Deblocking/Blocking User Application Program ................................. 4-52
4.3.36 Saving Application in Target................................................................. 4-53
4.3.37 Using the Diagnostics (Diagnosis) Program ......................................... 4-55
4.3.38 About On-line Test Functions ............................................................... 4-57

ii 3BDS 100 595R401

 Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.3.39 Preparing PC Terminals for Display ..................................................... 4-58
4.3.40 Displaying PC Terminal Values On-line............................................... 4-61
4.3.41 Preparing PC Terminals for Forcing ..................................................... 4-65
4.3.42 Forcing PC Terminals On-line.............................................................. 4-67
4.3.43 Preparing DB Terminals for Display .................................................... 4-70
4.3.44 Displaying DB Terminal Values On-line .............................................. 4-72
4.3.45 About Forcing DB Terminals ............................................................... 4-72
4.3.46 About Setting DB Terminal Values ...................................................... 4-73
4.3.47 About On-line Configuration and Programming .................................. 4-74
4.3.48 On-line Editing of PC Program ............................................................ 4-75
4.3.49 On-line Editing of Data Base................................................................ 4-77
4.4 Operating Instructions............................................................................................ 4-81
4.4.1 Basic Procedures................................................................................... 4-81
4.4.1.1 Handling Windows and Navigating ............................... 4-81
4.4.1.2 How to Use the Mouse................................................... 4-82
4.4.1.3 Using the Keyboard Instead of the Mouse..................... 4-86
4.4.2 Preparatory Procedures ......................................................................... 4-89
4.4.2.1 Node or Node Structure?................................................ 4-89
4.4.2.2 Considering Use of Circuits ........................................... 4-90
4.4.2.3 Considering Use of Type Circuits .................................. 4-90
4.4.2.4 Create an Object............................................................. 4-91
4.4.2.5 Start-up of Function Chart Builder ................................ 4-92
4.4.2.6 Password Protection of Nodes, TCs, CIs ....................... 4-94
4.4.2.7 Element Library Handling ............................................. 4-98
4.4.2.8 Initialize an Object ....................................................... 4-101
4.4.2.9 Support of Display Adapters and Printers.................... 4-101
4.4.2.10 Specifying Document Layout ...................................... 4-101
4.4.2.11 Creation of Own Templates ......................................... 4-103
4.4.2.12 Remove an Object ........................................................ 4-105
4.4.2.13 Regenerate an Object ................................................... 4-105
4.4.2.14 Start-up of Diagnostics................................................. 4-106
4.4.2.15 Ending Function Chart Builder and Diagnostics ......... 4-106
4.4.3 Object-specific Programming Procedures .......................................... 4-107
4.4.3.1 Edit a Node................................................................... 4-107
4.4.3.2 Prepare a Type Circuit.................................................. 4-107
4.4.3.3 Edit a Type Circuit ....................................................... 4-109
4.4.3.4 Instantiate a Type Circuit ............................................. 4-109
4.4.3.5 Type Circuits for AC 100 Series Nodes........................4-111

3BDS 100 595R401 iii

Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.4.3.6 Prepare a Circuit ........................................................... 4-113
4.4.3.7 Edit a Circuit ................................................................ 4-114
4.4.3.8 Locate a Circuit ............................................................ 4-114
4.4.3.9 Edit a Node Structure ................................................... 4-116
4.4.3.10 Expand Node Data........................................................ 4-117
4.4.3.11 Update Type Circuit Instances and Located Circuits ... 4-117
4.4.4 Section-specific Programming Procedures ......................................... 4-118
4.4.4.1 Choice of Sections........................................................ 4-118
4.4.4.2 Insert PC Elements ....................................................... 4-119
4.4.4.3 Change the Order of PC Elements................................ 4-120
4.4.4.4 Connect Terminals by Editing the Connection
Definition...................................................................... 4-121
4.4.4.5 Connect Terminals by Dedicated Commands .............. 4-123
4.4.4.6 Connect Terminals by Mouse....................................... 4-124
4.4.4.7 Disconnect a Terminal.................................................. 4-126
4.4.4.8 Delete PC Elements...................................................... 4-126
4.4.4.9 Multiple Selection of PC Elements .............................. 4-127
4.4.4.10 Cut, Copy, and Paste in the PC Section........................ 4-131
4.4.4.11 Create/Edit/Delete a Name ........................................... 4-133
4.4.4.12 Create/Edit/Delete a DB Element................................. 4-135
4.4.4.13 Create/Edit/Delete a Symbol ........................................ 4-136
4.4.4.14 Create/Edit/Delete a TC/CI Terminal........................... 4-137
4.4.4.15 Print Out Documentation.............................................. 4-138
4.4.5 Procedures Concerning Source Code.................................................. 4-140
4.4.5.1 Generate Source Code .................................................. 4-140
4.4.5.2 Backtranslate Source Code to Internal Representation 4-140
4.4.5.3 Source Code Transfer to/from AC 400 Series.............. 4-141
4.4.5.4 Validation of PC Source Code...................................... 4-142
4.4.6 On-line Programming Procedures....................................................... 4-143
4.4.6.1 About On-line and Off-line Modes .............................. 4-143
4.4.6.2 Preparation of Target Code........................................... 4-147
4.4.6.3 About Target Connection.............................................. 4-150
4.4.6.4 Connect the Engineering Station to an
AC 100 Series Target.................................................... 4-151
4.4.6.5 Types of Routing, Diagrams......................................... 4-153
4.4.6.6 Routing Possibilities Depending on Node Type........... 4-161
4.4.6.7 Target Access Protection .............................................. 4-163
4.4.6.8 Load Application to an AC 100 Series Target.............. 4-166

iv 3BDS 100 595R401

 Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.4.6.9 Display (Monitor) PC Terminals in
AC 100 Series Target ................................................... 4-167
4.4.6.10 Force PC Terminals in AC 100 Series Target .............. 4-169
4.4.6.11 Display and Force DB Terminals in
AC 100 Series Target ................................................... 4-171
4.4.6.12 Set DB Terminals in AC 100 Series Target.................. 4-174
4.4.6.13 Edit an AC 100 Series Application On-line................. 4-175
4.4.6.14 Upload Parameter from an AC 100 Series Target........ 4-176
4.4.6.15 Retrieve Application from an AC 100 Series Target ... 4-178
4.4.7 Diagnostic Procedures ........................................................................ 4-181
4.4.7.1 Diagnostic Procedures with the Diagnostics Program . 4-181
4.4.7.2 Diagnostic Procedures with the Diagnosis Program.... 4-186
4.4.8 Rules and Conventions ....................................................................... 4-192
4.4.8.1 Connection Rules ......................................................... 4-192
4.4.8.2 On-line Editing Rules................................................... 4-193
4.4.8.3 Use of Names ............................................................... 4-193
4.4.8.4 About Symbols............................................................. 4-195
4.4.8.5 Use of Symbols ............................................................ 4-197
4.4.8.6 Evaluation of Symbols ................................................. 4-199
4.4.8.7 Values of Symbols........................................................ 4-202
4.4.8.8 Examples of Symbol Usage ......................................... 4-204
4.4.8.9 Use of TC/CI Terminals ............................................... 4-205
4.4.8.10 Page Division Rules ..................................................... 4-206
4.5 Runtime Operation Menus................................................................................... 4-208
4.5.1 Controls in Title Bar, Toolbar and Status Bar..................................... 4-208
4.5.1.1 Controls in Title Bar..................................................... 4-208
4.5.1.2 Controls in Toolbar ...................................................... 4-209
4.5.1.3 Indicators in Status Bar .................................................4-211
4.5.2 Controls in Document Windows......................................................... 4-212
4.5.2.1 *.ODB Window............................................................ 4-212
4.5.2.2 PC Section Window ..................................................... 4-213
4.5.2.3 DB Section Window..................................................... 4-217
4.5.2.4 Symbol Section Window.............................................. 4-220
4.5.2.5 TC/CI Terminal Section Window ................................ 4-222
4.5.2.6 Output Window ............................................................ 4-223
4.5.2.7 Name Table Window.................................................... 4-224
4.5.2.8 Test Table Window....................................................... 4-227
4.5.2.9 Status Report Window ................................................. 4-239
4.5.2.10 Options Report Window............................................... 4-241

3BDS 100 595R401 v

Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.5.2.11 Diagnostics, Error Report Window .............................. 4-242
4.5.3 On Menu Commands, General............................................................ 4-243
4.5.4 File Menu ............................................................................................ 4-244
4.5.4.1 File | Initialize............................................................... 4-244
4.5.4.2 File | Rebuild Element Types........................................ 4-244
4.5.4.3 File | New Section > ..................................................... 4-245
4.5.4.4 File | Open Section > .................................................... 4-246
4.5.4.5 File | Delete Section > .................................................. 4-247
4.5.4.6 File | On-line Mode ...................................................... 4-248
4.5.4.7 File | On-line Preparation Mode ................................... 4-248
4.5.4.8 File | Save ..................................................................... 4-249
4.5.4.9 File | Save and Load ..................................................... 4-249
4.5.4.10 File | Skip Modifications .............................................. 4-249
4.5.4.11 File | Set Password….................................................... 4-250
4.5.4.12 File | Generate Target Code… ...................................... 4-252
4.5.4.13 File | Generate Target Code (External)......................... 4-255
4.5.4.14 File | Generate BCD Data............................................. 4-256
4.5.4.15 File | Generate Source… .............................................. 4-257
4.5.4.16 File | Expand Node Structure ....................................... 4-267
4.5.4.17 File | Check PC Source…............................................. 4-268
4.5.4.18 File | Backtranslate Source… ....................................... 4-269
4.5.4.19 File | Backtranslate Target Code................................... 4-277
4.5.4.20 File | Export DB Section............................................... 4-279
4.5.4.21 File | Import DB Section............................................... 4-280
4.5.4.22 File | Print… ................................................................. 4-281
4.5.4.23 File | Print Setup… ....................................................... 4-295
4.5.4.24 File | Page Setup… ....................................................... 4-296
4.5.4.25 File | Exit ...................................................................... 4-297
4.5.5 Edit Menu............................................................................................ 4-299
4.5.5.1 Edit | Undo.................................................................... 4-299
4.5.5.2 Edit | Redo .................................................................... 4-299
4.5.5.3 Edit | Create… .............................................................. 4-299
4.5.5.4 Edit | Cut....................................................................... 4-311
4.5.5.5 Edit | Copy .................................................................... 4-311
4.5.5.6 Edit | Paste… ................................................................ 4-311
4.5.5.7 Edit | Delete .................................................................. 4-318
4.5.5.8 Edit | Find… ................................................................. 4-319
4.5.5.9 Edit | Process Conflicts................................................. 4-320

vi 3BDS 100 595R401

 Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.5.5.10 Edit | Call Parameters…............................................... 4-321
4.5.5.11 Edit | Name ….............................................................. 4-322
4.5.5.12 Edit | Delete Name ....................................................... 4-323
4.5.5.13 Edit | DB Terminal Values…........................................ 4-323
4.5.5.14 Edit | Symbol…............................................................ 4-326
4.5.5.15 Edit | Symbol Values… ................................................ 4-328
4.5.5.16 Edit | TC/CI Terminal…............................................... 4-331
4.5.5.17 Edit | Upload… ............................................................ 4-332
4.5.5.18 Edit | Document Texts… .............................................. 4-335
4.5.6 View Menu.......................................................................................... 4-335
4.5.6.1 View | Function Chart .................................................. 4-335
4.5.6.2 View | Tree - All Elements ........................................... 4-336
4.5.6.3 View | Tree - Structure Elements ................................. 4-336
4.5.6.4 View | Tree - Top of Page Elements............................. 4-336
4.5.6.5 View | PC Pane | Next .................................................. 4-337
4.5.6.6 View | PC Pane | Previous ............................................ 4-337
4.5.6.7 View | PC Pane | Split Horizontally ............................. 4-337
4.5.6.8 View | PC Pane | Split Vertically .................................. 4-337
4.5.6.9 View | Zoom… ............................................................. 4-337
4.5.6.10 View | Prepared Variables ............................................ 4-337
4.5.6.11 View | Item Designations ............................................. 4-338
4.5.6.12 View | Phys. Addresses ................................................ 4-338
4.5.6.13 View | PARDAT Unit and Init Value............................ 4-338
4.5.6.14 View | Cross Reference ................................................ 4-339
4.5.6.15 View | Cross Ref. of sel. DB Elem............................... 4-341
4.5.6.16 View | Cross Ref. of sel. PC Elem ............................... 4-341
4.5.6.17 View | Sort by Name .................................................... 4-342
4.5.6.18 View | Sort by Number................................................. 4-342
4.5.6.19 View | Sort by Item Designation .................................. 4-342
4.5.6.20 View | Hide System DB Elements ............................... 4-342
4.5.6.21 View | Toolbar .............................................................. 4-342
4.5.6.22 View | Status Bar .......................................................... 4-342
4.5.7 Options Menu ..................................................................................... 4-343
4.5.7.1 Options | Preferences…................................................ 4-343
4.5.7.2 Options | Workspace…................................................. 4-348
4.5.7.3 Options | Cycle Times… .............................................. 4-350
4.5.7.4 Options | Language > ................................................... 4-352
4.5.8 PC-Section Menu................................................................................ 4-352

3BDS 100 595R401 vii

Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.5.8.1 PC-Section | Goto Element > ....................................... 4-352
4.5.8.2 PC-Section | Goto Page > ............................................. 4-354
4.5.8.3 PC-Section | Select… ................................................... 4-355
4.5.8.4 PC-Section | Execution Order > ................................... 4-356
4.5.8.5 PC-Section | Modify Item Destination… ..................... 4-356
4.5.8.6 PC-Section | Renumber Lower Level........................... 4-357
4.5.8.7 PC-Section | Renumber … ........................................... 4-357
4.5.8.8 PC-Section | Computing Time > .................................. 4-358
4.5.8.9 PC-Section | Memory Calculation>.............................. 4-362
4.5.8.10 PC-Section | Page Layout >.......................................... 4-364
4.5.9 PC-Terminal Menu.............................................................................. 4-373
4.5.9.1 PC-Terminal | Goto > ................................................... 4-373
4.5.9.2 PC-Terminal | Mark ...................................................... 4-374
4.5.9.3 PC-Terminal | Unmark.................................................. 4-374
4.5.9.4 PC-Terminal | Connect… (common)............................ 4-374
4.5.9.5 PC-Terminal | Connect Selected >................................ 4-377
4.5.9.6 PC-Terminal | Virtual Connections…........................... 4-381
4.5.9.7 PC-Terminal | Disconnect…......................................... 4-382
4.5.9.8 PC-Terminal | Unit > .................................................... 4-383
4.5.9.9 PC-Terminal | Select for Display >............................... 4-385
4.5.9.10 PC-Terminal | Force Value > ........................................ 4-385
4.5.9.11 PC-Terminal | Invert ..................................................... 4-387
4.5.9.12 PC-Terminal | Insert...................................................... 4-387
4.5.9.13 PC-Terminal | Delete .................................................... 4-387
4.5.10 Target Menu ........................................................................................ 4-388
4.5.10.1 Target | Connect…........................................................ 4-388
4.5.10.2 Target | Disconnect ....................................................... 4-391
4.5.10.3 Target | Deblock Program............................................. 4-391
4.5.10.4 Target | Block Program................................................. 4-391
4.5.10.5 Target | Load Application ............................................. 4-391
4.5.10.6 Target | Upload Application ......................................... 4-392
4.5.10.7 Target | Save in PROM ................................................. 4-392
4.5.10.8 Target | Update Slave.................................................... 4-393
4.5.10.9 Target | Clear PROM .................................................... 4-393
4.5.10.10 Target | Restart.............................................................. 4-393
4.5.10.11 Target | Set Date and Time… ....................................... 4-394
4.5.10.12 Target | Set Password…................................................ 4-395
4.5.10.13 Target | Application Checksum… ................................ 4-396

viii 3BDS 100 595R401

 Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.5.10.14 Target | Report Status ................................................... 4-397
4.5.10.15 Target | Report Options ................................................ 4-397
4.5.10.16 Target | Report Attributes ............................................. 4-397
4.5.10.17 Target | Diagnostics ...................................................... 4-397
4.5.11 Test Menu ........................................................................................... 4-398
4.5.11.1 Test | Single Display..................................................... 4-398
4.5.11.2 Test | Cyclic Display .................................................... 4-398
4.5.11.3 Test | Stop Display........................................................ 4-399
4.5.11.4 Test | Set Cycletime….................................................. 4-399
4.5.11.5 Test | Set Trigger… ...................................................... 4-400
4.5.11.6 Test | Activate Force Values ......................................... 4-401
4.5.11.7 Test | Deactivate Force Values ..................................... 4-402
4.5.11.8 Test | Activate All Force Values................................... 4-403
4.5.11.9 Test | Deactivate All Force Values ............................... 4-404
4.5.11.10 Test | Upload DB Force List......................................... 4-404
4.5.11.11 Test | Set DB Value…................................................... 4-404
4.5.11.12 Test | Import (Test Values) … ...................................... 4-405
4.5.11.13 Test | Export (Test Values) … ...................................... 4-407
4.5.12 Window Menu .................................................................................... 4-408
4.5.12.1 Window | New Window ............................................... 4-408
4.5.12.2 Window | Cascade ........................................................ 4-408
4.5.12.3 Window | Tile Horizontally.......................................... 4-408
4.5.12.4 Window | Tile Vertically .............................................. 4-408
4.5.12.5 Window | Arrange Icons............................................... 4-408
4.5.12.6 Window | Resize........................................................... 4-408
4.5.12.7 Window | Slide ............................................................. 4-409
4.5.12.8 Window | Close… ........................................................ 4-409
4.5.12.9 Window | Close All ...................................................... 4-410
4.5.12.10 Window | *.ODB.......................................................... 4-410
4.5.12.11 Window | Output .......................................................... 4-410
4.5.12.12 Window | Name Table.................................................. 4-410
4.5.12.13 Window | Test Table..................................................... 4-410
4.5.12.14 Window | 1, 2, … (Activate Section Windows) ........... 4-410
4.5.13 Help Menu ...........................................................................................4-411
4.5.13.1 Help | Contents ..............................................................4-411
4.5.13.2 Help | On Context..........................................................4-411
4.5.13.3 Help | How to Use Help ................................................4-411
4.5.13.4 Help | On Node…..........................................................4-411

3BDS 100 595R401 ix

Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.5.13.5 Help | DB Element Reference ...................................... 4-412
4.5.13.6 Help | PC Element Reference ....................................... 4-412
4.5.13.7 Help | Other Reference ................................................. 4-412
4.5.13.8 Help | Release Notes..................................................... 4-413
4.5.13.9 Help | About Function Chart Builder… ....................... 4-413
4.5.14 Controls of Diagnostics....................................................................... 4-414
4.5.14.1 Controls in Title Bar of Diagnostics............................. 4-414
4.5.14.2 Controls in Toolbar of Diagnostics............................... 4-414
4.5.14.3 Indicators in Status Bar of Diagnostics ........................ 4-415
4.5.15 Controls in Document Windows of Diagnostics................................. 4-416
4.5.15.1 Error Report Window ................................................... 4-416
4.5.15.2 Module List Window.................................................... 4-418
4.5.15.3 Module Diagnostics Window ....................................... 4-419
4.5.16 Menu Commands of Diagnostics ........................................................ 4-421
4.5.17 File Menu of Diagnostics .................................................................... 4-421
4.5.17.1 File | Save As................................................................ 4-421
4.5.17.2 File | Log....................................................................... 4-423
4.5.17.3 File | Logfile Setup ....................................................... 4-423
4.5.17.4 File | Print ..................................................................... 4-424
4.5.17.5 File | Print Setup ........................................................... 4-426
4.5.17.6 File | Exit ...................................................................... 4-427
4.5.18 View Menu of Diagnostics.................................................................. 4-427
4.5.18.1 View | Toolbar .............................................................. 4-427
4.5.18.2 View | Status Bar .......................................................... 4-427
4.5.19 Target Menu of Diagnostics ................................................................ 4-428
4.5.19.1 Target | Report Errors ................................................... 4-428
4.5.19.2 Target | List Modules .................................................... 4-428
4.5.19.3 Target | Diagnose Module............................................. 4-428
4.5.19.4 Target | Delete Reported Errors * ................................. 4-429
4.5.20 Window Menu of Diagnostics............................................................. 4-429
4.5.20.1 Window | Cascade ........................................................ 4-430
4.5.20.2 Window | Tile Horizontally .......................................... 4-430
4.5.20.3 Window | Tile Vertically............................................... 4-430
4.5.20.4 Window | Arrange Icons............................................... 4-430
4.5.20.5 Window | Resize ........................................................... 4-430
4.5.20.6 Window | 1, 2, … (Activate Diagnostics Windows) .... 4-430
4.5.21 Help Menu of Diagnostics .................................................................. 4-430
4.5.21.1 Help | Contents ............................................................. 4-430

x 3BDS 100 595R401

 Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.5.21.2 Help | On Context......................................................... 4-431
4.5.21.3 Help | How to Use Help ............................................... 4-431
4.5.21.4 Help | About Diagnostics ............................................. 4-431
4.5.22 Controls of Diagnosis ......................................................................... 4-431
4.5.22.1 Controls in Title Bar of Diagnosis ............................... 4-432
4.5.22.2 Controls in Toolbar of Diagnosis ................................. 4-432
4.5.22.3 Indicators in Status Bar of Diagnosis........................... 4-433
4.5.23 Controls in Document Windows of Diagnosis ................................... 4-434
4.5.23.1 Status Report Window of Diagnosis ............................ 4-434
4.5.23.2 Error Report Window................................................... 4-436
4.5.23.3 Module List Window ................................................... 4-438
4.5.23.4 Module Diagnosis Window.......................................... 4-440
4.5.23.5 Channel Diagnosis Window......................................... 4-444
4.5.23.6 Output Window of Diagnosis....................................... 4-447
4.5.24 Menu Commands of Diagnosis........................................................... 4-447
4.5.25 File Menu of Diagnosis....................................................................... 4-447
4.5.25.1 File | Save As ............................................................... 4-447
4.5.25.2 File | Log ...................................................................... 4-449
4.5.25.3 File | Logfile Setup....................................................... 4-449
4.5.25.4 File | Print..................................................................... 4-450
4.5.25.5 File | Print Setup........................................................... 4-451
4.5.25.6 File | Exit ...................................................................... 4-452
4.5.26 Edit Menu of Diagnosis ...................................................................... 4-453
4.5.26.1 Edit | Copy.................................................................... 4-453
4.5.27 View Menu of Diagnosis .................................................................... 4-453
4.5.27.1 View | Status Report..................................................... 4-453
4.5.27.2 View | Error Report ...................................................... 4-453
4.5.27.3 View | Module List....................................................... 4-453
4.5.27.4 View | Module Diagnosis ............................................. 4-453
4.5.27.5 View | Channel Diagnosis ............................................ 4-455
4.5.27.6 View | Toolbar .............................................................. 4-457
4.5.27.7 View | Status Bar .......................................................... 4-457
4.5.28 Target Menu of Diagnosis................................................................... 4-458
4.5.28.1 Target | Delete Reported Errors *................................. 4-458
4.5.28.2 Target | Delete All Reported Errors.............................. 4-458
4.5.29 Window Menu of Diagnosis ............................................................... 4-459
4.5.29.1 Window | Cascade ........................................................ 4-459
4.5.29.2 Window | Tile Horizontally.......................................... 4-459

3BDS 100 595R401 xi

Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
4.5.29.3 Window | Tile Vertically............................................... 4-459
4.5.29.4 Window | Arrange Icons............................................... 4-459
4.5.29.5 Window | Resize ........................................................... 4-460
4.5.29.6 Window | Close All Diagnosis ..................................... 4-460
4.5.30 Help Menu of Diagnosis ..................................................................... 4-460
4.5.30.1 Help | Contents ............................................................. 4-460
4.5.30.2 Help | On Context......................................................... 4-460
4.5.30.3 Help | How to Use Help................................................ 4-460
4.5.30.4 Help | About Diagnosis ................................................ 4-460

Chapter 5 - Maintenance
5.1 Preventive Maintenance ........................................................................................... 5-1
5.2 Error Messages......................................................................................................... 5-1
5.3 Fault Finding and User Repair ................................................................................. 5-1
5.3.1 Reporting Problems................................................................................. 5-1
5.3.2 What to Do at Program Halts .................................................................. 5-3

Appendix A - Function Chart Builder Files

A.1 FCB Directory Structure ......................................................................................... A-1
A.1.1 Release Directory Structure ................................................................... A-1
A.1.2 Project Directory Structure .................................................................... A-2
A.2 Short Description of FCB Files............................................................................... A-3

Appendix B - Data Flow in Function Chart Builder

B.1 Working with an AC 400 or MP 200/1 Node.......................................................... B-1
B.2 Instantiating Type Circuits in a Node ..................................................................... B-2
B.3 Working on Type Circuits ....................................................................................... B-3
B.4 Working on Circuits ................................................................................................ B-4
B.5 Working on Node Structures ................................................................................... B-5
B.6 Expanding Node Data ............................................................................................. B-6
B.7 Advant Controller 100 Series Target Code Generation .......................................... B-7
B.8 Upgrading to New FCB Release, Regenerating Objects ........................................ B-8

Appendix C - Syntax of Symbolic Expressions and Formulas

C.1 Syntax of Symbolic Expressions............................................................................. C-1
C.2 Syntax of Symbolic Formulas................................................................................. C-2

Appendix D - Syntax of TC, CI, and NS Source Code

D.1 General .................................................................................................................... D-1
D.1.1 Introduction ............................................................................................ D-1

xii 3BDS 100 595R401

 Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
D.1.2 Conventions ............................................................................................D-1
D.1.3 Implementation .......................................................................................D-3
D.1.4 Release History .......................................................................................D-4
D.2 Syntax of TC Source Code ......................................................................................D-5
D.2.1 Lexical Part .............................................................................................D-5
D.2.1.1 Simple Character Sets ......................................................D-5
D.2.1.2 Compound Character Sets................................................D-5
D.2.1.3 Tokens ..............................................................................D-6
D.2.1.4 Keywords .........................................................................D-6
D.2.1.5 Comments ........................................................................D-6
D.2.1.6 Specials ............................................................................D-6
D.2.2 Syntactical Part (TCS File) .....................................................................D-7
D.2.3 On TC Source Code Syntax..................................................................D-13
D.2.3.1 On Variants.....................................................................D-13
D.2.3.2 Placement of Variants.....................................................D-14
D.2.3.3 On Loops........................................................................D-14
D.2.3.4 Placement of Loops........................................................D-14
D.2.3.5 Symbols in Symbol Section of *.TCS and Their Scope D-15
D.2.3.6 On Nested Symbolic Expressions ..................................D-15
D.2.3.7 On Formulas...................................................................D-15
D.3 Syntax of CI Source Code .....................................................................................D-16
D.3.1 Lexical Part ...........................................................................................D-16
D.3.1.1 Simple Character Sets ....................................................D-16
D.3.1.2 Compound Character Sets..............................................D-17
D.3.1.3 Tokens ............................................................................D-17
D.3.1.4 Keywords .......................................................................D-17
D.3.1.5 Comments ......................................................................D-18
D.3.1.6 Specials ..........................................................................D-18
D.3.2 Syntactical Part (CIS File) ....................................................................D-18
D.3.3 On CI Source Code Syntax...................................................................D-23
D.3.3.1 Variants and Loops.........................................................D-23
D.3.3.2 Symbols in Symbol Section of *.CIS and Their Scope .D-24
D.3.3.3 On Nested Symbolic Expressions ..................................D-25
D.3.3.4 On Formulas...................................................................D-25
D.3.3.5 TCs Instantiated in CI ....................................................D-25
D.4 Syntax of NS Source Code ....................................................................................D-26
D.4.1 Lexical Part ...........................................................................................D-26
D.4.1.1 Simple Character Sets ....................................................D-26

3BDS 100 595R401 xiii

Function Chart Builder User’s Guide
Table of Contents

CONTENTS (continued)
D.4.1.2 Compound Character Sets ............................................. D-27
D.4.1.3 Tokens............................................................................ D-27
D.4.1.4 Keywords....................................................................... D-27
D.4.1.5 Comments...................................................................... D-28
D.4.1.6 Specials.......................................................................... D-28
D.4.2 Syntactical Part (NSS File) .................................................................. D-28
D.4.3 On NS Source Code Syntax ................................................................. D-33
D.4.3.1 Variants and Loops ........................................................ D-33
D.4.3.2 Symbols in Symbol Section of *.NSS and Their Scope D-33
D.4.3.3 On Nested Symbolic Expressions ................................. D-33
D.4.3.4 On Formulas .................................................................. D-33
D.4.3.5 TCs Instantiated in NS .................................................. D-34
D.4.3.6 CIs Located in NS ......................................................... D-35

Appendix E - Syntax of Names

E.1 Syntax of PC Names ................................................................................................E-1
E.1.1 General ....................................................................................................E-1
E.1.2 Rules........................................................................................................E-1
E.1.3 Scope .......................................................................................................E-1
E.2 Character Set of PC Names......................................................................................E-2
E.3 Syntax of DB Names................................................................................................E-5
E.3.1 General ....................................................................................................E-5
E.3.2 Rules........................................................................................................E-5
E.3.3 Scope .......................................................................................................E-5
E.4 Character Set of DB Names .....................................................................................E-6

Appendix F - Syntax of Template Files

F.1 General .....................................................................................................................F-1
F.2 Template File Syntax................................................................................................F-1
F.3 Hints .........................................................................................................................F-6

Appendix G - Configuration of AdvaBuild Communicator

G.1 Introduction ............................................................................................................. G-1
G.2 Assignment of Access and Launch Permissions..................................................... G-1
G.3 Access Right (Privilege) of AF 100 Interface Software ......................................... G-8
G.4 User On Remote Engineering Station ..................................................................... G-8

Appendix H - Glossary

xiv 3BDS 100 595R401

 Function Chart Builder
Table of Contents

ILLUSTRATIONS
Figure 1-1. Documentation Structure Chart of the Function Chart Builder.................... 1-2
Figure 3-1. Assigning Circuits to Process Devices ......................................................... 3-1
Figure 3-2. Referencing Type Circuits ........................................................................... 3-2
Figure 3-3. Locating Circuits in Node Structures ........................................................... 3-3
Figure 3-4. Resolving References and Expanding Node Data........................................ 3-4
Figure 3-5. Warning on Missing Initialization Data ....................................................... 3-6
Figure 3-6. Application Window, Initial State ................................................................ 3-7
Figure 3-7. Page Setup .................................................................................................... 3-7
Figure 4-1. FCB General Data Flow ............................................................................... 4-2
Figure 4-2. Function Chart Builder Window Opened ..................................................... 4-5
Figure 4-3. Initial Page Setup Dialog Box ...................................................................... 4-6
Figure 4-4. TT_10_PW.ODB Initialized......................................................................... 4-6
Figure 4-5. Help Topics Window .................................................................................... 4-7
Figure 4-6. Help Information on a Command................................................................. 4-8
Figure 4-7. Defining PC1 as New PC Program .............................................................. 4-9
Figure 4-8. Creating PCPGM........................................................................................ 4-10
Figure 4-9. Tree Diagram and Function Chart of PC1...................................................4-11
Figure 4-10. Setting Call Parameters of CONTRM........................................................ 4-12
Figure 4-11. CONTRM with Call Parameters ................................................................ 4-13
Figure 4-12. Inserting New Page Division...................................................................... 4-14
Figure 4-13. Modifying Headline of Page 3 ................................................................... 4-15
Figure 4-14. Tree Diagram of PC1, Full Structure.......................................................... 4-15
Figure 4-15. Opening the DB Section Window .............................................................. 4-16
Figure 4-16. Creating DI* ............................................................................................... 4-17
Figure 4-17. Editing DB Terminal Values of DI2.4 ........................................................ 4-18
Figure 4-18. Creating Symbol <CH_NR> ...................................................................... 4-21
Figure 4-19. Symbol Section of TC_10_T1.................................................................... 4-21
Figure 4-20. Creating DI<MOD_NR>.<CH_NR> ......................................................... 4-22
Figure 4-21. Creating a Type Circuit Input Terminal...................................................... 4-23
Figure 4-22. Creating a Type Circuit Output Terminal ................................................... 4-24
Figure 4-23. TC/CI Terminal Section Window............................................................... 4-24
Figure 4-24. Connecting to a Constant............................................................................ 4-25
Figure 4-25. Pane with Function Chart of TC_10_T1 .................................................... 4-26
Figure 4-26. Generate TC Source Code Dialog Box ...................................................... 4-27
Figure 4-27. Output During Code Generation of TC_10_T1.......................................... 4-27
Figure 4-28. Inserting TC_10_T1 ................................................................................... 4-28
Figure 4-29. Edit Symbol Values of TC_10_T1 ............................................................. 4-29
Figure 4-30. Pane with Function Chart of PC1 of TT_10_PW, Final Stage................... 4-30

3BDS 100 595R401 xxix

Function Chart Builder
Table of Contents

ILLUSTRATIONS (continued)
Figure 4-31. Generating Source Code of TT_10_PW..................................................... 4-31
Figure 4-32. A Document Page ....................................................................................... 4-32
Figure 4-33. Editing the Footer for Documents of PC1 .................................................. 4-33
Figure 4-34. Print Dialog Box ......................................................................................... 4-34
Figure 4-35. Print PC Section Dialog Box ...................................................................... 4-34
Figure 4-36. Structure of the Node WATER.................................................................... 4-36
Figure 4-37. Type Circuit PUSHB .................................................................................. 4-36
Figure 4-38. Value Substitution via <DIMODULE> and <DI_NR> .............................. 4-39
Figure 4-39. PC Diagram, Draft ...................................................................................... 4-43
Figure 4-40. Generate Target Code Dialog Box .............................................................. 4-45
Figure 4-41. Changes in Sections, Warning .................................................................... 4-45
Figure 4-42. Output Window in Foreground ................................................................... 4-46
Figure 4-43. Connect Target Dialog Box ........................................................................ 4-47
Figure 4-44. Target Not Reached, Warning..................................................................... 4-48
Figure 4-45. Status Report After Target | Connect .......................................................... 4-48
Figure 4-46. Options Report............................................................................................ 4-49
Figure 4-47. Set Date and Time Dialog Box, Phase 1..................................................... 4-49
Figure 4-48. Set Date and Time Dialog Box, Phase 2..................................................... 4-50
Figure 4-49. Confirm Start Download............................................................................. 4-50
Figure 4-50. Confirm Switching Directly to On-line Mode............................................ 4-51
Figure 4-51. Warning at Switching to On-line Mode ...................................................... 4-51
Figure 4-52. On-line Mode Indication in Title ................................................................ 4-51
Figure 4-53. Output Window After Download................................................................ 4-52
Figure 4-54. Status Report After Download.................................................................... 4-52
Figure 4-55. Confirm Deblock Program.......................................................................... 4-53
Figure 4-56. Status Report After Deblock....................................................................... 4-53
Figure 4-57. Confirm Save in PROM.............................................................................. 4-54
Figure 4-58. Saved in PROM, Message .......................................................................... 4-54
Figure 4-59. Status Report After Save in PROM ............................................................ 4-54
Figure 4-60. Status Report with Errors Detected ............................................................ 4-55
Figure 4-61. Error Report - No Battery Plugged ............................................................. 4-56
Figure 4-62. PC Terminal Selected for Display, On-line Preparation Mode................... 4-59
Figure 4-63. Entering On-line Mode, Warning ............................................................... 4-60
Figure 4-64. PC Terminal Selected for Display, On-line Mode ...................................... 4-60
Figure 4-65. Monitored Values in Function Chart........................................................... 4-61
Figure 4-66. Create/Edit Table Entry Dialog Box ........................................................... 4-62
Figure 4-67. Test Table with PC Display Values............................................................. 4-63
Figure 4-68. Cyclic Display............................................................................................. 4-64

xxx 3BDS 100 595R401

 Function Chart Builder
Table of Contents

ILLUSTRATIONS (continued)
Figure 4-69. Create/Edit Force Value Dialog Box .......................................................... 4-66
Figure 4-70. Chaining Force and Single Display............................................................ 4-67
Figure 4-71. Function Chart with Forced and Monitored Values ................................... 4-68
Figure 4-72. Test Table with PC Force Values................................................................ 4-69
Figure 4-73. Confirmation of Force Deactivation........................................................... 4-69
Figure 4-74. Change in Test Table, Warning................................................................... 4-69
Figure 4-75. Preparing DB Values in Test Table, On-line Preparation Mode................. 4-71
Figure 4-76. Monitored DB Values in Test Table Window............................................. 4-72
Figure 4-77. Modified PC Program................................................................................. 4-76
Figure 4-78. Confirmation of On-line PC Modification ................................................. 4-76
Figure 4-79. Output Window After Save and Load of PC Change................................. 4-77
Figure 4-80. Modified DB Section.................................................................................. 4-78
Figure 4-81. Attempt to Change in a Second Execution Unit, Warning ......................... 4-78
Figure 4-82. Confirmation of On-line DB Modification................................................. 4-79
Figure 4-83. Output Window After Save and Load of DB Change ................................ 4-79
Figure 4-84. Connecting DB Terminal On-line .............................................................. 4-80
Figure 4-85. Confirmation of Disconnection .................................................................. 4-80
Figure 4-86. Warning, Initialization Data Missing.......................................................... 4-92
Figure 4-87. FCB Started for a Node .............................................................................. 4-93
Figure 4-88. Initial Page Setup Dialog Box .................................................................... 4-94
Figure 4-89. Set Initial ODB Password........................................................................... 4-95
Figure 4-90. ODB Password Query at FCB Start-up ...................................................... 4-95
Figure 4-91. Change ODB Password .............................................................................. 4-97
Figure 4-92. Clear ODB Password.................................................................................. 4-98
Figure 4-93. Example of Circuit Check .......................................................................... 4-99
Figure 4-94. Example of Library Differences ............................................................... 4-100
Figure 4-95. Contiguous Selection of PC Elements on Same Level............................. 4-129
Figure 4-96. Selection of Whole Executable Unit ........................................................ 4-129
Figure 4-97. Selection of Partial Subtree on Lower Level............................................ 4-130
Figure 4-98. Impossible Disjoint Selection of PC Elements......................................... 4-130
Figure 4-99. Non-allowed Selection from Lower Level to Higher Level..................... 4-131
Figure 4-100. FCB Modes (States) and Transitions........................................................ 4-145
Figure 4-101. Target Code Generation Protocol (Example) ........................................... 4-149
Figure 4-102. Point-to-point Connection via COMx, Topology ..................................... 4-155
Figure 4-103. Point-to-point Connection via COMx, Setting......................................... 4-155
Figure 4-104. Routing via COMx, AC 100 Series Node, AF 100, Topology................. 4-155
Figure 4-105. Routing via COMx, AC 100 Series Node, AF 100, Setting..................... 4-156

3BDS 100 595R401 xxxi

Function Chart Builder
Table of Contents

ILLUSTRATIONS (continued)
Figure 4-106. Routing via COMx, AC 100 Series, AF 100, 2nd AC 100 Series,
2nd AF 100, Topology .............................................................................. 4-156
Figure 4-107. Routing via COMx, AC 100 Series, AF 100, 2nd AC 100 Series,
2nd AF 100, Setting .................................................................................. 4-156
Figure 4-108. Routing via X3, AC 4xx, AF 100, Topology............................................ 4-157
Figure 4-109. Routing via X3, AC 4xx, AF 100, Setting................................................ 4-157
Figure 4-110. Routing via X3, AC 4xx, AF 100, AC 100 Series Node, 2nd AF 100,
Topology ................................................................................................... 4-157
Figure 4-111. Routing via X3, AC 4xx, AF 100, AC 100 Series Node, 2nd AF 100,
Setting ....................................................................................................... 4-158
Figure 4-112. Routing via X3, AC 4xx, RCOM Net, Topology ..................................... 4-158
Figure 4-113. Routing via X3, AC 4xx, RCOM Net, Setting ......................................... 4-158
Figure 4-114. Routing via X3, Several AC 4xx Connected by MB 300, AF 100,
Topology ................................................................................................... 4-159
Figure 4-115. Routing via X3, Several AC 4xx Connected by MB 300, AF 100,
Setting ....................................................................................................... 4-159
Figure 4-116. Routing via X3, Several AC 4xx Connected by MB 300, AF 100,
AC 100 Series Node, 2nd AF 100, Topology ........................................... 4-159
Figure 4-117. Routing via X3, Several AC 4xx Connected by MB 300, AF 100,
AC 100 Series Node, 2nd AF 100, Setting ............................................... 4-160
Figure 4-118. Routing via X3, Several AC 4xx Connected by MB 300, RCOM Net,
Topology ................................................................................................... 4-160
Figure 4-119. Routing via X3, Several AC 4xx Connected by MB 300, RCOM Net,
Setting ....................................................................................................... 4-160
Figure 4-120. Routing via AF 100, Topology ................................................................. 4-161
Figure 4-121. Routing via AF 100, Setting ..................................................................... 4-161
Figure 4-122. Set Initial Password on Target .................................................................. 4-163
Figure 4-123. Target Password Query at Target Connection........................................... 4-164
Figure 4-124. Change Password on Target...................................................................... 4-164
Figure 4-125. Clear Password on Target ......................................................................... 4-165
Figure 4-126. Overview of Diagnostics Commands and Data Transfer in Diagnostics
Program..................................................................................................... 4-182
Figure 4-127. Accessing Diagnostic Information with Diagnostics Program, Example. 4-185
Figure 4-128. Overview of Diagnosis Commands and Data Transfer in Diagnosis
Program..................................................................................................... 4-187
Figure 4-129. Accessing Diagnostic Information with Diagnosis Program, Example ... 4-190
Figure 4-130. Inheritance of Symbol Values Between Neighboring Levels ................... 4-200
Figure 4-131. Toolbar of the Function Chart Builder...................................................... 4-209
Figure 4-132. Status Bar of the Function Chart Builder.................................................. 4-211
Figure 4-133. *.ODB Window ........................................................................................ 4-212

xxxii 3BDS 100 595R401

 Function Chart Builder
Table of Contents

ILLUSTRATIONS (continued)
Figure 4-134. PC Section Window with Three Panes..................................................... 4-214
Figure 4-135. PC Pane Toolbar ....................................................................................... 4-215
Figure 4-136. DB Section Window ................................................................................. 4-217
Figure 4-137. Symbol Section Window .......................................................................... 4-220
Figure 4-138. TC/CI Terminal Section Window............................................................. 4-222
Figure 4-139. Output Window ........................................................................................ 4-224
Figure 4-140. Name Table Window ................................................................................ 4-225
Figure 4-141. Test Table Window ................................................................................... 4-227
Figure 4-142. Detailed Value Display ............................................................................. 4-228
Figure 4-143. Trend Recording Dialog Box ................................................................... 4-233
Figure 4-144. Setup of Trend Recording......................................................................... 4-234
Figure 4-145. Color Table ............................................................................................... 4-235
Figure 4-146. Time - Scale.............................................................................................. 4-236
Figure 4-147. Trigger Setup ............................................................................................ 4-237
Figure 4-148. Value List of Trend Recording ................................................................. 4-238
Figure 4-149. Status Report ............................................................................................ 4-239
Figure 4-150. Options Report.......................................................................................... 4-241
Figure 4-151. Application Window of Diagnosis, Error Report ..................................... 4-242
Figure 4-152. Menu Bar of the Function Chart Builder.................................................. 4-243
Figure 4-153. New PC Program...................................................................................... 4-245
Figure 4-154. Open PC Program..................................................................................... 4-246
Figure 4-155. Delete PC Program ................................................................................... 4-247
Figure 4-156. Set Password in ODB ............................................................................... 4-251
Figure 4-157. Generate Target Code ............................................................................... 4-252
Figure 4-158. Generate Target Code with Support for Application Retrieval ................ 4-253
Figure 4-159. Generate BCD Data.................................................................................. 4-256
Figure 4-160. Generate Source Code .............................................................................. 4-258
Figure 4-161. Save PC Source Code As ........................................................................ 4-259
Figure 4-162. Select PC Program(s) .............................................................................. 4-261
Figure 4-163. Save DB Souce Code As .......................................................................... 4-262
Figure 4-164. Generate TC Source Code ........................................................................ 4-266
Figure 4-165. Check PC Source Code ............................................................................ 4-268
Figure 4-166. Backtranslate Source Code....................................................................... 4-270
Figure 4-167. Open PC Source Code Files(s) ................................................................. 4-271
Figure 4-168. Select PC Programs(s) for Backtranslate ................................................ 4-273
Figure 4-169. Open DB Source Code File(s) ................................................................. 4-274
Figure 4-170. Export DB Section.................................................................................... 4-279
Figure 4-171. Import DB Section.................................................................................... 4-281

3BDS 100 595R401 xxxiii

Function Chart Builder
Table of Contents

ILLUSTRATIONS (continued)
Figure 4-172. Print........................................................................................................... 4-282
Figure 4-173. Print DB Section ....................................................................................... 4-285
Figure 4-174. Print PC Section........................................................................................ 4-286
Figure 4-175. Print TC/CI Symbols ................................................................................ 4-287
Figure 4-176. Print Modules............................................................................................ 4-288
Figure 4-177. Print PC Cross Reference ......................................................................... 4-289
Figure 4-178. Print DB Section ....................................................................................... 4-290
Figure 4-179. Print Circuit Usage.................................................................................... 4-291
Figure 4-180. Print DB Names ........................................................................................ 4-292
Figure 4-181. Print PC Names......................................................................................... 4-293
Figure 4-182. Print Setup................................................................................................. 4-295
Figure 4-183. Page Setup................................................................................................. 4-296
Figure 4-184. Create PC Element.................................................................................... 4-300
Figure 4-185. Create DB Element ................................................................................... 4-303
Figure 4-186. Create Symbol........................................................................................... 4-305
Figure 4-187. Create TC/CI Terminal ............................................................................. 4-307
Figure 4-188. Edit TC/CI Terminal Attributes ................................................................ 4-308
Figure 4-189. Create Test Table Entry............................................................................. 4-310
Figure 4-190. Paste PC Section ....................................................................................... 4-312
Figure 4-191. Replace Options PC Section ..................................................................... 4-313
Figure 4-192. Multiple Input Connection to PC.............................................................. 4-314
Figure 4-193. Replace and Paste PC Section, General.................................................... 4-315
Figure 4-194. Replace and Paste PC Section, for TC/CI Symbol Values ....................... 4-316
Figure 4-195. Undo Replace PC Section......................................................................... 4-317
Figure 4-196. Paste Conflicts .......................................................................................... 4-318
Figure 4-197. Find ........................................................................................................... 4-319
Figure 4-198. Edit Call Parameters ................................................................................. 4-321
Figure 4-199. Create/Edit Name...................................................................................... 4-322
Figure 4-200. Edit DB Terminal Values .......................................................................... 4-324
Figure 4-201. References of DB Element ....................................................................... 4-325
Figure 4-202. Edit Symbol .............................................................................................. 4-326
Figure 4-203. Edit Symbol Values................................................................................... 4-328
Figure 4-204. Edit TC/CI Terminal ................................................................................. 4-331
Figure 4-205. Upload....................................................................................................... 4-333
Figure 4-206. Edit Document Texts ................................................................................ 4-335
Figure 4-207. Zoom Function Chart or Tree Diagram .................................................... 4-337
Figure 4-208. View Cross Reference .............................................................................. 4-339
Figure 4-209. PC Cross Reference .................................................................................. 4-340

xxxiv 3BDS 100 595R401

 Function Chart Builder
Table of Contents

ILLUSTRATIONS (continued)
Figure 4-210. DB Cross Reference ................................................................................. 4-341
Figure 4-211. Preferences ............................................................................................... 4-343
Figure 4-212. Extract of TC with including MODIFY keyword .................................... 4-347
Figure 4-213. Workspace ................................................................................................ 4-348
Figure 4-214. Cycle Times.............................................................................................. 4-350
Figure 4-215. Goto Page ................................................................................................. 4-355
Figure 4-216. Select PC Section ..................................................................................... 4-355
Figure 4-217. Modify Item Designation ......................................................................... 4-356
Figure 4-218. Renumber PC Section............................................................................... 4-357
Figure 4-219. Computing Time for Selected Element .................................................... 4-358
Figure 4-220. Computing Time for Selected Unit .......................................................... 4-359
Figure 4-221. Computing Time for Node ....................................................................... 4-361
Figure 4-222. Memory Calculation for Selected Element .............................................. 4-362
Figure 4-223. Memory Calculation for Selected Unit..................................................... 4-362
Figure 4-224. Memory Calculation for Node.................................................................. 4-363
Figure 4-225. Insert Page Division. ................................................................................ 4-364
Figure 4-226. Modify Page Division............................................................................... 4-366
Figure 4-227. Copy Headlines ........................................................................................ 4-367
Figure 4-228. Check Page Layout................................................................................... 4-368
Figure 4-229. Format Pages ............................................................................................ 4-369
Figure 4-230. Generate Page Division ............................................................................ 4-370
Figure 4-231. Modify Page Numbers.............................................................................. 4-371
Figure 4-232. Goto Terminal........................................................................................... 4-373
Figure 4-233. Connect..................................................................................................... 4-375
Figure 4-234. Connect to DB .......................................................................................... 4-378
Figure 4-235. Connect by Name ..................................................................................... 4-379
Figure 4-236. Connect to Symbol ................................................................................... 4-380
Figure 4-237. Connect to TC/CI Terminal ...................................................................... 4-381
Figure 4-238. Virtual Connections .................................................................................. 4-382
Figure 4-239. Disconnect ................................................................................................ 4-383
Figure 4-240. Create/Edit Unit........................................................................................ 4-384
Figure 4-241. Create/Edit Force Value............................................................................ 4-386
Figure 4-242. Connect Target.......................................................................................... 4-388
Figure 4-243. Set Date and Time .................................................................................... 4-394
Figure 4-244. Preset Target Data and Time..................................................................... 4-394
Figure 4-245. Set Password on Target............................................................................. 4-395
Figure 4-246. Application Checksum ............................................................................. 4-396
Figure 4-247. Attribute Report........................................................................................ 4-397

3BDS 100 595R401 xxxv

Function Chart Builder
Table of Contents

ILLUSTRATIONS (continued)
Figure 4-248. Set Cycletime............................................................................................ 4-399
Figure 4-249. Trigger Setup ............................................................................................ 4-400
Figure 4-250. Activate Force Values ............................................................................... 4-401
Figure 4-251. Activate All Force Values ......................................................................... 4-403
Figure 4-252. Set DB Value............................................................................................. 4-405
Figure 4-253. Import Test Table ...................................................................................... 4-406
Figure 4-254. Export Test Table ...................................................................................... 4-407
Figure 4-255. Close Windows ......................................................................................... 4-409
Figure 4-256. On Node.................................................................................................... 4-411
Figure 4-257. About Function Chart Builder .................................................................. 4-413
Figure 4-258. Toolbar of Diagnostics.............................................................................. 4-414
Figure 4-259. Status Bar of Diagnostics.......................................................................... 4-415
Figure 4-260. Error Report Window ............................................................................... 4-416
Figure 4-261. Module List Window ................................................................................ 4-418
Figure 4-262. Module Diagnostics Window ................................................................... 4-419
Figure 4-263. Module Diagnostics, Additional Information........................................... 4-421
Figure 4-264. Save Report/Diagnosis As ........................................................................ 4-421
Figure 4-265. Setup Logfile............................................................................................. 4-423
Figure 4-266. Print Diagnosis.......................................................................................... 4-424
Figure 4-267. Print Setup of Diagnostics ........................................................................ 4-426
Figure 4-268. List Modules of Station............................................................................. 4-428
Figure 4-269. Select Module, AC 110/70........................................................................ 4-429
Figure 4-270. Select Module, AC 55............................................................................... 4-429
Figure 4-271. About Diagnostics..................................................................................... 4-431
Figure 4-272. Toolbar of Diagnosis................................................................................. 4-432
Figure 4-273. Status Bar of Diagnosis............................................................................. 4-433
Figure 4-274. Status Report Window of Diagnosis......................................................... 4-434
Figure 4-275. Error Report Window of Diagnosis .......................................................... 4-436
Figure 4-276. Module List Window of Diagnosis........................................................... 4-438
Figure 4-277. Module Diagnosis Window of Diagnosis ................................................. 4-440
Figure 4-278. Channel Diagnosis Window of Diagnosis ................................................ 4-444
Figure 4-279. Output Window of Diagnosis ................................................................... 4-447
Figure 4-280. Save Report/Diagnosis As ........................................................................ 4-448
Figure 4-281. Setup Logfile............................................................................................. 4-449
Figure 4-282. Print Diagnosis.......................................................................................... 4-450
Figure 4-283. Print Setup of Diagnostics ........................................................................ 4-451
Figure 4-284. Select Module ........................................................................................... 4-454
Figure 4-285. Select Channel .......................................................................................... 4-456

xxxvi 3BDS 100 595R401

 Function Chart Builder
Table of Contents

ILLUSTRATIONS (continued)
Figure 4-286. Diagnosis, Warning Before Deleting Errors............................................. 4-458
Figure 4-287. Diagnosis, Warning Due to Non- reported Errors .................................... 4-458
Figure 4-288. Diagnosis, Delete All Errors, Warning..................................................... 4-459
Figure 4-289. About Diagnosis ....................................................................................... 4-460
Figure A-1. FCB Release Directory Structure .................................................................A-1
Figure A-2. FCB Project Directory Structure ..................................................................A-2
Figure B-1. Working with an AC 400 or MP 200/1 Node...............................................B-1
Figure B-2. Instantiating Type Circuits in a Node...........................................................B-2
Figure B-3. Working on Type Circuits.............................................................................B-3
Figure B-4. Working on Circuits......................................................................................B-4
Figure B-5. Working on Node Structures ........................................................................B-5
Figure B-6. Expanding Node Data...................................................................................B-6
Figure B-7. AC 100 Series Target Code Generation .......................................................B-7
Figure B-8. Upgrading to New FCB Release, Regenerating Objects..............................B-8
Figure G-1. Run DCOMCNFG........................................................................................G-2
Figure G-2. Distributed COM Configuration Properties .................................................G-2
Figure G-3. General Tab ..................................................................................................G-3
Figure G-4. Location Tab .................................................................................................G-3
Figure G-5. Security Tab..................................................................................................G-4
Figure G-6. Registry Value Permissions ..........................................................................G-4
Figure G-7. Add Users and Groups..................................................................................G-5
Figure G-8. Add Users and Groups, Name Added ..........................................................G-6
Figure G-9. Registry Value Permissions, User Added.....................................................G-7

3BDS 100 595R401 xxxvii

Function Chart Builder
Table of Contents

xxxviii 3BDS 100 595R401

 Function Chart Builder
Table of Contents

TABLES
Table 1-1. Common Documents .................................................................................... 1-5
Table 1-2. Related Documents, Advant Controller 400 Series and MasterPiece 200/1 1-6
Table 1-3. Related Documents, Advant Controller 100 Series...................................... 1-6
Table 1-4. Other Related Documents............................................................................. 1-7
Table 1-5. Release History............................................................................................. 1-8
Table 4-1. Objects Processed by FCB ........................................................................... 4-1
Table 4-2. Structure of Tutorial ..................................................................................... 4-4
Table 4-3. Panes of the PC Section Window ............................................................... 4-10
Table 4-4. Default Commands in Function Chart Pane of PC Section Window on
Double-click ............................................................................................... 4-84
Table 4-5. Default Commands in Tree Pane of PC Section Window on Double-click 4-84
Table 4-6. Use of Keys for Sliding .............................................................................. 4-88
Table 4-7. Handling of Type Circuit Classes for AC 100 Series................................4-112
Table 4-8. Selection in PC Section Windows by Mouse ........................................... 4-127
Table 4-9. Selection in PC Section Windows by Keys.............................................. 4-128
Table 4-10. FCB Mode (State) Transitions.................................................................. 4-147
Table 4-11. Position of Intermediate Nodes ................................................................ 4-154
Table 4-12. Position of Target...................................................................................... 4-154
Table 4-13. Routing Possibilities Depending on Node Type....................................... 4-162
Table 4-14. Presentation of Errors ............................................................................... 4-183
Table 4-15. Use of Symbols, Symbolic Expressions, and Symbolic Formulas........... 4-198
Table 4-16. Symbol Value Inheritance in TC, Instantiated in NS ............................... 4-200
Table 4-19. Symbol Value Inheritance from NS via CI to NS..................................... 4-201
Table 4-17. Symbol Value Inheritance in CI, Located in NS ...................................... 4-201
Table 4-18. Symbol Value Inheritance in TC, Instantiated in CI................................. 4-201
Table 4-20. Operators in Symbolic Formulas.............................................................. 4-204
Table 4-21. Icons and Commands of the Toolbar........................................................ 4-210
Table 4-22. Indicators in the Status Bar........................................................................4-211
Table 4-23. Columns in the Test Table Window.......................................................... 4-230
Table 4-24. Kind and State of Entries in the Test Table .............................................. 4-231
Table 4-25. Edit PC File Names .................................................................................. 4-272
Table 4-26. DB File Name Specification..................................................................... 4-275
Table 4-27. Print File Names ....................................................................................... 4-282
Table 4-28. Dialogs to Specify Document Parts (1) .................................................... 4-283
Table 4-29. Dialogs to Specify Document Parts (2) .................................................... 4-284
Table 4-30. Symbol Kinds in Different Objects .......................................................... 4-306
Table 4-31. Symbol Kinds Allowed in Different Objects ........................................... 4-327
Table 4-32. Restart Behavior ....................................................................................... 4-393

3BDS 100 595R401 xlvii

Function Chart Builder
Table of Contents

TABLES (continued)
Table 4-33. Icons and Commands in the Toolbar of Diagnostics ................................ 4-415
Table 4-34. Indicators in the Status Bar of Diagnostics............................................... 4-415
Table 4-35. Significance and Ranges of Target Address ............................................. 4-417
Table 4-36. Log Types ................................................................................................. 4-424
Table 4-37. Icons and Commands in the Toolbar of Diagnosis ................................... 4-432
Table 4-38. Indicators in the Status Bar of Diagnosis.................................................. 4-433
Table 4-39. Error Report State Filters.......................................................................... 4-437
Table 4-40. Significance and Ranges of Target Address ............................................. 4-437
Table 4-41. List Modules State Filters ......................................................................... 4-439
Table 4-42. Module Status Bits in Module Diagnosis ................................................. 4-441
Table 4-43. Module States ........................................................................................... 4-442
Table 4-44. Channel Types in Module Diagnosis ........................................................ 4-442
Table 4-45. Module Status Bits in Channel Diagnosis ................................................ 4-445
Table 4-46. Channel States for Most Standard Modules ............................................. 4-446
Table 4-47. Channel States for MasterFieldbus Master and Slave .............................. 4-446
Table 4-48. Channel States for Data Set CI626 ........................................................... 4-446
Table 4-49. Log Types ................................................................................................. 4-450
Table 4-50. List Modules State .................................................................................... 4-455
Table 4-51. List Channels Options............................................................................... 4-457
Table 5-1. File Describing Windows NT Environment ................................................. 5-2
Table 5-2. Advant Engineering and Project Files for Reporting Problems ................... 5-2
Table D-1. Parsers in FCB Based on Present Syntax Descriptions ............................... D-3
Table D-2. Nested Parsers in FCB Based on Present Syntax Descriptions ................... D-3
Table D-3. Editors in FCB Based on Present Syntax Descriptions ............................... D-4
Table D-4. Source Code Generators in FCB Based on Present Syntax Descriptions.... D-4
Table E-1. Character Set of PC Names ..........................................................................E-2
Table E-2. Character Set of DB Names..........................................................................E-6

xlviii 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 1.1 General Information

Chapter 1 Introduction

1.1 General Information

This guide describes the Function Chart Builder (FCB) running as Windows application under
Windows NT and Windows 2000 on Advant Station 100 Series Engineering Station, and
provides you with the information necessary for programming Advant Controller 400 Series,
MasterPiece 200/1, and Advant Controller 100 Series nodes.
The Function Chart Builder release 6.2 enhances project engineering productivity due to its user
comfort and some new or improved features in modes stand alone, integrated in Industrial IT or
integrated in Advant Engineering Workplace such as:
• In addition to the standard English language for use under Windows NT (English) or
Windows 2000 (English), Function Chart Builder can be switched to German language for
use under Windows NT (German) or Windows 2000 (German)
• Control Builder A Interface for integrated work in Industrial IT with Engineering Studio
2.0-1. For newer version see Control Builder A Interface Release Notes.
• AC 160 version 2.2 is supported.
This guide containing tutorial, “how to”, and reference information on the Function Chart
Builder is useful both for novice and expert programmers. It offers you new information, even if
you are an experienced user of former FCB releases.
This guide tells you how to install and use the Function Chart Builder, describes its menus and
commands, and covers interesting topics concerning Function Chart Builder usage but it does
not teach you Advant Controller or MasterPiece system programming. To learn how to program
an Advant Controller or MasterPiece system, attend system engineering courses offered by the
local ABB representative and consult the manuals listed at the end of this chapter.

1.2 Equipment Requirements

You can use your own personal computer or an Advant Station 100 Series Engineering Station
as a platform for running the Function Chart Builder. If case of your own PC check whether the
hardware and software requirements as stated in the Application Builder User’s Guide are
fulfilled. Advant Station 100 Series Engineering Stations do fulfill these requirements.
Using a pointing device with the Function Chart Builder, such as a Microsoft-compatible mouse
or trackball, is desirable.

DANGER
If you use a PC of yours as engineering station and if you want to work on-line
connected to target systems, your PC, its add-on boards, and its peripherals must
fulfill high mechanical, temperature, and electrical requirements, as stated in the
Application Builder User’s Guide.
Else you risk malfunction of the target system.
Advant Station 100 Series Engineering Stations and their peripherals fulfill these
requirements.

3BDS 100 595R401 1-1

Function Chart Builder User’s Guide
Chapter 1 Introduction

1.3 Manual Organization

Figure 1-1 shows the organization of the document.

Chapters

Configuration/ Runtime
Introduction Installation Application Maintenance Appendices Index
Building Operation

General Site Planning Design Product Preventive Function Cart

Information Environment Considerations Operation Maintenance Builder Files
Equipment Setup Capacity and Operating Error Data Flow
Requirements Performance Overview Messages in FCB
Manual Shut-down Application Runtime Fault Finding Syntax of Symb.
Organization Procedures Start-up Tutorial & User Repair Expressions &
Start-up Formulas
Operating
Conventions Procedures Instructions Syntax of TC, CI
Related Product Runtime & NS Source Files
Documentation Verification Operation
Menus Syntax of Names
Release
History Configuration of
AdvaBuild
Terminology Sections Communicator
Product Syntax of
Overview *.TPX Files
User Interface Glossary

Figure 1-1. Documentation Structure Chart of the Function Chart Builder

Chapter 1, Introduction
Provides you with basic information about the Function Chart Builder and this guide.

Chapter 2, Installation
Tells you how to install the Function Chart Builder.

Chapter 3, Configuration/Application Building

Gives you an overview of the function-oriented project engineering working method, introduces
basic Function Chart Builder terms. It tells you how to start the Function Chart Builder and the
Diagnostics program.

Chapter 4, Runtime Operation

Gives you an overview of product operation.

1-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 1.3 Manual Organization

The best way to learn how to use the Function Chart Builder is by using it to write simple
program examples. Follow the instructions and examples in Section 4.3, Runtime Tutorial,
practice using the menus and dialog boxes. You’ll find that most of the menu items are easy to
figure out without reading any further in the guide.
Section 4.4, Operating Instructions tells you how to perform programming operations, test, and
diagnostics. You will need several commands to do this. This section describes typical Function
Chart Builder command sequences and explains their relationships. Look up the function you
want to perform in the Table of Contents to locate the specific command sequences.
Use Section 4.5, Runtime Operation Menus as a reference to learn how to use the controls of the
Title Bar, Toolbar, Status Bar, the controls in the document windows, and the menu commands
of the Function Chart Builder and the Diagnostics program.

Chapter 5, Maintenance
Tells you how to handle problems that you cannot solve by reading the other chapters.

Appendix A, Function Chart Builder Files

Describes the software directory structure of the Function Chart Builder, lists all files contained
in and created by the Function Chart Builder, and describes the contents of each file.

Appendix B, Data Flow in Function Chart Builder

Describes the data flow when you work with the Function Chart Builder (including type
circuits, circuits, and node structures).

Appendix C, Syntax of Symbolic Expressions and Formulas

Describes the syntax definition of symbolic expressions and symbolic formulas.

Appendix D, Syntax of TC, CI, and NS Source Code

Contains the syntax definition of *.TCS, *.CIS, and *.NSS source code files. It serves as
reference for developers working on source code level.

Appendix E, Syntax of Names

Contains the syntax definition of PC names and DB names. It serves as reference at editing
applications with the Function Chart Builder.

Appendix F, Syntax of Template Files

Contains the syntax definition of *.TPX template files. It serves as reference for developers to
create own document templates.

Appendix G, Configuration of AdvaBuild Communicator

Describes the configuration of engineering station - target communication on server.

Appendix H, Glossary
Defines terms frequently used in this guide.

3BDS 100 595R401 1-3

Function Chart Builder User’s Guide
Chapter 1 Introduction

INDEX
The Index tells you where to find references to a variety of key topics within the text.
If you run into a term that you do not understand, look it up in the Appendix H, Glossary.
If you want to find references to a term or function within the text quickly, use the Index.

1.4 Conventions

1.4.1 General
Books, manuals, and so on, referenced in the text are written in italic.
Terms defined in Appendix H, Glossary or in Section 1.7, Terminology are in italic.
Filenames, directory names, acronyms appear in all capitals.
Words, which you have to type exactly in that form, are shown in boldface type, and if possible
in CAPITAL letters, for example, POWERSTN.
Texts and system messages displayed on the screen are shown in Courier font, for example,
Select Options.
Application windows, document windows, and dialog boxes are referenced by their names in
boldface type, for example, PC Section window.

1.4.2 Keys
Special keyboard keys are written plain with small capitals:
• ALT, CTRL, DEL, ENTER, ESC, INS, KEYPAD 5, NUMLOCK, SCROLL LOCK, SHIFT, SPACEBAR

• BACKSPACE (for <-)

• DOWN (for down arrow, numeric keypad 2), LEFT (for left arrow, numeric keypad 4),
UP (for up arrow, numeric keypad 8), RIGHT (for right arrow, numeric keypad 6)
• F1, F2, and so on (for function keys)
• MINUS (for ‘-’ sign in numeric keypad), PLUS (for ‘+’ sign in numeric keypad),
ASTERISK (for ‘*’ sign in numeric keypad)
• PGDOWN (for page down, numeric keypad 9), PGUP (for page down, numeric keypad 3)
• 1, 2,…(for keys in the upper row of the traditional typewriter keyboard, not in the numeric
keypad)
Shorthand for combined key usage, such as holding down the CTRL key and then pressing the
key L:
CTRL+L.

1.4.3 Commands and Menus

Commands are written bold with capital initial:
choose Exit …

1-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 1.5 Related Documentation

Menus are written bold with capital initial:

in the File menu …
Shorthand for commands that you choose as items from menus, for example, command Exit
from the File menu, appears as File | Exit.

1.5 Related Documentation

Common documents are listed in Table 1-1.

Table 1-1. Common Documents

Manual Description
Advant Station 100 Series Describes the hardware and setup of Advant Station 100
Engineering Station Series Engineering Stations, including the
User’s Guide Advant Station 100 Series Engineering Board.
Application Builder Describes installation of Advant Engineering components
User’s Guide and contains the operating instruction of Application
Builder and Advant Engineering support functions.
Bus Configuration Builder Describes bus configuration support functions for
User’s Guide AF100 OPC based and AdvaSoft for Windows based
Human-System Interface systems.
Source Code Handling Contains descriptions and instructions for use of AMPL
User’s Guide source code for application programs and data bases.
Advant Fieldbus 100 Contains user information on Advant Fieldbus 100.
User’s Guide
S800 I/O User’s Guide Contains user information on S800 I/O.
Control Builder Describes the functions of the Control Configuration
Commands for Structure Aspect System and the use of Application Builder and
Builder Function Chart Builder functionality by the Structure
User’s Guide Builder.
PROFIBUS Library Editor Describes the usage of the PROFIBUS Library Editor.
User’s Guide
Engineer IT Control Describes the usage of Control Builder commands when
Builder A Interface Version Engineering Studio Workplace is used as navigation tool.
1.1 User's Guide

3BDS 100 595R401 1-5

Function Chart Builder User’s Guide
Chapter 1 Introduction

Advant Controller 400 Series and MasterPiece 200/1 related documents are listed in Table 1-2.

Table 1-2. Related Documents, Advant Controller 400 Series and MasterPiece 200/1

Manual Description
On-line Builder Contains the operating instruction of On-line Builder.
Engineering Stations
User’s Guide
On-line Builder Describes all commands used in AS 100ES,
Reference Manual AS 500ES, and AS 500OS. Describes command sets,
working methods, and command file handling aspects.
AMPL Application Building Contains tutorial for configuration and application
Reference Manual programming of AC 410/450 controllers.
AMPL Configuration Contains instructions for configuration and application
Advant Controller 400 programming of AC 410/450 controllers including
Series command descriptions. The topics are:
Reference Manual AMPL configuration principles, application programming,
commissioning and testing, on-line editing,
documentation, backup and transfer of application data
Data Base Elements Data for all data base elements in
Advant Controller 400 Advant Controller 410/450.
Series Reference Manual
PC Elements Data for all PC elements in Advant Controller 410/450.
Advant Controller 400
Series Reference Manual
MasterPiece 200/1 Contains instructions for configuration and application
Configuration and programming of MasterPiece 200/1 including command
Programming descriptions. The topics are:
AMPL configuration principles, application programming,
commissioning and testing, on-line editing,
documentation, backup and transfer of application data

Advant Controller 100 Series related documents are listed in Table 1-3.

Table 1-3. Related Documents, Advant Controller 100 Series

Manual Description
AMPL Configuration Contains instructions for configuration, application
Advant Controller 100 programming, fault tracing, and maintenance.
Series Reference Manual
Advant Controller 110 Contains a description of the Advant Controller 110.
User’s Guide

1-6 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 1.5 Related Documentation

Table 1-3. Related Documents, Advant Controller 100 Series (Continued)

Manual Description
Data Base Elements Data for all data base elements in Advant Controller 110.
AC 100 Series
Reference Manual
PC Elements Data for all PC elements in Advant Controller 110.
AC 100 Series
Reference Manual
Advant Controller 110 Contains configuration of PROFIBUS and PROFIBUS-DP
PROFIBUS-DP slaves for Advant Controller 110.
User’s Guide
Advant Controller 70 Contains a description of the Advant Controller 70.
User’s Guide
Data Base Elements Data for all data base elements in Advant Controller 70.
Advant Controller 70
Reference Manual
PC Elements Data for all PC elements in Advant Controller 70.
Advant Controller 70
Reference Manual
Advant Controller 55 Contains a description of the Advant Controller 55.
User’s Guide
Data Base Elements Data for all data base elements in Advant Controller 55.
Advant Controller 55
Reference Manual
PC Elements Data for all PC elements in Advant Controller 55.
Advant Controller 55
Reference Manual

Other related documents are listed in Table 1-4.

Table 1-4. Other Related Documents

Manual Description
FCB Type Circuits Drives Describes FCB type circuit for standard and engineered
Objects User’s Guide drives.

3BDS 100 595R401 1-7

Function Chart Builder User’s Guide
Chapter 1 Introduction

1.6 Release History

This new version of the Function Chart Builder User’s Guide supersedes the earlier ones.
It applies to release 6.1/* of the Function Chart Builder, a 32-bit program running under
Windows NT and Windows 2000. It contains also:
• In addition to the standard English language for use under Windows NT (English) or
Windows 2000 (English), Function Chart Builder can be switched to German language for
use under Windows NT (German) or Windows 2000 (German)
• Control Builder A Interface for integrated work in Industrial IT with Engineering Studio
1.1
• The predefined DB Elements for S800 I/O with Advant Controller 160/110 via Profibus
are now adapted to CI830 Version 1.3.
Table 1-5 lists the major milestones in the development of the FCB and its predecessor.

Table 1-5. Release History

Version Description
FCE* 2.*/* Initial version of Function Chart Editor with programming support for
MP 200/1 and MP 90 nodes.
User’s Manual: 3BSE 000564R0001
FCE* 3.0/* Processing of node structures and circuits were added.
User’s Manual: 3BSE 000564R0101
FCE* 3.1/* Features for function-oriented project engineering have been added,
like support of target product structure, improved type circuit re-
identification, manual type circuit/circuit terminal definition, calculated
symbols, and validation of PC source code created with text editors.
User’s Manual: 3BSE 000564R0201
FCB* 4.0/0 Initial version of Function Chart Builder. The user interface has been
fully redesigned corresponding to Windows environment. New
features have been added, like parallel editing in different sections.
User’s Guide 3BSE 007149R0001:
The User’s Guide has been restructured, new sections have been
added, such as operating instructions.
User’s Guide 3BSE 007149R0101:
The User’s Guide has been completed and revised.
FCB* 4.1/0 Features like cut, copy, paste (off-line, in PC section) and the
description of the Diagnosis program have been added.
User’s Guide: 3BSE 007149R0201.

1-8 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 1.6 Release History

Table 1-5. Release History

Version Description
FCB* 4.2/0 Features like type circuit usage for Advant Controller 100 Series
without disintegration, enhancement of execution time calculation,
cycle time setting for cyclic display.
User’s Guide 3BSE 007149R0301:
Tutorial completed by Advant Controller 100 Series application with
accent on-line testing and editing.
FCB* 4.3/0 Features like support of extended DB elements, saving and loading
workspaces, multiple windows, splitting the PC Section window,
extended tutorial, and the Diagnostics program have been added.
User’s Guide: 3BSE 007149R0401.
FCB* 4.4/0 First version supporting also the cooperating mode in addition to the
traditional independent mode. First version available also as 32-bit
application running under Windows NT.
Features like the Test Table for common handling of force and display
values, recording and display of values (trend), editing virtual
connections also in nodes, assignment of instance names to PC
elements, type circuits and circuits, setting cycle times for
Advant Controller 400 Series applications, and additional navigation
between referencing DB elements have been added.
User’s Guide: 3BSE 007149R0501.
FCB* 4.5/2 Last version available also as 16-bit application running under
Windows for Workgroups 3.11.
Features like the Test | Set Trigger command for automatic stopping
of cyclic display, support of Bus Configuration Builder 2.5 by filling the
Bus Configuration Database, and PROFIBUS Library Editor
(attachment) have been added.
User’s Guide: 3BSE 007149R0601.
FCB* 4.6/1 Features like Target | Upload and File | Backtranslate Target Code for
application retrieval, File | On-line Preparation Mode for convenience
of on-line programming, password protection and Connect assistant
have been added.
User’s Guide: 3BSE 007149R0701.
FCB* 4.7/0 Features like the multi-level Edit | Undo and Edit | Redo commands,
context menu commands in PC-Section window, connection by
instance name, and preset of date and time on target independent
from date and time on AS100 ES have been added.
Runs under Windows NT. User’s Guide: 3BSE 007149R0801.

3BDS 100 595R401 1-9

Function Chart Builder User’s Guide
Chapter 1 Introduction

Table 1-5. Release History

Version Description
FCB* 5.0/0 Features like the View | Cross Reference command, context menu
commands in Output window, new options, and support of ABB
Objects based Human System Interface for Advant Controller 400
Series, MasterBus 300, and MB300 Connector by the File | Generate
BCD Data command have been added. Runs under Windows NT and
Windows 2000. User’s Guide: 3BDS 100 595R101.
FCB* 6.0/0 Features like the improved File | Generate Source Code and File |
Backtranslate Source Code commands. Runs under Windows NT
and Windows 2000. User’s Guide: 3BDS 100 595R201.
FCB* 6.1/0 Features like the support of german language in Function Chart
Builder. Runs under Windows NT and Windows 2000. User’s Guide:
3BDS 100 595R301 (english) and 3BDS 100 595R303 (german).

1.7 Terminology
The following is a list of terms you should be familiar with.

Term Description
AC 110 The abbreviation “AC 110” is used for
Advant Controller 110.
AC 160 The abbreviation “AC 160” is used for
Advant Controller 160.
AC 55 The abbreviation “AC 55” is used for Advant Controller 55.
AC 70 The abbreviation “AC 70” is used for Advant Controller 70.
AC 80 The abbreviation “AC 80” is used for Advant Controller 80.
Advant Controller 100 The term “Advant Controller 100 Series” is used for Advant
Series/AC 100 Series Controller X where X may have a value from 1 to 199.
Advant Controller 400 The terms “Advant Controller 400 Series” and
Series/AC 400 Series “AC 400 Series” are used for Advant Controller 410 and
Advant Controller 450.
Advant Station 100 The term “Advant Station 100 Series Engineering Stations”
Series Engineering and “AS 100ES” are used for
Stations Advant Station 120 Engineering Station (AS 120ES),
Advant Station 125 Engineering Station (AS 125ES),
Advant Station 130 Engineering Station (AS 130ES), and
Advant Station 140 Engineering Station (AS 140ES).
AF 100 The abbreviation “AF 100” is used for Advant Fieldbus 100.

1-10 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 1.7 Terminology

Term Description
AF100 OPC The abbreviation “AF100 OPC” is used for AF 100 OLE
Process Control, an interface between AF 100 bus and HMI
system.
APB The abbreviation “APB” is used for Application Builder.
Application Builder The term is used for Application Builder, an Advant
Engineering product component.
BCD The abbreviation “BCD” is used for Bus Configuration
Database.
Bus Configuration The Bus Configuration Database offered by Bus
Database Configuration Builder contains configuration data of AF 100
busses belonging to a project.
Bus Configuration Interface to Bus Configuration Database corresponding to
Interface Microsoft’s Component Object Model (COM).
DB The term “DB” is used for Advant Controller 100 Series
data base. It consists of database elements (DB elements).
Extended DB Elements DB elements with enhanced communication and HMI-
support capabilities, such as AIS, DIS.
FCB The abbreviation “FCB” is used for Function Chart Builder.
Function Chart Builder The term is used for the Function Chart Builder,
an Advant Engineering product component. It is runs on
Advant Station 100 Series Engineering Stations.
Function Chart Editor The term “Function Chart Editor” is used for the
Function Chart Editor AC 400 / MP 200/1 (QMA222) and
Function Chart Editor AC 100 (QMA223), that is, for the
predecessors of the Function Chart Builder.
The abbreviation for Function Chart Editor is “FCE”.
MB 300 The abbreviation “MB 300” is used for MasterBus 300.
MasterBus 300 is a high-performance serial synchronous
half duplex bus for medium communication distances. Use
it to interconnect Process Stations, Operator Stations and
MasterGate 230/1 stations in a Control Network.
MB300 Connector “MB300 Connector” is used for the interface between
MasterBus 300 and the Human-System Interface.
It is implemented according to the OLE Process Control
standard.
MP 200/1 The abbreviation “MP 200/1” is used for MasterPiece 200/1.

3BDS 100 595R401 1-11

Function Chart Builder User’s Guide
Chapter 1 Introduction

Term Description
On-line Builder The term is used for the On-line Builder, an Advant
Engineering product component.
The term “On-line Builder” is the new name for “Command
Oriented Functions”.
Series The term “Series” in product names is used to reference the
products in general terms, without any reference to a
specific model (for example, Advant Station 100 Series
Engineering Stations).
XDB The abbreviation “XDB” is used for extended DB elements

1.8 Product Overview

Function Chart Builder

The Function Chart Builder is a programming tool for Advant Controller 100 Series,
Advant Controller 400 Series and MasterPiece 200/1. It is runs on Advant Station 100 Series
Engineering Stations as an EngineerIT product component.
For creating and editing different objects it contains:
• Function chart (FC) editor and tree editor as PC editors
(with cut, copy, and paste functions)
• DB editor
• Symbol editor.
The Function Chart Builder supports the function-oriented project engineering.
You can program the following objects:
• Nodes (as nodes or as node structures)
• Circuits
• Type circuits.
The Function Chart Builder processes project data in internal data representation, generates
AMPL source code for data interchange, backtranslates source code to internal representation,
generates target code for Advant Controller 100 Series nodes.
The Function Chart Builder supports on-line editing and testing for
Advant Controller 100 Series nodes.
The Diagnostics program—part of the Function Chart Builder—supports on-line diagnostics of
Advant Controller 100 Series. It is adapted to the different diagnostics features of both former
and recent controller versions.

1-12 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 1.9 User Interface

1.9 User Interface

The Function Chart Builder and the Diagnostics program are Windows application programs
with typical graphic user interface and look-and-feel of Windows programs. They present the
different objects in windows, offers menus and dialog boxes. You choose the commands by
accelerator keys and shortcuts on the keyboard or by mouse actions.
See detailed information on the graphic user interface and on interacting with Windows
programs in the user´s guide of Windows installed on your engineering station, for example,
Basics and Installation Microsoft Windows NT Workstation Version 4.0, Microsoft Corporation,
Document No. 94945-0996.
Or select Help from the Start menu of Windows and then look for relevant topics in Windows
NT Help or Windows 2000 Help.

3BDS 100 595R401 1-13

Function Chart Builder User’s Guide
Chapter 1 Introduction

1-14 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 2.1 Site Planning Environment

Chapter 2 Installation

2.1 Site Planning Environment

Consult Product Guide - Advant Engineering Products for environmental considerations and
Advant Station 100 Series Engineering Station User’s Guide.
If you are working on a PC of your own, consult its user documentation.

2.2 Setup

2.2.1 Software Installation

The Function Chart Builder, included in Control Builder A, is a 32-bit Windows application.
It runs under Microsoft Windows NT and Windows 2000.
As hardware and software platform for running the Function Chart Builder, you can use an
Advant Station 100 Series Engineering Station with installed Windows NT or Windows 2000
operating system.
Or you can use an appropriate PC of yours with installed Windows NT or Windows 2000.
The installation is described in the Function Chart Builder Release Notes.

2.2.2 Compatibility of Software and Source Code

Different releases of the Function Chart Builder (and Function Chart Editor) are compatible on
source code level, but the internal representation of project data may be changed. The internal
representation of project data is different even for same releases of Function Chart Builder if
they run under different operating systems, such as Windows for Workgroups and Windows NT.
You must take measures to ensure compatibility of type circuit, circuit, and node structure
source files for different Function Chart Builder (and Function Chart Editor) releases or convert
them.
Type circuit and circuit source code syntax was slightly changed for the Function Chart Editor
version 3.1/0 to allow explicit (manual) type circuit/circuit terminal definition. This change is
also valid for the successor product Function Chart Builder. To transform type circuits and
circuits, which were prepared and validated for the Function Chart Editor version 3.0/0, install
the Function Chart Editor version 3.1/0 first, then use the stand-alone utility program UpTCCI
delivered with the Function Chart Editor version 3.1/0.
If you currently have an earlier release of the Function Chart Builder (or Function Chart Editor
3.1) on the engineering station, be sure you generate source code for all your nodes, type
circuits, circuits, and node structures before you install (a new release of) the Function Chart
Builder. To regenerate objects after having installed a new release of the Function Chart Builder,
see Section 4.4.2.13, Regenerate an Object.
Since Function Chart Builder 4.4/0, the source code contains also instance names for PC
elements, type circuits and circuits. So the source code produced by Function Chart Builder
4.4/0 and higher is not downward compatible to earlier versions of Function Chart Builder or
Function Chart Editor if you use instance names for PC elements, type circuits, and circuits.

3BDS 100 595R401 2-1

Function Chart Builder User’s Guide
Chapter 2 Installation

Editing of type circuits having variants and loops is not supported by the Function Chart
Builder. Nevertheless, variants and loops are allowed in type circuit source code, and you can
instantiate such type circuits by the Function Chart Builder.
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.

NOTE
If you are interested in source code syntax, consult Appendix D, Syntax of TC,
CI, and NS Source Code. You may need it in the following cases:

• You are working with source files edited by hand using some text editor like
AS100-EDIT.
• You are working with source files generated by other tools than the Function
Chart Builder.
• You want to edit advanced type circuits having variants (IFs) and loops using
some text editor.

2.2.3 Support of Additional Node Types and Options

By means of AMPL PC and DB Libraries, the Application Builder and the Function Chart
Builder support the following targets:
• All the standard Advant Controller 400 Series and MasterPiece 200/1 targets
• All the standard Advant Controller 100 Series targets.
Some ABB business units (BUs) develop new hardware or base software versions of the
standard targets, or extensions to them. They are available as BU-specific libraries containing
additional node types, additional element libraries, and programs realizing special features.
Additional node types may specify also additional menu items for the Function Chart Builder or
assign modified functions to the standard menu items.
Target description files *.TEL and the referenced *.PEL and *.DEL files of element libraries
carry the information, which is necessary for the Application Builder and the Function Chart
Builder to support the library options.
Install standard and BU-specific library options to be able to create nodes, circuits, and type
circuits with the corresponding node types by the Application Builder, and to edit them using
the corresponding element libraries by the Function Chart Builder. See AMPL PC and DB
Element Libraries Release Notes.

2.3 Shut-down and Start-up Procedures

Follow the basic shutdown and power up procedure of AS 100ES or your PC as applicable.

2.4 Product Verification

Start the Function Chart Builder. See Section 3.3, Application Start-up.
Choose the Help | About … command to verify product name, version, and copyright notice.

2-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 3.1 Design Considerations - General Working Method

Chapter 3 Configuration/Application Building

3.1 Design Considerations - General Working Method

NOTE
This method concerns the use of Function Chart Builder in independent mode.
For methods of its use in cooperating mode, that is, when the Function Chart
Builder functionality is called as part of the Control Builder A, see Control
Configuration Functions User’s Guide.

Process control projects generally deal with process devices like motors, valves, sensors, and so
on, controlled by a process control system. You can assign a functional piece of software
running on the control system to each process device. This piece of software is called a circuit
(CI). See Figure 3-1. Lines with arrows on both sides show assignment or correspondence.

HARDWARE SOFTWARE

M
Motor1 Circuit1

M
Motor75 Circuit75

Valve1 Circuit76

Valve22 Circuit97

Figure 3-1. Assigning Circuits to Process Devices

Circuits are the basic objects of function-oriented project engineering. They can contain the
process control functions for particular devices in the process. A circuit is independent of the
process station on which it runs.

3BDS 100 595R401 3-1

Function Chart Builder User’s Guide
Chapter 3 Configuration/Application Building

When analyzing an application, you normally find similar control logic for a group of circuits.
To guarantee high software quality and high project efficiency, build circuits using standardized,
reusable control solutions called type circuits (TCs). See Figure 3-2.

HARDWARE SOFTWARE

M
Motor1 Circuit1

Type Circuit
M Motor Control

Motor75 Circuit75

Valve1 Circuit76

Type Circuit
Valve Control

Valve22 Circuit97

Figure 3-2. Referencing Type Circuits

In the scenario illustrated in Figure 3-2, designing circuits is essentially reduced to referencing
type circuits and specifying instance-specific parameters for them. Of course, you can structure
your application also in other ways by circuits and type circuits.
The dot on one end of a line stands for the reference to the object shown by the arrow on the
other end of the line.
The reference to a type circuit together with the pertinent parameters is called an instance of the
type circuit.
A type circuit can be instantiated, that is, referenced and supplied with parameters, several
times.

3-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 3.1 Design Considerations - General Working Method

At the point in the project, when you have finished implementing circuits, you must locate the
circuits in the structure of the process station. The location list for a certain process station is
called a node structure (NS). You must consider aspects of process station load, response time
requirements, number of I/O channels, and so on, during this step. See Figure 3-3.

HARDWARE SOFTWARE

M
Motor1 Circuit1

Type Circuit
M Motor Control
Process Node
Motor75 Station1 Structure1 Circuit75

Valve1 Circuit76

Type Circuit
Valve Control
Process Node
Valve22 Station8 Structure8 Circuit97

Figure 3-3. Locating Circuits in Node Structures

We may choose, for example, Circuit1 and Circuit76 to run on a process station.
The corresponding NodeStructure1 references these circuits and assigns physical locations to
the I/O channels used in them. That is what we call to locate a circuit.
A circuit can be located only once.

3BDS 100 595R401 3-3

Function Chart Builder User’s Guide
Chapter 3 Configuration/Application Building

Finally, you can generate executable code for a certain process station (node within a process
control network) if the references in the corresponding node structure to circuits and type
circuits are resolved and their contents are expanded. See Figure 3-4.

HARDWARE SOFTWARE

M
Motor1 Type Circuit
Motor Control

Type Circuit
Valve Control
M
Process Node1
Motor75 Station1

Valve1 Type Circuit

Motor Control

Type Circuit
Valve Control

Process Node8
Valve22 Station8

Figure 3-4. Resolving References and Expanding Node Data

NOTE
Since Function Chart Builder release 4.7 you can locate circuits directly in nodes.
The circuits are resolved and disintegrated at the time of their location. That also
means that steps 3 and 4 are merged. However, locating circuits directly in nodes
is not recommended in independent mode.

3-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 3.2 Capacity and Performance

3.2 Capacity and Performance

The Function Chart Builder as Windows task can be started several times on different objects,
that is, several instances of the Function Chart Builder can run at a time provided each of them
has been started for a different object.
All editors can be started simultaneously for the object, which was selected in the Application
Builder, that is, for a node, node structure, circuit or type circuit. The Function Chart Builder
opens a (main) application window and the following child windows depending on the selected
object and on the off-line/on-line mode:
• *.ODB window
• PC Section window
• DB Section window
• Symbol Section window
• TC/CI Terminal Section window
• Output window
• Name Table window
• Test Table window
• Status Report window
• Options Report window.
The Diagnostics (Diagnosis) program is adapted to the different diagnostics features of both
former and recent controller versions.
The Diagnosis program displays diagnostic information about the connected of AC 110 2.0,
AC 70 1.0, or AC 55 1.0 target in the following windows within its own application window:
• Status Report window
• Error Report window
• Module List window
• Module Diagnosis window
• Channel Diagnosis window.
The Diagnostics program displays diagnostic information about the connected AC 100 Series
targets of newer node types, such as AC 160, AC 110 2.1 and higher, AC 80, AC 70 1.1 and
higher, and AC 55 1.1, in the following windows within its own application window:
• Error Report window
• Module List window
• Module Diagnostics window.

3BDS 100 595R401 3-5

Function Chart Builder User’s Guide
Chapter 3 Configuration/Application Building

3.3 Application Start-up

3.3.1 Start-up of the Function Chart Builder

Preparation
Before starting the Function Chart Builder you generally start the Application Builder to select a
project and an object to work on.
If you follow the function-oriented project engineering method described in Section 3.1, Design
Considerations - General Working Method, you generally select a node structure, a circuit, or a
type circuit.
You can also select a node in a straightforward way.
See Application Builder User’s Guide for detailed description of Application Builder menus and
commands.

Ways of Starting the Function Chart Builder

• Start from within the Application Builder by choosing the Tools | Function Chart
Builder or Tools | Node Structure Function Chart Builder menu command.
The Function Chart Builder works on the project and the object, which has been selected
in Application Builder.
• Start by choosing it in the Start | Advant | Engineering menu of Windows.
If the Function Chart Builder is already running, the Function Chart Builder application
window gets the focus.
If not, the Function Chart Builder is started on the project and object it recently worked on.
If no information is available on recent project and object, for example, when starting first
time after installation, Function Chart Builder warns you with the message shown by
Figure 3-5.

Figure 3-5. Warning on Missing Initialization Data

3-6 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 3.3.1 Start-up of the Function Chart Builder

The Function Chart Builder opens the application window like the one shown by Figure 3-6.

Figure 3-6. Application Window, Initial State

It has the title “Function Chart Builder - …” with the name of the selected object,
a Menu Bar, a child window and optionally the Toolbar and the Status Bar.
If you start the Function Chart Builder for the first time on a new object of a project and no
project default page layout was defined in the Application Builder, define the page layout for
your diagrams in the following dialog box:

Figure 3-7. Page Setup

For the Page Setup dialog see the File | Page Setup command.

3BDS 100 595R401 3-7

Function Chart Builder User’s Guide
Chapter 3 Configuration/Application Building

3.3.2 Start-up of Diagnostics

You can start the Diagnostics (Diagnosis) program only from within the Function Chart Builder
and for AC 100 Series targets.
Connect the target on-line and choose the Target | Diagnostics command.
In case of AC 100 Series targets of newer node types, such as AC 160, AC 110 2.1 and higher,
AC 80, AC 70 1.1 and higher, and AC 55 1.1, it starts the Diagnostics program.
In case of AC 110 2.0, AC 70 1.0, and AC 55 1.0 it starts the Diagnosis program.
For detailed information see Section 4.4.7.1, Diagnostic Procedures with the Diagnostics
Program and Section 4.4.7.2, Diagnostic Procedures with the Diagnosis Program.

3.3.3 Start-up of Utilities

You can start the utility programs attached to the Function Chart Builder from the Start menu of
Windows.
Choose the corresponding commands:
• Start | Advant | Engineering | Utilities | PROFIBUS Library Editor
• Start | Advant | Engineering | Utilities | Setup Add-Ons
• Start | Advant | Engineering | Utilities | CI57x LON Interface Generator.

3-8 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.1 Product Operation

Chapter 4 Runtime Operation

4.1 Product Operation

Function Chart Builder and Application Builder support function-oriented project engineering,
provide adequate objects, as shown in Table 4-1, and offer the same user interface for all of
them.

Table 4-1. Objects Processed by FCB

Objects
Node
Node structure (NS)
Circuit (CI)
Type circuit (TC)

You can work simultaneously on different parts of your project because the Function Chart
Builder allows connections to virtual elements (elements that are already specified but not yet
implemented).
Working with references to objects and their interfaces rather than working with object contents
ensures that you have a high degree of flexibility when you make modifications.
Expand object contents and check their interface during the late instantiation phase of the
project.
Textual representation, or source code, for all objects enables you to import customer data.

3BDS 100 595R401 4-1

Function Chart Builder User’s Guide
Chapter 4 Runtime Operation

4.2 Operating Overview

4.2.1 Interaction of Objects
For performance reasons, the Function Chart Builder works on binary internal data representa-
tion of all objects. They are also represented textually by source code. Editing any of the objects
node, node structure, circuit, or type circuit means working on the corresponding binary
representation. You can reference other objects by their source code. That means you generate
source code after editing an object, so you can refer to it in another object. See Figure 4-1 for
interaction of objects in the Function Chart Builder.
The display symbol stands for screen data and data entered on the keyboard, the disk symbol
stands for data in the Function Chart Builder’s internal data representation, and the printer
symbol stands for source code data (data in text representation). The thick lines show the main
data transformation paths.
A thin line with a dot on one end stands for the reference to the object shown by the arrow on
the other end of the line.

Generating

Editing TCs TC source code

Generating

Editing CIs CI source code

Generating

Editing NSs NS source code

Expanding and
checking
node data

Editing Generating

Node Data AMPL source code

Generating target code

for AC 100 Series
Loading target code

to AC 100 Series

Figure 4-1. FCB General Data Flow

For more detailed flow charts see Appendix B, Data Flow in Function Chart Builder.

4-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.2.2 Structure of Objects

4.2.2 Structure of Objects

In the Function Chart Builder, the elements of objects are grouped in the following sections:
• The PC Section contains process control elements (PC elements), which are the
elementary building blocks for process control logic. The PC elements may be structured
as process control programs (PC programs) within the PC section.
• The DB Section contains data base elements (DB elements), which provide views of
peripheral devices connected to a process station.
• The Symbol Section contains symbols, which are used to define parameters of type
circuits and circuits. They are also used as internal variables in type circuits and circuits.
• The TC/CI Terminal Section contains symbols, which are used to define terminals of
type circuits and circuits.
Not all objects have all 4 sections.
The objects can also have references to other objects. The following cases may occur:
• Circuits have references to type circuits.
• Node structures have references to circuits.
• Node structures have references to type circuits.
In a node all references are resolved and the contents expanded. You will, nevertheless, see type
circuit boundaries, but no circuit boundaries.

4.2.3 Editors
The Function Chart Builder provides view-oriented editors to manipulate elements of the
PC section, DB section, symbol section, and TC/CI terminal section.
The editors also handle references to type circuits and circuits.
The Function Chart Builder offers two kinds of diagrams for graphical representation of
PC sections:
• Tree diagram that gives you an overview of the control logic
• Function chart that gives you a more detailed view, including the connections between
the PC elements, circuits, and type circuits.
The Function Chart Builder has two PC editors corresponding to the two kinds of diagrams:
• Tree editor that enables you to create, modify, and delete PC elements
• Function chart editor that also enables you to connect and disconnect terminals.
In the DB section, the DB editor functions enable you to create, modify, and delete DB
elements and edit DB element properties.
In the symbol and TC/CI terminal sections, use the symbol editor to declare, modify, and delete
symbols and terminals, and define their type and default values or formulas.
For Advant Controller 100 Series targets the Function Chart Builder provides on-line editing
and test functions and diagnostics.

3BDS 100 595R401 4-3

Function Chart Builder User’s Guide
Chapter 4 Runtime Operation

4.3 Runtime Tutorial

In this section, you are encouraged to work through some practice exercises. By doing so, you
will become familiar with how to use the Function Chart Builder, how to work with its
commands, windows, and dialog boxes.
The exercises accentuate different aspects of work with the Function Chart Builder:

Table 4-2. Structure of Tutorial

No Application and Accent Sections

Example 1 Node and type circuits, From Section 4.3.1, Preparations in the
accent on elementary Application Builder to Section 4.3.19,
operations Completing the Application Program
Example 2 Node structure and circuits, From Section 4.3.22, Working with Node
accent on structuring an Structures and Circuits
application to Section 4.3.27, Expanding Node Data
and Producing Source Code
Example 3 AC 100 Series application, From Section 4.3.28, Working On-line with
accent on target control, an Application
diagnostics, test functions, to Section 4.3.49, On-line Editing of Data
on-line editing Base

Advant Engineering products, like the Function Chart Builder, are available as a set of 32-bit
applications to be installed and used under Windows NT® and Windows® 2000.
We suppose that you have an engineering station, that is, an AS 100ES or a PC, and Windows
NT or Windows 2000 and the corresponding products are installed on it. We suppose also that
you are familiar with handling programs in Windows and with general Windows terms.

NOTE
Earlier releases of Advant Engineering products were available also as 16-bit
applications running under Windows for Workgroups™. The windows, dialogs,
and usage of Advant Engineering product components is very similar under each
of the Windows operating systems.

4.3.1 Preparations in the Application Builder

Start the Windows NT or Windows 2000 operating system on the engineering station.
Start the Application Builder by choosing it in the Advant | Engineering start menu.
In Application Builder create the new project TT_10 by the File | New | Project command.
Enter AC 450 with SW QC02-BAS21* 7.0 as node type and do not select any options.
Then create the new node TT_10_PW by the File | New | Node command. Enter AC 450 with
SW QC02-BAS21* 7.0 as node type, 001,002 as net and node. Do not enter any comments.
Do not select any options.
We suppose that these entries correspond to the characteristics of the node, for which we
prepare a process control application program with the help of the Function Chart Builder.

4-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.2 Starting the Function Chart Builder

NOTE
Selecting node type and options means selecting a set of precompiled PC and DB
element libraries or selecting support of special target system features. Additional
PC and DB element libraries created by customers are also bundled as options.

4.3.2 Starting the Function Chart Builder

Start the Function Chart Builder from the Application Builder by the Tools | Function Chart
Builder menu command. In the Application Builder you selected the TT_10_PW node of the
TT_10 project, so you edit and process this object by the Function Chart Builder.
The Function Chart Builder opens the empty Function Chart Builder window.

Figure 4-2. Function Chart Builder Window Opened

The Function Chart Builder initializes the internal data representation of the node
TT_10/TT_10_PW, creates system DB elements, that is, inserts them for this node, then looks
for type circuits and circuits in the project-specific type circuit and circuit directories and in the
level1 and level2 type circuit element libraries, and checks if they are compatible with the actual
Function Chart Builder version (they must contain the lines VERSION TC 3 and TC_TYPE …
or VERSION CI 3 and CI_TYPE …).
You started the Function Chart Builder for the first time on a new object of the TT_10 project
and no project default page layout was defined in the Application Builder. The Function Chart
Builder presents the Page Setup dialog box, where you have to define the page layout for your
diagrams.
Set the following template and page size by using the mouse or the keyboard:

3BDS 100 595R401 4-5

Function Chart Builder User’s Guide
Chapter 4 Runtime Operation

Figure 4-3. Initial Page Setup Dialog Box

Activate the OK button. The Function Chart Builder opens the TT_10_PW.ODB window as
container for the initialized *.ODB file of TT_10_PW.

Figure 4-4. TT_10_PW.ODB Initialized

The *.ODB file is the internal, binary representation of objects in the Function Chart Builder.
The TT_10_PW.ODB window lists the sections of the TT_10_PW node:
• PC section with no, one, or more PC programs consisting generally of PC elements
• DB section containing DB elements.

4-6 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.3 Using Commands and Help

Node structures, circuits, and type circuits generally have a symbol section containing symbols
used as parameters of type circuits and circuits.
Circuits and type circuits generally have also a TC/CI terminal section containing symbols used
as terminals of type circuits and circuits.

4.3.3 Using Commands and Help

Pull the menus down with the mouse to see the commands.
The commands are available depending on the window, which has the focus. The commands,
which are not available, are dimmed.
The most frequently used commands are also presented in the Toolbar. In due case, resize or
maximize the Function Chart Builder application window to see the whole Toolbar.
Select, for example, the Help | Contents command by clicking with the mouse on the
icon in the Toolbar.
Windows opens the Help Topics window with contents, index, and full text search facility of
Help. In the title of the Help Topics window you find the major revision of Function Chart
Builder you are using.
Help has a hierarchical tree structure and several contents levels. To navigate in the Help Topics
window, double-click with the mouse, for example, on Function Chart Builder
Reference, then on Commands of Function Chart Builder to see the list of menus.

Figure 4-5. Help Topics Window

3BDS 100 595R401 4-7

Function Chart Builder User’s Guide
Chapter 4 Runtime Operation

Double-click on File Menu to see a detailed list of commands of a menu.

Double-click on File | Open Section | PC - for Node and NS.
This title in the contents is not further structured, it leads to a Help topic in the Help window.
It is shown in the following figure:

Figure 4-6. Help Information on a Command

Move the cursor over the figure in the Help window. The cursor changes to a hand if
there is additional help information pertaining to the given part of the figure. This happens, for
example, over the PC Program combo box. If you click with the mouse, the additional help
information is displayed in a popup window. Click to some other part of the Help window to
close it.
Navigate in the Help also by clicking on underlined (and generally green colored) words.
By clicking, for example, on PC Section window you get help information on the PC Section
window. The buttons Contents, Index, and so on, and the menu commands make it easy to get
the information you need, to navigate and find your way back.
By activating the Glossary button you find the Function Chart Builder-specific terms.
To access general, Windows related terms, choose the Help command in the Windows Start
menu, open Glossary, then double-click on Glossary Entries.

4-8 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.4 Creating the PC Section and a PC Program

To access help on Windows Help, choose the Help | How To Use Help command.

Click with the mouse on the close button of the Help window or the possible secondary
windows to close them.
To get immediate, context-sensitive help
1. Select the Help | On Context command by clicking with the mouse on the icon in
the Toolbar. The cursor changes to the form as shown in the icon.
2. Click on the window, dialog box or command name, about which you need information.
Windows opens the Help window if it is not open yet, and displays the corresponding help
information.
Click, for example, on the TT_10_PW.ODB window.
You get help on the *.ODB window.
To get help in dialog boxes, press F1 or activate the Help button.

4.3.4 Creating the PC Section and a PC Program

Create a PC program by selecting PC in the Section list box and activating the New button.
Alternatively, you can create a PC program by the File | New Section | PC command.
The Function Chart Builder displays the New PC Program dialog box. Fill the PC Program
text box as shown in the following figure:

Figure 4-7. Defining PC1 as New PC Program

Activate the OK button.

A PC program (of a node or node structure) contains always a PCPGM as top element.
The Function Chart Builder displays the Create Element dialog box to create the
PCPGM of PC1.
Fill cycle time = 20 (milliseconds) in Callname [(Call Parameters,…)] as shown in the
following figure:

3BDS 100 595R401 4-9

Function Chart Builder User’s Guide
Chapter 4 Runtime Operation

Figure 4-8. Creating PCPGM

Activate the OK button.
The Function Chart Builder opens the PC Section window in one of its possible forms.
Function chart and tree diagram are available in the Function Chart Builder as graphical
representations for PC programs. The Function Chart Builder offers two corresponding
PC editors. The diagrams, first of all the function charts, are normally several pages long.
They are generally much larger than a full window, even one page is larger than a full window.
The diagrams can be displayed in PC Section windows and can be printed.
The PC Section window consists of three panes divided by a horizontal and a vertical split bar.
You can move the bars and so change the division into panes either by dragging them by the
mouse or by choosing the View | PC Pane | Split Vertically or View | PC Pane | Split
Horizontally command and the UP, DOWN or LEFT, RIGHT keys.

Table 4-3. Panes of the PC Section Window

Pane Number Pane Position

1 Left
2 Upper right
3 Lower right

4-10 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.5 Adding PC Elements to PC Program

One of the comfortable ways to configure the panes of the PC Section window is the following:
1. Split the window vertically into two panes.
2. Display the tree diagram in the left pane for overview and fast navigation.
To define this view, select the left pane and choose one of the View | Tree … commands.
To see the contents of the PC Element, Headline, and Page columns appropriately, resize
them by dragging and dropping the divisions that separate the header parts at the top of the
pane.
3. Display the function chart in the right pane for editing and connecting PC elements.
To define this view, select the right pane choose the View | Function Chart command.
The tree diagram and the function chart of PC1 is displayed in the following way in the PC
Section window:

Figure 4-9. Tree Diagram and Function Chart of PC1

The PC program PC1 currently consists of only one element, PCPGM.

PC1 appears in the Contents combo box of the TT_10_PW.ODB window as contents of the PC
section. In the list box part you get all existing PC programs listed. The text box part shows the
actual selection.

4.3.5 Adding PC Elements to PC Program

Select one of the panes of the PC Section window of PC1, for example, the one with its tree
diagram. For this, click somewhere in pane 1. You can also use the F6 key to switch to a next
pane.
The procedure described in this section would be similar also if you worked with the function
chart of PC1.
The selected PC element is the PCPGM. It is shown highlighted and in the active pane also by a
dashed frame.

3BDS 100 595R401 4-11

Function Chart Builder User’s Guide
Chapter 4 Runtime Operation

Check that the Status Bar (at the bottom of the Function Chart Builder window) does not
display the SCRL indicator, that is, the slide mode is cleared. If necessary, clear the SCRL
indicator by pressing the SCROLL LOCK key.
Choose the Edit | Create command.
The Create Element dialog box appears. The list box contains all PC elements that can be
inserted on one level lower than the PCPGM.
Select CONTRM by clicking on it in the list box and activate the Call Parameters button.
The Function Chart Builder displays the Edit Call Parameters dialog box.
Enter the call parameter values 100 [ms] and 2nd place by clicking on each call parameter in the
list box, then editing their values in the Value text box as shown in the following figure:

Figure 4-10. Setting Call Parameters of CONTRM

Activate the OK button (of the Edit Call Parameters dialog box).
The Function Chart Builder closes the Edit Call Parameters dialog box.
Alternatively, you could have directly edited CONTRM(100,2,0) in the Callname text box of
the Create Element dialog box as shown in Figure 4-11.
Activate the Apply button in the Create Element dialog box.
The Function Chart Builder has created a CONTRM element and latter has become the selected
PC element in the PC Section window of PC1. Nevertheless, the Create Element dialog box
has remained open.

NOTE
Both the tree diagram in one pane and the function chart in the
other pane reflect the changes of the represented PC program.

4-12 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.5 Adding PC Elements to PC Program

Figure 4-11. CONTRM with Call Parameters

The Function Chart Builder changes the contents of the list box in the Create Element dialog
box. It contains now all PC elements that can be inserted on one level lower than the CONTRM.
Select AND from the list box or enter AND(2) in the Callname text box.
Activate the Apply button.
The Function Chart Builder updates the Create Element dialog box.
To insert a second CONTRM, leave the Create Element dialog box by activating the Close
button. Select the first CONTRM by clicking on it with the mouse in the tree diagram in the PC
Section window. Choose the Edit | Create command.
The Create Element dialog box reappears.
Select the On Same Level option button from the Insert group box.
The Function Chart Builder changes the contents of the list box in the Create Element dialog
box. Now you can insert CONTRM(100,3,0) with item designation PC1.2 in the same way as
you inserted the first CONTRM.
Insert a PC element on the level below the second CONTRM. For example, insert an OR(2)
with item designation PC1.2.1 in one of the ways shown for AND(2) before, but activate the
OK button instead of the Apply button.

3BDS 100 595R401 4-13

Function Chart Builder User’s Guide
Chapter 4 Runtime Operation

4.3.6 Inspecting the Function Chart and the Tree Diagram

Pane 1 of the PC Section window shows the tree diagram of PC1 of TT_10_PW.
Be sure it is the active pane.
Click once on the View menu. Or click with the right mouse button in the pane to open the
context menu with the commands that are most relevant in the current context. The Function
Chart Builder offers three checked commands to set the granularity of tree diagram presentation
on the screen:
Tree - All Elements, Tree - Structure Elements, Tree - Top of Page Elements
Try all the alternatives. Select the Tree - All Elements command to see all elements of PC1.
The tree diagram indicates the page divisions in the function chart of the PC program by dashed
lines. At the right end of the line you find the page number. To reveal it, enlarge the pane and
resize the columns PC Element, Headline, and Page by dragging the divisions that separate the
header parts at the top of the pane.
In case of soft, that is, not fixed, page numbers it is preceded by a hash mark ‘#’.
Page divisions structure the function chart of your PC programs. They are inserted
automatically at instantiation of the PCPGM element and each time a page is full and you add a
next PC element.
The function chart of PC1 has now one page.
If the PC Section window has the focus, the PC Section | Page Layout | … commands become
available.
Add a new page division at CONTRM PC1.1:
1. Select CONTRM PC1.1 in the tree diagram.
2. Choose the PC Section | Page Layout | Insert Page Division command.
3. Fill the Insert Page Division dialog box as shown in the following figure:

Figure 4-12. Inserting New Page Division

4. Activate the OK button.

4-14 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.6 Inspecting the Function Chart and the Tree Diagram

Insert a page division at CONTRM PC1.2 in the same way but leave the headline empty.
To edit the headline of page division at CONTRM PC1.2, proceed as follows:
1. Select CONTRM PC1.2 in the tree diagram.
2. Choose the PC Section | Layout | Modify Page Division command.
(If you click with the right mouse button on CONTRM PC1.2 in the tree diagram, the
context menu contains in this case also the Layout | Modify Page Division command.)
3. Fill the Modify Page Division dialog box as shown in the following figure:

Figure 4-13. Modifying Headline of Page 3

4. Activate the OK button.

If you called up the View | Tree - All Elements command recently, the tree diagram of PC1 has
the structure, page divisions, and headlines as shown on the following figure.
Move the vertical split bar to the right to increase pane 1 containing the tree diagram and drag
and drop the divisions between the PC Element, Headline, and Page header parts at the top of
the pane to reveal the headline texts:

Figure 4-14. Tree Diagram of PC1, Full Structure

Resize the panes and select pane 2 of the PC Section window with the function chart of PC1,
for example, by pressing F6.
Use the PC Section | Goto Page | … commands to see every page of the function chart.

3BDS 100 595R401 4-15

Function Chart Builder User’s Guide
Chapter 4 Runtime Operation

Use the PC Section | Goto Element | … commands to move the selection from PC element to
PC element. You automatically slide also pane 2 of the PC Section window over the function
chart in a way that the selected PC element always becomes visible.
Drag the scroll boxes to slide pane 2 horizontally and vertically over each function chart page to
see also the header and the headlines over the headers.
Try the arrow buttons in the left bottom part of pane 2 as alternative mouse shortcuts for
navigation in the PC program.

4.3.7 Creating the DB Section and DB Elements

Select DB in the Section list box of TT_10_PW.ODB window. The Contents combo box
contains an asterisk ‘*’. It indicates that the selected section is not empty.
Remember, the system DB elements were generated during the initialization of TT_10_PW.
Open the DB section by activating the Open button.
Alternatively, you can open a DB program by the File | Open Section | DB command.
The Function Chart Builder displays the DB Section window and lists the existing DB element
instances.

Figure 4-15. Opening the DB Section Window

To see only a subset of the DB elements, select another filter criterion from the Filter/Item Des.
drop-down combo box. Do not use other filter criteria than those listed here.
Or edit the text box part of the Filter/Instance Name drop-down combo box and press ENTER to
set a filter criterion for the name property of the DB element instances to be listed.
To create a new DB element, activate the Create button. Alternatively, you can create a DB
element by the Edit | Create command provided the DB Section window has the focus.
The Function Chart Builder displays the Create Element dialog box for DB elements. Select DI
in the list box or enter DI in the Callname text box as shown in the next figure.

4-16 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.7 Creating the DB Section and DB Elements

Leave the proposed DI* item designation of the DB element to be created in the Instance text
box. The * is a wildcard standing for the first free item designation.

Figure 4-16. Creating DI*

Activate the Apply button.

You have created the DI1 DI board and the pertaining DI1.1 to DI1.32 DIS channels.
Because you have activated the Apply button (and not the OK button), the Create Element
dialog box remains displayed still with the proposed instance DI*.
Activate the Apply button again.
Note that the Apply button is highlighted by a dashed frame around the label “Apply”, so it is
now the selected button. That means you could simply press the SPACE bar as the alternative to
double-clicking on the Apply button.
The Apply button is highlighted also by a thicker outline of the button, so it is now also the
default button. That means you could simply press the ENTER key as another alternative to
double-clicking on the Apply button. Or double-click on “DI” in the listbox.
The next free item designation was DI2, so you have created DI2 and its DI2.1 to 32 DISs.
To create an DI instance with explicit instance name, enter DI4 in the Instance text box.
Activate the OK button this time.
The Function Chart Builder closes the Create Element dialog box and the DB Section window
gets the focus again. Now it shows the lastly created DI4 in the text box and the lists also the
recently created DI1, DI2, and DI4 boards and the DI1.1 to DI1.32, DI2.1 to DI2.32, and DI4.1
to DI4.32 channels among the existing DB element instances in the list box.

3BDS 100 595R401 4-17

Function Chart Builder User’s Guide
Chapter 4 Runtime Operation

4.3.8 Editing DB Terminal Values

Select DI2.4 in the list box of the DB Section window, or enter DI2.4 as instance in the
appropriate text box.
To edit the properties of the selected DIS element, activate the Edit button.
Alternatively you can choose the Edit | Edit DB Terminal Values command.
The Function Chart Builder displays the Edit DB Terminal Values dialog box with a rectangle
symbolizing the base part of DI2.4, its terminals, and with a list of values next to the input
terminals.
Change, for example, the INV (invert) terminal from 0 to 1 as shown in the following figure:

Figure 4-17. Editing DB Terminal Values of DI2.4

Activate the OK button.

The Function Chart Builder closes the dialog box. The DB Section window has the focus again.

4-18 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.9 Deleting DB Elements

4.3.9 Deleting DB Elements

Choose DI1 from the list box or enter DI1 in the Instance field.
To delete DI1, activate the Delete button and answer Yes to the question “Do you really…?”.
Try the alternative methods of deleting a DB element:
• Choose DI2 from the list box or enter DI2 in the Instance field.
Be sure the DB Section window has the focus. Choose the Edit | Delete command.
• Or choose DI2 from the list box or enter DI2 in the Instance field.
Be sure the DB Section window has the focus. Press the DEL key, that is, the keyboard
shortcut of the Edit | Delete command.
Do not delete DI4.
The Function Chart Builder does not list the deleted DI1 and DI2 boards and their channels any
more among the existing DB element instances.

4.3.10 Saving Your Work

To ensure that you do not lose your work if a problem occurs causing the program to halt or
leave your work abruptly, save your work by the File | Save command. It copies all the
modifications, which you made, to the *.ODB file containing Function Chart Builder's internal
data representation. This is the common way to save an application program between two
Function Chart Builder sessions.
If you want to backup your application program and/or load it to a target system, use the
File | Generate Source command at first. See later.
Choose the File | Exit command to leave the Function Chart Builder. This command also saves
your work in the *.ODB file.
If you wish to leave the Function Chart Builder without saving your work, or just skip the
modifications, which you made since the last execution of the File | Save or
File | Generate Source command during the current session, choose at first the
File | Skip Modifications command.
CAUTION
Be aware that if you execute the File | Skip Modifications command, you lose all
the modifications, which you made since the last execution of the File | Save or
File | Generate Source command during the current session.

The Function Chart Builder application window closes, Application Builder regains the focus.

4.3.11 Working with Type Circuits

In the first part of this tutorial you practice creating type circuits and instantiating them in a
straightforward way in a node.
Suppose you need digital input channels of the DI data base element (DB element), always with
certain properties and in conjunction with some simple logic consisting of an AND and an OR
process control element (PC element). You create TC_10_T1 containing these elements.
You already inserted a DI in the TT_10_PW node and implicitly created its channels DIS.
So you can instantiate TC_10_T1 once or several times in TT_10_PW.
Each TC_10_T1 instance adds the AND/OR logic and modifies the channel properties as
specified.

3BDS 100 595R401 4-19

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.3.12 How to Create Type Circuits

You create and edit type circuits in the same way as nodes.
In Application Builder create the new type circuit TC_10_T1 by the File | New | Type Circuit
menu command.
Enter AC 450 with SW QC02-BAS21* 7.0 as node type. Do not enter any comments. Do not
select any options.
We suppose that these entries correspond to the characteristics of the targets, for which we
prepare this type circuit with the help of the Function Chart Builder.
Start the Function Chart Builder from the Application Builder by the Tools | Function Chart
Builder menu command.
The Function Chart Builder initializes the internal data representation of the TT_10/TC_10_T1
type circuit.
You started the Function Chart Builder for the first time on the new TC_10_T1 object of the
TT_10 project and no project default page layout was defined in the Application Builder. The
Function Chart Builder presents the Page Setup dialog box. Define the page layout in the same
way as you did for TT_10_PW.
Create the PC section of TC_10_T1 by the File | New Section | PC command.
Create an AND(2) and an OR(2) element by the Edit | Create command.
The Function Chart Builder shows these elements with the relative item designations * and *+1
in the PC Section window.

4.3.13 Declaring Symbols

To be flexible, type circuits must change their properties, or even their structure, on the basis of
actual values of parameters. The Function Chart Builder uses symbols as parameters. A symbol
is an identifier between ‘<’ and ‘>’. It stands for a value that is substituted at type circuit
instantiation in a node. (If it is instantiated in a node structure or a circuit, the symbol value can
be changed also after the instantiation.)
Create the symbol section of TC_10_T1 by the File | New Section | Symbol command.
The Function Chart Builder creates the empty Symbol Section window and opens the Create
Symbol dialog box.
Create the symbols MOD_NR and CH_NR standing for the module number (board number)
and channel number of the DIS element to be modified by TC_10_T1.
The actual values of these symbols must be unique for each instance of TC_10_T1 because you
cannot or should not modify, for example, the same channel twice.
So you select IU (instance-unique) for MOD_NR and CH_NR in the Kind group box.
These symbols will be used for substitution of string, for example, of maximum 2 characters.
So you select the type A (String) and edit 2 in the Size text box.
Do not select here the data type of the channel that is to be referenced with the help of these
symbols.

4-20 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.13 Declaring Symbols

Fill the Create Symbol dialog box for the <CH_NR> symbol as shown in the following figure:

Figure 4-18. Creating Symbol <CH_NR>

Activate the Apply button.

Fill the Create Symbol dialog box for the <MOD_NR> symbol similarly.
Activate the OK button.
The Symbol Section window contains the existing symbols as shown in the following figure:

Figure 4-19. Symbol Section of TC_10_T1

Note the asterisk ‘*’ at the end of the window title. It shows that the contents of the pertaining
section has been changed since the last Save command.

3BDS 100 595R401 4-21

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.3.14 Using Symbols

Create the DB section of TC_10_T1 by the File | New Section | DB command.
The Function Chart Builder creates the empty DB Section window and opens the Create
Element dialog box for DB elements.
To create a modifying DB element, select the Modify Attribute check box.
The Function Chart Builder displays in the list box all DB elements, which are available in this
context.
Select the DIS callname and enter the symbolic value DI<MOD_NR>.<CH_NR> in the
Instance text box of the Create Element dialog box according to the following figure:

Figure 4-20. Creating DI<MOD_NR>.<CH_NR>

Activate the OK button.

A modifying DIS DB element is created. It is selected in the DB Section window.
Activate the Edit button.
The Function Chart Builder displays the Edit DB Terminal Values dialog box for the DIS
element DI<MOD_NR>.<CH_NR>.
Change here the NAME terminal to IN<MOD_NR>_<CH_NR> and activate the OK button.
It is reasonable to save this portion of work. Choose the File | Save command.
In this section we have referenced only symbols, which were already declared in the symbol
section. The Function Chart Builder allows also entering undeclared symbols, for example, as
instance names. In this case it calls the Create Symbol dialog box automatically and lets you
declare symbols “on the fly”, too.

4-22 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.15 Defining Type Circuit Terminals

4.3.15 Defining Type Circuit Terminals

The terminals of type circuits (and circuits) are defined, in fact, also by symbols. You can have
input, output, or function parameter as terminal kinds and different data types as terminal types.
Via these TC/CI terminals you can connect the instantiated type circuit like a normal PC
element to other elements within the parent node (or node structure or circuit).
Create the terminal section of TC_10_T1 by the File | New Section | TC/CI Terminal
command.
The Function Chart Builder creates the empty TC/CI Terminal Section window and opens the
Create TC/CI Terminal dialog box.
Create the terminals IN and OUT standing for Boolean input and output of TC_10_T1,
respectively.
For the IN terminal fill the Create TC/CI Terminal dialog box as shown in the following
figure:

Figure 4-21. Creating a Type Circuit Input Terminal

Activate the Apply button.

3BDS 100 595R401 4-23

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

For the OUT terminal fill the dialog box as shown in the following figure:

Figure 4-22. Creating a Type Circuit Output Terminal

Activate the OK button.

The Function Chart Builder displays the TC/CI Terminal Section window with the created
terminals.

Figure 4-23. TC/CI Terminal Section Window

4-24 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.16 Connecting PC Terminals

4.3.16 Connecting PC Terminals

Select the PC Section window of TC_10_T1. Select the pane with the function chart.
(To select and configure panes, see Section 4.3.4, Creating the PC Section and a PC Program.)
Check that the Status Bar of the Function Chart Builder application window does not display
the SCRL indicator, that is, the slide mode is cleared. If necessary, clear the SCRL indicator by
pressing the SCROLL LOCK key.
We show different ways of connecting PC terminals.
Set the “classical” quick connect mode (as known before Function Chart Builder 4.7): choose
the Options | Preferences command, select the Quick Connect by Right Mouse Button check
box in the Preferences dialog box, and activate the OK button.
Click with the left mouse button on the output terminal of the AND element and click with the
right mouse button on the first input of the OR element.
To try the alternative connect mode, choose the Edit | Undo Connect PC command, choose the
Options | Preferences command, unselect the Quick Connect by Right Mouse Button check
box, and activate the OK button.
Click again with the left mouse button on the output terminal of the AND element and with the
right mouse button on the first input of the OR element. Now the Function Chart Builder opens
the context menu as usual. Here you can choose the Connect to Marked menu item, which is in
that case always directly under the cursor, with another click.
The Function Chart Builder connects the terminals and redraws the function chart after each
connection.
Press DOWN to select the OR element. Press LEFT or RIGHT to select different terminals of it.
Select the second input terminal of the OR element.
To connect it to a constant, choose the PC-Terminal | Connect command. Fill the Connect
dialog box as shown in the following figure:

Figure 4-24. Connecting to a Constant

Activate the OK button.

Select the first input of the AND element, for example, by clicking on it with the left mouse
button. To connect it to a DB terminal, choose the PC-Terminal | Connect command. Clear the
To text box in the Connect dialog box by pressing DEL. Activate the DB button.

3BDS 100 595R401 4-25

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder opens the Connect to DB dialog box and offers all the existing DB
elements of TC_10_T1 with terminals, which have the same data type as the terminal previously
selected in the function chart.
Select DI<MOD_NR>.<CH_NR>. VALUE is the default terminal to be connected. You can
select the DB terminal to be connected explicitly in the list part of the DB Terminal drop-down
combo box.
Activate the OK button in the Connect to DB dialog box, then the Apply/Next button in the
Connect dialog box.
The next terminal of the AND element is automatically selected in the Item Designation text
box. Clear the To text box by pressing DEL. To connect the selected terminal to a terminal of the
type circuit, activate the TC/CI Terminal button.
The Function Chart Builder opens the Connect to TC/CI Terminal dialog box and offers all
the existing type circuit terminals of TC_10_T1, which have the same data type as the terminal
previously selected in the function chart.
Select IN. Activate the OK button in the Connect to TC/CI Terminal dialog box, then the OK
button in the Connect dialog box.
Select the output terminal of the OR element, for example, by the PC-Section | Goto | Next and
the PC-Terminal | Goto | Last commands.
Or, you can activate the Next button in the Connect dialog box to select the output terminal of
the OR element as the next unconnected PC terminal.
To connect it to a type circuit terminal, choose the PC-Terminal | Connect command. Open the
drop-down list box of the To group box to see the recent connection strings. Edit T=<OUT> in
the To text box of the Connect dialog box. Activate the OK button.
The PC Section window regains the focus.
You see the following ready function chart of TC_10_T1:

Figure 4-25. Pane with Function Chart of TC_10_T1

Scroll the pane with the function chart in the PC Section window down.
Just above the footer you see the resolution of the placeholder >1):

>1) =DI<MOD_NR>.<CH_NR>/IN<MOD_NR>_<CH_NR>

4-26 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.17 Generating Source Code

4.3.17 Generating Source Code

To use TC_10_T1 in TT_10_PW, generate its source code. Choose the File | Generate Source
command.
The Function Chart Builder opens the Generate TC Source Code dialog box.

Figure 4-26. Generate TC Source Code Dialog Box

Activate the OK button.
The Function Chart Builder generates the type circuit source code and writes error messages,
warnings, and messages about the progress of code generation in the Output window.
In our case the Output window looks like this:

Figure 4-27. Output During Code Generation of TC_10_T1

The Function Chart Builder has generated the source code of TC_10_T1 in form of the
TC_10_T1.TCS file. It is now available for other nodes, node structures, and circuits of TT_10.
Choose the File | Exit command to leave the Function Chart Builder and return to the
Application Builder. Answer Yes to a possible question
Do you like to save all changes ...?

3BDS 100 595R401 4-27

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.3.18 Instantiating a Type Circuit

In the Application Builder select the Node List window or open it by the File | Open | Node
List menu command. Select TT_10_PW from the list box or enter TT_10_PW in the Node
Name text box. Start the Function Chart Builder by the Tools | Function Chart Builder menu
command.
The Function Chart Builder looks for available type circuits and circuits and opens the
TT_10_PW.ODB window.
Open the DB Section window. Check the presence of DI4 and DI4.1 to DI4.32.
Open the PC Section window of PC1. We want to instantiate TC_10_T1 here. TC_10_T1 does
not contain any structure elements, like CONTRM, just simple PC elements AND and OR. So,
it can be instantiated only on the level of the simple PC elements, for example below the PC1.1
CONTRM element. Press DOWN twice to select the PC1.1.1 AND element.
To instantiate TC_10_T1, choose the Edit | Create command. The On Same Level option is
selected in the Insert group box. Drop-down the list box part of the Element Type combo box.
The Function Chart Builder displays here the available element types, which were found at
start-up and which can be inserted on the level corresponding to the selected option in the Insert
group box. Select TC.
The Function Chart Builder displays TC_10_T1 as the available type circuit in the list box.
Select it as shown in the following figure:

Figure 4-28. Inserting TC_10_T1

4-28 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.18 Instantiating a Type Circuit

Activate the Symbol Values button.

The Function Chart Builder displays symbols MOD_NR and CH_NR and their data types and
default values in the Edit Symbol dialog box.
Remember DI4 is available in our node. So change the value of MOD_NR to 4 as shown in the
following figure:

Figure 4-29. Edit Symbol Values of TC_10_T1

Activate the OK button in the Edit Symbol Values dialog box and then in the Create Element
dialog box.
The Function Chart Builder instantiates the type circuit and writes error messages, warnings,
and messages in the Output window. Open it by the Window | Output command.
Check the last line in the Output window:
TC instantiated without errors.
Click with the mouse on the close button (or double-click on the Control Menu button
) of the Output window to close it.
The instantiated type circuit box PC1.1.2 appears below the AND element in the PC Section
window, in both panes.
The box contains the callname of the type circuit and the names of the type circuit terminals.
Default values are connected (if possible) to the type circuit terminals. For this reason, you find
the constant 1 connected to the input terminal IN of the type circuit.

3BDS 100 595R401 4-29

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.3.19 Completing the Application Program

To simplify the task, delete the PC elements PC1.2.1 OR and PC1.2 CONTRM:
Select PC1.2.1 OR by clicking on it, then press the SHIFT key and select PC1.2 CONTRM by
clicking on it, too. (You have made a multiple selection.)
Delete the selected PC elements by pressing the DEL key or by the Edit | Delete command.
Select the pane of the PC Section window with tree diagram of PC1 by the
View | PC Pane | Next command. Select PC1.1 CONTRM. Delete the page division by the
PC-Section | Page Layout | Delete Page Division command.
Select the pane of the PC Section window with the function chart of PC1.
Complete PC1 by connections as shown in the following figure:

Figure 4-30. Pane with Function Chart of PC1 of TT_10_PW, Final Stage

NOTE
In the function chart <n USERS> indicates multiple connection. We connected at
first D=1 to PC1:ON and D=0 to PC1:R, then PC1:ON to PC1.1:ON, and PC1:R
to PC1.1:SINGLE and PC1.1:R.

Generate source code for the complete node by the File | Generate Source command.

4-30 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.20 Preparing Documentation

The Function Chart Builder opens the Generate Source Code dialog box. Specify PWST as
source code file name as shown in the following figure:

Figure 4-31. Generating Source Code of TT_10_PW

Activate the OK button.

The Function Chart Builder generates the source code files PWST0101.AAX, PWST01.BAX
and the type circuit information file PWST0101.TIX. It lists the processed elements and,
possibly, warnings or error messages in the Output window.
Save your work by the File | Save command.

4.3.20 Preparing Documentation

Generally, you have to document your application program.
The Function Chart Builder offers paper documents of all sections of your application program.
You defined the page layout template already in Section 4.3.2, Starting the Function Chart
Builder.
The page layout has the following parts:
• Frame
• Text area containing the function chart, tree diagram, or other text information
• Headline (only with function charts)
• Footer with some fixed captions and areas to be filled with variable texts.

3BDS 100 595R401 4-31

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

See Figure 4-32 as an example:

Frame

Text area

Headline

Footer

Figure 4-32. A Document Page

You defined some headline texts with the page divisions for the function chart of the PC
program already in Section 4.3.6, Inspecting the Function Chart and the Tree Diagram.
You define the text of the footer separately for the documents of the DB section and for the PC
section. The footer of the DB section serves also for other DB related documents. The footer of
the PC section serves also for other PC program related documents.
To define the footer texts for PC1 as shown in Figure 4-32, click on the PC Section window, or
if it is closed, open it.
Choose the Edit | Document Texts command. You find this command also in the context menu
if you click with the right mouse button on the footer in the function chart pane.
The Function Chart Builder opens the Edit Document Texts - PC1 dialog box.

4-32 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.21 Printing Documentation

Figure 4-33. Editing the Footer for Documents of PC1

By pressing the TAB key you can step from a text area to the next one.
Enter appropriate texts. Then activate the OK button.
You can define the footer texts for the DB documents in a similar way. Just be sure the
DB Section window has the focus before choosing the Edit | Document Texts command.

4.3.21 Printing Documentation

Advant Engineering product components use the printer in the standard way it is supported by
Windows NT.
We suppose you installed your printer and an appropriate printer driver, your printer is ready to
print.
Check your printer settings by the File | Print Setup command.
Be sure the appropriate printer is selected.
The paper orientation and size have to correspond with the paper in the selected feeder of the
printer and with the template and size defined previously by the File | Page Setup command.
See Section 4.3.2, Starting the Function Chart Builder.
Choose the File | Print command.
The Function Chart Builder opens the Print dialog box as shown in Figure 4-34.
To print the documentation of the DB section, select the DB Section check box.
The Function Chart Builder opens the Print DB Section dialog box.
Just activate the OK button of this dialog box to close it.

3BDS 100 595R401 4-33

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-34. Print Dialog Box

The Function Chart Builder opens the Print PC Section dialog box.

Figure 4-35. Print PC Section Dialog Box

4-34 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.22 Working with Node Structures and Circuits

Select here Function Chart and All Pages in the Function Chart group and All Elements in
the Tree group. Select Print Only on Success in the Page Layout Check group.
Then activate the OK button of this dialog box to close it.
To start printing, activate the OK button of the Print dialog box.
The database listing is printed.
Print Only on Success is selected. So the Function Chart Builder checks at first whether all the
pages of the PC diagram can be printed with the current layout. In our example the PC diagram
layout check passes, and the PC diagram is printed.
Finally, the tree diagram is printed.
Choose the File | Exit command to leave the Function Chart Builder.

4.3.22 Working with Node Structures and Circuits

In this second part of the tutorial you practice working with the function-oriented project
engineering method. You structure a small project and build it as a node structure referencing
several circuits and type circuits.

NOTES
The exercise in this section shows you only one of the ways of working with
circuits (and type circuits) in a node structure. It does not reflect the large variety
of type circuit and circuit usage.

The example is intentionally very simple, thus not realistic. We constructed it

with the intention just to illustrate principles but not to burden you with too much
editing.

After completing the exercises in the previous sections, you are experienced in working with
Function Chart Builder menus, commands, and dialog boxes. For this reason, in the following
we describe the operator actions just on Function Chart Builder command level and not as
keyboard or mouse actions, stroke by stroke.

4.3.23 How to Structure Your Application

WATER, a node of TT_10, is responsible for manual control of three pumps. Each pump is
controlled by a push button and the state of control is indicated by lamps. The control part is
connected to the process by digital inputs and outputs.
Keeping in mind that control and signal parts are often projected independently, divide the
functions of this node into the following major parts and realize them using circuits:
• Circuit INPUT bundling dedicated digital inputs
• Circuit OUTPUT bundling dedicated digital outputs
• Circuits MOT_TOP, MOT_MID, MOT_BOT realizing the control part for the 3 motors.

3BDS 100 595R401 4-35

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

We propose the node structure in Figure 4-36.

MOT_TOP

INPUT MOT_MID OUTPUT

MOT_BOT

Figure 4-36. Structure of the Node WATER

Circuits are always unique in a project

They may, however, correspond with or be similar to a solution used in other projects.
It is probable that the circuits contain some typical parts that can be applied repeatedly.
We cover them by type circuits. We suggest to build the following type circuits:
• Type circuit CRDIN creating a DI module
• Type circuit CRDOUT creating a DO module
• Type circuit PUSHB containing control logic of a push button.
These type circuits are presumably used repeatedly in the nodes of this project, or they may be
part of a type circuit library and valid for many projects.
Note that CRDIN and CRDOUT are type circuits containing only a DB section.
For type circuit PUSHB, see the proposal on Figure 4-37.

Figure 4-37. Type Circuit PUSHB

PUSHB contains an SR-D PC element connected to a T flip-flop that is suitable to toggle

between the states <GO>=0 and <GO>=1 if <PUSH> changes from 0 to 1.

4-36 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.24 Preparing Type Circuits

4.3.24 Preparing Type Circuits

There is no difference in the nature, structure, and properties of type circuits projected to be
instantiated in node structures and those projected for nodes.
In the Application Builder create new type circuits CRDIN, CRDOUT, and PUSHB by the
File | New | Type Circuit menu command.
Enter AC 450 with SW QC02-BAS21* 7.0 as node type. Do not enter any comments. Do not
select any options.

Preparing CRDIN
CRDIN must create the DB element DI for a digital input module each time it is instantiated.
We suggest for it the module number <DI_NR> as a parameter.

NOTE
A symbol is here the natural choice. A TC terminal would not be the appropriate
means to convey a (parameter) value to the type circuit.

Select CRDIN and start the Function Chart Builder.

Create the new Symbol Section window.
Consider that each time you instantiate CRDIN you want to define another digital input module,
that is, you want to and have to create another DI element.
So define DI_NR as an IU (instance-unique) symbol. Define A*18 as its type and 1 as default
value.
Create the new DB Section window. Create a single DI element DI<DI_NR> with default
terminal values.
Generate source code for the complete type circuit. Exit the Function Chart Builder.

Preparing CRDOUT
CRDOUT must create the DB element DO for a digital output module each time it is
instantiated. We suggest for it the module number <DO_NR> as a parameter.
Select CRDOUT and start the Function Chart Builder.
Create the new Symbol Section window. Define DO_NR as an IU symbol, type A*18, with a
default value of 1.
Create the new DB Section window. Create a single DO element DO<DO_NR> with default
terminal values.
Generate source code for the complete type circuit. Exit the Function Chart Builder.

Preparing PUSHB
PUSHB must create a piece of PC program. It does not need to have parameters.
When instantiated, it will be connected to its environment by its terminals.
Select PUSHB and start the Function Chart Builder.

3BDS 100 595R401 4-37

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Create the new TC/CI Terminal Section window.

Create the Boolean input terminal PUSH.
Consider that PUSH will be connected to the clock input of an SR-D element.
So select the Dynamic attribute, and if set, clear the Non-Invertible attribute.
Create the Boolean output terminal GO.
Create the new PC Section window. Insert a single SR-D element.
It obtains * as item designation.
Select a pane with function chart. Invert input 2 and connect its terminals as suggested in
Figure 4-37.
Generate source code for the complete type circuit. Exit Function Chart Builder.

4.3.25 Preparing Circuits

For the sake of simplicity, each suggested circuit contains just one type circuit.
Here, the symbols of circuits will be used to convey actual values to the symbols of type circuits
contained in the circuits.
In Application Builder create new circuits INPUT, OUTPUT, MOT_TOP, MOT_MID, and
MOT_BOT by the File | New | Circuit menu command.
Enter AC 450 with SW QC02-BAS21* 7.0 as node type. Do not enter any comments. Do not
select any options.

NOTE
These circuits are very simple. Real circuits may contain PC elements as glue
logic, DB elements, and several type circuits instantiated in the PC or DB section
of the circuit.

Preparing INPUT
INPUT must provide the signals of a digital input module.
Create the DB element for the module with CRDIN.
For INPUT we suggest the module number <DIMODULE> as a parameter. It is a symbol of the
circuit. It is to be substituted as actual value of DI_NR, that is, of a symbol of the type circuit
CRDIN contained in this circuit. So DIMODULE will pass a value from the environment of
INPUT over to the final DI element inside of CRDIN.
Select INPUT in the Application Builder and start the Function Chart Builder.
Create the new DB Section window. Insert a single type circuit CRDIN.
Enter <DIMODULE> as the actual value for its DI_NR parameter.
Now you have referenced <DIMODULE>, a symbol that is not declared yet in the symbol
section. In this case the Function Chart Builder calls the Create Symbol dialog box
automatically and lets you declare symbols “on the fly”.
Define DIMODULE as an IU symbol of type A*18 with a default value of 1.

4-38 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.25 Preparing Circuits

Consider that DIMODULE is a parameter of the circuit. If an actual value is assigned to it later,
it will also be transferred to DI_NR.

Node structure

INPUT
Circuit

CRDIN
Type circuit
IN<DI_NR>
(DB element) <DI_NR> = <DIMODULE> = actual value
at instantiation

Figure 4-38. Value Substitution via <DIMODULE> and <DI_NR>

NOTE
After having created <DIMODULE>, do not forget to activate the OK button in
the Create Element dialog box to accomplish the instantiation of CRDIN in
INPUT.

In the DB Section window, $$TC1 is displayed to indicate that you instantiated a type circuit
containing a DB section but no PC section.
When instantiating a type circuit in a node structure or circuit, you insert only its frame
(envelope). The Function Chart Builder checks only the interface of the type circuit and asks
you to assign values to the parameters. The inside of the type circuit remains unknown and
invisible for the Function Chart Builder in these cases, corresponding to the principle of late
instantiation.
Generate source code for the circuit. Exit the Function Chart Builder.

Preparing OUTPUT
OUTPUT must provide signals of a digital output module.
Create the DB element for the module with CRDOUT.
For OUTPUT we suggest the module number <DOMODULE> as a parameter. It is to be
substituted as actual value of DO_NR for CRDOUT contained in this circuit. So DOMODULE
will pass a value from the environment of OUTPUT over to the final DO element inside of
CRDOUT.
Select OUTPUT in the Application Builder and start the Function Chart Builder.

3BDS 100 595R401 4-39

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Create the new Symbol Section window. Define symbol <DOMODULE>. If, for example,
you want to fix <DOMODULE> on circuit level, define it as a location-unique (LU) symbol.
Define its type and default value, for example, as A*18 and 1, respectively.
Create the new DB Section window. Insert a single type circuit CRDOUT. Enter
<DOMODULE> as the value for its DO_NR parameter.
For implicit symbol creation, see Preparing INPUT.
Consider that DOMODULE is a parameter of the circuit. If an actual value is assigned to it later,
it will also be transferred to DO_NR.
Generate source code for the circuit. Exit the Function Chart Builder.

Preparing MOT_*
MOT_* must create a piece of PC program. They do not need to have parameters.
When instantiated, they will be connected to their environment by their terminals.
Select MOT_TOP in the Application Builder and start the Function Chart Builder.
Create the new TC/CI Terminal Section window.
Create the Boolean input terminal PTOP. For PTOP enter 0 as the default value, select the
Dynamic attribute, and if set, clear the Non-Invertible attribute.
Create the Boolean output terminal GTOP.
Create the new PC Section window with the function chart. Insert the type circuit PUSHB once.
Connect pin 1 of the type circuit instance PUSHB to circuit terminal T=<PTOP>.
Connect pin 2 of PUSHB, that is, terminal GO, to circuit terminal T=<GTOP>.
You can use here also the shorter dedicated PC-Terminal | Connect Selected | To TC/CI
Terminal command.
Generate source code for the circuit. Exit the Function Chart Builder.
To keep it simple, prepare MOT_MID and MOT_BOT with the same content as MOT_TOP, but
name the terminals PMID and GMID and PBOT and GBOT, respectively.

NOTE
The MOT_* circuits are identical. Real motor control circuits having the same
interface may be very different.

4.3.26 Completing Node Structure by Circuits

You prepared circuits INPUT and OUTPUT containing mainly I/O and circuits MOT_*
containing mainly logic. Now you bring them together in node structure WATER.
Suppose the digital input module DI3 and its channels 1, 2, and 3, and the digital output module
DO1 and its channels 6, 8, and 10 are available for WATER.

4-40 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.26 Completing Node Structure by Circuits

Preparation in APB
In Application Builder create the new node WATER by the File | New | Node menu command.
Enter AC 450 with SW QC02-BAS21* 7.0 as node type, 001,003 as net and node. Do not enter
any comments. Do not select any options.
Select WATER and start the Function Chart Builder by the Tools | Node Structure Function
Chart Builder menu command.

Creating the PC Part

Open the PC Section window with the function chart, create PC1. Enter 20 as cyclicity of
PCPGM. Insert a CONTRM with cyclicity 100 and place 0 on the lower level. Insert, that is,
locate, the circuits MOT_TOP, MOT_MID, and MOT_BOT on the lower level. In the Create
Element dialog box, do not forget to select CI as element type.

Creating the DB Part

Open the DB Section window to locate the circuits INPUT and OUTPUT. In the Create
Element dialog box, do not forget to select CI as element type.
Define the physical layout by assigning actual values to the symbols declared in the circuits:
• Enter the value 3 for the DIMODULE symbol.
• Leave the default value 1 unchanged for the DOMODULE symbol.
The Function Chart Builder displays $$CI1 and $$CI2 in the DB Section window to indicate
located circuits containing only a DB section and no PC section.

Connecting Terminals
Disconnect the zeros from pin 1 of the circuits MOT_*.
By locating a circuit, you insert only its frame (envelope). Function Chart Builder checks only
the interface of the circuit and asks you to assign a value to the parameters. The inside of the
circuits remains unknown and invisible for Function Chart Builder while working on a node
structure (late instantiation). Nevertheless, you as user know the specification of type circuits
and circuits. You can also make connections immediately to terminals of DB elements that are
created within type circuits or circuits and exist and become visible only after the expansion of
these type circuits and circuits.
Connect pin 1 of the circuits to DI3.1, 2, and 3 by entering accordingly
=DI3.1 =DI3.2 =DI3.3
Connect pin 2 of the circuits to DO1.6, 8, and 10 by entering accordingly
=DO1.6 =DO1.8 =DO1.10
Connect the input terminals of PCPGM and CONTRM to appropriate constants 1 and 0.

Generating Source Code

Generate node structure source code. Exit the Function Chart Builder.
Ignore the warning “There are virtual connections”.

3BDS 100 595R401 4-41

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.3.27 Expanding Node Data and Producing Source Code

Working with node structure and circuits is a way of structuring projects. To obtain AMPL
source code, which you can translate and then load into the target system, you must resolve the
references in node structure and circuits and transform node structure to node.
Select WATER again and start the Function Chart Builder by the Tools | Function Chart
Builder menu command (and not by Tools | Node Structure Function Chart Builder).
You initialize WATER, this time as a node. This operation does not destroy the internal data
representation of the node structure WATER, nor the related source code.
Choose the File | Expand Node Structure command.
The Function Chart Builder resolves the circuit references in the node structure and the type
circuit references in the circuits, that is, references are replaced by the referenced objects.
Symbols are substituted successively by their values as shown, for example, in Figure 4-38.
The result is stored as internal data representation of the TT_10/WATER node. Nevertheless, the
type circuits remain visible in the PC Section window and the DB Section window.
After successful expansion generate source code for the complete node.
Use, for example, file name WATR.
The Function Chart Builder generates the AMPL source code files WATR0101.AAX and
WATR01.BAX, and the type circuit information file WATR0101.TIX.
These files can be translated and loaded to your target system by using appropriate Application
Builder menu commands and On-line Builder commands.
You can also print the documentation of WATER in the same way as you did it for TT_10_PW
in Section 4.3.20, Preparing Documentation and Section 4.3.21, Printing Documentation.

4-42 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.28 Working On-line with an Application

4.3.28 Working On-line with an Application

In this third part of the tutorial you practice working on-line with an application.
You get acquainted with the following features of the Function Chart Builder:
• Target code generation
• Target control functions
• Diagnostics
• Test functions (monitoring and forcing)
• On-line editing.
For these exercises you need an Advant Controller 100 Series target having digital input and
output. The exercises are shown for an AC 110 target but you can use any other Advant
Controller 100 Series target. The possible minor differences are pointed out for AC 55 and
AC 70.
After completing the exercises in the previous sections, you are experienced in working off-line
with Function Chart Builder menus, commands, and dialog boxes. For this reason, in the
following we describe in all details only the operator actions that concern on-line commands.
The application TT_10_DM evaluates the status of four switches and controls two lamps.
Suppose the AC 110 station hardware consists of a PM632 controller module, a DI620 input
module (in position 4), and a DO620 output module (in position 5).
(In case of AC 70, the hardware may consist of a PM810 controller module, a DI810 input
module in position 4, and a DO810 output module in position 5.
In case of AC 55, the hardware may consist of a CT482 basic unit containing also digital I/O.)
Realize the application with a simple node without any special structuring. See Figure 4-39:

PC1
PCPGM(20)
D=1 1 ON
D=0 2 R

.1
CONTRM(50)
DI1.1 DO 1.1/
1 ON RUN 5
DI1.2 CONTRM_RUN
2 >SINGLE MODP 6
DI1.3
3 R

DI1.4 .1
1 DO 1.2/
& 20
D=1 2 FLASH
3 o

Figure 4-39. PC Diagram, Draft

3BDS 100 595R401 4-43

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.3.29 Preparing an Advant Controller 100 Series Application Off-line

Preparation in Application Builder

Start the Application Builder. Create the new TT_10 project.
Create the new node TT_10_DM by the File | New | Node menu command.
Enter AC 110 2.1 as node type (or the node type of the available AC 70 or 55).
Suppose you have an isolated AC 110 node with addresses 0 and the node does not have any
options. Enter 0,0 as net and node and 0,0 also as bus and station. Ignore position. Do not enter
any comments. Do not select any options.
Select TT_10_DM and start the Function Chart Builder by the Tools | Function Chart Builder
menu command.

Creating the DB Part

Create the DB section of TT_10_DM by the File | New Section | DB command.
Create the processor module PM632.
Set its NAME terminal to PM1 and its WITH_BAT terminal to 1.
Create a DI620 element.
Set its POSITION terminal to 4.
Create a DO620 element.
Set its POSITION terminal to 5.
(In case of AC 70, create a PM810, a DI810, and a DO810.
In case of AC 55, create just a CT482 basic unit. It contains also the necessary I/O.)
Change the name of the DB terminal DO1.1 to CONTRM_RUN.
Change the name of the DB terminal of DO1.2 to FLASH.

Creating the PC Part

Create the PC section of TT_10_DM as PC1.
Create the PCPGM element with parameters 20,1.
Create a CONTRM element with parameters 50,2,0.
Create an AND element with 3 inputs on the level under CONTRM.
Invert input 3 of AND(3).
Connect the terminals of the PC elements as suggested in the draft in Figure 4-39.
Save the application by File | Save.
Generate source code with file names DEMO.

4-44 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.30 Generating Target Code

4.3.30 Generating Target Code

Applications can be loaded in target code form to an Advant Controller 100 Series target.
The controllers execute the target code directly. The application is prepared in internal data
representation in the Function Chart Builder, it is available as TT_10_DM.ODB.
To generate target code from it, choose the File | Generate Target Code command.
The Function Chart Builder opens the Generate Target Code dialog box.
For our example fill it as shown in the following figure:

Figure 4-40. Generate Target Code Dialog Box

Activate the OK button. If the following warning appears, activate its Yes button:

Figure 4-41. Changes in Sections, Warning

The Function Chart Builder generates the target code.

Depending on the completeness of your application program, its elements, and connections, the
application program may contain semantic errors. During target code generation the Function
Chart Builder opens the Output window and lists the errors, warnings, and other messages.

NOTE
If the corresponding option is set by the Options | Preferences command, the
Output window is iconized during target code generation for better performance.

In our example the target code generation list looks like Figure 4-42.
(You may have chosen the Window | Cascade command to rearrange the open windows.)

3BDS 100 595R401 4-45

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-42. Output Window in Foreground

Leave the Function Chart Builder, choose File | Exit. The Application Builder regains the focus.

4.3.31 Preparing the Connection

Connect the engineering station to the Advant Controller 100 Series target by an appropriate
cable. See Advant Controller 110 User’s Guide, Advant Controller 70 User’s Guide, and
Advant Controller 55 User’s Guide, respectively.
Be sure the configuration and addresses of the Advant Controller 100 Series target and its
modules correspond to those defined in the application program and in the Application Builder:
• In case of AC 110 and 70, check the station number on the rotary (or thumbwheel) switch.
In case of AC 55, set station number 0 for the node in the Application Builder.
• Check the types of modules.
• Check the position of the modules.
In case of AC 55, the positions correspond to the unit addresses.
Switch the power on at the power supply if applicable (for example, SA610).

4-46 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.32 Connecting to the Target

Reset the CPU module (or basic unit):

• In case of AC 110, set the start mode switch to CLEAR position.
In case of AC 55, set the start mode switch to CLEAR position 2.
• Push the INIT or RESET button as applicable.
If you have left the Function Chart Builder, start it again for TT_10_DM.
In that case the Function Chart Builder reopens its application window and the different
document windows (TT_10_DM.ODB window, PC Section windows with their panes,
DB Section windows, and so on), or even the recent selections, depending on the options set by
the Options | Preferences and Options | Workspace commands during the last session.

4.3.32 Connecting to the Target

The Function Chart Builder offers commands in the Target menu for target control functions.
Choose the Target | Connect command to connect the Advant Controller 100 Series target to
the engineering station logically.
The Function Chart Builder opens the Connect Target dialog box.
Suppose the cable to the AC 110 (or other AC 100 Series target) is connected to the COM2
connector of the engineering station and you selected the following suitable item in the
Connection Path drop-down list box, in the connection history.
(In more complex cases activate the Connect Assistant. It guides you through the steps of
connection path definition and address assignment.)

Figure 4-43. Connect Target Dialog Box

Activate the OK button.

3BDS 100 595R401 4-47

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder tries to connect the controller and the engineering station.
If the conditions mentioned in Section 4.3.31, Preparing the Connection are not met, the
Function Chart Builder warns you, for example, by the following message:

Figure 4-44. Target Not Reached, Warning

In our example the Function Chart Builder establishes the connection between the AC 110
target (or other AC 100 Series target) and the engineering station successfully. Then it opens
two windows and shows the Status Report and the Options Report in them.
Suppose the RAM and the PROM of the target are empty.
The No errors detected static text is displayed and the Report Errors button is dimmed in the
Status Report if the target system has a correct state:

Figure 4-45. Status Report After Target | Connect

Not equal signs “<>” indicate differences between three columns of the Status Report.
See Section 4.3.37, Using the Diagnostics (Diagnosis) Program for case of errors.
The Options Report compares the options and the base software as selected on the engineering
station (in fact, in the Application Builder) and as available on the on-line connected target:

4-48 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.33 Synchronizing the Target

Figure 4-46. Options Report

The options and the base software are identified in one of the following forms:
ident_string major_release . minor_release
ident_string major_release . minor_release / revision
For successful on-line operations the base software and all the options selected in the
engineering station must be available in the on-line connected target.
The ident_string, major_release, and minor_release of the item selected in the engineering
station must equal the ident_string, major_release, and minor_release of the corresponding item
available on the target. That means, revision is not evaluated.
In our example these conditions are met.

4.3.33 Synchronizing the Target

Time identifies programs and events. It is important to synchronize the clock of the on-line
connected Advant Controller 100 Series target to the one of the engineering station.
Choose the Target | Set Date and Time command.
The Function Chart Builder opens the Set Date and Time dialog box with the actual time on the
engineering station and the target, for example:

Figure 4-47. Set Date and Time Dialog Box, Phase 1

3BDS 100 595R401 4-49

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Activate the Synchronize Target button.

The Function Chart Builder updates the Set Date and Time dialog box, for example:

Figure 4-48. Set Date and Time Dialog Box, Phase 2

Activate the Close button.

4.3.34 Downloading the Target Code

Conditions to load an application program to an Advant Controller 100 Series target are the
following:
• Target code has been generated.
• The target is connected to the engineering station by cable.
• The target is connected.
• The target is blocked.
We met these conditions in the previous sections. (If the target were deblocked, see Section
4.3.35, Deblocking/Blocking User Application Program to block it.)
Now choose the Target | Load Application command to load the application program.
For safety reasons the Function Chart Builder prompts you to confirm this command:

Figure 4-49. Confirm Start Download

Download is an action modifying the state of the target. Release such actions by the keyboard,
rather then with the mouse. Press Y for Yes.
The Function Chart Builder downloads the application program.
The download has succeeded. So the Function Chart Builder offers switching to on-line mode.

4-50 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.34 Downloading the Target Code

Figure 4-50. Confirm Switching Directly to On-line Mode

To keep the capability of working on-line with this application, press Y for Yes.
Read and quit the warning at switching to on-line mode by clicking on the OK button:

Figure 4-51. Warning at Switching to On-line Mode

The on-line mode is indicated in the Title of the document windows, for example:

Figure 4-52. On-line Mode Indication in Title

Remember you generated target code and loaded it to the target. So the internal data
representation TT_10_DM.ODB corresponds exactly to the application program in the target.
Once in on-line mode, the Function Chart Builder will help you to keep the accordance of the
internal representation with the application in the target:
If you disconnect the target, the Function Chart Builder switches from on-line mode to on-line
preparation mode limiting the modification of the application and ensuring continuation of on-
line work after reconnection of the target.

3BDS 100 595R401 4-51

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTE
On-line preparation mode has been introduced with Function Chart Builder 4.6/0.

After the download, the Function Chart Builder opens the Output window and shows there the
protocol of the download. In case of our example it looks like this:

Figure 4-53. Output Window After Download

NOTE
Click with the right mouse button in the Output window to open a context menu.
Use the Save As context menu command to save the download protocol in a file.

The Function Chart Builder updates the Status Report window:

Figure 4-54. Status Report After Download

4.3.35 Deblocking/Blocking User Application Program

To deblock, that is, to start, the application program in the on-line connected target, choose the
Target | Deblock Program command.

4-52 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.36 Saving Application in Target

For safety reasons the Function Chart Builder prompts you to confirm this command:

Figure 4-55. Confirm Deblock Program

Release deblocking by the keyboard, rather then with the mouse. Press Y for Yes.
The Function Chart Builder deblocks the application program and updates the Status Report
window:

Figure 4-56. Status Report After Deblock

To block, that is, to stop, the application program in the on-line connected target, choose the
similar Target | Block Program command.

4.3.36 Saving Application in Target

After being tested and finalized, application programs must be saved in the non-volatile PROM
of the Advant Controller 100 Series target.
Choose the Target | Save in PROM command to copy the application program from the RAM
of the on-line connected target to its PROM.

3BDS 100 595R401 4-53

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

For safety reasons the Function Chart Builder prompts you to confirm this command:

Figure 4-57. Confirm Save in PROM

Release saving in PROM by the keyboard, rather then with the mouse. Press Y for Yes.
The Function Chart Builder copies the application program from the RAM of the target to its
PROM and after a while informs you by the following message:

Figure 4-58. Saved in PROM, Message

The Function Chart Builder updates the Status Report window again:

Figure 4-59. Status Report After Save in PROM

4-54 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.37 Using the Diagnostics (Diagnosis) Program

4.3.37 Using the Diagnostics (Diagnosis) Program

In case of errors the Function Chart Builder displays a Status Report like this:

Figure 4-60. Status Report with Errors Detected

To identify and localize errors, use the Diagnostics (Diagnosis) program attached to the
Function Chart Builder.

NOTES
The Diagnostics (Diagnosis) program is adapted to the different diagnostics
features of both former and recent controller versions.
In case of AC 110 2.0, AC 70 1.0, and AC 55 1.0 the Function Chart Builder calls
the Diagnosis program.
In case of AC 100 Series targets of newer node types, such as AC 160, AC 110
2.1 and higher, AC 80, AC 70 1.1 and higher, and AC 55 1.1, the Function Chart
Builder calls the Diagnostics program.

Corresponding to the advanced features of newer AC 100 Series node types,

the usage of the Diagnostics program is more simple and more direct.

In our case we have an AC 110 2.1 node and you exercise with the Diagnostics program.
Start the Diagnostics program by activating the Report Errors button in the Status Report
window or choose the Target | Diagnostics and then the Target | Report Errors command.
The Diagnostics (Diagnosis) program has the following functions:
• Reads the errors reported from the on-line connected Advant Controller 100 Series target
and collected since the last clear by an appropriate diagnostic command.
• Opens the Error Report window and displays the errors there.

3BDS 100 595R401 4-55

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Let us illustrate these functions by an example:

Suppose you programmed the PM632 with the property WITH_BAT=1 in the DB section
but the battery is missing.
The Error Report looks like this:

Figure 4-61. Error Report - No Battery Plugged

Plug the battery. Or switch off-line, edit WITH_BAT=0 in the PM632 DB element,
generate target code, and reload it.
Delete the error. Leave Diagnostics with its own File | Exit command.

NOTES
Some errors are deleted by being read. Other ones need an explicit Diagnostics
command, for example, Target | Delete Reported Errors.

Errors Detected may indicate also errors which occurred during or at the end of
the previous connection.

For more information see Section 4.4.7.1, Diagnostic Procedures with the Diagnostics Program
and Section 4.4.7.2, Diagnostic Procedures with the Diagnosis Program.
(In case of AC 70 or 55, a power failure, caused by switching of the power for a short time,
may be a similar situation for exercising with the Diagnostics/Diagnosis program.)

4-56 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.38 About On-line Test Functions

4.3.38 About On-line Test Functions

Terms
The Function Chart Builder supports the following on-line test functions in the on-line
connected Advant Controller 100 Series target:
• Monitoring (display of) PC terminals
• Monitoring (display of) DB terminals
• Forcing PC terminals
• Forcing of the VALUE terminals of extended DB elements
• Setting writable and PC-connectable DB terminals.
Monitoring means a single or cyclic observation of a value in the on-line connected controller
and displaying it in the engineering station.
Forcing means preparation of a value in the engineering station and its forcing in the on-line
connected controller. The force value is effective in the application program running on the
controller until deactivation of forcing.
Setting means preparation of a value in the engineering station and setting it once in the on-line
connected controller. The set value is effective on the controller until the value is overwritten,
for example, by the application program itself in its next execution cycle.
Extended DB elements are complex DB elements with the following properties:
• They allow definition of signals independently of the hardware, also for MMI purposes.
• Encapsulate channel elements.
• Support signal distribution and event transfer on the Advant Fieldbus 100.
• Create automatically all the DB elements necessary for the communication, such as DSP,
DAT, EVS(S), and MDAT.

NOTE
Extended DB elements have been introduced with AC 110 2.1.
They are supported by Function Chart Builder versions 4.3/0 and higher.

Conditions of On-line Testing

Conditions of forcing and monitoring terminals (as well as of editing an application program) in
the on-line connected target are the following:
• Exactly the same target code is downloaded to the target as the one selected in the
Function Chart Builder. The on-line preparation mode and on-line mode facilitate keeping
the accordance of the internal representation with the application in the target.
• The target is deblocked.
We met these conditions in the previous sections: The on-line mode is indicated in the Title of
the document windows, and if the target were blocked, see Section 4.3.35, Deblocking/Blocking
User Application Program to deblock it.

3BDS 100 595R401 4-57

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder offers preparatory commands in the PC-Terminal menu and on-
line test commands in the Test menu.

4.3.39 Preparing PC Terminals for Display

Preparation of PC Terminals for Display

Steps of preparing PC terminals for display:
1. Select a pane of the PC Section window with function chart.
2. Select the PC terminals for monitoring, then choose the PC-Terminal | Select for Display
| Select command or unselect them by PC-Terminal | Select for Display | Unselect.
Or, alternatively, click with the right mouse button on the terminal and choose the
equivalent Select/Unselect for Display command from the context menu.
You can prepare PC terminals for display also in the Test Table window:
1. Choose the Window | Test Table command to open the Test Table window.
To see the prepared terminals, select All or PC Display in Signal Select Filter.
2. Resize the columns of the Test Table window by dragging the divisions that separate the
header parts Instance, Terminal, and so on, to overview and check the terminals selected
for monitoring. Some divisions may be visible only if you enlarge the window.
You will need typically the columns Instance, Terminal, Value on Target, Physical Unit,
Type, and State.
3. Activate the Create/Edit… button in the List Entry group of the Test Table window.
Or choose the Edit | Create command.
The Function Chart Builder opens the Create/Edit Table Entry dialog box.
4. Enter the item designation of an existing PC element in the text box part of the
Element[:Terminal] or Signal Name drop-down list box or select it from the drop-down
list box part.
If the terminal is not defined yet, enter the name of the PC element terminal to be
monitored in the text box part of the Terminal drop-down list box or select it from the
drop-down list box part. Select the For Display option.
Activate the OK button, or if you want to remain in the Create/Edit Table Entry dialog
box, activate the Apply button.
The Function Chart Builder fills the Test Table window depending on the filter settings with PC
elements and terminals to be monitored.
The Value on Target column contains question marks ‘?’. That shows that no values are
fetched from the target yet. In the State column a ‘D’ indicates an entry for monitoring.

Preparation in On-line Preparation Mode

Suppose you disconnected the AC 110 (or other AC 100 Series target) by the
Target | Disconnect command in our example. The Function Chart Builder switched from the
on-line mode to on-line preparation mode.
Select a pane of the PC Section window the function chart. Select input 3 of AND(3).
Choose the PC-Terminal | Select for Display | Select command.

4-58 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.39 Preparing PC Terminals for Display

The Function Chart Builder marks the terminal with asterisks ‘*’ in the function chart:

Figure 4-62. PC Terminal Selected for Display, On-line Preparation Mode

You can choose the View | Prepared Variables command to see (or hide) the PC terminals,
which are already selected for monitoring.

Preparation in On-line Mode

You can select PC terminals for monitoring in the same way as you it do in on-line preparation
mode.
Suppose in our example the target is not connected.
Reconnect the AC 110 (or other AC 100 Series target) by the Target | Connect command.
The Function Chart Builder displays the Status Report and the Options Report window.
Suppose there are no errors and the Function Chart Builder from on-line preparation mode to
on-line mode.
The Function Chart Builder warns you at entering the on-line mode:

3BDS 100 595R401 4-59

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-63. Entering On-line Mode, Warning

Activate the OK button.

Be sure that the Function Chart Builder is on-line mode:
there is a check mark ‘ ’ next to the On-line Mode command in the File menu.
Select a pane of PC Section window with function chart.
Click with the right mouse button on output 5 of CONTRM and choose the Select/Unselect for
Display command from the context menu.
The Function Chart Builder marks also this terminal with asterisks ‘*’ in the function chart:

Figure 4-64. PC Terminal Selected for Display, On-line Mode

4-60 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.40 Displaying PC Terminal Values On-line

4.3.40 Displaying PC Terminal Values On-line

To display PC terminal values proceed as follows:
1. Select a pane of PC Section window with function chart or the Test Table window.
2. Check PCPGM State in the Status Report. If the PC program is blocked (stopped),
choose the Target | Deblock Program command to deblock (start) it.
3. Update the display of PC terminal values by the Test | Single Display or Test | Cyclic
Display command.
In our example a pane of PC Section window with function chart is selected.
Choose the Target | Deblock Program command to deblock (start) it.
Check PCPGM State is deblocked in the Status Report.
Choose the Test | Single Display command.
The Function Chart Builder displays the monitored values on the connection line near the PC
terminals in the function chart.
If you set the switches so that the process signal is 1 on channel DI1.1 and 0 on channels DI1.2
to 4 to 0, the function chart looks like this:

Figure 4-65. Monitored Values in Function Chart

3BDS 100 595R401 4-61

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Choose the Window | Test Table command to open the Test Table window.
Select All in Signal Select Filter.
Resize the columns of the Test Table window by dragging the divisions that separate the header
parts, so that the columns Instance, Terminal, Value on Target, Type, and State become
visible.
The Function Chart Builder displays the monitored PC terminal values in the Value on Target
column.
To illustrate the alternative method, activate the Create/Edit button in the Test Table window.
The Function Chart Builder displays the Create/Edit Table Entry dialog box.
Edit PC1.1:3 as additional PC terminal to be monitored in the Element[:Terminal] or Signal
Name text box:

Figure 4-66. Create/Edit Table Entry Dialog Box

Activate the OK button.

Choose the Test | Single Display command again.

4-62 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.40 Displaying PC Terminal Values On-line

The Function Chart Builder displays the monitored values in the Test Table but also in panes of
PC Section windows with function chart, which are at the moment in the background.
The Test Table looks like this:

Figure 4-67. Test Table with PC Display Values

Now select a PC Section window pane with function chart.

Choose the Test | Cyclic Display command.
The Function Chart Builder displays the monitored values in panes of PC Section windows
with function chart but also in the Test Table, which is at the moment in the background.
The values are periodically updated.
The time stamp of the values is shown in the Status Bar.

3BDS 100 595R401 4-63

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder application window and the PC-Section window look like this:

Figure 4-68. Cyclic Display

To stop cyclic monitoring, choose the Test | Stop Display command.

You can also use the Test | Set Trigger command to define the condition, at the occurrence of
which cyclic monitoring stops automatically.

4-64 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.41 Preparing PC Terminals for Forcing

4.3.41 Preparing PC Terminals for Forcing

Preparation of PC Terminals for Forcing

Steps of preparing PC terminals for forcing:
1. Select a pane of PC Section window with function chart.
2. Select the PC terminals for forcing, then choose the PC-Terminal | Force Value |
Create/Edit command or unselect them by the PC-Terminal | Force Value | Delete
command.
You can prepare PC terminals for forcing also in the Test Table window:
1. Choose the Window | Test Table command to open the Test Table window.
To see the prepared terminals, select All or PC Force in Signal Select Filter.
2. Resize the columns of the Test Table window by dragging the divisions that separate the
header parts Instance, Terminal, and so on, to overview and check the terminals selected
for forcing. Some divisions may be visible only if you enlarge the window.
You will need typically the columns Instance, Terminal, Force Value, Value on Target,
Type, and State.
3. Activate the Create/Edit… button in the List Entry group of the Test Table window.
Or choose the Edit | Create command.
The Function Chart Builder opens the Create/Edit Table Entry dialog box.
4. Enter the item designation of an existing PC element in the text box part of the
Element[:Terminal] or Signal Name drop-down list box or select it from the drop-down
list box part.
If the terminal is not defined yet, enter the name of the PC element terminal to be forced in
the text box part of the Terminal drop-down list box or select it from the drop-down list
box part.
Select the For Force option.
Enter the force value in the text box part of the Value drop-down list box or select it from
the drop-down list box part.
Activate the OK button, or if you want to remain in the Create/Edit Table Entry dialog
box, activate the Apply button.
The Function Chart Builder fills the Test Table window. The Value on Target column contains
question marks ‘?’. That shows that no values are fetched from the target yet. In the State
column a ‘P’ indicates an entry prepared for forcing and an ‘R’ an entry prepared for removal
from the table.

Preparation in On-line Mode

You can select terminals for forcing in on-line preparation mode in the same way
as you do it in on-line mode.
Be sure the target is connected and on-line mode is selected:
there is a check mark ‘ ’ next to the On-line Mode command in the File menu.
We continue our example at this point.
Select a pane of PC Section window with function chart.

3BDS 100 595R401 4-65

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Select input 1 of AND(3).

Choose the PC-Terminal | Force Value | Create/Edit command.
The Function Chart Builder displays the Create/Edit Force Value dialog box.
The Item Designation text box reflects the selection.
Edit 0 as force value as shown in the following figure:

Figure 4-69. Create/Edit Force Value Dialog Box

Activate the Apply button.

The Create/Edit Force Value dialog box remains displayed.
Force, for example, the output of AND to 1.
To define a next terminal for forcing, you can directly edit the Item Designation text box of the
Create/Edit Force Value dialog box.
Enter PC1.1.1:20 in the Item Designation text box and 1 in the Value text box.
Activate the OK button.

4-66 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.42 Forcing PC Terminals On-line

4.3.42 Forcing PC Terminals On-line

To force PC terminals proceed as follows:
1. Select a pane of the PC Section window with function chart or the Test Table window.
2. Check PCPGM State in the Status Report. If the PC program is blocked (stopped),
choose the Target | Deblock Program command to deblock (start) it.
3. Activate the force values for the PC terminals by the Test | Activate All Force Values
command.
In our example a pane of the PC Section window with function chart is selected. The target is
deblocked.
Choose the Test | Activate All Force Values command.
The Function Chart Builder opens the Activate Force Values dialog box where you can specify
chaining of force and display actions.
Press DOWN to fill it as shown in the following figure:

Figure 4-70. Chaining Force and Single Display

Activate the OK button by pressing ENTER.

The Function Chart Builder forces the corresponding PC terminals of the on-line connected
target, then monitors the PC terminals.

3BDS 100 595R401 4-67

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder updates the forced and monitored values in the panes of the PC
Section windows with function chart.

Figure 4-71. Function Chart with Forced and Monitored Values

Choose the Window | Test Table command to open the Test Table with the forced values and
see the values also in table form.
Select All Force (DB & PC) in Signal Select Filter.
Resize the columns of the Test Table window by dragging the divisions that separate the header
parts, so that the columns Instance, Terminal, Force Value, Value on Target, Type, and State
become visible.
You can change the order of the columns by dragging the header parts to the required position.
You can also set or invert the sort order by clicking on the header part, according to which you
want to sort the entries.
An icon or in the corresponding header part indicates the sorting.

The Test Table window looks like this:

4-68 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.42 Forcing PC Terminals On-line

Figure 4-72. Test Table with PC Force Values

Choose the Test | Deactivate All Force Values command or select All in the Force group of
Test Table and click on the Deactivate All button to stop forcing the on-line connected target.
The Function Chart Builder prompts you to confirm this action:

Figure 4-73. Confirmation of Force Deactivation

Activate the OK button by pressing ENTER. Choose the Target | Disconnect command.
Due to the terminal selection for forcing in on-line mode the Function Chart Builder warns you:

Figure 4-74. Change in Test Table, Warning

3BDS 100 595R401 4-69

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Activate the Yes button to save the contents of the Test Table in TT_10_DM.ODB.
Disconnecting involves switching from the on-line mode to the on-line preparation mode.
Now the target is not connected any more but the on-line preparation mode ensures the
accordance of the internal representation with the application in the target, hence a later return
to on-line mode.

4.3.43 Preparing DB Terminals for Display

Preparation of DB Terminals for Display

Steps of preparing DB terminals for display:
1. Select the DB Section window just to have an overview of created DB elements.
2. Choose the Window | Test Table command to open the Test Table window.
To see the prepared terminals, select All or DB Display in Signal Select Filter.
3. Resize the columns of the Test Table window by dragging the divisions that separate the
header parts to overview and check the terminals selected for monitoring. Some divisions
may be visible only if you enlarge the window.
You will need typically the columns Instance, Terminal, Value on Target, Type,
Description, and State.
4. Activate the Create/Edit… button in the List Entry group of the Test Table window.
Or choose the Edit | Create command.
The Function Chart Builder opens the Create/Edit Table Entry dialog box.
5. Enter an equal sign ‘=’ and the instance name of an existing DB element in the text box
part of the Element[:Terminal] or Signal Name drop-down list box or select it from the
drop-down list box part.
If the terminal is not defined yet, enter the name of the DB element terminal to be
monitored in the text box part of the Terminal drop-down list box or select it from the
drop-down list box part.
Select the For Display option.
Activate the OK button, or if you want to remain in the Create/Edit Table Entry dialog
box, activate the Apply button.
The Function Chart Builder fills the Test Table window. The Value on Target column contains
question marks ‘?’. That shows that no values are fetched from the target yet. In the State
column a ‘D’ indicates an entry for monitoring.

Preparation in On-line Preparation Mode

Suppose you disconnected the AC 110 (or other AC 100 Series target) by the
Target | Disconnect command in our example.
Select the DB Section window and the Test Table window.
Select DB Display in Signal Select Filter.
Resize the columns of the Test Table window by dragging the divisions that separate the header
parts, so that the columns Instance, Terminal, Value on Target, Type, Description, and State
become visible.

4-70 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.43 Preparing DB Terminals for Display

Activate the Create/Edit… button in the List Entry group of the Test Table window.
Enter =DO1.1 as DB element and VALUE as terminal to be monitored in the Create/Edit
Table Entry dialog box.
Select the For Display option.
Activate the OK button.

Figure 4-75. Preparing DB Values in Test Table, On-line Preparation Mode

Preparation in On-line Mode

You can select DB terminals for monitoring in the same way as you do it in the on-line
preparation mode.
Be sure that the Function Chart Builder is on-line mode.
See Section 4.3.39, Preparing PC Terminals for Display (Preparation On-Line) for reconnecting
the AC 110 (or other AC 100 Series target) and switching to on-line mode.
We continue our example at this point.
Open the Test Table window by the Window | Test Table command.
Activate the Create/Edit… button in the List Entry group of the Test Table.
The Function Chart Builder opens the Create/Edit Table Entry dialog box.
Enter =DI1.1 as DB element and VALUE as a second DB terminal to be monitored in the
Create/Edit Table Entry dialog box.
Select the For Display option. Activate the OK button.

3BDS 100 595R401 4-71

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.3.44 Displaying DB Terminal Values On-line

To display DB terminal values proceed as follows:
1. Open the Test Table window.
2. Check PCPGM State in the Status Report. If the PC program is blocked (stopped),
choose the Target | Deblock Program command to deblock (start) it.
3. Update the display of the DB terminal values by the Test | Single Display or Test | Cyclic
Display command. Or you can activate the Single or the Cyclic button in the Display
group of the Test Table.
In our example the Test Table window is selected.
Being in on-line mode, the Function Chart Builder does not dim the buttons in the Display
group.
Check PCPGM State is deblocked in the Status Report. If it is blocked, choose the
Target | Deblock Program command to deblock (start) the application.
Activate the Single button in the Display group to fetch DB terminal values from the target.
The Function Chart Builder displays the monitored values in the Value on Target column
instead of the question marks.

Figure 4-76. Monitored DB Values in Test Table Window

4.3.45 About Forcing DB Terminals

You can prepare force values for DB terminals like you prepare DB terminals for monitoring.
You can force DB terminals in on-line mode with the same commands as the ones you use for
forcing PC terminals.

4-72 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.46 About Setting DB Terminal Values

NOTES
Forcing DB terminals is supported only by extended DB elements that are
available, for example, for AC 110 version 2.1.

Forcing DB terminals is supported by the Function Chart Builder only from its
version 4.3/0 on.

You can prepare force values only for the VALUE terminals of extended DB elements and force
them using the Test Table, the buttons in its Force group, and corresponding commands of the
Edit and Test menus.
For convenient use you have to select All or DB Force in Signal Select Filter and configure the
Test Table window appropriately.
Resize the columns of the Test Table window by dragging the divisions that separate the header
parts, so that typically the columns Instance, Terminal, Force Value, Value on Target, Type,
Description, and State become visible.
In the Test Table, in the State column a ‘D’ indicates an entry for monitoring,
a ‘P’ an entry prepared for forcing, ‘F’ a forced entry, and an ‘R’ an entry prepared for removal
from the table.

CAUTION
Forced PC and DB terminals behave differently on the on-line connected
AC 100 Series target if you disconnect it from the engineering station:

• At PC terminals, the force values will be deactivated on the target after its
disconnection.
• At DB terminals, the force values will remain active on the target after its
disconnection.

4.3.46 About Setting DB Terminal Values

In this context setting means preparation of a value in the engineering station and setting it once
in the on-line connected controller. Setting is not the same function as forcing.
The Function Chart Builder offers the Test | Set DB Value command for setting. The set value
is effective on the controller until it is overwritten typically by the application program in a next
PC execution cycle, by setting another value, and so on.

NOTE
Before setting a DB value, deactivate all PC elements that can overwrite the set
value. For example, keep the ON terminals of the corresponding PCPGM,
CONTRM, or other structure element forced to 0 for a necessary period.

You can use this function for testing cables in the following way:
You set some characteristic values and test with an instrument that corresponding levels
are present on cable ends or (physical) terminal connections.
In our example, suppose our target is connected and the Function Chart Builder is in on-line
mode.

3BDS 100 595R401 4-73

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Set DO1.2/FLASH to 1 by choosing the Test | Set DB Value command and filling the Set DB
Value dialog box appropriately.
This value is effective until a 0 generated on the output of AND(3) overwrites it in a next
execution cycle as controlled by CONTRM.
To achieve setting of DO1.2/FLASH to 1 for a long or definite duration, you should force the
ON terminal of CONTRM to 0 before.

4.3.47 About On-line Configuration and Programming

Terms
An application for an AC 100 Series node is normally split into a DB section and a PC section
consisting of a single PC program. The PC program consists of executable units. An executable
unit contains a structure element (with cycle time) and subordinate PC elements.
In on-line mode, the Function Chart Builder supports editing in the PC section and DB section
of on-line connected AC 100 Series target executable unit by executable unit. The changes are
effective (almost) immediately in the target without explicit target code generation and
downloading of the whole application.
In the new on-line preparation mode introduced with FCB release 4.6/0, you can edit one
executable unit off-line. Then you connect the target again and go on-line. Now you download
only the difference to achieve a bumpless modification of the running application on the target.
For an overview of different states of the Function Chart Builder,
see Section 4.4.6.1, About On-line and Off-line Modes.

Conditions of On-line Editing

Conditions of editing an application program (as well as of monitoring and forcing terminals) in
the on-line connected target are the following:
• Exactly the same target code is downloaded to the target as the one selected in the
Function Chart Builder. The on-line preparation mode and on-line mode facilitate keeping
the accordance of the internal representation with the application in the target.
• The target is deblocked.
The Function Chart Builder offers most of the commands in the Edit, PC-Section, and
PC-Terminal menus also in on-line mode and in on-line preparation mode.

Restriction of Editing in On-line Mode and On-line Preparation Mode

In contrast to editing in off-line mode, restricted handling is possible when you make changes in
an application in on-line mode or in on-line preparation mode:
• Changes such as inserting, modifying, and deleting PC elements are allowed for only one
executable unit at a time.
• The first change fixes the executable unit.
• Deleting connections is always allowed in the fixed executable unit and between the fixed
executable unit and one other executable unit.
• Connections to constants and to DB elements are only allowed in the fixed executable unit.

4-74 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.48 On-line Editing of PC Program

• Adding connections between executable units is only allowed in the following way:
a. Fix the executable unit having the input terminal.
b. Connect the input terminal of the fixed executable unit to the output terminal of the
other executable unit.
• Some terminals of DB elements cannot be changed on-line.
• The PC and DB sections cannot be changed simultaneously.
All these restrictions hold in the case of substantial changes, that is, for those that are reflected
by the target code and are conveyed to target.
Changes of DB elements, PC elements and signals, item designations, page divisions, and
header and footer texts are generally unsubstantial. Though, in case of AC 100 Series nodes
supporting application retrieval or if you generate also information for HMI, you may have
completed the target code with some or all of these items. Then also their changes become
substantial.
If you have edited in on-line preparation mode, switch to on-line mode by the Target | Connect
command.
In on-line mode, use the File | Save and Load command to store the changes in the
AC 100 Series target. Thereafter, you can modify some other executable unit.

4.3.48 On-line Editing of PC Program

Suppose all conditions mentioned in Section 4.3.47, About On-line Configuration and
Programming are met for our example.
Select a pane of the PC Section window with function chart. You may have maximized the
PC Section window.
Be sure the target is connected and the Function Chart Builder is in on-line mode:
the word On-line is displayed in the Title Bar of the PC Section window.
Check PCPGM State in the Status Report. If the PC program is blocked (stopped), choose the
Target | Deblock Program command to deblock (start) it.
Modify a PC element and add a new connection as example for on-line editing.
Select input 1 of AND(3). Choose the PC-Terminal | Insert command to insert a fourth input.
So you have changed AND(3) to AND(4).
Connect the new input to the MODP output of CONTRM.

3BDS 100 595R401 4-75

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The modified PC program looks like this:

Figure 4-77. Modified PC Program

Choose the File | Save and Load command to make the changes effective in the target.
The Function Chart Builder generates target code for the modified executable unit.
You have to confirm the modification on the target:

Figure 4-78. Confirmation of On-line PC Modification

4-76 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.49 On-line Editing of Data Base

Activate the OK button by pressing ENTER.

The Function Chart Builder downloads the new target code to the target.
The protocol of these actions is shown in the Output window:

Figure 4-79. Output Window After Save and Load of PC Change

NOTE
Click with the right mouse button in the Output window to open a context menu.
Use the Save As context menu command to save the download protocol in a file.

You can now test the application program, save it, load it to PROM of the target, and so on.
Or you can modify another executable unit.

4.3.49 On-line Editing of Data Base

Suppose all conditions mentioned in Section 4.3.47, About On-line Configuration and
Programming are met for our example.
Select the DB Section window. Or, if necessary, choose the File | Open Section | DB command.
Be sure the target is connected and on-line mode is selected:
the word On-line is displayed in the Title Bar of the DB Section window.
Check PCPGM State in the Status Report. If the PC program is blocked (stopped), choose the
Target | Deblock Program command to deblock (start) it.
Modify a DB element and add a new connection as example for on-line editing.
Select the DO1.3 digital output channel.
Change its NAME property from DO1.3 to CONTRM_MODP, for example, by activating the
Edit button in the DB Section window, editing the terminal in the Edit DB Terminal Values
dialog box, then activating the OK button there.

3BDS 100 595R401 4-77

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder closes the Edit DB Terminal Values dialog box and displays the
DB Section window with modified contents as shown in the following figure:

Figure 4-80. Modified DB Section

Edit the DI1 DB element. Change its IMPL terminal from 1 to 0. Edit the DI1 again. Change its
IMPL terminal back to 1. This is to pretend a substantial change in the DB part.
Make an attempt to connect DO1.3:VALUE to the MODP output of CONTRM (PC1.1:6).
That means a violation of the rule “the modification can concern one executable unit”.
The Function Chart Builder displays the following warning:

Figure 4-81. Attempt to Change in a Second Execution Unit, Warning

Activate the OK button.

Follow the hint given in the message.
Choose the File | Save and Load command to make the DB changes effective in the target.

4-78 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.3.49 On-line Editing of Data Base

The Function Chart Builder prompts you to confirm this action:

Figure 4-82. Confirmation of On-line DB Modification

Activate the OK button by pressing ENTER.

The Function Chart Builder generates target code for the modified DB section and downloads it
to the target.
The Function Chart Builder opens the Output window and shows the protocol of these actions:

Figure 4-83. Output Window After Save and Load of DB Change

Now you can make a change in the PC section (in another executable unit).
Try the method “connect terminals in other windows than PC Section” (an alternative to the
way shown in Section 4.3.16, Connecting PC Terminals):
Open a pane of the PC Section window with function chart and select the MODP terminal of
CONTRM.

3BDS 100 595R401 4-79

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Open the DB Section window.

Select the DO1.3 channel in the Item Designation, Instance Name, … list box.
Drop down the DB Terminal list box and select the VALUE terminal.
Choose the PC-Terminal | Connect Selected command (or activate the Connect button in the
DB Section window).
The Function Chart Builder establishes the connection as shown in the following figure:

Figure 4-84. Connecting DB Terminal On-line

Make the connection effective in the target by the next File | Save and Load command. Proceed
as in Section 4.3.48, On-line Editing of PC Program.
Finally, choose the File | Exit command to finish your Function Chart Builder session.
If applicable, confirm the following message, press Y to activate the Yes button:

Figure 4-85. Confirmation of Disconnection

4-80 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4 Operating Instructions

Answer with Yes also the possible question

“Loaded application not saved in PROM. Disconnect target?”.
The Application Builder regains the focus. Choose its File | Exit menu command to finish your
Application Builder session.

4.4 Operating Instructions

In this section we give you step-by-step instructions how to solve typical tasks with the
Function Chart Builder. The procedures are given in their natural order, grouped as follows:
• Basic procedures
• Preparatory procedures
• Object-specific programming procedures
• Section-specific programming procedures
• Procedures concerning source code
• On-line programming procedures
• Diagnostic procedures
• Rules and conventions.

4.4.1 Basic Procedures

4.4.1.1 Handling Windows and Navigating
Resources
When you start the Function Chart Builder, it opens the Function Chart Builder window. It is
an application window with Title Bar, Menu Bar with pull-down menus containing the menu
commands, optional Toolbar, and optional Status Bar.
The Function Chart Builder opens the *.ODB window that lists the sections of the object you
are working on.
Use the controls of this window to create, open, or delete sections or a PC program.
The Function Chart Builder offers the following windows for the sections:
• PC Section window for each PC program, or—in case of type circuits and circuits—for
the PC section
• DB Section window for the DB section
• Symbol Section window for the symbol section
• TC/CI Terminal Section window for the TC/CI terminal section.
The PC Section windows are divided into one to three panes for the presentation of tree
diagram or function chart.
To work on a section, select its window by clicking on it with the mouse or by using the View
menu and Window menu commands.
Here you can open or activate some more windows:
• Output window for lists
• Name Table window for names and units

3BDS 100 595R401 4-81

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Test Table window for PC and DB terminals to be forced and monitored on-line in
AC 100 Series targets
• A second, third, and so on, PC Section window, DB Section window, and so on with the
Window | New command for comfortable work.
When you work with an on-line connected AC 100 Series target, use the commands Target |
Report … to open the following windows to get information about the target:
• Status Report window
• Options Report window
• Attribute Report dialog box.
When you work with an on-line connected AC 100 Series target, use the Target | Diagnostics
command to start the Diagnostics (Diagnosis) program and get more information about the
target.
The Diagnostics (Diagnosis) program offers own windows with the usual control elements to
facilitate the diagnosis of on-line connected AC 100 Series targets:
• Error Report window
• Module List window
• Module Diagnostics (Module Diagnosis) window.
In case of AC 110 2.0, AC 70 1.0, and AC 55 1.0 also the following windows are offered:
• Channel Diagnosis window
• Status Report window, similar to Status Report window of the Function Chart Builder.
See Section 4.5.22, Controls of Diagnosis, Section 4.5.23, Controls in Document Windows of
Diagnosis and Section 4.5.24, Menu Commands of Diagnosis.

Usage
Use the controls (integrated in Title Bar) to move, size, iconize, restore, and close the windows.
See Section 4.5.2, Controls in Document Windows.
Use the menus of the Menu Bar to choose commands concerning the active document window.
See Section 4.5.3, On Menu Commands, General.
Select the Toolbar icons as shortcuts to the most frequently used menu commands.
See Section 4.5.1, Controls in Title Bar, Toolbar and Status Bar.
Use the Status Bar to check keyboard state and connection state.
See Section 4.5.1, Controls in Title Bar, Toolbar and Status Bar.

4.4.1.2 How to Use the Mouse

Purpose
The mouse is a convenient tool you can use to control the cursor's position and to point to and
select graphical objects. Use the mouse shortcuts to work more efficiently.

General Mouse Shortcuts

You can use the mouse in the way you generally do in Windows applications.
To select menus and activate windows, commands, buttons, and so on, click on them with the
left mouse button.

4-82 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.1 Basic Procedures

Double-clicking in a list box activates also the default button, that is the button, which is
highlighted by a thicker outline.
When you are editing in a PC Section window, the Output window, or text boxes, you can open
the context menu, that is, a menu with the most useful commands in the given context, by
clicking with the right mouse button.
When you are editing in text boxes or in the Output window, to select a part of a text, proceed
as follows:
• Either click on one end of the text part, keep the left mouse button pressed, and move the
cursor with the mouse to the other end, then release the mouse button.
• Or click on one end of the text part, then press the SHIFT key and hold it down while
clicking on the other end.
You can change the presented content or the dimensions of windows, list boxes, panes, columns,
and so on, by dragging and dropping their frames, corners, scroll boxes, split bars, and
divisions.
To drag and drop a graphical element means the following:
Point to the graphical element with the cursor by moving the mouse. In this case the cursor
changes its form. Press the left mouse button and hold it down. That means you have
“seized” the element and you can drag it by moving the mouse. When you have positioned
or resized the element as required, “drop” it there by releasing the left mouse button.

Special Mouse Shortcuts

Mouse shortcuts for use in PC Section windows, in panes with function chart
• To select a PC element, click on it.
• To extend the (multiple) selection to some other PC elements, press the SHIFT key and hold
it down while clicking on that PC element.
• To extend the (multiple) selection to the end of a PC element subtree on lower level, press
the SHIFT key and hold it down while double-clicking on a subtree element.
• To select and mark a PC terminal, click on it.
• To connect two PC terminals
– If you selected the “classical” quick connect mode (as known before Function Chart
Builder 4.7) by the Options | Preferences command and selecting the Quick
Connect by Right Mouse Button check box:
Click on one terminal to select and mark it, and click on the other terminal with the
right mouse button.
– If you unselected the “classical” quick connect mode by the Options | Preferences
command and unselecting the Quick Connect by Right Mouse Button check box:
Click on one terminal to select and mark it, and double-click on the other terminal
with the right mouse button. (The context menu opens at the first click and you
choose the Connect to Marked menu item, which is in that case always directly
under the cursor, with the second click.)

3BDS 100 595R401 4-83

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Different functions are assigned to double-click with the left mouse button:

Table 4-4. Default Commands in Function Chart Pane of PC Section Window on Double-click

Double-click Location Default Command Dialog That Will Open

PC element Edit | Call Parameters Edit Call Parameters
TC/CI instance Edit | Symbol Values Edit Symbol Values
Terminal PC-Terminal | Connect… Connect
Footer Edit | Document Texts Edit Document Texts
Page frame File | Page Setup Page Setup
Other none none

Mouse shortcuts for use in PC Section windows, in panes with tree diagram
• To select a PC element, click on it.
• To extend the (multiple) selection to some other PC elements, press the SHIFT key and hold
it down while clicking on that PC element.
• To extend the (multiple) selection to the end of a PC element subtree on lower level, press
the SHIFT key and hold it down while double-clicking on a subtree element.
• Different functions are assigned to double-click with the left mouse button:

Table 4-5. Default Commands in Tree Pane of PC Section Window on Double-click

Double-click Location Default Command Dialog That Will Open

PC element Edit | Call Parameters Edit Call Parameters
in PC Element column
TC/CI instance Edit | Symbol Values Edit Symbol Values
in PC Element column
Element with page break PC-Section | Page Layout Modify Page Division
in Headline or Page column | Modify Page Division
Element without page break PC-Section | Page Layout Insert Page Division
in Headline or Page column | Insert Page Division
Other Command and dialog correspond to the nearest
element (PC element or TC/CI instance) and to the
column

Mouse shortcuts for use in DB Section windows

• To edit (modify) terminal values of a DB element, double-click on the appropriate item in
the Item Designation, Instance Name,… list box.
The Function Chart Builder shows the Edit DB Terminal Values dialog box.
• To connect a DB terminal to the PC terminal, which is selected in the PC Section window,
click on the appropriate item in the Item Designation, Instance Name,… list box or the
DB Terminal drop-down list box with the right mouse button.

4-84 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.1 Basic Procedures

(If you want to connect other DB terminal than VALUE, select the DB element in the Item
Designation, Instance Name,… list box and the DB terminal in the DB Terminal drop-
down list box previously.)
• To switch from a referencing DB element, such as DSP, MVB, or MVI, to a referenced DB
element, such as a DAT or MVC, click with the right mouse button on the corresponding
REFn or CHANNELn terminal in the Edit DB Terminal Values dialog box.
Mouse shortcuts for use in Symbol Section windows
• To edit (modify) a symbol, double-click on the symbol.
The Function Chart Builder shows the Edit Symbol dialog box.
• To connect a symbol to the PC terminal, which is selected in the PC Section window, click
on the symbol in the Name, Kind,… list box with the right mouse button.
Mouse shortcuts for use in TC/CI Terminal Section windows
• To select a TC/CI terminal for modification, double-click on the terminal name.
The Function Chart Builder shows the Edit TC/CI Terminal dialog box.
• To connect a TC/CI terminal to the PC terminal, which is selected in the PC Section
window, click on the TC/CI terminal in the Name, No.,… list box with the right mouse
button.
Mouse shortcuts for use in Name Table windows
• To select a name for modification, double-click on the name.
The Function Chart Builder shows the Create/Edit Name dialog box.
• To connect the PC terminal, which is selected in the PC Section window, by a name
standing for a PC terminal, click on the name in the Kind, Name,… list box with the right
mouse button.
Mouse shortcuts for use in Test Table windows
• To select several lines of a contiguous part of the Instance, Terminal,… list box, click on
the first line to be selected, then press and hold down SHIFT while click on the last line to be
selected.
• To add (or clear) a single line to (or from) a selected contiguous part of the Instance,
Terminal,… list box, press and hold down CTRL while click on the line.
You can choose the Edit | Delete command to act on the selected lines all at once.
• To resize the columns, drag the divisions that separate the header parts Instance,
Terminal, and so on, to the required position.
• To change the order of the columns, drag the header parts Instance, Terminal, and so on,
to the required position.
• To set or invert the sort order, click on the header part Instance, Terminal, and so on,
according to which you want to sort the entries shown in the list box.
Mouse shortcut for use in the Output window
• To select a corresponding listfile, double-click on a line with a warning or error message.
• To open a context menu with the Goto, Find, Copy, Select All, Save As, and Print
commands, click with the right mouse button.
Mouse shortcut for use in the Module Diagnostics window of the Diagnostics program
To open a dialog box with additional information about an error in the on-line connected
target, double-click on a line with error state, error message, and so on, in the list box.

3BDS 100 595R401 4-85

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Mouse Usage in On-line Mode

To ensure high system reliability for the engineering station and high security for your
AC 100 Series target system, as default no mouse shortcuts are available in dialog boxes for
actions directly changing the state of the target system during on-line editing and testing.
If you use a PC of yours as engineering station, and if you want to work on-line connected to
target systems, your PC, add-on boards, and its peripherals must fulfill high mechanical,
temperature, and electrical requirements, for example, concerning electromagnetic
compatibility (EMC), as stated in the Application Builder User’s Guide.
Advant Station 100 Series Engineering Stations and their peripherals fulfill these requirements.
If you have a mouse or trackball fulfilling these requirements and you want to use mouse
shortcuts during on-line editing and testing, you have to allow it explicitly by the Options |
Preferences command.
DANGER
Allow mouse shortcuts for actions directly changing the state of the on-line
connected target system only if you use a mouse or trackball fulfilling the
requirements stated in the Application Builder User’s Guide.
Else you risk malfunction of the target system.

Scrolling (Sliding) with the Mouse

Alternatives:
1. Check slide mode in the Status Bar. If slide mode is cleared, set it by the Window | Slide
command. Hold down the left mouse button and move the mouse.
2. Press the ALT key. Hold down the left mouse button and move the mouse.
(It is not necessary to keep ALT pressed while moving the mouse.)
3. If you have a mouse with 3 buttons, hold down the middle button and move the mouse.

4.4.1.3 Using the Keyboard Instead of the Mouse

General Windows Key Sequences
Use the general key and key sequence functions as offered by Windows NT.
Examples:
• Press ALT+F4 to close an application window.
• Press CTRL+ESC to display the Start menu of Windows NT.
• Press and hold down ALT while pressing TAB (or SHIFT+TAB) repeatedly to cycle through
running applications.
• Press ALT+ESC (or SHIFT+ESC) to switch to the next (or previous) running application.
• Press CTRL+F4 to close a document window.
• Press CTRL+F6 (or SHIFT+CTRL+F6) to switch to the next (or previous) document window.
• Press F6 (or SHIFT+F6) to switch to the next (or previous) pane of a document window.
• Press TAB (or SHIFT+TAB) to step forward (or backward) from field to field in dialog boxes.
• Press ENTER to activate the default button (the button, which is highlighted by a thicker
outline) in dialog boxes.

4-86 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.1 Basic Procedures

• Press SPACE to activate the selected button (the button, which is highlighted by a dashed
frame around its label) in dialog boxes.
• Press ESC to activate the Cancel button in dialog boxes.
• Press UP, DOWN, PGUP, PGDOWN, HOME, END, LEFT, RIGHT to move the selection within menus,
groups, list boxes, and so on.
• Press and hold down SHIFT while pressing UP, DOWN, PGUP, PGDOWN, HOME, END to extend the
(multiple) selection to a part of a text in text boxes or to several items within list boxes.
• Press DOWN to open a drop-down list box.
• Press SPACE to select or unselect a check box.
• Press CTRL+C to copy a selected text part to the Clipboard of Windows NT.
• Press CTRL+V to paste text from the Clipboard of Windows NT to the cursor position or to
overwrite selected text part.
• Press CTRL+X to cut a selected text part and move it to the Clipboard of Windows NT.
• Press CTRL+Y to redo the last undone action.
• Press CTRL+Z to undo the last action.
• Press DEL to delete selected text part in text boxes or selected item(s) in list boxes or
selected PC elements.
• Press the context menu key (available only on WIN95 keyboards) to open the context
menu.

Special Function Chart Builder Key Sequences

1. Some keys and key sequences have special meaning in PC Section windows:
– Press and hold down SHIFT while pressing UP, DOWN, PGUP, PGDOWN, HOME, END to
extend the (multiple) selection to several PC elements.
– Press and hold down SHIFT and CTRL while pressing LEFT or RIGHT to extend the
(multiple) selection to the PC element on higher level or to the end of PC element
subtree on lower level.
– Press CTRL+C to copy selected PC elements to the paste buffer.
– Press CTRL+V to paste the contents of the paste buffer to the PC section.
– Press CTRL+X to cut selected PC elements and move them to the paste buffer.
– Press DEL to delete selected PC elements.
2. Use the accelerator keys of menu commands of the Function Chart Builder.
The accelerator key letters are underlined in the menu names and command names.
Examples:
– Press ALT+F, X to choose the File | Exit command.
– Press ALT+P, G, P to choose the PC-Section | Goto Element | Previous command.
3. Use the key shortcuts of certain menu commands of the Function Chart Builder.
Examples:
– Press CTRL+P to choose the File | Print command.
– Press UP to choose the PC-Section | Goto Element | Previous command.

3BDS 100 595R401 4-87

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4. Use the accelerator keys to select fields or activate buttons in the dialog boxes of the
Function Chart Builder. The accelerator key letters are underlined.
Examples:
– Press C to select the Callname… field in the Create Element dialog box.
– Press H to activate the Help button in several dialog boxes.
5. Other special shortcuts:
Press ALT+S to jump to graphic symbol selection in the Edit DB Terminal Values
dialog (or to the first terminal if the current DB element has only one graphic
symbol).

Using the Keyboard During On-line Editing, Testing, and Diagnostics

To ensure high system reliability for the engineering station and high security for your
AC 100 Series target systems, as default no mouse shortcuts are available in dialog boxes to
change directly the state of the target system during on-line editing and testing.
For example, you can prepare target code for download with mouse shortcuts, but you can
trigger the download process only by keys unless you explicitly allow it. See Section 4.4.1.2,
How to Use the Mouse, Mouse Usage in On-line Mode.

Scrolling (Sliding)
1. Check slide mode in the Status Bar.
2. If slide mode is cleared, set it by the Window | Slide command.
3. Use the following keys for sliding:
Table 4-6. Use of Keys for Sliding

Key(s) Alternative Slide Function

HOME Scroll to far left of current line.
CTRL+HOME Scroll to upper left corner.
END Scroll to far right of current line.
CTRL+END Scroll to bottom right corner.
UP Same as clicking the vertical scroll arrow Up.
CTRL+UP PAGE UP Same as clicking above the scroll box in the vert. scroll bar.
DOWN Same as clicking the vertical scroll arrow Down.
CTRL+DOWN PAGE DOWN Same as clicking below the scroll box in the vert. scroll bar.
LEFT Same as clicking the horizontal scroll arrow Left.
CTRL+LEFT Same as clicking left to the scroll box in the hor. scroll bar.
RIGHT Same as clicking the horizontal scroll arrow Right.
CTRL+RIGHT Same as clicking right to the scroll box in the hor. scroll bar.

Alternative Method to Scroll (Slide)

Keep the ALT key pressed and use the keys in the table above.

4-88 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.2 Preparatory Procedures

4.4.2 Preparatory Procedures

4.4.2.1 Node or Node Structure?

Definition
Node and node structure are two aspects of the same program concerning a physical node.
The Function Chart Builder processes a selected node as node or as node structure depending on
the menu command, by which it is started from the Application Builder:
• Tools | Function Chart Builder
• Tools | Node Structure Function Chart Builder.
The node has all references resolved, the referenced parts are expanded, and it is fully checked.
A node consists of process control elements (PC elements) and data base elements
(DB elements), and of circuits and type circuits resolved at instantiation.
A node structure consists of located circuits, symbol value assignments, and also of glue logic,
such as instructions creating or modifying DB elements and PC elements, even instantiated type
circuits. It emphasizes the structure of the node. It references the located circuits and
instantiated type circuits rather than containing them resolved.

NOTE
Expert users may allow virtual connections also in nodes,
see Options | Preferences command.

Methods
The Function Chart Builder supports two methods:
• Function oriented project engineering method based on node structures and circuits
(see also Section 3.1, Design Considerations - General Working Method)
• Straightforward method (you program nodes directly, possibly instantiate also type circuits
in them, and in rare cases, locate circuits in them).

Phases of Working with the Function-oriented Project Engineering Method

1. Preparing type circuits, see Section 4.4.3.2, Prepare a Type Circuit
2. Editing and completing circuits,
see Section 4.4.3.7, Edit a Circuit and Section 4.4.3.4, Instantiate a Type Circuit
3. Locating circuits in the node structure, see Section 4.4.3.8, Locate a Circuit
4. Completing the node structure, see Section 4.4.3.9, Edit a Node Structure
5. Transition from node structure aspect to node, see Section 4.4.3.10, Expand Node Data

Phases of Working with the Straightforward Method

1. Preparing type circuits, see Section 4.4.3.2, Prepare a Type Circuit
2. Editing and completing the node, see Section 4.4.3.1, Edit a Node and Section 4.4.3.4,
Instantiate a Type Circuit, possibly also Section 4.4.3.8, Locate a Circuit.

3BDS 100 595R401 4-89

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.4.2.2 Considering Use of Circuits

Definition
Circuits are medium-level building blocks containing major, but variable, application program
parts prepared for a single use within a project. A circuit consists of symbol declarations,
PC elements, type circuit references, and instructions creating or modifying DB elements.
You can locate (insert) a circuit only once in a node structure, and since Function Chart Builder
release 4.7—though not recommended—, also in a node. By assigning values to symbols
(parameters) at insertion, you anchor the circuit in the node structure (and node) in a given way.
The purpose of circuits is to support the following:
• Projecting large applications part by part (for example, to project major control parts and
signal parts separately)
• Function-oriented projecting methods (specification of solutions independently from
actual nodes and physical layout of process automation equipment)
• Interfacing between projecting teams.
See also Section 3.1, Design Considerations - General Working Method.

Phases of Working with Circuits

1. Preparing (creating or editing) circuits, see Section 4.4.3.6, Prepare a Circuit
2. Locating (using) circuits, see Section 4.4.3.8, Locate a Circuit.

4.4.2.3 Considering Use of Type Circuits

Definition
Type circuits are low-level variable building blocks containing typical application program parts
prepared for repeated use within or throughout projects. A type circuit consists of symbol
declarations, PC elements, and instructions creating or modifying DB elements.
You can instantiate (insert) a type circuit several times in nodes, node structures, and circuits.
By assigning different values to symbols (parameters) at instantiation, you vary the function of
each type circuit instance.
Using type circuits is a classic way of structuring application programs.

NOTE
Editing of type circuits having variants and loops is not supported by the Function
Chart Builder. Nevertheless, variants and loops are allowed in type circuit source
code, and you can instantiate such type circuits by the Function Chart Builder.

See also Section 3.1, Design Considerations - General Working Method.

Phases of Working with Type Circuits

1. Preparing type circuits (creating or editing), see Section 4.4.3.2, Prepare a Type Circuit
2. Instantiating (using) type circuits, see Section 4.4.3.4, Instantiate a Type Circuit

4-90 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.2 Preparatory Procedures

4.4.2.4 Create an Object

Prerequisites
Use the Application Builder for these application procedures. For more information on the
Application Builder see Application Builder User’s Guide.
The object will have a certain node type and options. Be sure the pertaining PC and DB element
libraries are installed. AMPL PC and DB Element Libraries contain standard node types for
AC 100 Series and AC 400 Series. Other node types, like AC 166 and AC 80, and additional PC
and DB element libraries created by customers are also available bundled to libraries or options.
For installation see AMPL PC and DB Element Libraries Release Notes.

Create or Open a Project

Create a new project by the File | New | Project menu command or open an existing project by
the File | Open | Project menu command. The project is identified by its name.
Set defaults for the project by the Options | Project Defaults menu command if necessary:
• Node type
• Selected options
• Tool versions
• Document texts
• Page layout.

Open Object List

Choose the File | Open | Node List, File | Open | Circuit List, File | Open | Type Circuit List
menu commands to list the existing objects of the opened project and their characteristics:
• Object name
• Node type options
and for nodes also:
• Net and node address
• RCOM net and node address
• Bus and station address, position.
NOTE
Selecting node type and options means selecting a set of precompiled PC and DB
element libraries or selecting support of special target system features.

Create a New Object

Create the new node by the File | New | Node menu command.
Create the new circuit by the File | New | Circuit menu command.
Create the new type circuit by the File | New | Type Circuit menu command.
NOTE
Even if you want to program a new node structure in the Function Chart Builder,
you have to create a new node for it in the Application Builder.
Node structure is just another aspect of node.

3BDS 100 595R401 4-91

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Retrieve a Node
The retrieval of an application from an AC 100 Series target by the File | Retrieve Application
command creates implicitly the corresponding node. No explicit object creation is necessary.
See Section 4.4.6.15, Retrieve Application from an AC 100 Series Target.

4.4.2.5 Start-up of Function Chart Builder

Preparation
Before starting the Function Chart Builder you generally start the Application Builder to select a
project and an object to work on.
See Application Builder User’s Guide for detailed description of Application Builder menus and
commands.
If you follow the function-oriented project engineering method described in Section 3.1, Design
Considerations - General Working Method, you generally select a node structure, a circuit, or a
type circuit.
You can also select a node in a straightforward way.

Ways of Starting the Function Chart Builder

• Start from within the Application Builder by choosing the Tools | Function Chart
Builder or Tools | Node Structure Function Chart Builder menu command, or by
clicking on the corresponding toolbar icon.
The Function Chart Builder works on the project and the object, which has been selected
in Application Builder.
• In this way, you can start the Function Chart Builder several times on different objects.
That is, several instances of Function Chart Builder may exist simultaneously, each
working on a different *.ODB file.
• Start by choosing it in the Advant | Engineering start menu.
If the Function Chart Builder is already running, the Function Chart Builder application
window gets the focus.
If not, the Function Chart Builder is started on the project and object it recently worked on.
If no information is available on recent project and object, for example, when starting first
time after installation, Function Chart Builder warns you with the following message:

Figure 4-86. Warning, Initialization Data Missing

4-92 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.2 Preparatory Procedures

Phases of Start-up
1. At first, if the object is protected, you have to enter the password pertaining to the object.
See Section 4.4.2.6, Password Protection of Nodes, TCs, CIs for more information.
Furthermore, if another user has already started the Function Chart Builder on an object—
that means, he has opened the *.ODB file of the object—and you try to start Function
Chart Builder on the same object, you will be prompted to open a read-only copy and work
on it instead. Then you can view and print the object but you cannot change it.
2. The Function Chart Builder looks for type descriptions and element libraries referenced
and used by the object and checks whether they are consistent.
In due case, the Function Chart Builder warns you, displays the differences in the Output
window, prompts you to initialize, or even refuses starting up on the object and allows only
to choose the Help | …, File | Rebuild Element Types, and File | Exit commands.
See Section 4.4.2.7, Element Library Handling for more information.
3. The Function Chart Builder looks for a DBGENDEF.BAX file in the node directory, or in
..\PR_TC\TCDATA, or in ..\PR_CI\CIDATA depending on the current object.
This file, if it exists at all, contains DB system defaults (general defaults).
The Function Chart Builder checks it and lists the results in the Output window.
If DBGENDEF.BAX is correct, the Function Chart Builder applies the general defaults
taken from in DBGENDEF.BAX at source code generation, instead of the ones defined in
the current element library.
4. The Function Chart Builder opens the application window having the title “Function Chart
Builder - …” with the name of the selected object, a Menu Bar, a child window, and
optionally the Toolbar and the Status Bar:

Figure 4-87. FCB Started for a Node

3BDS 100 595R401 4-93

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

5. If you start the Function Chart Builder for the first time on a new object of a project and no
project default page layout is defined in the Application Builder, define the page layout for
your diagrams in the following dialog box:

Figure 4-88. Initial Page Setup Dialog Box

See Section 4.4.2.10, Specifying Document Layout for more information.

4.4.2.6 Password Protection of Nodes, TCs, CIs

In this chapter all functions described for nodes also apply to Type Circuits and Circuits.
Function Chart Builder offers protection of manipulations by unauthorized persons. Every node
may have a different password.
For every node the degree of protection is selectable on three levels:
1. Lock the access to the complete Function Chart Builder.
2. Lock functions changing the node. The Function Chart Builder works in “View Mode”.
3. Lock all functions but Target Control functions. The Function Chart Builder works in
“Loader Mode”.
In fact, the access to the node is protected by the password. This works by protecting the *.ODB
file containing the internal data representation of the node you are working on by the ODB
password.

4-94 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.2 Preparatory Procedures

Workflow
1. After creation of a new node, type circuit, or circuit, the initial password is empty and the
node is not protected.
2. You can define an ODB password by File | Set Password command.

Figure 4-89. Set Initial ODB Password

Enter here the password in the New Password and Confirm New Password text boxes.
The password has to consist of 8 to 50 printable characters, it is case sensitive.
a. In case you select “User Needs to Enter Password on FCB Startup...” no access to
this node is allowed without entering the correct password. The protection takes
effect at the next start of FCB.
Each time you start the Function Chart Builder on this node, you are prompted to
enter the correct password.

Figure 4-90. ODB Password Query at FCB Start-up

3BDS 100 595R401 4-95

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

If you enter the correct password, the Function Chart Builder starts fully up, opens
the *.ODB window, and offers its commands. You can work on the object.

If you enter an incorrect password, the Function Chart Builder cancels the dialog and
exits automatically. You can neither see the application program (PC and DB
elements, symbols, terminals), nor change it, just try to enter the correct password
again.
b. In case you select “User can view Node,...” the protection takes effect after leaving
the File > Set Password dialog.
All menu items and buttons modifying ODB are disabled. The ODB is on Read only
mode. It's possible to connect to target and perform target control functions. In status
bar “View Only” mode is indicated.
c. In case you select “User can use Target Control Functions ONLY ...” the protection
takes effect after leaving the File > Set Password dialog.
All menu items but FCB | Exit and Target Control functions are disabled. PC/DB
Section window and ODB window cannot be opened. In status bar “Target Control
Only” mode is indicated.

CAUTION
Use password protection only if it is reasonable.

Be aware that there is no “back door” or “universal password” if you forget the
password. File | Initialize does not clear the password.

On the other side, files other than *.ODB, for example source code files, are not
protected.

4-96 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.2 Preparatory Procedures

3. You can change or clear the ODB password by the File | Set Password command. In these
cases you have to enter at first the old password. You can change the password by enter a
new password and / or you can change the access rights e.g. “User Needs to Enter new
Password ...” to “User can View Node ...”.:

Figure 4-91. Change ODB Password

3BDS 100 595R401 4-97

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4. You clear the password by input of an empty string as new password:

Figure 4-92. Clear ODB Password

The access rights are reset to the Function Chart Builder default behavior after the
password is cleared.
NOTE
Do not mix up the ODB password with the target password.
See Section 4.4.6.7, Target Access Protection.

4.4.2.7 Element Library Handling

General
DB and PC element libraries reflect the functions of the corresponding node type.
The node type description contains which libraries pertain to the base software and to each
option. Node type description and library files are identified by name and protected by
checksum (CRC).

Element Libraries Installed as Product

At installation, the sources of the supported node type descriptions and the libraries are stored as
compressed *.TE_, *.DE_, *.PE_, and so on, files in the \SRC_LIB subdirectory of the release
directory drive:\AdvaBNT\FCB\release_*\BIN32. They are than compiled to binary *.TEL,
*.DEL, *.PEL, and so on, files and stored in the release directory and its subdirectories

4-98 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.2 Preparatory Procedures

\DB_LIB and \PC_LIB. Additional element libraries are referenced, compiled, and stored in a
similar way. See also Appendix A, Function Chart Builder Files.
From time to time, node type descriptions and libraries are modified and released, normally
together with Function Chart Builder releases and new releases of Advant Controllers.
Different library releases are not fully compatible with each other, nor with other
Function Chart Builder releases.

Node-specific Element Libraries

Certain nodes may need element libraries that are different from those installed as product with
your current Function Chart Builder. Typical cases of need for node-specific element libraries:
• You program both standard Advant Controllers and their special modified versions.
• You retrieve an application from an Advant Controller 100 Series target together with the
libraries. The latter are an earlier release that is not installed on your engineering station.
See also Section 4.4.6.15, Retrieve Application from an AC 100 Series Target.
If there are node-specific element library files in the \LIBDATA\release_*\BIN32\DB_LIB and
\PC_LIB subdirectories of the node directory project_root\project*\NODES\node*,
the Function Chart Builder takes them instead of the standard libraries stored in the
corresponding subdirectories of the release directory.

Element Library Check At Function Chart Builder Start-up

1. The Function Chart Builder looks for node-specific node type descriptions and element
libraries. If the node type descriptions and element libraries are available and consistent,
go to Step 3.
2. The Function Chart Builder looks for type descriptions and element libraries installed as
product. If the node type descriptions and element libraries are not consistent, the Function
Chart Builder exits.
3. The Function Chart Builder checks the type circuits and circuits available for the current
node. In case the internal and external name of a type circuits and circuits differs the object
is renamed. This is listed in output window. In case double names exists an error file is
written.
Example of circuit check:

Figure 4-93. Example of Circuit Check

3BDS 100 595R401 4-99

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4. The Function Chart Builder compares the found type descriptions and element libraries
with the ones referenced and used by the current object. The latter information is stored in
the internal data representation (*.ODB file) of the object.
In due case, the Function Chart Builder warns you, displays the differences in the Output
window.
Example of library differences:

Figure 4-94. Example of Library Differences

Depending on the differences, the Function Chart Builder behaves differently:

Case 1 You have added new options in APB or added new types to any of the selected libraries,
for example, by PROFIBUS Library Editor:
FCB starts up and just displays hints about the differences in the Output window. You can
go on working with the current ODB. On-line capability is also preserved provided the
new options are available on the controller. The full FCB command set is available.
Case 2 You have modified or deleted some types in any of the selected libraries, for example,
PROFIBUS DB element types, or deleted some options in APB, but there are no instances of
them in the ODB:
FCB starts up and just displays hints about the differences in the Output window.
You can go on working with the current ODB. On-line capability is also preserved.
The full FCB command set is available.
Case 3 You have modified or deleted some types in any of the selected libraries, for example,
PROFIBUS DB element types, or deleted some options in APB, and at least one of the types is
instantiated in the ODB:
FCB starts up and displays the differences in the Output window. You cannot work with
the current ODB without restitution of libraries. Neither the on-line capability is preserved.
FCB prompts you to initialize. Only the commands File | Initialize, File | Rebuild
Element Types, File | Exit, and Help | … are available.
If this situation is intentional:
You can initialize, backtranslate the adapted source code of the object, and go on working
with less or modified types.
If this situation is unintentional:
You can exit without initializing. Then you can re-select the deleted option in APB, restore

4-100 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.2 Preparatory Procedures

the modified or deleted type, respectively, and restart FCB.

Alternatively, you can refuse the initialization and—without exiting FCB—re-select the
deleted option in APB and restore the modified or deleted type, respectively, then choose
the File | Rebuild Element Types command in FCB to take the restored circumstances
into account, and go on working in FCB.

4.4.2.8 Initialize an Object

The Function Chart Builder needs a valid internal data representation to work on. You can
initialize the internal data representation for the selected object (node, node structure, circuit,
type circuit) by the File | Initialize command.
Initialization means that the Function Chart Builder deletes the existing *.ODB file containing
the internal data representation of the current object and creates a new, empty file. You lose all
information you entered previously for that object. Source code files and print files of the object
are not affected.
Initialization is automatic if you start the Function Chart Builder with a new object.
For a new node or a new node structure, the Function Chart Builder creates system DB elements
corresponding to the node type and selected options. This operation takes about 10 seconds.
No system DB elements exist generally for Advant Controller 100 Series objects.

4.4.2.9 Support of Display Adapters and Printers

The Function Chart Builder runs under Windows NT, and uses the peripherals of the PC via
their drivers, which are installed and selected in the operating system.
For changing display resolution, colors, refresh rate, and selection of small or large font see the
Windows NT setup program or the specific setup program of the selected display driver.
For connecting printers and setting printer option defaults, see the Settings | Printers command
in the Start menu of Windows NT.
For selecting a printer before printing a diagram use the File | Print Setup command.
By this command you select, for example, the following:
• One of the available printer
• Size of the paper
• Orientation of the paper.
The selection has to fit the page layout. See Section 4.4.2.10, Specifying Document Layout.
For selecting a printer before printing an error report or diagnostic data, use the File | Print
Setup command of the Diagnostics program.

4.4.2.10 Specifying Document Layout

Documents
The documents, such as diagrams, data base listings, consist of pages.

3BDS 100 595R401 4-101

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Pages
The pages have a text area (or desk area), a frame, a footer, and—in case of function charts—
a headline immediately above the footer.
For the function chart you can change the page divisions and specify the pagination.
You generally do this after editing the function chart.
To specify page divisions and page numbering proceed as follows:
1. Select one of the PC Section windows.
You get more overview if you select a PC Section window pane with tree diagram.
2. Use the PC-Section | Page Layout | … commands.
3. In case of layout problems you may have to redefine the layout.

Layout
You generally specify the layout of your documents at the start of a new project.
To specify the default layout for all the documents of a project, use the File | Page Setup
command of the Application Builder.
For more and detailed information on the Application Builder see Application Builder User’s
Guide.
To specify the layout for the documents of an object, use the File | Page Setup command of the
Function Chart Builder.
You can do the following:
• Select one of the templates delivered with the Advant Engineering products.
Expert users may want to add new templates, see Section 4.4.2.11, Creation of Own
Templates.
• Set the number of rows and columns to be printed in the text area of a page.
• Use the defaults as set for the project within the Application Builder.
Your selection has to harmonize with the size and orientation of the selected paper.
See Section 4.4.2.9, Support of Display Adapters and Printers.

Number of Rows and Columns

The number of rows and columns are common for both displayed and printed pages of the
diagrams and are important for division of diagrams to pages.
Keep in mind the size and orientation of the paper you intend to use. If you select the default
numbers of rows and columns, the size and the proportions of the printed letters will allow easy
reading of your diagrams and listings. In other cases the letters will be automatically scaled to
fit the text area within the frame.
The function chart needs rather large area, especially for large PC elements, like NOVATUNE,
and for routing numerous and ramified connections. Keep number of rows and columns high.

4-102 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.2 Preparatory Procedures

Footer
If you are working on a node, you can define the texts in the footer differently for the documents
of each PC program and of the DB section.
If you are working on a node structure, circuit, or type circuit, you define the texts in the footer
only once, and they are valid for all the documents.
To specify the contents of the footer, select the corresponding section window and use the
Edit | Document Texts command.
The footers of the selectable templates correspond to international standards.

Headline
A function chart page may contain a headline immediately above the footer. You may specify a
different headline for each function chart page.
To specify the headline, select the PC Section window and use the
PC-Section | Page Layout | Insert Page Division, PC-Section | Page Layout | Modify Page
Division, and PC-Section | Page Layout | Copy Headlines commands.

4.4.2.11 Creation of Own Templates

General
The templates define the outlines, sizes, and fields of documents.
In case of Advant Engineering products Application Builder, Function Chart Builder, and
On-line Builder, the file foot001.TPX file contains the standard template set.

Storage and Processing of Template Files

At the installation of the Application Builder, Function Chart Builder, and On-line Builder, the
template file or files containing the newest template set or sets are stored together with the
standard ABB logo file abblogo.WMF in the reference directory C:\Advabldenv (unless you
redefined it at the installation or later by the environment variable ADVABLDENV).
User-defined and/or project-specific template files *.TPX and pertaining logo files *.WMF (or
*.BMP) have to be stored also in the reference directory.
At the creation of a new project, the Application Builder offers the contents of the available
—standard and user-defined—template files in the Page Layout Template Sets drop-down list
box of New Project dialog box. The Application Builder copies the template file of the selected
set in project directory project_root\project* of the new project * and renames it there to
foot001.TPX.
NOTE
In each project directory there is a foot001.TPX file. These files have the same
name but their contents may be different.

When you work on an object of a project, the Application Builder, Function Chart Builder, and
On-line Builder offer the templates of the template set selected for this project.

3BDS 100 595R401 4-103

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

See also Appendix A, Function Chart Builder Files.

About the *.TPX Files

*.TPX is an editable ANSI file, with a structure resembling the *.INI files. Additionally, it is
divided in templates. A template starts with the keyword BEGIN followed by the unique
template name. The end of a template description is marked by the keyword END.
A footer template file can contain any number of templates.
Comments are allowed: If a semicolon ‘;’ is found in the first column of a line, the line is
ignored.
Most cardinal values are given in so called lometric units. 1 lometric unit is 0.1 mm, or 1 mm is
10 lometric units. The origin of the lometric coordinate system is the top left corner, with rising
x-values to the right and rising y-values downwards.
“001” in the filename is used as syntax version identifier.

How to Modify or Create an Own Template?

1. Make a copy the original C:\Advabldenv\foot001.tpx and rename it, for example, to
C:\Advabldenv\mytp001.tpx.
2. If you need an own logo, store it preferably as Windows Metafile (*.WMF), else as Bitmap
file (*.BMP) in the reference directory.
3. Modify the mytp001.tpx file as necessary, using AS100-EDIT or a simple text editor like
Notepad:
Follow the syntax of *.TPX Files. See Appendix F, Syntax of Template Files.
Avoid whitespace characters such as blanks or tabulators between the different parameters
of a line.
If you modify the position or the size of a field, be sure that a text consisting of MaxChar
characters fits in this field.
Preserve the appropriate relation between the Frame and ValueArea parameters
throughout a template.
In most cases, you modify just the company name and reference your own logo file.
Example
Lines in the standard template file:
Logo=215,2705,abblogo.wmf,50
StaticText=395,2773,Arial,47,0,700,BA Automation & Drives
Corresponding lines in a template file for the company “X and Y”:
Logo=215,2705,xylogo.wmf,100
StaticText=400,2773,Arial,52,0,700,X and Y Co.
In this example, also the x-position of the text start and the font height had to be
changed. The new logo fits without downscaling, so it is scaled to 100%.

4-104 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.2 Preparatory Procedures

4. Check your new template set:

Select it for a new project in the Application Builder. Create a new node.
Start the Function Chart Builder. Select a new template by the File | Page Setup
command. Create a PC program. Fill the footer by the Edit | Document Texts command.
Inspect the footer in the function chart pane of the PC Section window.
Print a page of the function chart.
In the case of too many modifications, proceed step by step, always checking the partial
changes.

4.4.2.12 Remove an Object

Use the Application Builder for these application procedures.
For more and detailed information on the Application Builder see Application Builder User’s
Guide.
Choose the File | Open | Node List, Circuit List, Type Circuit List menu commands to open
the corresponding list with the existing objects.
Select a node and delete it by the File | Delete | Selected menu command.
Select a circuit and delete it by the File | Delete | Selected menu command.
Select a type circuit and delete it by the File | Delete | Selected menu command.

CAUTION
Be careful when selecting and deleting an object. The Application Builder deletes
all the files of the selected object, even its source file!

To delete a whole project with all its objects, use the File | Delete | Project menu command.

CAUTION
Be careful when deleting a project. The Application Builder deletes all files of the
pertaining objects, even their source files!

4.4.2.13 Regenerate an Object

To regenerate the internal data representation of objects, for example, after having installed a
new release of the Function Chart Builder, backtranslate the source code of the objects you
intend to work with. See Section 4.4.5.2, Backtranslate Source Code to Internal Representation.
To regenerate the source code of the objects, for example, after having installed a new release of
the Function Chart Builder, backtranslate their (old) source code and then generate source code
again. See Section 4.4.5.1, Generate Source Code.
These procedures work for type circuits only if they do not contain variants nor loops.
If you have type circuits or circuits prepared with Function Chart Editor 3.0/0, transform them
at first by the stand-alone utility program UpTCCI delivered with the Function Chart Editor
version 3.1/0 to match the valid source code syntax.
See also Figure B-8 in Appendix B, Data Flow in Function Chart Builder.

3BDS 100 595R401 4-105

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTE
Upgrading of objects after installation of a new FCB release is supported by the
File | Update FCB Data | Project and File | Update FCB Data | Selected
commands of the Application Builder (version 2.7 and higher).

4.4.2.14 Start-up of Diagnostics

You can start the Diagnostics (Diagnosis) program only from within the Function Chart Builder
and for AC 100 Series targets.
Connect the target on-line and choose the Target | Diagnostics command.
In case of AC 100 Series targets of newer node types, such as AC 160, AC 110 2.1 and higher,
AC 80, AC 70 1.1 and higher, and AC 55 1.1, it starts the Diagnostics program.
In case of AC 110 2.0, AC 70 1.0, and AC 55 1.0 it starts the Diagnosis program.
For detailed information see Section 4.4.7.1, Diagnostic Procedures with the Diagnostics
Program and Section 4.4.7.2, Diagnostic Procedures with the Diagnosis Program.

4.4.2.15 Ending Function Chart Builder and Diagnostics

You can end the Function Chart Builder and the Diagnostics (Diagnosis) program as any other
Windows application in the following ways:
• Select the application and choose the File | Exit command.
• Select the application and choose the Control | Close command in its Application Control
menu.
In case of unsaved changes the application asks whether you want to save them before exiting.
CAUTION
Be careful at answering warnings to avoid lost of useful changes that you made
since the last File | Save or File | Exit command.
If you are testing an AC 100 Series application on-line, Exit saves all selected
display terminals and all prepared force values by writing them to the Function
Chart Builder's internal data representation. When leaving the Function Chart
Builder, the PC force values are canceled on the target but the DB force values
remain active. The target will be disconnected.

If you exit the Function Chart Builder, the Application Builder gets generally the focus and
becomes the active Windows application.
If you exit the Diagnostics (Diagnosis) program, the Function Chart Builder gets generally the
focus and becomes the active Windows application.

4-106 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.3 Object-specific Programming Procedures

4.4.3 Object-specific Programming Procedures

4.4.3.1 Edit a Node

Preparation
Start the Function Chart Builder by the Tools | Function Chart Builder menu command from the
Application Builder.

Editing a Node
See Section 4.4.4.1, Choice of Sections to Section 4.4.4.12, Create/Edit/Delete a DB Element.

Special Features in the PC Section

Generally, a node can have one or several PC programs.
A PCPGM is the top PC element of each PC program.
AC 100 Series nodes must have only one PC program.

Other Special Features

The node has neither a symbol section, nor a TC/CI terminal section.
It is supported but not recommended that you insert (locate) circuits directly in nodes.

Suggested Next Steps

1. Save the internal data representation of the node, see File | Save command.
2. Generate AMPL source code, see Section 4.4.5.1, Generate Source Code.

NOTE
When you update your Function Chart Builder release, regenerate your nodes
belonging to your project. See Section 4.4.2.13, Regenerate an Object.

4.4.3.2 Prepare a Type Circuit

TC/CI Terminal Section of the Type Circuit

TC/CI terminals connect the type circuit to other elements when the type circuit is instantiated
in a node, node structure or circuit.
To specify type circuit terminals, see Section 4.4.4.14, Create/Edit/Delete a TC/CI Terminal.

Symbol Section of the Type Circuit

Symbols are used in one of the following ways:
• Symbols serve as parameters to change the properties and structure of the type circuit at its

3BDS 100 595R401 4-107

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

instantiation.
• Symbols serve as internal symbols (within the type circuit).
– They can simplify long symbolic expressions and symbolic formulas.
– They can combine use of arithmetical, logical, and relational operations allowed with
calculated symbols and the use of concatenation allowed with non-calculated
symbols.
To specify symbols, see Section 4.4.4.13, Create/Edit/Delete a Symbol.

DB Section of the Type Circuit

The DB elements of the type circuit can be understood as commands to create or modify DB
elements.
These “commands” are executed at the type circuit’s expansion time if you instantiated the type
circuit in a node structure or circuit.
Or they are executed at instantiation time if you instantiate the type circuit in a node.
So, the DB elements to be modified may be created outside the type circuit.
By using symbols, you make the DB elements and their properties, which are to be created or
modified by the type circuit, relocatable.
See Section 4.4.4.12, Create/Edit/Delete a DB Element.

PC Section of the Type Circuit

The PC section of a type circuit contains the control logic in relocatable form, which is
indicated by the relative item designation of the PC elements (*, *+1, and so on).
See Section 4.4.4.1, Choice of Sections to Section 4.4.4.10, Cut, Copy, and Paste in the PC
Section.

Considering Type Circuits for AC 100 Series Nodes

In case of type circuits instantiated in AC 100 Series nodes, the Function Chart Builder offers
different handling and on-line test capabilities depending on the structure and complexity of the
type circuits.
See the recommendations in Section 4.4.3.5, Type Circuits for AC 100 Series Nodes.

Suggested Next Steps

1. Save the internal data representation of the type circuit. See File | Save command.
2. Generate type circuit source code. See Section 4.4.5.1, Generate Source Code.

4-108 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.3 Object-specific Programming Procedures

NOTES
You can instantiate a type circuit if its source code is available in the project-
specific type circuit directory (..\NODES\PR_TC\TCDATA) or in the level1 or
level2 type circuit element libraries.

When you update your Function Chart Builder release, regenerate your type
circuits belonging to your project. See Section 4.4.2.13, Regenerate an Object.

See also
Figure B-3 in Appendix B, Data Flow in Function Chart Builder.

4.4.3.3 Edit a Type Circuit

General
See Section 4.4.4.1, Choice of Sections to Section 4.4.4.14, Create/Edit/Delete a TC/CI
Terminal.

Special Features in PC Section

A type circuit does not necessarily have a PC section.
The first or top PC element of a type circuit is not necessarily a structure element.

Special Features in DB Section

A type circuit does not necessarily have a DB section.
The DB elements of the type circuit can be understood as commands to create or modify DB
elements.
The DB elements to be modified in the type circuit may be created outside the type circuit.

Considering Type Circuits for AC 100 Series Nodes

See the recommendations in Section 4.4.3.5, Type Circuits for AC 100 Series Nodes.

Suggested Next Steps

1. Save the internal data representation of the type circuit. See File | Save command.
2. Generate type circuit source code. See Section 4.4.5.1, Generate Source Code.

4.4.3.4 Instantiate a Type Circuit

Preparation
Keep your project-specific type circuits and the type circuit element libraries as source code
files in the project-specific type circuit directory (..\NODES\PR_TC\TCDATA) and in the
level1 or level2 type circuit directories, respectively.

3BDS 100 595R401 4-109

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

When you start the Function Chart Builder, it finds the *.TCS source files and checks if they are
compatible with the actual Function Chart Builder version (they must contain the lines
VERSION TC 3 and TC_TYPE …).
A list of improper type circuits is stored in TCERRORS.LIS file.

Instantiating a Type Circuit in the PC Section

Insert one or more instances of the type circuit.
See Section 4.4.4.2, Insert PC Elements.
Select TC as element type in the Create Element dialog box.
In the Edit Symbol Values dialog box do the following:
1. Define the actual values of instance-unique symbols.
This happens in two steps if you have an advanced type circuit with variants (IFs) and
loops.
2. Modify the project-unique symbols if necessary.

Instantiating a Type Circuit in the DB Section

Insert one or more instances of the type circuit. See Section 4.4.4.12, Create/Edit/Delete a DB
Element.
Select TC as element type in the Create Element dialog box.
In the Edit Symbol Values dialog box do the following:
1. Define the actual values of instance-unique symbols.
This happens in two steps if you have an advanced type circuit with variants (IFs) and
loops.
2. Modify the project-unique symbols if necessary.

Response of the Function Chart Builder

If you are working on a node, the Function Chart Builder executes the following:
• Resolves the type circuit and interprets and checks all of its parts.
For example, it substitutes the symbols by their resulting values, interprets the DB
elements of the type circuit as DB create and modify commands, and executes the
connections.
• Connects the type circuit to the rest of the node and checks the interface.
• Connects the default values to the TC/CI terminals of the type circuit.
If you are working on a node structure or a circuit, the Function Chart Builder executes the
following:
• Connects the type circuit to the rest of node structure or circuit and checks the interface.
(There is only a restricted check for tree structure rules.)
• Connects the default values of the TC/CI terminals to the terminals of the type circuit.
Type circuits, which contain PC elements, are shown by a rectangle in the function chart and by
a corresponding line in the tree diagram.

4-110 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.3 Object-specific Programming Procedures

Type circuits, which contain DB elements and which were instantiated in the DB section, are
shown by $$TC in the DB Section window.
Type circuits, which contain DB elements and which were instantiated in the PC section, are
shown by $$DB_OF_TC in the DB Section window.

See also
Figure B-2 in Appendix B, Data Flow in Function Chart Builder.

4.4.3.5 Type Circuits for AC 100 Series Nodes

Type Circuit and Circuit Instances in AC 100 Series Nodes

At instantiation in the node, the type circuits are simply referenced, they are not disintegrated.
This is also reflected by the contents of the source code of the node containing type circuits.
At backtranslation of the node source code the Function Chart Builder offers the possibility to
disintegrate the type circuit instances: it resolves the type circuits and interprets and checks all
of their parts. See Section 4.5.4.18, File | Backtranslate Source….
This may be necessary due to the structure and complexity of some of type circuits, instantiated
in the AC 100 Series node.
Inserting (locating) circuits directly in nodes is supported though not recommended.
At location in a node, the circuits are resolved and disintegrated except the type circuit instances
within the circuits. The boundaries of the circuits are not visible any more, at most the type
circuit boundaries.

Type Circuit Classes for AC 100 Series Nodes

In case of type circuits instantiated in AC 100 Series nodes, the Function Chart Builder offers
different handling and on-line test capabilities depending on the structure and complexity of the
type circuits.
Classes of type circuits:
• Class 1 - type circuits containing only DB elements
• Class 2 - type circuits containing only simple PC elements, like AND, MOVE, PI, and so
on, and BLOCK and FUNCM structure elements, but no executable units CONTRM,
MASTER, and SEQ and no special structure elements SLAVEM and STEP
• Class 3 - type circuits containing DB elements and PC elements as in class 2
• Class 4 - type circuits containing any of the executable units CONTRM, MASTER, and
SEQ or special structure elements SLAVEM and STEP
• Class 5 - type circuits containing DB elements and PC elements as in class 4.
The target code generation for AC 100 Series nodes with circuits and the on-line editing and
testing of nodes with circuits concern their PC and DB elements and their TC instances.
For the latter, reapply the table; see cells describing handling of the pertaining TC class.

3BDS 100 595R401 4-111

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Handling of Type Circuit Classes for AC 100 Series Nodes

Table 4-7. Handling of Type Circuit Classes for AC 100 Series

Action Class 1 Class 2 Class 3 Class 4 Class 5

Create/instantiate + + + + +
type circuit (1)
off-line
Edit symbol + + + + +
values off-line
Delete type circuit + + + + +
off-line
Generate target + + + + but TC must be + but TC must be
code off-line disintegrated(2) disintegrated
Create/instantiate + + - - -
type circuit
on-line
Edit symbol - - - - -
values on-line
Delete type circuit + + - - -
on-line
On-line + for internal DB + for TC as a + for TC as a whole + for the internal + for the internal
monitoring and elements whole if it is not if it is not disinte- PC elements of PC elements of
forcing for TC created by the disintegrated; grated; or for inter- the TC (TC the TC (TC
instances in node TC or for internal nal PC elements if instance is instance is
PC elements if TC is disintegrated; disintegrated) disintegrated);
TC is + for internal DB + for internal DB
disintegrated elements created by elements created
the TC by the TC
(1) You can instantiate a type circuit only in its “non-disintegrated” form.
(2) You can disintegrate type circuits only at backtranslation of the node.

Advantages of Disintegrated and Non-disintegrated Forms of TC Instances

Disintegrated type circuit instances allow the following:
• Insight in the details of the type circuit instances
• On-line testing of internal signal states of the type circuit instances.
This form is useful if you start with testing new type circuits in AC 100 Series targets.
Non-disintegrated type circuit instances allow the following:
• Good overview of application program structure by hiding details of standard parts
• On-line testing of the signals on the type circuit terminals without the need to bother for
the type circuit contents and internal signal states.
You may appreciate this form if you work with already well-tested type circuits in
AC 100 Series targets.

4-112 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.3 Object-specific Programming Procedures

4.4.3.6 Prepare a Circuit

TC/CI Terminal Section of the Circuit

TC/CI terminals connect the circuit to other elements when the circuit is located in a node
structure. To specify circuit terminals, see Section 4.4.4.14, Create/Edit/Delete a TC/CI
Terminal.

Symbol Section of the Circuit

Symbols are used in one of the following ways:
• Symbols serve as parameters to change the properties and structure of the circuit when you
locate it.
• Symbols serve as internal symbols (within the circuit).
– They can simplify long symbolic expressions and symbolic formulas.
– They can combine use of arithmetical, logical, and relational operations allowed with
calculated symbols and the use of concatenation allowed with non-calculated
symbols.
To specify symbols, see Section 4.4.4.13, Create/Edit/Delete a Symbol.

DB Section of the Circuit

The DB elements of the circuit can be understood as commands to create or modify DB
elements.
These “commands” are executed during the circuit's expansion, for example, as part of the
expansion of node data for the node structure, in which the circuit is located.
So, the DB elements to be modified may be created outside the circuit.
By using symbols, you make the DB elements and their properties, which are to be created or
modified by the circuit, relocatable.
See Section 4.4.4.12, Create/Edit/Delete a DB Element.

PC Section of the Circuit

The PC section of a circuit contains the control logic in relocatable form, which is indicated by
the relative item designation of the PC elements (*, *+1, and so on).
See Section 4.4.4.1, Choice of Sections to Section 4.4.4.10, Cut, Copy, and Paste in the PC
Section.

Suggested Next Steps

1. Save the internal data representation of the circuit. See File | Save command.
2. Generate circuit source code. See Section 4.4.5.1, Generate Source Code.

3BDS 100 595R401 4-113

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTES
You can locate a circuit if its source code is available in the project-specific
circuit directory (..\NODES\PR_CI\CIDATA).
When you update your Function Chart Builder release, regenerate your circuits
belonging to your project. See Section 4.4.2.13, Regenerate an Object.

See also
Figure B-4 in Appendix B, Data Flow in Function Chart Builder.

4.4.3.7 Edit a Circuit

General
See Section 4.4.4.1, Choice of Sections to Section 4.4.4.14, Create/Edit/Delete a TC/CI
Terminal.

Special Features in PC Section

A circuit does not necessarily have a PC section.
The first or top PC element of a circuit is not necessarily a structure element.

Special Features in DB Section

A circuit does not necessarily have a DB section.
The DB elements of the circuit can be understood as commands to create or modify DB
elements.
The DB elements to be modified in the circuit may be created outside the circuit.

Special Feature in Symbol Section

The circuit may have also location-unique symbols.

Suggested Next Steps

1. Save the internal data representation of the circuit. See File | Save command.
2. Generate circuit source code. See Section 4.4.5.1, Generate Source Code.

4.4.3.8 Locate a Circuit

Preparation
Keep your project-specific circuits as source code files in the project-specific circuit directory
(..\NODES\PR_CI\CIDATA).
When you start the Function Chart Builder, it finds the *.CIS source files and checks if they are
compatible with the actual Function Chart Builder version (they must contain the lines
VERSION CI3 and CI_TYPE …).
A list of improper circuits is stored in CIERRORS.LIS file.

4-114 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.3 Object-specific Programming Procedures

NOTES
You can locate several circuits in the node structures (and nodes) of a project, but
you can locate each circuit only once.
Locating circuits directly in nodes is not recommended in independent mode.

Locating a Circuit in the PC Section

Locate the circuit.
See Section 4.4.4.2, Insert PC Elements.
Select CI as element type in the Create Element dialog box.
In the Edit Symbol Values dialog box do the following:
1. Define the actual values of instance-unique symbols.
2. Modify the project-unique symbols if necessary.
3. Check the values of location-unique symbols.

Locating a Circuit in the DB Section

Locate the circuit. See Section 4.4.4.12, Create/Edit/Delete a DB Element.
Select CI as element type in the Create Element dialog box.
In the Edit Symbol Values dialog box do the following:
1. Define the actual values of instance-unique symbols.
2. Modify the project-unique symbols if necessary.
3. Check the values of location-unique symbols.

Response of the Function Chart Builder

If you are working on a node structure, the Function Chart Builder executes the following:
• Connects the circuit to the rest of node structure and checks the interface.
(There is only a restricted check for tree structure rules.)
• Connects the default values of the TC/CI terminals to the terminals of the circuit.
Circuits, which contain PC elements, are shown by a rectangle in the function chart and by a
corresponding line in the tree diagram.
Circuits, which contain DB elements and which were instantiated in the DB section, are shown
by $$CI in the DB Section window.
Circuits, which contain DB elements and which were instantiated in the PC section, are shown
by $$DB_OF_CI in the DB Section window.
If you are working on a node, the Function Chart Builder executes the following:
• Resolves the circuit and interprets and checks all of its parts. For example, it substitutes the
symbols by their resulting values, interprets the DB elements of the circuit as DB create
and modify commands, and executes the connections.
• Connects the resolved and disintegrated circuit to the rest of the node and connects the
default values to the terminals that used to be the TC/CI terminals.
The boundaries of the resolved circuits in the node are not visible any more.

3BDS 100 595R401 4-115

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.4.3.9 Edit a Node Structure

Preparation
Start the Function Chart Builder by the Tools | Node Structure Function Chart Builder menu
command from the Application Builder.

Editing a Node Structure

See Section 4.4.4.1, Choice of Sections to Section 4.4.4.13, Create/Edit/Delete a Symbol.

Special Features in the PC Section

The node structure can have several PC programs. A PCPGM is the top PC element of each PC
program.
You can insert (locate) circuits.

Special Features in the DB Section

You can insert (locate) circuits.

Special Feature in the Symbol Section

You should create only symbols, which occur in the located circuits and the instantiated type
circuits. Define them as project-unique (PU) symbols.

Other Special Features

You generally locate circuits, and add PC and DB elements (perhaps type circuits) as glue logic.
The Function Chart Builder follows the principle of late instantiation:
• The circuits and type circuits are referenced in the node structure but not expanded.
• The Function Chart Builder checks only the interface of these elements, so you can work
with virtual elements and refer to virtual terminals.

Suggested Next Steps

1. Save the internal data representation of the node structure. See File | Save command.
2. Generate node structure source code. See Section 4.4.5.1, Generate Source Code.

NOTES
You can expand node data if the node structure source code is available in the
\CIDATA subdirectory of the node.

When you update your Function Chart Builder release, regenerate your node
structures belonging to your project. See Section 4.4.2.13, Regenerate an Object.

See also
Figure B-5 in Appendix B, Data Flow in Function Chart Builder.

4-116 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.3 Object-specific Programming Procedures

4.4.3.10 Expand Node Data

Preparation
1. Keep the node structure source code files in the \CIDATA subdirectory of the node.
2. Start the Function Chart Builder by the Tools | Function Chart Builder menu command
from the Application Builder.
3. Initialize the node if necessary.

Expanding Node Data

Choose the File | Expand Node Structure command.
The Function Chart Builder resolves the circuit and type circuit references in the node structure
and the type circuit references in the circuits, that is, replaces the references with the referenced
objects. The result is stored as internal data representation of the selected node.
See also Figure B-6 in Appendix B, Data Flow in Function Chart Builder.

Suggested Next Steps

1. Save the internal data representation of the node. See File | Save command.
2. Generate AMPL source code. See Section 4.4.5.1, Generate Source Code.

4.4.3.11 Update Type Circuit Instances and Located Circuits

Definition
1. You are working according to the straightforward method. You program nodes directly and
instantiate type circuits in them. Suppose that the node is edited ready. Then you change
the type circuits and generate new type circuit source code.
2. You are working according to the function oriented project engineering method.
You program node structures and circuits and expand node structures to nodes.
Suppose the node structure is ready and you have expanded it. Then you change type
circuits and circuits and generate new type circuit and circuit source code, respectively.
In both case you have to update the instances of the changed objects to make the changes
effective in the node.

Preparation
1. The new type circuit source code, if any, is available in the project-specific type circuit
directory (..\NODES\PR_TC\TCDATA) or in the level1 or level2 type circuit directories.
The new circuit source code, if any, is available in the in the project-specific circuit
directory (..\NODES\PR_CI\CIDATA). To take them into account during the current
Function Chart Builder session, use the File | Rebuild Element Types command.
2. In case of the straightforward method edit the node and find out the symbol values that
were set at the instantiation of the old type circuits.
In case of the function oriented project engineering method edit the node structure and find
out the symbol values that were set at the instantiation of the old type circuits and at the
location of the old circuits.

3BDS 100 595R401 4-117

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Update of Type Circuits (Circuits) Instantiated (Located) in DB Section

1. Delete the corresponding type circuit instances (located circuits) in the DB Section
window. See Section 4.4.4.12, Create/Edit/Delete a DB Element.
2. Re-instantiate (re-locate) them one by one.
See Section 4.4.3.4, Instantiate a Type Circuit, Section 4.4.3.8, Locate a Circuit.

Update of Type Circuits (Circuits) Instantiated (Located) in PC Section

1. Select all PC programs containing the corresponding type circuit instances (located
circuits) in the *.ODB window and cut them.
See Section 4.4.4.9, Multiple Selection of PC Elements.
2. Re-paste them at once. See Section 4.4.4.10, Cut, Copy, and Paste in the PC Section.

Special Case - Update of Circuits Located in Nodes

If you work according to the straightforward method and locate circuits directly in node, the
Function Chart Builder resolves and disintegrates the circuits at once and their boundaries are
not visible any more. You can try to use the previously described procedures accordingly:
1. Consult the documentation of the old circuit to identify all its DB and PC elements.
Delete the DB and PC elements of the node stemming from the old circuit.
2. Study the old circuit instance to find out the symbol values set at its location.
Locate the new circuit with appropriate symbol values.
3. Reconstruct possible later connections to and changes of the DB and PC elements
stemming from the circuit.
CAUTION
This is a very unreliable procedure. To prevent the need for its usage, we
recommend not to locate circuits directly in nodes in independent mode.

Suggested Next Steps

1. In case of the function oriented project engineering method generate node structure source
code and expand node data.
2. Save the internal data representation of the node and generate source code. See the File |
Save command and Section 4.4.5.1, Generate Source Code.

4.4.4 Section-specific Programming Procedures

4.4.4.1 Choice of Sections
PC Section
To create and edit PC elements do the following:
• Create or open the PC Section window by the File | New Section | PC or
File | Open Section | PC command.
• In case of nodes and node structures define the name of the PC program.
• Open or select the PC Section window pane with the tree diagram if you want to have an
overview of the control logic and to break the function chart into pages.

4-118 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

• Open or select the PC Section window pane with the function chart if you want to have a
more detailed view of the control logic, including the connections between the PC
elements, located circuits, and instantiated type circuits.
Use the View | Function Chart and View | Tree … commands to select the corresponding view
in the active pane.

DB Section
To create and edit data base, create or open the DB Section window by the
File | New Section | DB or File | Open Section | DB command.

The following section is also available if you are working on a circuit or a type circuit or a node
structure:

Symbol Section
To create and edit symbols, create or open the Symbol Section window by the
File | New Section | Symbol or File | Open Section | Symbol command.

The following section is also available if you are working on a circuit or a type circuit:

TC/CI Terminal Section

To create and edit TC/CI terminals, create or open the TC/CI Terminal Section window by the
File | New Section | TC/CI Terminal or File | Open Section | TC/CI Terminal command.

4.4.4.2 Insert PC Elements

Preparation
Select the PC Section window pane with function chart or tree diagram.

Inserting a PC Element on Lower Structure Level

1. Select the PC element (or instantiated type circuit or located circuit), below which you
want to insert the new PC element (or type circuit or circuit).
2. Choose the Edit | Create command.
3. Select the On Lower Level option in the Create Element dialog box.
4. Select the appropriate items, edit the call parameters or the symbol values if applicable.
5. Activate the OK or Apply button.

Inserting a PC Element on the Same Level as an Existing Element

1. Select the PC element (or instantiated type circuit or located circuit), behind which but on
the same level you want to insert the new PC element (or type circuit or circuit).
2. Choose the Edit | Create command.
3. Select the On Same Level option in the Create Element dialog box.
4. Select the appropriate items, edit the call parameters or the symbol values if applicable.
5. Activate the OK or Apply button.

3BDS 100 595R401 4-119

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTES
Unless you resolve and disintegrate instantiated type circuits and located circuits,
you cannot reach their inside, you cannot insert further PC elements inside them,
and you cannot insert further PC elements on a lower level below them.

To be able to select PC elements by shortcuts UP, DOWN, and so on, in the

PC Section window be sure the slide mode is cleared.
See Window | Slide command.

If you miss some PC elements in the list box of the Create Element dialog box,
be sure you selected the appropriate filter, for example, ‘*’, element type, and
insert level.

Inserting Several PC Elements (from the Paste Buffer)

See Section 4.4.4.9, Multiple Selection of PC Elements and Section 4.4.4.10, Cut, Copy, and
Paste in the PC Section for selecting and inserting several PC elements.

4.4.4.3 Change the Order of PC Elements

Order of PC Elements
The PC elements (and instantiated type circuits and located circuits) can be ordered by their
item designation and by the sequence, in which they are executed in the target.
The item designation and the execution order correspond initially to the order of creation of
these elements.
Select the PC Section window pane with function chart or tree diagram.

Changing the Execution Order of PC Elements

1. Select the PC element (or type circuit or circuit), the position of which you want to change
in the execution order.
2. Choose the PC-Section | Execution Order | Move Down or the PC-Section | Execution
Order | Move Up command depending on the direction of the change.

NOTE
If you move a structure element, its subordinate elements are also moved.

Matching Item Designation of Subordinate Elements to a New Execution Order

If you want to renumber all subordinate elements belonging to a structure element, proceed as
follows:
1. Select the structure element (or type circuit or circuit), the subordinate elements of which
you want to renumber.
2. Choose the PC-Section | Renumber Lower Level command.

4-120 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

Renumbering Item Designation of Several Neighboring Elements

If you want to renumber several neighboring PC elements (or type circuit or circuit) and to set
their item designations to a contiguous new range, proceed as follows:
1. Select the PC elements that you want to renumber.
2. Choose the PC-Section | Renumber … command.

Changing the Item Designation of PC Elements

1. Select the PC element (or type circuit or circuit), the item designation of which you want
to modify.
2. Choose the PC-Section | Modify Item Designation command.

4.4.4.4 Connect Terminals by Editing the Connection Definition

Connections
The Function Chart Builder supports the following kinds of connections:
• PC terminal to PC terminal
• DB terminal to PC terminal
• Constant to PC terminal
• PC terminal to PC terminal by name,
if you are working on a circuit or type circuit or node structure, also
• Symbol or symbolic expression to PC terminal,
if you are working on a circuit or type circuit, also
• TC/CI terminal to PC terminal.

NOTES
The Function Chart Builder offers many alternatives of connecting by commands
in the Menu Bar and the context menu and by buttons in dialog boxes.
In this section we give only one general alternative for connection.

To be able to select PC elements and PC terminals by shortcuts UP, LEFT, and so on,
be sure the slide mode is cleared. See Window | Slide command.

When you connect terminals, for a better overview of the PC program open more
than one PC Section window by the Window | New command.

Common Method to Connect by Editing the Connection Definition

1. Select the PC Section window pane with function chart.
2. Choose the PC-Terminal | Connect command.
3. To select a PC element and a PC terminal, edit the Item Designation text box of the
Connect dialog box, or activate the Next button to jump to the next terminal
corresponding to the condition set in the Next drop-down box.

3BDS 100 595R401 4-121

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4. The Function Chart Builder suggests a connection definition in the To text box of the
Connect dialog box on the basis of the recent connections.
Accept it or select another one from the list box part of the To text box.
Or edit a new connection definition.
In many cases instead of disconnecting some terminals and then connecting other ones you
can simply re-edit the connection definition.
5. Activate the OK or the Apply/Next button.

Syntax of Connection Definition

The connection strings correspond to the AMPL source code syntax.
• A minus `-´ means that the PC terminal is inverted.
• Item designations participating in multiple connections are separated by commas `,´.
• An empty string means no connection (disconnect).
In case of multiple connections to constants, DB terminals, symbols, and TC/CI terminals, the
connection string starts with the source definition.
All the terms of the connection string must be of the same data type.

Examples of Connection Definition for Specifying Different Items

• Item designation: PC2.1.4:1 *+2.3:2 =DI1.7
• Name: ADDER4:1 BRAKE2 =RATE:ERR
• Constant: 0 D=1 CD=0 MD=0 D=“Ready” D=3.14
• TC/CI terminal: T=<INPUT> T=<OUTPUT>
• Symbol: <PARAM1> N=<VAR4>
• Symbolic expression:PC1.1.<PAR1>:20 N=SIGNAL<NR2>

Examples of Relative PC Connection Definition

Suppose PC1.2.3:1 is selected. Then you can define connection/PC item designation also by
:20 instead of PC1.2.3:20 same element
.4:20 instead of PC1.2.4:20 same level
.4.5:20 instead of PC1.2.4.5:20 1 level down
.4.5.6:20 instead of PC1.2.4.5.6:20 2 levels down
Moreover, Function Chart Builder supports definition of connection/PC item designation also
with relative item designations by traversing upper levels of the tree.
Suppose PC1.2.3:1 is selected. Then you can define connection/PC item designation also by
..7:5 instead of PC1.7:5 1 level up
...1:5 instead of PC1:5 2 levels up
..7.8.9:4 instead of PC1.7.8.9:4 1 level, 2 levels down
In the examples, the third level is shown boldfaced for better orientation.

Examples of Connection Definition for Specifying Multiple Connections

• Multiple connection, the PC output terminal source is selected:
PC1.1.4:1, PC1.1.5:1, PC1.1.6:1

4-122 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

• Multiple connection, PC input terminal considered as primarily attached to the constant

source is selected: D=1, PC1.1.2:1, PC1.1.2:2, PC1.1.2:3
• Multiple connection, PC input terminal considered as primarily attached to the DB
terminal source is selected: =DI1.7, PC1.1.3:2, PC1.4.3:1

Examples of Connection Definition for Specifying Name and Unit

• Name: …, N=G03
• Unit: …, U=m/s

See also
Section 4.4.1.2, How to Use the Mouse for mouse shortcuts to simplify connecting,
Section 4.4.8.5, Use of Symbols for connections to symbols and symbolic expressions,
Section 4.4.4.5, Connect Terminals by Dedicated Commands, and
Section 4.4.4.6, Connect Terminals by Mouse for further alternatives.

4.4.4.5 Connect Terminals by Dedicated Commands

NOTES
The Function Chart Builder offers many alternatives of connecting by commands
in the Menu Bar and the context menu and by buttons in dialog boxes.
In this section we give only one alternative for each kind of connection.

To be able to select PC elements and PC terminals by shortcuts UP, LEFT, and so on,
be sure the slide mode is cleared. See Window | Slide command.

When you connect terminals, for a better overview of the PC program open more
than one PC Section window by the Window | New command.

Preparation
1. Select the PC Section window pane with the function chart.
2. Select (or select and mark) the PC element and the terminal, which you want to connect.
For selection and marking you can use the commands Edit | Find, PC-Section | Goto
Element | …, PC-Terminal | Goto | … and PC-Terminal | Mark, respectively.

Connecting the Marked PC Terminal to Another PC Terminal

1. Select the PC element and the other terminal, which you want to connect.
For selection you can use the Edit | Find, PC-Section | Goto Element | … and
PC-Terminal | Goto | … commands.
2. Choose the PC-Terminal | Connect Selected | To Marked command.

Connecting a DB Terminal to the Selected PC Terminal

1. Select the DB Section window.
2. Select the DB element and the DB terminal, which you want to connect.
3. Choose the PC-Terminal | Connect Selected command.

3BDS 100 595R401 4-123

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Connecting the Selected PC Terminal by Name

1. Select the Name Table window.
2. Select the name, by which you want to connect the selected terminal, in fact, to a PC
output terminal, a constant or a DB terminal.
3. Choose the PC-Terminal | Connect Selected command.

Connecting a Symbol to the Selected PC Terminal

1. Select the Symbol Section window.
2. Select the symbol, which you want to connect.
3. Choose the PC-Terminal | Connect Selected command.

Connecting a Symbolic Expression to the Selected PC Terminal

1. Select the PC Section window with function chart.
2. Choose the PC-Terminal | Connect Selected | To Symbol command.
3. Edit the symbolic expression in the Connection Definition text box of the Connect
Symbol dialog box.
4. Activate the OK button in the Connect Symbol dialog box.
5. Activate the OK or the Apply/Next button in the Connect dialog box.

Examples of Connection Definition Using Symbolic Expressions

• D=KEY<PARAM1>
• N=<<ANAME>BNAME>

Connecting a TC/CI Terminal to the Selected PC Terminal

1. Select the TC/CI Terminal Section window.
2. Select the TC/CI terminal, which you want to connect.
3. Choose the PC-Terminal | Connect Selected command.

See also
Section 4.4.4.6, Connect Terminals by Mouse to simplify connecting,
Section 4.4.8.5, Use of Symbols for connections to symbols and symbolic expressions.

4.4.4.6 Connect Terminals by Mouse

Preparation
1. Select the PC Section window pane with function chart.

4-124 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

2. Select (or select and mark) the PC element and the terminal, which you want to connect,
by clicking on it (with the left mouse button).
3. Prepare an other window of the appropriate section to show the item to be connected with
the PC terminal selected in step 2.

Connecting Another PC Terminal to the Marked PC Terminal

1. Select a PC Section window pane with function chart showing the PC element and the
other terminal.
2. You have two alternatives (the second one only since Function Chart Builder version 4.7):
a. “Classical” quick connect mode. To set it, choose the Options | Preferences
command and select the Quick Connect by Right Mouse Button option.
Click on the other terminal with the right mouse button.
b. Connect by context menu. To set this mode, choose the Options | Preferences
command and unselect the Quick Connect by Right Mouse Button option.
Double-click on the other terminal with the right mouse button. In fact, you open the
context menu with the first click and you choose the Connect to Marked menu item,
which is in that case always directly under the cursor, with the second click.

Connecting a DB Terminal to the Selected PC Terminal

1. Select the DB Section window showing the DB element.
2. Select the DB element in the Item Designation, Instance Name,… list box and select a
DB terminal in the DB Terminal drop-down list box.
This step is necessary only if you want to connect a DB terminal other than VALUE.
3. Click on the DB element in the Item Designation, Instance Name,… list box with the
right mouse button.

Connecting the Selected PC Terminal by Name

1. Select the Name Table window showing the name.
2. Click on the name in the Kind, Name,… list box with the right mouse button.

Connecting a Symbol to the Selected PC Terminal

1. Select the Symbol Section window showing the symbol.
2. Click on the symbol in the Name, Kind,… list box with the right mouse button.

Connecting a TC/CI Terminal to the Selected PC Terminal

1. Select the TC/CI Terminal Section window showing the TC/CI terminal.
2. Click on the TC/CI terminal in the Name, No.,… list box with the right mouse button.

3BDS 100 595R401 4-125

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.4.4.7 Disconnect a Terminal

Removing a Connection by Disconnect Command

1. Select the PC Section window pane with function chart.
2. Select the PC element and the terminal, which you want to disconnect.
For selection you can use the Edit | Find, PC-Section | Goto Element | … and
PC-Terminal | Goto | … commands.
3. Choose the PC-Terminal | Disconnect command in the Menu Bar, or the Disconnect
command in the context menu, or activate the corresponding button in the Toolbar.

Removing a Connection by Editing the Connection String

1. Select the PC Section window pane with function chart.
2. Select the PC element and the terminal, which you want to disconnect.
For selection you can use the Edit | Find, PC-Section | Goto Element | … and
PC-Terminal | Goto | … commands.
3. Choose the PC-Terminal | Connect command. The Function Chart Builder shows the
connection string in the To text box of the Connect dialog box.
4. Delete the terminal to be disconnected in the connection string. Keep the connection rules
and the syntax of the connection definition in case of multiple connections.

4.4.4.8 Delete PC Elements

Deleting One or Several PC Elements

1. Select the PC Section window pane with function chart or tree diagram.
2. Select the PC elements (or instantiated type circuits or located circuits), which you want to
delete. See Section 4.4.4.9, Multiple Selection of PC Elements.
3. Choose the Edit | Delete command.

Deleting All PC Elements of One or Several PC Programs

1. Select the *.ODB window.
2. Select one or several PC programs in the Contents box of the *.ODB window.
3. Choose the Edit | Delete command.

Deleting the Last PC Element of the PC Section

Choose the File | Delete Section | PC command.

4-126 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

4.4.4.9 Multiple Selection of PC Elements

Purpose
The Function Chart Builder allows multiple selection during on-line editing in the PC section,
that is, the selection of more than one PC element, to support and enhance the cut, copy, and
delete function. Due to the tree structure of PC programs, the Function Chart Builder supports
contiguous multiple selection only.

Multiple Selection in PC Section Windows by Command

Use the PC-Section | Select command. Fill the From Item Designation and To fields
appropriately in the Select PC Section dialog box. Or activate the To End of Subtree button to
fill the To field automatically.

Selection in PC Section Windows by Mouse

Table 4-8. Selection in PC Section Windows by Mouse

Action Selected PC Elements

Click Selection of the pointed single PC element
Pressing SHIFT and Contiguous multiple selection, that is, extension of the
click selection to all PC elements from the previously selected
ones to the pointed one
Pressing SHIFT and Contiguous multiple selection, that is, selection of the pointed
double-click single PC element and extension of the selection from the
pointed one to the end of subtree on lower level

3BDS 100 595R401 4-127

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Selection in PC Section Windows by Keys

Table 4-9. Selection in PC Section Windows by Keys

Action Selected PC Elements

UP/DOWN Selection of the previous/next single PC element
SHIFT + UP/DOWN Add previous/next PC element to selection
SHIFT + PGUP/PGDOWN Add all PC elements on the previous/next page to selection
SHIFT + HOME/END Extension of the selection to the top/bottom PC element
SHIFT + CTRL + LEFT Extension of the selection to the end of subtree on lower level
SHIFT + CTRL + RIGHT Extension of the selection to higher level

Scope of Selection in PC Section Windows

The multiple selection in the PC Section window pane with the function chart covers all PC
elements shown in reverse video.
The scope of selection in the PC Section window pane with the tree diagram depends on the
views All Elements, Structure Elements, and Top of Page Elements as set by the
corresponding View | Tree - … command:
• In Tree - All Elements view the multiple selection covers all PC elements shown in
reverse video.
• In Tree - Structure Elements view the multiple selection covers all structure elements
shown in reverse video and also all PC elements in the subtrees under these structure
elements.
• In Tree - Top of Page Elements view the multiple selection covers all top of page
elements shown in reverse video and also all PC elements in the subtrees under these top
of page elements.

Selection in *.ODB Window

Select one, several, or all PC programs or—in case of type circuits and circuits—the whole PC
section in the Contents box of the *.ODB window to select all the PC elements of these PC
programs or of the PC section.

Allowed, Restricted and Illegal Cases of Multiple Selection

Contiguous selection of PC elements on same level:

4-128 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

Edit | Cut allowed, Edit | Copy allowed, Edit | Delete allowed.

Figure 4-95. Contiguous Selection of PC Elements on Same Level

Selection of whole executable unit:

Edit | Cut allowed, Edit | Copy allowed, Edit | Delete allowed

Figure 4-96. Selection of Whole Executable Unit

3BDS 100 595R401 4-129

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Selection of partial subtree on lower level:

Edit | Cut NOT allowed, Edit | Copy allowed, Edit | Delete NOT allowed.

Figure 4-97. Selection of Partial Subtree on Lower Level

NOTE
The Edit | Cut or Edit | Delete command must not
leave any subtree without “father” element.

Disjoint selection of PC elements is NOT POSSIBLE at all.

Figure 4-98. Impossible Disjoint Selection of PC Elements

4-130 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

Selection from lower level of a subtree to higher level of another subtree is NOT ALLOWED.

Figure 4-99. Non-allowed Selection from Lower Level to Higher Level

Suggested Next Steps

Cut, copy or delete the selected PC elements. See Section 4.4.4.10, Cut, Copy, and Paste in the
PC Section and Section 4.4.4.8, Delete PC Elements.

4.4.4.10 Cut, Copy, and Paste in the PC Section

Purpose
To copy or move one or more PC elements (or instantiated type circuits or located circuits) with
its or their connections, names, and symbol values to a so called paste buffer and then to copy
the contents of the paste buffer to the PC section.
Cut, copy, and paste are possible during off-line editing having the following scopes:
• Within one object (node, node structure, type circuit or circuit)
• Between objects of same or different type within a project
• Between objects of different projects
• Between different versions of Function Chart Builder supporting cut, copy, and paste.

Cut
1. Select one or more PC elements (or instantiated type circuits or located circuits), or one or
more PC programs or the whole PC section. See Section 4.4.4.9, Multiple Selection of PC
Elements.
2. Choose the Edit | Cut command.
The Function Chart Builder copies the selection to the paste buffer and then deletes the
selection.

3BDS 100 595R401 4-131

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Copy
1. Select one or more PC elements (or instantiated type circuits or located circuits), or one or
more PC programs, or the whole PC section. See Section 4.4.4.9, Multiple Selection of PC
Elements.
2. Choose the Edit | Copy command.
The Function Chart Builder copies the selection to the paste buffer.

Paste
1. Preparation
a. It is supposed that due to the last Cut or Copy command the paste buffer contains the
PC elements you want to paste. If necessary, select another object or an object in
another project, or start a new session with another version of Function Chart Builder
supporting cut, copy, and paste.

NOTE
It makes no difference whether the paste buffer contents stem from PC Section
window pane with function chart or tree diagram, or an *.ODB window.

b. Be sure the options (PC element libraries) selected in Application Builder for the
current object contain all PC elements to be pasted.
If you want to paste also instantiated type circuits or located circuits, be sure they are
present in the PR_TC and PR_CI subdirectory pertaining to the current object.
If necessary, select or copy the libraries using commands of Application Builder.
c. The Function Chart Builder does not create automatically DB elements, TC/CI
terminals, or symbols when it replaces connections to them.
So create corresponding DB elements, TC/CI terminals, and symbols before paste.
d. Select a single PC element (or instantiated type circuit or located circuit) as insertion
point in the PC Section window pane either with function chart or tree diagram.
The insertion point has to match to the first element in the paste buffer.
For example, no CONTRM can be pasted on the same level as an AND,
or no instantiated type circuit can be pasted into another type circuit.
To paste a whole PC program or a whole PC section, no insertion point is necessary
and you can select also the *.ODB window instead of the PC Section window.
2. Choose the Edit | Paste command.
The Function Chart Builder opens the Paste PC Section dialog box.
Open further dialog boxes to check or specify paste options and replace rules:
a. In the Paste Options PC Section dialog box check connections, names, units, page
divisions to be preserved at paste. Uncheck items you do not want to be pasted.
These are automatically disconnected/deleted at paste.
b. In the Replace and Paste PC Section dialog box find and replace names,
connections to DB, to TC/CI terminals, to symbols, and so on.
If applicable, choose the Edit | Symbol Values command to edit symbol values of
type circuits and circuits.

4-132 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

3. Start pasting without replacing names, and so on, by activating the OK button of the Paste
PC Section dialog box or with replacing names, and so on, by activating the OK button of
the Replace and Paste PC Section dialog box.
In case of conflicts the Function Chart Builder executes the following:
– Opens the Output window and displays the error messages and warnings.
– Indicates in a message box that not all PC elements are correctly pasted and offers the
Undo Paste function.
4. Correct the conflicts depending on the severity and number of conflicts:
– Solve connection conflicts by selecting the lines in the Output window one by one,
double-clicking on them or pressing F4 to open automatically the appropriate
Connect dialog box and correcting the connections there.
– Undo the paste operation, change paste options and replace rules,
then repeat the Paste command.
– Undo the paste operation, select necessary options (libraries) in Application Builder,
create necessary DB elements, terminals, symbols, and unique names,
restart the Function Chart Builder if necessary, then repeat the Paste command.

Undo Paste
• Undo paste by activating the Undo Paste button or the Edit | Undo Paste command.
Thereafter, the PC section equals the one before pasting. The paste buffer is not affected.
• After successful paste, all pasted PC elements are selected in the PC Section window.
So you can undo the recent paste operation also by deleting the selected PC elements.
• Undo is also possible if paste is incomplete due to conflicts. See Step 4 above.

4.4.4.11 Create/Edit/Delete a Name

PC Names
Creating/Editing a Signal Name
1. Select a PC element terminal, in fact, a signal source, in the PC Section window.
2. Choose the Edit | Name command.
3. Create a name for the selected terminal or edit it in the Create/Edit Name dialog box.
4. Activate the OK or Apply button.
Alternatively, you can directly edit in the Item Designation and Name text boxes of the
Create/Edit Name dialog box.

Creating/Editing a PC Instance Name

1. Select a PC element, or an instantiated type circuit, or a located circuit in the PC Section
window.
2. Choose the Edit | Name command.

3BDS 100 595R401 4-133

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

3. Create a name for the selected element or edit it in the Create/Edit Name dialog box.
4. Activate the OK or Apply button.
Alternatively, you can directly edit in the Item Designation and Name text boxes of the
Create/Edit Name dialog box.

Inspecting and Editing PC Names

1. Select the Name Table window and appropriate filters to inspect PC names.
2. To modify a name, select it and choose the Edit | Name command.
3. Modify the name in the Create/Edit Name dialog box.
4. Activate the OK or Apply button.

Deleting a PC Name
1. Select the PC Section window and select the PC element or the terminal, from which you
want to remove the name.
Or select the Name Table window and select the name to be deleted.
2. Choose the Edit | Delete Name command.
Alternatively, you can directly delete the name string in the Name text box of the Create/Edit
Name dialog box.

DB Names
Creating/Editing a DB Instance Name
1. In the DB Section window select a DB element, or a type circuit (instantiated in the DB
section), or a circuit (located in the DB section).
2. Choose the Edit | Name command.
3. Create a name for the selected element or edit it in the Create/Edit Name dialog box.
4. Activate the OK or Apply button.
Alternatively, you can directly edit in the Item Designation and Name text boxes of the
Create/Edit Name dialog box.
Further alternative in case of DB elements
(not applicable in case of type circuits instantiated in the DB section and circuits located in the
DB section):
1. In the DB Section window select a DB element, or a type circuit (instantiated in the DB
section), or a circuit (located in the DB section).
2. Choose the Edit | DB Terminal Values command.
3. Edit the value of the NAME terminal in the Edit Terminal Values dialog box.
4. Activate the OK or Apply button.

4-134 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

Deleting a DB Instance Name

1. Select the DB Section window and select the DB element, from which you want to remove
the name.
2. Choose the Edit | Delete Name command.
Alternatively, you can directly delete the name string in the Name text box of the Create/Edit
Name dialog box.
Further alternative in case of DB elements
(not applicable in case of type circuits instantiated in the DB section and circuits (located in the
DB section):
1. Select the DB Section window and select the DB element, from which you want to remove
the name.
2. Choose the Edit | DB Terminal Values command.
3. Delete the value of the NAME terminal in the Edit Terminal Values dialog box.
4. Activate the OK or Apply button.
When you delete the name of a DB element, the Function Chart Builder assigns the item
designation as default instance name.
(This is not applicable for type circuits instantiated in the DB section and circuits located in the
DB section.)

See also
Section 4.4.8.3, Use of Names and Appendix E, Syntax of Names.

4.4.4.12 Create/Edit/Delete a DB Element

Creating a DB Element
1. Select the DB Section window.
2. Choose the Edit | Create command.
3. Select the element type, callname, instance, select the check boxes in the Create Element
dialog box.
4. Check or edit the DB terminal values or—in case of type circuits and circuits to be
instantiated/located in the DB section—the symbol values.
5. Activate the OK or Apply button.

NOTE
If you miss some DB elements in the list box of the Create Element dialog box,
be sure you selected the appropriate filter, for example, ‘*’, element type, and
modify attribute.

3BDS 100 595R401 4-135

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Editing a DB Element
1. Select the DB Section window.
2. Select the DB element, which you want to edit.
3. Choose the Edit | DB Terminal Values command.
4. Select the appropriate DB element parts in the Edit DB Terminal Values dialog box.
5. Edit the appropriate DB terminals or the symbol values as applicable.
6. Activate the OK or Apply button.

Editing a TC (CI) Instantiated (Located) in DB Section,

Editing a TC (CI) Instantiated (Located) in PC Section and Containing also
DB Elements
1. Select the appropriate section window.
2. Select the instantiated type circuit or the located circuit, which you want to edit.
3. Choose the Edit | Symbol Values command.
4. Edit the symbol values in the Edit Symbol Values dialog box.
5. Activate the OK button.

Deleting a DB Element
1. Select the DB Section window.
2. Select the DB element, which you want to delete.
3. Choose the Edit | Delete command.

4.4.4.13 Create/Edit/Delete a Symbol

Creating a Symbol Explicitly

1. Select the Symbol Section window.
2. Choose the Edit | Create command.
3. Edit the symbol name, select the symbol kind and type and edit the default value in the
Create Symbol dialog box.
4. Activate the OK or Apply button.

Creating a Symbol Implicitly (“on the fly”)

1. Use a new, undeclared symbol, for example, connect a PC terminal to a new symbol.
Edit the connection definition in the Connect dialog box, type the new symbol name with
symbol delimiters < and >.
Activate the OK or Apply button.
The Function Chart Builder displays the Create Symbol dialog box as above.

4-136 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

2. Select the symbol kind and type and edit the default value in the Create Symbol dialog
box.
3. Activate the OK or Apply button.
The Function Chart Builder connects the specified PC terminal and the symbol.

NOTES
A default value is optional for instance-unique symbols and mandatory for
location-unique and project-unique symbols.

If you are working on a node structure, do not create new symbols. You can
assign new values to project-unique symbols, which are available due to located
circuits and instantiated type circuits. Define them as project-unique symbols in
the node structure.

Editing a Symbol
1. Select the Symbol Section window, select the symbol.
2. Choose the Edit | Symbol command.
3. Modify the symbol kind, type, and default value in the Edit Symbol dialog box.
4. Activate the OK or Apply button.

Deleting a Symbol
1. Select the Symbol Section window.
2. Select the symbol, which you want to delete.
3. Choose the Edit | Delete command.

See also
Section 4.4.8.4, About Symbols,
Section 4.4.8.7, Values of Symbols.

4.4.4.14 Create/Edit/Delete a TC/CI Terminal

Creating a TC/CI Terminal Explicitly

1. Select the TC/CI Terminal Section window.
2. Choose the Edit | Create command.
3. Select the terminal name, number, kind, and type and edit the default value in the Create
TC/CI Terminal dialog box.
4. Activate the Attributes button and select the attributes in the Edit TC/CI Terminal
Attributes dialog box as you need them for the graphical presentation of the type circuit
(circuit) at its instantiation (location).
5. Activate the OK or Apply button.

3BDS 100 595R401 4-137

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Creating a TC/CI Terminal Implicitly (“on the fly”)

1. Use a new, undeclared TC/CI terminal, for example, connect a PC terminal to a new TC/CI
terminal.
Edit the connection definition in the Connect dialog box, type the new TC/CI terminal
name with symbol delimiters < and > in form of T=<TC/CI_terminal>.
Activate the OK or Apply button.
The Function Chart Builder displays the Create TC/CI Terminal dialog box as above.
2. Select the terminal number, kind, and type and edit the default value in the
Create TC/CI Terminal dialog box.
3. Activate the Attributes button and select the attributes in the
Edit TC/CI Terminal Attributes dialog box as you need them for the graphical
presentation of the type circuit (circuit) at its instantiation (location).
4. Activate the OK or Apply button.

NOTE
The default value is optional. The default value will be connected as default
connection to the type circuit (circuit) at its instantiation (location).

Editing a TC/CI Terminal

1. Select the TC/CI Terminal Section window.
2. Choose the Edit | TC/CI Terminal command.
3. Modify the TC/CI terminal number, kind, type, and default value in the
Edit TC/CI Terminal dialog box.
4. Activate the Attributes button and select the attributes in the
Edit TC/CI Terminal Attributes dialog box, if you want to modify the graphical
presentation of the type circuit (circuit) at its instantiation (location).
5. Activate the OK or Apply button.

Deleting a TC/CI Terminal

1. Select the TC/CI Terminal Section window.
2. Select the TC/CI terminal, which you want to delete.
3. Choose the Edit | Delete command.

See also
Section 4.4.8.9, Use of TC/CI Terminals.

4.4.4.15 Print Out Documentation

Preparations
1. Be sure your printer is switched on, connected with the engineering station, possibly via a
computer network, and switched on-line.
2. Be sure the printer has the necessary amount of paper in its feeder.

4-138 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.4 Section-specific Programming Procedures

3. Be sure the paper has the appropriate format corresponding both your printer and the
layout of your documents.
See Section 4.4.2.9, Support of Display Adapters and Printers and Section 4.4.2.10, Specifying
Document Layout.

Selection of Document Parts

The Function Chart Builder offers documents of available sections, like
Database Listing, PC Diagram, Tree Listing, TC/CI Symbols, PC Cross Reference and
DB Cross Reference Listing.
The Function Chart Builder offers documents for general purposes, like
Modules, Circuit Usage, Options Listing.
The Function Chart Builder offers documents of certain DB elements, like DAT Cross
Reference, DPS Cross Reference, EVS Cross Reference, MDAT Cross Reference Listing.
For more information see Section 4.5.4.22, File | Print….

Printing Documents
1. Choose the File | Print command.
2. Select the documents in the Print dialog box.
3. Specify the selected documents and activate the OK button in the Print document_part
dialog boxes if applicable.
4. If needed, set print quality and select the Print to File check box in the Print dialog box.
5. Check and, if necessary, modify the printer setup by activating the Setup button.
6. Activate the OK button in the Print dialog.

Printing Function Chart in the PC Diagram

Remember, the function chart needs rather large area, especially for large PC elements, like
NOVATUNE, and for routing numerous and ramified connections.
When printing function chart in the PC Diagram document part, it is a good practice to select
Print Only on Success in the Page Layout Check group of the Print PC Section dialog box.
So the Function Chart Builder checks at first whether all pages of the PC Diagram can be
printed with the current layout.
If the layout check passes, the PC Diagram is printed.
If the layout check fails, the PC Diagram is not printed. Instead, the Function Chart Builder
opens the Output window and displays the list of pages with layout problems.
To repair them, either modify the page layout by the File | Page Setup command, for example,
increase the number of rows and columns, or insert page divisions on pages with too many
elements by the PC-Section | Page Layout | Insert Page Division command, or both.
You may use also the PC-Section | Page Layout | Check, Format, and
Generate Page Division commands to analyze and solve page layout problems.

3BDS 100 595R401 4-139

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Printing by Context Menu Commands of PC Section

If you click in the PC Section window with the right mouse button, you open the context menu.
You can use the following context menu commands for printing:
• In case of clicking in a pane with tree diagram, choose the Print This View context menu
command to print the Tree Listing.
• In case of clicking in a pane with function chart, choose the Print This Page context menu
command to print the currently shown function chart page (PC Diagram).

NOTE
Before printing by context menu commands, be sure the appropriate printer is
selected. In due case use the File | Print Setup command.

4.4.5 Procedures Concerning Source Code

4.4.5.1 Generate Source Code

Purpose
You generate source code for the following purposes:
• To download it by ONB to AC 400 Series controllers
• To export and import DB elements and PC programs from one node to another
• For backup reasons, that is, to store applications in a form that is valid throughout the
Function Chart Builder releases
• As intermediate step, to update ODB from one FCB version to another
• To store type circuits and circuits in a form that makes their use in other objects possible.

Generating Source Code

Choose one of the File | Generate Source commands depending on the object, on which you
are working.
The Function Chart Builder generates the source code on the basis of the internal data
representation of the object.
If you are working on an AC 400 Series or MasterPiece 200/1 node, the Function Chart Builder
generates also a *. CFX command file for dimensioning the data base by the On-line Builder.
See also the flow charts in Appendix B, Data Flow in Function Chart Builder.

4.4.5.2 Backtranslate Source Code to Internal Representation

Purpose
You backtranslate source code for the following purposes:
• To transfer applications, or parts of them, from other systems
• To regenerate applications programmed with earlier Function Chart Builder releases

4-140 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.5 Procedures Concerning Source Code

• To modify applications archived in source code form

• To disintegrate type circuit instances (in a node).

Preparations Before Backtranslation

1. Be sure you selected the appropriate node type and options for the object in the
Application Builder.
2. Be sure you started the Function Chart Builder for the object, for which you want to
backtranslate the source code.
3. Be sure the internal representation of the object is initialized.

Backtranslating Source Code

Choose one of the File | Backtranslate Source commands depending on the object, on which
you are working.
The Function Chart Builder generates the internal data representation of the object on the basis
of its source code. See also the flow charts in Appendix B, Data Flow in Function Chart Builder.

4.4.5.3 Source Code Transfer to/from AC 400 Series

To transfer source code to and from an Advant Controller 400 Series or MasterPiece 200/1
target, use the commands of the Application Builder and the On-line Builder. For more and
detailed information see the Application Builder User’s Guide and On-line Builder User’s
Guide. See also Figure B-1 in Appendix B, Data Flow in Function Chart Builder.

Converting Source Code Generated by the Function Chart Builder

1. It is supposed that the corresponding node is selected in the Application Builder and that
you have already generated source code for the node.
2. Choose the File | Convert menu command in the Application Builder.
3. Select the PC source files (*.AAX), the DB source files (*.BAX), command files for
dimensioning the data base (*.CFX), the type circuit information files (*.TIX and *.TBX)
as applicable.
Select the source files of type circuits (*.TCS), which are referenced in the PC and DB
source files you selected before.
The Application Builder converts the selected files from general representation to ABB Master
representation and assigns the file extensions AA, BA, CF, TI, TB, and TC, respectively.
The converted PC and DB source files are copied to \SRCE, the type circuit information and
source files are copied to \USER.

Loading Source Code to an AC 400 Series or a MP 200/1 Target

1. Start the On-line Builder to load the code files to the target.
2. Dimension DB corresponding to the needs of the volumes SRCE and USER.
3. Load to the target using the commands TRDBS and TRPCS.

3BDS 100 595R401 4-141

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Dumping Source Code from an AC 400 Series or a MP 200/1 Target

1. It is supposed that the corresponding node is selected in the Application Builder.
2. Start the On-line Builder to dump source code files from the target.
3. Dump from the target using the commands DUDBS and DUPCS.

Converting Source Code for the Function Chart Builder

1. Choose the File | Convert menu command in the Application Builder.
2. Select the PC source files (*.AA), the DB source files (*.BA), the type circuit information
files (*.TI and *.TB), and the source files of type circuits (*.TC) as applicable.
The Application Builder converts the selected files from ABB Master representation to general
representation and assigns the file extensions AAX, BAX, TIX, TBX, and TCS, respectively.
It copies the converted files to \PCDATA, \DBDATA, and \TCDATA directories, respectively.

4.4.5.4 Validation of PC Source Code

Purpose
You may edit source code of PC programs with a text editor, like AS100-EDIT, independently
of the Function Chart Builder.
You can check by the Function Chart Builder the following conditions:
• The source code corresponds to the AMPL syntax.
• The DB elements referenced in the PC programs exist.

Preparation
Be sure the following is fulfilled:
• The PC program to be validated pertains to the node selected in the Application Builder.
• Or, at least, the PC program to be validated pertains to a node that has the same node type,
version, and options as the selected node.

Checking
Choose the File | Check PC Source command.

4-142 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

4.4.6 On-line Programming Procedures

4.4.6.1 About On-line and Off-line Modes

Definition
Generally, you prepare an application for an AC 100 Series target system using the Function
Chart Builder off-line. Then, you connect the engineering station to the target and download the
target code of the application. The latter can be time consuming.
Now, you can test and edit the application running on the target by the Function Chart Builder
on-line. When editing on-line, you can change only one executable unit at a time. So, you have
to download only the changed part of the target code.
You may want to prepare a change limited to one executable unit off-line and disconnected from
the target, then connect and go on-line again and download only the difference to achieve a
bumpless modification of the running application on the target.
To support these procedures, four modes (states) are available. When the Function Chart
Builder works with the same AC 100 Series target system, it is any time in one of them:
• Off-line (non-connected)
• Off-line connected
• On-line (connected)
• On-line preparation.

NOTES
The on-line preparation mode is supported since Function Chart Builder
release 4.6.

If the Function Chart Builder works on an AC 400 Series node,

it is always in off-line (non-connected) mode.

Modes and Transitions - State Diagram

Follow the different possible modes (states) of the Function Chart Builder working on a given
AC 100 Series node in Figure 4-100.

Off-line (non-connected) Mode

The engineering station and the target system are not connected.
The application on the AC 100 Series target system and the corresponding node as seen by the
Function Chart Builder may be different, they are not synchronized.
When editing in this mode, you can change any number of executable units.
The following commands are available:
• Target | Connect to switch to off-line connected mode
• If the difference between the application on the target and the node is not more than one

3BDS 100 595R401 4-143

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

executable unit also File | On-line Preparation Mode to switch to on-line preparation
mode, in fact, to limit off-line editing to 1 executable unit.
The Connect command in the Target menu and the dimmed On-Line Preparation Mode
command in the File menu or the missing check mark ( ) before this command indicate this
mode.

NOTES
You work with the Function Chart Builder in this mode after start-up.

In this state you can use the Target | Connect command also to connect any other
AC 100 Series target system, for example, to identify it on the basis of its Status
Report and Options Report or to diagnose it.

4-144 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

On-line
(connected)

On-line Mode 9 On-line Mode Connect Disconnect

On-line
Off-line Preparation
connected (non-connected)

Connect Disconnect On-line Preparation Mode

9 On-line Preparation Mode

Legend:
Off-line
Mode : mode (state) (non-connected)
: available
9 ccc command
: transition on
command New state & commands
activation ( Start ) introduced with
: notice FCB release 4.6

Figure 4-100. FCB Modes (States) and Transitions

3BDS 100 595R401 4-145

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Off-line Connected Mode

The engineering station and the target system are connected.
The application on the AC 100 Series target system and the corresponding node as seen by the
Function Chart Builder may be different, they may be not synchronized.
When editing in this mode, you can change any number of executable units.
You download the target code of the whole application generally in this mode.
The following commands are available:
• Target | Disconnect to switch to off-line (non-connected) mode
• If there is a difference between the application on the target and the node, the
Target | Load Application can be used to download the target code and switch to on-line
mode immediately thereafter.
• If there is no difference between the application on the target and the node, also
File | On-line Mode to switch to on-line mode and edit and test the application on the
target on-line.
The Disconnect command in the Target menu and the dimmed On-Line Preparation Mode
command in the File menu or the missing check mark ( ) before the On-Line Mode
command in the File menu indicate this mode.

On-line Mode
The engineering station and the target system are on-line connected.
The application on the AC 100 Series target system and the corresponding node as seen by the
Function Chart Builder are the same, they are synchronized.
In this mode, you can test and edit the application on the target on-line.
When editing in this mode, you can change at most one executable unit.
The following commands are available:
• Target | Disconnect to switch to on-line preparation mode, in fact, to preserve the
limitation to one executable unit also during off-line editing
• File | On-line Mode to switch to off-line connected mode, in fact, to allow off-line editing
beyond the one executable unit limit.
The check mark ` ´before the On-Line Mode command in the File menu indicates this mode.

On-line Preparation Mode

The engineering station and the target system are not connected.
The application on the AC 100 Series target system differs from the corresponding node as seen
by the Function Chart Builder by not more than one executable unit.
When editing in this mode, you can change at most one executable unit.
The following commands are available:
• Target | Connect to switch to on-line mode
• File | On-line Preparation Mode to switch to off-line (non-connected) mode, in fact, to
allow off-line editing beyond the one executable unit limit.
The check mark ` ´before the On-Line Preparation Mode command in the File menu
indicates this mode.

4-146 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

NOTES
To reach this mode, the Function Chart Builder has to have passed the on-line
mode at least once with this application.

In this state you can use the Target | Connect command also to connect any other
target system, for example, to identify it on the basis of its Status Report and
Options Report or to diagnose it. Then also the Target | Disconnect command is
available. The on-line preparation mode regains its meaning only when you
reconnect the same target system, with which you worked in on-line mode.

Transitions

Table 4-10. FCB Mode (State) Transitions

Transition Command to Trigger the Transition

Off-line (non-connected) Mode ---> Off-line Connected Mode Target | Connect
Off-line Connected Mode ---> Off-line (non-connected) Mode Target | Disconnect
Off-line Connected Mode ---> On-line Mode File | On-line Mode or Target | Load Application
On-line Mode ---> Off-line Connected Mode File | On-line Mode
On-line Mode ---> On-line Preparation Mode Target | Disconnect
On-line Preparation Mode ---> On-line Mode Target | Connect concerning the same target
On-line Preparation Mode ---> Off-line (non-connected) Mode File | On-line Preparation Mode
Off-line (non-connected) Mode ---> On-line Preparation Mode File | On-line Preparation Mode

See also
Section 4.4.6.13, Edit an AC 100 Series Application On-line.

4.4.6.2 Preparation of Target Code

Purpose
To generate target code, that is, a data format directly loadable to AC 100 Series target, from the
application data. The target code has to fulfill several requirements concerning RAM, PROM,
and code and data area.
In case of AC 100 Series nodes supporting application retrieval (upload and backtranslation of
target code), the Function Chart Builder can generate also additional, complete information for
storing in and later retrieval from the target. See Section 4.4.6.15, Retrieve Application from an
AC 100 Series Target.
During target code generation or at on-line changes, and if the corresponding check box is
selected, the Function Chart Builder fills also the Bus Configuration Database and generates
BOIL*.C00 and COIL*.C00 files to support Human-System Interfaces and to facilitate access
of process signals in AC 100 Series targets connected to Advant Fieldbus 100.
See Bus Configuration Builder User’s Guide.

3BDS 100 595R401 4-147

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Procedure
1. Generate target code by the File | Generate Target Code command.
The Function Chart Builder opens the Output window and protocols the target code
generation here and also in the \DBDATA\COTL0000.C00 and \PCDATA\RETL0000.Cpp
files (where pp = PC program number).
2. Evaluate the target code generation protocol.
a. Check the lines “w Warnings detected” and “e Errors detected” in
both sections (files).
w>0 indicates violation of programming conventions, for example, the case when
input connections are left unconnected.
e>0 indicates violation of normal execution conditions on the target, for example,
missing necessary DB elements or exhaustion of resources (RAM, PROM, and code
and data area).
b. In case of exhaustion of resources identify the violated requirement and the section(s)
and the executable unit(s) responsible for the violation.
The estimated values of memory requirements delivered by the PC-Section |
Memory Calculation | … commands are also helpful.
3. If errors, warnings, or both occurred, change your application accordingly.
That is, create the missing DB elements, restructure your application to decrease resource
demand, connect open input PC terminals, and so on.
Then repeat the procedure from Step 1.

Memory Requirements on the Target

1. Sum of PROM required by sections of the application must be less than the free PROM on
the target.
required_PROM = DB_section_PROM + PC_section_PROM
(This also equals sum_DB_section_CODE + sum_PC_section_CODE.)
Find free PROM in the Technical Description of the corresponding Advant Controller.
2. Sum of RAM required by sections of the application must be less than the free RAM on
the target.
required_RAM = DB_section_RAM + PC_section_RAM
(This also equals sum_DB_section_CODE + sum_PC_section_CODE +
+ sum_DB_section_DATA + sum_PC_section_DATA.)
To check free RAM choose Target | Clear PROM, then Target | Restart.
Find free RAM in the Free Memory row of the (last) Status Report.
3. Sum of code of each code domain must be less than 64 kBytes.
The code domains are denoted by CODE: in the target code generation protocol.
In case of application retrieval support also Complete Info xxx domains may be
generated. With respect to memory requirements, they count as code domains.

4-148 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

4. Sum of data area of each data domain must be less than the maximum indicated at the end
of corresponding lines in the target code generation protocol.
The maximum length of data domains is normally 32 kBytes. But in some cases it is
8 kBytes, for example, in case of PARDAT elements for AC 110 2.1.
The data domains are denoted by DATA: in the target code generation protocol.

Example of Target Code Generation Protocol

Start of generating target code for a data

domain, a code domain, or both.

The processed DB elements for a code

domain, a data domain, or both.

Information about a code domain of the

generated target code. The code length of
the previously listed elements or unit is
summed and rounded to the next multiple
of 256. The maximum allowed length of
the domain is indicated at the end of line.

Information about a data domain of the

generated target code. The local data
length of the previously listed elements
or unit is summed and rounded to the
next multiple of 256. The maximum
allowed length is at the end of line.

CODE and DATA show the sum of the

code and data domains of the given
section, respectively. Both the code and
data domains are loaded at first into
RAM: RAM = CODE + DATA
The downloaded code can be copied to
PROM: PROM = CODE

Number of warnings and errors occurred

during processing of a section.
Number of errors must be 0 for
successful target code generation.

Figure 4-101. Target Code Generation Protocol (Example)

3BDS 100 595R401 4-149

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTES
In case of executable unit code domains a further 256 bytes are added for internal
code to code length. The length of data exchange internal code is 256 bytes.
The local data length of data exchange between executable units depends on the
number and data type of these connections.
The values delivered by the PC-Section | Memory Calculation | … commands
do not comprise these code and data lengths.

4.4.6.3 About Target Connection

Purpose
To connect the engineering station to an AC 100 Series target.

Definition
You connect the engineering station to an AC 100 Series target mainly in two ways:
• Directly
• By routing via other AC 100 Series or AC 400 Series nodes of a network.

NOTE
Different AC 100 Series node types support different cases of routing.

The engineering station to be connected can be the local one, on which you run the application
requesting the connection, such as the Function Chart Builder or the Diagnostics program, but
also another remote one, a server, connected to a common computer network. Then your local
engineering station (“this PC”) is client of the connection service available on the server.

Conditions of Successful Connection

1. The connection service is available either on the local engineering station or on a server
connected to a common computer network, which you intend to use.
For conditions of successful server operation and instructions for the Windows NT system
administrators see Appendix G, Configuration of AdvaBuild Communicator.
2. If an engineering board is involved in the routing, the On-line Builder must be installed on
the pertaining engineering station and the engineering board must be configured
appropriately by the Engineering Board Setup program. See On-line Builder User’s Guide,
Chapter 2, Installation.
3. The engineering station(s), the involved nodes along the routing path, and the target are
cabled appropriately.
4. Applications, loaded to the nodes along the routing path, are configured to support the
communication via MB 300, AF 100, and RCOM net, as applicable.
5. The connection path is defined appropriately in the Connect dialog of the
Target | Connect command.

See also
Section 4.4.6.6, Routing Possibilities Depending on Node Type and Section 4.4.6.5, Types of
Routing, Diagrams to decide type of connection and Section 4.4.6.4, Connect the Engineering
Station to an AC 100 Series Target to prepare and establish the connection.

4-150 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

4.4.6.4 Connect the Engineering Station to an AC 100 Series Target

Preparation of Engineering Station
If you want to use the connection service running on a remote engineering station, it has to be
accessible via computer network from your local engineering station.
See Appendix G, Configuration of AdvaBuild Communicator for configuration of engineering
station - target communication on server.

Preparation of Links
In case of point-to-point RS 232C connection do the following:
Connect one end of an appropriate cable to the connector, generally denoted by CH1 or
CHANNEL 1, of the AC 100 Series target and the other end to a free connector COM1,
COM2, … of serial interface of the engineering station.
In case of connection by routing via other nodes and if the first node in the routing path is an
AC 100 Series node, do the following:
1. Connect one end of an appropriate cable to the connector, generally denoted by CH1 or
CHANNEL 1, of the first AC 100 Series node in the routing path and the other end to a
free connector COM1, COM2, … of serial interface of the engineering station.
2. Be sure the nodes up to the target are cabled appropriately to realize the AF 100
communication paths.
In case of connection by routing via other nodes and if the first node in the routing path is an
AC 400 Series node, do the following:
1. Be sure the appropriate AS 100 Series Engineering Board is installed correctly in the
engineering station and configured appropriately by the Engineering Board Setup
program. Choose the latter in the Start | Advant | Engineering | Utilities menu.
(The Engineering Board Setup program is installed together with the On-line-Builder,
see also On-line Builder User’s Guide, Chapter 2, Installation.)
2. Connect one end of an appropriate cable to the connector, generally denoted by SERVICE,
of the first AC 400 Series node in the routing path and the other end to the connector X3 of
the AS 100 Series Engineering Board of the engineering station.
3. Be sure the nodes up to the target are cabled appropriately to realize the necessary
MB 300, AF 100, and RCOM communication paths.
In case of direct AF 100 connection via the AF 100 interface of the engineering station, do the
following:
1. Be sure the AF 100 Interface, for example, the CI526 communication interface module
and the AF 100 Interface software, is installed correctly on the engineering station. AF 100
Interface 1.0/* and Advant OPC Server for AF 100 1.0/0 require administrator privileges.
2. Be sure the target is cabled appropriately to realize the AF 100 communication.

Preparation of Intermediate Nodes

In case of connection by routing via other nodes be sure appropriate application programs are
loaded to the nodes along the routing path that configure them to support the communication via
MB 300, AF 100, and RCOM net and to manifest the appropriate addresses.

3BDS 100 595R401 4-151

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Connection
1. Choose the Target | Connect command.
The Function Chart Builder displays the Connect dialog box.
2. In case of simple and repeated connections select the appropriate connection path in the
connection history contained in the Connection Path drop-down list box without
bothering about details.
Or, in case of complex paths and new connections, activate the Connect Assistant by the
Assistant button.
The Connect Assistant guides you through steps of connection path definition:
a. Define the server, that is, the engineering station offering the connection service.
This can be “this PC” but also some other PC accessible via a computer network.
To select a remote server, you have three possible ways:
• Activate the Browse button and find a server in your computer network.
• Select one of the recently used servers in the Selected server PC
drop-down list box.
• Enter a server directly in Selected server PC text box.
You can do the latter in different forms, like
- Name corresponding to universal naming convention (UNC),
for example, \\gpa789 or gpa789
- TCP-IP address, for example, 123.456.789.87
- Distributed server name (DSN) like a world-wide-web address,
for example, www.abb.de or deind.de.
Select also the server's interface or port to be used.
b. Define the target by its AF 100 or RCOM address if it has one.
The address has to correspond to the setting by appropriate DB elements of the
application running on the target.
An AF 100 address consists of bus number, station number, and position.
An RCOM address consists of remote net number, remote node number, and position.
In case of point-to-point COMx connection, there is no need to define the address
explicitly.
c. Define the intermediate nodes, if there are any, by their MB 300 or AF 100 address.
The address has to correspond to the setting by appropriate DB elements of the
application running on the intermediate node.
An MB 300 address consists of net number and node number.
An AF 100 address consists of bus number, station number, and position.
In case of point-to-point X3 connection, there is no need to define the address
explicitly.
d. Return to the Connect dialog.
3. Activate the OK button.
The connection will be established. It may take some seconds.
The the Function Chart Builder requesting the connection can continue. It displays the
Status Report and the Options Report about the connected target.

4-152 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

Suggested Next Steps

1. If the Function Chart Builder has been in on-line preparation mode, the Function Chart
Builder switches automatically to on-line mode. If the loaded application program differs
from the one saved in the internal data representation exactly by one executable unit, you
can update the application on the target by the File | Save and Load command.
See Section 4.4.6.1, About On-line and Off-line Modes.
2. If the Function Chart Builder has been in off-line (non-connected) mode, it switches
automatically to off-line connected mode. You can download a new application or a new
version of it. See Section 4.4.6.8, Load Application to an AC 100 Series Target.
3. In on-line mode, you can monitor and force terminals and edit the application on-line.
See Section 4.4.6.9, Display (Monitor) PC Terminals in AC 100 Series Target to
Section 4.4.6.13, Edit an AC 100 Series Application On-line.
4. You can diagnose the target.
See Section 4.4.7.1, Diagnostic Procedures with the Diagnostics Program and
Section 4.4.7.2, Diagnostic Procedures with the Diagnosis Program.
5. Or just disconnect the target by the Target | Disconnect command.

4.4.6.5 Types of Routing, Diagrams

The following types of routing are supported:
1. Point-to-point connection via COMx (no routing)
2. Routing via COMx
a. Routing via COMx, AC 100 Series Node, AF 100
b. Routing via COMx, AC 100 Series Node, AF 100, 2nd AC 100 Series Node,
2nd AF 100.
3. Routing via X3
a. Routing via X3, AC 4xx, AF 100
b. Routing via X3, AC 4xx, AF 100, AC 100 Series Node, 2nd AF 100
c. Routing via X3, AC 4xx, RCOM Net
d. Routing via X3, Several AC 4xx Connected by MB 300, AF 100
e. Routing via X3, Several AC 4xx Connected by MB 300, AF 100,
AC 100 Series Node, 2nd AF 100
f. Routing via X3, Several AC 4xx Connected by MB 300, RCOM Net.
4. Direct Connection via AF 100 (no routing)
See the topology of routing with exemplary addresses for each type of routing in the following.
The pertaining settings of connection path in the Connect dialog of the Target | Connect
command refer
• Target Name
Is set on the basis of the status information fetched from the target after a successful
connection.

3BDS 100 595R401 4-153

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Server
The empty string ('') and “This PC” denotes your local engineering station you work on.
If you want to use the connection service running on a remote engineering station, you can
set it with the help of the Connect Assistant.
• PC Interface
This is the interface of the server towards the routing network (in case of routing) or
towards the target (in case of direct connection).
Examples: COM1, COM4, X3, AF100IF.
• Intermediate Node Address
This is the identification of the intermediate node.
In case of point-to-point (direct) connection it is omitted.
In other cases the intermediate node is identified by the kind of bus it is reached and by its
address on this bus.
Examples of address form: AF100[bus, station, position],
MB300[net, node], RCOM[rnet, rnode, position].
In the Connect Assistant, Position of the intermediate node is preset originally to 0.
Set the appropriate value according to the configuration of the corresponding
AC 100 Series station:

Table 4-11. Position of Intermediate Nodes

Node Type Position

AC 110 1
AC 70 0
AC 160 (station with CPU redundancy) 3, 4,… 8

• Target Address
This is the identification of the target.
In case of point-to-point (direct) connection it is omitted. In other cases the target is
identified by the kind of bus it is reached and by its address on this bus.
Examples of address form: AF100[bus, station, position],
RCOM[rnet, rnode, position].
In the Connect Assistant, Position of the target is preset on the basis of the corresponding
value for the target in the Application Builder.

Table 4-12. Position of Target

Node Type Position

AC 110 1
AC 55 0
AC 70 0
AC 160 (station with 3, 4,… 8
CPU redundancy)

4-154 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

Point-to-point Connection via COMx

Topology of connection with exemplary addresses:

Figure 4-102. Point-to-point Connection via COMx, Topology

Detail of Connect dialog with corresponding setting:

Figure 4-103. Point-to-point Connection via COMx, Setting

Routing via COMx, AC 100 Series Node, AF 100

Topology of connection with exemplary addresses:

Figure 4-104. Routing via COMx, AC 100 Series Node, AF 100, Topology

Detail of Connect dialog with corresponding setting:

3BDS 100 595R401 4-155

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-105. Routing via COMx, AC 100 Series Node, AF 100, Setting

Routing via COMx, AC 100 Series Node, AF 100, 2nd AC 100 Series, 2nd AF 100
Topology of connection with exemplary addresses:

Figure 4-106. Routing via COMx, AC 100 Series, AF 100, 2nd AC 100 Series, 2nd AF 100,
Topology

Detail of Connect dialog with corresponding setting:

Figure 4-107. Routing via COMx, AC 100 Series, AF 100, 2nd AC 100 Series, 2nd AF 100,
Setting

4-156 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

Routing via X3, AC 4xx, AF 100

Topology of connection with exemplary addresses:

Figure 4-108. Routing via X3, AC 4xx, AF 100, Topology

Detail of Connect dialog with corresponding setting:

Figure 4-109. Routing via X3, AC 4xx, AF 100, Setting

Routing via X3, AC 4xx, AF 100, AC 100 Series Node, 2nd AF 100
Topology of connection with exemplary addresses:

Figure 4-110. Routing via X3, AC 4xx, AF 100, AC 100 Series Node, 2nd AF 100, Topology

Detail of Connect dialog with corresponding setting:

3BDS 100 595R401 4-157

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-111. Routing via X3, AC 4xx, AF 100, AC 100 Series Node, 2nd AF 100, Setting

Routing via X3, AC 4xx, RCOM Net

Topology of connection with exemplary addresses:

Figure 4-112. Routing via X3, AC 4xx, RCOM Net, Topology

Detail of Connect dialog with corresponding setting:

Figure 4-113. Routing via X3, AC 4xx, RCOM Net, Setting

4-158 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

Routing via X3, Several AC 4xx Connected by MB 300, AF 100

Topology of connection with exemplary addresses:

Figure 4-114. Routing via X3, Several AC 4xx Connected by MB 300, AF 100, Topology

Detail of Connect dialog with corresponding setting:

Figure 4-115. Routing via X3, Several AC 4xx Connected by MB 300, AF 100, Setting

Routing via X3, Several AC 4xx Connected by MB 300, AF 100, AC 100 Series
Node, 2nd AF 100
Topology of connection with exemplary addresses:

Figure 4-116. Routing via X3, Several AC 4xx Connected by MB 300, AF 100, AC 100 Series Node, 2nd AF 100, Topology

Detail of Connect dialog with corresponding setting:

3BDS 100 595R401 4-159

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-117. Routing via X3, Several AC 4xx Connected by MB 300, AF 100, AC 100 Series
Node, 2nd AF 100, Setting

Routing via X3, Several AC 4xx Connected by MB 300, RCOM Net

Topology of connection with exemplary addresses:

Figure 4-118. Routing via X3, Several AC 4xx Connected by MB 300, RCOM Net, Topology

Detail of Connect dialog corresponding setting:

Figure 4-119. Routing via X3, Several AC 4xx Connected by MB 300, RCOM Net, Setting

4-160 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

Direct Connection via AF 100

Topology of connection with exemplary addresses:

Figure 4-120. Routing via AF 100, Topology

Detail of Connect dialog with corresponding setting:

Figure 4-121. Routing via AF 100, Setting

4.4.6.6 Routing Possibilities Depending on Node Type

The following table summarizes the routing possibilities depending on the node type of the
target and, if applicable, on the intermediate node, to which the server engineering station is
connected.

3BDS 100 595R401 4-161

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Table 4-13. Routing Possibilities Depending on Node Type

Eng. Station Routed via AC 110 or AC 160

AC 70 Target AC 55 Target
Interface 1st Node Target
COMx No routing; no + + +
intermediate node.
COMx AC 110 or AC 160 AF100, AF100, -
AF100+AF100 AF100+AF100
COMx AC 70 AF100 AF100 -
COMx AC 55 - - -
X3 AC 400 Series, AF100, AF100, RCOM net,
then AC 110 or AF100+AF100, AF100+AF100, MB300+RCOM net
AC 160 as MB300+AF100, MB300+AF100,
applicable MB300+AF100+AF100, MB300+AF100+AF100
RCOM net,
MB300+RCOM net
AF 100 * No routing; no + + -
intermediate node.
Other, such as No routing; no - - -
PCMCIA, ISA, … intermediate node.

Legend:
* The engineering station has to be additionally equipped with hardware and
software necessary for AF 100 interface, that is, with a communication
interface such as CI526 and with the AF 100 Interface software installed as a
separate component or as part of, for example, AF100 OPC.
+ Direct connection is supported.
- No routing is supported.
1bus Routing path is
engineering station --> comm. port --> 1st intermediate node --> 1bus -->
--> target.
1bus+2bus Routing path is
engineering station --> comm. port --> 1st intermediate node --> 1bus -->
--> 2nd intermediate node --> 2bus --> target.
1bus+2bus+3bus Routing path is
engineering station --> X3 --> 1st intermediate AC 400 Series node -->
--> 1bus --> last intermediate AC 400 Series node --> 2bus -->
--> intermediate AC 110 or AC 160 node --> 3bus --> target.
Comma Separates possible routing paths.
Routing possibilities of AC 80 are typically the same as those of AC 70.

4-162 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

4.4.6.7 Target Access Protection

NOTE
These functions are available only for targets, the base software of which supports
target access protection. Such node types are, for example, AC 110 2.3,
AC 160 1.2, and AC 166 1.0.

The Function Chart Builder offers three different target access protection functions:
1. Target password protection from manipulations of the application program by
unauthorized persons
In fact, the connection to a target with a certain application program running on it is
protected by the target password.
2. Application program checksum
You can inspect and store the checksum (CRC) of the application program running in the
RAM and inspect the checksum of the system in target PROM.
These checksums can be inspected later again and be compared with stored values.
If they are not equal, the application has been changed in the meantime.
3. Restriction of network programming
You can allow or forbid programming of a target by routing via an AF 100 network.

Target Password Protection

1. At cold start of the target or stop target the initial target password is empty and the
connection to the target is not protected.
2. You can define a target password by the Target | Set Password command if the target is
connected.

Figure 4-122. Set Initial Password on Target

Enter here the password in the New Password and Confirm New Password text boxes.
The password has to consist of 8 to 50 printable characters, it is case sensitive.
On activating the OK button the new password is saved in the target RAM.

3BDS 100 595R401 4-163

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

CAUTION
Use password protection only if it is reasonable.
Be aware, if you forget the password, there is no “universal password”, you can
just stop the target to clear the password.
A warm start does not clear the password.

3. After that, each time you—or any other user—connect to this target, the Function Chart
Builder prompts to enter the password associated with the target.

Figure 4-123. Target Password Query at Target Connection

If you enter the correct password, the Function Chart Builder connects to the target and
offers its on-line testing and editing. You can test and edit the application stored in the
target.
If you enter an incorrect password, the Function Chart Builder refuses the connection.
You can neither test nor edit the application program stored in target, just try to enter the
correct password again.
4. You can change or clear the target password by the Target | Set Password command if the
target is connected.
In these cases you have to enter at first the old password:

Figure 4-124. Change Password on Target

4-164 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

You clear the password by the empty string as new password:

Figure 4-125. Clear Password on Target

5. The target password is implicitly cleared at stopping the target by reset button and no start
position of the stop mode switch.
Together with the application program in the target RAM, the target password, if there is
any, is implicitly copied to the target PROM
The target password is implicitly taken from the target PROM at cold start of the target by
reset button and cold start position of the stop mode switch.

NOTE
Do not mix up the target password with the ODB password.
See Section 4.4.2.6, Password Protection of Nodes, TCs, CIs.

Nevertheless, if the ODB password equals the target password, you do not need to
enter the same password again when connecting to the target.

Application Program Checksum

Use the Target | Application Checksum command to
• Inspect the actual CRC of the application in the target RAM, the stored CRC, and date and
time of CRC storage, and the CRC of the system in target PROM
• Store the application checksum (CRC) in the target RAM.

NOTE
You can access these three CRC values also by an appropriate PC element and use
them to check integrity or change of your application program and PROM
contents.

3BDS 100 595R401 4-165

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Remote Access Protection - Restriction of Network Programming

To restrict remote accessing and programming of targets by routing via MB 300, AF100, and
RCOM networks, the DB elements of processor modules PMnnn of appropriate nodes offer the
terminal NETACC.
If you program NETACC=1 (default), the target can be connected and programmed also
remotely, by routing via MB 300, AF100, and RCOM networks.
If you program NETACC=0, the target can only be connected point-to-point via COMx and
programmed directly. When the inadvertent user tries to connect the target remotely, the
Function Chart Builder refuses the connection and shows the following warning message:

“This target is protected from being connected via the control

network.
You can only connect directly to the target using port COMx.”

4.4.6.8 Load Application to an AC 100 Series Target

Purpose
To load PC programs and data base to an AC 100 Series target.

Preparation Off-line
Generate target code for the PC program and the data base by File | Generate Target Code.

Preparation On-line
1. Connect the Function Chart Builder on-line to the AC 100 Series target by the Target |
Connect command.
The Function Chart Builder displays the Status Report and the Options Report window.
In the following, if necessary, choose the Target | Report commands to reopen or update
the … Report windows.
2. If there are errors reported in the Status Report, check and clear them by the Diagnostics
(Diagnosis) program. For that choose the Target | Diagnostics command.
3. Check the options and the base software in the Options Report for conditions of
successful target code download:
a. The base software and all the options selected in the engineering station must be
available in the on-line connected target.
b. The ident_string, major_release, and minor_release of the item selected in the
engineering station must equal the ident_string, major_release, and minor_release of
the corresponding item on the target.
That means revision is not evaluated.
4. Check PCPGM State in the Status Report.
If the PC program is deblocked, choose the Target | Block Program command to stop it.

Loading Target Code to the Target

1. Choose the Target | Load Application command to load the generated target code
from the engineering station.

4-166 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

After successful download the Function Chart Builder offers switching to on-line mode.
Generally, you accept it and quit the warning.
The Function Chart Builder opens the Output window. You can check here the download
process.
2. The Function Chart Builder updates the Status Report of the connected target.
Check if there are some recent errors in the Status Report. You can analyze them by the
Diagnostics (Diagnosis) program. For that choose the Target | Diagnostics command.

Suggested Next Steps

1. If the download is successful, you can start the execution of the new application in the
AC 100 Series target by the Target | Deblock Program command.
2. In on-line mode, you can also monitor and force terminals in the target and edit the
application on-line. See Section 4.4.6.9, Display (Monitor) PC Terminals in AC 100 Series
Target to Section 4.4.6.11, Display and Force DB Terminals in AC 100 Series Target and
Section 4.4.6.13, Edit an AC 100 Series Application On-line.
3. Or just disconnect the target by the Target | Disconnect command. If the Function Chart
Builder has been in on-line mode, it switches to on-line preparation mode.

4.4.6.9 Display (Monitor) PC Terminals in AC 100 Series Target

Purpose
To monitor selected PC terminals in an AC 100 Series target on-line.
The Function Chart Builder offers monitoring and forcing of PC and DB terminals and unified
presentation of the values in the Test Table window.
PC terminals can be prepared and the values can be presented also in PC Section window panes
with the function chart.

Preparation Off-line (Optional)

1. Select the PC Section window pane with the function chart.
Generally, the Function Chart Builder is in on-line preparation mode.
2. Select the PC terminals for monitoring, then choose the PC-Terminal | Select for Display
| Select command or unselect them by the PC-Terminal | Select for Display | Unselect
command. Choose the View | Prepared Variables command to see the PC terminals,
which are already selected for monitoring.
The Function Chart Builder marks the PC terminals selected for monitoring by asterisks
‘*’ in the function chart.
3. Select the Test Table window by the Window | Test Table command.
Set its Signal Select Filter appropriately.
Resize the columns of the Test Table window by dragging the divisions that separate the
header parts Instance, Terminal, and so on, to overview and check the terminals selected
for monitoring. Some divisions may be visible only if you enlarge the window.
You can also select and unselect terminals directly in the Test Table window.

3BDS 100 595R401 4-167

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTE
The Function Chart Builder saves the contents of the Test Table in the internal
data representation of the node if you choose the File | Save or
File | Save and Load or File | Exit command (the latter with saving the changes).
At the beginning of a new session the Function Chart Builder restores also the
Test Table from the internal data representation with the contents recently saved.

Preparation On-line
1. Connect the Function Chart Builder on-line to the AC 100 Series target by the
Target | Connect command. If the Function Chart Builder has been in on-line preparation
mode—and generally this is the case—, it switches to on-line mode.
The Function Chart Builder displays the Status Report and the Options Report window.
In the following, if necessary, choose the Target | Report commands to reopen or update
the … Report windows.
2. If there are errors reported in the Status Report, you can check and clear them by the
Diagnostics (Diagnosis) program. For that choose the Target | Diagnostics command.
3. If the Function Chart Builder is not in on-line mode
a. You can check the options and the base software in the Options Report for
conditions of successful target code download.
b. You can check that the data in the Node on AS 100ES column of the Status Report
equal those in the Target RAM column.
If the checks are successful, switch to on-line mode explicitly by the File | On-line Mode
command.
Otherwise you have to ensure correct base software and options and reload the application
to allow switching to on-line mode. See Section 4.4.6.8, Load Application to an
AC 100 Series Target.
4. You select and unselect PC terminals for monitoring in the same way in on-line mode as
you do it in on-line preparation mode (or in off-line mode).

Monitoring PC Terminal Values on the Target

1. To display the PC terminal values, select the PC Section window pane with the function
chart. Or to display the PC and also DB terminal values, select the Test Table window by
the Window | Test Table command.
2. Update the Status Report by the Target | Report Status command.
Check PCPGM State in the Status Report. If the PC program is blocked, choose the
Target | Deblock Program command to deblock it.
3. Update the display values for PC and also DB terminals by the Test | Single Display or
Test | Cyclic Display command.
Or activate the Single or the Cyclic button in the Display group of the Test Table window.
Be sure all the conditions were fulfilled during the on-line preparation.
Or activate the Recording button to record the values of selected terminals as trend.
The Function Chart Builder displays the monitored values on the connection line near the
PC terminals in the function chart and the monitored PC and also DB values in the
Test Table window. Or it shows the recorded trend.

4-168 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

NOTE
If the Function Chart Builder displays ‘X’ as value, the PC program
is blocked yet. Deblock it as suggested in Step 2.

4. Stop cyclic monitoring by the Test | Stop Display command.

You can also use the Test | Set Trigger command to define the condition, at the occurrence
of which cyclic monitoring stops automatically.

Suggested Next Steps

1. You can also monitor DB terminals and force PC and DB terminals in the target,
see Section 4.4.6.11, Display and Force DB Terminals in AC 100 Series Target and
Section 4.4.6.10, Force PC Terminals in AC 100 Series Target.
2. If no terminals are monitored cyclically or forces, you can edit the application on-line.
See Section 4.4.6.13, Edit an AC 100 Series Application On-line.
3. Or disconnect the target by the Target | Disconnect command.
The Function Chart Builder changes to on-line preparation mode.

4.4.6.10 Force PC Terminals in AC 100 Series Target

Purpose
To force selected PC terminals in an AC 100 Series target on-line.
The Function Chart Builder offers monitoring and forcing of PC and DB terminals and unified
presentation of the values in the Test Table window.
PC terminals can be prepared and the values can be presented also in PC Section window panes
with the function chart.

Preparation Off-line (Optional)

1. Select the PC Section window pane with the function chart.
Generally, the Function Chart Builder is in on-line preparation mode.
2. Select the PC terminals for forcing by the PC-Terminal | Force Value | Create/Edit
command or unselect them by the PC-Terminal | Force Value | Delete command.
Choose the View | Prepared Variables command to see the PC terminals, which are
already selected for forcing.
The Function Chart Builder marks the PC terminals selected for forcing by asterisks ‘*’ in
the function chart.
3. Select the Test Table window by the Window | Test Table command.
Set its Signal Select Filter appropriately.
Resize the columns of the Test Table window by dragging the divisions that separate the
header parts Instance, Terminal, and so on, to overview and check the terminals selected
for forcing. Some divisions may be visible only if you enlarge the window.
You can also select and unselect terminals directly in the Test Table window.

3BDS 100 595R401 4-169

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTE
The Function Chart Builder saves the contents of the Test Table in the internal
data representation of the node if you choose the File | Save or
File | Save and Load or File | Exit command (the latter with saving the changes).
At the beginning of a new session the Function Chart Builder restores also the
Test Table from the internal data representation with the contents recently saved.

Preparation On-line
1. Connect the Function Chart Builder on-line to the AC 100 Series target by the
Target | Connect command. If the Function Chart Builder has been in on-line preparation
mode—and generally this is the case—, it switches to on-line mode.
The Function Chart Builder displays the Status Report and the Options Report window.
In the following, if necessary, choose the Target | Report commands to reopen or update
the … Report windows.
2. If there are errors reported in the Status Report, you can check and clear them by the
Diagnostics (Diagnosis) program. For that choose the Target | Diagnostics command.
3. If the Function Chart Builder is not in on-line mode
a. You can check the options and the base software in the Options Report for
conditions of successful target code download.
b. You can check that the data in the Node on AS 100ES column of the Status Report
equal those in the Target RAM column.
If the checks are successful, switch to on-line mode explicitly by the File | On-line Mode
command.
Otherwise you have to ensure correct base software and options and reload the application
to allow switching to on-line mode. See Section 4.4.6.8, Load Application to an
AC 100 Series Target.
4. You select and unselect PC terminals for forcing in the same way in on-line mode as you
do it in on-line preparation mode (or in off-line mode).
Compare the Value on Target and the Force Value columns of the Test Table to see
which force values are effective and which are only prepared or no more prepared.

Forcing Terminal Values on the Target

1. To force the PC terminal values, select the PC Section window pane with the function
chart. Or, to force the PC and also DB terminal values, select the Test Table window by
the Window | Test Table command.
2. Update the Status Report by the Target | Report Status command.
Check PCPGM State in the Status Report. If the PC program is blocked, choose the
Target | Deblock Program command to deblock it.
3. Force all prepared values for PC and also DB terminals on the target by the Test | Activate
All Force Values command.
Or select some items in the list box of the Test Table window and force them on the target
by the Test | Activate Force Values command. You can also activate the appropriate check
box and button in the Force group of the Test Table window.
Be sure all the conditions were fulfilled during the on-line preparation.

4-170 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

The Function Chart Builder displays the force values on the connection line near the PC
terminals in the function chart and updates them in the Value on Target column of the
Test Table.

Suggested Next Steps

1. You can also monitor PC and DB terminals and force DB terminals in the target,
see Section 4.4.6.9, Display (Monitor) PC Terminals in AC 100 Series Target and Section
4.4.6.11, Display and Force DB Terminals in AC 100 Series Target.
2. Stop forcing of items selected in the Test Table by the Test | Deactivate Force Values
command.
Stop forcing all PC and DB terminals by the Test | Deactivate All Force Values
command.
3. If no terminals are monitored cyclically or forced, you can edit the application on-line.
See Edit an AC 100 Series Application On-line.See Section 4.4.6.13, Edit an
AC 100 Series Application On-line.
4. Or disconnect the target by the Target | Disconnect command.
The Function Chart Builder changes to on-line preparation mode.

CAUTION
If you disconnect the target, forcing of all PC terminals is deactivated in contrast
to DB terminals.

4.4.6.11 Display and Force DB Terminals in AC 100 Series Target

Purpose
To monitor and force selected DB terminals in an AC 100 Series target on-line.
The Function Chart Builder offers monitoring and forcing of PC and DB terminals and unified
presentation of the values in the Test Table window.

NOTES
Forcing DB terminals is supported only by extended DB elements that are
available, for example, for AC110 version 2.1 and higher.

Forcing DB terminals is supported by the Function Chart Builder only from its
version 4.3/0 on.

You can prepare force values only for the VALUE terminals of extended
DB elements.

Preparation Off-line (Optional)

1. Select the DB Section window for orientation and as reference.
Generally, the Function Chart Builder is in on-line preparation mode.

3BDS 100 595R401 4-171

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

2. Select the Test Table window by the Window | Test Table command. Set its Signal Select
Filter appropriately.
Resize the columns of the Test Table window by dragging the divisions that separate the
header parts Instance, Terminal, and so on, to overview and check the terminals selected
for monitoring or forcing. Some divisions may be visible only if you enlarge the window.
3. Select the DB terminals for monitoring or forcing by activating the Create/Edit… button
in the List Entry group of the Test Table.
The Function Chart Builder lists the DB terminals selected for monitoring or forcing and
the corresponding values in the list box of the Test Table.

NOTE
The Function Chart Builder saves the contents of the Test Table in the internal
data representation of the node if you choose the File | Save or File | Save and
Load or File | Exit command (the latter with saving the changes).
At the beginning of a new session the Function Chart Builder restores also the
Test Table from the internal data representation with the contents recently saved.

Preparation On-line
1. Connect the Function Chart Builder on-line to the AC 100 Series target by the
Target | Connect command. If the Function Chart Builder has been in on-line preparation
mode—and generally this is the case—, it switches to on-line mode.
The Function Chart Builder displays the Status Report and the Options Report window.
In the following, if necessary, choose the Target | Report commands to reopen or update
the … Report windows.
2. If there are errors reported in the Status Report, you can check and clear them by the
Diagnostics (Diagnosis) program. For that choose the Target | Diagnostics command.
3. If the Function Chart Builder is not in on-line mode
a. You can check the options and the base software in the Options Report for
conditions of successful target code download.
b. You can check that the data in the Node on AS 100ES column of the Status Report
equal those in the Target RAM column.
If the checks are successful, switch to on-line mode explicitly by the File | On-line Mode
command.
Otherwise you have to ensure correct base software and options and reload the application
to allow switching to on-line mode. See Section 4.4.6.8, Load Application to an
AC 100 Series Target.
4. You can select and unselect DB terminals for monitoring or forcing in the same way in on-
line mode as you do it in on-line preparation mode (or in off-line mode).
Compare the Value on Target and Force Value columns of the Test Table window to see
which force values are effective and which are only prepared or no more prepared.

4-172 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

Force and Monitor DB Terminal Values on the Target

1. To display and force the DB terminal values, select the Test Table window by the
Window | Test Table command.
2. Update the Status Report by the Target | Report Status command.
Check PCPGM State in the Status Report. If the PC program is blocked (stopped),
choose the Target | Deblock Program command to deblock (start) it.
3. Force values for DB terminals on the target by the Test | Activate All Force Values
command. Or select some items in the list box of the Test Table window and force them
on the target by the Test | Activate Force Values command.
You can also activate the appropriate check box and button in the Force group of the
Test Table window.
Be sure all the conditions were fulfilled during the on-line preparation.
The Function Chart Builder displays the force values in the appropriately configured
column of the Test Table.
4. Update the display values for DB and also PC terminals by the Test | Single Display or
Test | Cyclic Display command.
Or activate the Single or the Cyclic button in the Display group of the Test Table window.
Be sure all the conditions were fulfilled during the on-line preparation.
Or activate the Recording button to record the values of selected terminals as trend.
The Function Chart Builder displays the monitored values in the appropriately configured
column of the Test Table window. Or it shows the recorded trend.
5. Stop cyclic monitoring by the Test | Stop Display command.
You can also use the Test | Set Trigger command to define the condition, at the occurrence
of which cyclic monitoring stops automatically.

Suggested Next Steps

1. You can also monitor and force PC terminals in the target,
see Section 4.4.6.9, Display (Monitor) PC Terminals in AC 100 Series Target and
Section 4.4.6.10, Force PC Terminals in AC 100 Series Target.
2. Stop forcing of items selected in the Test Table by the Test | Deactivate Force Values
command.
Stop forcing all PC and DB terminals by the Test | Deactivate All Force Values
command.
3. If no terminals are monitored cyclically or forced, you can edit the application on-line.
See Section 4.4.6.13, Edit an AC 100 Series Application On-line.
4. Or disconnect the target by the Target | Disconnect command.
The Function Chart Builder changes to on-line preparation mode.

CAUTION
If you disconnect the target, DB terminals remain forced in contrast to PC
terminals.

3BDS 100 595R401 4-173

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.4.6.12 Set DB Terminals in AC 100 Series Target

Purpose
To set a selected DB terminal once in an AC 100 Series target on-line.

NOTE
Suppose the DB terminal is connected to the output terminal of some PC element.
After being set, the DB terminal can be overwritten with another value delivered
by this PC element in a next PC execution cycle.

A typical use of this function is to test cables by setting some characteristic values and checking
the corresponding levels on cable ends or (physical) terminal connections by an instrument.

Preparation On-line
1. Connect the Function Chart Builder on-line to the AC 100 Series target by the
Target | Connect command. If the Function Chart Builder has been in on-line preparation
mode—and generally this is the case—, it switches to on-line mode.
The Function Chart Builder displays the Status Report and the Options Report window.
In the following, if necessary, choose the Target | Report commands to reopen or update
the … Report windows.
2. If there are errors reported in the Status Report, you can check and clear them by the
Diagnostics (Diagnosis) program. For that choose the Target | Diagnostics command.
3. If the Function Chart Builder is not in on-line mode
a. You can check the options and the base software in the Options Report for
conditions of successful target code download.
b. You can check that the data in the Node on AS 100ES column of the Status Report
equal those in the Target RAM column.
If the checks are successful, switch to on-line mode explicitly by the File | On-line Mode
command.
Otherwise you have to ensure correct base software and options and reload the application
to allow switching to on-line mode. See Section 4.4.6.8, Load Application to an
AC 100 Series Target.

Setting DB Terminal Value on the Target

1. Find the PC element if there is any, the output of which is connected to the DB terminal to
be set. This PC element can overwrite the set value in a next PC execution cycle.
Deactivate it by keeping its ON terminal or the ON terminal of the superior PCPGM,
CONTRM, or other structure element forced to 0 for a necessary period.
See Section 4.4.6.10, Force PC Terminals in AC 100 Series Target.
2. Choose the Test | Set DB Value command.
The Function Chart Builder opens the Set DB Value dialog box
Fill its DB Element, Terminal, and Value text boxes.
Activate the OK button.

4-174 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

The Function Chart Builder sets the selected DB terminal once in an AC 100 Series target
to the defined value.
3. Activate the PC element deactivated in Step 1.

Suggested Next Steps

1. You can set further DB terminals in the target.
2. You can also monitor and force terminals in the target and edit the application on-line.
See Section 4.4.6.9, Display (Monitor) PC Terminals in AC 100 Series Target to
Section 4.4.6.11, Display and Force DB Terminals in AC 100 Series Target and
Section 4.4.6.13, Edit an AC 100 Series Application On-line.
3. Or disconnect the target by the Target | Disconnect command.
The Function Chart Builder changes to on-line preparation mode.

4.4.6.13 Edit an AC 100 Series Application On-line

Purpose
To edit the application in an AC 100 Series target on-line.

Preparation On-line
1. Connect the Function Chart Builder on-line to the AC 100 Series target by the
Target | Connect command. If the Function Chart Builder has been in on-line preparation
mode—and generally this is the case—, it switches to on-line mode.
The Function Chart Builder displays the Status Report and the Options Report window.
In the following, if necessary, choose the Target | Report commands to reopen or update
the … Report windows.
2. If there are errors reported in the Status Report, you can check and clear them by the
Diagnostics (Diagnosis) program. For that choose the Target | Diagnostics command.
3. If the Function Chart Builder is not in on-line mode
a. You can check the options and the base software in the Options Report for
conditions of successful target code download.
b. You can check that the data in the Node on AS 100ES column of the Status Report
equal those in the Target RAM column.
If the checks are successful, switch to on-line mode explicitly by the File | On-line Mode
command.
Otherwise you have to ensure correct base software and options and reload the application
to allow switching to on-line mode. See Section 4.4.6.8, Load Application to an
AC 100 Series Target.

3BDS 100 595R401 4-175

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Editing the Application in the Target

1. Update the Status Report by the Target | Report Status command.
Check PCPGM State in the Status Report. If the PC program is blocked, choose the
Target | Deblock Program command to deblock it.
2. Select the PC Section window or the DB Section window and edit an executable unit on-
line. See Section 4.4.8.2, On-line Editing Rules.
3. Choose the File | Save and Load command to store the changes on the AC 100 Series
target. Thereafter, you can modify some other executable unit.

Suggested Next Steps

1. You can also monitor and force terminals in the target.
See Section 4.4.6.9, Display (Monitor) PC Terminals in AC 100 Series Target to
Section 4.4.6.11, Display and Force DB Terminals in AC 100 Series Target.
2. You can upload the new parameter values from the target.
See Section 4.4.6.14, Upload Parameter from an AC 100 Series Target.
3. Or disconnect the target by the Target | Disconnect command.
The Function Chart Builder changes to on-line preparation mode.

4.4.6.14 Upload Parameter from an AC 100 Series Target

Purpose
To upload parameter values of elements such as PARDAT from an on-line connected
AC 100 Series target to the Function Chart Builder and substitute them as new initial values in
the Function Chart Builder.

Previous Events
1. Remember PARDAT elements have—among others—the following terminals:
– INIT_VAL serving as initial value for the VALUE terminal
– VALUE readable and writable also externally by MMI devices,
serving as parameter in the application
2. Tune the application running on the AC 100 Series target using procedures described in
Section 4.4.6.9, Display (Monitor) PC Terminals in AC 100 Series Target to Section
4.4.6.11, Display and Force DB Terminals in AC 100 Series Target, and Section 4.4.6.13,
Edit an AC 100 Series Application On-line.
Or tune the application running on the AC 100 Series target externally via some HMI
device.
3. Due to tuning the values of VALUE terminals may have changed, and you need to change
the initial values on the INIT_VAL terminals accordingly to optimize the start-up.

4-176 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

Preparation On-line
1. Connect the Function Chart Builder on-line to the AC 100 Series target by the
Target | Connect command. If the Function Chart Builder has been in on-line preparation
mode—and generally this is the case—, it switches to on-line mode.
The Function Chart Builder displays the Status Report and the Options Report window.
In the following, if necessary, choose the Target | Report commands to reopen or update
the … Report windows.
2. If there are errors reported in the Status Report, you can check and clear them by the
Diagnostics (Diagnosis) program. For that choose the Target | Diagnostics command.
3. If the Function Chart Builder is not in on-line mode
a. You can check the options and the base software in the Options Report for
conditions of successful target code download.
b. You can check that the data in the Node on AS 100ES column of the Status Report
equal those in the Target RAM column.
If the checks are successful, switch to on-line mode explicitly by the File | On-line Mode
command.
Otherwise you have to ensure correct base software and options and reload the application
to allow switching to on-line mode. See Section 4.4.6.8, Load Application to an
AC 100 Series Target.

Uploading VALUE and Substituting INIT_VAL in One or More DB Elements

1. Select the DB Section window.
2. Choose the Edit | Upload command.
Activate the Upload button in the Upload dialog box.
The Function Chart Builder uploads the parameter values (values of the VALUE
terminals) of all uploadable elements from the on-line connected AC 100 Series target and
shows them dimmed in the Item Des., Instance Name, Callname, Init Value list box.
3. Select one, more or all DB elements in the Item Des., Instance Name, Callname, Init
Value list box.
4. Activate the Store button in the Upload dialog box.
The Function Chart Builder stores the uploaded parameter values of the selected elements
and substitutes them as new initial values (values of the INIT_VAL terminals) in the DB
section. The uploaded and stored parameter values are shown bright (not dimmed) in the
Item Des., Instance Name, Callname, Init Value list box.
5. Activate the Close button in the Upload dialog box.

Suggested Next Steps

1. Save changes in the internal data representation by the File | Save and Load command (or
by File | Save after switching off-line).
2. You can generate new source code, see Section 4.4.5.1, Generate Source Code.
3. You can generate new target code and reload it, see Section 4.4.6.8, Load Application to an
AC 100 Series Target.
4. Or just ignore the uploaded and stored values by the File | Skip Modifications command.

3BDS 100 595R401 4-177

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.4.6.15 Retrieve Application from an AC 100 Series Target

Purpose
To regenerate the directories, element libraries, and so on, of a node and upload the target code
from an AC 100 Series target, then translate the target code back to internal data representation
for analysis, editing, and testing with the Function Chart Builder.
The scope of application retrieval depends on the information included in the target code stored
on the target, that is, on the options that were selected at target code generation.

NOTES
Application retrieval is supported by Application Builder version 2.6 and higher
and Function Chart Builder 4.6 and higher.

The application can only be retrieved if you work with the same Function Chart
Builder version as the one with which its target code was generated.

These functions are available only for new node types explicitly supporting
application retrieval, such as AC 80 2.0.

Previous Events
It is supposed that you generated target code, then connected the target and downloaded the
target code to the RAM of the target as described in Section 4.4.6.2, Preparation of Target Code
to Section 4.4.6.8, Load Application to an AC 100 Series Target.
The scope of the later retrieval is basically determined by the additional, complete information
included in the target code at target code generation. See Section 4.5.4.12, File | Generate Target
Code….

Prerequisites
1. Be sure the Function Chart Builder version, with which the target code of the application
was generated, is installed on your engineering station.
2. The target code is in the RAM of the target.
3. Be sure node type and element library versions used by the application to be retrieved are
available and installed in the corresponding release subdirectories.
Or they must be stored with the target code on the target. This is important especially in the
case of derived, modified, and user-defined libraries.

Complex Application Retrieval Started from Application Builder

1. Connect the engineering station to the target by an appropriate cable.
2. Start the Application Builder, open the Node List.
3. Choose the File | Retrieve Application command.

4-178 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.6 On-line Programming Procedures

The Application Builder fetches the node information from the target by functions of the
Function Chart Builder:
• Creates the directory structure for the node if necessary.
• Fills the subdirectories with the information uploaded from the target, such as *.INI file of
the node, libraries, *.TCS files of type circuits, and *.TPX file of footer template or
overwrites existing files there.
• Uploads and backtranslates the target code from the target by functions of the Function
Chart Builder.
See Application Builder User’s Guide for more information.

Partial Application Retrieval Started from Function Chart Builder

The Function Chart Builder offers only a part of the application retrieval functions by the user
interface: target code uploading and backtranslation.
You can use this method only if node directory structure, *.INI file of the node, libraries, and
type circuits are available, for example, due to a former complex application retrieval started
from the Application Builder.
1. Connect the engineering station to the target by an appropriate cable.
2. Start the Function Chart Builder on the node and connect the target by the
Target | Connect command.
Now the Function Chart Builder is generally in off-line connected mode.
3. Upload the target code by the Target | Upload Application command.
The Function Chart Builder stores the target code files in the \CONTROL subdirectory of
the node. You can disconnect the target.
4. Backtranslate the target code by the File | Backtranslate Target Code command.
The Function Chart Builder initializes the *.ODB file and translates the target code files in
the \CONTROL subdirectory to internal data representation. As usual for AC 100 Series
applications, the DB part and one PC program will be backtranslated. The latter will have
the original PC program number.

NOTE
If necessary, expert users may redefine the PC program number before
backtranslation: edit the PCPGMNo value in the DBPCVERS.INI file stored in the
corresponding project_root\project*\NODES\node*\CONTROL directory.

The application will be restored according to the scope of the target code as set at target code
generation:
• Names of DB elements, PC elements, and PC signals will be restored only if this
information was generated and stored together with the target code on the target.
Else the names will be omitted.
• Type circuit instances as such will be restored only if the corresponding information was
stored together with the target code on the target.
Else the type circuit instances remain disintegrated.

3BDS 100 595R401 4-179

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Elements of documentation, such as item designation of elements, position of page

divisions, and texts of headers and footers, will be restored only if the corresponding
information was stored together with the target code on the target.
Else the item designations will be generated in natural order and the headers and footers
remain empty. The page divisions have to be generated by the PC-Section | Page Layout |
Format or PC-Section | Page Layout | Generate Page Division command explicitly.
Now the application in the Function Chart Builder corresponds to the one in the target,
so the Function Chart Builder is either in on-line mode or in on-line preparation mode
depending on whether the target is connected yet or not.

NOTE
Program details producing equivalent target code cannot be distinguished. For
example, connections “=DI1.1 to PC1.1.2:1” and “=DI1.1 to PC1.1.2:2” cannot
be distinguished from connections “=DI1.1 to PC1.1.2:1” and “PC1.1.2:1 to
PC1.1.2:2”. So, the first pair will be retrieved in the second form. Us e the
PC-Section | Page Layout | Format command in case of “grayed” PC pages.
If such a problem occurs within a type circuit instance, the type circuit cannot be
identified and will be disintegrated.

After successful restoration of the internal data representation, the Function Chart Builder asks
whether to restore also HMI information.
• If you answer Yes, the Function Chart Builder restores BOIL*.C00 and COIL*.C00 files
and Bus Configuration Database as applicable. To complete the restoration, you will need
to execute the File | Save and Load command when you switch next time to on-line mode.
• In case of No it is supposed that these files are yet available and valid.

Suggested Next Steps

1. You can monitor and force terminals in the target.
See Section 4.4.6.9, Display (Monitor) PC Terminals in AC 100 Series Target,
Section 4.4.6.10, Force PC Terminals in AC 100 Series Target, and
Section 4.4.6.11, Display and Force DB Terminals in AC 100 Series Target.
2. You can edit the application on-line.
See Section 4.4.6.13, Edit an AC 100 Series Application On-line.

4-180 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.7 Diagnostic Procedures

4.4.7 Diagnostic Procedures

4.4.7.1 Diagnostic Procedures with the Diagnostics Program

Purpose of the Diagnostics Program

To select, display, and save summary, compact, verbose, and detailed diagnostic information
about the connected AC 100 Series target of a newer node type, such as AC 160, AC 110 2.1
and higher, AC 80, AC 70 1.1 and higher, and AC 55 1.1.

NOTE
The Diagnostics program is adapted to the different diagnostics features of both
former and recent controller versions. In case of AC 110 2.0, AC 70 1.0, and
AC 55 1.0 it is called the Diagnosis program. In case of AC 100 Series targets of
newer node types, such as AC 160, AC 110 2.1 and higher, AC 80, AC 70 1.1 and
higher, and AC 55 1.1, it is called the Diagnostics program.

The Diagnostics program has the following functions:

• Fetches the error information.
• Offers it in windows in appropriate form.
• Deletes the stored error information in the target.

Overview of the Diagnostics Program

Find the overview of Diagnostics commands and data transfer on the following figure:

3BDS 100 595R401 4-181

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

AC 100 Series Function Chart Builder

Target
Status Report
Target | ReportStatus
Read status
Report Errors
Target | Diagnostics

Activate

Diagnostics Program

Error Report Target | ReportErrors

CPU
Read error types
of 1st errors
Error Buffers
Reset Target | DeleteReportedErrors

Module List
Target | ListModules

Read status Select module position

I/O modules
with or w/o of all positions
Module Diag.
errors Read error Target | DiagnoseModule
states

Figure 4-126. Overview of Diagnostics Commands and Data Transfer in Diagnostics Program

The diagnostic aspects of modules are described by a model, where each module consists of one
or more instances of one or more (diagnostic) object types. For example, an I/O module may
consist of one instance of the “Device” object type for the description of its common properties
and of several instances of the “Channel” object type for the description of its channels.
In the target, the CPU module collects, buffers, and summarizes the errors from all of the
modules of the station them.

4-182 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.7 Diagnostic Procedures

The target offers the errors on different levels. The Diagnostics program presents this
information in different windows.

Table 4-14. Presentation of Errors

Window or Dialog Box

Level Error Presentation
for Presentation
Summary information Status Report (of FCB) Status
for station error / no error
Summary information Module List Status
for module error / no error
Compact information Error Report Error type (category)
for module of first detected error)
Verbose information for Module Diagnostics Error state,
instance, corresponding to error message,
object/instance model and so on
Detailed information for Additional Info Error ID, error count,
instance, corresponding to concerned base software
object/instance model task number, and so on.

The errors are stored in the target until they are deleted explicitly by the Diagnostics program.
You control the Diagnostics program by commands and evaluate the error information.

Preparation On-line
1. Connect the Function Chart Builder on-line to AC 100 Series target of a newer node type,
such as AC 160, AC 110 2.1 and higher, AC 80, AC 70 1.1 and higher, and AC 55 1.1,
by the Target | Connect command.
2. Start the Diagnostics program by the Target | Diagnostics command, or if errors are
detected on the target, alternatively by activating the Report Errors button in the Status
Report window.
In the Diagnostics program you have two possibilities to access module diagnosis, either via
Error Report or via Module List.

Accessing the Module for Diagnosis via Error Report

The Error Report window displays compact information on modules, which are configured,
that is, prepared for or involved in the execution of the loaded application program, and for
which some errors are detected and stored in the target, that is, for which the target has collected
some errors since the last deletion of the error buffer in the target.
Set a filter to reduce the set of modules.
Accessing diagnosis via the Error Report window may be preferably used when requesting
information only for erroneous modules involved in the execution of the loaded application
program.

3BDS 100 595R401 4-183

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Proceed as follows:
1. If the Module List window or the Module Diagnostics window are open, close them by
choosing the Close control command.
2. Open the Error Report window by the Target | Report Errors command.
For each module, in which an error has been detected since the last deletion of error buffer,
the Diagnostics program reads the type of first error and displays it in the Error Report
window.
3. Access detailed diagnostic information on a selected module by choosing the
Target | Diagnose Module command.
In the Error Report window the modules are shown dimmed, for which you already
called the Diagnose Module function.

Accessing the Module for Diagnosis via Module List

The Module List window displays summary information about all of the modules of the target.
Set a filter to reduce the set of modules.
Accessing diagnosis via the Module List window may be preferably used when requesting
information for all modules, which are involved in the current application program, not only for
the ones with detected errors.
Proceed as follows:
1. If the Error Report window or the Module Diagnostics window are open, close them by
choosing the Close control command.
2. Open the Module List window by the Target | List Modules command.
The Diagnostics program reads the summary information from the target and displays it in
the Module List for all modules of the station.
This information is new if you previously deleted the error buffer in the target by the
Target | Delete Reported Errors command.
3. Access detailed diagnostic information on a selected module by choosing the
Target | Diagnose Module command.
In the Module List window the modules are shown dimmed, for which you already called
the Diagnose Module function.

Navigating in Error Report and Module List

The Diagnostics program offers the diagnostic information in a structured way to facilitate its
access and evaluation.
1. Select a module in the Error Report window or Module List window and start its
diagnosis by choosing the Target | Diagnose Module command.
The Module Diagnostics window lists all object types of the selected module with
detected errors.
2. Select an object type. Then select one by one the instances with detected errors.
The Diagnostics program lists for each instance the error state, a verbose error message,
and other error characteristics depending on the complexity of the selected module.
3. Expert users may get additional binary error information by double-clicking on an item.

4-184 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.7 Diagnostic Procedures

The following figure shows an example of accessing diagnostic information about a CI626
module of an AC 110 2.1 station:

Selection
Status by Pos. (Module) by Object Type and Instance
Report
Report Errors
(button) Error Report
or
Target|Diagnostics Module List Target|DiagnoseModule
(command) Module
0,0,2,0; CI626
Diagnostics
0,2 (Selection in window) (Double-click on item)

Device Module Additional

Item 1 Info
bus, station, position, Diagnostics
(= module itself) (Device) Item 1
subposition

module type FPROM Module 2 Additional

Diagnostics Info
object type (FPROM) Item 2

Module Additional
Data Set 1 m
Diagnostics Info
(DataSet 1) Item m
Function Diagnostics item
Chart program Module ErrorState,Message,etc.
2 Diagnostics
Builder
(DataSet 2)

n Module
instance Diagnostics
(DataSet n)

Figure 4-127. Accessing Diagnostic Information with Diagnostics Program, Example

Consistency of Diagnosis
for Access by Report Error and Diagnose Module
Suppose you deleted the detected errors on the target, then start some on-line action, like
download, deblock, and editing.
The occurred errors, if any, are buffered in the CPU module. A (first) error is generally a reason
for further errors. So first errors of error chains deserve special attention.
Start Diagnostics and open the Error Report window.
Data for filling the Error Report window are read from the CPU module. The type of the first
occurred error is transferred for each module.
Be aware that some errors persist, others are transient.

3BDS 100 595R401 4-185

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Select a module and start module diagnosis for it.

In contrast to the Error Report, the data for the Module Diagnostics window are directly read
from the modules.
Errors for all instances of all object types detected since the last deletion are transferred.
Some modules can detect transient errors and differentiate between transient and persistent
errors, others can not.
Be aware that some modules, like the Series 600 I/O, delete their error buffer if they are read.
That means, the Module Diagnostics window contents may be different for repeated
Target | Diagnose Module commands.
To keep consistency of reported errors, it is a good practice to proceed as follows:
• Inspect modules systematically in the order of the occurrence of their (first) errors.
• Inspect module errors systematically for all pertinent object types and instances.
• Use automatic logging to keep track of diagnostic data.

Consistency of Diagnosis
for Access by List Modules and Diagnose Module
If you open the Module List window instead of the Error Report window, the Diagnostics
program checks all possible positions of the selected station and looks for available modules.
It accesses not only the configured modules. This action takes several seconds or even minutes
depending on station size, number of available modules, communication path, and routing.
Data for filling the Module List window are read from the modules.
The status error detected/no error detected is transferred for each module.
Be aware that some errors persist, others are transient.
Select a module and start module diagnosis for it. See Consistency of Diagnosis for Access by
Report Error and Diagnose Module at the beginning of this section.

4.4.7.2 Diagnostic Procedures with the Diagnosis Program

Purpose of the Diagnosis Program

To select, display, and save status, (summary) error, and detailed diagnostic information about
the connected AC 110 2.0, AC 70 1.0, and AC 55 1.0 target.

NOTE
The Diagnostics program is adapted to the different diagnostics features of both
former and recent controller versions. In case of AC 110 2.0, AC 70 1.0, and
AC 55 1.0 it is called the Diagnosis program.
In case of AC 100 Series targets of newer node types, such as AC 160, AC 110
2.1 and higher, AC 80, AC 70 1.1 and higher, and AC 55 1.1, it is called the
Diagnostics program.

Overview of the Diagnosis Program

Find the overview of Diagnosis commands and data transfer on the following figure:

4-186 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.7 Diagnostic Procedures

AC 110, 70, Diagnosis Program Commands

or 55 Target Status Report
Status Report
Read status

Activate
Error Report
Error Report
(sum) Error Read err. position,
Buffer (CPU) and time
Delete All Rep.Err.
Reset

Collect Module List

Read modules, Module List
state, etc.

Modules with or
Select module position
w/o errors Read Module Diag.
96 bits Module Diagnosis
Data
Buffer
Reset Select
channel
Read
96 bits Channel Diag.
Channels with Data
Buffer Channel Diagnosis
or w/o errors
Reset

Figure 4-128. Overview of Diagnosis Commands and Data Transfer in Diagnosis Program

The target collects the errors for the modules, and if applicable, for their channels, and prepares
the following information:
• 96-bit detailed error for each module and—depending on the class of the module—for
each channel
• Summary error for each module (with all channels) for error types: system error, module
error, and process error
• Compact status for the target: errors detected or no errors detected.

3BDS 100 595R401 4-187

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The errors are stored in the target until they are acknowledged, that is, read and deleted, by the
Diagnosis program.
The Diagnosis program has the following functions:
• Fetches the error information.
• Stores the detailed error information in data buffers to relieve the load on the target.
• Offers it in appropriate windows.
• Acknowledges and deletes the stored error information in the target.
You control the Diagnosis program by commands and evaluate the error information.

Preparation On-line
1. Connect the Function Chart Builder on-line to the AC 110 2.0, AC 70 1.0, or AC 55 1.0
target by the Target | Connect command.
2. Start the Diagnosis program by the Target | Report Errors command.
If the Diagnosis program is already running, you have two possibilities to access module
diagnosis, either via the Error Report window or via the Module List window.

Accessing the Module for Diagnosis via Error Report

The Error Report window displays summary information on modules (with their channels),
which are configured, that is, prepared for or involved in the execution of the application
program loaded as a result of the last Target | Load Application command, and for which some
summary errors are stored in the target, that is, for which the target collected some errors since
the last acknowledgment (deletion) of the summary error buffer in the target.
Set a filter to reduce the set of modules.
Accessing diagnosis via the Error Report window may be preferably used when requesting
information only for erroneous modules and their channels involved in the execution of the
loaded application program:
1. If the Error Report window and Module Diagnosis or Channel Diagnosis windows are
open, close them by choosing the Window | Close All Diagnosis command.
2. As prerequisite and for preserving consistency, Status Report window of Function Chart
Builder or Status Report window of Diagnosis have to contain the static text Errors
detected. If necessary, open the latter by View | Status Report.
3. Open the Error Report window by activating the Report Errors button in the Status
Report window of Function Chart Builder, or by activating the Error Report button in
the Status Report window of Diagnosis, or by the View | Error Report diagnosis
command.
The Diagnosis program reads the summary error with the erroneous modules from the
target, and displays the summary error information for these modules in the Error Report
window.
This information is new if you previously deleted the summary error buffer in the target by
Target | Delete All Reported Errors command, or if you started a new Diagnosis session.

4-188 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.7 Diagnostic Procedures

NOTE
Do not close the Error Report window unless you are sure you do not need the
information contained in it any more.

4. Access detailed diagnostic information on erroneous modules (and their channels) by

choosing the View | Module Diagnosis and View | Channel Diagnosis command and
opening for each erroneous module and channel a Module Diagnosis or Channel
Diagnosis window.

Accessing the Module for Diagnosis via Module List

The Module List window displays summary information on modules (with their channels) of
the target.
Set a filter to reduce the set of modules.
Accessing diagnosis via the Module List window may be preferably used when requesting
information for all modules (and their channels), which are involved in the current application
program, not only for the erroneous ones:
1. If the Error Report window and Module Diagnosis or Channel Diagnosis windows are
open, close them by choosing the Window | Close All Diagnosis command.
2. Open the Module List window by activating the Module List button in the Status Report
window of Diagnosis or by choosing the View | Module List diagnosis command.
The Diagnosis program reads the summary information from the target and displays it in
the Module List for all modules involved in the current application program.
This information is new if you previously deleted the summary error buffer in the target by
Target | Delete All Reported Errors command, or if you started a new Diagnosis session.
3. Access detailed diagnostic information on modules (and their channels) by choosing the
View | Module Diagnosis and/or View | Channel Diagnosis command and opening for
each module and channel a Module Diagnosis or Channel Diagnosis window.

Navigating in Error Report and Module List

The Diagnosis program offers the diagnostic information in a structured way to facilitate its
access and evaluation.
1. As prerequisite and for preserving consistency, the No errors detected / Errors detected
status should be fetched and displayed in the Status Report window of Function Chart
Builder or Status Report window of Diagnosis. If necessary, open the latter by
View | Status Report. By the appropriate button you can open either the Error Report
window or the Module List window
2. Select a module in the Error Report window or Module List window and start its
diagnosis by choosing the View | Module Diagnosis diagnosis command.
The Module Diagnosis window lists all channel types of the selected module as well as
the system or process errors.
3. If applicable, select a channel type to concentrate only on a pertinent part of the module.
The module may have one or several instances of each channel type.
In many cases channel type is just a means to structure diagnostic information.
For example, the channel of type 0 is the module itself.

3BDS 100 595R401 4-189

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4. If applicable, select an instance (one of the channels of a certain type) and start its
diagnosis by choosing the View | Channel Diagnosis diagnosis command.
The following figure shows an example of accessing diagnostic information pertaining to
Data Set part of the communication interface CI626:

Selection
Status by Pos. (Module) by Channel Type by Instance
Report View|Error Report
or View|Module List Error Report
or
Module List View|ModuleDiagnosis

0,2; CI626 Module

Diagnosis
0,2 View|ChannelDiagnosis

0 (= module itself) Channel

(sub)station number and position Diagnosis
(1)

1 (= FPROM) Channel
Diagnosis
(1)

channel type 53 (= Data Set) 1 Channel

Diagnosis
for inst. 1

Channel
2 Diagnosis
for inst. 2

channel instance n Channel

Diagnosis
for inst. n

Figure 4-129. Accessing Diagnostic Information with Diagnosis Program, Example

Consistency - Error Bits in Target

In contrast to the Error Report, the data for the Module Diagnosis window or Channel
Diagnosis window are directly read from the module, see Figure 4-128. Each possible error
corresponds to one out of 96 error bits, which is set if a fault is present or a transient fault
occurred.
Once data for the Module Diagnosis window or Channel Diagnosis window are read,
the errors are acknowledged and the corresponding error bits are reset in the target.

4-190 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.7 Diagnostic Procedures

NOTE
It is possible that diagnostic information becomes inconsistent with the
(summary) Error Report window contents or with the Module List window
contents. For example, the Error Report or Module List window indicates an
error on a module while the Module Diagnosis window reports no error and vice
versa. In addition, diagnostic data from the same module or channel read at
different times may differ.

Support of Consistency
The target and the Diagnosis program support consistency of diagnostic data on different levels
by the following measures:
• The Diagnosis program provides all document windows with time stamps.
• The Diagnosis program displays the summary errors with the time of their first occurrence
since the last acknowledge (deletion).
• The target deletes the summary error buffer and the modules' 96 bit buffers,
if the Diagnosis program reads the module or channel diagnosis data,
or if the Diagnosis program terminates the target communication.

NOTE
Once a module or channel diagnosis has been acknowledged, that is, it has been
read from the target and is displayed in the Module Diagnosis window or
Channel Diagnosis window, remember the following:

• At the first request, the diagnostic data are stored in buffers in the Diagnosis
program, one for each object (see Data Buffer in Figure 4-128). These data
buffers hold the data even if the window has been closed. If you open the
Module Diagnosis window or Channel Diagnosis window again, the data are
read from the data buffer.
• The object is marked as an object with already reported diagnosis with an
asterisk ‘*’ in each list box (Error Report, Module List, Module
Diagnosis). Already reported and thus buffered diagnostic data are
additionally indicated by the ‘*’ in the Status Bar.
• If diagnostic data are requested again for an already diagnosed object, the data
are read from the corresponding buffer. Even if the Module Diagnosis or
Channel Diagnosis window has been closed, no new data are read from the
target. This guarantees consistency between the Error Report window or
Module List window and the module or channel diagnosis.

Keeping Track of Diagnostic Data

To keep track of consistent diagnostic data, take the following precautions:
1. Before evaluating errors in a document window check the date and time when the
report/diagnosis was read from the target.
2. Save each report/diagnosis in a separate file.
3. Open a log file to automatically log all or the selected reports/diagnosis.

3BDS 100 595R401 4-191

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Requesting New Diagnostic Data from the Target

You have several possibilities to read new diagnostic data from the target and reset the data
buffers of Diagnosis:
• Close the Error Report or Module List window.
• Activate the Target | Delete Reported Errors * diagnosis command.
If there are modules with already reported and buffered diagnostic data (marked with an
asterisk ‘*’), a warning message is displayed.
If Module Diagnosis windows or Channel Diagnosis windows are open, they are closed
together with the Error Report or Module List.
If there are non-reported channels of reported modules, a warning message is displayed,
they can be acknowledged, and the corresponding data buffers in Diagnosis program can
be reset.
• Or activate the Target | Delete All Reported Errors diagnosis command.
If Module Diagnosis window or Channel Diagnosis windows are open, they are closed
together with the Error Report or Module List.
Non-reported channels of reported modules are acknowledged, the corresponding data
buffers in Diagnosis program are reset.
If necessary, choose the View | Status Report diagnosis command to update and open the
Status Report window.
Then you can fetch new diagnostic data from the target and open the Error Report or Module
List window by activating the Error Report or Module List button in the Status Report
window or by choosing the View | Error Report or View | Module List diagnosis command.

4.4.8 Rules and Conventions

4.4.8.1 Connection Rules

The Function Chart Builder allows to connect two terminals or a terminal to a constant, a name,
a symbol, or a symbolic expression if you follow these rules:
• The terminals (or constant, name, symbol, symbolic expression) must have the same or
compatible data types.
• An output terminal can only be connected to input terminals.
• An input terminal can be connected to another input terminal if the latter is already
connected to a source, that is, to an output terminal, a constant, a name, or to a symbol or
symbolic expression standing for some source.
• A DB terminal can be connected to another DB terminal only via a PC element like
MOVE. (This rule does not concern referencing DB elements on terminals of other DB
elements, for example, referencing DAT elements on REFi terminals of DSP elements.)
• Terminals of virtual elements can be connected only if you are working on a node
structure, circuit or type circuit.
Expert users may allow virtual connections also in nodes, see the Options | Preferences
command.

4-192 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.8 Rules and Conventions

4.4.8.2 On-line Editing Rules

An application for an AC 100 Series target is normally split into a DB section and a PC section
consisting of a single PC program.
The PC program consists of executable units. An executable unit contains a structure element
(with cycle time) and subordinate PC elements.
In contrast to off-line editing, restricted handling is possible when the Function Chart Builder is
in on-line mode or on-line preparation mode, that is, you make on-line changes in a running
application or prepare them:
• Changes such as inserting, modifying, and deleting PC elements are allowed for only one
executable unit at a time.
• The first change fixes the executable unit.
• Deleting connections is always allowed in the fixed executable unit and between the fixed
executable unit and one other executable unit.
• Connections to constants and to DB elements are only allowed in the fixed executable unit.
• Adding connections between executable units is only allowed in the following way:
a. Fix the executable unit having the input terminal.
b. Connect the input terminal of the fixed executable unit to the output terminal of the
other executable unit.
• Some terminals of DB elements cannot be changed on-line.
• The PC and DB sections cannot be changed simultaneously.
All these restrictions hold in the case of substantial changes, that is, for those that are reflected
by the target code and are conveyed to target.
Changes of DB element, PC element and signal names, item designations, page divisions, and
header and footer texts are normally unsubstantial. Though, in case of AC 100 Series nodes
supporting application retrieval or if you generate also information for HMI, you may have
completed the target code with some or all of these items. Then also their changes become
substantial.
If you have edited in on-line preparation mode, switch to on-line mode by the Target | Connect
command. In on-line mode, use the File | Save and Load command to store the changes in the
AC 100 Series target. Thereafter, you can modify some other executable unit.

4.4.8.3 Use of Names

Definition
Element instances and signal sources (in connections) are primarily identified by their item
designation.
A name is a unique string of characters, for example, COMMON_RESET, to be used as an alias
for element instances and sources.
Names can be used in the PC section and DB section to improve engineering and ensure better
readability of the application program.

3BDS 100 595R401 4-193

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

In different windows and dialogs names appear after a slash ‘/’ for example, in form of
item_designation/instance_name.

Name in PC Section, Signal Names

In the PC section a name can be used as signal name. The name is then an alias for a signal, in
fact, for a source to be used in connections:
• Either for an output terminal of a PC element
• Or for a constant or a DB element terminal connected to an input terminal of a PC element
in an existing connection.
In this case
• The scope of a name is the PC program or—in case of type circuits and circuits—the PC
section, in which it is created.
All signal names and (PC) instance names within the scope must be unique.
• The signal name carries the data type and kind of the source, for which it stands.
• The length of the signal name is 1 to 20 characters.

Name in PC Section, PC Instance Names

In the PC section a name can be used as instance name. The name is then an alias for a
PC element instance, a type circuit instantiated in the PC section, or a circuit located in the
PC section.
In this case
• The scope of a name is the PC program or—in case of type circuits and circuits—the PC
section, in which it is created.
All signal names and PC instance names within the scope must be unique.
• The instance name carries the element type of the instance, for which it stands.
• The length of instance name is 1 to 72 characters.
• The PC elements have no default names.

Name in DB Section, DB Instance Names

In the DB section a name can be used as instance name. The name is an alias for a DB element
instance, a type circuit instantiated in the DB section, or a circuit located in the DB section.
In case of DB elements
• The DB instance name is equal to the value of their NAME input terminal.

NOTES
Not all DB elements have a NAME terminal. Only the ones having a NAME
terminal can carry an instance name.

In some cases the NAME terminal is read-only. Then it cannot be modified.

• The scope of a name is the DB section.

All DB instance names within the scope must be unique.

4-194 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.8 Rules and Conventions

• The length of name is normally 1 to 20 characters, in certain cases 1 to 6, or 1 to 12,

or 1 to 19.
• The default DB instance name is the item designation.
In case of instantiated DB type circuits and located DB circuits
• The scope of a name is the DB section.
All DB instance names within the scope must be unique.
• The length of name is 1 to 72 characters.
• The default DB instance name is $$TCn and $$CIn, respectively.

See also
Appendix E, Syntax of Names and Section 4.4.4.11, Create/Edit/Delete a Name.

4.4.8.4 About Symbols

Definition and Purpose

Symbols are substitutes carrying values to type circuit instances and located circuits.
A symbol is a unique string of 1 to 18 characters, for example, PARAM3.
If referenced, symbols are enclosed in angle brackets ‘<’ and ‘>’.
For example, you connect a PC terminal to D=<PARAM3> or create the DB element
AO<MOD_NR>.<CHANNEL_NR> within a type circuit.
Symbols are a means for building flexible type circuits and circuits:
1. You build a type circuit (circuit).
Create, that is, declare symbols, and if applicable, assign default values to them.
Connect the symbols to the PC terminals, use symbols when referencing DB elements, and
so on, instead of using some constants, usual DB item designations, and so on.
2. You instantiate the type circuit (locate the circuit).
Define only at this moment the actual value of the symbols to be substituted and effective
in the given type circuit instance (located circuit).

Symbol Types (Data Type of Symbols)

Symbols have the data type of the value, which they carry.
It can be a non-calculated or a calculated data type.

Symbol Values
The values assigned to a symbol can be any of the following:
• Constants
• Other symbols
• Symbolic expressions
• Symbolic formulas.

3BDS 100 595R401 4-195

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The data type of the value must be compatible with the symbol type.
For example, you can assign the integer value 15 or the calculated integer symbol <CINT_1> to
a symbol if it is of type integer, but not if it is of type Boolean.
Or you can assign the text constant “123456” or the symbolic expression
“<IN_OR_OUT>PUT” to a symbol if it is of type A* (string), but not if it is of type integer.
You may assign default values to the symbols, when you declare (create) them.
You assign actual values to the symbols, when you instantiate type circuits or locate circuits
containing them.
The Function Chart Builder computes the resulting values by evaluating the symbolic
expressions or symbolic formulas in the following cases:
• At instantiation of type circuits in nodes
• At expansion of node data.
See also Section C.1, Syntax of Symbolic Expressions and Section C.2, Syntax of Symbolic
Formulas and Section 4.4.8.7, Values of Symbols.

Symbol Kinds
You may need symbols that may have different values in different instances of a type circuit and
different located circuits. In this case, use the instance-unique (IU) symbol kind.
You may need symbols that must have the same value in all instances of certain type circuits and
in several located circuits. You want to administer the value centrally for a given node.
In this case, use the project-unique (PU) symbol kind.
You may need symbols that must have the same value in a located circuit and in all instances of
certain type circuits within this circuit. The value must not be changed either at the location of
the circuit, nor later. In this case, use the location-unique (LU) symbol kind.
In type circuits the Function Chart Builder supports the following symbol kinds:
• Instance-unique (IU)
• Project-unique (PU).
In circuits the Function Chart Builder supports the following symbol kinds:
• Instance-unique
• Project-unique
• Location-unique (LU).
In node structures the Function Chart Builder supports only the project-unique (PU) symbols.
Advanced type circuits may have also variant or loop (VL) symbols. They are special instance-
unique symbols, which serve as conditions for variants (IFs) and as loop variables.

Special Symbols
These symbols have reserved names and special functions:
$$LOOPCTR
A symbol carrying the current value of a loop counter in advanced type circuits wit loops.

4-196 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.8 Rules and Conventions

__INAM__
At instantiation of a type circuit / location of a circuit, Function Chart Builder checks if the
type circuit/circuit has a symbol __INAM__. If so, and if it is not overridden by an explicit
instance name in the Create Element dialog, Function Chart Builder automatically
assigns the value of __INAM__ as instance name to this type circuit/circuit instance.

Scope of Values
You can create the same symbols, that is, symbols with the same name and of the same type, on
different levels (node structure, circuit, type circuit) and assign different values to them.
Keeping this fact in mind, the scope of values of different kinds of symbols on different levels
are the following:
• An instance-unique symbol is supported only in type circuits and circuits.
You are asked for actual values of instance-unique symbols (default values are offered if
they are available) each time you locate a circuit or instantiate a type circuit.
Each entered value or accepted default is effective only for the current instance, and—in
case of a circuit—it can be effective also for the type circuits instantiated in this circuit.
You can modify the value of an instance-unique symbol in type circuits and circuits also
after their instantiation and location, respectively.
• A project-unique symbol is supported in type circuits, circuits, and node structure.
It has default values for all its occurrences. These values may differ. You can modify them
when you locate a circuit, or instantiate a type circuit, or later. They can be suppressed by
values inherited from the neighboring higher level, that is, from the node structure where
the circuit is located or from the circuit where the type circuit is instantiated.
In case of a circuit, the value of a project-unique symbol can be effective also for the type
circuits instantiated in this circuit.

NOTE
Use also project-unique symbols in the circuit if you just have to pass symbol
values defined in the node structure to type circuits instantiated in the circuit.

• A location-unique symbol is supported only in a circuit.

It has a default value. This value is effective for the only occurrence of this circuit and it
can be effective for the type circuits instantiated in this circuit.
You cannot modify the value of a location-unique symbol in circuits after their location.
See also Section 4.4.8.6, Evaluation of Symbols.

4.4.8.5 Use of Symbols

Declaration (Creation) of Symbols

To create symbols, select the Symbol Section window by the File | Open Section | Symbol
command and choose the Edit | Create command.
To set or modify the default value of a symbol, select the symbol in the Symbol Section
window and choose the Edit | Symbol command.

3BDS 100 595R401 4-197

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Use of Symbols, Symbolic Expressions, and Symbolic Formulas

You can use symbols, symbolic expressions, and symbolic formulas to define different items
within different objects:

Table 4-15. Use of Symbols, Symbolic Expressions, and Symbolic Formulas

\Object Node Type TC Located

Circuit Node
Item\ Structure Circuit Instance Circuit
PC Symbol, Symbol, Symbol, No symbs Not Not
instance symb.expr. symb.expr. symb.expr. available editable editable
name
PC Symbol, Symbol, Symbol, No symbs Not Not
terminal symb.expr. symb.expr. symb.expr. available editable editable
value
DB item Symbol, Symbol, Symbol, No symbs Not Not
design. symb.expr. symb.expr. symb.expr. available editable editable
DB Symbol, Symbol, Symbol, No symbs Not Not
instance symb.expr. symb.expr. symb.expr. available editable editable
name
DB Symbol, Symbol, Symbol, No symbs Not Not
terminal symb.expr. symb.expr. symb.expr. available editable editable
value
Default No TC/CI Symbol, Symbol, No symbs Not Not
value of terminals symb.expr. symb.expr. available editable editable
TC/CI available
terminal
Default Symbol, Symbol, Symbol, No symbs Not Not
value of symb.expr., symb.expr., symb.expr., available editable editable
other symb.frml. symb.frml. symb.frml.
symbol
Actual Symbol, Symbol, Symbol, No symbs Symbol, Symbol,
value of symb.expr., symb.expr., symb.expr., available symb.expr., symb.expr.,
other symb.frml. symb.frml. symb.frml. symb.frml. symb.frml.
symbol

See Section 4.4.8.8, Examples of Symbol Usage.

Assignment of Value to Symbols of TC Instances and Located Circuits

To instantiate a type circuit or locate a circuit, choose the Edit | Create - for PC Section or
Edit | Create - for DB Section command, select the appropriate element type.

4-198 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.8 Rules and Conventions

Activate the Symbol Values button in the Create Element dialog box to open the Edit Symbol
Values dialog box. Here, you inspect the available default values of the symbols of the type
circuit or circuit. You can enter new actual values but also leave the default values unchanged.
In due case do not forget to activate the OK button of both the Edit Symbol Values dialog box
and the Create Element dialog box.
If you want to change later the actual values of symbols in instantiated type circuits and located
circuits, choose the Edit | Symbol Values command.

NOTE
Changing actual values of symbols is limited to off-line mode. In on-line mode
you can use the Edit | Symbol Values command only for inspecting the actual or
resulting values of symbols.

4.4.8.6 Evaluation of Symbols

Evaluation of Symbols in Nodes

Nodes do not have symbol sections.
So the symbols of each type circuit instance get their values only from within these instances.
No conflicts occur.

Evaluation of Symbols in Node Structures

As mentioned previously, you can create the same symbols, that is, symbols with the same name
and of the same type, on different levels in node structure - circuit - type circuit hierarchies and
assign different values to them.
In node structure - circuit - type circuit hierarchies symbols—especially those with multiple
occurrences—get their final values only after the expansion of node data.
Here, values are also inherited from higher to lower level.
During expansion of node data, conflicts of differing values of symbols with the same name and
of the same type are resolved on the basis of the following symbol value inheritance rules:
1. In general, if the symbol is declared on neighboring levels, the value from the highest level
dominates. The Function Chart Builder conveys it to the lower levels and suppresses the
values there except the following cases 2 and 3.
2. If a symbol is declared as instance-unique in a circuit (type circuit), its value remains
effective for this circuit (type circuit) as set at its location (instantiation).
3. If a symbol is declared as location-unique in a circuit, its value remains effective for this
circuit as set at its location.

3BDS 100 595R401 4-199

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

See the graphical representation of the symbol value inheritance rules in the following figure:

In the node PU symbol; value Legend: If the same symbol exists

structure: defined locally on higher level, its value
overwrites the value of the
symbol on lower level.
Though the same symbol
exists on higher level, its
value does not overwrite the
value of the symbol on lower
In located PU; IU LU level.
circuits: local value defined defined
suppressed locally locally

(If there are no symbols with

the same name and of the
In type circuit PU; IU same type on neighboring
instances: local value defined levels, no conflicts to be
suppressed locally described arise.)

Figure 4-130. Inheritance of Symbol Values Between Neighboring Levels

See the tabular representation of the symbol value inheritance rules in the following tables.
Table 4-16, Table 4-17, and Table 4-18 contain the value inheritance of symbols occurring in the
doubles NS-TC, NS-CI, and CI-TC, respectively.

Table 4-16. Symbol Value Inheritance in TC, Instantiated in NS

Type of Same Symbol Defined in

Type Circuit Value of the Symbol in the Type Circuit After
Node Structure Instantiated in Expansion of the Node
Node Structure
PU PU As set in symbol section of the node structure.
PU IU As set at instantiation of the type circuit.
It can be modified by Edit | Symbol Values
from the node structure.

4-200 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.8 Rules and Conventions

Table 4-17. Symbol Value Inheritance in CI, Located in NS

Type of Same Symbol Defined in Value of the Symbol in the Circuit

Node Structure Circuit After Expansion of the Node

PU PU As set in symbol section of the node structure.

PU IU As set at location of the circuit. Can be modified
by Edit | Symbol Values from node structure.
PU LU As set in symbol section of the circuit.
It is constant, it cannot be modified.

Table 4-18. Symbol Value Inheritance in TC, Instantiated in CI

Type of Same Symbol Defined in

Type Circuit Value of the Symbol in the Type Circuit After
Circuit Instantiated in Expansion of the Node
Circuit
PU or IU PU As set at location of the circuit.
PU or IU or LU IU As set at instantiation of the type circuit. Can be
modified by Edit | Symbol Values from circuit.
LU PU As set in symbol section of the circuit.
It is constant, it cannot be modified.

Table 4-19 contains the value inheritance of symbols occurring in the triple NS-CI-TC.

Table 4-19. Symbol Value Inheritance from NS via CI to NS

Type of Same Symbol Defined in

TypeCircuit Value of the Symbol in the Type Circuit
Node After Expansion of the Node
Circuit Instantiated
Structure
in Circuit
PU PU PU As set in symbol section of the node
structure.
PU PU or IU IU As set at instantiation of the type circuit.
or LU It can be modified by Edit | Symbol
Values from the circuit.
PU IU PU As set at location of the circuit.
It can be modified by Edit | Symbol
Values from the node structure.
PU LU PU As set in symbol section of the circuit.
It is constant, it cannot be modified.

3BDS 100 595R401 4-201

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder supports also the choice between referencing a symbol of an object
itself or referencing the same symbol of the object on next higher level. You may need this
distinction, for example, when assigning other symbols, symbolic expressions or symbolic
formulas as values to symbols, or when connecting symbols to terminals.
To distinguish the symbols of the lower level object, use ‘<%’ and ‘%>’ instead of the simple
‘<’ and ‘>’ symbol delimiters.
The Function Chart Builder supports the following case:
Type circuit instantiated in a circuit
– <s> carries the value of symbol s of the circuit.
– <%s%> carries the value of symbol s of the type circuit.
Referencing the symbol of the higher or lower level object does not influence or suspend
inheritance.
Consider that the two alternatives lead to different values only if the local symbol is instance-
unique or location-unique.

NOTE
There are two other possible cases. Then the Function Chart Builder supports
only referencing symbols of the lower level:

• Type circuit instantiated in a node structure

<%s%> carries the value of symbol s of the type circuit.
• Circuit located in a node structure
<%s%> carries the value of symbol s of the circuit.

4.4.8.7 Values of Symbols

Values of Non-calculated Symbols

Non-calculated symbol types allow (only) symbol substitution and concatenation.
Non-calculated symbols have the following values:
• Default value
as set at symbol creation time. It can be empty, a constant, a further symbol, or a symbolic
expression consisting of text constants and symbols connected by concatenation.
For example, the symbol DICHANNEL of type A*18 has the default value “DI1.1”.
• Actual value
is a new value as set at instantiation (or location) time or the default value, if any, left
unchanged.
For example, the actual value of symbol DICHANNEL of type A*18 has been set to
“DI<DI_NR>.<CH_NR>”.
• Resulting value
is the result of the following operations:
- Substitution and concatenation on the basis of the actual value
- Application of the inheritance rules

4-202 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.8 Rules and Conventions

After expansion of node data or, if you are working on a node, at instantiation, the symbols
in the actual value string are evaluated and their resulting values are substituted and
concatenated.
For example, suppose <DI_NR> equals 5 and <CH_NR> equals 2. In a line of the PC
source code of the expanded node, you will find the connection :3 =DI5.2:ERR instead of
the original type circuit source code line :3 =<DICHANNEL>:ERR.

Values of Calculated Symbols

Calculated symbol types support building complex arithmetical and logical formulas to
calculate the resulting value. They do not allow symbol concatenation. The formula must not
contain symbols of types T, TR, and A*.
Calculated symbols have the following values:
• Default value
of a calculated symbol is a symbolic formula set at symbol creation time, or it can be left
empty. The symbolic formula consists of constants, simple symbols, operators, and
parentheses. It can be complex. The only limiting factor is the text box length
(80 characters) to enter the symbolic formula.
For example, the symbol AREA of type CR has the default value
<BASE> * <HEIGHT> / 2.
• Actual value
is a new symbolic formula set at instantiation (or location) time or the default value,
if there is any, left unchanged.
For example, the actual value of symbol AREA of type CR has been set to
(<RADIUS> ^ 2) * <PI> / 4.00.
• Resulting value
is the result of the following operations:
- Calculation on the basis of the symbolic formula in its last form
- Application of the inheritance rules
After expansion of node data or, if you are working on a node, at instantiation, the symbols
in the symbolic formula are evaluated, that is, their resulting values are substituted in the
symbolic formula, and the symbolic formula is calculated.
For example, suppose <RADIUS> equals 5.00 and <PI> equals 3.14. In a line of the PC
source code of the expanded node, you will find the connection :1 D=19.63 instead of the
original type circuit source code line :1 D=<AREA>.

NOTE
The Function Chart Builder internally converts all operands into real format with
a precision of 0.01. For example, the integer -5 will be converted internally to -
5.00, the Boolean constants TRUE and FALSE to 1.00 and 0.00, respectively.
The Function Chart Builder executes the operations on the converted operands
from left to the right in accordance with the priority of the operators and the
parentheses. Finally, the Function Chart Builder converts the real format result to
the type of the symbol to which the symbolic formula belongs. For example,
6.6E5 will be converted to 660000 for a calculated long integer, or 17.20, being
nonzero, will be converted to 1 (TRUE) for a calculated Boolean.

3BDS 100 595R401 4-203

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The operators allowed in the formula and their priority are shown in the next table.

Table 4-20. Operators in Symbolic Formulas

Operator Designation Priority

^, NOT Exponentiation, negation High
*, /, AND Multiplication, division, AND
+, -, OR Sign, addition, subtraction, OR
=, <, >, <>, <=, >= Equal, less, greater, not equal, Low
less or equal, greater or equal

4.4.8.8 Examples of Symbol Usage

PC Instance Name
PROC<PR_NR>

PC Terminal Value
Connecting a symbol to an input PC terminal: <PARAM1>
Connecting a symbol to an output PC terminal: N=<VAR4>
Connecting a symbolic expression to an input PC terminal: PC1.1.<PAR1>:20
Connecting a symbolic expression to an output PC terminal: N=SIGNAL<NR2>
Connecting a symbol to an input or output TC/CI terminal
(within the type circuit or circuit):
T=<INPUT> T=<OUTPUT>

DB Item Designation
AO<MOD_NR>.<CHANNEL_NR>

DB Instance Name
ANA_OUT_10V_<MOD_NR>

DB Terminal Value
DI<DI_NR>.1 <GENERAL_BLOCKED>

Default Value of (an Input) TC/CI Terminal

<MODE> 1<ZEROS>

Default Value of a Non-calculated Symbol

NUMBER_OF_ERROR<S_OF_PLURAL>

Default Value of a Calculated Symbol:

<PI>*<RADIUS>^2

4-204 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.8 Rules and Conventions

(Actual) Value of a Non-calculated Symbol

Symbolic expression using a symbol from within the type circuit or circuit:
CHANNEL<%CH_NR%>
Symbolic expression using a symbol from outside of the type circuit or circuit:
MODULE<MOD_NR>

(Actual) Value of a Calculated Symbol

Symbolic formula using a symbol from within the type circuit or circuit:
<%CH_NR%> + 2
Symbolic formula using a symbol from outside of the type circuit or circuit:
10.0 * <MM_PER_INCH>

4.4.8.9 Use of TC/CI Terminals

Definition and Purpose
TC/CI terminals are terminals of type circuits and circuits.
They are substitutes carrying some value and properties:
• You define the TC/CI terminals within the type circuit (circuit).
They convey all the values and properties from within the type circuit (circuit) to the
object, in which they are instantiated (located).
• You use the TC/CI terminals to connect an instantiated type circuit (located circuit) to
other terminals within the object, in which they are instantiated (located). The TC/CI
terminals of an instantiated type circuit (located circuit) convey all the values from the
object, in which they are instantiated (located), in the instantiated type circuit (located
circuit). In the function chart the Function Chart Builder shows the TC/CI terminals as
short lines leading to or from the graphical symbol of type circuits and circuits.
A TC/CI terminal is a unique string of 1 to 8 characters, for example, IN2.
If referenced, TC/CI terminals are enclosed in < and >. For example, you connect a PC terminal
to T=<IN2>.
TC/CI terminals are a means for building flexible type circuits and circuits.

TC/CI Terminal Number

The number of a TC/CI terminal is a cardinal in the range 1 - 999.

TC/CI Types (Data Type of TC/CI Terminals)

The TC/CI terminal has always a defined TC/CI terminal (data) type, for example, B (Boolean),
I (integer). It must be the same as the data type of PC terminal, to which it is connected within
the type circuit or circuit.
It can be only a non-calculated type.
You have to define size for the A* (array, string) type. You can define size also for groups of the
following types: B (Boolean), I (integer), IL (long integer), R (real), T (time), and TR (time as
real).
You can define type or size also by a symbol.

3BDS 100 595R401 4-205

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

TC/CI Terminal Kinds

The kind of the TC/CI terminals can be input (IN), output (OUT), or function parameter (FP).
It must be the same as the kind of PC terminal, to which it is connected within the type circuit or
circuit.
OUT stands also for the case if both input and output PC terminals are connected.

Default Value
TC/CI terminals may have a default value of the appropriate type.
For example, IN2 may have the default value “EMPTY”. Suppose IN2 is of type A*80 (array).

Attributes
The attributes of the TC/CI terminals have one of the following functions:
• The attribute reflects to what kind of terminals the TC/CI terminal is connected within the
type circuit or circuit, such as
Dynamic, DB Reference, Non-Invertible.
• The attribute defines the form of the graphical symbol representing the instantiated type
circuit or the located circuit in the function chart, such as
Adjust, Blank Line, Waist.

4.4.8.10 Page Division Rules

Common Page Division Rules
• The function chart—displayed or printed—is divided by page divisions into pages.
• Page divisions can be attached only to PC elements.
No more than one page division can be attached to one PC element.
• Each page of the function chart has a page number.
It can be either a soft page number or a fixed page number.
Soft page numbers are just relative positions. They are recalculated after every relevant
change of the PC section.
Fixed page numbers are final definite numbers.
• Page numbers must be unique and in the interval 0.1 to 9999.9.
They must have the form nnnnn or nnnnn.f, where nnnnn and f are figures.
• Page numbers need not be in regular numerical order. That means,
the page number of a page is not necessarily greater than the page number of the preceding
page and not necessarily smaller than the page number of the following page.
• The first page division with soft page number acquires the page number 1.0 if it is free.
Else it acquires the page number dynamically by incrementing at first 1.0 and then the last
used page number by the auto increment value and finding the first free number.
• Every next page division with soft page number acquires the page number dynamically by
incrementing the last used page number by the auto increment value and finding the first
free number.

4-206 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.4.8 Rules and Conventions

• The auto increment value is normally 1 for soft page numbers.

(Only for expert users: To change the auto increment value, modify the following line in
the [PCSection] section of the FCB.INI file:
PageIncrement=increment
where 0.1 <= increment <= 1000.0)
• The tree diagram indicates the page divisions in the function chart by dashed lines. At the
right end of the line you find the page number. In case of soft page numbers it is preceded
by a hash mark `#´.

Automatically Inserted Page Divisions

If you create, modify, or delete PC elements, instantiate type circuits, locate circuits, or
explicitly generate page divisions by the PC-Section | Page Layout | Generate Page Division
command or just add necessary page divisions by the PC-Section | Page Layout | Format
command, the Function Chart Builder inserts automatically page divisions.
• The Function Chart Builder can automatically insert only page divisions with soft page
numbers.
• The Function Chart Builder attaches a page division to the PCPGM element.
This page division cannot be deleted.
• In case of the PC-Section | Page Layout | Generate Page Division command (only),
the Function Chart Builder attaches a page division also to every structure element unless
it follows immediately a superior element.
This page division can be deleted, but the contents of the merged page may be larger than
the page layout and then the contents cannot be displayed nor printed.
• The Function Chart Builder attaches a page division to any other PC element if it does not
fit in the page.
This page division can be deleted, but the page contents can not be displayed nor printed.
• At instantiation the Function Chart Builder converts the page numbers of the type circuits
to soft ones. Normally, the Function Chart Builder does not reserve the amount of page
numbers for instantiated type circuits that they have inside themselves.
If you are working with the function-oriented project engineering method, that means that
the pages of the expanded node have the same page numbers as the node structure.
(Only for expert users: To make the Function Chart Builder reserve the amount of page
numbers for instantiated type circuits that they have inside themselves, add the following
line in the [General] section of the FCB.INI file:
TCPageBreakStrategy=1
That means that the pages of the node have the same page numbers as the node with
resolved type circuits in APB.)

Manual Handling of Page Divisions

You can use PC-Section | Page Layout | … commands to insert page divisions with soft page
numbers and fixed page numbers, change the kind of page numbers, and delete page divisions.
The Function Chart Builder applies or tries to apply all of the previous rules.

3BDS 100 595R401 4-207

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5 Runtime Operation Menus

This section describes the following items:
• Controls in the Title Bar, Toolbar, and Status Bar
• Controls in the document windows
• Commands in the menus of the Menu Bar.

4.5.1 Controls in Title Bar, Toolbar and Status Bar

4.5.1.1 Controls in Title Bar

Windows and dialog boxes have standard pull-down control menus and other controls
integrated in their Title Bar located along the top of a window or dialog box.

Control Menu Button

Click on the icon of the application, for example, , in the upper left corner of the

application window to pull down the Application Control menu containing

generally the following commands:
• Restore
• Move
• Size
• Minimize
• Maximize
• Close.
Click on the icon of the document, for example, , in the upper left corner of the

document window to pull down the Document Control menu containing

generally the following commands:
• Restore
• Move
• Size
• Minimize
• Maximize
• Close
• Next
• Previous.
For detailed information on the Control menu commands see the on-line help.

4-208 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.1 Controls in Title Bar, Toolbar and Status Bar

Title
• The Title of the application window is the name of application, possibly followed by the
parameters, such as project name and object name, for example,
Function Chart Builder - Circuit: WATER/INPUT
• The Title of the document window can be a section name, preceded by a number in angle
brackets, or a filename. The number is the key, which serves as shortcut for the window
when combined with ALT.
For example, <2> indicates the shortcut ALT+2.
The asterisk ‘*’ in the Title indicates that you modified the contents of the document
window since its opening.
The word On-line in the Title indicates the following:
– The document window reflects conditions of the on-line connected AC 100 Series
target.
– The modifications done in the document window are—or can be—effective in the
on-line connected AC 100 Series target.
• The Title of dialog box describes the purpose of the dialog box.
To move an application window, a document window, or a dialog box, drag and drop their Title.
Double-click on the Title of an application window or a document window to switch between
maximized and restored window size.

Shortcut Buttons for Window Sizing

Use the following buttons depending on the operating system as shortcuts for corresponding
commands in the control menus:
• Maximize button

• Minimize button

• Restore button

• Close button .

4.5.1.2 Controls in Toolbar

The Toolbar is displayed across the top of the Function Chart Builder window, below the
Menu Bar.

Figure 4-131. Toolbar of the Function Chart Builder

To hide or display the Toolbar, choose the View | Toolbar command.

3BDS 100 595R401 4-209

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

It provides quick mouse access to many commands used in the Function Chart Builder.
The following table lists the Toolbar commands:

Table 4-21. Icons and Commands of the Toolbar

Icon Command Short Description

File | Open Section | PC Open an existing PC program of the selected node or node structure or
PC section of the selected circuit or type circuit.
File | Open Section | DB Open the DB section of the selected node, node structure, circuit, or type
circuit.
File | Open Section | Open the symbol section of the selected node structure, circuit, or type
Symbol circuit.
File | Open Section | Open the TC/CI terminal section of the selected type circuit or circuit.
TC/CI Terminal
File | Save Save all the changes you have made in the internal data representation of
the Function Chart Builder.
File | Print Define the parts of the document for the selected object and to start
printing.
View | Zoom Set the zoom factor for the active PC Section pane on the screen.
Edit | Cut Cut the selection and put it into the paste buffer.
Edit | Copy Copy the selection to the paste buffer.
Edit | Paste Paste the paste buffer contents.
Edit | Undo Undo the previous action.
Edit | Redo Redo the previously undone action.
Edit | Find Find the PC element (or type circuit or circuit) or PC connection
in the active PC Section window.
Edit | Name Edit name of selected DB element, or PC element, or PC terminal.
View | Function Chart, Switch between with function chart and tree diagram views in PC Section
View | Tree … window panes.
Edit | Create - for PC Insert a PC element (or a type circuit or circuit creating PC elements) in
Section the PC program corresponding to the active PC Section window.
Options | Preferences, Assign right mouse button to quick connect mode or to opening the
toggle Quick Connect context menu in the PC Section window.
by Right Mouse Button
PC-Terminal | Connect Connect selected PC terminal.
PC-Terminal | Disconnect Disconnect selected PC terminal.
PC-Terminal | Invert Invert selected PC terminal.

4-210 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.1 Controls in Title Bar, Toolbar and Status Bar

Table 4-21. Icons and Commands of the Toolbar (Continued)

Icon Command Short Description

PC-Terminal | Select for Select or unselect PC terminal for displaying its value on-line.
Display
PC-Terminal | Force Value Add a PC terminal with a force value to the Test Table
| Create/Edit for on-line forcing or edit a force value.
Help | Contents Open the Help Topics: Function Chart Builder 4.* - Help window and
display the contents of the on-line help.
Help | On Context Obtain context-specific help on the Function Chart Builder.

4.5.1.3 Indicators in Status Bar

The Status Bar is displayed at the bottom of the Function Chart Builder window.

Figure 4-132. Status Bar of the Function Chart Builder

To display or hide the Status Bar, use the View | Status Bar command.
Generally, the left area describes actions of menu commands as you use the arrow keys to
navigate through menus. This area similarly shows messages that describe the actions of toolbar
buttons while you depress them. If after viewing the description of the toolbar button command
you do not want to execute the command, release the mouse button only after you moved the
pointer off the toolbar button.
During a connection with an AC 100 Series target the Function Chart Builder displays here also
information about the progress and status of the connection, time stamp of the last successful
transfer of display values, and target status. In on-line mode, the information is displayed in the
left area with white letters on dark background (in reverse video).
The right areas of the Status Bar indicate whether some keys are latched down, and show the
selected communication port and target address.

Table 4-22. Indicators in the Status Bar

Indicator Description
NUM The NUM LOCK key is latched down.
SCRL The SCROLL LOCK key is latched down.
COMx/X3/AF 100 Selected port for communication with the AC 100 Series target:
COM1 to COM4, X3, or AF 100.
target_name Name and address of the connected AC 100 Series target.
[net, node |bus, station, position] Net and node are shown only in case of routing (X3).

3BDS 100 595R401 4-211

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTES
If the last right areas are dimmed, they contain data as set in the Application
Builder.
If the last right areas are displayed normally, they contain actual data of an on-line
connected AC 100 Series target.
The COMx/X3/AF 100 indicator is highlighted during the communication to and
from the connected target.
AF 100 standing for Advant Fieldbus 100 may be indicated only in case of
special configurations of the Function Chart Builder.

4.5.2 Controls in Document Windows

4.5.2.1 *.ODB Window

This window reflects the internal representation of the object, on which you are working, and
lists its sections.
Use this window to create, open, and delete sections of the object and to create, open, delete,
cut, copy, and paste PC programs of the PC section.

Figure 4-133. *.ODB Window

Title
The window is titled by filename of the internal representation of the selected object.
The number in angle brackets is the key that serves as shortcut for the window when combined
with ALT, in this case ALT+1.
An asterisk ‘*’ indicates that you modified the *.ODB window since its opening.

Section
Select the section you want to create, open, or delete.
Select the PC section if you want to create, open, delete, cut, copy, or paste PC programs.
Dimmed sections are not available for the selected object.

4-212 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

Contents
For PC section of nodes or node structures:
• The list box part of the combo box shows the existing PC programs.
• Before opening a PC program, select its name in the list box part or edit it in the text box
part in PCpp form, where the PC program number pp is a value in the range 1 - 99.
• Before copying, cutting, or deleting one, several, or all PC programs, select their names in
the list box part, for example, by clicking on them while keeping the CTRL key pressed, or
edit the PC program names in the text box part in PCpp form separated by a space, where
the PC program numbers pp are different values in the range 1 - 99.
In all other cases:
A wildcard asterisk ‘*’ shows that the section, selected in the Section list box, exists.

New
Activate this button to create the selected section or PC program.
For further actions and dialogs see the File | New Section commands.

Open
Activate this button to open the selected section or PC program.
The Function Chart Builder opens the corresponding PC Section window, DB Section window,
Symbol Section window, or TC/CI Terminal Section window and displays its elements.
See also the File | Open Section commands.

Delete
Activate this button to delete the selected PC program.
For further actions and dialogs see the File | Delete Section | PC commands.
(This function is not implemented yet for DB section, symbol section, and TC/CI section.)

4.5.2.2 PC Section Window

The PC Section window is a configurable window with 1, 2 or 3 panes.
The panes can be configured to show a PC program or—in case of a circuit or type circuit—
the PC section in function chart or tree representation.
Each pane can be configured to show one of the following views:
• Function chart
• Tree - all elements
• Tree - structure elements
• Tree - top of page elements.
Each pane uses its own zoom factor.
There can be one and only one active pane having the focus. This is indicated by a focus
rectangle drawn with a dashed line around the selected element.

3BDS 100 595R401 4-213

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The recent tree view is always synchronized with the recent active function chart view.
Panes of the same view type are not synchronized, neither panes belonging to different
PC Section windows.
See example of PC Section window with 3 panes in the following figure.
Pane 1 shows the tree diagram with all elements, panes 2 and 3 show the function chart.

Figure 4-134. PC Section Window with Three Panes

You can use the context menu with relevant commands by clicking with the right mouse button
on different parts of the PC Section window or by pressing the context menu key. The latter is
available only on WIN95 keyboards. Which commands appear in the context menu depends on
the location of the mouse cursor and the current selection, respectively. Choose the Options |
Preferences command and select the Quick Connect by Right Mouse Button check box to
preserve the classical quick connect mode when clicking with the right mouse button on a PC
terminal.

Title
The Title consists of the following items:
• A number in angle brackets
It serves as shortcut for opening the window when combined with ALT.
For example, <2> indicates the shortcut ALT+2.

4-214 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

• The word On-line

If it is displayed, the PC Section window reflects conditions of the on-line connected
AC 100 Series target, and the modifications done in the PC section are—or can be—
effective in the target.
• The name of the section
• The name (number) of the PC program in case of nodes and node structures, preceded by a
hyphen ‘-’
• The asterisk ‘*’ indicating that you modified the PC Section window since its opening
• An order number 1, 2, and so on, preceded by a colon ‘:’
It is used to differentiate between PC Section windows if more than one are available.

Vertical Splitbar
To increase and decrease pane 1, drag this splitbar with the mouse to the right and the left,
respectively.
Or choose the View | PC Pane | Split Vertically command and use the RIGHT and LEFT keys.

Horizontal Splitbar
To increase and decrease pane 2, drag this splitbar with the mouse down and up, respectively.
Or choose the View | PC Pane | Split Horizontally command and use the DOWN and UP keys.

PC Pane Toolbar
Each pane has its own toolbar. Parts of the PC pane toolbar see in the following figure:

Select top PC element Horizontal scrollbar

Goto previous page Select view in this pane

Current page number

Goto next page

Select bottom PC element

Figure 4-135. PC Pane Toolbar

If the pane is too narrow, some buttons are not shown.

• Select Top PC Element

Activate this button to go to the page with the top PC element and select the latter.

• Goto Previous Page

Activate this button to go to the previous page and select the last element there.

3BDS 100 595R401 4-215

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Current Page Number

This is a drop-down combo box showing the current page number in its text box part.
Drop its list box part down to see all the page numbers.
Select one of the page numbers by clicking on it with the left mouse button to go to the
corresponding page and select the top PC element there.

• Goto Next Page

Activate this button to go to the next page and select the first element there.

• Select Bottom PC Element

Activate this button to go to the page with the bottom PC element and select the latter.

• Horizontal Scrollbar
Use this ordinary scrollbar with arrow boxes and scroll box to scroll the pane horizontally.

• Select View
Activate this button to open a pop-up menu and select there one of the views for the pane.

PC Section Window Pane with Function Chart

Use the panes with function chart for the following purposes:
• Build and inspect the PC programs of a node or node structure or the PC section of a
circuit or type circuit in function chart representation.
• Make connections to PC terminals.
In case of in AC 100 Series nodes use it also for the following purposes:
• Edit the application on-line.
• Select PC terminals for monitoring (display) and forcing.
• Inspect the display and force values.

PC Section Window Pane with Tree Diagram

Use the panes with tree diagram for the following purposes:
• Build and inspect the PC programs of a node or node structure or the PC section of a
circuit or type circuit in tree diagram representation.
• Overview the whole PC program or PC section.
• Set the page layout of PC diagrams.
The pane with the tree diagram has three columns to show the PC elements and the headlines
and the page numbers of the pages of the function chart.
To see relevant information, resize the columns PC Element, Headline, and Page by dragging
the divisions that separate the header parts at the top of the pane.
The divisions may be visible only if you enlarge the pane.

4-216 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

4.5.2.3 DB Section Window

Use this window to create, open, or delete DB elements and objects, which create or modify DB
elements, and to connect DB terminals to PC terminals.

Figure 4-136. DB Section Window

Title
The Title consists of the following items:
• A number in angle brackets
It serves as shortcut for opening the window when combined with ALT.
For example, <3> indicates the shortcut ALT+3.
• The word On-line
If it is displayed, the DB Section window reflects conditions of the on-line connected
AC 100 Series target, and the modifications done in the DB section are—or can be—
effective in the target.
• The name of the section
• The asterisk ‘*’ indicating that you modified the DB Section window since its opening
• An order number 1, 2, and so on, preceded by a colon ‘:’
It is used to differentiate between DB Section windows if more than one are available.

Filter/Item Des.
Edit a filter in the text box part to show only DB elements with a certain item designation in the
Item Designation, Instance Name, Attr., Callname, Address list box.
Open the list box part to see the valid filters and select one. Hash mark ‘#’ is wildcard for board
and channel numbers.

3BDS 100 595R401 4-217

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Item Designation
The item designation of the selected DB element appears here.
To change selection, you can also edit another item designation here.
The new selection will be effective in the Item Designation, Instance Name, Attr., Callname,
Address list box if you activate one of the buttons Create, Edit, or Delete.

Filter/Instance Name
Select a filter in the list box part or edit it directly in the text box part to show only DB elements
with a certain instance name in the Item Designation, Instance Name, Attr., Callname,
Address list box.
Wildcards ‘*’ and ‘?’ are also allowed.
Close the new filter condition with ENTER to make it effective.
The list box part contains the recently used filters.

NOTE
Be sure to select the View | Sort by Name command if you want to see
the DB elements sorted alphabetically by name in the list box.

Instance Name
The instance name of the selected DB element appears here.
To change selection, you can also edit another instance name here.
The new selection will be effective in the Item Designation, Instance Name, Attr., Callname,
Address list box if you activate one of the buttons Create, Edit, or Delete.

DB Terminal
The drop-down list box contains all terminals of the selected DB element, which can be
connected to the PC terminal selected in the PC Section window.
See Section 4.4.8.1, Connection Rules.
Select the DB terminal here.
The text box part reflects your selection. You can also edit here any appropriate DB terminal.

Item Designation, Instance Name, Attr., Callname, Address

This list box shows the DB elements, which satisfy the filter conditions, by their item
designation, instance name, attribute, callname, and address.
Select a DB element here.
Your selection appears in the Item Designation and Instance Name text boxes.
Use the View | Sort by Name and View | Sort by Item Designation commands to change
sorting.
To see relevant information, resize the columns Item Designation, Instance Name, and so on,
by dragging the divisions that separate the header parts at the top of the list box.
The divisions may be visible only if you enlarge the dialog box.

4-218 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

NOTES
Because the number of elements is not continually determined for this list, the
position of the scroll box does not reflect the position of the selected item in the
list. Nevertheless, all other features of the scrollbar are available.
The Function Chart Builder shows or hides DB elements implicitly created by
remote I/O elements (attribute: R), extended DB elements (attribute: X), and
AF100S DB elements (attribute: S) in the Item Designation, Instance Name,
Attr., Callname, Address list box depending on the Show Implicitly Created
Communication DB Elements preference option as set by Options |
Preferences.

Create
Activate this button to create the selected DB element.
For further actions and dialogs see the Edit | Create - for DB Section command.

Edit
Activate this button to modify the selected DB element.
For further actions and dialogs see the Edit | DB Terminal Values command.

NOTE
The DB elements implicitly created by remote I/O elements (attribute: R),
extended DB elements (attribute: X), and AF100S DB elements (attribute: S)
cannot be changed.

Delete
Activate this button to delete the selected DB element.

NOTE
The DB elements implicitly created by type circuits (attribute: T), remote I/O
elements (attribute: R), extended DB elements (attribute: X), and AF100S DB
elements (attribute: S) cannot be deleted on their own. If you delete a parent
element, also the DB elements implicitly created by it will be deleted.

Connect
Activate this button to connect the selected DB terminal and the PC terminal, which is selected
in the PC Section window.
If no DB terminal is selected explicitly, the VALUE terminal will be connected as default.
If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagram in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

3BDS 100 595R401 4-219

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.2.4 Symbol Section Window

Use this window to create, edit, or delete symbols, and to connect symbols to PC terminals.

Figure 4-137. Symbol Section Window

Title
The Title consists of the following items:
• A number in angle brackets
It serves as shortcut for opening the window when combined with ALT.
For example, <3> indicates the shortcut ALT+3.
• The name of the section
• The asterisk ‘*’ indicating that you modified the Symbol section since its opening
• An order number 1, 2, and so on, preceded by a colon ‘:’
It is used to differentiate between Symbol Section windows if more than one are available.

Filter/Name
Select a filter in the list box part or edit it directly in the text box part to show only symbols with
a certain name in the Name, Kind, Type, Default Value list box.
Wildcards ‘*’ and ‘?’ are also allowed.
Close the new filter condition with ENTER to make it effective.
The list box part contains the recently used filters.

4-220 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

Name
Shows (repeats) the name of the symbol, which is selected in the Name, Kind, Type, Default
Value list box.
You can also change the selection in the list by editing here.

Filter/Kind
Select a filter in the list box part or edit it directly in the text box part to show only symbols of a
certain kind in the Name, Kind, Type, Default Value list box.
Kinds Any, instance-unique (IU, not for node structure), location-unique (LU, only for circuit),
and project-unique (PU) are available.

Name, Kind, Type, Default Value

This list box shows the symbols, which satisfy the filter conditions, by their name, kind, type,
and default value.

Create
Activate this button to create a new symbol.
For further actions and dialogs see the Edit | Create - for Symbol Section command.

Edit
Activate this button to modify the selected symbol.
For further actions and dialogs see the Edit | Symbol command.

Delete
Activate this button to delete the selected symbol.

Connect
Activate this button to connect the selected symbol and the PC terminal, which is selected in the
PC Section window.
If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagram in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

3BDS 100 595R401 4-221

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.2.5 TC/CI Terminal Section Window

Use this window to create, edit, or delete type circuit terminals or circuit terminals, and to
connect them to PC terminals.

Figure 4-138. TC/CI Terminal Section Window

Title
The Title consists of the following items:
• A number in angle brackets
It serves as shortcut for opening the window when combined with ALT.
For example, <4> indicates the shortcut ALT+4.
• The name of the section
• The asterisk ‘*’ indicating that you modified the TC/CI terminal section since its opening
• An order number 1, 2, and so on, preceded by a colon ‘:’
It is used to differentiate between TC/CI Terminal Section windows if more than one are
available.

Filter/Name
Select a filter in the list box part or edit it directly in the text box part to list only terminals with
a certain name in the Name, No., Kind, Type, Default Connection list box.
Wildcards ‘*’ and ‘?’ are also allowed.
Close the new filter condition with ENTER to make it effective.
The list box part contains the recently used filters.

NOTE
Be sure to select the View | Sort by Name command if you want to see the TC/CI
terminals sorted alphabetically by name in the Name, No., Kind, Type, Default
Connection list box.

4-222 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

Name
Shows (repeats) the name of the terminal, which is selected in the Name, No., Kind, Type,
Default Connection list box.
You can also change the selection in the list by editing here.

Filter/Kind
Select a filter in the list box part or edit it directly in the text box part to show only terminals of
a certain kind in the Name, No., Kind, Type, Default Connection list box.
Kinds Any, FP, IN, and OUT are available.

Name, No., Kind, Type, Default Connection

This list box shows the terminals, which satisfy the filter conditions, by their name, number,
kind, type, and default value.
Use the View | Sort by Name and View | Sort by Number commands to change sorting.

Create
Activate this button to create a new terminal.
For further actions and dialogs see the Edit | Create - for TC/CI Terminal Section command.

Edit
Activate this button to modify the selected terminal.
For further actions and dialogs see the Edit | TC/CI Terminal command.

Delete
Activate this button to delete the selected terminal.

Connect
Activate this button to connect the selected TC/CI terminal and the PC terminal, which is
selected in the PC Section window.
If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagram in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

4.5.2.6 Output Window

In this window the Function Chart Builder displays lists, that is, source code lists, element lists,
—and in due case—warnings, error messages, and error statistics, in conjunction with the
following commands:
• File | Backtranslate Source
• File | Check PC Source
• File | Expand Node Structure

3BDS 100 595R401 4-223

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• File | Generate Source

• File | Generate Target Code
• Edit | Create (only if you instantiate a type circuit or locate a circuit)
• Edit | Paste
• Edit | Call Parameters
• Edit | Symbol Values
• View | Cross Reference
• PC-Terminal | Virtual Connections.
The Output window is opened or iconized during the execution of these commands depending
on the Minimize Output While Working option as set by the Options | Preferences
command.
You can select the whole contents of the Output window or a part of it. To operate on the
contents of the Output window, the commands Goto, Find, Copy, Select All, Save As, and
Print are available in a context menu. To open the context menu, click with the right mouse
button in the Output window.

Examples
1. Type descriptions and element libraries found at start-up of the Function Chart Builder
may differ from those referenced and used by the current object. The Function Chart
Builder displays the differences, if there are any, in the Output window.
2. The Function Chart Builder displays lists of DB and PC source code, and possibly,
warnings and error messages in the Output window during execution of the File |
Generate Source command.

Figure 4-139. Output Window

4.5.2.7 Name Table Window

In this window the Function Chart Builder displays the Name Table with all the names and
units, which are defined in the recently active PC Section window.
Use this window to inspect, create, and delete PC names and units, connect PC terminals by
name, and select a named item in the recently active PC Section window.

4-224 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

Figure 4-140. Name Table Window

Title
The Title consists of the following items:
• A number in angle brackets
It serves as shortcut for opening the window when combined with ALT.
For example, <5> indicates the shortcut ALT+5.
• The name of the table
• The asterisk ‘*’ indicating that you modified the Name Table since its opening
• An order number 1, 2, and so on, preceded by a colon ‘:’
It is used to differentiate between Name Table windows if more than one are available.

Filter/Name
Select a filter in the list box part or edit it directly in the text box part to list only certain names
in the Kind, Name, Unit, Item Designation list box.
Wildcards ‘*’ and ‘?’ are also allowed.
Close the new filter condition with ENTER to make it effective.
The list box part contains the recently used filters.

Name
Shows (repeats) the name, which is selected in the list box below.
You can also edit a new name here.

3BDS 100 595R401 4-225

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Filter Kind
Select one of the filter kinds All, PC Elements, PC Terminals in the list box part to list all or
only certain names in the Kind, Name, Unit, Item Designation list box.

Goto
Activate this button to select the PC terminal or PC element, pertaining to the selected name, in
the recently active PC Section window.

Kind, Name, Unit, Item Designation

Set the filters appropriately to show only a subset of existing PC names in the table.
In the Kind column, appropriate symbols stand for PC element and for PC terminal.
For the PC element kind this list box shows all the instance names, which satisfy the filter
conditions, and the item designations of the pertinent PC elements (or instantiated type circuits
or located circuits).
For the PC terminal kind this list box shows all the signal names, which satisfy the filter
conditions, and the item designations of PC terminals standing for sources, for which the names
serve as aliases. In this case the list box shows also the units if there are any attached to the
corresponding terminals (sources).

Name…
Activate this button to create or edit the name serving as alias for a source or as instance name
as applicable.
For further actions and dialogs see the Edit | Name command.

Unit…
Activate this button to create or edit the unit attached to a source having already a name.
For further actions and dialogs see the PC-Terminal | Unit | Create/Edit command.

Delete
Activate this button to delete the name (and unit) of a source or to delete an instance name as
applicable.
For further actions and dialogs see the Edit | Delete Name command.

Connect
Activate this button to connect the PC terminal, which is selected in the PC Section window,
by the selected name.
The button can be activated only for names of kind “PC terminal”.
If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagram in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

4-226 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

4.5.2.8 Test Table Window

In this window the Function Chart Builder displays the Test Table with PC, DB, or both kinds
of terminals that are forced, monitored, or both in your application. Trend recording of
monitored terminals is also available.

NOTE
Forcing and monitoring are possible only for connected AC 100 Series targets
and in on-line mode, but the Test Table can be prepared also in off-line mode.

Figure 4-141. Test Table Window

Table Contents
You can select filters to display all of the monitored and forced terminals in a Test Table
window or only a subset of them.
To overview and check the values of interest, you can resize the columns by dragging the
divisions that separate the header parts Instance, Terminal, and so on. You can change the
order of the columns by dragging the header parts to the required position. You can set or invert
the sort order by clicking on the header part, according to which you want to sort the entries.
You can insert PC and DB terminals in the table by the Edit | Create command or by the
Create/Edit… button of the List Entry group.
The entries are ordered as they were entered. Normally, the order is the input sequence. Select
any existing entry to insert a new entry immediately after it. If no item is selected—you achieve
it by holding down CTRL while clicking on the selected item—, the new item is inserted as
item 0, before all the rest.
Interpret the different values within the table as percent value or as physical value depending on
the PC or DB element and the related HW module.

3BDS 100 595R401 4-227

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

To see a value, for example, of type I or IL, also as 32 single bits or in hexadecimal format, click
with the right mouse button on it to open the Detailed Value Display dialog box.

Figure 4-142. Detailed Value Display

You can edit a selected item by the Edit | Create command or by the Create/Edit… button.
You can remove one or more selected items from the table by the Delete button. Deleted force
entries remain in the table with state ‘R’ until the deactivation of the values in the target.

Activation and Deactivation

Set an instance name filter, select one or several entries.
Activate and deactivate forcing of selected entries of the active Test Table window by the
Activate and Deactivate buttons of the Force group.
Activate and deactivate all force values of the whole Test Table by the Activate All and
Deactivate All buttons of the Force group.
The values are set on-line in the target. The Function Chart Builder updates the force values in
the Value on Target column.
Activate the buttons of the Display group to sample the display entries or to stop sampling.
You can also use the Test | Set Trigger command to define the condition, at the occurrence of
which cyclic monitoring stops automatically. Alternatively to the buttons of the Force and
Display groups you can use the corresponding Test | … commands.
The values are fetched on-line from the target. The Function Chart Builder updates the
monitored values in the Value on Target column.
NOTE
The display and force values in the Value on Target column are significant only if
the target is unblocked and all of the pertaining executable units are also
deblocked, that is, the RUN terminals of the pertaining PC structure elements are
set to 1, the IMPL and ACT terminals of the pertaining DB elements are set to 1.

The time stamp of Test Table contents appears in the Test Table windows and in the Status
Bar. It is date and time of the recent transfer of values from the target to the engineering station.
It is displayed only after successful Test | Single Display or Test | Cyclic Display commands or
after successful activation one of the buttons in the Display group.
Activate the Recording button to open the Trend Recording dialog box, configure it, and start
and stop recording.

4-228 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

Table Transfer, Save and Restore

Use the Test | Upload DB Force List command to read global force list of currently activated
forced DB elements from the on-line connected target. It is recommended to make an upload at
the start of each session to get the actual force state.
Use the Test | Export command to write the Test Table to a file.
Use the Test | Import command to load the Test Table from a file.
You can save the table explicitly by using the File | Save or File | Save and Load commands, or
if you leave the session, by using File | Exit command. If you execute the File | Skip
Modifications command, the modifications, which you made in the Test Table since the last
File | Save command during the current Function Chart Builder session, are lost.
The Function Chart Builder restores the recently saved items, if any, from the internal data
representation at the opening of the Test Table window.

NOTE
It is useful to check the Test Table to see whether or not there are any obsolete
force values restored from the last Function Chart Builder session.

Title
The Title consists of the following items:
• A number in angle brackets
It serves as shortcut for opening the window when combined with ALT.
For example, <4> indicates the shortcut ALT+4.
• The word On-line
If you just prepare the Test Table off-line, and the Function Chart Builder is not connected
on-line to an AC 100 Series target yet, the word On-line is missing in the Title. If it is
displayed, it indicates the following:
• The Test Table reflects conditions of the on-line connected AC 100 Series target.
• The modifications done in the Test Table window are—or can be—effective in the on-line
connected AC 100 Series target.
• The name of the table
• The asterisk ‘*’ indicating that you modified the Test Table window since its opening
• An order number 1, 2, and so on, preceded by a colon ‘:’ It is used to differentiate between
Test Table windows if more than one are available.

Inst. Name Filter

Select a filter in the list box part or edit it directly in the text box part to show only certain list
entries depending on the Instance column.
Wildcards ‘*’ and ‘?’ are also allowed.
Close the new filter condition with ENTER to make it effective.
The list box part contains the recently used filters.

3BDS 100 595R401 4-229

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Signal Select Filter

Select a filter in the list box part or edit it directly in the text box part to show only list entries of
a certain kind in the Instance, Terminal, …, State list box.
The allowed filters are All, All DB (Force & Display), All Display (DB & PC), All Force (DB
& PC), All PC (Force & Display), DB Display, DB Force, PC Display, and PC Force.

Instance, Terminal, …, State

This list box shows the entries pertaining to elements, which satisfy the filter conditions.
Resize the columns by dragging the divisions that separate the header parts Instance, Terminal,
and so on. Some divisions may be visible only if you enlarge the window.
Change the order of the columns by dragging the header parts to the required position.
Set or invert the sort order by clicking on the header part, according to which you want to sort
the entries. An icon or in the corresponding header part indicates the sorting.

Table 4-23. Columns in the Test Table Window

Column Description
(#) Natural order number of items (0, 2,...) assigned at their creation.
Instance This column identifies the signal or the PC or DB instance, which is
the source of the signal, by
• the signal name if available,
• else the instance name of the PC or DB instance if available,
• else the item designation of the PC or DB instance.
DB signals are preceded by an equal sign ‘=’.
Terminal Terminal name of the terminal if available, else its terminal number.
Force Value Value to be forced to when the entry is activated.
It is empty if the table entry is a display entry.
This value need not be identical with the value on target because
another tool may force another value.
Value on Target The value that is active in the target and effective for the process.
For force entries it is the active forced value.
For display entries it is the value monitored in the target.
Values are significant only if the target is unblocked and all of the
pertaining executable units are also deblocked. Question marks `?´
indicate that no values are fetched from the target yet. Value `X´ of
PC terminals indicates that the PC program is blocked yet.
Physical Unit Physical unit of the value, for example, m/s, bar, if specified.
Type Data type of signal value, for example, R, I, IL, B.
Description DESCR terminal of the DB terminal if available.
State Reflects the kind and state of the entries, see Table 4-24.

4-230 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

The following states are possible:

Table 4-24. Kind and State of Entries in the Test Table

Entry Kind State Indicator State Description

Display Monitoring (display) is prepared for the terminal,
D
no forcing.
Force P Force value is prepared.
F Force value is activated.
Force value is removed in the Test Table
R
but it may yet be active on the target.

Date and Time

Time stamp of Test Table contents.
It is date and time of the recent transfer of values from the target to the engineering station.
It is displayed only after successful Test | Single Display or Test | Cyclic Display commands or
after successful activation one the corresponding buttons in the Display group.
If the target is blocked or stopped, the Function Chart Builder warns you in the Status Bar:
(TARGET BLOCKED)
In this case you cannot expect new display values.

Trigger Information
A static text appears here if some trigger condition is defined by the Test | Set Trigger
command for stopping cyclic monitoring. The text reflects whether
• The trigger condition is enabled or disabled
• Cyclic display is stopped by trigger condition.

Create/Edit
Activate this button to create a new display or force entry or edit the selected entry in the
Instance, Terminal, …, State list box.
For further actions and dialogs see Section 4.5.5.3, Edit | Create… - for Test Table.

Delete
Activate this button to delete one or more selected entries in the
Instance, Terminal, …, State list box.
Deleted force entries remain in the table with state ‘R’ until the deactivation of the values in the
target.

Activate
Activate this button to activate the selected force entries in the Instance, Terminal, …, State
list box. It has the same effect as selecting the Test Table window and choosing the
Test | Activate Force Values command.

3BDS 100 595R401 4-231

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Activate All
Activate this button to activate all—visible and invisible—force entries of the Test Table.
It has the same effect as selecting the Test Table window and choosing the
Test | Activate All Force Values command.

Deactivate
Activate this button to deactivate the selected force entries in the Instance, Terminal, …, State
list box.
It has the same effect as selecting the Test Table window and choosing the
Test | Deactivate Force Values command.

Deactivate All
Activate this button to deactivate all—visible and invisible—force entries in the Test Table.
It has the same effect as selecting the Test Table window and choosing the
Test | Deactivate All Force Values command.

All
If this check box is not checked, the Force group offers the Activate and Deactivate buttons.
If this check box is checked, the Force group offers the Activate All and Deactivate All
buttons.

Single
Activate this button to sample all—visible and invisible—display entries in the Instance,
Terminal, …, State list box once.
The Function Chart Builder updates the corresponding values in the
Instance, Terminal, …, State list box.
It has the same effect as selecting the Test Table window and choosing the
Test | Single Display command.

Cyclic
Activate this button to sample all—visible and invisible—display entries in the Instance,
Terminal, …, State list box continuously.
The Function Chart Builder attempts to sample the display entries in the target and update the
corresponding values in the Instance, Terminal, …, State list box with the cycletime defined
by the Test | Set Cycletime command or as stored as workspace-specific parameter.
It has the same effect as selecting the Test Table window and choosing the
Test | Cyclic Display command.

Stop
Activate this button to stop sampling display entries in the target.
It has the same effect as selecting the Test Table window and choosing the Test | Stop Display
command.

4-232 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

Recording
Activate the Recording button to open the Trend Recording dialog box, configure it, and start
and stop recording.

Figure 4-143. Trend Recording Dialog Box

Use this dialog box to scale and setup trend recording of signals selected in the pertaining
Test Table, and to display their trend curves.
Activate the Setup button to open the Setup dialog.
Activate the Details button to open the Value List of Trend Recording.
You can save the recorded trend in a *.GLX file, generally in the LIST subdirectory of the node.
You can inspect trends saved in *:GLX files by AS100-EDIT (or by Microsoft Excel).

Vertical Scale
An own scale is prepared for each displayed value, but for clarity only one scale is shown at a
time. You can switch between different scales with the < and > buttons below the scale.
In this example in the figure the scale is shifted by an offset of one. With an offset you can
adjust different signals—especially binary signals—so that they do not overlap each other.

Scale Switch
You can switch between different vertical scales with the < and > buttons.

Trend
This area contains the recorded trend curves of selected signals corresponding to the common
horizontal time scale.

3BDS 100 595R401 4-233

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Marker
The marker is a vertical, broken line.
You can set it by clicking at the desired position in the trend.
Activate the Details button to see the values at the marker position.

Time Scrolling
You can scroll within the area of the horizontal time scale with the <<, <, >, and >> buttons.
With < and > the display will be scrolled by one unit, while << and >> scroll ten units when
pressed.

Recording Status
Shows the actual status of trend recording.
Examples
Logging data ...
Logging stopped.

Setup Button
Activate this button to open the Setup dialog of Trend Recording:

Figure 4-144. Setup of Trend Recording

Specify for each value listed in the Value list box the arrangement of the vertical scale and style
and color of the displayed curve.
Activate the Time - Scale button to adjust the common time scale for all signals.
Activate the Trigger button to define a common trigger condition for all signals.

• Value
Signals selected in the pertaining Test Table window are listed in the Value list box.
A total of 20 signals can be registered.
The signal name is displayed in the color selected for the trend curve of the signal.
Values in the Vertical Scale and Style groups belong to the signal selected in Value.

4-234 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

• Vertical Scale - Values

Defines the principal spread of the vertical axis. Select one of the possible values:
– Positive: only positive values will be displayed
– Negative: only negative values will be displayed
– Positive/Negative: both positive and negative values will be displayed
– With offset: the scale is shifted by an offset.

• Vertical Scale - Offset

Specify an offset as an integer or real number in the field to separate the trend curves of
different signals.

• Vertical Scale - Range

Specify the range of the vertical scale in powers of ten.
If the scale shall extend for example from -100 to +100, type 2 in the Range field and
select positive/negative in the Values box.

• Style - Line Style

Select one of the three different styles for painting the thickness of the curve
Normal - Bold - Double Bold.

• Style - Color
Press this button to open a color table.

Figure 4-145. Color Table

Select a color here.

The curve and the corresponding texts will be drawn with the selected color.

3BDS 100 595R401 4-235

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Time - Scale Button

Activate this button to open the Time Scale dialog:

Figure 4-146. Time - Scale

Specify the common time scale, sample time, and time display notation for all signals here.
Time Scale Unit
Specify here the units of the horizontal time scale. The available times range from 1s to 1h.
Sample Time
Specify here the cyclicity of reading data from the Advant Controller 100 Series
A sample time of 10s means that the values will be read once in 10s.

NOTES
The sample time cannot be greater than the time scale unit. Further on, the
number of display points is restricted. Therefore the shorter sample times are not
available for long time scale units.
There is no direct synchronization between Advant Controller 100 Series and the
engineering station.
To get a value from each cycle of Advant Controller 100 Series, select a sample
time that is shorter than the cycle time of the corresponding PC program.
If you select short sample times, a warning message will be displayed. It informs
you that the recording of data may lead to problems if the overall load on the
target is higher than 85%. This may lead to a longer effective cycle time.

Time Display
Relative time display means that the time notation at the ticks of the time scale will be
relative to the start of data recording. Absolute time display means notation according to
the day time. The clock of the Advant Controller 100 Series will be used for the display.

• Trigger Button
Activate this button to open the Trigger Setup dialog:

4-236 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

Figure 4-147. Trigger Setup

Specify the trigger condition and operation for recording here.

You can define an event and an action that shall take place when the event occurs.
An example of an event may be that a signal exceeds a defined threshold. When this
happens, recording of values may start or stop. The detection of the event does not take
place on the Advant Controller 100 Series, but on the engineering station with the data
read from the controller.
NOTE
There is no direct synchronization between Advant Controller 100 Series and the
engineering station. If you want to assure that you will get a value from each
cycle of the Advant Controller 100 Series, select a sample time that is shorter
than the cycle time of the corresponding PC program.

Formula
The formula is a valid expression which may contain values, constants, operators, and
indexes for values.
Value: Any signal that has been selected in the pertaining Test Table window.
You can pick up a name from the Available Variable Names drop-down box
and insert it into the Formula field by copy and paste.
Constant: Any constant like 2 or 50.5.
Operator: ==, <, <=, >, >=, +, -, *, /, (, ), AND, OR, XOR, NOT.
Index: signal_name [n]; with -10 <= n <= -1.
A signal name without an index means the current value, signal_name [-1]
means the foregoing value, and so on.
Example: A formula to detect a positive slope of a curve may look like this:
(CURRENT_VAL - CURRENT_VAL[-1])>0

3BDS 100 595R401 4-237

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Available Variable Names

A list containing the values selected in the pertaining Test Table window.
Use copy and paste to pick up values from this list and to insert them into the Formula.
Trigger Type
Disable: The trigger is disabled independent of the formula.
Start if condition is TRUE: Means recording will be started when condition is true.
Depending on the Trigger Length value, the specified number of values will
be recorded after the event occurred. Then the recording stops.
Stop if condition is TRUE: Means recording will be stopped when condition is true.
Depending on the Trigger Length value, at maximum the specified number of
values will be recorded before the event occurs. If the event occurs earlier, the
number of recorded data points corresponds to the time between start of
recording and the event.
Center trigger event: Means the recording tries to keep the event centered in the amount of
recorded data points.
When, for example, the Trigger Length is set to 1000, the recording tries to
retain 500 data points before and catch further 500 data points after the event.
If the event occurs earlier, for example, at data point 200, still further 800 data
points will be recorded after the occurrence of the event.
Trigger Length
Its value defines a continuous area of data points around the triggered event. The length is
specified in time scale units. How the area is arranged around the triggered event depends
on the Trigger Type value.

Details Button
Activate this button to open the Value List of Trend Recording:

Figure 4-148. Value List of Trend Recording

It shows either the newest values or the values at the marker position.
The marker—when positioned—is presented as a vertical, broken line. You can set the marker
by clicking at the desired position into the display.

4-238 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

4.5.2.9 Status Report Window

In this window the Function Chart Builder displays the status of the node and the application
program as defined and stored in the following system components:
• The engineering station
• The RAM of the on-line connected target
• The PROM of the on-line connected target.

Figure 4-149. Status Report

Compare the data.

The node and the application program are identified in the following form:
name DB_time_stamp PCPGM_number PC_time_stamp
For successful on-line operations node and application program descriptions must be identical
in the Node on AS 100ES and in the Target RAM columns.
In case of errors you can start the Diagnostics (Diagnosis) program attached to the Function
Chart Builder.

Title
The number in angle brackets is the key that serves as shortcut for the window when combined
with ALT. For example, <3> indicates the shortcut ALT+3.

Date and Time

Time stamp of Status Report contents.

3BDS 100 595R401 4-239

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Node on AS 100ES
Data describing the node and the application program as defined in the engineering station.

Target RAM
Data describing the on-line connected target and the application program stored in its RAM.

Differences
The “not equal” sign ‘<>’ points out the differences between the columns Node on AS 100ES,
Target RAM, and Target PROM.

Target PROM
Data describing the on-line connected target and the application program stored in its PROM.

PCPGM State
State of the application program in the on-line connected target is Deblocked (running) or
Blocked (stopped).

Free Memory
Free memory space in the RAM of the on-line connected target.

No errors detected / Errors detected

The static text version reflects whether some errors were recently detected in the on-line
connected target or not.
If errors are detected, the Report Errors button is enabled, else it is disabled and dimmed.

Report Errors
This button is displayed only if some errors were recently detected in on-line connected target.
Activate it to trigger the following actions:
1. Start the Diagnostics (Diagnosis) program attached to the Function Chart Builder.
2. The Diagnostics (Diagnosis) program reads the errors reported from the on-line connected
target.
The target reports all errors collected since the last clear by an appropriate diagnostic
command.
3. The Diagnostics (Diagnosis) program displays the reported errors in the Error Report
window.

4-240 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.2 Controls in Document Windows

4.5.2.10 Options Report Window

In this window the Function Chart Builder displays the options of the node and the base
software as defined and stored in the engineering station and the on-line connected target.

Figure 4-150. Options Report

Compare the data.

The options and the base software are identified in the following form:
ident_string major_release . minor_release / revision
The conditions of successful on-line operations are the following:
• The base software and all the options selected in the engineering station must be available
in the on-line connected target.
• The ident_string, major_release, and minor_release of the item selected in the engineering
station must equal the ident_string, major_release, and minor_release of the
corresponding item on the target. So revision is not evaluated.
Title
The number in angle brackets is the key that serves as shortcut for the window when combined
with ALT. For example, <5> indicates the shortcut for ALT+5.
Date and Time
Time stamp of Options Report contents.
On AS 100ES Selected, On Target Available
Options selected in the engineering station and the ones available on the target, respectively.
Differences
The “not equal” sign ‘<>’ points out the differences between the columns On AS 100ES
Selected and On Target Available, both for options and base software version.
Base Software on AS 100ES, Base Software of Target
Base software supported by the engineering station and base software of the target, respectively.

3BDS 100 595R401 4-241

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.2.11 Diagnostics, Error Report Window

Diagnostics is a program attached to the Function Chart Builder and having an own application
window, document windows, such as Error Report, own menus, and commands.
Use it to diagnose an on-line connected AC 100 Series target.

NOTE
The Diagnostics program is adapted to the different diagnostics features of both
former and recent controller versions.
In case of AC 110 2.0, AC 70 1.0, and AC 55 1.0 it is called the Diagnosis
program.
In case of AC 100 Series targets of newer node types, such as AC 160, AC 110
2.1 and higher, AC 80, AC 70 1.1 and higher, and AC 55 1.1, it is called the
Diagnostics program.

You can start Diagnostics (Diagnosis) only from within the Function Chart Builder.
When started, Diagnosis opens its Error Report window.
In case of Diagnostics you may have to open a similar Error Report window explicitly.

Figure 4-151. Application Window of Diagnosis, Error Report

If you are working with a target of node type AC 110 2.0, AC 70 1.0, and AC 55 1.0, for further
information see Section 4.5.22, Controls of Diagnosis, Section 4.5.23, Controls in Document
Windows of Diagnosis, and Section 4.5.24, Menu Commands of Diagnosis.
If you are working with a AC 100 Series target of newer node type, such as AC 160, AC 110 2.1
and higher, AC 80, AC 70 1.1 and higher, and AC 55 1.1, for further information see Section
4.5.14, Controls of Diagnostics, Section 4.5.15, Controls in Document Windows of Diagnostics,
and Section 4.5.16, Menu Commands of Diagnostics.

4-242 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.3 On Menu Commands, General

4.5.3 On Menu Commands, General

You control FCB by using commands. You choose them from menus or from the Toolbar by the
mouse or call them up by accelerator keys or shortcuts using the keyboard.
The Menu Bar is displayed across the top of the application window, below the Title Bar.
The Menu Bar contains the menus of the Function Chart Builder.

Figure 4-152. Menu Bar of the Function Chart Builder

When you choose a command, the Function Chart Builder executes it and/or changes its own
state. The state of the Function Chart Builder depends mainly on the following conditions:
• Is the selected object, on which you are working, a node structure, a circuit, a type circuit,
or a node?
• Are you editing PC program (in function chart or tree diagram representation), DB section,
symbols, or TC/CI terminals?
• What are you using the Function Chart Builder for?
– An Advant Controller 400 Series or MasterPiece 200/1 target (standard node types)
– An Advant Controller 100 Series target (standard node types)
– Some special target developed by an ABB business unit (additional node types).
• Are you working in on-line mode? (Is the engineering station connected on-line to an
AC 100 Series target? Are the program prepared with the Function Chart Builder and the
program, which is running in the connected Advant Controller AC 100 Series target,
identical?)
Depending on its state and on the document window having the focus, the Function Chart
Builder offers only a subset of its commands. So, if you pull down a menu, several commands
may be dimmed.
Additional node types may specify additional menu items or modified functions for the standard
Function Chart Builder menu items. These variants are displayed and valid if you are working
on an object of such a node type.
For documentation about features depending on additional node types turn to their developer or
supplier.
The Function Chart Builder displays the menus and their menu items on the screen in a non-
alphabetical order that reflects the logical execution sequence or the groups of related functions.
The Contents of Function Chart Builder Help lists the menu commands also in this order.
The commands are denoted in menu | menu_option or menu | menu_option | submenu_option
form.
The menus correspond to the de-facto Windows standard:
• Items having submenus are designated with a greater-then sign ‘>’ or a right-pointing
triangle.
• Items, which display dialog boxes for full specification of the command, are designated
with an ellipsis (…).
• The accelerator keys are denoted by underline.
• If a command has a shortcut key, it is displayed next to the command in the menu or
submenu.

3BDS 100 595R401 4-243

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.4 File Menu

4.5.4.1 File | Initialize

Use this command to initialize the *.ODB file, that is, the Function Chart Builder’s internal data
representation of the object, for which you started the Function Chart Builder.

CAUTION
This function deletes the existing *.ODB file containing the internal data
representation of the Function Chart Builder and creates a new, empty one for the
object, on which you are going to work. You will lose all information you entered
previously for this object and saved in its *.ODB file by the File | Save or
File | Exit command. Source code and print files are not affected by Initialize.

The Function Chart Builder asks you to confirm the initialization.

If you answer Yes, the Function Chart Builder initializes the internal data representation of the
object and creates system DB elements (generally not for AC 100 Series objects).
If you started the Function Chart Builder for the first time on a new object and no project default
page layout was defined in the Application Builder, the Function Chart Builder presents the
Page Setup dialog box, where you have to define the page layout for your diagrams.
See Section 4.5.4.24, File | Page Setup… for dialog.

4.5.4.2 File | Rebuild Element Types

Use this command to re-scan options, element libraries, and referenced objects of the current
object, to make system defaults saved in the object-specific DBGENDEF.BAX file effective
(instead of the ones defined in the current DB element library), and to rebuild the list of
available PC and DB elements and of available type circuits and circuits, as applicable.
Generally, you use this command in following cases:
1. You are working on an object with the Function Chart Builder. You change the options,
hence the element libraries, for this object with the Application Builder. Or you create a
new DB element type with the PROFIBUS Library Editor. With this command, you let the
Function Chart Builder take the new elements into account “on the fly”, without exiting
and restarting it.
2. You are working on a node with the Function Chart Builder. You add or delete some type
circuits with the Application Builder or in other sessions of the Function Chart Builder
(that is, with other instances of the Function Chart Builder). With this command, you let
the Function Chart Builder take the changed set of available type circuits into account
“on the fly”, without interrupting your first Function Chart Builder session.
3. You are working on a node with the Function Chart Builder. To achieve a DB source code
size reduction or to reflect your default I/O address assignments you change the
DBGENDEF.BAX file with AS100-EDIT. With this command, you let the Function Chart
Builder take the changed system defaults (DB general defaults) into account “on the fly”,
without interrupting your first Function Chart Builder session.

4-244 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

NOTES
File | Rebuild Element Types has the same effect as File | Exit and a subsequent
restart on the same object by Tools | Function Chart Builder or Tools | Node
Structure Function Chart Builder in the Application Builder.
File | Rebuild Element Types leaves PC and DB element, type circuit, and
circuit instances unchanged, it does not re-instantiate them.

4.5.4.3 File | New Section >

Submenus:

File | New Section | PC… - for Node and NS

Use this command to create a new PC program of the selected node or node structure.

Figure 4-153. New PC Program

• PC Program
The Function Chart Builder displays the numbers of already existing PC programs in the
list box part.
Type the name of the PC program to be created in the text box part in PCpp form, where
the PC program number pp may have any of the free values in the range 1 - 99.
After you defined the new PC program, the Function Chart Builder displays the Create
Element dialog box. For dialog see Section 4.5.5.3, Edit | Create… - for PC Section.
Insert here a PCPGM element as top element.
The Function Chart Builder opens the PC Section window of the selected PC program and
shows the created PCPGM.
Create further PC elements there.

File | New Section | PC… - for CI and TC

Use this command to create the PC section of the selected type circuit or circuit.
The Function Chart Builder displays the Create Element dialog box.
For dialog see Section 4.5.5.3, Edit | Create… - for PC Section.
Insert here any but the PCPGM element as top element.

3BDS 100 595R401 4-245

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder opens the PC Section window of the selected type circuit or circuit
and shows the created PC element.
Create further PC elements there.

File | New Section | DB

Use this command to create the DB section of the selected node, node structure, circuit, or type
circuit.
The Function Chart Builder opens the empty DB Section window of the selected object and
displays the Create Element dialog box.
For dialog see Section 4.5.5.3, Edit | Create… - for DB Section.
Create DB elements there.

File | New Section | Symbol

Use this command to create the symbol section of the selected node structure, circuit, or type
circuit.
The Function Chart Builder opens the empty Symbol Section window of the selected node
structure, circuit, or type circuit, and displays the Create Symbol dialog box
For dialog see Section 4.5.5.3, Edit | Create… - for Symbol Section.
Create symbols there.

File | New Section | TC/CI Terminal

Use this command to create the TC/CI terminal section of the selected circuit or type circuit.
The Function Chart Builder opens the empty TC/CI Terminal Section window of the selected
circuit or type circuit, and displays the Create TC/CI Terminal dialog box.
For dialog see Section 4.5.5.3, Edit | Create… - for TC/CI Terminal Section.
Create TC/CI terminals there.

4.5.4.4 File | Open Section >

Submenus:

File | Open Section | PC… - for Node and NS

Use this command to open an existing PC program of the selected node or node structure.

Figure 4-154. Open PC Program

4-246 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

• PC Program
The Function Chart Builder displays the numbers of available PC programs in the list box.
Select the name of the one to be opened in the list box or edit it in the text box in PCpp
form, where PC program number pp may have any of the listed values in the range 1 - 99.
After you selected the PC program, the Function Chart Builder opens its PC Section window.

File | Open Section | PC - for CI and TC

Use this command to open the PC section of the selected type circuit or circuit.
The Function Chart Builder opens the PC Section window of the selected type circuit or circuit.

File | Open Section | DB

Use this command to open the DB section of the selected node, node structure, circuit, or type
circuit. The Function Chart Builder opens the DB Section window of the selected object and
lists its DB elements and further objects, which create or modify DB elements.

File | Open Section | Symbol

Use this command to open the symbol section of the selected node structure, circuit, or type
circuit. The Function Chart Builder opens the Symbol Section window and lists the existing
symbols of the selected node structure, circuit, or type circuit.

File | Open Section | TC/CI Terminal

Use this command to open the TC/CI terminal section of the selected type circuit or circuit.
The Function Chart Builder opens the TC/CI Terminal Section window of the selected type
circuit or circuit and lists its TC/CI terminals.

4.5.4.5 File | Delete Section >

Submenus:

File | Delete Section | PC… - for Node and NS

Use this command to delete a PC program of the selected node or node structure.

Figure 4-155. Delete PC Program

3BDS 100 595R401 4-247

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• PC Program
Select the PC program to be deleted from the list box part, which contains all available PC
programs of the selected node or node structure, or edit its name in the text box part.
The Function Chart Builder asks you to confirm the deletion.
CAUTION
This function deletes the selected PC program of the node or node structure in the
*.ODB file containing the internal data representation of the Function Chart
Builder. You will lose all information you entered previously for this PC program
of the selected object and saved in its *.ODB file by the File | Save or File | Exit
command. AMPL source code, node structure source code, and print files are not
affected by Delete Section.
If you answer Yes, the Function Chart Builder deletes the selected PC program.

File | Delete Section | PC - for CI and TC

Use this command to delete the PC section of the selected circuit or type circuit.
CAUTION
This function deletes the PC section of the circuit or type circuit in the *.ODB file
containing the internal data representation of the Function Chart Builder. You will
lose all information you entered previously for the PC section of the selected
object and saved in its *.ODB file by the File | Save or File | Exit command.
Circuit source code, type circuit source code, and print files are not affected by
Delete Section.

File | Delete Section | DB

File | Delete Section | Symbol
File | Delete Section | TC/CI Terminal
(These commands are not implemented yet.)

4.5.4.6 File | On-line Mode

Toggle switch.
Use this command to toggle explicitly between off-line connected mode and on-line mode.
The command is available only for connected AC 100 Series targets.
A check mark ‘ ’ appears next to the menu item when the Function Chart Builder is in on-line
mode.

4.5.4.7 File | On-line Preparation Mode

Toggle switch.
Use this command to toggle explicitly between off-line (non-connected) mode and on-line
preparation mode.
The command is available only for AC 100 Series nodes and if the loaded application in the
target differs from the one in the internal data representation by at most one executable unit.
A check mark ‘ ’ appears next to the menu item when the Function Chart Builder is in on-line
preparation mode.

4-248 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

NOTES
To reach on-line preparation mode, the Function Chart Builder has to have passed
the on-line mode at least once with a given application for a target system.
In on-line preparation mode, you can connect also any other target system.
The on-line preparation mode regains its meaning only when you reconnect the
same target system, with which you worked in on-line mode.

4.5.4.8 File | Save

Shortcut: CTRL+S
Use this command to save in the internal data representation of the Function Chart Builder all
the modifications that you made in the following windows:
• PC Section windows
• DB Section windows
• Symbol Section windows
• TC/CI Terminal Section windows
• Name Table windows.
In case of AC 100 Series objects also the modifications in the Test Table windows are saved.
If you start the Function Chart Builder for the same object the next time, the contents of these
windows are automatically restored.

4.5.4.9 File | Save and Load

Shortcut: CTRL+S
Use this command to save in the internal data representation of the Function Chart Builder all
the modifications that you made in the following windows concerning an AC 100 Series node:
• PC Section windows
• DB Section windows
• Name Table windows
• Test Table windows.
Furthermore, use this command to translate and load the changes to the AC 100 Series target,
and to activate the changes. This command is available only in on-line mode.
The target code corresponding to the changes is implicitly generated with the same options as
set at the last explicit target code generation by File | Generate Target Code for this target.
The Function Chart Builder opens the Output window, protocols there the target code
generation for the changed executable unit and the download process.
If you start the Function Chart Builder for the same node the next time, the contents of these
windows are automatically restored.

4.5.4.10 File | Skip Modifications

Use this command to skip modifications, which you made during the current Function Chart
Builder session since the last File | Save or File | Save and Load, in the following windows:
• PC Section windows
• DB Section windows
• Symbol Section windows
• TC/CI Terminal Section windows
• Name Table windows
• Test Table windows.

3BDS 100 595R401 4-249

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder asks you to confirm skipping.

CAUTION
If you answer Yes, you lose all the changes that you made since the last
File | Save, File | Save and Load, or File | Exit command. You cannot undo this
command. Source code and print files are not affected by Skip Modifications.

4.5.4.11 File | Set Password…

Use this command to set, change, and clear an ODB password.
In this chapter all functions described for nodes also apply to Type Circuits and Circuits.
Function Chart Builder offers protection of manipulations by unauthorized persons. Every node
may have a different password.
For every node the degree of protection is selectable on three levels:
1. Lock the access to the complete Function Chart Builder.
2. Lock function changing the *.ODB file containing the internal data representation of the
object you are working on. The Function Chart Builder works in “View Mode”.
3. Lock all functions but Target Control function. The Function Chart Builder works in
“Loader Mode”.

CAUTION
Use password protection only if it is reasonable. Be aware that there is no “back
door” or “universal password” if you forget the password. File | Initialize does
not clear the password. On the other side, files other than *.ODB, for example
source code files, are not protected.

4-250 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

The following figure shows the Set Password dialog.:

Figure 4-156. Set Password in ODB

• Old Password
Enter here the old password if there is any.
Be sure using lower case and upper case correctly.

• New Password
Enter here the new password if you want to set one.
The password has to consist of 8 to 50 printable characters.
Leave this text box empty if you want to clear the password.

• Confirm New Password

Repeat here the new password if you want to set one.
Leave this text box empty if you want to clear the password.

• Set Access Mode

Check access mode that shall be used.
The protection with the new password is takes effect at the next start of FCB with the same node
in case you select “User Needs to Enter Password on FCB Startup ...”. In case “User can View
Node ...” and “User can use AC 100 Target Control Function ONLY ...” the passwords takes
affect after leaving the File > Set Password dialog.
NOTE
Do not mix up the ODB password with the target password. See Section
4.5.10.12, Target | Set Password…. Nevertheless, if the ODB password equals the

3BDS 100 595R401 4-251

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

target password, the user does not need to enter the same password again when
connecting to a protected target.

4.5.4.12 File | Generate Target Code…

Use this command to generate target code for an AC 100 Series node from its internal data
representation.

Figure 4-157. Generate Target Code

In case of AC 100 Series nodes supporting application retrieval (upload and backtranslation of
target code), the Function Chart Builder displays also check boxes to generate also additional,

4-252 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

complete information for storing in and later retrieval from the target.
See Section 4.5.4.19, File | Backtranslate Target Code.

Figure 4-158. Generate Target Code with Support for Application Retrieval

The selections are effective during target code generation and File | Save and Load.

• PC Section
Select this check box to generate PC parts of the target code.
PCpp shows the current and only PC program.

• DB Section
Select this check box to generate DB part of the target code.

• Generate Information for HMI

Bus Configuration Database
Select this check box to fill also the Bus Configuration Database with data about AF 100
connections of the AC 100 Series node from its internal data representation.
In the DB section of the AC 100 Series node the Function Chart Builder checks the
conditions of AF 100 communication: it looks for a PM# processor module,
communication interfaces such as CI626, and DSP# DataSet elements. (Hash mark `#´ is
wildcard.) Then it fills the Bus Configuration Database of the node with the found
elements.
The completed Bus Configuration Database and the Bus Configuration Builder are used
for projecting and checking AF 100 networks and calculating AF 100 bus load. They are
necessary for supporting Human-System Interfaces and facilitating access of process
signals.

3BDS 100 595R401 4-253

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

All DSPs Visible in AF100 OPC

This check box is available if Bus Configuration Database is selected.
Select this check box to create automatically DAT_DAT elements for all DAT elements
referenced on some REFj terminals of the DSPi elements and fill the Bus Configuration
Database during target code generation also with them.
The generated DAT_DAT elements get the following values:
NAME= AUTO_HMI_i . *
where i is the number (index) of the given DSP element
and j is the number (index) of the given REF terminal
OBJ_NAME= nameOfReferencedDAT
that is, value of the given DSPi:REFj terminal
DAT_OBJ= nameOfReferencedDAT
that is, value of the given DSPi:REFj terminal.
Through DAT_DAT DB elements the AF100 OCP makes DAT DB elements visible for
Human-System Interfaces.

NOTE
Automatically created DAT_DAT elements do not appear in the *.ODB file.

Unselect this check box to suppress automatic generation of such DAT_DAT elements.
This is recommended if you have manually created DAT_AI, DAT_AO, DAT_DAT,
DAT_DI, and DAT_DO elements for making the corresponding referenced elements
visible for Human-System Interfaces.

NOTE
Avoid mixing manual and automatic creation DAT_* elements.

BOIL, COIL
Select these check boxes to prepare data about AF 100 connections of the AC 100 Series
node in BOILnnnn.C00 and COILnnnn.C00 files for programming AdvaSoft for Windows
nodes.

• Include Complete Information for

Select the check boxes to include corresponding additional, complete information in the
target code. The selection determines the scope of the later application retrieval from the
target. It sets also the scope of the substantial changes allowed at once in on-line mode and
on-line preparation mode. Each item costs memory on the target and download time.
Libraries
The target description and the DB and PC element libraries (PC and DB element
descriptions) will be added to the target code. This can be important especially for later
retrieval of derived, modified, and user-defined libraries.
If this check box is not selected, successful retrieval is possible only if identical versions of
target description and DB and PC element libraries are available for the Function Chart
Builder.
DB Elements
Names of DB elements will be added to the target code.

4-254 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

PC Elements
Names of PC elements and PC signals will be added to the target code.
Type Circuits
Type circuit files *.TCS, *.TBX, and *.TIX will be added to the target code.
If this check box is not selected, type circuit instance remain disintegrated.
Documentation
Information for documentation, such as item designation of elements, page divisions, texts
of headers and footers, and footer template (*.TPX file), will be added to target code.
NOTES
Due to the complexity of some type circuits, the Function Chart Builder may
reject to generate target code for nodes containing instances of such type circuits
in non-disintegrated form.
In this case, generate source code for the node, backtranslate it, and at the same
time, disintegrate the type circuit instances in the node. (Be sure to select the
Disintegrate TCs check box in the dialog box of File | Backtranslate Source.)

If there are changes in the DB section, generate target code for both sections,
or generate target code at first for the DB section and then for the PC section.
The Function Chart Builder opens the Output window (or iconizes it as set by Options |
Preferences), and lists messages about progress and termination of the target code generation.
The Function Chart Builder generates the DB target code in *.C00 form and a listing in
COTL0000.C00 form, and stores them in the \DBDATA subdirectory of the node.
The Function Chart Builder generates the PC target code files in *.Cpp (pp = PC program
number) form and a listing in RETL0000.Cpp form, and stores them in the \PCDATA
subdirectory of the node.
NOTE
Additional node types may specify another function for the File | Generate
Target Code standard menu item than described here. The modified function is
valid if you are working on an object of such a node type. See Section 4.5.4.13,
File | Generate Target Code (External).

4.5.4.13 File | Generate Target Code (External)

Use this command to generate target code for a target of non-standard node type from its
internal data representation.
NOTES
This is a modified (non-standard) menu command.
It is specified by the node type of the object you are working on.
Some ABB business units (BUs) develop additional (non-standard) node types
and options. Additional node types may specify also additional menu items for
the Function Chart Builder or assign modified functions to the standard menu
items. These variants are displayed and valid if you are working on an object of
such a node type.

3BDS 100 595R401 4-255

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder generates temporary AMPL source code for the PC section in
node.AAX form and stores it in the \CONTROL subdirectory of the node.
Then it starts the external target code generator specified for the command by the additional
node type and/or option of the node you are working on.
The external target code generator generates target code necessary for the non-standard target
on the basis of the temporary source code node.AAX.
For the documentation of the external target code generator turn to its developer or supplier.

4.5.4.14 File | Generate BCD Data

This command is available only if you are working on an AC 400 Series node with AF 100
interface or MB 300 interface and the Bus Configuration Builder is installed.
Use this command to fill the Bus Configuration Database with data about AF 100 and MB 300
connections of the AC 400 Series node from its internal data representation.

Figure 4-159. Generate BCD Data

The completed Bus Configuration Database and the Bus Configuration Builder are used for
projecting and checking AF 100 networks and calculating AF 100 bus load. They are necessary
for supporting Human-System Interfaces and facilitating access of process signals.

AF 100
Select this check box to generate BCD data for Advant Fieldbus 100.
In the DB section of the AC 400 Series node the Function Chart Builder checks the conditions
of AF 100 communication: it looks for a PM# processor module, one or more AF100_#
communication interface, and DSP# DataSet elements, the USER terminal of the latter having
other value than 4. (Hash mark ‘#’ is wildcard; USER=4 means fast DSP communication.)
It fills the Bus Configuration Database of the node with the found elements.
Then the Function Chart Builder creates automatically DAT_DAT elements for all DAT
elements referenced on some REFj terminals of the DSPi elements and fills the Bus
Configuration Database also with them. Through DAT_DAT DB elements the AF100 OCP
makes DAT DB elements visible for Human-System Interfaces.
NOTES
This function equals the one controlled by the All DSPs Visible in AF100 OPC
check box of File | Generate Target Code available for AC 100 Series.
Automatically created DAT_DAT elements do not appear in the *.ODB file.

4-256 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

In case of AC 400 Series, S800 I/O is realized partly in the PC section. The PC
part is not reflected in the Bus Configuration Database, hence not checked by the
Bus Configuration Builder and not reflected in the calculated bus load.

MB 300
Select this check box to generate BCD data for MasterBus 300.
In the DB section of AC 400 Series node the Function Chart Builder checks the conditions of
MB 300 communication: it looks for DB elements LAN#, callname CS513, that fulfill the
following conditions:
Terminal NET has a value >= 0, and terminal NODE has a value > 0, and terminal
PROTOCOL has any of the values “MB300”, “MB300_F”, “MB300_E”.
MP 200/1 nodes have no corresponding DB elements. In that case the Function Chart Builder
checks the MB 300 address of MP 200/1 nodes as set by APB:
“Net” is >= 0, and “Node” is > 0.
Function Chart Builder fills the Bus Configuration Database if the conditions are met.

GCOM
Select this check box to generate BCD data for GCOM (on MasterBus 300).
In the DB section of AC 400 Series node the Function Chart Builder checks the conditions of
GCOM communication: it looks for DB elements LAN#, callname CS513, that fulfill the
following conditions:
Terminal NET has a value >= 0, and terminal NODE has a value > 0, and terminal
PROTOCOL has any of the values “GCOM”, “GCOM_F”, “GCOM_S”.
Function Chart Builder fills the Bus Configuration Database if the conditions are met.

4.5.4.15 File | Generate Source…

File | Generate Source… - for Node
Use this command to generate AMPL source code for the selected node on the basis of its
internal data representation.

3BDS 100 595R401 4-257

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-160. Generate Source Code

• PC Section
Select this check box to generate PC source code.
The controls in the left column are relevant only if the PC Section check box is selected.

4-258 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

• PC File Name
Edit a PC file name, or single-select one from the drop-down combo box or browse for
source code in any directory using common explorer-style dialog Save PC Source Code
As..

Figure 4-161. Save PC Source Code As

The drop-down combo box "PC File Name" is filled with already existing source code in
the \PCDATA directory, and with the history of most recent source code files in any
directory.
Enter the filename with any extension to specify the complete filename. Otherwise the
given filename aaaa is automatically appended by aaaannss.AAX with nn = PC program
number, ss = segment number, and AAX = default extension for PC source code.
Prefix the filename by a directory path or UNC network path specification to generate
source code in the given directory, e.g. "e:\temp\asterix.aax" or "\\gpaxyz\c\temp\obelix".
Enclose file name in quotes if it contains blanks, e.g. "copy of 1".
Do not use characters in the range [\/:*?"<>|;!].

NOTE
Specify a maximum of 4 characters [A-Za-z0-9] as filename if you intend to
download the source code via On-line Builder to AC400 Series controllers. You
get a warning for AC400 Series controller node types if you enter more than 4
characters, or enter filenames containing other characters than [A-Za-z0-9], or
specify a directory other than the nodes \PCDATA directory, or specify an
extension other than .AAX.

3BDS 100 595R401 4-259

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

If you ignore that warning, you can still generate valid source code to be
backtranslated in Function Chart Builder, but you cannot convert that source code
and load it via On-line Builder.

NOTE
If you entered the filename with any extension to specify the complete filename,
make sure that you have selected only one PC program. The PC program number
postfix nn is not appended in that case to the file specification. Thus if you select
all PC programs or more than, the specified source code file is overwritten by
each PC program.
You get a warning in that case.

The file filters Save as type of dialog Save PC Source Code As list all files matching the
selected file type:
– PCnn Source Code for ONB (*nn01.aax)
– All PC Source Code (*.aax)
– All Files (*.*)
On Save, the selected or edited file name is echoed in dialog Generate Source Code:
The first file filter (... for ONB) echo the file name specification without PCnn postfix,
without segment number ss, and without extension, e.g. 10101.aax => 1.
The other two filters echo the complete filename with extension, e.g. 10101.aax.
If the directory is not default (\PCDATA), the complete directory path is echoed, e.g.
"e:\temp\asterix.aax".
• PC Program(s)
Edit PC programs(s) separated by blank or comma, or select PC program(s) from the drop-
down combo box, or multi-select PC programs via dialog Select PC Programs..., or check
All Programs.
The drop-down combo box "PC Program(s)" is filled with all PC programs of the node,
and with the history of most recent selected PC Programs(s).
The dialog "Select PC Program(s)" displays all PC programs of the node.

4-260 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

Figure 4-162. Select PC Program(s)

NOTE
If you entered the filename with any extension to specify the complete filename,
make sure that you have selected only one PC program. The PC program number
postfix nn is not appended in that case to the file specification. Thus if you select
all PC programs or more than, the specified source code file is overwritten by
each PC program.
You get a warning in that case.

• PC Item Designation From/To

To generate partial PC source code, check From and To, and enter the starting and ending
PC item designation. You can also select PC item designations from the combo boxes
holding the most recent selected ones.
If you do not specify To item designation, PC source code is generated from the given
From item designation to the end of the PC program.
You can also specify a To item designation ending with wildcard *, e.g. PC1.1.*.
This is useful if you do not know the very last PC element of the corresponding tree level.
• Disintegrate TCs
This control is used on Backtranslate Source Code only and not selectable on Generate
Source Code.
• DB Section
Select this check box to generate DB source code.
The controls in the right column are relevant only if the DB Section check box is selected.

3BDS 100 595R401 4-261

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• DB File Name
Edit a DB file name, or single-select one from the drop-down combo box, or browse for
source code in any directory using common Explorer-style dialog Save DB Source Code
As.

Figure 4-163. Save DB Souce Code As

The drop-down combo box "DB File Name" is filled with already existing source code in
the \DBDATA directory, and with the history of most recent source code files in any
directory.
Enter the filename with any extension to specify the complete filename. Otherwise the
given filename bbbb is automatically appended by bbbbss.BAX with ss = segment
number.
Prefix the filename by a directory path or UNC network path specification to generate
source code in the given directory, e.g. "e:\temp\asterix.bax" or "\\gpaxyz\c\temp\asterix".
Enclose file name in quotes if it contains blanks, e.g. "copy of 1".
Do not use characters in the range [\/:*?"<>|;!].

NOTE
Specify a maximum of 6 characters [A-Za-z0-9] as filename if you intend to
download the source code via On-line Builder to AC400 Series controllers. You
get a warning for AC400 Series controller node types if you enter more than 6
characters, or enter filenames containing other characters than [A-Za-z0-9], or
specify a directory other than the nodes \DBDATA directory, or specify an
extension other than .BAX. If you ignore that warning, you can still generate

4-262 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

valid source code to be backtranslated in Function Chart Builder, but you cannot
convert that source code and load it via On-line Builder.

The file filters Save as type of dialog Save DB Source Code As list all files matching the
selected file type:
– DB Source Code for ONB (*01.bax)
– All DB Source Code (*.bax)
– All Files (*.*)
On Save, the selected or edited file name is echoed in dialog Generate Source Code:
The first file filter (... for ONB) echo the file name specification without segment number
ss, and without extension, e.g. 101.bax => 1.
The other two filters echo the complete filename with extension, e.g. 101.bax.
If the directory is not default (\DBDATA), the complete directory path is echoed, e.g.
"e:\temp\asterix.bax".
• Include System Defaults
Use this check box to include system defaults (that is, DB general defaults) in the DB
source code. Select this check box if you want to extract the general defaults from the DB
source code of a node and save it as DBGENDEF.BAX file in the node directory and
possibly in ..\PR_TC\TCDATA and ..\PR_CI\CIDATA.
Unselect this check box if you want to generate “lean” DB source code. Then you rely on
general defaults in an object-specific DBGENDEF.BAX file or—if no object-specific
DBGENDEF.BAX file exists—on those defined in the current element library.
• Include System DB Elements
Select this check box the to include system DB elements in the DB source code.
AC 100 Series nodes have generally no system DB elements.
• Replace Item Designations By Wildcard
Check that option to generate (partial) DB source code with item designations replaced by
wildcard, e.g. PIDCON1 => PIDCON*m and so on. This is useful when creating DB
source code to be loaded or appended into an existing system where no DB listing is
available.
• Prefix DB Elements By MODIFY
Check that option to generate (partial) DB source code with MODIFY prefix as in On-line
Builder, e.g. PIDCON1 => MODIFY PIDCON1. This is useful when creating DB source
code to update an existing system.
• DB Filter/Callname and Filter/Name
Select this check box to limit the DB source code generation to DB elements with
callnames and/or instance names corresponding to the filters.
Open the list box parts of the adjacent combo boxes to see earlier filters and select one, or
edit directly in the text box part. Wildcards ‘*’ and ‘?’ are also allowed.

3BDS 100 595R401 4-263

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• DB Item Designation From/To

Select these check boxes to limit the DB source code generation to an item designation
range of DB elements. Open the list box parts of the adjacent combo boxes to see earlier
From and To values. Select a filter in the list box part of the adjacent combo box or edit
directly in the text box part.
If the \DBDATA and \PCDATA subdirectory of the node contains some old PC or DB source
files with the specified filenames, the Function Chart Builder prompts you to confirm:
Overwrite existing source file ... ?
CAUTION
If you answer Yes, the Function Chart Builder deletes the old source code files
with the specified names. If the old source code files are valuable, answer No at
first, copy or rename them by using the File | Copy command of the Application
Builder or the Explorer of Windows NT, then retry the Generate Source
command.
You can switch off that warning by unchecking “Options | Preferences | Query Overwrite
Source Code".
You can also force automatic generation of source code BAK files by checking "Options |
Preferences | Create Source Code BAK Files".
The Function Chart Builder opens the Output window (or iconizes it as set by
Options | Preferences), and lists messages about progress and termination of the source code
generation.
If no extension is specified, Function Chart Builder appends the given DB filename by ss.BAX
(ss = segment number). If no directory is specified, Function Chart Builder generates the DB
source code and attached type circuit information files *.TBX in the \DBDATA subdirectory.
To download the DB source code via On-line Builder to AC 400 Series controllers, the filename
is restricted to max. 6 chars in the range [A-Za-z0-9], and must follow the syntax
bbbbbbss.BAX and bbbbbbss.TBX (bbbbbb = given file name and ss = segment number).
AC 100 Series node types can use longer file names and other syntax..
If you are working on an AC 400 Series or MasterPiece 200/1 node, the Function Chart Builder
generates also a command file in bbbbbbss.CFX form for dimensioning the data base by the
On-line Builder.
If no extension is specified, Function Chart Builder appends the given PC filename by
nnss.AAX (nn = PC program number, ss = segment number). If no directory is specified,
Function Chart Builder generates the PC source code and attached type circuit information files
*.TIX in the \PCDATA subdirectory.
To download the PC source code via On-line Builder to AC 400 Series controllers, the filename
is restricted to max. 4 chars in the range [A-Za-z0-9], and must follow the syntax aaaannss.AAX
and aaaannss.TIX (aaaa = given file name, nn = PC program number and ss = segment number.
AC 100 Series node types can use longer file names and other syntax.

4-264 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

NOTES
*.TBX files stand for type circuit instances, which were instantiated in the
DB Section window. These are the type circuits having only DB section.
*.TIX files stand for type circuit instances, which were instantiated in the
PC Section window. These are the type circuits having PC section.
The Function Chart Builder does not take care of the 32K segmentation for text
files, which is usual with the On-line Builder, so only segment numbers ss = 01
appear.

File | Generate Source - for NS

Use this command to generate node structure source code for the selected node structure on the
basis of its internal data representation.
NOTE
You can expand a node structure only if you have generated source code for it.

If the \CIDATA subdirectory of the node contains an old node structure source file with the
node_name.NSS filename (, where node_name is the name of the selected node structure),
the Function Chart Builder prompts you to confirm:
Delete existing source file ... ?
CAUTION
If you answer Yes, the Function Chart Builder deletes the old node structure
source code file in the \CIDATA subdirectory of the node. If the old node
structure source code file is valuable, answer No at first, copy or rename it by
using the File | Copy command of the Application Builder or the Explorer
of Windows NT, then retry the Generate Source command.

The Function Chart Builder opens the Output window (or iconizes it as set by
Options | Preferences), and lists messages about progress and termination of the source code
generation.
The Function Chart Builder stores the node structure source code in the node_name.NSS file in
the \CIDATA subdirectory of the node.

File | Generate Source - for CI

Use this command to generate circuit source code for the selected circuit on the basis of its
internal data representation.
NOTE
You can locate a recently created or edited circuit only if you have generated
source code for it.

If the \NODES\PR_CI\CIDATA subdirectory of the current project contains an old circuit

source file with the circuit_name.CIS filename (, where circuit_name is the name of the selected
circuit), the Function Chart Builder prompts you to confirm:
Delete existing source file ... ?

3BDS 100 595R401 4-265

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

CAUTION
If you answer Yes, the Function Chart Builder deletes the old circuit source code
file with the corresponding name in the \NODES\PR_CI\CIDATA subdirectory.
If the old circuit source code file is valuable, answer No at first, copy or rename it
by using the File | Copy command of the Application Builder or the Explorer
of Windows NT, then retry the Generate Source command.

The Function Chart Builder opens the Output window (or iconizes it as set by
Options | Preferences), and lists messages about progress and termination of the source code
generation.
The Function Chart Builder stores the circuit source code in the circuit_name.CIS file in the
\NODES\PR_CI\CIDATA subdirectory.

File | Generate Source… - for TC

Use this command to generate type circuit source code for the selected type circuit on the basis
of its internal data representation.

NOTE
You can instantiate a recently created or edited type circuit only if you have
generated source code for it.

Figure 4-164. Generate TC Source Code

• Complete TC
Select this option if you want to generate source code that specifies the type circuit
completely.

• TC Frame Only
Select this option if you want to generate source code that specifies only the interface
(frame) of the type circuit leaving its contents empty.

4-266 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

NOTE
On the basis of the generated type circuit source code containing just the interface
of the type circuit, you can insert the type circuit already in circuits and node
structures (but not in nodes!). You can get the source code of the final, completed
type circuit later from another designer in your team, or you can complete the
content of the type circuit yourself. Nevertheless, the source code of the complete
type circuit must be copied or generated in the \NODES\PR_TC\TCDATA
subdirectory of the current project before the expansion of node data.

• TC Frame Sections
Select the check boxes of this group box to define the corresponding sections in the
type circuit frame.

• PC Section Properties
These controls are valid only if the PC Section check box is selected.
Select the top PC element in the Top PC Element drop-down combo box. Select
ELEMENTS for all top PC elements, which are not explicitly listed in the list box part.
Define the number of top level PC elements within the type circuit. Type it in the
Item Des. Range text box.
If the \NODES\PR_TC\TCDATA subdirectory of the current project contains an old type circuit
source file with the type_circuit_name.TCS filename (, where type_circuit_name is the name of
the selected type circuit), the Function Chart Builder prompts you to confirm:
Delete existing source file ... ?

CAUTION
If you answer Yes, the Function Chart Builder deletes the old type circuit source
code file with the corresponding name in the \NODES\PR_TC\TCDATA
subdirectory. If the old type circuit source code file is valuable, answer No at first,
copy or rename it by using the File | Copy command of the Application Builder
or the Explorer of Windows NT, then retry the Generate Source command.

The Function Chart Builder opens the Output window (or iconizes it as set by Options |
Preferences), and lists messages about progress and termination of the source code generation.
The Function Chart Builder stores the type circuit source code in the type_circuit_name.TCS
file in the \NODES\PR_TC\TCDATA subdirectory.

4.5.4.16 File | Expand Node Structure

Use this command to generate—internally non-structured—node data from the equally named
node structure and its referenced circuits and type circuits. It is assumed that:
• The node structure is available in the form of node structure source code.
• You start the Function Chart Builder on the node.
• The internal data representation of the node is empty.
If the internal data representation of the node is not empty, use File | Initialize at first.

3BDS 100 595R401 4-267

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTE
Initialization of internal data representation of a node does not destroy the internal
data representation of the equally named node structure nor any source code.

The Function Chart Builder resolves the circuit and type circuit references in the node structure
and the type circuit references in the circuits, that is, replaces the references with the referenced
objects. The result is stored as internal data representation of the selected node.
The Function Chart Builder opens the Output window (or iconizes it as set by
Options | Preferences), and lists messages about progress and termination of the expansion.

4.5.4.17 File | Check PC Source…

Use this command to validate the PC source code, which have been created by tools other than
the Function Chart Builder, such as a text editor.
It is assumed that the PC program to be validated pertains to the selected node, or has at least the
same node type, version, and options.

Figure 4-165. Check PC Source Code

• Directory
The symbol shows the directory currently browsed for files.
Default is the \PCDATA subdirectory of the current node.
You can also select a subdirectory in the list box below.
Or go to the directory on the next higher level by clicking on the Up One Level icon.
Click on the Create New Folder icon to create a new subdirectory.

• Up One Level and Create New Folder (Icons)

Click on the Up One Level icon to go to the directory on the next higher level.
Click on the Create New Folder icon to create a new subdirectory.

4-268 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

• List and Details (Icons)

Click on these icons to display the files and subdirectories in corresponding forms.

• Files and Subdirectories

The list box contains all available files and subdirectories in the specified directory, which
correspond to the filter condition.
Click on the List and Details icons to display the files and subdirectories in corresponding
forms.

• File Name
Select a file name from the list box or type it here. Or edit a new filter condition, for
example, MY*.AAX, and press ENTER to make it effective.

• Files of Type
Select a filter condition from the standard filters in this drop-down list box.
The default extension for PC source code files is AAX.

• With DB
Select it if you want to check whether all DB elements exist, to which connections are
made in the PC program.

• Open
Activate this button to start checking.
The Function Chart Builder checks whether the PC source code corresponds to AMPL syntax,
opens the Output window (or iconizes it as set by Options | Preferences), and lists messages
about progress and termination of the check.
If there are syntactic errors in the source file or—in case of selected With DB— some
referenced DB elements do not exist, the Function Chart Builder stores messages in a list file
with the extension LS1 or LS2 in the subdirectory of the source file. The extensions reflect the
two passes of the validation.

4.5.4.18 File | Backtranslate Source…

File | Backtranslate Source… - for Node

Use this command to translate the source code of the selected node to internal data
representation of the Function Chart Builder.
In case that you backtranslate complete node source code, i.e. both PC and DB source code, the
internal representation of the node must be initialized first. The Function Chart Builder warns
you if this condition is not met.

3BDS 100 595R401 4-269

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-166. Backtranslate Source Code

• PC Section
Select this check box to backtranslate PC source code.
The controls in the left column are relevant only if the PC Section check box is selected.

4-270 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

• PC File Name
Edit PC file name(s) separated by blank, or select from the drop-down combo box, or
browse for source code in any directory using common explorer-style dialog Open PC
Source Code Files(s)..

Figure 4-167. Open PC Source Code Files(s)

The drop-down combo box "PC File Name" is filled with existing source code in the
\PCDATA directory, and with the history of most recent source code files in any directory.
Enter the filename with any extension to specify the complete filename. Prefix the
filename by a directory path or UNC network path specification to backtranslate source
code from the given directory, e.g. "e:\temp\asterix.aax" or "\\gpaxyz\c\temp\obelix".
Enclose file names in quotes if they contain blanks, e.g. "copy of 1", "copy of 2".
According to the existence of the edited / selected PC file name specification, the PC
program(s) combo box is refilled. If more than one PC filename is given, the PC
program(s) combo box is filled with the according superset.

3BDS 100 595R401 4-271

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Table 4-25. Edit PC File Names

Edited / selected "PC File Combo box "PC

PC source code files
Name" Program(s)"
any file and extension combo box reset, empty
given asterix.aax
e.g. ‘asterix.aax’ asterix.aax.bak
e.g. ‘asterix.aax.bak’
no extension given, no combo box filled with all PC
PCnn specification programs PCnn with
e.g ‘aaaa’ aaaa0101.aax existing source code files
aaaa0301.aax ‘aaaan01.aax’, e.g. PC1,
aaaa4201.aax PC3, PC42

no extension given, but combo box filled with PC

PCnn specified program PCnn, e.g. PC42
e.g ‘aaaa42’ aaaa4201.aax
no extension given, but combo box filled with PC
PCnn and segment index program PCnn, e.g. PC42
specified
e.g ‘aaaa4201’ aaaa4201.aax
extension .aax given, and combo box filled with PC
PCnn and segment file program PCnn, e.g. PC42
index specified
e.g ‘aaaa4201.aax’ aaaa4201.aax
extension .aax.bak given, combo box filled with PC
and PCnn and segment file program PCnn, e.g. PC42
index specified
e.g ‘aaaa4201.aax.bak’ aaaa4201.aax.bak

NOTE
Specify a maximum of 4 characters [A-Za-z0-9] as filename if you intend to
backtranslate AC400 Series controller source code from On-line Builder into
Function Chart Builder.

The file filters Files of type of dialog Open PC Source Code File(s) see Figure 4-167 list
all files matching the selected file type:
– PCnn Source Code for ONB (*nn01.aax)
– All PC Source Code (*.aax)
– Backup PC source code (*.aax.bak)
– All Files (*.*)

4-272 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

On Open, the selected or edited file name(s) are echoed in dialog Backtranslate Source
Code.
The first file filter (... for ONB) echo the file name specification without segment number
ss, and without extension, e.g. "10101.aax" "10501.aax" "14201.aax" => 101 105 142 will
backtranslate PC1, PC5, PC42.
If you select all source code files aaaann01.aax for all PC programs PCnn, only aaa is
echoed, e.g. "10101.aax" "10201.aax" "10501.aax" "14201.aax" "18801.aax" => 1 will
backtranslate PC1, PC2, PC5, PC42, PC88.
The other two filters echo the complete filename with extension, e.g. 10101.aax.
If the directory is not default (\PCDATA), the complete directory path is echoed, e.g.
"e:\temp\asterix.aax".
• PC Programs
This combo box is automatically refilled when you modify the PC file name, see
Table 4-25.
You can change that default and edit the subset of PC programs(s) to be backtranslated.
Separate them by blank or comma, or select PC program(s) from the drop-down combo
box, or multi-select PC programs via dialog Select PC Programs(s), or check All
Programs.

Figure 4-168. Select PC Programs(s) for Backtranslate

The drop-down combo box "PC Programs" is filled with all PC programs found for the
specified PC file name(s), and with the history of most recent selected PC Programs(s).
Dialog "Select PC Program(s)" displays all PC programs found for the specified PC file
name(s).
• PC Item Designation From/To
These controls are used for partial PC source code generation only and not selectable on
Backtranslate Source Code.

3BDS 100 595R401 4-273

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Disintergrate TCs
Select this check box to disintegrate the type circuits, if any, instantiated in the node.
• DB Section
Select this check box to backtranslate DB source code.
The controls in the right column are relevant only if the DB Section check box is selected.
• DB File Name
Edit DB file name(s) separated by blank, or select from the drop-down combo box, or
browse for source code in any directory using common explorer-style dialog Open DB
Source Code.

Figure 4-169. Open DB Source Code File(s)

The drop-down combo box "DB File Name" is filled with existing source code
in the \DBDATA directory, and with the history of most recent source code files in any
directory.
Enter the filename with any extension to specify the complete filename. Prefix the
filename by a directory path or UNC network path specification to backtranslate source
code from the given directory, e.g. "e:\temp\asterix.bax" or "\\gpaxyz\c\temp\obelix".
Enclose file names in quotes if they contain blanks, e.g. "copy of 1", "copy of 2".

4-274 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

According to the existence of the edited / selected DB file name specification, the
following DB source code file(s) are backtranslated:

Table 4-26. DB File Name Specification

DB File Name DB Source Code File

any file and extension
given obelix.bax
e.g. ‘obelix.bax’ obelix.bax.bak
e.g. ‘obelix.bax.bak’
no extension given, no
segment index specified
e.g ‘bbbbbb’ bbbbbb01.bax
no extension given, but
segment index specified
e.g ‘bbbbbb01’ bbbbbb01.bax
extension .bax given, and
segment index specified
e.g ‘bbbbbb01.bax’ bbbbbb01.bax
extension .bax.bak given,
and segment index
specified
e.g ‘bbbbbb01.bax.bak’ bbbbbb01.bax.bak

NOTE
Specify a maximum of 6 characters [A-Za-z0-9] as filename if you intend to
backtranslate AC400 Series controller source code from On-line Builder into
Function Chart Builder.

The file filters Files of type of dialog Open DB Source Code File(s) list all files matching
the selected file type.
– DB Source Code for ONB (*01.bax)
– All DB Source Code (*.bax)
– Backup DB source code (*.bax.bak)
– All Files (*.*)
On Open, the selected or edited file name(s) are echoed in dialog Backtranslate Source
Code.
The first file filter (... for ONB) echo the file name specification without segment number
ss, and without extension, e.g. "101.bax" "301.bax" "E01.bax" => 1 3 E.
The other two filters echo the complete filename with extension, e.g. 101.bax.

3BDS 100 595R401 4-275

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

If the directory is not default (\DBDATA), the complete directory path is echoed, e.g.
"e:\temp\asterix.bax".
• DB Code Generator Options, DB Filter, DB Item Designation
These controls are used on Generate Source Code only and are not selectable on
Backtranslate Source Code.
The Function Chart Builder opens the Output window (or iconizes it as set by
Options | Preferences), and lists messages about progress and termination of the
backtranslation.
The Function Chart Builder accepts DB source code files in any syntax and in any directory:
a. AC400 Series controller source code from On-line Builder in the form bbbbbbss.BAX
(bbbbbb = given file name [A-Za-z0-9] and ss = segment number) stored in the \DBDATA
subdirectory, and PC source code files in the form aaaappss.AAX form (aaaa = given file
name [A-Za-z0-9], pp = PC program number and ss = segment number) stored in the
\PCDATA subdirectory.
b. source code files with long filenames.
c. source code files with blanks and any character but [\/:*?"<>|;!].
d. source code files in any directory.
The Function Chart Builder disintegrates the type circuit instances, if there are any, that is, it
resolves the type circuit references in the node, if you select the Disintegrate TCs check box. If
there are type circuit instances in the node and you clear the Disintegrate TCs check box, the
Function Chart Builder tries to identify the type circuits and represent the instances as
references, unresolved. Nevertheless, the Function Chart Builder disintegrates any type circuit
instance in any of the following cases:
• The interface or the contents of type circuit instances was changed compared with the
original type circuit. (This may happen if the source code was dumped from a target,
where parts of application, covered by type circuits, had been modified.
The changes made in the target are properly reflected in the Function Chart Builder.)
• An appropriate entry in a type circuit information file or the corresponding type circuit
information file is missing.

NOTE
The Function Chart Builder expects

• type circuit information files attached to DB source code with the extension
.TBX located in the same directory as the DB source code file with the same
filename.
• type circuit information files attached to PC source code with the extension
.TIX located in the same directory as the PC source code file with the same
filename.

Type circuit information files attached to AC400 Series controller DB source code from On-line
Builder are in bbbbbbss.TBX form and stored in the \DBDATA subdirectory, and type circuit

4-276 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

information files attached to AC400 Series controller PC source code from On-line Builder are
in aaaappss.TIX form and stored in the \PCDATA subdirectory.

*.TBX files stand for type circuit instances, which were instantiated in the DB Section window.
These are the type circuits having only DB section.
*.TIX files stand for type circuit instances, which were instantiated in the PC Section window.
These are the type circuits having PC section.
The Function Chart Builder assumes that the original type circuits are in tttttttt.TCS form (tttttttt
= type circuit name) and are located in the \TCDATA subdirectory of the node directory.

If an error occurs, the Function Chart Builder stores messages in list files with the filename of
the DB and PC source code, and with the extension LS1 or LS2 (corresponding to the two
passes). The list files are located in the directory of the DB and PC source code file(s). By
default in the \DBDATA subdirectory for the DB section, or in the \PCDATA subdirectory for
the PC section.
File | Backtranslate Source - for CI, NS, and TC
Use this command to translate the source code of the selected circuit, node structure, or type
circuit to internal data representation of the Function Chart Builder.
The internal representation of the circuit, node structure, or type circuit must be initialized for
the backtranslation. The Function Chart Builder warns you if this condition is not met.
The Function Chart Builder opens the Output window (or iconizes it as set by
Options | Preferences), and lists messages about progress and termination of the
backtranslation.
For circuits:
The Function Chart Builder backtranslates the circuit_name.CIS circuit source code file
stored in the \NODES\PR_CI\CIDATA subdirectory.
For node structures:
The Function Chart Builder backtranslates the node_name.NSS node structure source code
file stored in the \CIDATA subdirectory of the node.
For type circuits:
The Function Chart Builder backtranslates the type_circuit_name.TCS type circuit source
code file stored in the \NODES\PR_TC\TCDATA subdirectory.
If some error occurs, the Function Chart Builder stores the messages in list files with the
extensions LS1 and LS2 in the directory of the corresponding source file.

4.5.4.19 File | Backtranslate Target Code

Use this command to translate the target code of the selected node to internal data representation
of the Function Chart Builder. It is normally preceded by a Target | Upload Application
command.

3BDS 100 595R401 4-277

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTES
Application retrieval is supported by Application Builder version 2.6 and higher
and Function Chart Builder 4.6 and higher.
The application can only be retrieved if you work with the same Function Chart
Builder version as the one with which its target code was generated.
These functions are available only for new node types explicitly supporting
application retrieval, such as AC 80 2.0.
For successful retrieval, node type and element library versions used by the
application to be retrieved must be available and installed in the corresponding
release subdirectories. Or they must be stored with the target code on the target.

The Function Chart Builder initializes the *.ODB file and translates the target code files *.C00
and *.C?? in the \CONTROL subdirectory to internal data representation. As usual for AC 100
Series applications, the DB part and one PC program will be backtranslated. The latter will have
the original PC program number.
The scope of application retrieval depends on the information included in the target code, that
is, on the options that were selected at its generation by the File | Generate Target Code
command:
• Names of DB elements, PC elements, and PC signals will be restored only if this
information was generated and stored together with the target code on the target.
Else the names will be omitted.
• Type circuit instances as such will be restored only if the corresponding information was
stored together with the target code on the target.
Else the type circuit instances remain disintegrated.
• Elements of documentation, such as item designation of elements, position of page
divisions, and texts of headers and footers, will be restored only if the corresponding
information was stored together with the target code on the target.
Else the item designations will be generated in natural order, the page divisions will be
generated automatically, and the headers and footers remain empty.
After successful execution of File | Backtranslate Target Code, the internal data
representation corresponds to the one in the target, so the Function Chart Builder is either in on-
line mode or in on-line preparation mode depending on whether the target is connected yet or
not.
After successful restoration of the internal data representation, the Function Chart Builder asks
whether to restore also HMI information.
• If you answer Yes, the Function Chart Builder restores BOIL*.c00 and COIL*.c00 files
and Bus Configuration Database as applicable. To complete the restoration, you will need
to execute the File | Save and Load command when you switch next time to on-line mode.
• In case of No it is supposed that these files are yet available and valid.
See also Section 4.4.6.15, Retrieve Application from an AC 100 Series Target.

4-278 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

4.5.4.20 File | Export DB Section

Use this command to export the DB section of the selected node, node structure, circuit, or type
circuit for further use by other Windows applications.

Figure 4-170. Export DB Section

• Create One File per Callname

Select this check box to export to as many files as there are callnames used in the DB
section instead of to one file. The DB callnames are used as filenames, the file extension
can be selected in the drop-down combo box on the right.
Unselect this check box to export the DB section to one file, or to the Clipboard of
Windows NT, or to both destinations.

• Include Headline with DB Terminal Names

Select this check box to include a headline with names of the DB terminals for each group
of available DB elements with the same callname.
This line is necessary if the exported file shall be imported later with File > Import DB
Section.

• Include System Defaults

Select this check box to include a line with the DB system defaults for each group of
available DB elements with the same callname.

• Include System DB Elements

Select this check box to include the terminal values of the system DB elements into the
exported text.

3BDS 100 595R401 4-279

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Filter/Callname
Select this check box and edit a callname filter in the text box of the drop-down combo box
to export just an except of the DB section. The list box part contains the previous callname
filters. You can combine both filters to limit the exported text more.

• Filter/Name
Select this check box and edit a DB name filter in the text box of the drop-down combo
box to export just an except of the DB section. The list box part contains the previous DB
name filters. You can combine both filters to limit the exported text more.

• DB Export File Name

If the Create One File per Callname check box is not selected, edit the file name of the
DB export file in the text box part of this drop-down combo box.
You can also enter an optional file name extension separated by a dot ‘.’.
Else the file gets the default extension DBT.
The list box part contains the files available in the ..\LIST subdirectory.

• Copy to Clipboard
Select this check box to write the exported text to the Clipboard of Windows NT.

• Apply
Activate this button to start exporting DB section contents and remain in the
Export DB Section dialog.
A similar action as that of the OK button.
The Function Chart Builder extracts the specified part of the DB section, converts it to text, and
writes this text to the Clipboard of Windows NT, or to a file with the specified name in the
..\LIST subdirectory pertaining to the object you are working on, or to both destinations.
The default extension of the file is DBT.
Alternatively, the Function Chart Builder divides the text into parts on the basis of groups of
available DB elements with the same callname and writes them to as many files as there are
callnames used in the DB section.
In this case the DB callnames are used as filenames, the extension is selectable (normally DBT).
You get, for example, the files AI.DBT, DAT(R).DBT, and so on.
The text file contains the terminal values of the DB elements available in the DB section
separated by TAB (tabulator) characters to support other Windows applications.
If specified so, it contains also a headline consisting of the terminal names and the default
values for each group of available DB elements with the same callname.

4.5.4.21 File | Import DB Section

Use this command to import the DB section former exported by File | Export DB Section or
created or modified by other Windows applications.

4-280 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

Figure 4-171. Import DB Section

Files exported with File | Export DB Section can be imported with this function. 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.

• Filename
Enter here the filename and path, where the import file is located. The import file can have
any extension. For structure of the import file see structure of the output file.
Import files for AC 400 Series targets need to included position dependent DB Elements
e.g. AIC in front of position independent DB Elements.

• Delimiter
Enter here the delimiter stored in the import file. The default delimiter is TAB, shown as
blank.

4.5.4.22 File | Print…

Shortcut: CTRL+P
Use this command to define the document parts for the selected object and to start printing.

3BDS 100 595R401 4-281

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-172. Print

• Printer
The Name combo box shows the selected printer. The static text shows some of its
parameters. Drop the combo box down to list available printers and select another one.
Activate the Properties button to change properties of the selected printer.
See also the Setup button for printer changes.

• Print to File
Select this check box if you want to create a print file in the LIST subdirectory of the
current object instead of printing on the printer.
See Appendix A, Function Chart Builder Files, Section A.1, FCB Directory Structure.
Edit the name of the print file in the text box to the right.

• Filename
If the Print to File check box is selected, enter here the print_filename, where
print_filename is one to six characters long start of the full filename.
The file names of the print files have default extensions as shown in the following table:

Table 4-27. Print File Names

Document Part Title Name of Print File

Database Listing print_filename.DB

4-282 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

Table 4-27. Print File Names

Document Part Title Name of Print File

PC Diagram print_filename1.PCF, print_filename2.PCF, etc.
Tree Listing print_filename1.PCT, print_filename2.PCT, etc.
TC/CI Symbols print_filename.SYL
Module Listing print_filename.ML
PC Cross-reference Listing print_filename.PXR
DB Cross-reference Listing print_filename.DXR
Circuit Usage Listing print_filename.UCI
Option Listing print_filename.OL
DAT Crossreference Listing print_filename.DAT
DSP Crossreference Listing print_filename.DSP
EVS Crossreference Listing print_filename.EVS
MDAT Crossreference Listing print_filename.MDT
DB Names print_filename.NAM
PC Names print_filename1.NAM, print_filename1.NAM,, etc

• Document
Select the check boxes to include the corresponding parts into the document to be printed.
The Function Chart Builder opens further dialog boxes to set document-specific print
options depending on the selected check boxes.
Most document parts are offered only if the corresponding sections have been created:

Table 4-28. Dialogs to Specify Document Parts (1)

Document Part Title Section with Description of Print Dialog

Database Listing File | Print, Database Listing Included
PC Diagram File | Print, PC Diagram and/or Tree Listing Included
Tree Listing File | Print, PC Diagram and/or Tree Listing Included
TC/CI Symbols File | Print, TC/CI Symbols Included
Module Listing File | Print, Module Listing Included
PC Crossreference Listing File | Print, PC Cross-reference Listing Included
DB Crossreference Listing File | Print, DB Cross-reference Listing Included
Circuit Usage Listing File | Print, CI Usage Listing Included

3BDS 100 595R401 4-283

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Table 4-28. Dialogs to Specify Document Parts (1)

Document Part Title Section with Description of Print Dialog

Option Listing File | Print, Option Listing Included
DB Names File | Print, DB Names Included
PC Names File | Print, PC Names Included

Some document parts are offered only if the corresponding DB elements have been created
and are visible in the DB Section window.

NOTE
DB elements, which were created implicitly by extended DB elements, are visible
in the DB Section window if Show Implicitly Created Communication
Elements is selected in the Preferences dialog box.
Table 4-29. Dialogs to Specify Document Parts (2)

Document Part Title Section with Description of Print Dialog

DAT Crossreference Listing File | Print, DAT Cross-reference Listing Included
DSP Crossreference Listing File | Print, DSP Cross-reference Listing Included
EVS Crossreference Listing File | Print, EVS Cross-reference Listing Included
MDAT Crossreference Listing File | Print, MDAT Cross-reference Listing Included

• Copies
Edit the number of copies you want to print. Select the Collate Copies check box if you
want to print document copies in page number order, instead of separated multiple copies
of each page. Select this check box for proper sorting of pages in case of multiple copies.

• Setup
Activate this button to open the Print Setup dialog box. See File | Print Setup for dialog.
You can follow the progress of printing or abort printing in the Printing dialog box.
Description of document-specific print dialogs see on the following pages:

File | Print, Database Listing Included

Select the DB Section check box in the Document group box of the Print dialog to include the
DB section of the selected node, node structure, circuit, or type circuit into the document to be
printed in source code format.
The Function Chart Builder opens the Print DB Section dialog box

4-284 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

Figure 4-173. Print DB Section

• Filter/Callname and Name

Select these check boxes to limit the printing of DB source code to DB elements with
callnames and/or instance names corresponding to the filters. Open the list box parts of the
adjacent combo boxes to see earlier filters and select one. Or edit directly in the text box
part. Wildcards ‘*’ and ‘?’ are also allowed.

• Item Designation/From and To

Select these check boxes to limit the printing of DB source code to an item designation
range of DB elements. Open the list box parts of the adjacent combo boxes to see earlier
“From” and “To” values. Select a filter in the list box part of the adjacent combo box or
edit directly in the text box part.

• Include Default PU Symbols

Select it to include default values of project-unique (PU) symbols in the Database Listing.
Footer text entered in the Edit | Document Texts command is displayed and printed in the
bottom lines of each page.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension DB in the \LIST subdirectory.

File | Print, PC Diagram and/or Tree Listing Included

Select the PC Section check box in the Document group box of the Print dialog to include the
PC Diagram (function chart) and/or the Tree Listing of the selected node, node structure, circuit,
or type circuit into the document to be printed.
The Function Chart Builder opens the Print PC Section dialog box.

3BDS 100 595R401 4-285

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-174. Print PC Section

• PC Program(s)
Select PC programs here to include them in the PC Diagram and/or the Tree Listing.

• All PC Programs
Select this check box to include all PC programs in the PC Diagram and/or the Tree
Listing.

• Function Chart
Select this check box to include the PC Diagram document part.

• All Pages
Select this option to include all the pages of the function chart in the PC Diagram.

• Pages
If you have selected only one PC program, select this option to include only the specified
pages of the function chart in the PC Diagram document part.
Define the page range in the From and To text boxes.

• From, To
If Pages is selected, edit in these text boxes the page range of the function chart to be
included in the PC Diagram document part.
Or drop down the list box part to select one of the existing page numbers.
Be sure the “From” page precedes the “To” page. Check page order in the list box parts.

NOTE
Due to fixed page numbers pages are not necessarily in strict numerical order.
The “To” page number is not necessarily greater than the “From” page number.

4-286 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

• Print Only on Success

If you select this check box, the Function Chart Builder checks whether all pages of the
PC Diagram in the specified range can be printed with the current layout.
If the layout check fails, the PC Diagram is not printed. Instead, the Function Chart
Builder opens the Output window and displays the list of pages with layout problems.
If you clear this check box, all the pages of the PC Diagram in the specified range are
printed. In case of pages not fitting to current layout the Function Chart Builder opens the
Output window and displays the list of pages with layout problems, and prints just a
message instead of the corresponding part of function chart, for example:
PC element is too large ...
Modify page layout by changing rows/column width.
First PC element on page: PC2.1.4 NOVATUNE (1,0)
Last PC element on page: PC2.1.4 NOVATUNE (1,0)

• Tree
Select any of the check boxes All Elements, Structure Elements, and Top of Page
Elements to include the Tree Listing document part. The Tree Listing document part will
contain one to three PC element lists according to the selected check boxes.
Footer text entered in the Edit | Document Texts command is displayed and printed in the
bottom lines of each page.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file of the PC Diagram with default extension PCF and of the Tree Listing with
default extension PCT in the \LIST subdirectory.

File | Print, TC/CI Symbols Included

Select the TC/CI Symbols check box in the Document group box of the Print dialog to include
symbol values of instantiated type circuits and located circuits in the selected node, node
structure, or circuit into the document to be printed.
The Function Chart Builder opens the Print TC/CI Symbols dialog box.

Figure 4-175. Print TC/CI Symbols

3BDS 100 595R401 4-287

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• PC Program(s)
Select PC programs here to include their symbols in the TC/CI Symbols document part.

• All PC Programs
Select this check box to include the symbols of all PC programs in the TC/CI Symbols
document part.

• Include Default PU Symbols

Select it to include default values of project-unique (PU) symbols in the TC/CI Symbols
document part.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension SYL in the \LIST subdirectory.

File | Print, Module Listing Included

Available only for AC 100 Series target.
Select the Modules check box in the Document group box of the Print dialog to include the
Module Listing into the document to be printed.
It gives you an overview of the used modules (boards).
The Function Chart Builder opens the Print Modules dialog box.

Figure 4-176. Print Modules

• By Address
Select this option to generate the Module Listing document part with listing order based on
increasing addresses of the modules.

• By Item Designation
Select this option to generate the Module Listing document part with listing order based on
increasing item designations of the modules.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension ML in the \LIST subdirectory.

File | Print, PC Cross-reference Listing Included

Select the PC Cross Reference check box in the Document group box of the Print dialog to
include the list of cross references in PC program(s) into the document to be printed. The listing
includes the page numbers from the PC Section separated by ’-’.

4-288 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

The Function Chart Builder opens the Print PC Cross Reference dialog box.

Figure 4-177. Print PC Cross Reference

• PC Program(s)
Select PC programs in this list box to include their PC references in the PC Cross-
reference Listing.
• All PC Programs
Select this check box to include PC references of all PC programs in the PC Cross-
reference Listing.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension PXR in the \LIST subdirectory.

File | Print, DB Cross-reference Listing Included

Select the DB Cross Reference check box in the Document group box of the Print dialog to
include the list of DB references in PC program(s) into the document to be printed. The listing
includes the page numbers from the PC Section separated by ’-’.

3BDS 100 595R401 4-289

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder opens the Print DB Cross Reference dialog box

Figure 4-178. Print DB Section

• Filter/Callname and Name

Select these check boxes to limit the printing of DB references to DB elements with
callnames and/or instance names corresponding to the filters. Open the list box parts of the
adjacent combo boxes to see earlier filters and select one. Or edit directly in the text box
part. Wildcards ‘*’ and ‘?’ are also allowed.

• Item Designation/From and To

Select these check boxes to limit the printing of DB references to an item designation
range of DB elements. Open the list box parts of the adjacent combo boxes to see earlier
“From” and “To” values. Select a filter in the list box part of the adjacent combo box or
edit directly in the text box part.
The Function Chart Builder includes the DB references of all PC programs in the DB Cross-
reference Listing.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension DXR in the \LIST subdirectory.

4-290 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

File | Print, CI Usage Listing Included

Select the Circuit Usage check box in the Document group box of the Print dialog to include a
list on usage of circuits into the document to be printed.
The Function Chart Builder opens the Print Circuit Usage dialog box.

Figure 4-179. Print Circuit Usage

• NSS-File(s)
Select this option to generate the Circuit Usage Listing on the basis of the available *.NSS
files.

• ODB(s)
Select this option to generate the Circuit Usage Listing on the basis of the available *.ODB
files.
The Function Chart Builder generates the Circuit Usage Listing, which contains all existing
circuits in the project and points out the node in which they are located.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension UCI in the \LIST subdirectory.

File | Print, Option Listing Included

The Function Chart Builder generates a document with the options and base software of the
object you are working on.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension OL in the \LIST subdirectory.

File | Print, DB Names Included

Select the DB Names check box in the Document group box of the Print dialog to include the
list of DB names in the document to be printed. The listing includes the DB element instance
names of the compete DB Section.

3BDS 100 595R401 4-291

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder opens the Print DB Names dialog box

Figure 4-180. Print DB Names

Filter/Callname and Name

Select these check boxes to limit the printing of DB names to DB elements with callnames
and/or instance names corresponding to the filters. Open the list box parts of the adjacent
combo boxes to see earlier filters and select one. Or edit directly in the text box part.
Wildcards ‘*’ and ‘?’ are also allowed.

• Item Designation/From and To

Select these check boxes to limit the printing of DB names to an item designation range of
DB elements. Open the list box parts of the adjacent combo boxes to see earlier “From”
and “To” values. Select a filter in the list box part of the adjacent combo box or edit
directly in the text box part.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension NAM in the \LIST subdirectory.

File | Print, PC Names Included

Select the PC Names check box in the Document group box of the Print dialog to include the
PC names of the selected node, node structure, circuit, or type circuit into the document to be
printed.
The Function Chart Builder opens the Print PC Names dialog box.

4-292 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

Figure 4-181. Print PC Names

• PC Program(s)
Select PC programs here to include PC Names of these PC Program(s) in the PC Names
Listing.

• All PC Programs
Select this check box to include PC Names of all PC programs in the PC Names Listing.

• Instance Names
Select this check box to include the PC Instance Names in the PC Names Listing.

• Signal Names
Select this check box to include the PC Signal Names in the PC Names Listing.

• Item Designation
If you have selected only one PC program, select this option to include only the specified
item designations of the function chart in the PC Names document part.
Define the PC Item Designations in the From and To text boxes.

• From, To
Select these check boxes to limit the printing of PC names to an item designation range of
PC elements. Open the list box parts of the adjacent combo boxes to see earlier “From”
and “To” values. Select a filter in the list box part of the adjacent combo box or edit
directly in the text box part.

3BDS 100 595R401 4-293

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTE
Item designations are not necessarily in strict numerical order.
The “To” item designation is not necessarily greater than the “From” item
designation.

File | Print, DAT Cross-reference Listing Included

Select the DAT Cross Reference check box in the Document group box of the Print dialog to
include the list of DAT DB elements into the document to be printed.
The DAT Crossreference Listing contains all the visible DATs, and if there are any, the extended
DB elements to which the DATs are attached. In this document you can explicitly check the
presence of the DATs automatically generated by extended DB elements.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension DAT in the \LIST subdirectory.

File | Print, DSP Cross-reference Listing Included

Select the DSP Cross Reference check box in the Document group box of the Print dialog to
include the list of DSP DB elements into the document to be printed.
The DSP Crossreference Listing contains all the visible DSPs, the DATs referenced by them,
and if there are any, the extended DB elements to which the DSPs are attached. In this document
you can explicitly check the presence of the DSPs automatically generated by extended DB
elements.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension DSP in the \LIST subdirectory.

File | Print, EVS Cross-reference Listing Included

Select the EVS Cross Reference check box in the Document group box of the Print dialog to
include the list of EVS DB elements into the document to be printed.
The EVS Crossreference Listing contains all the visible EVSs, and if there are any, the extended
DB elements referenced by the EVSs. In this document you can explicitly check the presence of
the EVSs automatically generated by extended DB elements.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension EVS in the \LIST subdirectory.

File | Print, MDAT Cross-reference Listing Included

Select the MDAT Cross Reference check box in the Document group box of the Print dialog
to include the list of MDAT DB elements into the document to be printed.
The MDAT Crossreference Listing contains all the visible MDATs, and if there are any, the
extended DB elements to which the MDATs are attached. In this document you can explicitly
check the presence of the MDATs automatically generated by extended DB elements.
If the Print to File check box is selected in the Print dialog box, the Function Chart Builder
stores the output file with default extension MDT in the \LIST subdirectory.

4-294 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

4.5.4.23 File | Print Setup…

Use this command to select a printer and a printer connection.

Figure 4-182. Print Setup

• Printer
The Name combo box shows the selected printer. The static text shows some of its
parameters. Drop the combo box down to list available printers and select another one.
Activate the Properties button to change properties of the selected printer.
Use the Control Panel of Windows NT to install printers and configure ports.

• Paper Size and Source

Select the size of paper that the document is to be printed on.
Some printers offer multiple trays for different paper sources. Specify the tray here.
Paper size and orientation will be preserved if you exit the current Function Chart Builder
session and start a new one, or if you select another printer, or the default printer changes.

• Orientation
Select Portrait or Landscape corresponding to the selected layout template.
To check or select layout templates, activate the Page Setup button.

• Page Setup
Activate this button to open the Page Setup dialog.
See Section 4.5.4.24, File | Page Setup… for dialog.

• Network
Activate this button to connect to a network location, assigning it a new drive letter.

3BDS 100 595R401 4-295

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.4.24 File | Page Setup…

Use this command to choose a layout template and set page size for your diagrams.

Figure 4-183. Page Setup

• Page Layout Template

Select the page layout template for your diagrams in the drop-down list box.
The size of the selected template, such as A3, A4, US legal, US letter, should correspond
to paper sizes handled by the printer.
To check or select paper size for the printer, choose the File | Print Setup command.

• Height and Width

Edit here the number of rows and columns for a diagram page.
Activate the Use Defaults button to fetch default values corresponding to the page layout
template.

• Use Defaults
Activate this button to fetch default values corresponding to the selected page layout
template as delivered with the Function Chart Builder.

• Project Defaults
Activate this button to fetch the project-specific defaults for layout (layout template and
actual page size) as set in Application Builder for the selected project.

4-296 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.4 File Menu

4.5.4.25 File | Exit

Use this command to close the windows of the Function Chart Builder and leave it.
It is equivalent with the Control | Close command in the Application Control menu.
If there are unsaved changes, the Function Chart Builder asks you whether you want to save
them in internal data representation before exiting.
Answer Yes if you want to save the changes and then leave the Function Chart Builder.
Answer No only if you are sure you want to leave the Function Chart Builder without saving the
changes.
Answer Cancel if you changed your mind and you do not want to leave the Function Chart
Builder.

CAUTION
If you answer No, you lose all the changes that you made since the last
File | Save, File Save and Load, or File | Exit command.
Source code and print files are not affected by Exit.

If you answer Yes and the Generate Source Code on Exit option was set by the last
Options | Preferences command, the Function Chart Builder starts the File | Generate Source
command to save the changes also in source code form.
If you are testing an AC 100 Series application on-line, Exit saves all selected display terminals
and all prepared force values by writing them to the Function Chart Builder’s internal data
representation.

CAUTION
When leaving the Function Chart Builder, the PC force values are canceled on the
target but the DB force values remain active.

If you are working with an on-line connected AC 100 Series target, the Function Chart Builder
prompts you also to load the possible modifications to the target and to disconnect the target.

3BDS 100 595R401 4-297

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4-298 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

4.5.5 Edit Menu

4.5.5.1 Edit | Undo

Shortcut: CTRL+Z
Use this command to undo a previous operator action, generally the last one.
You can choose this command repeatedly to undo several actions.
The name of the command in the Edit menu reflects the operator action to be undone:
Undo Delete …, Undo Create …, Undo Cut, Undo Paste, Undo Edit …, Undo Upload,
Undo Document Texts, Undo Move …, Undo Item Designation, Undo Renumber,
Undo … Page Division, Undo (Dis)Connect PC, Undo … Name, Undo … Unit,
Undo … Display, Undo … Force Value, Undo Invert PC Terminal,
Undo Insert PC Terminal.
The Function Chart Builder restores the previous state of the object you are working on and
refreshes the affected open windows accordingly.

4.5.5.2 Edit | Redo

Shortcut: CTRL+Y
Use this command to redo a previously undone operator action, generally the last one.
You can choose this command repeatedly to redo several undone actions.
The name of the command in the Edit menu reflects the operator action to be redone:
Redo Delete …, Redo Create …, Redo Cut, Redo Paste, Redo Edit …, Redo Upload,
Redo Document Texts, Redo Move …, Redo Item Designation, Redo Renumber,
Redo … Page Division, Redo (Dis)Connect PC, Redo … Name, Redo … Unit,
Redo … Display, Redo … Force Value, Redo Invert PC Terminal,
Redo Insert PC Terminal.
The Function Chart Builder restores the state of the object you are working on and refreshes the
affected windows accordingly.

4.5.5.3 Edit | Create…

Shortcut: INS

Edit | Create… - for PC Section

Use this command to insert a PC element—or a type circuit or a circuit creating PC elements—
in the PC program corresponding to the active PC Section window.
The Function Chart Builder opens the sizable Create Element dialog box.

3BDS 100 595R401 4-299

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-184. Create PC Element

• Element Type
Contains type of the element to be inserted
PC for PC element
If applicable, also:
– TC for type circuit
– CI for circuit

• Item Designation
Shows the suggested item designation of the element to be created. It is suggested on
“lowest free” basis.
NOTE
If you are working on a type circuit or a circuit, an asterisk ‘*’ stands for the item
designation of the first PC element of the object.

You can edit the last number of the item designation and change it to some other free item
designation.

4-300 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

• Insert
Select the appropriate option in this group box to create the element on the same level as
the selected PC element in the active PC Section window, or by one level lower.
The At Item Designation text box reflects the reference item designation, that is, the item
designation of the element, which is selected at the start of the current create operation.

NOTE
If you are working on a type circuit or a circuit, an asterisk ‘*’ stands for the item
designation of the first PC element of the object.

You can also edit the At Item Designation text box and change it to the item designation
of any existing PC element within the current PC program or—in case of type circuits and
circuits—within the PC section.

• Instance Name
Edit an optional instance name for the PC element in the text box part of the
Instance Name drop-down combo box.
Drop down the list part to display recent instance names. Here you can also select an
instance name to copy it to the text box part for further edition.
The instance name is shown after a slash‘/’ in form of item_designation/instance_name
in the function chart.
You can use also symbols or symbolic expressions in instance_name, for example,
*+2.1/CNT<INST_NR>.
See also Section 4.4.8.5, Use of Symbols.

• Filter/Callname
Select a filter in the list box part of the Filter drop-down combo box or edit it in the text
box part to show only PC elements with a certain callname in the list box below.
Wildcards ‘*’and ‘?’are also allowed.
Close the new filter condition with ENTER to make it effective.
The list part of the Filter drop-down combo box contains the recently used filters.
The Callname text box contains the callname of the element to be created, and if
applicable, its call parameters.
Select a callname in the list box below. You can also edit here any callname, which is listed
in the list box.
If Element Type is PC, the call parameter values, if any, are listed in parentheses and
separated by commas after the callname.
Then leave the default parameter values unchanged or edit them here or in the
Edit Call Parameters dialog box.
See Section 4.5.5.10, Edit | Call Parameters… for dialog.

3BDS 100 595R401 4-301

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• List Box
Contains all elements, which satisfy the filter condition, correspond to the selected element
type, and are available for the selected insert level.

• Multiple Columns
Select this check box to present the elements in the list box in multiple columns.
Unselect this check box to present the elements in the list box in one wide column.

• Call Parameters
Available if Element Type is PC.
Activate this button to open the Edit Call Parameters dialog box.
See Section 4.5.5.10, Edit | Call Parameters… for dialog.
If the call parameters are not edited there, the default values are used.

• Symbol Values
Available if Element Type is TC or CI:
Activate this button to open the Edit Symbol Values dialog box.
See Section 4.5.5.15, Edit | Symbol Values… for dialog.
If the symbol values are not edited there, the default values are used. You can also use
further symbols for symbol values.

• Apply
Activate this button to create more than one element.
A similar action as that of the OK button but you remain in the Create Element dialog
and the Function Chart Builder shows the item designation of the recently created element
in the At Item Designation text box and the item designation of the next element to be
created in the Item Designation text box.
The Function Chart Builder updates the PC diagram in the PC Section windows at once or after
closing the Create Element dialog box depending on the Update Function Chart on Apply
option set in the Options | Preferences command.

Edit | Create… - for DB Section

Use this command to insert a DB element—or a type circuit or a circuit creating or modifying
DB elements—in the active DB Section window.
The Function Chart Builder opens the sizable Create Element dialog box.

4-302 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

Figure 4-185. Create DB Element

• Element Type
Contains type of the element to be inserted
DB for DB element.
If applicable, also:
– TC for type circuit creating or modifying DB elements
– CI for circuit creating or modifying DB elements.

• Modify Attribute
Select this check box in the following cases:
– You are editing a type circuit and you want to modify terminals of a DB element that
you anticipate in nodes, node structures, or circuits, in which the type circuit is
instantiated.
– You are editing a circuit and you want to modify terminals of a DB element that you
anticipate in the node structure, in which the circuit is located.

• Use item_designation as Template

If checked, the Function Chart Builder takes the item_designation DB element as template
for further instances of the same element. That means, the Function Chart Builder offers
the terminal values of item_designation in the Edit DB Terminal Values dialog box also
for further instances and the defaults from the DB element description are temporarily
overridden.

3BDS 100 595R401 4-303

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Filter/Callname
Select a filter in the list box part of the Filter drop-down combo box or edit it in the text
box part to show only DB elements with a certain callname in the list box below.
Wildcards ‘*’and ‘?’are also allowed.
Close the new filter condition with ENTER to make it effective.
The list part of the Filter drop-down combo box contains the recently used filters.
The Callname text box contains the callname of the element to be created.
Select a callname in the list box below. You can also edit here any callname, which is listed
in the list box.

• Instance
The Instance text box shows the suggested default item designation of the element to be
created. Wildcard asterisk ‘*’ stands for the “lowest free” index of the item designation.
Leave the default item designation unchanged or edit a new complete item designation by
substituting the asterisk ‘*’. After a slash ‘/’ you can also add an optional instance name in
form of item_designation/instance_name.
You can use also symbols or symbolic expressions in item_designation and
instance_name, for example, AI<MOD_NR>/ANAINP_<MOD_NR>.
See also Section 4.4.8.5, Use of Symbols.
The list box part of the Instance drop-down combo box contains the recently used item
designations and assigned instance names.

• List Box
Contains all elements, which satisfy the filter condition and correspond to the selected
element type.

• Multiple Columns
Select this check box to present the elements in the list box in multiple columns.
Unselect this check box to present the elements in the list box in one wide column.

• Apply
Activate this button to create more than one element.
A similar action as that of the OK button but you remain in the Create Element dialog.

• DB Terminal Values
Available if Element Type is DB.
Activate this button to open the Edit DB Terminal Values dialog box.
See Section 4.5.5.13, Edit | DB Terminal Values… for dialog.
If the terminal values are not edited there, the default values are used.

4-304 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

• Symbol Values
Available if Element Type is TC or CI.
Activate this button to open the Edit Symbol Values dialog box.
See Section 4.5.5.15, Edit | Symbol Values… for dialog.
If the symbol values are not edited there, the default values are used. You can also use
further symbols for symbol values.
The Function Chart Builder creates the DB instance if the instance name is legal and the
instance does not exist yet.
If you define the DB instance name by a new symbol or a symbolic expression containing a new
symbol, the Function Chart Builder opens the Create a Symbol dialog.
For dialog see Edit | Create - for Symbol Section command.
The Function Chart Builder updates the DB element list in the DB Section windows.

Edit | Create… - for Symbol Section

Use this command to create a symbol in the active Symbol Section window.

Figure 4-186. Create Symbol

• Name
Type the name of the symbol to be created without symbol delimiters ‘<’ and ‘>’ in the
text box part of this combo box.
The list box part contains the already existing symbol and terminal names.

NOTE
Symbol names and terminal names must be unique.

• Kind
Select symbol kind by the corresponding option.

3BDS 100 595R401 4-305

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Symbols can have different symbol kinds (scope) in different objects as shown in the
following table:

Table 4-30. Symbol Kinds in Different Objects

Object Symbol Kind

Type circuit Instance-Unique (IU)
Project-Unique (PU)
Circuit Instance-Unique (IU)
Project-Unique (PU)
Location-Unique (LU)
Node structure Project-Unique (PU)

• Type
Select the symbol (data) type from the drop-down list box of this group box. You can also
edit in the text box part and change it to any other type listed in the list box part.
If you selected A (String) type, edit the length in the Size text box.
Maximum length of a string is 80 characters.

• Default Value
Type here an appropriate value, a symbolic expression, or formula, or leave it empty.
See also Section 4.4.8.5, Use of Symbols.
A default value is optional for instance-unique (IU) symbols and mandatory for location-
unique (LU) and project-unique (PU) symbols.
The Browse Button in only available if PPA (Process Portal A) is installed. It can be used
if CBA Interface is installed and the current FCB is started out of the Engineering Studio
Workplace. For further information see Control Builder A Interface Manual.

• Apply
Activate this button to create more than one symbol.
A similar action as that of the OK button but you remain in the Create Element dialog.
The Function Chart Builder assigns the default value if it is valid for the data type as set in
Type.
If you assign a new symbol, a symbolic expression, or formula, containing a new symbol in
Default Value, the Function Chart Builder opens the Create Symbol dialog for the new symbol
again.
The Function Chart Builder updates the symbol list in the Symbol Section windows.

4-306 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

Edit | Create… - for TC/CI Terminal Section

Use this command to create a type circuit terminal or circuit terminal in the active TC/CI
Terminal Section window..

Figure 4-187. Create TC/CI Terminal

• Name
Type the name of the terminal to be created without symbol delimiters ‘<’ and ‘>’ in the
text box part of this combo box.
The list box part contains all already created symbol and terminal names.

• Number
Shows the suggested terminal number.
The list box part contains all already created terminal numbers.
You can also edit in the text box part any free terminal number in the range 1 - 999.

• Kind
Select terminal kind by the corresponding option: In (input), Out (output), or FP (function
parameter).
Terminal kind must be the same as the kind of PC terminal, to which it is connected within
the type circuit or circuit.
Select Out if both input and output PC terminals are connected.

• Type
Select terminal data type from the drop-down list box of this group box. You can also edit
in the text box part and change it to any other type listed in the list box part. Terminal data
type must be compatible with the data type of the corresponding PC terminal.

3BDS 100 595R401 4-307

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

If you selected A (String) type, edit the length in the Size text box. Maximum length of an
array is 80 characters. You can define size also for groups of other types, for example, B
(Boolean) or I (integer). You can define type or size also by a symbol.

• Default Connection
Type here an appropriate value or a symbolic expression. A default connection is optional.
See also Section 4.4.8.5, Use of Symbols.

• Function Parameter Limit

In case of functional parameter kind (FP) type the allowed minimum and maximum values
in this group box.

• Apply
Activate this button to create more than one terminal. A similar action as that of the OK
button but the Create TC/CI Terminal dialog box remains open, and the Function Chart
Builder increases the suggested terminal number in the Number text box.

• Attributes
Activate this button to specify terminal attributes.
The Function Chart Builder opens the Edit TC/CI Terminal Attributes dialog box.

Figure 4-188. Edit TC/CI Terminal Attributes

- Type
Shows the data type of the terminal, the attributes of which you are editing.
- Presentation
Select any of the check boxes here to include the corresponding attribute for the
graphical presentation of the type circuit or circuit.

4-308 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

Adjust
If selected, the actual group of input terminals is adjusted to the actual group of
output terminals.
Dynamic
If selected, a triangle is added at the terminal, indicating that it is a dynamic input,
for example, a clock input.
- Miscellaneous
Select any of the check boxes here to include the corresponding attribute for the
graphical presentation of the type circuit or circuit.
DB Reference
If selected, this terminal expects a DB connection.
Non-Invertible
If selected, the terminal can not be inverted by the PC-Terminal | Invert command.
- Separation
Select one of the options in this group box to include the corresponding attribute for
the graphical presentation of the type circuit or circuit.
None
If selected, the actual terminal follows the previous one immediately.
Blank Line
If selected, a blank line will be inserted between the previous terminal and the actual
one.
Waist
If selected, a waist will be inserted between the previous terminal and the actual one.
The Function Chart Builder assigns the attributes to the terminal for the graphical
presentation of the type circuit or circuit.
The Function Chart Builder assigns the default connection if the connection rules are fulfilled.
If you assign a new symbol or a symbolic expression containing a new symbol in
Default Connection, the Function Chart Builder opens the Create a Symbol dialog.
For dialog see Edit | Create - for Symbol Section command.
The Function Chart Builder updates the terminal list in the TC/CI Terminal Section windows.

3BDS 100 595R401 4-309

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Edit | Create… - for Test Table

Use this command to create or edit a new display or force entry in the Instance, Terminal, …,
State list box of the active Test Table window.

Figure 4-189. Create Test Table Entry

• Element[:Terminal] or Signal Name

Type the entry for the Test Table in the text box part of this combo box.
You can enter an item designation without or with terminal number or name or a signal
name. An equal sign ‘=’ indicates a DB terminal.
The list box part contains the recently created entries.

• Terminal
Type the terminal name or number in the text box part of this combo box if you entered an
item designation without terminal number or name in the Element[:Terminal] or Signal
Name box. Else ignore the contents of this text box.
Drop down the list box part to inspect the terminal names or numbers available for the
given PC or DB element.

• Value
Type the value to be forced in the text box part of this combo box if you create or edit this
entry for force.
Drop down the list box part to inspect the recently entered force values.

• For Force
Select this option if you create an entry for force.

• For Display
Select this option if you create an entry for display.

4-310 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

• Apply
Activate this button to create or edit more than one entry.
A similar action as that of the OK button but the Create/Edit Table Entry dialog box
remains open.
The Function Chart Builder updates the Instance, Terminal, …, State list box of the active
Test Table window.

4.5.5.4 Edit | Cut

Shortcut: CTRL+X
Use this command to cut the selected part of the PC section or to cut one or more PC programs
selected in the *.ODB window, that is, to move one or more selected PC elements (or
instantiated type circuits or located circuits) with its or their connections, names, and symbol
values to the paste buffer, and then to delete the selected part of the PC section or the selected
PC programs.
Cut is possible only during off-line editing.
See Section 4.5.8.3, PC-Section | Select… for selecting several PC elements.

4.5.5.5 Edit | Copy

Shortcut: CTRL+C
Use this command to copy the selected part of the PC section or to copy one or more PC
programs selected in the *.ODB window, that is, to copy one or more selected PC elements
(or instantiated type circuits or located circuits) with its or their connections, names, and symbol
values to the paste buffer.
The selected part of the PC section or the selected PC programs remain unchanged.
See Section 4.5.8.3, PC-Section | Select… for selecting several PC elements.

4.5.5.6 Edit | Paste…

Shortcut: CTRL+V
Use this command to copy the contents of the paste buffer to the PC section, that is, to insert one
or more PC elements (or instantiated type circuits or located circuits) with or without their
connections, names, and symbol values in the paste buffer at some insertion point.
The paste buffer may contain also one of more PC programs.
The contents of the paste buffer remain unchanged.
Paste is possible only during off-line editing.
NOTE
Be sure the first PC element in the past buffer matches to the insertion point.

See Section 4.5.8.3, PC-Section | Select… for selecting several PC elements.

3BDS 100 595R401 4-311

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder displays the following dialog box:

Figure 4-190. Paste PC Section

• Insert
The first two static lines show the first PC element and the number of elements in the paste
buffer.

• Item Designation
Shows the item designation of the next element after pasting.

• At Item Designation
This static line shows the item designation of the insertion point.

• On Same Level and On Lower Level

These options are only enabled if the level of insertion is ambiguous.

• Options…
Activate this button to open the Paste Option PC Section dialog box. You can define the
paste options there, that is, preserve connections, names, symbol values, and so on, at
pasting the PC elements (or instantiated type circuits or located circuits), or not.

• Replace & Paste…

Activate this button to open the Replace and Paste PC Section dialog box.
You can select different items there and define replacements for them.
By selecting appropriate set of options and appropriate replacements you can optimize
efficiency of editing and minimize paste conflicts.

4-312 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

Activate the Options… button to open the Paste Option PC Section dialog box.

Figure 4-191. Replace Options PC Section

You can define the paste options here, that is, preserve connections, names, symbol values, and
so on, at pasting the PC elements (or instantiated type circuits or located circuits), or not.
- Input and Output Connections To
Select the corresponding check boxes to paste different kinds of connections together
with the PC elements (or instantiated type circuits or located circuits).
- Connection to External PC Element
This group handles connections to PC elements outside the copied/paste range.
Select the corresponding check box “Display Warnings on Paste” to get for each
connection to external PC element a warning and the possibility to replace it by a
connection, for example, to a TC terminal.
Select check box "Copy and Paste Multiple Input Connections to PC" to preserve
multiple input connections to external PC elements.

NOTE
A change of that settings does not effect paste, but next cut/copy
command.

3BDS 100 595R401 4-313

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

If unchecked, such connections are separated into two independent connections.

Warnings may occur on paste in case of duplicate names. This equals the behavior of
former FCB releases.
If checked, multiple input connections are preserved and there are no warnings like
"duplicate name".

Figure 4-192. Multiple Input Connection to PC

Select check box "Copy and Paste (Virtual PC) Names instead of Item Designations
on Input Connections" to cut/copy and paste input connections to external PC
elements with a named source.

NOTE
A change of that settings does not effect paste, but next cut/copy
command.

If unchecked, such connections are copied and pasted using the item designation of
the source terminal. This equals the behavior of former FCB releases.
If checked, such connections are copied and pasted using the name of the source.
By that, you can cut or copy some functionality in the PC section and paste it in
another PC program, node, TC, or CI where the named source exists but not the
original item designation.
If you additionally enable support for virtual connections in dialog Options |
Preferences, you can also replace the copied (virtual) names on "Replace and Paste
PC Section", item "Connections to virtual PC".
- Instance Names, Names, and Units
Select the corresponding check boxes to paste the instance names, signal names and
units together with the PC elements (or instantiated type circuits or located circuits).
- Page Breaks and Headlines
Select the corresponding check box to paste the page divisions and headlines together
with the PC elements (or instantiated type circuits or located circuits).

4-314 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

Activate the Replace and Paste… button to open the sizable Replace and Paste PC Section
dialog.

Figure 4-193. Replace and Paste PC Section, General

In case of TC/CI symbol values the Function Chart Builder displays a modified sizable
Replace and Paste PC Section dialog box.

3BDS 100 595R401 4-315

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-194. Replace and Paste PC Section, for TC/CI Symbol Values

You can select different items here and define replacements for them.
- Select Item
The drop-down list box part of this combo box contains the items, for which you can
make replacements:
• Signal names, instance names, headlines
• DB elements, symbols, TC/CI terminals, and virtual PC terminals in connections
• TC/CI symbol values.
The Function Chart Builder fills the List Box accordingly with all occurrences of
names or DB elements, and so on, in the paste buffer.
- List Box
The Function Chart Builder displays here all occurrences of names or DB elements,
and so on, in the paste buffer according to the selection in Select Item.
You can edit here directly and replace original paste buffer contents by new names,
DB elements, and so on.
Use the Find Next, Replace and Replace All functions to edit more effectively.
- Find What
Edit here a search pattern to be found in the List Box.
The drop-down list box part contains the search patterns, which were recently edited.
Select here a search pattern to copy it to the text box part.
- Replace With
Edit here a replace pattern that has to replace the selected search pattern in some or
all occurrences in the List Box.

4-316 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

The drop-down list box part contains the replace patterns, which were recently
edited.
Select here a replace pattern to copy it to the text box part.
- Match Whole Word Only
Select this check box if you want to find the search pattern only as whole word in the
List Box.
- Find Next
Activate this button to find and select the first and then the next occurrence of the
search pattern in the List Box.
- Replace
Activate this button to replace the search pattern selected (found) in the List Box by
the replace pattern.
If necessary, the original paste buffer contents can be restored.
- Replace All
Activate this button to replace all occurrences of the search pattern in the List Box by
the replace pattern.
If necessary, the original paste buffer contents can be restored.
- Undo Replace
Activate this button to undo stored replacements.
The Function Chart Builder opens the Undo Replace PC Section dialog box.
Select here the scope of undo, that is, define whether you want to restore the paste
buffer contents partly or completely.

Figure 4-195. Undo Replace PC Section

In case of the modified Replace and Paste PC Section dialog box:

- Symbol Values
Activate this button to open the Edit Symbol Values dialog box to change symbol
values of instantiated type circuits and located circuits.
For dialog see Section 4.5.5.15, Edit | Symbol Values….
Activate the OK button of the Paste PC Section dialog box to start pasting.
Or activate the OK button of the Replace and Paste PC Section dialog box to start pasting with
replaced items.

3BDS 100 595R401 4-317

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder opens the Output window (or iconizes it as set by
Options | Preferences), and lists messages about progress of pasting and about paste conflicts.
In case of paste conflicts the Function Chart Builder opens the following dialog box:

Figure 4-196. Paste Conflicts

This is a modeless dialog box offering the possibility to inspect the result of pasting and
solve conflicts before closing it. See Section 4.5.5.9, Edit | Process Conflicts.
Activate the OK button to accept the result of pasting and close the dialog box.
Else activate the Undo Paste button or choose the Edit | Undo Paste command.
- Static Text
A summary on result of pasting.
- Undo Paste
Activate this button to undo pasting (delete the pasted elements).

4.5.5.7 Edit | Delete

Shortcut: DEL

Edit | Delete - for PC Section

Use this command to delete the selected part of the PC section or one or more PC programs
selected in the *.ODB window, that is, to delete one or more selected PC elements
(or instantiated type circuits or located circuits).
To delete more than one element at once is possible only during off-line editing.
The Function Chart Builder automatically disconnects all existing connections of the element
and updates the PC diagrams in the corresponding PC Section windows.

NOTE
You cannot delete a single element having subordinated elements on lower
structure levels. Delete subordinate elements at first, or select the element
together with its subtree for deletion.

See Section 4.5.8.3, PC-Section | Select… for selecting several PC elements.

4-318 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

Edit | Delete - for DB Section

Use this command to delete a DB element currently selected in the active DB Section window.
Use this command also to delete type circuits or circuits, which create or modify DB elements,
contain no PC section, and are denoted collectively by $$TC and $$CI.
The Function Chart Builder updates the DB element list in the DB Section windows.

NOTE
To delete a type circuit (circuit), which is instantiated (located) by its PC section,
contains also a DB section, and is denoted collectively by $$DB_OF_TC
($$DB_OF_CI), select this type circuit (circuit) in the PC Section window.

Edit | Delete - for Symbol Section

Use this command to delete a symbol currently selected in the active Symbol Section window.
The Function Chart Builder updates the symbol list in the Symbol Section windows.

Edit | Delete - for TC/CI Terminal Section

Use this command to delete the type circuit terminal or circuit terminal, which is currently
selected in the active TC/CI Terminal Section window.
The Function Chart Builder updates the terminal list in the TC/CI Terminal Section windows.

Edit | Delete - for Test Table

Use this command to delete the selected entry in the Instance, Terminal, …, State list box.
Deleted force entries remain in the table with state `R´ until the deactivation of the values in the
target.

4.5.5.8 Edit | Find…

Shortcut: ALT+F3
Use this command to find the specified PC elements (or type circuits or circuits) or PC terminals
with the specified connection in the active PC Section window.

Figure 4-197. Find

3BDS 100 595R401 4-319

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Find What
Type in the text box part the search string, which you want to find.
You can use the wildcards asterisk ‘*’ and question mark ‘?’.
Omit ‘<’ and ‘>’ around the symbol in case of searched PC connection to symbol.
No search string is necessary if you want to find unconnected PC input terminal.
Open the list box part to select previous search strings.

• PC Element
Select the corresponding option in this group box if you want to find the PC element with
the specified item designation, or instance name, or the next PC element with the specified
callname.

• Direction
Select the Up option to search from the currently selected PC element and PC terminal to
the ones with higher item designation and higher terminal number.
Select the Down option to search from the currently selected PC element and PC terminal
to the ones with lower item designation and lower terminal number.

• PC Connection
Select the corresponding option in this group box if you want to find the next PC
connection to a source with specified name, to a specified symbol, TC/CI terminal, or DB
terminal, or find the next unconnected PC input terminal or the next virtual connection,
that is, a connection to an element that is specified but does not exist yet.

• Find or Find Next

Activate this button to start or repeat searching.
This dialog is modeless. So you can create or edit PC elements, DB elements, and so on, while
the dialog box remains open.
If the PC element or the terminal is found, the Function Chart Builder selects it (them) and
shows the corresponding page in the active PC Section window.

4.5.5.9 Edit | Process Conflicts

Shortcuts
Keys: F4
Mouse: double-click on a line indicating error in the Output window.
The Function Chart Builder offers this command to support the following:
• Debugging of application program errors
• Solution of source code problems
• Solution of editing errors, such as paste conflicts.
Use this command to open the source code file, for which a recent list file exist with errors, with
the AS100-EDIT editor.
Repeat this command to jump to every line, which caused an error, in the source file.
Use this command to open the Connect dialog box with the connection, which caused a
connection conflict during pasting.
Repeat this command to change to every conflicting connection.

4-320 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

4.5.5.10 Edit | Call Parameters…

Shortcut: ENTER
Use this command to inspect and modify call parameter values of the selected PC element in the
active PC Section window.
The Function Chart Builder opens the Edit Call Parameters dialog box.

Figure 4-198. Edit Call Parameters

• Callname and Item Designation

These static text lines show callname and item designation of the PC element, which is
currently selected in the active PC Section window.

• Call Parameter and Value

Edit here the value of the call parameter, which is selected in the list box.
Use UP and DOWN keys to change the selection in the list box.

• List Box
Contains all call parameters and values.
Use UP and DOWN keys to select a call parameter.
If you change some values and activate the OK button, the Function Chart Builder executes the
call parameter modification by the following steps:
1. Deletes the PC element with its old call parameters.
2. Creates the same PC element with new parameters.
3. Tries to reconnect all the original connections of the element.
If conflicts occur, for example, at reconnecting the terminals, the Function Chart Builder opens
the Output window (or iconizes it as set by Options | Preferences), and lists messages about
the conflicts.
To undo call parameter changes, choose the Edit | Undo Call Parameters command.
The Function Chart Builder updates the call parameter values in the list box and in the internal
representation and updates the PC Section windows.

3BDS 100 595R401 4-321

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

To set allowed cyclicities of structure elements for AC 400 Series or MP 200/1 objects,
see Section 4.5.7.3, Options | Cycle Times….

4.5.5.11 Edit | Name …

Shortcut: F5
Use this command to name or rename a PC terminal, in fact, to create or change an alias name
for a source, that is, for one of the following:
• For an output terminal of a PC element
• For a constant or a DB element terminal connected to an input terminal of a PC element in
an existing connection.
Or use this command to name or rename a PC element (or instantiated type circuit or located
circuit), that is, to assign an instance name to it.
Or use this command to name or rename a DB element (or instantiated type circuit or located
circuit) having a NAME terminal.

Figure 4-199. Create/Edit Name

• Item Designation
The text box part shows the item designation of the selected PC terminal or PC element.
You can also edit here the item designation and use also relative PC item designations, see
in Section 4.4.4.4, Connect Terminals by Editing the Connection Definition.
The drop-down list box part contains item designations of the PC terminals or PC
elements, which were recently involved in creation or edition of names.
Select here an item to copy it to the text box part.

• Name
Edit here the name for the source associated with the terminal or for the element, which is
shown by Item Designation.
The drop-down list box part contains all the existing names.
Select here a name to copy it to the text box part.

4-322 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

• Apply
Activate this button to create or edit more than one name.
A similar action as that of the OK button but you remain in the Create/Edit Name dialog.
This dialog is modeless. So you can create or edit PC elements, DB elements, and so on, while
the dialog box remains open.
The Function Chart Builder creates the specified name or changes the name as specified, and in
case of terminal names defines or redefines it as alias for the associated source.
To inspect names attached to other terminals or elements, use the Edit | Name command
without entering any new data, or open the Name Table window by the Window | Name Table
command.

4.5.5.12 Edit | Delete Name

Shortcut: SHIFT+F5
Use this command to remove the assigned name from the selected DB element having a NAME
terminal, or from the selected PC terminal or PC element (or instantiated type circuit or located
circuit).

4.5.5.13 Edit | DB Terminal Values…

Use this command to edit terminal values of DB elements in the active DB Section window.

3BDS 100 595R401 4-323

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder opens the Edit DB Terminal Values dialog box.

Figure 4-200. Edit DB Terminal Values

• Element Type
This static text shows the type of the selected DB element.

• Graphic Symbol Selection / Part of DB Terminals

Simple data base elements consist of one single graphic symbol, whereas more complex
elements are split into several graphic symbols. Each graphic symbol contains a part of the
terminals, normally a group of related terminals.
The names of available graphic symbols are listed in this drop-down list box.
Select the appropriate graphic symbol to show the corresponding part of terminals below.

• Logical File, Logical Record

A hint for storage of the DB element in the internal representation.
It is not applicable for all DB elements.

• Graphic Symbol
It symbolizes the part of DB terminals selected in the drop-down list box.

4-324 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

Type the new DB terminal values in the editable fields on the left side of the graphic
symbol or leave the shown values or default values unchanged.
You can also use symbolic expressions for DB terminals in type circuits, circuits, and node
structures. See also Section 4.4.8.5, Use of Symbols.
For DB elements, which have the physical address terminals BUS, STATION, and
POSITION, the Function Chart Builder checks that the new DB element does not collide
with physical addresses of the existing DB elements.
BUS=0, STATION=0, and POSITION=0 means an unspecified address.
From referencing DB elements, such as DSP, MVB, or MVI, you can directly switch to
referenced DB elements, such as a DAT or MVC, by clicking with the right mouse button
on the corresponding REFn or CHANNELn terminal.

• Default
Activate this button to set (restore) the default values as they are defined in the (original)
DB element description.
The values from a possible template are overridden.
For setting up a template see Section 4.5.5.3, Edit | Create… - for DB Section.

• References
Activate this button to show the references, if any, to and from the DB instance selected
in the Item Designation, Instance Name, Attr., Callname, Address list box of the
DB Section window.

Figure 4-201. References of DB Element

Select a referenced or referencing item in the list box.

The selection is echoed in the text box.
Activate the Goto button to switch to that DB instance in the Edit DB Terminal Values
dialog box.

• Apply
Activate this button to edit DB terminal values for more than one element.

3BDS 100 595R401 4-325

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

A similar action as that of the OK button but you remain in the Edit DB Terminal Values
dialog.

• Previous and Next

Activate these buttons to switch to the previous or next DB instance displayed in the
Item Designation, Instance Name, Attr., Callname, Address list box of the DB Section
window.
NOTE
The item designation and instance name filters in the Item Designation,
Instance Name, Attr., Callname, Address list box of the active DB Section
window are taken into account.

The Function Chart Builder assigns the values to the terminals of the DB instance if the values
are legal.
If you define the DB terminal value by a new symbol or a symbolic expression containing a new
symbol, the Function Chart Builder opens the Create a Symbol dialog.
For dialog see Section 4.5.5.3, Edit | Create… - for Symbol Section.
To set allowed scan times of DB elements for AC 400 Series or MP 200/1 objects,
see Section 4.5.7.3, Options | Cycle Times….

4.5.5.14 Edit | Symbol…

Use this command to modify the symbol, which is selected in the active Symbol Section
window.

Figure 4-202. Edit Symbol

• Name
The text box part shows the selected symbol.
The list box part contains the symbol names as displayed in the
Name, Kind, Type, Default Value list box of the Symbol Section window.

4-326 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

NOTE
The name and kind filters in the Name, Kind, Type, Default Value list box of the
active Symbol Section window are taken into account.
Select the symbol to be edited in the list box part.

• Kind
Change symbol kind by the corresponding option here.
Symbols can have different symbol kinds (scope) in different objects:

Table 4-31. Symbol Kinds Allowed in Different Objects

Object Symbol Kind

Type circuit Instance-unique (IU)
Project-unique (PU)
Circuit Instance-unique (IU)
Project-unique (PU)
Location-unique (LU)
Node structure Project-unique (PU)

• Type
Change the symbol (data) type from the drop-down list box of this group box. You can
also edit in the text box part and change it to any other type listed in the list box part.
If you selected A (String) type, edit the length in the Size text box.
Maximum length of a string is 80 characters.

• Default Value
Type here an appropriate new value, a symbolic expression, or formula, or leave it empty.
A default value is optional for instance-unique (IU) symbols and mandatory for location-
unique (LU) and project-unique (PU) symbols. See also Section 4.4.8.5, Use of Symbols.
The Browse Button in only available if PPA (Process Portal A) is installed. It can be used
if CBA Interface is installed and the current FCB is started out of the Engineering Studio
Workplace. For further information see Control Builder A Interface Manual.

• Apply
Activate this button to edit more than one symbol.
A similar action as that of the OK button but you remain in the Edit Symbol dialog.
The Function Chart Builder assigns the default value if it is valid for the data type as set in
Type.
If you assign a new symbol—or a symbolic expression or formula containing a new symbol—
in Default Value, the Function Chart Builder opens the Create Symbol dialog for the new
symbol.
The Function Chart Builder updates the symbol list in the Symbol Section windows.

3BDS 100 595R401 4-327

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.5.15 Edit | Symbol Values…

Shortcut: ENTER
Use this command to modify or inspect the symbol values of an instantiated type circuit or
located circuit that is selected in the active PC Section window or DB Section window.
The Function Chart Builder opens the sizable Edit Symbol Values dialog box.

Figure 4-203. Edit Symbol Values

• Type Circuit or Circuit

This static text shows the name of the element, which is currently selected in the active
PC Section window or DB Section window.

• Symbol Kind
The Function Chart Builder indicates kind of the symbol by the selected option.
If this group box does not appear, the Edit Symbol Values dialog box contains variant or
loop (VL) symbols, that is, the instance-unique (IU) symbols of an advanced type circuit,
which are used in variants (IFs) and loops.

• Symbol Name
This text box repeats the name of the selected symbol in the list box below.

• Type
This text box repeats the type of the selected symbol in the list box below.

4-328 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

• Value
You can modify here the value of the symbol if symbol kind is instance-unique (IU) and
project-unique (PU) and if the Symbol Substituted check box is cleared.
For non-calculated symbols
(B - Boolean, I - integer, IL - long integer, R - real, T - time, TR - time as real, A* - string)
the value can be one of the following:
– Constant
– Symbol
– Symbolic expression with concatenated constants and symbols,
for example, CHANNEL<%CH_NR%>, where <%CH_NR%> references the
symbol CH_NR of the selected type circuit instance or located circuit,
or MODULE<MOD_NR>, where <MOD_NR> references the symbol MOD_NR of
the circuit you are working on and not that of the selected type circuit instance.
For calculated symbols
(CB - calculated Boolean, CI - calculated integer, CIL - calculated long integer, and
CR - calculated real) the value can be one of the following:
– Constant
– Symbol
– Symbolic formula with arithmetical, logical, and relational operators, constants, and
symbols, for example, <%CH_NR%> + 2, where <%CH_NR%> references the
symbol CH_NR of the selected type circuit instance or located circuit,
or 10.0 * <M_PER_IN>, where <M_PER_IN> references the symbol M_PER_IN of
the circuit you are working on and not that of the selected type circuit instance.
See also Section 4.4.8.5, Use of Symbols and Section 4.4.8.7, Values of Symbols.

• Remember Recent Values

This check box is available only at instantiation of type circuits and location of circuits.
Select this check box if you want to remember the symbol values for the given TC/CI
callname. Then, at the next instantiation/location of the TC/CI with the corresponding
TC/CI callname, the dialog presents these values as defaults.

• Symbol Substituted
For non-calculated symbols
(B - Boolean, I - integer, IL - long integer, R - real, T - time, TR - time as real, A* - string)
– Select it to show result as value.
– Clear it to show symbolic expression as value.
For calculated symbols
(CB - calculated Boolean, CI - calculated integer, CIL - calculated long integer, and CR -
calculated real)
– Select it to show result as value.
– Clear it to show formula as value.

3BDS 100 595R401 4-329

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• List Box
All symbols of the selected type circuit or circuit are listed in the list box with their names,
types, and values.

• Update default TC/CI connections and DB references created by TC/CI

This check box is available only at edition of instantiated type circuits and located circuits.
Select this check box if you want to recalculate the default connections of TC/CI terminals
and DB references of the selected type circuit instance on the basis of new symbol values.
Unselect this check box if you want to keep the default connections of TC/CI terminals
and DB references as set at the instantiation of the selected type circuit (at the location of
the circuit).
Example
You are working on a node and you have instantiated a type circuit containing symbol
<ASYMB> and TC/CI terminal INP1. The latter has a default connection consisting of the
symbolic expression INP1 = <ASYMB>_INP1.
<ASYMB> had the value “FIRE” at the instantiation. Then the Function Chart Builder
connected the INP1 terminal to FIRE_INP1. After instantiation you modify the symbol
values of the type circuit instance: you change the value of <ASYMB> to “WATER”.
If Update default TC/CI connections and DB references created by TC/CI is checked,
the Function Chart Builder connects INP1 to WATER_INP1.
If Update default TC/CI connections and DB references created by TC/CI is not
checked, INP1 remains connected to FIRE_INP1.

• Default Values
Activate this button to reset all symbols to their original default values.
If you change some values and activate the OK button, the Function Chart Builder executes the
symbol value modification by the following steps:
1. Deletes the type circuit instance (located circuit) with its old symbol values.
2. Creates the same type circuit instance (located circuit) with new symbol values.
3. Tries to reconnect all the original connections of the type circuit instance (located circuit).
If conflicts occur, for example, at reconnecting the terminals, the Function Chart Builder opens
the Output window (or iconizes it as set by Options | Preferences), and lists messages about
the conflicts.
To undo symbol value changes, choose the Edit | Undo Symbol Values command.
The Function Chart Builder updates the actual value of the symbols in the list box and in the
internal representation.
If you are working with an AC 100 Series application on-line, you can only inspect symbol
values.

4-330 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

4.5.5.16 Edit | TC/CI Terminal…

Use this command to modify a type circuit terminal or circuit terminal in the active TC/CI
Terminal Section window.

Figure 4-204. Edit TC/CI Terminal

• Name
The text box part shows the name of the selected terminal.
The list box part contains the terminals as displayed in the Name, No., Kind, Type,
Default Connection list box of the active TC/CI Terminal Section window.

NOTE
The name and kind filters in the Name, No., Kind, Type, Default Connection
list box of the active TC/CI Terminal Section window are taken into account.

Select the terminal to be edited in the list box part.

• Number
The text box part shows the terminal number.
Open the list box part to see the numbers that are assigned to existing terminals.
You can edit the terminal number in the text box part and change it to any free number in
the range 1 - 999.

• Kind
Change terminal kind by the corresponding option here.
Terminal kind must be the same as the kind of the PC terminal, to which it is connected
within the type circuit or circuit.
Select Out if both input and output PC terminals are connected.

3BDS 100 595R401 4-331

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Type
Change terminal data type from the drop-down list box.
Terminal data type must be compatible with the data type of the corresponding PC
terminal.
For A (String) type, change the length in the Size text box.
Maximum length of an array is 80 characters.
You can define size also for groups of other types, for example, B (Boolean) or I (integer).
You can define type or size also by a symbol.

• Default Connection
Type here a new connection or a symbolic expression, leave empty or unchanged.
See also Section 4.4.8.5, Use of Symbols.
A default connection is optional.

• Function Parameter Limits

In case of functional parameter kind (FP) change the allowed minimum and maximum
values in the Min and Max text boxes of this group box.

• Apply
Activate this button to edit more than one terminal.
A similar action as that of the OK button but the Edit TC/CI Terminal dialog box
remains open, and the Function Chart Builder increases the suggested terminal number in
the Number text box.

• Attributes
Activate this button to open the Edit TC/CI Terminal Attributes dialog box and change
terminal attributes.
See Section 4.5.5.3, Edit | Create… - for TC/CI Terminal Section for the
Edit TC/CI Terminal Attributes dialog box.
The Function Chart Builder assigns the default connection if the connection rules are fulfilled.
If you assign a new symbol or a symbolic expression containing a new symbol in Default
Connection, the Function Chart Builder opens the Create a Symbol dialog.
For dialog see Section 4.5.5.3, Edit | Create… - for Symbol Section.
The Function Chart Builder updates the terminal list in the TC/CI Terminal Section windows.

4.5.5.17 Edit | Upload…

Use this command to upload parameter values of several DB elements from an on-line
connected AC 100 Series target to the Function Chart Builder and substitute them as new initial
values in the Function Chart Builder.

4-332 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.5 Edit Menu

You can apply this command for uploadable DB elements, such as PARDAT and the extended
DB elements.
This command is available if all the following conditions are met:
• You are working on an AC 100 Series target.
• The target is connected (by the Target | Connect command).
• On-line mode is selected (by the File | On-line Mode command).
• The DB Section window has the focus.

Figure 4-205. Upload

• Filter/Item Des.
Select one of the filters in the list box part or edit it directly in the text box part to show
only DB elements with a certain instance name in the Item Des., Instance Name,
Callname, Init Value list box.
Open the list box part to see the valid filters and select one.
Wildcards hash mark ‘#’ and asterisk ‘*’ are also allowed.

• Item Designation
The item designations of the selected DB elements are shown in this text box.
You can also edit item designations here to select DB elements.
Separate the item designations by SPACE.

• Filter/Instance Name
Select a filter in the list box part or edit it directly in the text box part to show only DB
elements with a certain instance name in the Item Des., Instance Name, Callname,
Init Value list box. Wildcards ‘#’ and ‘*’ are also allowed.

3BDS 100 595R401 4-333

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Close the new filter condition with ENTER to make it effective.

The list box part contains the recently used filters.

• Instance Name
The instance names of selected DB elements are shown in this text box.
You can also edit the names here to select the corresponding DB elements.
Separate the names by SPACE.

• Item Des., Instance Name, Callname, Init Value

This list box contains the DB elements by item designation, instance name, callname, and
initial value corresponding to the filters in the Filter/Instance and Filter/Name text
boxes. The selected DB element instances are shown by reverse video bars.
You can select here one ore more DB element instances.
For multiple selection see Section 4.4.1.2, How to Use the Mouse and Section 4.4.1.3,
Using the Keyboard Instead of the Mouse.
The uploaded initial values are shown dimmed if they are not stored yet.

• Select All
Activate this button to select all DB element instance in the Item Des., Instance Name,
Callname, Init Value list box.

• Upload
Activate this button to upload the initial values to the Item Des., Instance Name,
Callname, Init Value list box from the on-line connected target for all uploadable DB
element instances.

• Store
Activate this button to store the uploaded values of the VALUE terminals as values of the
INIT_VAL terminals for the DB element instances selected in the Item Des., Instance
Name, Callname, Init Value list box.

• Close
Activate this button to close the Upload dialog box.
If you activate Upload, the Function Chart Builder transfers the parameter values (values of
VALUE terminal) from the on-line connected target to the Init Value column.
If you activate Store, the Function Chart Builder stores the uploaded values in the
corresponding DB element instances as initial values (values of INIT_VAL terminals) for the
DB element instances selected in the Item Des., Instance Name, Callname, Init Value list
box. (You can check it by Edit | DB Terminal Values.)
You save the new values on the INIT_VAL terminals of the corresponding DB element
instances in the internal data representation of the node only by the next File | Save or
File | Exit (with save) command.

4-334 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.6 View Menu

4.5.5.18 Edit | Document Texts…

Use this command to specify the text fields of the footer.
The footer appears at the bottom of each page of your documents, such as diagrams, data base
listings.
If you are working on a node, you can define the texts in the footer differently for the documents
of each PC program and of the DB section.
If you are working on a node structure, circuit, or type circuit, you can define the texts only
once, and they are valid for all the documents of the object.
The Function Chart Builder displays a dialog box with the template of the footer.

Figure 4-206. Edit Document Texts

Use the scroll box or resize the dialog box to see the other parts of the template.
Use TAB and SHIFT+TAB to move the cursor to the text fields of the template and edit the text you
wish to appear in the footer of your documents.

4.5.6 View Menu

4.5.6.1 View | Function Chart
If a PC Section window is active, use this command to select the function chart view for its
pane having the focus.
A check mark ‘ ’ next to the menu item shows the view selected for the active pane.
If you have open PC Section windows not having the focus, use this command to bring the
focus to the recently selected PC Section window having a pane with function chart.
If there is no such open PC Section window, the Function Chart Builder brings the focus to the
recently selected open PC Section window and selects the function chart view for its recently
selected pane.
For on-line editing in AC 100 Series targets see Section 4.4.8.2, On-line Editing Rules.

3BDS 100 595R401 4-335

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.6.2 View | Tree - All Elements

Alternative to the View | Tree - Structure Elements and View | Tree - Top of Page Elements
commands.
If a PC Section window is active, use this command to select the tree view for its pane having
the focus and display all the PC elements on all levels in this pane.
A check mark ‘ ’ next to the menu item shows the view selected for the active pane.
If you have open PC Section windows not having the focus, use this command to bring the
focus to the recently selected PC Section window that has a pane with tree diagram showing all
the PC elements on all levels.
If there is no such open PC Section window, the Function Chart Builder brings the focus to the
recently selected open PC Section window, preferably to one having a pane with some tree
view, and selects the tree - all elements view for its recently selected pane, preferably for one
with some tree view.
For on-line editing in AC 100 Series targets see Section 4.4.8.2, On-line Editing Rules.

4.5.6.3 View | Tree - Structure Elements

Alternative to the View | Tree - All Elements and View | Tree - Top of Page Elements
commands.
If a PC Section window is active, use this command to select the tree view for its pane having
the focus, compress it moderately, and display only the structure elements in this pane.
A check mark ‘ ’ next to the menu item shows the view selected for the active pane.
If you have open PC Section windows not having the focus, use this command to bring the
focus to the recently selected PC Section window that has a pane with tree diagram showing
only the structure elements.
If there is no such open PC Section window, the Function Chart Builder brings the focus to the
recently selected open PC Section window, preferably to one having a pane with some tree
view, and selects the tree - structure elements view for its recently selected pane, preferably for
one with some tree view.
For on-line editing in AC 100 Series targets see Section 4.4.8.2, On-line Editing Rules.

4.5.6.4 View | Tree - Top of Page Elements

Alternative to the View | Tree - All Elements and View | Tree - Structure Elements
commands.
If a PC Section window is active, use this command to select the tree view for its pane having
the focus, compress it, and display only the PC elements with page division in this pane.
A check mark ‘ ’ next to the menu item shows the view selected for the active pane.
If you have open PC Section windows not having the focus, use this command to bring the
focus to the recently selected PC Section window that has a pane with tree diagram showing
only the PC elements with page division.
If there is no such open PC Section window, the Function Chart Builder brings the focus to the
recently selected open PC Section window, preferably to one having a pane with some tree

4-336 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.6 View Menu

view, and selects the tree - top of page elements view for its recently selected pane, preferably
for one with some tree view.
For on-line editing in AC 100 Series targets see Section 4.4.8.2, On-line Editing Rules.

4.5.6.5 View | PC Pane | Next

Shortcut: F6
Use this command to select the next pane of the active PC Section window.

4.5.6.6 View | PC Pane | Previous

Shortcut: SHIFT+F6
Use this command to select the previous pane of the active PC Section window.

4.5.6.7 View | PC Pane | Split Horizontally

Use this command to bring the focus to the horizontal split bar between the panes in the active
PC Section window.
Move the split bar by pressing the UP or DOWN keys.

4.5.6.8 View | PC Pane | Split Vertically

Use this command to bring the focus to the vertical split bar between the panes in the active PC
Section window.
Move the split bar by pressing the LEFT or RIGHT keys.

4.5.6.9 View | Zoom…

Use this command to set the zoom factor for the active PC Section window pane.

Figure 4-207. Zoom Function Chart or Tree Diagram

• Percentage
The text box part of this drop-down combo box shows the zoom factor.
Edit any value here between 20% and 400%.
Or select any of the preset value in the list box part.
The zoom factor is valid for the presentation of diagrams on the screen.

4.5.6.10 View | Prepared Variables

Toggle switch. Available only for AC 100 Series nodes.

3BDS 100 595R401 4-337

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Use this command to show the prepared force values and the display markings ‘*’ (and values)
in the active PC Section window pane with function chart.
Repeat the command to make the prepared force values and the display markings (and values)
disappear.

NOTE
The prepared force values and the display markings (and values) may cover and
hide essential parts of the function chart (names, item designations, inversion
symbols, and so on).

A check mark ‘ ’ appears next to the menu item when the prepared force values and the
display markings (and values) are displayed.

4.5.6.11 View | Item Designations

Alternative to View | Phys. Addresses.
Use this command to identify the connections to DB terminals by item designation in the active
PC Section window pane with function chart (and also in the printed function chart diagram).
Available only for AC 400 Series and AC 100 Series objects.
A check mark ‘ ’ appears next to the menu item if you selected it recently.

4.5.6.12 View | Phys. Addresses

Alternative to View | Item Designations.
Use this command to identify the connections to DB terminals by physical address, that is, by
bus, station, and position numbers, in the active PC Section window pane with function chart
(and also in the printed function chart diagram).
Available only for AC 400 Series and AC 100 Series objects.
A check mark ‘ ’ appears next to the menu item if you selected it recently.

4.5.6.13 View | PARDAT Unit and Init Value

Toggle switch. Available only for node types supporting DB elements PARDAT with terminal
UNIT.
The terminal UNIT is supported by the DB elements:
• PARDAT(I),
• PARDAT(IL),
• PARDAT(R).
The target type which supports the UNIT terminal are
• AC 110 in versions >= 2.3
• AC 160 in versions >= 2.1.

4-338 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.6 View Menu

AC 55, AC 70, AC 410 and AC 450 do not support the terminal UNIT.
Use this command to show the value of the terminals INIT_VAL and UNIT of DB element
PARDAT which is connected to a PC element at the connection in the active PC Section
window pane with function chart (and also in the printed function chart diagram).
A check mark ‘ ’ appears next to the menu item if you selected it recently.

4.5.6.14 View | Cross Reference

Use this command to list cross references in the Output window.

Figure 4-208. View Cross Reference

Select the check boxes to include the corresponding parts to be shown in the Output window.
The Function Chart Builder opens further dialog boxes to set specific listing options depending
on the selected check boxes.
Most check boxes are offered only if the corresponding sections have been created or if the
current element libraries of the node type contain the corresponding DB elements.
Select the PC Cross Reference check box to include the list of cross references in PC
program(s) into the list to be shown. The listing includes the page numbers from the PC Section
separated by ’-’.

3BDS 100 595R401 4-339

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder opens the PC Cross Reference dialog box.

Figure 4-209. PC Cross Reference

• PC Program(s)
Select PC programs in this list box to include their PC references in the cross reference list.
• All PC Programs
Select this check box to include PC references of all PC programs.

• Item Designation/From and To

Select these check boxes to limit the listing of DB references to an item designation range
of DB elements. Open the list box parts of the adjacent combo boxes to see earlier “From”
and “To” values. Select a filter in the list box part of the adjacent combo box or edit
directly in the text box part.

Select the DB Cross Reference check box to include the list of cross references in PC
program(s) into the list to be shown. The listing includes the page numbers from the PC Section
separated by ’-’.

4-340 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.6 View Menu

The Function Chart Builder opens the Print DB Cross Reference dialog box

Figure 4-210. DB Cross Reference

• Filter/Callname and Name

Select these check boxes to limit the listing of DB references to DB elements with
callnames and/or instance names corresponding to the filters. Open the list box parts of the
adjacent combo boxes to see earlier filters and select one. Or edit directly in the text box
part. Wildcards ‘*’ and ‘?’ are also allowed.

• Item Designation/From and To

Select these check boxes to limit the listing of DB references to an item designation range
of DB elements. Open the list box parts of the adjacent combo boxes to see earlier “From”
and “To” values. Select a filter in the list box part of the adjacent combo box or edit
directly in the text box part.

4.5.6.15 View | Cross Ref. of sel. DB Elem

Available if DB Section is the active window.
Use this command to list cross references of the selected DB Element in the Output
window.

4.5.6.16 View | Cross Ref. of sel. PC Elem

Available if PC Section is the active window.
Use this command to list cross references of the selected PC Element in the Output
window.

3BDS 100 595R401 4-341

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.6.17 View | Sort by Name

Use this command to list all DB elements sorted by instance name in the active DB Section
window as an alternative to View | Sort by Item Designation.
Or use it to list all TC/CI terminals of the type circuit or circuit sorted by terminal name in the
active TC/CI Terminal Section window as an alternative to View | Sort by Number.
A check mark ‘ ’ appears next to the menu item if you selected it recently.

4.5.6.18 View | Sort by Number

Alternative to View | Sort by Name.
Use this command to list all TC/CI terminals of the type circuit or circuit sorted by terminal
number in the active TC/CI Terminal Section window.
A check mark ‘ ’ appears next to the menu item if you selected it recently.

4.5.6.19 View | Sort by Item Designation

Alternative to View | Sort by Name.
Use this command to list all DB elements sorted by item designation in the active DB Section
window.
A check mark ‘ ’ appears next to the menu item if you selected it recently.

4.5.6.20 View | Hide System DB Elements

Toggle switch. Available only for AC 400 Series nodes.
If a DB Section window is active, use this command to hide all System DB Elements.
A check mark ‘ ’ appears next to the menu item if you selected it recently.

4.5.6.21 View | Toolbar

Toggle switch.
Use this command to display and hide the Toolbar, which includes buttons for some of the most
common commands in the Function Chart Builder.
A check mark ‘ ’ appears next to the menu item when the Toolbar is displayed.

4.5.6.22 View | Status Bar

Toggle switch.
Use this command to display and hide the Status Bar, which describes the action to be executed
by the selected menu item or toolbar button, and keyboard latch state.
A check mark ‘ ’ appears next to the menu item when the Status Bar is displayed.

4-342 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.7 Options Menu

4.5.7 Options Menu

4.5.7.1 Options | Preferences…

Use this command to customize the behavior of the Function Chart Builder.
Set your preferences in the following dialog box:

Figure 4-211. Preferences

• Update Function Chart on Apply

Select this check box to update the PC diagram during repeated creation of PC elements or
repeated connection by the Apply button in the Create Element, Connect,

3BDS 100 595R401 4-343

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Create/Edit Name, Create/Edit Unit, Create/Edit Force Value, and Create/Edit Table
Entry dialog boxes.
Clear this check box to update the PC diagram only at leaving these dialog boxes.

• Minimize Output While Working

Select this check box to minimize (iconize) the Output window during execution of
commands, which fill the Output window, like File | Generate Source,
File | Backtranslate Source.
If the Output window is iconized, the engineering station executes such commands faster.
After execution of the command the Function Chart Builder restores the Output window.
Clear this check box to keep the Output window open during code generation,
backtranslation, and so on.

• Save and Restore Recent Selection

Select this check box to save the following items at the end of the current Function Chart
Builder session or at the closure of a window:
– Selected elements in the PC Section, DB Section, Symbol Section,
TC/CI Terminal Section, Name Table, and Test Table windows
– Marked PC terminal.
The Function Chart Builder restores the saved selection at the start of the next session or at
the opening of the window.
Clear this check box to skip saving and restoring the recent selection.

• Prompt Before Saving ODB

Select this check box if you want to be prompted each time you have not saved
modifications in the internal data representation and you do any of the following:
– Generate target code
– Backtranslate source code without initialization
– Check PC source
– Change from off-line mode to on-line mode.

• Generate Source Code on Exit

Select this check box to be alerted for source code generation each time when you exit the
Function Chart Builder and there are changes in the application which you want to save.
Depending on the object you are working on when exiting, the Function Chart Builder
starts one of the following commands:
– File | Generate Source - for Node
– File | Generate Source - for NS
– File | Generate Source - for CI
– File | Generate Source - for TC.

• Query Overwrite Source Code

Select this check box to make the Function Chart Builder display the following query box
if you repeatedly generate source code:

4-344 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.7 Options Menu

Overwrite existing ... source file "nnnn"?

Clear the check box to allow the Function Chart Builder to overwrite existing source code
files without warning and query.

• Create Source Code BAK Files

Select this check box to make the Function Chart Builder backup old source code files
with the extension BAK if you repeatedly generate source code. So you preserve the
previous state of your source files for later recovery.
Clear the check box to suppress source code file backup.

• Allow Confirmation by Mouse for Target Control

Select this check box to allow confirmation by mouse for target control.

DANGER
Allow mouse shortcuts for actions directly changing the state of the on-line
connected target system only if you use a mouse or trackball fulfilling the
requirements stated in the Application Builder User’s Guide.
Else you risk malfunction of the target system.

See also Section 4.4.1.2, How to Use the Mouse, Mouse Usage in On-line Mode.

• Quick Connect by Right Mouse Button

Select this check box to preserve the classical quick connect mode when clicking with the
right mouse button on a terminal in the PC Section window.
Unselect this check box to open always a context menu no matter where you click with the
right mouse button in the PC Section window.

NOTE
Even if you unselect this check box, you have a quick way to connect PC
terminals: double-click with the right mouse button.

See also Section 4.4.1.2, How to Use the Mouse, General Mouse Shortcuts and Special
Mouse Shortcuts.

• Show Implicitly Created Communication DB Elements

Extended DB elements implicitly create DB elements necessary for the communication,
such as DSP, DAT, EVS(S), and MDAT.
DB elements for S800 Series I/O and coupler modules implicitly create DSP and DAT
elements.
Select this check box to allow the presentation of implicitly created DB elements in the
Item Designation, Instance Name, Attr., Callname, Address list box of the DB Section
window.
Unselect this check box to suppress the presentation of implicitly created DB elements in
the DB Section window.

• Support Virtual Connections

Select this check box to allow virtual connections.
It is always checked if you are working on a node structure, circuit, or type circuit.

3BDS 100 595R401 4-345

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Keep PC Connections of Deleted DB Elements as Virtual Connections

Select this check box to keep PC connections to DB elements as virtual connections if you
delete the DB elements. It can be checked only if Support Virtual Connections is
checked. This allows exchange of DB elements without losing connections.

• Keep PC Connections of Deleted PC Elements as Virtual Connections

Select this check box to keep PC connections to PC elements as virtual connections if you
delete the PC elements. It can be checked only if Support Virtual Connections is
checked. . This allows exchange of PC elements without losing connections.

• Substitute Symbols in Default Connections of TC/CI Terminals

Select this check box to substitute symbols by their actual values in default connections of
TC/CI terminals. This is always the case if you are working on a node or a type circuit.
Unselect this check box to keep symbols in default connections of TC/CI terminals.
You can do this if you are working on a node structure or a circuit.
In this case, for example, you can change the values connected to the terminals of type
circuit instances also after their instantiation.

• Separator for Automatically Created DATs

Set any of the separators in the drop-down list box as separator in the instance name of
DATs that have been automatically created by DB elements like DSP and MVB.
Examples
DAT1 DSP1.B1
DAT2 MVB1.I1
or
DAT1 DSP1_B1
DAT2 MVB1_I1

• Warning Level on Create TC, Expand CI, Expand Node Structure

The warning levels in that group effect the following functions in case of type circuits or
circuits modifying DB elements:
– Create Type Circuit
– Expand Circuit
– Expand Node Structure
Select suitable warning levels from the drop-down combo boxes:
– Error
default, behaviour as in Function Chart Builder < 6.0/0
– Warning
instantiate TC or CI with warning.
– None
instantiate TC or CI without warning

4-346 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.7 Options Menu

Type circuit and circuit source code supports the following syntax to modify DB elements:

modifyDbLine ::= MODIFY dbIdentity eol

dbIdentity ::= dbItemDes | ( dbName(20) [dbCallNameAll(8)] )
Remark: for DS, DSP, and DAT elements only dbName(12)
dbItemDes ::= dbItemDesSup | dbItemDesSub
dbCallNameAll ::= AAB_FILE | AI | AIPT | AIPTS | AIS | ...
Remark: superior, independent, and subordinate call names depending on
the DB element library

Figure 4-212. Extract of TC with including MODIFY keyword

The DB item designation or DB name is sufficient to identify the DB element to be

modified in the node.
The DB callname is optional. However, if DB callname is given, and does not match the
callname of the DB element in the node, Function Chart Builder issues semantic error
"Invalid Item Designation" on type circuit instanciation, circuit, or node structure
expansion.
E.g. consider a type circuit with the line
MODIFY AI1.1 AIS610 : NAME MyDBElement
to be instanciated in node with DB element AI1.1 AIS620.
– If you select "MODIFY DB Callname Mismatch" warning level "Error", the type
circuit is not instanciated and you get a semantic error.
– If you select "MODIFY DB Callname Mismatch" warning level "Warning", the type
circuit is instanciated modifiying AI1.1, and you get a warning.
– If you select "MODIFY DB Callname Mismatch" warning level "None", the type
circuit is instanciated modifiying AI1.1 without warning.
You can select similar warning level for the case of non-matching item designations of AI
/ AIS / AO / AOS / DI / DIS / DO / DOS DB elements. S800 I/O DB elements use the item
designation pattern AI800_#, AI800_#.# ... DO800_#, DO800_#.#, while other I/O DB
elements use the pattern AI#, AI#.# ... DO#, DO#.#.
E.g. consider a type circuit with the line
MODIFY AI1.1 AIS610 : NAME MyDBElement
to be instanciated in node with DB element AI800_1.1 AIS820.
AI1.1 does not exist in that node.
– If you select "MODIFY DB Item Designation Mismatch" warning level "Error", the
type circuit is not instanciated and you get a semantic error "Invalid Item
Designation".
– If you select "MODIFY DB Item Designation Mismatch" warning level "Warning",
the type circuit is instanciated modifiying AI800_1.1, and you get a warning.
– If you select "MODIFY DB Item Designation Mismatch" warning level "None", the
type circuit is instanciated modifying AI800_1.1 without warning.

3BDS 100 595R401 4-347

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Delete Confirmation
Select the check boxes to make the Function Chart Builder display the following warning
message before the execution of a corresponding Edit | Delete command:
Do you really want to delete ... ?
Clear the check boxes to suppress warning messages before the execution of a
corresponding Edit | Delete commands.

• Symbol, TC/CI Terminal Creation

Select the check boxes to make the Function Chart Builder display the following warning
message if you reference an undefined symbol or TC/CI terminal:
One or more undefined symbols found in ...
Do you want to create them first?
or
Undefined TC/CI terminal ... found.
Do you want to create it?
Clear the check boxes to suppress warning messages and jump directly to the
corresponding Create … dialogs.

4.5.7.2 Options | Workspace…

Use this command to define the initial workspace for the Function Chart Builder sessions, to
save different workspaces of different scopes, and to load them.

Figure 4-213. Workspace

• Scope
Select the corresponding option to set the scope of subsequent workspace operations.

4-348 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.7 Options Menu

• Initial Workspace
The list box part of this drop-down combo box contains all the workspaces available for
the selected scope. The Last Workspace Used is always available.
Select a workspace here. The text box part shows the name of the selected workspace.
At the start of the next sessions the Function Chart Builder restores the windows,
selections, and so on, accordingly.

• Combo Box
The list box part of this combo box contains the names of the initial workspaces saved and
available for the selected scope.
Select the initial workspace in the list box part if you want to load it and make it the current
initial workspace, or if you want to delete it. The text box part shows the name of the
selected initial workspace. If you want to save the current initial workspace for the
selected scope, edit the new initial workspace name in the text box part.

• Save
Activate this button to save the current workspace with the name edited and selected in the
combo box.

• Load
Activate this button to load the workspace selected in the combo box and make it the
current workspace. The Function Chart Builder reopens the windows, sets preferences,
selects elements, and so on, accordingly.

• Delete
Activate this button to delete the workspace selected in the combo box.
The current Function Chart Builder session is not concerned.

• Close
Activate this button to close the Workspace dialog box.
The Function Chart Builder sets the workspace parameters at the start of each session depending
on the Initial Workspace recently selected with the Option | Workspace command.
You can load any workspace saved for the selected scope and make it the current workspace.
The Function Chart Builder reopens the windows, sets preferences, selects elements, and so on,
accordingly.
At the end of every session the Function Chart Builder saves the current general and object-
specific workspace parameters. It is called the Last Workspace Used.

3BDS 100 595R401 4-349

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.7.3 Options | Cycle Times…

Use this command to set the allowed cyclicities of structure elements and allowed scan times of
DB elements in the Function Chart Builder.

Figure 4-214. Cycle Times

The command is available only if you are working on an AC 400 Series or MP 200/1 object.

NOTE
In earlier releases of the Function Chart Builder the defaults of basic cycle times
were saved in the QMP200CT.DAT file. This file is not used any more, the basic
cycle times are stored in *.INI files of the objects.

• Interpreter Cycle Times

These are cycle times of interpreters A, B, and C running on the AC 400 Series or MP 200/1
nodes.
The first column contains the basic cycle times. The dimmed cells in the other columns show
the valid multiples *2, *4, and *8 of the basic cycle times.

• Slow Signal Scan Times

These are cycle times of interpreter D running on the AC 400 Series or MP 200/1 nodes.
The first column contains the basic cycle time.
The dimmed cells in the other columns show the valid multiples *2, *4, *8, *16, and *32 of the
basic cycle time.

4-350 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.7 Options Menu

• Keep PC Scan Table Position Callparameters at Source Code Generation

Select this check box to keep the positions in source code at generation. For example, the edited
or backtranslated position value “2” in CONTRM (50, 2 ,0) will be kept unchanged in the
generated source code.
Unselect this check box to replace the positions by “0” in source code at generation. For
example, a backtranslated or edited CONTRM (50, 2 ,0) becomes CONTRM (50, 0 ,0) in the
generated source code.
NOTE
Function Chart Builder does not check the correct usage of scan times and places
in the scantime table.

Setting Cycle Times

To specify the basic cycle times of interpreters A, B, C; and D running on the AC 400 Series or
MP 200/1 nodes, set the values in the first column following the rules:
1. Basic cycle times of interpreters A, B, C must be an integer multiple of 5ms and must be
unique.
2. The range of basic cycle times of interpreter A is 5ms to 50 ms.
The range of basic cycle times of interpreter B is
(4 * basic_cycle_time_of_interpreter_A) + 5ms to
(basic_cycle_time_of_interpreter_C / 4) - 5ms.
The range of basic cycle times of interpreter C is
(4 * basic_cycle_time_of_interpreter_B) + 5ms to 4000 ms.
That means, the cycle time values of the interpreters A, B, and C have to build increasing
scan time values without overlap. For example, that the lowest cycle time value of
interpreter B must be higher than the highest one of interpreter A.
3. Basic cycle times of interpreters D must be an integer multiple of 1s.
4. The range of basic cycle times of interpreter D is 1s to 6s.
The dimmed cells in the 2nd, 3rd, and 4th columns of the table show the valid multiples *2, *4,
and so on, as applicable. They are automatically updated while you edit the basic cycle times.

Usage of Cycle Times in PC Part

The allowed cyclicity for PCPGM are the values defined in the table for interpreter A.
The allowed cyclicity for the other structure elements CONTRM, FUNCM, and so on, are the
values defined in the table for interpreters A, B, and C.
If you create a structure element with an invalid cycle time, Function Chart Builder warns you.
For cyclicity, see Section 4.5.5.10, Edit | Call Parameters….

Usage of Cycle Times in DB Part

The allowed cycle times on the SCANT terminal of DB elements are the values defined in the
table for interpreters A, B, C, and D.
For cycle time (SCANT), see the Section 4.5.5.13, Edit | DB Terminal Values….

3BDS 100 595R401 4-351

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTE
If you change the basic cycle time of an interpreter, the Function Chart Builder
changes the values on SCANT terminals of existing DB elements, which use this
interpreter, proportionally to the change of the basic cycle time.

4.5.7.4 Options | Language >

Submenus:
Options | Language > English
Use this command to switch to english language. Leave the FCB with File | Exit. Be sure to
save you current application program. At next start of FCB the FCB starts in english language.
Options | Language > Deutsch
Use this command to switch to german language. Leave the FCB with File | Exit. Be sure to
save you current application program. At next start of FCB the FCB starts in german language.
A check mark ‘ ’ appears next to the menu item if you selected it recently.

4.5.8 PC-Section Menu

4.5.8.1 PC-Section | Goto Element >
Submenus:

PC-Section | Goto Element | Previous

Shortcut: UP
Use this command to select the previous PC element in the execution order within the PC
program.
The Function Chart Builder moves the object cursor to this PC element and displays the
corresponding page in the active PC Section window.
NOTE
To be able to use the shortcut, be sure the slide mode is cleared.
See Section 4.5.12.7, Window | Slide.

PC-Section | Goto Element | Next

Shortcut: DOWN
Use this command to select the next PC element in the execution order within the PC program.
The Function Chart Builder moves the object cursor to this PC element and displays the
corresponding page in the active PC Section window.

NOTE
To be able to use the shortcut, be sure the slide mode is cleared.
See Section 4.5.12.7, Window | Slide.

4-352 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.8 PC-Section Menu

PC-Section | Goto Element | Lower Level

Shortcut: CTRL+RIGHT
Use this command to select the first PC element on the level below the currently selected
element.
The Function Chart Builder moves the object cursor to this PC element and displays the
corresponding page in the active PC Section window.

NOTE
To be able to use the shortcut, be sure the slide mode is cleared.
See Section 4.5.12.7, Window | Slide.

PC-Section | Goto Element | Higher Level

Shortcut: CTRL+LEFT
Use this command to select the PC element on the level above the currently selected element.
The Function Chart Builder moves the object cursor to this PC element and displays the
corresponding page in the active PC Section window.

NOTE
To be able to use the shortcut, be sure the slide mode is cleared.
See Section 4.5.12.7, Window | Slide.

PC-Section | Goto Element | Previous on Level

Use this command to select the previous PC element on the same level as the currently selected
element.
The Function Chart Builder moves the object cursor to this PC element and displays the
corresponding page in the active PC Section window.

PC-Section | Goto Element | Next on Level

Use this command to select the next PC element on the same level as the currently selected
element.
The Function Chart Builder moves the object cursor to this PC element and displays the
corresponding page in the active PC Section window.

PC-Section | Goto Element | Top

Shortcut: HOME
Use this command to select the first PC element of the program.
The Function Chart Builder moves the object cursor to this PC element and displays the
corresponding page in the active PC Section window.

NOTE
To be able to use the shortcut, be sure the slide mode is cleared.
See Section 4.5.12.7, Window | Slide.

3BDS 100 595R401 4-353

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

PC-Section | Goto Element | Bottom

Shortcut: END
Use this command to select the last PC element of the program.
The Function Chart Builder moves the object cursor to this PC element and displays the
corresponding page in the active PC Section window.

NOTE
To be able to use the shortcut, be sure the slide mode is cleared
See Section 4.5.12.7, Window | Slide.

4.5.8.2 PC-Section | Goto Page >

Submenus:

PC-Section | Goto Page | Previous

Shortcut: PGUP
Use this command to go to the previous page of the function chart or tree diagram.
If the PC Section window pane with the function chart is active, the Function Chart Builder
displays the previous page of the function chart. The first element of the previous page is
selected.
If the PC Section window pane with the tree diagram is active, the Function Chart Builder
selects the first element of the page and scrolls the diagram one screen page up.

NOTE
To be able to use the shortcut, be sure the slide mode is cleared.
See Section 4.5.12.7, Window | Slide.

PC-Section | Goto Page | Next

Shortcut: PGDOWN
Use this command to go to the next page of the function chart or tree diagram.
If the PC Section window pane with the function chart is active, the Function Chart Builder
displays the next page of the function chart. The first element of the next page is selected.
If the PC Section window pane with the tree diagram is active, the Function Chart Builder
selects the last element of the page and scrolls the diagram one screen page down.

NOTE
To be able to use the shortcut, be sure the slide mode is cleared.
See Section 4.5.12.7, Window | Slide.

4-354 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.8 PC-Section Menu

PC-Section | Goto Page | Number…

Shortcut: CTRL+G
Use this command to switch to the specified page of the function chart.

Figure 4-215. Goto Page

• Number
Open the list box part of this drop-down combo box to see page numbers of existing pages
of the function chart.
Select a page number here to define the page, to which you want to go.
Or edit an existing page number in the text box part.
If the page exists, the Function Chart Builder sets the object cursor to its first PC element and
displays the page in the active PC Section window.

4.5.8.3 PC-Section | Select…

Use this command to select one or more PC elements (or instantiated type circuits or located
circuits), a whole subtree of PC elements or a whole PC program.
Use this command before Edit | Cut, Edit | Copy, Edit | Delete, PC-Section | Renumber, and
PC-Section | Layout | Delete Page Division.

Figure 4-216. Select PC Section

• From Item Designation

Reflects the current selection in the PC Section window.

3BDS 100 595R401 4-355

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Edit the text box part directly to define the first element of the selection.
Or open the drop-down list box part containing the selection history (the recent selected
item designations) and select the first element there.

• To
Edit the text box part directly to define the last element of the selection.
Or open the drop-down list box part containing the selection history (the recent selected
item designations) and select the last element there.

• To End of Subtree
Activate this button to fill the To text box with the last element of the subtree.

4.5.8.4 PC-Section | Execution Order >

Submenus:

PC-Section | Execution Order | Move Up

Use this command to move the selected PC element, instantiated type circuit or located circuit
one position up (forward) in the execution order.
If you move a structure element, its subordinate elements are also moved.

PC-Section | Execution Order | Move Down

Use this command to move the selected PC element, instantiated type circuit or located circuit
one position down (backward) in the execution order.
If you move a structure element, its subordinate elements are also moved.

4.5.8.5 PC-Section | Modify Item Destination…

Use this command to modify the last figure (part number) in the item designation of the selected
PC element, type circuit or circuit.
This command is available only in off-line mode.

Figure 4-217. Modify Item Designation

• Callname
Shows the callname of the selected PC element.

4-356 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.8 PC-Section Menu

• Old Item Designation

Shows the old item designation of the selected PC element.

• New Item Designation

Edit here the new item designation that has to be assigned to the selected PC element.
Change only the last number in comparison with the old item designation.
If the modification is valid, the Function Chart Builder changes the item designation and
updates the PC diagrams in the PC Section windows.

4.5.8.6 PC-Section | Renumber Lower Level

Use this command to renumber the item designation of the subordinate elements of the selected
PC element. By renumbering, you can match the subordinate elements to their new execution
order after moving or inserting PC elements (or type circuits or circuits).
This command is available only in off-line mode and if you selected only one PC element. It is
effective only on the one level immediately below the selected PC element. (If several PC
elements are selected, the PC-Section | Renumber … command is available instead.)
The new numbering of the subordinate elements begins with 1 and is increased by 1.
Ranges required by type circuit and circuit contents are observed.
The Function Chart Builder updates the PC Section windows.

4.5.8.7 PC-Section | Renumber …

Use this command to renumber the item designation of several selected PC elements.
By renumbering, you can assign a new range of item designations to these PC elements and
match them to their new execution order after moving or inserting PC elements (or type circuits
or circuits).
This command is available only in off-line mode and if you selected several PC elements.
It is effective only on this level and only for the selected PC elements. For selecting several PC
elements, see Section 4.5.8.3, PC-Section | Select…. (If only one PC element is selected, the
PC-Section | Renumber Lower Level command is available instead.)

Figure 4-218. Renumber PC Section

3BDS 100 595R401 4-357

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The new numbering of the elements begins with the number defined in the dialog and is
increased by 1 for each subsequent element. Ranges required by type circuit and circuit contents
are observed.
The Function Chart Builder updates the PC Section windows.

4.5.8.8 PC-Section | Computing Time >

Available only for Advant Controllers.

NOTE
If there are several processor modules PMnnn available for a node type and
having different performance, the simplest one is taken as basis for computing
time calculation. To get computing time for systems with the other ones,
multiply the values by a factor depending on node type and processor module.
For example, for AC 110 computing time is calculated on the basis of PM632.
To get computing time for systems with the faster PM633 and PM634,
multiply the values by 0.5.
In due case, consult the User’s Guide of the corresponding Advant Controller.

Submenus:

PC-Section | Computing Time | For Selected Element…

Use this command to show the computing time of the selected PC element.

Figure 4-219. Computing Time for Selected Element

PC-Section | Computing Time | For Selected Unit…

Use this command to show the computing time and capacity-use of one or more executable
units in the target.
If you select a structure element other than PCPGM, the Function Chart Builder calculates the
computing time and controller capacity-use only for this executable unit.
If you select a PCPGM, computing times and controller capacities are calculated for all its
subordinate executable units, too.
The Function Chart Builder has two algorithms for calculation of computing time in the target.
For AC 400 Series algorithm 1 is available.

4-358 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.8 PC-Section Menu

For AC 100 Series both algorithms are available. They are executed depending on the
completeness of the application:
1. The PC elements of the selected executable units are created. Only the PC element
execution times are taken into account. The resulting values are displayed in the
PC Elements column group. The values can be used as a first estimate and are typically
less then the real computing times and capacity loads on the target.
2. The PC elements of the selected executable units are connected, possibly also to DB
elements, and valid target code is generated. Connections, DB elements, and
implementation details, like in-line code, are also taken into account. The calculation is
based on time data given in the *.TCD file of the selected node type.
The resulting values are displayed in the DB, PC, Connections column group.
They are a very good approximation of computing times and capacity loads on the target.
They reflect the worst case.
Select the structure element of an executable unit or the PCPGM element in the PC Section
window. If you need the more precise results (algorithm 2), be sure target code is available.
(If necessary, generate target code by File | Generate Target Code.)
Then choose this command.
The Function Chart Builder presents the resulting values in the following dialog box:

Figure 4-220. Computing Time for Selected Unit

• Designation, Callname, Cycletime

Contain an executable unit selected in the PC Section window, or a PCPGM element with
its subordinate executable units and also other time-consuming activities of the target.
They are listed by item designation (or abbreviation of DB element group), callname and
cycle time.

3BDS 100 595R401 4-359

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• PC Elements - Comp.Time, Capacity

Contain the computing time necessary for the target to process the executable unit and the
quotient “computing time divided by cycle time”. These values are calculated on the basis
of pure PC element execution times. Take them as first estimate.

• DB, PC, Connections - Comp.Time, Capacity

Contain the computing time necessary for the target to process the corresponding
executable units and the quotient “computing time divided by cycle time”.
These values can be calculated only for AC 100 Series.
The values are calculated on the basis of PC element execution times, connections, DB
elements, and implementation details. Take them as a very good approximation of real
computing times and capacity load on the target. They reflect the worst case.
NOTE
This column group can be filled with values only if target code is available.
If necessary, generate target code and repeat the PC-Section | Computing Time |
For Selected Unit command. This column group can be filled with values only if
the *.TCD file with time data is available for the selected node type.

• Total
The sum of single capacities.

PC-Section | Computing Time | For Node…

Use this command to show the computing time and capacity-use of the whole node.
The Function Chart Builder calculates the computing time and controller capacity-use for all the
PCPGM elements and for all their subordinate executable units, too.
The Function Chart Builder has two algorithms for calculation of computing time in the target.
For AC 400 Series algorithm 1 is available.
For AC 100 Series both algorithms are available. They are executed depending on the
completeness of the application:
1. The PC elements of the selected executable units are created. Only the PC element
execution times are taken into account. The resulting values are displayed in the
PC Elements column group. The values can be used as a first estimate and are typically
less then the real computing times and capacity loads on the target.
2. The PC elements of the selected executable units are connected, possibly also to DB
elements, and valid target code is generated. Connections, DB elements, and
implementation details, like in-line code, are also taken into account. The calculation is
based on time data given in the *.TCD file of the selected node type. The resulting values
are displayed in the DB, PC, Connections column group. They reflect the worst case and
are a very good approximation of computing times and capacity loads on the target.
If you need the more precise results (algorithm 2), be sure target code is available.
(If necessary, generate target code by File | Generate Target Code.)
The Function Chart Builder presents the resulting values in the following dialog box:

4-360 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.8 PC-Section Menu

Figure 4-221. Computing Time for Node

• Designation, Callname, Cycletime

Contain all the PCPGM elements, their subordinate executable units, and also other time-
consuming activities of the target. They are listed by item designation (or abbreviation of
DB element group), callname and cycle time.

• PC Elements - Comp.Time, Capacity

Contain the computing time necessary for the target to process the corresponding PCPGM
elements and executable units, and the quotient “computing time divided by cycle time”.
These values are calculated on the basis of pure PC element execution times.
Take them as first estimate.

• DB, PC, Connections - Comp.Time, Capacity

Contain the computing time necessary for the target to process the corresponding PCPGM
elements and executable units, and the quotient “computing time divided by cycle time”.
These values can be calculated only for AC 100 Series.
The values are calculated on the basis of PC element execution times, connections, DB
elements, and implementation details. Take them as a very good approximation of real
computing times and capacity load on the target. They reflect the worst case.

NOTE
This column group can be filled with values only if target code is available.
If necessary, generate target code and repeat the
PC-Section | Computing Time | For Node command.
This column group can be filled with values only if the *.TCD file with time data
is available for the selected node type.

• Total
The sum of single capacities.

3BDS 100 595R401 4-361

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.8.9 PC-Section | Memory Calculation>

Available only for Advant Controllers.
Submenus:
PC-Section | Memory Calculation | For Selected Element…
Use this command to show the memory requirement of the selected PC element in the target.

Figure 4-222. Memory Calculation for Selected Element

PC-Section | Memory Calculation | For Selected Unit…

Use this command to show the memory requirement of executable units in the target.
If you select a structure element other than PCPGM, the Function Chart Builder calculates the
memory requirement only for this executable unit. If you select a PCPGM, memory
requirements are calculated for all its subordinate executable units, too.
The Function Chart Builder calculates the required memory on the basis of call parameter
values of the PC elements. The results can be used as a good approximation and are typically
more then the memory really required on the target.
Select the structure element of an executable unit or the PCPGM element in the PC Section
window. Then choose this command.
The Function Chart Builder presents the resulting values in the following dialog box:

Figure 4-223. Memory Calculation for Selected Unit

4-362 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.8 PC-Section Menu

• Designation, Callname
Contain an executable unit selected in the PC Section window, or a PCPGM element with
its subordinate executable units.
They are listed by item designation and callname.

• PC Statement, Local Data Area

Contain the memory necessary for the target to process the corresponding executable units.
These values are calculated on the basis of call parameter values of the PC elements.
Take them as a good approximation.

• % (Percent)
“Required memory divided by maximum available memory” for the local data area in %.

• Total
The sum of required memory.

PC-Section | Memory Calculation | For Node…

Use this command to show the memory requirement of the whole node.
The Function Chart Builder calculates the required memory for all the PCPGM elements and for
all their subordinate executable units, too.
The Function Chart Builder calculates the required memory on the basis of call parameter
values of the PC elements. The results can be used as a good approximation and are typically
more then the memory really required on the target.
The Function Chart Builder presents the resulting values in the following dialog box:

Figure 4-224. Memory Calculation for Node

3BDS 100 595R401 4-363

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Designation, Callname
Contain all the PCPGM elements and their subordinate executable units.
They are listed by item designation and callname.

• PC Statement, Local Data Area

Contain the memory necessary for the target to process the corresponding PCPGM
elements and executable units. These values are calculated on the basis of call parameter
values of the PC elements. Take them as a good approximation.

• % (Percent)
“Required memory divided by maximum available memory” for the local data area in %.

• Total
The sum of required memory.

4.5.8.10 PC-Section | Page Layout >

Submenus:

PC-Section | Page Layout | Insert Page Division…

Shortcut: CTRL+D
Use this command to insert a page division at the selected PC element or instantiated type
circuit or located circuit.

Figure 4-225. Insert Page Division.

• Actual Number
This static text shows the suggested number for the new page.
It is the preceding page number plus 1.

4-364 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.8 PC-Section Menu

• Page Number
Edit here the new page number. Default value is the actual number.
– To insert a page division with a soft page number, accept the wildcard hash mark ‘#’
displayed in the Page Number text box, denoting automatic page assignment.
The new page is inserted with the suggested page number.
The subsequent soft page numbers, if there are any, down to the first fixed page
number are renumbered with increments of 1.
(The auto increment value is 1 for soft page numbers.)
– To insert a page division with a fixed page number, edit a definite page number as
nnnnn or nnnnn.f (where nnnnn and f are figures) instead.
The new page is inserted with this page number.
The subsequent soft page numbers, if there are any, down to the first fixed page
number are renumbered with increments of 1.

• Headline
Edit here the text to appear in the lower right-hand corner above the footer on the new page
of the function chart. You can enter the text from the scratch, or you load the headline of
some existing page by From Page and Copy at first and change it.

• From Page
Edit here the number of the page, from which you want to copy the headline.
Or drop down the list box part to select one of the existing page numbers.
Fill the text box part only if you want to copy a headline by the Copy button before editing
it in the Headline text box.

• Copy
Activate this button to fetch the headline text from the page defined in the From Page
drop-down combo box and copy it to the Headline text box.
The Function Chart Builder inserts the new page division in the function chart as specified only
if the page division rules are not violated. Otherwise error messages are displayed.
In the tree diagram, the page division is indicated by a dash line and the first words of the
headline text behind the element.

PC-Section | Page Layout | Modify Page Division…

Shortcut: CTRL+E
Use this command to modify the page number, kind (soft or fixed), and the headline of the
selected page division.

3BDS 100 595R401 4-365

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-226. Modify Page Division

• Actual Number
This static text shows the number of the selected page before modification. This is the
page that contains the PC element currently selected in the active PC Section window.

• Page Number
Edit here the modified page number. Default value is the actual number.
– To assign a soft page number to the current page, edit the wildcard hash mark ‘#’.
The subsequent soft page numbers, if there are any, down to the first fixed page
number are renumbered with increments of 1.
(The auto increment value is 1 for soft page numbers.)
– To assign a fixed page number to the current page, edit a definite page number as
nnnnn or nnnnn.f (where nnnnn and f are figures).
The subsequent soft page numbers, if there are any, down to the first fixed page
number are renumbered with increments of 1.

• Headline
Shows the old headline text, if any, of the selected page.
Edit here the text to appear in the lower right-hand corner above the footer on the selected
page of the function chart. You can enter the text from the scratch, or you load the headline
of some existing page by From Page and Copy at first and change it.

• From Page
Edit here the number of the page, from which you want to copy the headline.
Or drop down the list box part to select one of the existing page numbers.
Fill the text box part only if you want to copy a headline by the Copy button before editing
it in the Headline text box.

4-366 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.8 PC-Section Menu

• Copy
Activate this button to fetch the headline text from the page defined in the From Page
drop-down combo box and copy it to the Headline text box.

PC-Section | Page Layout | Delete Page Division…

Shortcut: CTRL+SHIFT+D
Use this command to delete page divisions attached to one or more selected PC elements.
See Section 4.5.8.3, PC-Section | Select… for selecting several PC elements.
The page division is not deleted if it violates the page division rules.
If the resulting page does not fit the selected page layout template, the Function Chart Builder
warns you. Nevertheless, you can delete the page division. In this case, the Function Chart
Builder displays a text in the PC Section window instead of the function chart page:
There are too many elements on this page.
Insert or generate page division(s), or format the page.
First PC element on page: PCn... ABC
Last PC element on page: PCm... XYZ

PC-Section | Page Layout | Copy Headlines…

Use this command to copy the headline of the selected page division to all headlines of a
specified range of pages.

Figure 4-227. Copy Headlines

• From Page
This static text shows number of the page, the headline of which is to be copied. This is the
page that contains the PC element currently selected in the active PC Section window.

• Headline
This static text shows the headline to be copied.

3BDS 100 595R401 4-367

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• To Start Page, Stop Page

Edit here the number of the first page and last page of the range, to which the headline is to
be copied. Or drop down the list box part to select one of the existing page numbers.
Be sure the stop page does not precede the start page.
Check page order in the list box parts.

NOTE
Due to fixed page numbers pages are not necessarily in strict numerical order.
That means, the stop page number is not necessarily greater than the start page
number.

PC-Section | Page Layout | Check…

Use this command to check the layout of a range of function chart pages.

Figure 4-228. Check Page Layout

• Range Options
Select All Pages to check the layout of all the pages of the function chart.
Select Selection to check the layout of the pages, the elements of which are selected
currently. See Section 4.5.8.3, PC-Section | Select… for selecting several PC elements.
Select Pages to check the layout of a range specified by From and To.

• From, To
The text box parts of these drop-down combo boxes show the first and last page number of
the range corresponding to the selected range option.
If you have selected the Pages option, modify here the page numbers.
The list box parts contain the existing page numbers.
Be sure the “To” page does not precede the “From” page.
Check page order in the list box parts.

NOTE
Due to fixed page numbers pages are not necessarily in strict numerical order.
That is, page number “To” is not necessarily greater than page number “From”.

4-368 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.8 PC-Section Menu

The Function Chart Builder checks whether all pages of the function chart in the specified range
can be displayed and printed with the current layout.
The Function Chart Builder opens the Output window and displays either a message about the
success of the layout check or the list of pages with layout problems.

PC-Section | Page Layout | Format…

Use this command to format a range of function chart pages and generate necessary page
divisions on the basis of the page layout template and page size as set by the File | Page Setup.

Figure 4-229. Format Pages

• Range Options
Select All Pages to format all the pages of the function chart.
Select Selection to format the pages, the elements of which are selected currently.
See Section 4.5.8.3, PC-Section | Select… for selecting several PC elements.
Select Pages to format pages in a range specified by From and To.

• From, To
The text box parts of these drop-down combo boxes show the first and last page number of
the range corresponding to the selected range option.
If you have selected the Pages option, modify here the page numbers.
The list box parts contain the existing page numbers.
Be sure the “To” page does not precede the “From” page.
Check page order in the list box parts.

NOTE
Due to fixed page numbers pages are not necessarily in strict numerical order.
That means, the “To” page number is not necessarily greater than the “From”
page number.

• Delete Obsolete Soft Pages

Select this check box to delete obsolete page divisions with soft page numbers.

3BDS 100 595R401 4-369

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder processes the specified range of pages in the following way:
1. Creates page divisions and assigns soft page numbers where necessary.
2. Copies headlines for the new pages from the preceding pages.
3. If specified so, deletes obsolete (unnecessary) page divisions with soft page numbers.
The Function Chart Builder opens the Output window and displays either a message about the
success of formatting or the list of pages with remaining layout problems.

PC-Section | Page Layout | Generate Page Division…

Use this command to reformat a range of function chart pages and generate page divisions anew
on the basis of the page layout template and page size as set by the File | Page Setup command.

Figure 4-230. Generate Page Division

• Range Options
Select All Pages to reformat all the pages of the function chart.
Select Selection to reformat the pages, the elements of which are selected currently.
See Section 4.5.8.3, PC-Section | Select… for selecting several PC elements.
Select Pages to reformat pages in a range specified by From and To.

• From, To
The text box parts of these drop-down combo boxes show the first and last page number of
the range corresponding to the selected range option.
If you have selected the Pages option, modify here the page numbers.
The list box parts contain the existing page numbers.
Be sure the “To” page does not precede the “From” page.
Check page order in the list box parts.

NOTE
Due to fixed page numbers pages are not necessarily in strict numerical order.
That means, the “To” page number is not necessarily greater than the “From”
page number.

4-370 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.8 PC-Section Menu

• Delete Headlines
Select this check box if you want to ignore and delete the old headlines.
Clear this check box if you want to preserve the old headlines.
The Function Chart Builder processes the specified range of pages in the following way:
1. Associates old headlines temporarily with the PC elements on the top of the pages.
2. Deletes the existing page divisions.
3. Applies the page division rules.
4. Creates page divisions and assigns soft page numbers where necessary.
5. If specified so, regenerates headlines on the basis of Step 1.
The Function Chart Builder opens the Output window and displays either a message about the
success of the page division generation or the list of pages with layout problems.

PC-Section | Page Layout | Modify Page Numbers…

Use this command to modify page numbers and page divisions.

Figure 4-231. Modify Page Numbers

• Renumber Pages
Use this option to renumber the pages within the specified range.
“From” and “To” have to be fixed page numbers.
The new range starts at “First Page” and uses the page increment “Step”.
The new range will be converted to fixed page numbers.
If any of the new fixed page numbers collides with an existing fixed page number,
the function will be rejected.

• Shift Page Numbers

Use this option to shift the page numbers belonging to the specified range by the value of
Step. “From” and “To” have to be fixed page numbers.

3BDS 100 595R401 4-371

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The new range will be converted to fixed page numbers.

If any of the new fixed page numbers collides with an existing fixed page number,
the function will be rejected.

• Convert to Soft
Use this option to convert fixed page numbers to soft page numbers within a range.
Remember, a soft page number is not a final definite number, just a relative position,
it is inserted using the wildcard ‘#’.

• Convert to Fix
Use this option to convert soft page numbers to fixed page numbers within a range.
Remember, a fixed page number is a final definite number, not a relative position.

• Range Options
Select All Pages to process all the pages of the function chart.
Select Selection to process the pages, the elements of which are selected currently.
See Section 4.5.8.3, PC-Section | Select… for selecting several PC elements.
Select Pages to process pages in a range specified by From and To.

• From, To
The text box parts of these drop-down combo boxes show the first and last page number of
the range corresponding to the selected range option.
If you have selected the Pages option, modify here the page numbers.
The list box parts contain the existing page numbers.
Be sure the “To” page does not precede the “From” page.
Check page order in the list box parts.

NOTE
Due to fixed page numbers pages are not necessarily in strict numerical order.
That means, the “To” page number is not necessarily greater than the “From”
page number.

• First Page
Edit here the number that the first page of the range obtains after the modification.

• Step
If Renumber Pages is selected, edit here the value, by which the numbers of consecutive
pages of the range have to differ.
If Shift Page Numbers is selected, edit here the value, by which the page numbers of the
range have to be shifted.
The offset can be positive or negative.

4-372 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.9 PC-Terminal Menu

4.5.9 PC-Terminal Menu

4.5.9.1 PC-Terminal | Goto >

Submenus:

PC-Terminal | Goto | Previous

Shortcut: LEFT
Use this command to select the previous terminal of the selected PC element.

NOTE
To be able to use the shortcut, be sure the slide mode is cleared.
See Section 4.5.12.7, Window | Slide.

PC-Terminal | Goto | Next

Shortcut: RIGHT
Use this command to select the next terminal of the selected PC element.

NOTE
To be able to use the shortcut, be sure the slide mode is cleared.
See Section 4.5.12.7, Window | Slide.

PC-Terminal | Goto | First

Use this command to select the first terminal of the selected PC element.

PC-Terminal | Goto | Last

Use this command to select the last terminal of the selected PC element.

PC-Terminal | Goto | Sink…

Shortcut: CTRL+R
If a source PC terminal is selected, use this command to go to a corresponding sink PC terminal
and select it.

Figure 4-232. Goto Terminal

3BDS 100 595R401 4-373

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Terminal
The text box part reflects the selection in the list box below.
Edit here the name of the sink terminal, to which you want to go.
The list box part shows all available sink terminals of the source, which is selected in the
active PC Section window.
If a sink PC terminal is selected, see PC-Terminal | Goto | Source to select its source.

PC-Terminal | Goto | Source

Shortcut: CTRL+R
If a sink PC terminal is selected, use this command to go to the corresponding source PC
terminal and select it.
If a source PC terminal is selected, see PC-Terminal | Goto | Sink to select corresponding
sinks.

4.5.9.2 PC-Terminal | Mark

Shortcut: KEYPAD 5
Use this command to mark the terminal indicated by the cursor. That means you prepare this
terminal for connection to other PC terminals.
See Section 4.5.9.5, PC-Terminal | Connect Selected >, …| To Marked command.
The Function Chart Builder highlights the parent PC element, the marked terminal, and any
connecting lines leading to the marked terminal.

4.5.9.3 PC-Terminal | Unmark

Shortcut: SHIFT+KEYPAD 5
Counterpart of PC-Terminal | Mark.
Use this command to unmark the selected and marked PC terminal.
That means you cancel the preparation of this terminal for connection to other PC terminals.
The Function Chart Builder removes the highlight from the parent PC element, the marked
terminal, and any connecting lines leading to the marked terminal.

4.5.9.4 PC-Terminal | Connect… (common)

Shortcut: CTRL+MINUS
Use this command to connect the selected terminal to another terminal.
The Function Chart Builder opens a modeless dialog. That means you can select PC terminals in
the PC Section window with the function chart, create DB elements, and so on, while the dialog
box remains open.

4-374 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.9 PC-Terminal Menu

Figure 4-233. Connect

• Item Designation
The static text in parentheses shows the data type of the selected terminal.
The text box part shows the item designation of the selected terminal.
You can change the selection here and edit some other valid and existing item designation.
The drop-down list box contains the recently selected terminals.

• Next
Select the condition for the “next terminal” in the list box part or edit it directly in the text
box part.
The Function Chart Builder steps to the “next terminal” on the basis of this condition
if you activate the Apply/Next or the Next button.

• To
The Function Chart Builder fills this text box with one of the following connection strings:
– The actual connection if the selected terminal is connected
– The recent connection from the history if the selected terminal is unconnected.
In case of multiple connections to constants, DB terminals, symbols, and TC/CI terminals
and if the input terminal considered as primarily attached to the source is selected,
the connection string starts with the source definition.
Proposed connections are highlighted.
Accept the proposal or select another string from the list box part containing the recently
used connection strings.
Edit the connection in the text box part according to the AMPL source code syntax.
You can use also relative PC item designations. For syntax and examples see Section
4.4.4.4, Connect Terminals by Editing the Connection Definition.
All the terms of the connection string must be of the data type shown in the static text in
parentheses above the Item Designation combo box.
In case of paste conflicts the conflicting connect string is highlighted.

3BDS 100 595R401 4-375

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Name
Activate this button to append a source by name to the connection string of the selected
terminal in the To text box.
If you have selected some part of the connection string in the To text box, it will be
overwritten with the name.
The Function Chart Builder opens the Connect by Name dialog box.
For dialog see Section 4.5.9.5, PC-Terminal | Connect Selected >, By Name.

• DB
Activate this button to append a DB terminal to the connection string of the selected
terminal in the To text box.
If you have selected some part of the connection string in the To text box, it will be
overwritten with the DB terminal.
The Function Chart Builder opens the Connect to DB dialog box.

• TC/CI Terminal
Activate this button to append a TC/CI terminal (from within the circuit or type circuit) to
the connection string of the selected terminal in the To text box.
If you have selected some part of the connection string in the To text box, it will be
overwritten with the TC/CI terminal.
The Function Chart Builder opens the Connect To TC/CI Terminal dialog box.
For dialog see Section 4.5.9.5, PC-Terminal | Connect Selected >, To TC/CI Terminal.

• Symbol
Activate this button to append a symbol representing a PC terminal to the connection
string of the selected terminal in the To text box.
If you have selected some part of the connection string in the To text box, it will be
overwritten with the symbol.
The Function Chart Builder opens the Connect To Symbol dialog box.
For dialog see Section 4.5.9.5, PC-Terminal | Connect Selected >, To Symbol.

• Apply/Next
Activate this button to build the connection with more than one terminal.
A similar action as that of the OK button but you remain in the Connect dialog and the
Function Chart Builder shows the item designation of the next terminal in the
Item Designation text box corresponding the condition set in the Next text box.

NOTE
To skip a terminal use the Next button instead.

• Next
Activate this button to step to the next terminal without leaving the Connect dialog and
without making any connection, that is, to skip terminals.

4-376 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.9 PC-Terminal Menu

If you connect to a new symbol or a symbolic expression containing a new symbol, the Function
Chart Builder opens the Create a Symbol dialog.
For dialog see Section 4.5.5.3, Edit | Create… - for Symbol Section.
If you connect to a new TC/CI terminal, the Function Chart Builder opens the Create a TC/CI
Terminal dialog. For dialog see Section 4.5.5.3, Edit | Create… - for TC/CI Terminal Section.
If you connect to a new name, create it at first by the Edit | Name command.
To change a connection, edit the connection definition in the To text box.
For syntax and examples of connection definition, also for relative connection definitions, see
Section 4.4.4.4, Connect Terminals by Editing the Connection Definition.
If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagrams in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

4.5.9.5 PC-Terminal | Connect Selected >

Submenu for other active section windows than the PC Section window,
or for active Name Table window:

PC-Terminal | Connect Selected (stand-alone)

Shortcut: ALT+MINUS
Use this command to connect the selected terminal in the active window to the selected
PC terminal:
• If the DB Section window is active, connect the selected DB terminal (or the VALUE
terminal of the selected DB element) to the PC terminal, which is selected in the
PC Section window.
• If the Symbol Section window is active, connect the selected symbol to the PC terminal,
which is selected in the PC Section window.
• If the TC/CI Terminal window is active, connect the selected TC/CI terminal to the
PC terminal, which is selected in the PC Section window.
• If the Name Table window is active, connect the selected name to the PC terminal, which
is selected in the PC Section window.
If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagrams in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

Submenus for the active PC Section window:

PC-Terminal | Connect Selected | To Marked

Shortcut: ALT+MINUS
Use this command to connect the selected terminal to the marked PC terminal.
For marking a terminal see Section 4.5.9.2, PC-Terminal | Mark.
If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagrams in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

3BDS 100 595R401 4-377

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

PC-Terminal | Connect Selected | To DB

Shortcut: CTRL+B
Use this command to connect the selected terminal to a DB terminal.

Figure 4-234. Connect to DB

• Filter/Item Des.
Edit a filter in the text box part to list only DB elements with a certain item designation.
Open the list box part to see the valid filters and select one.
# is wildcard for board and channel numbers.

• Item Designation
The item designation of the selected DB element appears here.
To change selection, you can also edit another item designation.
The new selection will be effective in the Item Designation, Instance Name, Attr.,
Callname, Address list box if you press ENTER (activate the OK button.)

• Filter/Instance Name
Select a filter in the list box part or edit it directly in the text box part to list only DB
instances with a certain name. The list box part contains the recently used filters.
Wildcards ‘*’ and ‘?’ are also allowed.
Close the new filter condition with ENTER to make it effective.

NOTE
Be sure to select the View | Sort by Name command if you want to see the
DB elements sorted alphabetically by name in the Item Designation,
Instance Name, Attr., Callname, Address list box.

4-378 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.9 PC-Terminal Menu

• Instance Name
The instance name of the selected DB element appears here.
To change selection, you can also edit another name.
The new selection will be effective in the Item Designation, Instance Name, Attr.,
Callname, Address list box if you press ENTER (activate the OK button.)

• DB Terminal
The drop-down list box contains all terminals of the selected DB element, which can be
connected to the PC terminal selected in the PC Section window.
Select the DB terminal here. See Section 4.4.8.1, Connection Rules.
The text box part reflects your selection. You can also edit here any appropriate DB
terminal.

• Item Designation, Instance Name, Attr., Callname, Address

This list box shows the DB instances, which satisfy the filter conditions, by their item
designation, instance name, attribute, callname, and address.
Select a DB element here.
Your selection appears in the Item Designation and Instance Name text boxes.
Use the View | Sort by Name and View | Sort by Item Designation commands in the
DB Section window to change sorting. You can resize the columns Item Designation,
Instance Name, and so on, by dragging the divisions that separate the header parts at the
top of the list box. The divisions may be visible only if you enlarge the dialog box.
NOTE
Because the number of elements is not continually determined for this list,
the position of the scroll box does not reflect the position of the selected
item in the list. Nevertheless, all other features of the scrollbar are available.

If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagrams in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

PC-Terminal | Connect Selected | By Name

Shortcut: CTRL+A
Use this command to connect the selected terminal to a source by the name of the latter.

Figure 4-235. Connect by Name

3BDS 100 595R401 4-379

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Terminal
The list box part contains all the names, which have the appropriate data type for the
connection. Select a name here.
The text box part reflects your selection. You can also edit here any existing name.
If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagrams in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

PC-Terminal | Connect Selected | To Symbol

Shortcut: CTRL+M
Use this command to connect the selected terminal to a symbol representing a PC terminal.

Figure 4-236. Connect to Symbol

• Connection Definition
Edit here the connection with constants, symbols, or symbolic expressions in form of an
equation, like D=constant, D=<symbol>, or D=symbExpression.
Examples: D=KEY<PARAM1> N=<OUT32>
For more information see Section 4.4.8.5, Use of Symbols.
You can use also new symbols in the symbolic expression. In this case the Function Chart
Builder opens the Create Symbol dialog.
For dialog see Section 4.5.5.3, Edit | Create… - for Symbol Section.
Take care that the value of the expression has the appropriate data type for the connection.

• Symbol
The list box part contains all symbols of the selected object, which have the appropriate
data type for the connection. Select the symbol here.
The text box part reflects your selection.
You can also edit here any appropriate symbol.

4-380 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.9 PC-Terminal Menu

• Append
Activate this button to append the symbol name, which is shown in the text box part of the
Symbol combo box, to the Connection Definition string.
The Function Chart Builder closes the symbol name in angle brackets corresponding to the
syntax of symbolic expressions.
If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagrams in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

PC-Terminal | Connect Selected | To TC/CI Terminal

Shortcut: CTRL+T
Use this command to connect the selected terminal to a TC/CI terminal (from within the circuit
or type circuit).

Figure 4-237. Connect to TC/CI Terminal

• Terminal
The list box part contains all terminals of the circuit or type circuit, which have the
appropriate data type for the connection. Select the terminal here.
The text box part reflects your selection. You can also edit any appropriate existing
terminal name here.
If the connection rules are fulfilled, the Function Chart Builder builds the connection and
updates the PC diagrams in the PC Section windows depending on the Update Function Chart
on Apply preference option set by the Options | Preferences command.

4.5.9.6 PC-Terminal | Virtual Connections…

Use this command to list or consolidate virtual connections in a defined scope.
A connection becomes virtual in the following cases:
• At the moment of its creation, that is, if one of the connected items does not exists yet.
• At the deletion of DB elements connected to PC elements, that is, if one of the connected
items does not exist any more.

3BDS 100 595R401 4-381

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

See also Section 4.5.7.1, Options | Preferences…, Keep PC Connections of Deleted DB

Elements as Virtual Connections.
A connection becomes ordinary, that is, one with no connected items being a virtual object,
explicitly by consolidation.
Condition of successful consolidation of a connection is that the connected items exist.

Figure 4-238. Virtual Connections

• Scope
Select one of the options to define the scope of function of the Consolidate and List
buttons.

• Consolidate
Activate this button to start the consolidation of the virtual connections in the defined
scope.

• List
Activate this button to list the virtual connections in the defined scope.
If you activate the Consolidate button, the Function Chart Builder tries to consolidate the
virtual connections in the defined scope, opens the Output window, and lists there the virtual
connections that cannot be consolidated.
If you activate the List button, the Function Chart Builder opens the Output window and lists
there all of the virtual connections in the defined scope.

4.5.9.7 PC-Terminal | Disconnect…

Shortcut: CTRL+SHIFT+MINUS
Select a terminal before choosing this command.
If you disconnect an output with multiple sinks, the Function Chart Builder displays the
Disconnect dialog box.

4-382 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.9 PC-Terminal Menu

Figure 4-239. Disconnect

• From
The list box shows all the input terminals, which are connected to the selected output
terminal.
Select one or several terminals to be disconnected here.
The text box reflects your selection. You can also edit here the name of the input terminal
to be disconnected.

• Apply
Activate this button to disconnect a sink.
A similar action as that of the OK button but you remain in the Disconnect dialog and the
Function Chart Builder prepares the item designation of the next connected sink in the
From text box.

• All
Activate this button to disconnect all the sinks.
A similar action as that of the OK button.
To remove a name from a selected PC output terminal, use the Edit | Delete Name command.

4.5.9.8 PC-Terminal | Unit >

Submenus:

PC-Terminal | Unit | Create/Edit…

Shortcut: ALT+F5
Use this command to attach a unit to a PC terminal, in fact, for one of the following:
• For an output terminal of a PC element
• For a constant or a DB element terminal connected to an input terminal of a PC element in
an existing connection.

3BDS 100 595R401 4-383

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Use this command also to edit already assigned units.

Figure 4-240. Create/Edit Unit

• Item Designation
The text box part shows the selected PC terminal. You can also edit here the item
designation and use also relative PC item designations, see in Section 4.4.4.4, Connect
Terminals by Editing the Connection Definition.
The drop-down list box part contains the terminals, to which units were recently assigned.
Select here a terminal to copy it to the text box part.

• Unit
Edit here the unit for the terminal, which is shown by Item Designation.
The unit may consist of maximum 6 character.
The drop-down list box part contains the units, which were recently assigned to terminals
or edited.
Select here a unit to copy it to the text box part.

• Apply
Activate this button to assign units to more than one terminal.
A similar action as that of the OK button but you remain in the Create/Edit Unit dialog.
The Function Chart Builder and assigns the specified unit to the selected PC terminal.

NOTE
In the function chart the Function Chart Builder shows the unit only for a constant
source and only at the input terminal, which was connected at first to the constant.
To inspect units not shown in the function chart, select the terminal and choose
the PC-Terminal | Unit | Create/Edit command without editing in the
Create/Edit Unit dialog box.

PC-Terminal | Unit | Delete

Shortcut: SHIFT+ALT+F5
Use this command to remove the unit from the selected terminal.

4-384 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.9 PC-Terminal Menu

4.5.9.9 PC-Terminal | Select for Display >

Submenus:

PC-Terminal | Select for Display | Select

Shortcut: F7
Use this command to select a PC terminal for monitoring.
The Function Chart Builder marks the monitoring by an asterisk ‘*’ on the connection line near
the terminal in the PC Section window with the function chart and also includes the terminal in
the Test Table.
If the engineering station is connected on-line to an AC 100 Series target, if the application
loaded to the target and the one currently selected in the Function Chart Builder are identical,
and if the monitoring is activated, values of the corresponding terminals in the application on
the target will be shown next to the asterisks.
Related commands:
• Window | Test Table to open or activate the Test Table window
• Test | Single Display, Test | Cyclic Display, and Test | Stop Display to start and stop the
monitoring of selected terminals.

PC-Terminal | Select for Display | Unselect

Shortcut: F7
Counterpart of PC-Terminal | Select for Display | Select.
Use this command to cancel the preparation for monitoring of the selected PC terminal.
The Function Chart Builder removes the marking for monitoring from the terminal in the
PC Section window panes with the function chart and also deletes the corresponding PC
display entries in the Test Table.

PC-Terminal | Select for Display | Unselect All

Counterpart of PC-Terminal | Select for Display | Select.
Use this command to cancel the preparation for monitoring of all PC terminals.
The Function Chart Builder removes the marking for monitoring from all terminals in the
PC Section window panes with the function chart and also deletes all PC display entries in the
Test Table.

4.5.9.10 PC-Terminal | Force Value >

Submenus:

PC-Terminal | Force Value | Create/Edit…

Shortcut: F9
Use this command to select a PC terminal for forcing and define or change its force value.

3BDS 100 595R401 4-385

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-241. Create/Edit Force Value

• Item Designation
The text box part shows the selected PC terminal. You can also edit here the item
designation and use also relative PC item designations, see in Section 4.4.4.4, Connect
Terminals by Editing the Connection Definition.
The drop-down list box part contains the terminals, for which force values were recently
created or edited.
Select here a terminal to copy it to the text box part.

• Value
Edit here the force value for the terminal, which is shown by Item Designation.
The drop-down list box part contains the force values, which were recently assigned to
terminals or changed.
Select here a value to copy it to the text box part.

• Apply
Activate this button to include more than one terminal and prepare (set or change) their
force values in the Force Value column of the Test Table window.
A similar action as that of the OK button but you remain in the Create/Edit Force Value
dialog.
The Function Chart Builder displays the force value next to an asterisk ‘*’ on the connection
line near the terminal in the PC Section window panes with the function chart and also includes
the terminal and its prepared force value in the Test Table.
If the engineering station is connected on-line to an AC 100 Series target, if the application
loaded to the target and the one currently selected in the Function Chart Builder are identical,
and if the force values are activated, the corresponding terminals in the application on the target
will be forced to these values.
Related commands:
• Window | Test Table to open or activate the Test Table window
• Test | Activate Force Values to activate the forcing of selected terminals with new values
• Test | Deactivate Force Values to deactivate the forcing of selected terminals.

4-386 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.9 PC-Terminal Menu

PC-Terminal | Force Value | Delete

Shortcut: SHIFT+F9
Use this command to cancel the preparation for forcing of the selected PC terminal.
The Function Chart Builder removes the marking for forcing from the terminal in the
PC Section window panes with the function chart and also deletes the corresponding PC force
entry in the Test Table.
The Function Chart Builder does not force the terminal at the next activation by the Test |
Activate Force Values command.

PC-Terminal | Force Value | Delete All

Use this command to cancel the preparation for forcing of all PC terminals.
The Function Chart Builder removes the markings for forcing from all terminals in the
PC Section window panes with the function chart and also deletes all PC force entries in the
Test Table.
The Function Chart Builder does not force any PC terminal at the next activation by the
Test | Activate Force Values command.

4.5.9.11 PC-Terminal | Invert

Shortcut: CTRL+I
Use this command to invert the logical condition of the selected Boolean input terminal if the
terminal can be inverted.
The Function Chart Builder shows the inversion graphically by adding or removing a small
circle at the terminal in the function chart.

4.5.9.12 PC-Terminal | Insert

Shortcut: CTRL+PLUS
Use this command to insert an additional PC terminal or a set of additional PC terminals if the
PC element can be expanded.
The Function Chart Builder increments the corresponding call parameter value.
Terminals (terminal sets) are always inserted after the last terminal (terminal set).

4.5.9.13 PC-Terminal | Delete

Shortcut: CTRL+SHIFT+PLUS
Use this command, if the PC element allows it, to delete a PC terminal or a set of PC terminals.
The Function Chart Builder decrements the corresponding call parameter value.

NOTE
The last terminal (terminal set) is always deleted independently of selection or
existing connections of that terminal. Make sure to relocate the connections of the
last terminal (terminal set) before deleting.

3BDS 100 595R401 4-387

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.10 Target Menu

4.5.10.1 Target | Connect…
Use this command to connect an AC 100 Series target directly or by routing via other nodes to
the Function Chart Builder.
Prerequisites:
1. The engineering station, the target, and—in case of routing—the nodes along the routing
path are cabled accordingly.
2. In case of routing the nodes along the routing path support routing.
3. In case of routing the nodes along the routing path are configured to support the involved
communication busses.
4. If you want to use connection services running on a remote engineering station, they has to
be accessible via computer network from your local engineering station. See Appendix G,
Configuration of AdvaBuild Communicator for configuration of engineering station -
target communication on the server. In case of remote usage of Advant Station 100 Series
Engineering Board see also On-line Builder User’s Guide, Chapter 2, Installation.

Figure 4-242. Connect Target

• Connection Path
This drop-down list box shows the connection path in symbolic form:
[’target_name’] [server_addr] interface [[intermediate_addr1 [intermediate_addr2]] target_addr]
The list box part contains the connection history, that is, the recent connection paths.
It generally contains also the default connection “COMx”: the point-to-point connection
via the first available COM port of the local engineering station, without target name.

4-388 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.10 Target Menu

• Description of Connection Path

You see here the verbose description of the selected connection path:
Target Name
It is set on the basis of the status information fetched from the target after a successful
connection.
Server
The empty string ('') and “This PC” denotes your local engineering station you work on.
If you want to use the connection service running on a remote engineering station, you can
set it with the help of the Connect Assistant.
To select a server, you have three possible ways:
• Activate the Browse button and find a server in your computer network.
• Select one of the recently used servers in the Selected server PC drop-down list box.
• Enter a server directly in Selected server PC text box.
You can do it in different forms, like
- Name corresponding to universal naming convention (UNC), for example,
\\gpa789 or gpa789
- TCP-IP address, for example, 123.456.789.87
- Distributed server name (DSN) like a world-wide-web address, for example,
www.abb.de or deind.de.
PC Interface
This is the interface of the server towards the routing network (in case of routing) or
towards the target (in case of direct connection).
Examples: COM1, COM4, X3, AF100IF.
Intermediate Node Address
This is the identification of the intermediate node.
In case of point-to-point (direct) connection it is omitted. In other cases the intermediate
node is identified by the kind of bus it is reached and by its address on this bus.
Examples of address form: AF100[bus, station, position], MB300[net, node],
RCOM[rnet, rnode, position].
Target Address
This is the identification of the target.
In case of point-to-point (direct) connection it is omitted. In other cases the target is
identified by the kind of bus it is reached and by its address on this bus.
Examples of address form: AF100[bus, station, position], RCOM[rnet, rnode, position].

• Tip
Describes possible next actions.

• Assistant
Activate this button to call the Connect Assistant guiding you through steps of defining a
new connection path.
In case of simple and repeated connections select the appropriate connection path in the
connection history contained in the Connection Path drop-down list box.

3BDS 100 595R401 4-389

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

In case of complex paths and new connections activate the Connect Assistant by the Assistant
button. The Connect Assistant guides you through steps of connection path definition. See more
information about the usage of the Connect Assistant in Section 4.4.6.4, Connect the
Engineering Station to an AC 100 Series Target.
Upon activation of the OK button the connection will be established. This may take some
seconds. The application requesting the connection can continue.
After successful connection, the Function Chart Builder displays the Status Report of the
target, and if there are differences between the options and base software defined for the
application and those identified in the target, the Options Report window.
Concerning target connection, see also Section 4.4.6.4, Connect the Engineering Station to an
AC 100 Series Target to Section 4.4.6.5, Types of Routing, Diagrams.
If the Function Chart Builder has been in off-line (non-connected) mode, it switches to off-line
connected mode. If the Function Chart Builder has been in on-line preparation mode, it switches
to on-line mode. See also Section 4.4.6.1, About On-line and Off-line Modes.

Comments to Error Message

“AF 100 address on target differs from AF 100 address in application.”
• Connecting an AC 110:
The BUSNO and/or the STNNO terminals of the current CI626 or CI627 DB elements
differ from those loaded on the target. Loading this application would re-configure the bus
and station number of the target. This is not possible on-line.
To do it nevertheless, you must first reset the target without any application by setting the
start-mode switch in the STOP position and pressing the RESET button.

WARNING
This action stops the current application.
When the processor module displays P3, you can load your new application.
• Connecting an AC 70:
– If there is an application loaded to AC 70 (PM810), the BUSNO and/or the STNNO
terminals of the current PM810 DB element differ from those loaded on the target.
Loading this application would re-configure the bus and station number of the target.
– If there is no application loaded, the BUSNO and/or the STNNO terminals of the
current PM810 DB element differ from those set in the Connect dialog.
The bus number set in the Connect dialog at the first connection defines the bus
number on AC 70. This is the bus number that the AC 70 expects at all further
connections.
To enable loading of the application, reset the target without any application by either
pressing the RESET button until P3 is shown or by choosing the Target | Clear PROM
and Target | Restart commands.

WARNING
This action stops the current application.
When P3 is shown on the PM810, you can load your new application.
• Connecting an AC 55: This error message does not occur.

4-390 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.10 Target Menu

Comment to Error Message “Network: Routing not possible”

This error message can also occur if you specify direct connection (no routing) but set a
wrong position in the Address - Target group of the Connect dialog box.

4.5.10.2 Target | Disconnect

Counterpart of Target | Connect.
The Function Chart Builder disconnects the on-line connected AC 100 Series target.
If the Function Chart Builder has been in off-line connected mode, it switches to off-line (non-
connected) mode.
If the Function Chart Builder has been in on-line mode, it switches to on-line preparation mode.

CAUTION
Forced PC and DB terminals behave differently on the target:
• At PC terminals, the force values will be deactivated on the target after its
disconnection.
• At DB terminals, the force values will remain active on the target after its
disconnection.

4.5.10.3 Target | Deblock Program

Use this command to start the execution of the application program in the on-line connected
AC 100 Series target.
The Function Chart Builder displays a query box to confirm the command.
Rather than using mouse actions, you answer by pressing keys.
The Function Chart Builder updates the Status Report of the target.

4.5.10.4 Target | Block Program

Counterpart of Target | Deblock Program.
Use this command to stop the execution of the application program in the on-line connected
AC 100 Series target.
The Function Chart Builder displays a query box to confirm the command.
Rather than using mouse actions, you answer by pressing keys.
The Function Chart Builder updates the Status Report of the target.

4.5.10.5 Target | Load Application

Use this command to load the target code of an application program to the on-line connected
AC 100 Series target.
Prerequisites:
• Translate the application program first with the File | Generate Target Code command.
• Block the application program running on the AC 100 Series target with the
Target | Block Program command before loading if there is another application program
running.

3BDS 100 595R401 4-391

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder displays a query box to confirm the command.
Rather than using mouse actions, you answer by pressing keys.
The Function Chart Builder opens the Output window, protocols there the download process,
and updates the Status Report of the target.
If the download is successful, the Function Chart Builder offers switching to on-line mode.

4.5.10.6 Target | Upload Application

Use this command to upload the target code of an application program from the RAM of the
on-line connected AC 100 Series target. It is normally followed by a
File | Backtranslate Target Code command.

NOTES
Application retrieval is supported by Function Chart Builder 4.6 and higher.

The application can only be retrieved if you work with the same Function Chart
Builder version as the one with which its target code was generated.

This command is available only for new node types explicitly supporting
application retrieval, such as AC 80 2.0.

For successful retrieval, node type and element library versions used by the
application to be retrieved must be available and installed in the corresponding
release subdirectories. Or they must be stored with the target code on the target.

The command will not be executed if the application is exactly the same in the
target and in the Function Chart Builder, for example, after a Target | Load
Application. After any substantial change Target | Upload Application becomes
effective again.

The scope of application retrieval depends on the information included in the target code stored
on the target, that is, on the options that were selected at target code generation.
The Function Chart Builder stores the target code files *.C00 and *.C?? in the \CONTROL
subdirectory of the node.
See also Section 4.4.6.15, Retrieve Application from an AC 100 Series Target.

4.5.10.7 Target | Save in PROM

The application program in the AC 100 Series targets is usually stored in RAM.
Use this command to save the application program in a non-volatile flash PROM of the on-line
connected target.
The Function Chart Builder displays a query box to confirm the command.
Rather than using mouse actions, answer by pressing keys.
The Function Chart Builder updates the Status Report of the target.

4-392 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.10 Target Menu

4.5.10.8 Target | Update Slave

The application program in the AC 100 Series targets is usually stored in RAM.
Use this command to copy the application program from the on-line connected master controller
of an AC 100 Series target with CPU redundancy to the slave controller and save it there in non-
volatile flash PROM.
This command is available only for target types supporting this function, such as AC 160.
The Function Chart Builder displays a query box to confirm the command.
Rather than using mouse actions, answer by pressing keys.
The Function Chart Builder updates the Status Report of the target.

4.5.10.9 Target | Clear PROM

The application program in AC 100 Series targets is usually backed up in non-volatile flash
PROM. Use this command to clear the PROM of the on-line connected target.
The Function Chart Builder displays a query box to confirm the command.
Rather than using mouse actions, answer by pressing keys.
The Function Chart Builder updates the Status Report of the target.

4.5.10.10 Target | Restart

Use this command to restart the connected AC 100 Series target. This command is equivalent
with pushing the INIT button of the controller.
The Function Chart Builder disconnects the target after having triggered the restart.
The controller executes a cold start. Depending on the implementation of start-up behavior,
it takes into account
• Position of the START MODE selector: AUTO, CLEAR, or STOP
• Value of STARTMOD terminal of the PMi DB element: AUTO, CLEAR, or STOP. (
It is in the DB part of the application program stored in the PROM of the controller.)

Table 4-32. Restart Behavior

Position/Value Restart Behavior

AUTO Copies the application from PROM to RAM.
Leaves all variables and historical values
unchanged. Deblocks the application.
CLEAR Hardware is reset to initial state.
Copies the application from PROM to RAM.
All variables and historical values are reset.
Deblocks the application from scratch.
STOP Hardware is reset to initial state. RAM is
cleared, no application is loaded from PROM.

3BDS 100 595R401 4-393

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.10.11 Target | Set Date and Time…

Use this command to set the date and time in the on-line connected AC 100 Series target.
You synchronize the target to the Advant Station 100 Series Engineering Station or set date and
time of the target to a predefined value.

Figure 4-243. Set Date and Time

• AS 100ES, Date and Time

Date and time in your engineering station.

• Target, Date and Time

Date and time in the target.

• Synchronize Target
Activate this button to synchronize the target to the engineering station.

• Preset Target Time

Activate this button to open the Preset Target Date and Time dialog and preset the target
time to a given value.

Figure 4-244. Preset Target Data and Time

- Date and Time

Edit here the date and time to be set in the target.
- Set Now
Activate this button to set the date and time in the target.
The Function Chart Builder sets this date and time in the target at the moment of the
activation of the Set Now button.

4-394 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.10 Target Menu

Rather than using mouse actions, answer by pressing keys.

The Function Chart Builder updates the Status Report of the target.

NOTES
Before synchronizing, it is reasonable to check and possibly set the date and time
of the engineering station, for example, by Settings | Control Panel in the Start
menu of Windows NT, then Date/Time.
You can use Settings | Control Panel in the Start menu of Windows NT, then
Regional Settings to set the date and time style.

4.5.10.12 Target | Set Password…

Use this command to set, change, and clear a password on an appropriate on-line connected
AC 100 Series target supporting target access protection.
This password serves to allow accessing the target and to protect the application on it.

CAUTION
Use password protection only if it is reasonable. Be aware, if you forget the
password, there is no “universal password”, you can just stop the target to clear
the password. A warm start does not clear the password.

Figure 4-245. Set Password on Target

• Old Password
Enter here the old password if there is any.
Be sure using lower case and upper case correctly.

• New Password
Enter here the new password if you want to set one.
The password has to consist of 8 to 50 printable characters.
Leave this text box empty if you want to clear the password.

• Confirm New Password

Repeat here the new password if you want to set one.
Leave this text box empty if you want to clear the password.
The protection with the new password is effective for every connection to this target.

3BDS 100 595R401 4-395

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTE
Do not mix up target password and ODB password. See Section 4.5.4.11, File |
Set Password…. Nevertheless, if the ODB password equals the target password,
you do not need to enter the same password again when connecting to target.

4.5.10.13 Target | Application Checksum…

Use this command to inspect checksum (CRC) of the application in the RAM and checksum of
the system in the PROM of the target, and to store the application checksum. This command is
available if an AC 100 Series target is connected that supports target access protection.

Figure 4-246. Application Checksum

• Target RAM
Application CRC contains the current checksum of the application running in the RAM
of the target. Stored CRC is the checksum that was stored at date and time shown by
Stored At in the RAM of the target.

• Target PROM
System CRC contains the checksum of the system in the PROM of the target.

• Store
Activate this button to store the checksum shown by Target RAM - Application CRC in
the RAM of the target.

• Close
Activate this button to close the Application Checksum dialog box.
The application checksum is calculated in the target after every change of the application by
Target | Load Application or File | Save and Load. The calculation may take several seconds.
Then you can access the application checksum any time and compare with the stored value.
The checksum of the system in PROM is calculated cyclically in the target.
You can access the three checksum values also by an appropriate PC element (SYS-CRC) and
use them to check integrity or change of your application program and system and generate an
alarm, for example, at any on-line change.

4-396 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.10 Target Menu

4.5.10.14 Target | Report Status

Use this command to update the Status Report of the on-line connected AC 100 Series target.
See also Section 4.5.2.9, Status Report Window.

4.5.10.15 Target | Report Options

Use this command to read the options of the on-line connected AC 100 Series target and to
present them in the Options Report window.
You can compare them with the options selected in the Application Builder.
See also Section 4.5.2.10, Options Report Window.
The Function Chart Builder updates the Status Report of the target.

4.5.10.16 Target | Report Attributes

Use this command to read the attributes, such as the configured AF 100 communication
interfaces, of the on-line connected target of a newer node type and show them in the following
dialog box:

Figure 4-247. Attribute Report

4.5.10.17 Target | Diagnostics

Use this command to read the errors reported from the on-line connected AC 100 Series target.
If you are working with an AC 100 Series target of a newer node type, such as AC 160, AC 110
2.1 and higher, AC 80, AC 70 1.1 and higher, and AC 55 1.1, this command starts the
Diagnostics program attached to the Function Chart Builder.
If you are working with a target of node type AC 110 2.0, AC 70 1.0, and AC 55 1.0,
this command starts the Diagnosis program attached to the Function Chart Builder and displays
the reported errors in the Error Report window.
See Section 4.5.2.11, Diagnostics, Error Report Window.
The target reports all the errors collected since the last clear.

3BDS 100 595R401 4-397

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.11 Test Menu

4.5.11.1 Test | Single Display

Shortcut: ALT+F7
Alternative to Test | Cyclic Display.
Use this command to sample terminals selected for monitoring (terminals with state ‘D’ in
Test Table windows) once.
The command is available only in on-line mode, that is, if an AC 100 Series target is connected
and the application program loaded on this target equals the one saved in the internal data
representation.
If you have started sampling of terminals, the Function Chart Builder updates the PC and DB
terminal values once in the Test Table and the PC terminal values also in PC Section window
panes with the function chart, provided the corresponding windows are open.
NOTE
The display and force values in the target are significant only if the target is
unblocked and all of the pertaining executable units are also deblocked, that is,
the RUN terminals of the pertaining PC structure elements are set to 1, the IMPL
and ACT terminals of the pertaining DB elements are set to 1.

Related commands:
• Window | Test Table to open or activate the Test Table window
• PC-Terminal | Select for Display | … to select and unselect PC terminals for monitoring.

4.5.11.2 Test | Cyclic Display

Shortcut: CTRL+F7
Alternative to Test | Single Display.
Use this command to sample terminals selected for monitoring (terminals with state ‘D’ in
Test Table windows) continuously.
The command is available only in on-line mode, that is, if an AC 100 Series target is connected
and the application program loaded on this target equals the one saved in the internal data
representation.
If you have started sampling of terminals, the Function Chart Builder updates the PC and DB
terminal values continuously in the Test Table and the PC terminal values also in PC Section
window panes with the function chart, provided the corresponding windows are open.
NOTE
The display and force values in the target are significant only if the target is
unblocked and all of the pertaining executable units are also deblocked, that is,
the RUN terminals of the pertaining PC structure elements are set to 1, the IMPL
and ACT terminals of the pertaining DB elements are set to 1.

The Function Chart Builder attempts to sample terminals and update the values in the related
windows normally with the cycle time stored in the workspace, else with the cycletime defined
by the Test | Set Cycletime command.

4-398 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.11 Test Menu

NOTE
The effective cycle time of cyclic display depends also on other factors, like
target load, amount of displayed and forced terminal values, complexity of
communication path between the engineering station and the target.

The simplest way to stop and restart cyclic display is to press ENTER or the SPACE bar.
Related commands:
• Window | Test Table to open or activate the Test Table window
• PC-Terminal | Select for Display | … to select and unselect PC terminals for monitoring.

4.5.11.3 Test | Stop Display

Shortcut: CTRL+F7
Counterpart of Test | Cyclic Display and Test | Single Display.
Use this command to stop sampling terminals selected for monitoring (terminals with state ‘D’
in Test Table windows).
The command is available only in on-line mode, that is, if an AC 100 Series target is connected
and the application program loaded on this target equals the one saved in the internal data
representation.

4.5.11.4 Test | Set Cycletime…

Use this command to set cycle time for cyclic display (monitoring) of terminal values.

Figure 4-248. Set Cycletime

• Cycletime for Cyclic Display

Set a value between 1 and 60 second here.
Default value is 1 second.
0 second means “as fast as possible”.
If you choose the Test | Cyclic Display command, the Function Chart Builder attempts to
sample terminals selected for monitoring in the on-line connected target and update the values
in the related windows with the cycle time defined here.

3BDS 100 595R401 4-399

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTE
The value of cycle time is part of the object-specific workspace parameters.
So choose the Options | Workspace command and select the Last Workspace
Used option if you want to preserve any cycle time set to other than 1 second for
the next Function Chart Builder sessions with the selected node.

4.5.11.5 Test | Set Trigger…

Use this command to define the condition, at the occurrence of which cyclic monitoring stops
automatically. An example of a condition may be that a signal exceeds a defined threshold.

Figure 4-249. Trigger Setup

Formula
A valid expression which may contain values, constants, operators, and indexes for values.
Value: Any signal that has been selected in the pertaining Test Table window.
You can pick up a name from the Available Variable Names drop-down box
and insert it into the Formula field by copy and paste.
Constant: Any constant like 2 or 50.5.
Operator: ==, <, <=, >, >=, +, -, *, /, (, ), AND, OR, XOR, NOT.
Index: signal_name [n]; with -10 <= n <= -1.
A signal name without an index means the current value, signal_name [-1]
means the foregoing value, and so on.
Example: A formula to detect a positive slope of a curve may look like this:
(CURRENT_VAL - CURRENT_VAL[-1])>0

Available Variable Names

A list containing the values selected in the pertaining Test Table window.
Use copy and paste to pick up values from this list and to insert them into the Formula.

4-400 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.11 Test Menu

Trigger Type
Disable: The trigger is disabled independent of the formula.
Stop if condition is TRUE: Means recording will be stopped when condition is true.

Trigger Length
(This control is not selectable.)
The Function Chart Builder stops cyclic monitoring if the condition occurs and “Stop if
condition is TRUE” is set.
NOTES
The detection of the condition takes place on the engineering station with the data
read from the Advant Controller 100 Series and not on the controller itself.
There is no direct synchronization between Advant Controller 100 Series and
Advant Station 100 Series. If you want to assure that you will get a value from
each cycle of the Advant Controller 100 Series, try to set a cyclic display cycle
time by Test | Set Cycletime that is shorter than the cycle time of the
corresponding PC program

4.5.11.6 Test | Activate Force Values

Use this command to activate additionally the force values corresponding to prepared force
entries, which are selected in the active Test Table window.
NOTE
The display and force values in the target are significant only if the target is
unblocked and all of the pertaining executable units are also deblocked, that is,
the RUN terminals of the pertaining PC structure elements are set to 1, the IMPL
and ACT terminals of the pertaining DB elements are set to 1.

The command is available only in on-line mode, that is, if an AC 100 Series target is connected
and the application program loaded on this target equals the one saved in the internal data
representation.
The Function Chart Builder displays the Activate Force Values dialog box, you can combine
here monitoring with forcing. (Depending on previous actions it displays Figure 4-251 instead.)

Figure 4-250. Activate Force Values

3BDS 100 595R401 4-401

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Force Only
Select this option if you want to force without monitoring immediately thereafter.

• Force and Single Display

Select this option if you want to force and then monitor terminals once.

• Force and Cyclic Display

Select this option if you want to force and then monitor terminals continuously.
The Function Chart Builder
• Starts forcing the selected prepared force entries, that is, the ones with state ‘P’ in the
active Test Table window, on-line in the target, in addition to the values previously forced.
It changes their state to ‘F’.
• Continues forcing all already active force entries in the target, no matter they are visible or
not in the active Test Table window.
• Stops forcing force entries to be removed, that is, the ones with state ‘R’ in the active
Test Table window, on-line in the target.
Thereafter, it also deletes these entries in the Test Table.
Related commands:
• Window | Test Table to open or activate the Test Table window
• PC-Terminal | Force Value | … to select and unselect PC terminals for forcing and define
force values.

4.5.11.7 Test | Deactivate Force Values

Use this command to deactivate the values of terminals selected for forcing in the active
Test Table window.
The command is available only in on-line mode, that is, if an AC 100 Series target is connected
and the application program loaded on this target equals the one saved in the internal data
representation.
The Function Chart Builder
• Stops forcing the selected active force entries, that is, the ones with state ‘F’ in the active
Test Table window, on-line in the target.
It changes the state to ‘P’ and clears the force values in the Value on Target column.
• Stops forcing force entries to be removed, that is, the ones with state ‘R’ in the active
Test Table window, on-line in the target.
Thereafter, it also deletes these entries in the Test Table.
• Continues forcing all already active force entries in the target, that are not selected or are
invisible in the active Test Table window.
Related commands:
• Window | Test Table to open or activate the Test Table window
• PC-Terminal | Force Value | … to select and unselect PC terminals for forcing and define
force values.

4-402 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.11 Test Menu

4.5.11.8 Test | Activate All Force Values

Shortcut: ALT+F9
Use this command to activate additionally the force values corresponding to prepared force
entries of the Test Table.

NOTES
The display and force values in the target are significant only if the target is
unblocked and all of the pertaining executable units are also deblocked, that is,
the RUN terminals of the pertaining PC structure elements are set to 1, the IMPL
and ACT terminals of the pertaining DB elements are set to 1.

The force values may be visible or invisible in the Test Table windows.

The command is available only in on-line mode, that is, if an AC 100 Series target is connected
and the application program loaded on this target equals the one saved in the internal data
representation.
The Function Chart Builder displays the Activate Force Values dialog box, in which you can
combine monitoring with forcing.
(Depending on previous actions it displays Figure 4-250 instead.)

Figure 4-251. Activate All Force Values

• Force Only
Select this option if you want to force without monitoring immediately thereafter.

• Force and Single Display

Select this option if you want to force and then monitor terminals once.

• Force and Cyclic Display

Select this option if you want to force and then monitor terminals continuously.

3BDS 100 595R401 4-403

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

The Function Chart Builder

• Starts forcing all prepared force entries, that is, the ones with state ‘P’, on-line in the
target, in addition to the values previously forced. It changes their state to ‘F’.
• Continues forcing all already active force entries in the target, that is the ones with state
‘F’ on the target.
• Stops forcing force entries to be removed, that is, the ones with state ‘R’, on-line in the
target. Thereafter, it also deletes these entries in the Test Table.
Related commands:
• Window | Test Table to open or activate the Test Table window
• PC-Terminal | Force Value | … to select and unselect PC terminals for forcing and define
force values.

4.5.11.9 Test | Deactivate All Force Values

Shortcut: CTRL+F9
Use this command to deactivate forcing of values on all terminals.
The force values may be visible or invisible in the Test Table windows
The command is available only in on-line mode, that is, if an AC 100 Series target is connected
and the application program loaded on this target equals the one saved in the internal data
representation.
The Function Chart Builder
• Stops forcing all active force entries, that is, the ones with state ‘F’, on-line in the target.
It changes the state to ‘P’ and clears the force values in the Value on Target column.
• Stops forcing force entries to be removed, that is, the ones with state ‘R’, on-line in the
target. Thereafter, it also deletes these entries in the Test Table.
Related command:
Window | Test Table to open or activate the Test Table window.

4.5.11.10 Test | Upload DB Force List

Use this command to upload force values from the target to the Test Table.
The command is available only for an on-line connected AC 100 Series target, and if the loaded
application program equals to the one saved in the internal data representation.

4.5.11.11 Test | Set DB Value…

Use this command to set a value once in the target.

4-404 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.11 Test Menu

The command is available only in on-line mode, that is, if an AC 100 Series target is connected
and the application program loaded on this target equals the one saved in the internal data
representation.

Figure 4-252. Set DB Value

• DB Element, Terminal, Value

Edit in the text box parts of these combo boxes the DB element, its terminal, and the value
you want to set once. The drop-down list box parts contain the recent items and values.
The set value is effective on the controller until it is overwritten typically by the application
program in a next PC execution cycle, by setting another value, and so on.

NOTE
Before setting a DB value, deactivate all PC elements that can overwrite the set
value. For example, keep the ON terminals of the corresponding PCPGM,
CONTRM, or other structure element forced to 0 for a necessary period.

4.5.11.12 Test | Import (Test Values) …

Use this command to import display/force list from a file to the Test Table.
The command is available only for AC 100 Series
Define the file to be imported in the following dialog box.

3BDS 100 595R401 4-405

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-253. Import Test Table

• Directory
The symbol shows the directory currently browsed for files.
Default is the \DBDATA subdirectory of the current node.
You can also select a subdirectory in the list box below.
Or go to the directory on the next higher level by clicking on the Up One Level icon.
Click on the Create New Folder icon to create a new subdirectory.

• Up One Level and Create New Folder (Icons)

Click on the Up One Level icon to go to the directory on the next higher level.
Click on the Create New Folder icon to create a new subdirectory.

• List and Details (Icons)

Click on these icons to display the files and subdirectories in corresponding forms.

• Files and Subdirectories

The list box contains all available files and subdirectories in the specified directory, which
correspond to the filter condition. Click on the List and Details icons to display the files
and subdirectories in corresponding forms.

• File Name
Select a file name from the list box or type it here. Or edit a new filter condition, for
example, MY*.DFL, and press ENTER to make it effective.

• Files of Type
Select a filter condition from the standard filters in this drop-down list box.
The default extension for display/force list files is DFL.

• Open
Activate this button to start the import.

4-406 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.11 Test Menu

4.5.11.13 Test | Export (Test Values) …

Use this command to export the display/force list from the active Test Table window to a file.
The command is available only for AC 100 Series.
Define the file to be exported in the following dialog box:

Figure 4-254. Export Test Table

• Directory
The symbol shows the directory currently browsed for files.
Default is the \DBDATA subdirectory of the current node.
You can also select a subdirectory in the list box below.
Or go to the directory on the next higher level by clicking on the Up One Level icon.
Click on the Create New Folder icon to create a new subdirectory.

• Up One Level and Create New Folder (Icons)

Click on the Up One Level icon to go to the directory on the next higher level.
Click on the Create New Folder icon to create a new subdirectory.

• List and Details (Icons)

Click on these icons to display the files and subdirectories in corresponding forms.

• Files and Subdirectories

The list box contains all available files and subdirectories in the specified directory, which
correspond to the filter condition. Click on the List and Details icons to display the files
and subdirectories in corresponding forms.

• File Name
Select a file name from the list box or type it here. Or edit a new filter condition, for
example, MY*.DFL, and press ENTER to make it effective.

• Save as Type
Select a filter condition from the standard filters in this drop-down list box. If *.DFL is set,
extension .DFL (default for display/force list files) will be appended to the file name.

3BDS 100 595R401 4-407

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Save
Activate this button to start the export.

4.5.12 Window Menu

4.5.12.1 Window | New Window
If one of the following windows is active, use this command to open a new copy of it:
• PC Section window
• DB Section window
• Symbol Section window
• TC/CI Terminal Section window
• Name Table window
• Test Table window.

4.5.12.2 Window | Cascade

Use this command to arrange all open document windows in a partly overlapping fashion.

4.5.12.3 Window | Tile Horizontally

Use this command to arrange all open document windows one above the other in a non-
overlapping fashion.

4.5.12.4 Window | Tile Vertically

Use this command to arrange all open document windows side by side in a non-overlapping
fashion.

4.5.12.5 Window | Arrange Icons

Use this command to arrange the icons of minimized document windows along the bottom of
the application window.

NOTE
Some or all of the icons may be covered by open document windows in the
application window.

4.5.12.6 Window | Resize

If one of the following windows is active, use this command to resize it to its default size:
• DB Section window
• Symbol Section window
• TC/CI Terminal Section window
• Name Table window
• Test Table window.

4-408 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.12 Window Menu

The default size is a minimum size, which allows access of all controls of these windows
without the need for scrolling. The default size may differ from the initial size when opening the
window from the recent workspace.

4.5.12.7 Window | Slide

Shortcut: SCROLL LOCK
Toggle switch.
Use this command to toggle slide mode on or off.
Set the slide mode to enable sliding of window contents by cursor keys like LEFT, DOWN.
Clear the slide mode to enable selecting PC elements, list elements, PC terminals, and so on by
the cursor keys. See also Section 4.4.1.2, How to Use the Mouse and Section 4.4.1.3, Using the
Keyboard Instead of the Mouse.
A check mark ‘ ’ appears next to the menu item if you selected it recently.

4.5.12.8 Window | Close…

Use this command to close the one or several document windows.
Define the windows to be closed in the following dialog box:

Figure 4-255. Close Windows

• Sort by Number, Sort by Type

Select one of these options to sort the open windows in the list accordingly.

• List
Contains the open windows.
Select here one or several windows to be closed.

3BDS 100 595R401 4-409

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

For multiple selection see Section 4.4.1.2, How to Use the Mouse and Section 4.4.1.3,
Using the Keyboard Instead of the Mouse.

4.5.12.9 Window | Close All

Use this command to close all document windows.

4.5.12.10 Window | *.ODB

Shortcut: ALT+number

,where number = 1, 2,… 9, 0 corresponds to the ordinal 1, 2,… 9, 10, which was assigned to this
window at its creation during the current Function Chart Builder session.
Use this command to open or activate the *.ODB window.

4.5.12.11 Window | Output

Shortcut: ALT+number

,where number = 1, 2,… 9, 0 corresponds to the ordinal 1, 2,… 9, 10, which was assigned to this
window at its creation during the current Function Chart Builder session.
Use this command to open or activate the Output window.

4.5.12.12 Window | Name Table

Shortcut: ALT+number

,where number = 1, 2,… 9, 0 corresponds to the ordinal 1, 2,… 9, 10, which was assigned to this
window at its creation during the current Function Chart Builder session.
Use this command to open or activate the Name Table window.

4.5.12.13 Window | Test Table

Shortcut: ALT+number

,where number = 1, 2,… 9, 0 corresponds to the ordinal 1, 2,… 9, 10, which was assigned to this
window at its creation during the current Function Chart Builder session.
Use this command to open or activate the Test Table window.

4.5.12.14 Window | 1, 2, … (Activate Section Windows)

Shortcut: ALT+number

,where number = 1, 2,… 9, 0 corresponds to the ordinal 1, 2,… 9, 10, which was assigned to this
window at its creation during the current Function Chart Builder session.
Use this command to activate the document window listed with number 1, 2,… at the bottom of
the Window menu. They are generally windows for different sections of the object, you are
working on, for example, PC Section window.

4-410 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.13 Help Menu

4.5.13 Help Menu

4.5.13.1 Help | Contents

Use this command to display the Help Topics window of the Function Chart Builder Help.
Its Contents tab lists the available “how to”-type and reference information on the Function
Chart Builder. The information is hierarchically ordered.
Click on the book symbols to open them ( ) and on help topic symbols to jump to
final topics of interest.
In the Function Chart Builder 4.* - Help window you can click the Contents button whenever
you want to return to the Help Topics window. Here, use the Index tab to search for topics
containing a keyword and the Find tab for full text search.

4.5.13.2 Help | On Context

Shortcut: SHIFT+F1
Use this command to obtain context-specific help on the Function Chart Builder.
The mouse pointer changes to an arrow and question mark.
Click to an element of the Function Chart Builder windows, such as a command in a menu,
a toolbar button, or a dialog box.
The topic containing help information about this element will be shown in the
Function Chart Builder 4.* - Help window.

4.5.13.3 Help | How to Use Help

Use this command for instructions about using Help.

4.5.13.4 Help | On Node…

Use this command to display the On Node dialog box that contains node type, base software,
and options of the object you are working on.

Figure 4-256. On Node

3BDS 100 595R401 4-411

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.13.5 Help | DB Element Reference

This command is available depending on the node type of selected object.
Use it to open Data Base Elements Advant Controller nnn Reference Manual of the node type
nnn.
The Function Chart Builder looks for available on-line manual file, normally a *.PDF file, and
an appropriate program to open it, normally the Acrobat Reader, respectively.

NOTE
If the Function Chart Builder cannot open the on-line manual:

• If the on-line manual file is missing on the engineering station, install it.
• If the appropriate program that opens the on-line manual file is missing on the
engineering station, install it.
• If the on-line manual file extension is not associated with the program that
opens it, associate them, for example, by double-clicking on it in the Explorer
of Windows NT and choosing Acrobat Reader in the Open With dialog box.

4.5.13.6 Help | PC Element Reference

This command is available depending on the node type of selected object.
Use it to open PC Elements Advant Controller nnn Reference Manual of the node type nnn.
The Function Chart Builder looks for available on-line manual file, normally a *.PDF file, and
an appropriate program to open it, normally the Acrobat Reader, respectively.

NOTE
If the Function Chart Builder cannot open the on-line manual:

• If the on-line manual file is missing on the engineering station, install it.
• If the appropriate program that opens the on-line manual file is missing on the
engineering station, install it.
• If the on-line manual file extension is not associated with the program that
opens it, associate them, for example, by double-clicking on it in the Explorer
of Windows NT and choosing Acrobat Reader in the Open With dialog box.

4.5.13.7 Help | Other Reference

This command is available depending on the node type of selected object.
Use it to open the on-line manual with the given title.
The Function Chart Builder looks for available on-line manual file, for example, a *.HLP or a
*.PDF file, and an appropriate program to open it, for example, the Windows NT help engine
and Acrobat Reader, respectively.

4-412 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.13 Help Menu

NOTE
If the Function Chart Builder cannot open the on-line manual:

• If the on-line manual file is missing on the engineering station, install it.
• If the appropriate program that opens the on-line manual file is missing on the
engineering station, install it.
• If the on-line manual file extension is not associated with the program that
opens it, associate them, for example, by double-clicking on it in the Explorer
of Windows NT and choosing winhelp32 or Acrobat Reader, as applicable, in
the Open With dialog box.

4.5.13.8 Help | Release Notes

Use this menu command to open the Function Chart Builder Release Notes containing the
following:
• General information on the Function Chart Builder version, compatibility, and related
documentation
• New functions, improvements, discontinued and replaced functions of the Function Chart
Builder version; fixed or known problems, restrictions, and recommendations
• Installation and un-installation of the Function Chart Builder version; upgrading, backup,
and restoration of application data.

NOTE
The Release Notes is a *.PDF file.
To read it, you need Acrobat Reader installed on the engineering station and the
extension PDF associated with the Acrobat Reader.
Acrobat Reader is a free product of Adobe Systems Inc.

4.5.13.9 Help | About Function Chart Builder…

Use this command to display the copyright and release notice of the Function Chart Builder.

Figure 4-257. About Function Chart Builder

3BDS 100 595R401 4-413

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.14 Controls of Diagnostics

NOTE
The Diagnostics program is adapted to the different diagnostics features of both
former and recent controller versions.
In case of AC 110 2.0, AC 70 1.0, and AC 55 1.0 it is called the Diagnosis
program.
In case of AC 100 Series targets of newer node types, such as AC 160, AC 110
2.1 and higher, AC 80, AC 70 1.1 and higher, and AC 55 1.1, it is called the
Diagnostics program.

4.5.14.1 Controls in Title Bar of Diagnostics

The Diagnostics program has its own application window and several document windows,
which are identified by their title: Diagnostics, Module Diagnostics, and so on.
The title bar may contain the following elements:
• Application control menu button

• Document control menu button

• Title, that is, name of application or name of document

• Maximize button

• Minimize button

• Restore button

• Close button .

4.5.14.2 Controls in Toolbar of Diagnostics

Figure 4-258. Toolbar of Diagnostics

The Toolbar is displayed across the top of the application window, below the menu bar.
The Toolbar provides quick mouse access to many functions used in the Diagnostics program.
To hide or display the Toolbar of the Diagnostics window, choose the View | Toolbar
diagnostic command.

4-414 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.14 Controls of Diagnostics

The following table lists the toolbar commands of Diagnostics:

Table 4-33. Icons and Commands in the Toolbar of Diagnostics

Icon Diagnostic Command Short Description

File | Save As Saves the report or diagnosis in the active document window.
File | Log Logs the report or diagnosis in the active document window into a log file.
File | Print Prints a report or diagnostic data.
Target | Report Errors Reports errors of connected target and shows the Error Report.
Target | List Modules Lists modules of connected target and shows the Module List.
Target | Diagnose Module Starts diagnostics of a module, then shows the Module Diagnostics.
Help | Contents Starts the on-line help of Diagnostics and displays its contents.
Help | On Context Changes the mouse pointer to an arrow and question mark to get
context-specific help on Diagnostics.

4.5.14.3 Indicators in Status Bar of Diagnostics

Figure 4-259. Status Bar of Diagnostics

The Status Bar is displayed at the bottom of the application window. To display or hide the
Status Bar of the Diagnostics window, use the View | Status Bar diagnostic command.
The left area of the status bar describes actions of menu items as you use the arrow keys to
navigate through menus. This area similarly shows messages that describe the actions of toolbar
buttons as you depress them, before releasing them. If after viewing the description of the
toolbar button command you wish not to execute the command, then release the mouse button
while the pointer is off the toolbar button.
The right areas of the Status Bar display the following information:

Table 4-34. Indicators in the Status Bar of Diagnostics

Indicator Description
COMx/X3 Selected port for communication with the AC 100 Series target: COM1 to COM4, X3.
[bus, station, position] Address of the (final) target the engineering station is communicating with. The two forms
or of the address contents correspond to routing via AF 100 and RCOM, respectively.
[rNet, rNode, position] [0, 0, position] stand for directly connected target (no routing).
LOG Indicates that the report in the active window is already logged in a log file using the
File | Log and File | Logfile Setup diagnostic commands.

3BDS 100 595R401 4-415

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.15 Controls in Document Windows of Diagnostics

4.5.15.1 Error Report Window
In this window the Diagnostics program displays all the modules of the on-line connected
target, for which errors are reported.

Figure 4-260. Error Report Window

Date, Time
Date and time when the data was read from the target.

List Modules (Type)

Set here a filter to select the modules by their type.
Wildcards ‘?’ (for one character) and ‘*’ (for a group of characters) are supported.
The list box part contains the predefined filters *, AI*, AO*, CI*, DI*, and DO*.
Activate the filter by pressing the ENTER key.

Delete Reported Errors

Activate this button to delete all the reported errors on the target.
This action concerns not just the reported errors of the module selected in the list box.

Diagnose Module
Activate this button to open the Module Diagnostics window for the selected module.

4-416 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.15 Controls in Document Windows of Diagnostics

List Box
Select a module here for diagnosing it.
The modules are listed by their address.
The significance and ranges of target address for different node types see in the following table:

Table 4-35. Significance and Ranges of Target Address

2nd Address Part 3rd Address Part 4th Address Part

1st Address Part
Target
Rang
Significance Range Significance Significance Range Significance Range
e
AC 110 2.1 Bus number 0 - 255 Station number 1 - 80 Module position 1 - 20, Subposition
and higher (AF 100) (AF 100) + (position of
If connected If connected 100 * substation 101 - 120, the subcarrier
locally, without locally, without number ..., module): 1-2
routing: 0 routing: 0 (for I/O stations) 701 - 720 If module has
no subcarrier: 0
AC 70 1.1 Bus number 0 - 255 Station number 1 - 80 Module position 0 - 12, Subposition
and higher (AF 100) (AF 100) + not relevant 0
If connected If connected 100 * substation 100 - 112,
locally, without locally, without number ...,
routing: routing: 0 (for I/O stations) 700 - 712
0
AC 55 1.1 Bus number Station number Unit number 0-4 Subposition
not applicable - not applicable - not applicable -

NOTE
Addressing of AC 160 is typically the same as that of AC 110.
Addressing of AC 80 is typically the same as that of AC 70.

The list box shows also the module type and the date and time of the first error occurrence on
the module in the target and the type of the first error detected on the module.
List box rows of modules, for which you already called the Diagnose Module function, are
dimmed.

3BDS 100 595R401 4-417

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.15.2 Module List Window

In this window the Diagnostics program displays the list of all of the modules of an on-line
connected target or a subset of them.

Figure 4-261. Module List Window

Select a module here and start module diagnostics, no matter the module is error free.

Date, Time
Date and time when the data was read from the target.

Diagnose Module
Activate this button to open the Module Diagnostics window for the selected module.

List Modules
Set here a filter to select the modules by their type.
Wildcards ‘?’ (for one character) and ‘*’ (for a group of characters) are supported.
The list box part contains the predefined filters *, AI*, AO*, CI*, DI*, and DO*.
Activate the filter by pressing the ENTER key.

List Box
The modules are listed by their address.
The significance and ranges of target address for different node types see in Table 4-35.
The list box shows the module types, whether the module is active (in operation) or passive (not
in operation), and whether an error was detected in the module.
List box rows of modules, for which you already called the Diagnose Module function, are
dimmed.

4-418 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.15 Controls in Document Windows of Diagnostics

4.5.15.3 Module Diagnostics Window

In this window the Diagnostics program displays diagnostic data of a specific module of the
connected target (with or without errors).
The diagnostic aspects of modules are described by a model, where each module consists of one
or more instances of one or more (diagnostic) object types. For example, an I/O module may
consist of one instance of the “Device” object type to describe its common properties and of
several instances of the “Channel” object type to describe its channels.
The following picture shows the Module Diagnostics window for an AI620 module:

Figure 4-262. Module Diagnostics Window

Inspect and analyze errors occurred in the selected module.

Window Title
[address] identifies the module. See Table 4-35.

Date, Time
Date and time when the window was opened.

3BDS 100 595R401 4-419

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Module Type
The module type designation with revision index.

Module State
Shows the module state, like ready, not ready, operational, error, init.
The set of possible states is module specific.

Object Types
This list box shows all the object types available on the target, such as device (the module
itself), channels, data sets, parts of Multi Vendor Interface, and so on.
Select an object type here.

Instances with Errors

This drop-down list box contains the erroneous instances of the selected object type.
Select an instance here. The number of the selected instance is shown in three different forms
below the list box. The state of the selected instance is also shown.

NOTE
The instance number is internally handled as a two-byte word.
The tree forms facilitate its evaluation for different object types:

• Decimal form
This is the standard representation. For example, in case of an analog input
channel AIS620 the number 5 indicates the channel 5.
• Decimal form, bytewise
This form is useful, for example, in case of DSP, where the left byte indicates
the STATION terminal value and the right byte the IDENT terminal value of
the instance.
• Hexadecimal form
This form is useful, for example, in case of MVINODE and MVB, where
numbers less than 8000 (hexadecimal) indicate nodes and data blocks
belonging to MVI channel 1, numbers greater than 8000 (hexadecimal)
indicate nodes and data blocks belonging to MVI channel 2.

List Box
This list box contains all of the errors of the selected instance detected since the last deletion of
errors on the target in a form that depends on the complexity of the module.
The errors are listed in order of their occurrence (date and time) and are characterized by error
state, error message, and so on.

4-420 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.16 Menu Commands of Diagnostics

If you double-click on an item in the list box, the Diagnostics program shows additional
information useful for maintenance (for expert users only):

Figure 4-263. Module Diagnostics, Additional Information

4.5.16 Menu Commands of Diagnostics

4.5.17 File Menu of Diagnostics

4.5.17.1 File | Save As

Shortcut: CTRL+S
Use this diagnostic command to save the report or diagnosis in the active document window.
This command is a simple alternative to File | Log.

Figure 4-264. Save Report/Diagnosis As

3BDS 100 595R401 4-421

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Save in (Directory)
The symbol shows the directory currently browsed for files.
Default is the \LIST subdirectory of the current node.
You can also select a subdirectory in the list box below.
Or go to the directory on the next higher level by clicking on the Up One Level icon.
Click on the Create New Folder icon to create a new subdirectory.

• Up One Level and Create New Folder (Icons)

Click on the Up One Level icon to go to the directory on the next higher level.
Click on the Create New Folder icon to create a new subdirectory.

• List and Details (Icons)

Click on these icons to display the files and subdirectories in corresponding forms.

• Files and Subdirectories

The list box contains all available files and subdirectories in the specified directory, which
correspond to the filter condition.
Click on the List and Details icons to display the files and subdirectories in corresponding
forms.

• File Name
Select a file name from the list box or type it here.
Or edit here a new filter condition, for example, MY*.DGN, and press ENTER to make it
effective.

• Save as Type
Select a filter condition from the standard filters in this drop-down list box.
If *.DGN is set, extension DGN (default extension of diagnosis files) will be appended to
the file name.

• Save
Activate this button to start saving the report or diagnosis in the specified file.
The Diagnostics program writes the report or diagnosis in an ASCII file.
This file contains the following:
• Title of the application window
• Title of the document window
• Content of the document window.
If the report or diagnosis contains list boxes they are saved as simple lists in the file.

4-422 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.17 File Menu of Diagnostics

4.5.17.2 File | Log

Shortcut: CTRL+L
Use this diagnostic command to log the report or diagnosis in the active document window into
a log file with automatic filename assignment.
To setup the log file, choose the File | Logfile Setup diagnostic command.
The LOG indicator in the Status Bar of the Diagnostics application window shows that the
report or diagnosis is already logged. If your data is already logged and you try to log it again,
the Diagnostics program asks you to append the data or to cancel unnecessary logging.
This command is an alternative to File | Save As.

4.5.17.3 File | Logfile Setup

Use this command to define the type of logging and the automatic filename assignment for the
log files generated by the File | Log diagnostic commands.

Figure 4-265. Setup Logfile

• Directory
Enter a directory where you want to store your log files. The default directory is the LIST
subdirectory of the node, for which you started Diagnostics.
The list box part of this combo box contains the recent directories.

• Logfile
Enter the name of the log file. Default is DIAGnn.LOG where nn starts at 01 and is
incremented by 1 if the file already exists in the current directory.
If you enter a filename which already exists, you are asked to delete the old one or to
append the data to the existing file.
The list box part of this combo box contains the recent log file names.

3BDS 100 595R401 4-423

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Log
Select one of the following possibilities of specifying the type of logging:

Table 4-36. Log Types

Type Description
None Disable log
Log Automatically from Automatic logging of all new errors (windows).
Now on Windows that were opened before are not logged.
Log Report/Diagnostics Log the report/diagnosis in the active window manually.
Manually Activate the File | Log diagnostic command to start
logging, or depress the corresponding toolbar button.

4.5.17.4 File | Print

Shortcut: CTRL+P
Use this diagnostic command to start printing a report or diagnostic data.

Figure 4-266. Print Diagnosis

NOTE
Do not mix up this command with the File | Print command of the Function
Chart Builder.

4-424 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.17 File Menu of Diagnostics

• Printer
This static text shows the selected printer.
Activate the Properties button to change the printer and printer connection.

• Print Range
Specify the pages you want to print:
All Prints the entire document.
Selection Prints the currently selected text.
Pages Prints the range of pages you specify in the From and To boxes.

• Properties
Activate this button to open the Properties dialog box and change the printer properties.
See the File | Print Setup command for dialog.

• Print to File
Select this check box if you want to store a print file instead of printing on the printer.

• Copies
Edit the number of copies you want to print for the defined page range.

• Collate Copies
Select this check box if you want to print document copies in page number order, instead
of separated multiple copies of each page.
Select this check box for proper sorting of pages in case of multiple copies.
You can follow the progress of printing or abort printing in the Printing dialog box.

3BDS 100 595R401 4-425

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.17.5 File | Print Setup

Use this diagnostic command to select a printer and a printer connection.

Figure 4-267. Print Setup of Diagnostics

NOTE
This command is very similar to the File | Print Setup command of the Function
Chart Builder.

• Printer
Select one of the current installed printers shown in the drop-down list box you want to
use. The static text shows status, type, and location of the selected printer.
You install printers and configure ports using the Settings | Printers command of
Windows NT.

• Properties
Activate this button to open the Properties dialog box and change the printer properties.

• Paper Size and Source

Select the size of paper that the document is to be printed on.
Some printers offer multiple trays for different paper sources. Specify the tray here.

• Orientation
Select Portrait or Landscape.

• Network…
Activate this button to connect to a printer at a network location.

4-426 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.18 View Menu of Diagnostics

4.5.17.6 File | Exit

Use this command to close any open windows of the Diagnostics program and leave it.

NOTE
Do not mix up this command with the File | Exit command of the Function Chart
Builder.

The non- reported erroneous instances of a reported module will be acknowledged.

You can also use the Control | Close command in the Application Control menu.

4.5.18 View Menu of Diagnostics

4.5.18.1 View | Toolbar

Toggle switch.
Use this command to display and hide the Toolbar of Diagnostics, which includes buttons for
some of the most common commands in Diagnostics, such as File | Log.

NOTE
Do not mix up this command with the View | Toolbar command of the Function
Chart Builder.

A check mark ‘ ’ appears next to the menu item when the Toolbar is displayed.
See Section 4.5.14.2, Controls in Toolbar of Diagnostics.

4.5.18.2 View | Status Bar

Toggle switch.
Use this command to display and hide the Status Bar of Diagnostics, which describes the action
to be executed by the selected Diagnostics menu item or toolbar button.

NOTE
Do not mix up this command with the View | Status Bar command of the
Function Chart Builder.

A check mark ‘ ’ appears next to the menu item when the Status Bar is displayed.
See Section 4.5.14.3, Indicators in Status Bar of Diagnostics.

3BDS 100 595R401 4-427

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.19 Target Menu of Diagnostics

4.5.19.1 Target | Report Errors

Use this command to open the Error Report window of the connected target.
See Section 4.5.15.1, Error Report Window.

4.5.19.2 Target | List Modules

Use this command to open the Module List window of the connected target.
In contrast to the Error Report, the Module List displays all modules, not only the ones with
detected errors.
See Section 4.5.15.2, Module List Window.
To specify a node type, such as AC 160, AC 110 2.1 and higher, AC 80, and AC 70 1.1 and
higher, fill the following dialog box.

Figure 4-268. List Modules of Station

See Table 4-35. If the connection is not routed, that is, the engineering station is connected
directly to the target, enter 0 both for Bus and Station.
In case of AC 55 1.1 no further specification is necessary.

4.5.19.3 Target | Diagnose Module

Use this command to open the Module Diagnostics window of the connected target.
The command refers to the selected module if the Error Report or Module List window is
open.

4-428 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.20 Window Menu of Diagnostics

Else select the AC 160, AC 110 2.1 and higher, AC 80, AC 70 1.1 and higher, or similar module
in the following dialog box:

Figure 4-269. Select Module, AC 110/70

For the address specification see Table 4-35.

Or select the AC 55 1.1 or similar module in the following dialog box:

Figure 4-270. Select Module, AC 55

Select a module (or unit) and activate the OK button. Then the diagnostic data is read from the
module and is displayed in the Module Diagnostics window.
See Section 4.5.15.3, Module Diagnostics Window.

4.5.19.4 Target | Delete Reported Errors *

Use this command to delete reported errors on the target and close the Error Report window.

4.5.20 Window Menu of Diagnostics

NOTE
Do not mix up this command with the File | Print command of the Function
Chart Builder.

3BDS 100 595R401 4-429

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.20.1 Window | Cascade

Use this command to arrange all open document windows of Diagnostics in a partly overlapping
fashion.

4.5.20.2 Window | Tile Horizontally

Use this command to arrange all open document windows of Diagnostics one above the other in
a non-overlapping fashion.

4.5.20.3 Window | Tile Vertically

Use this command to arrange all open document windows of Diagnostics side by side in a non-
overlapping fashion.

4.5.20.4 Window | Arrange Icons

Use this command to arrange the icons for minimized windows of Diagnostics at the bottom of
its application window.

NOTE
Some or all of the icons may be covered by open document windows in the
application window.

4.5.20.5 Window | Resize

Use this command to resize the active document window of Diagnostics to its default size.
It makes all texts and controls well visible without the need to scroll.

4.5.20.6 Window | 1, 2, … (Activate Diagnostics Windows)

Shortcut: ALT+number

,where number = 1, 2,… 9, 0 corresponds to the ordinal 1, 2,… 9, 10, which was assigned to this
window at its creation during the current Diagnostics session.
Use this command to activate the document window listed with number 1, 2,… at the bottom of
the Window menu. You can apply this command for the Error Report, Module List, and
Module Diagnostics windows.

4.5.21 Help Menu of Diagnostics

4.5.21.1 Help | Contents
Use this command to display the Help Topics window of Diagnostics Help.
Its Contents tab lists the available “how to”-type and reference information on the Diagnostics
program.
The information is hierarchically ordered.

4-430 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.22 Controls of Diagnosis

Click on the book symbols to open them and on help topic symbols to jump to final topics of
interest.
In the Diagnostics Help window you can click the Contents button whenever you want to
return to the Help Topics window.

4.5.21.2 Help | On Context

Shortcut: SHIFT+F1
Use this command to obtain context-specific help on the Diagnostics program.
The mouse pointer changes to an arrow and question mark.
Click to an element of the Diagnostics program windows, such as a command in a menu, a
toolbar button, or a dialog box.
The topic containing help information about this element will be shown in the Diagnostics Help
window.

4.5.21.3 Help | How to Use Help

Use this command for instructions about using on-line help.

4.5.21.4 Help | About Diagnostics

Use this command to display the copyright notice and version number of your copy of
Diagnostics program.

Figure 4-271. About Diagnostics

4.5.22 Controls of Diagnosis

NOTE
The Diagnostics program is adapted to the different diagnostics features of both
former and recent controller versions.
In case of AC 110 2.0, AC 70 1.0, and AC 55 1.0 it is called the Diagnosis
program.
In case of AC 100 Series targets of newer node types, such as AC 160, AC 110
2.1 and higher, AC 80, AC 70 1.1 and higher, and AC 55 1.1, it is called the
Diagnostics program.

3BDS 100 595R401 4-431

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.22.1 Controls in Title Bar of Diagnosis

The Diagnosis program has its own application window and several document windows, which
are identified by their title: Diagnosis, Module Diagnosis, and so on.
The title bar may contain the following elements:
• Application control menu button

• Document control menu button

• Title, that is, name of application or name of document

• Maximize button

• Minimize button

• Restore button

• Close button .

4.5.22.2 Controls in Toolbar of Diagnosis

Figure 4-272. Toolbar of Diagnosis

The Toolbar is displayed across the top of the application window, below the menu bar.
The Toolbar provides quick mouse access to many functions used in the Diagnosis program.
To hide or display the Toolbar of the Diagnosis window, choose the View | Toolbar diagnosis
command.
The following table lists the toolbar commands of Diagnosis:

Table 4-37. Icons and Commands in the Toolbar of Diagnosis

Icon Diagnosis Command Short Description

File | Save As Saves the report or diagnosis in the active document window.
File | Log Logs the report or diagnosis in the active document window
into a log file.
File | Print Print a report or diagnosis data.

4-432 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.22 Controls of Diagnosis

Table 4-37. Icons and Commands in the Toolbar of Diagnosis

Icon Diagnosis Command Short Description

View | Status Report Shows Status Report of connected target.
View | Error Report Shows Error Report of connected target.
View | Module List Shows Module List of connected target.
View | Module Diagnosis Shows Module Diagnosis.
View | Channel Diagnosis Shows Channel Diagnosis.
Help | Contents Opens the Diagnosis Help window and displays the contents of
the on-line help.
Help | On Context Changes the mouse pointer to an arrow and question mark to
get context-specific help on Diagnosis.

4.5.22.3 Indicators in Status Bar of Diagnosis

Figure 4-273. Status Bar of Diagnosis

The Status Bar is displayed at the bottom of the application window. To display or hide the
Status Bar of the Diagnosis window, use the View | Status Bar diagnosis command.
The left area of the status bar describes actions of menu items as you use the arrow keys to
navigate through menus. This area similarly shows messages that describe the actions of toolbar
buttons as you depress them, before releasing them. If after viewing the description of the
toolbar button command you wish not to execute the command, then release the mouse button
while the pointer is off the toolbar button.
The right areas of the Status Bar display the following information:.
Table 4-38. Indicators in the Status Bar of Diagnosis

Indicator Description
COMx/X3 Selected port for communication with the AC 100 Series
target: COM1 to COM4, X3.
[net,node|bus,station] Selected net, node, bus, and station number.
* Indicates that some module or channel diagnosis data are
buffered in the Advant Station 100 Series Engineering Station.
LOG Indicates that the report in the active window is already logged
in a log file using the File | Log and File | Logfile Setup
diagnosis commands.

3BDS 100 595R401 4-433

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.23 Controls in Document Windows of Diagnosis

4.5.23.1 Status Report Window of Diagnosis
In this window the Diagnosis program displays the status of the node and the application
program as defined in the RAM and the PROM of the on-line connected target:

Figure 4-274. Status Report Window of Diagnosis

Compare the data.

The node and the application program are identified in the following form:
name bus,station DB_time_stamp PCPGM_number PC_time_stamp

Date, Time
Date and time when the data was read from the target.

Target
This column concerns the actual application program in the RAM of the target.

Differences
The “not equal” sign ‘<>’ points out the differences between the columns Target and PROM.

4-434 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.23 Controls in Document Windows of Diagnosis

PROM
This column concerns the actual application program in the PROM of the target.

Name
The name of the node.

Bus, Station
The target address (bus, station) in the target RAM and PROM.

DB Section Version
The time stamp of the database (DB) in the target RAM and PROM.

PCPGM Number
The number of the process control (PC) or application program.

PC Section Version
The time stamp of the PC (process control) section in the target RAM and PROM.

PCPGM State
The state of the application program or process control (PC) program Blocked or Deblocked.

Free Memory
Free space in the RAM of the target.

No errors detected / Errors detected

The static text version reflects whether some errors were recently detected in the on-line
connected target or not.
If errors are detected, the Error Report button is enabled, else it is disabled and dimmed.

Error Report
Activate this button to open the Error Report.
The button is only active if errors have been detected.

Module List
Activate this button to open the Module List.

3BDS 100 595R401 4-435

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.23.2 Error Report Window

In this window the Diagnosis program displays error reports for selected modules of the on-line
connected target.

Figure 4-275. Error Report Window of Diagnosis

Inspect errors occurred in selected modules.

NOTE
Do not close the Error Report window unless you are sure you do not need the
information contained in it any more.

Date, Time
Date and time when the data was read from the target.

List Modules (Type)

Set here a filter to select the modules by their type.
Wildcards ‘?’ (for one character) and ‘*’ (for a group of characters) are supported.
The list box part contains the predefined filters *, AI*, AO*, CI*, DI*, and DO*.
Activate the filter by pressing the ENTER key.

List Modules (State)

Set here a filter to select the modules by their state (in addition to the type filter).

4-436 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.23 Controls in Document Windows of Diagnosis

Select one of the following state filters:

Table 4-39. Error Report State Filters

Module State Filter Function

Any State List modules in any state
Active State ’A’ List modules in active state, only
Passive State ’P’ List modules in passive state only
System Errors ’S’ List modules with system errors
Module Errors ’A’ List modules with module errors
Process Errors ’P’ List modules with process errors
Reported Diagnosis ’*’ List modules with already reported diagnosis data
Without Errors List modules without errors

Module Diagnosis
Activate this button to open the Module Diagnosis window for the selected module (position).

Pos.
The module is defined by the address for different targets as shown in the following table:

Table 4-40. Significance and Ranges of Target Address

Significance of 1st Range of Significance of Ranges of

Target
Address Part 1st Address Part 2nd Address Part 2nd Address Part
AC 110 2.0 Station number; 0-7 Module position 1 - 20;
in fact: substation number for subcarrier module in
within an AC 110 station. subposition 1: 101 - 120;
Do not mix up with station
for subcarrier module in
number within an AF 100
subposition 2: 201 - 220
network!
AC 70 1.0 Station number 0 Module position 0 - 12
AC 55 1.0 Unit number 0-4 Not relevant (0)

Module
The module type designation.

3BDS 100 595R401 4-437

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

State
State of the module:
A Active (in operation)
P Passive (not in operation).

Errors
List of errors marked by the following flags:
S System Errors
M Module Errors
P Process Errors.
Already read, that is, reported and buffered, errors are marked with an ‘*’.

Date, Time
Date and time of the first error on the module in the target.

Error Text
Error text for the first error on the module.

4.5.23.3 Module List Window

In this window the Diagnosis program displays the list with selected modules of the on-line
connected target.

Figure 4-276. Module List Window of Diagnosis

Select a module here and start module diagnosis, no matter the module is error free.

4-438 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.23 Controls in Document Windows of Diagnosis

Date, Time
Date and time when the data was read from the target.

Module Diagnosis
Activate this button to open the Module Diagnosis window for the selected module.

List Modules (Type)

Set here a filter to select the modules by their type.
Wildcards ‘?’ (for one character) and ‘*’ (for a group of characters) are supported.
The list box part contains the predefined filters *, AI*, AO*, CI*, DI*, and DO*.
Activate the filter by pressing the ENTER key.

List Modules (State)

Set here a filter to select the modules by their state (in addition to the type filter).
Select one of the following state filters:

Table 4-41. List Modules State Filters

Module State Filter Function

Any State List modules in any state
Active State 'A' List modules in active state, only
Passive State 'P' List modules in passive state only
System Errors 'S' List modules with system errors
Module Errors 'A' List modules with module errors
Process Errors 'P' List modules with process errors
Reported Diagnosis '*' List modules with already reported diagnosis data
Without Errors List modules without errors

Pos.
The module is defined by the address for different targets as shown in Table 4-40.

Module
The module type designation.

State
State of the module:
A Active (in operation)
P Passive (not in operation).

3BDS 100 595R401 4-439

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Errors
List of errors marked by the following flags:
S System Errors
M Module Errors
P Process Errors.
Already read, that is, reported and buffered, errors are marked with an ‘*’.

4.5.23.4 Module Diagnosis Window

In this window the Diagnosis program displays diagnostic data of a specific module of the
connected target (with or without errors).
The diagnostic data in the Module Diagnosis window depend on the module class.
Some controls and fields are dimmed in case of simple, class 1 modules.
Class 2 and 3 modules are more complex, they have channels, which can be configured.
Therefore more information can be displayed and channel diagnosis is possible.
The following picture shows the Module Diagnosis window with contents for a class 2 or 3
module:

Figure 4-277. Module Diagnosis Window of Diagnosis

Inspect and analyze errors occurred in the selected module.

4-440 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.23 Controls in Document Windows of Diagnosis

Window Title
[station, module position] identify the module by its address.

Date, Time
Date and time when the data was read from the target.

Module Type
The module type designation with revision index.

Module Status
The module status word is displayed as a 16-bit pattern.
The 7 first bits (on the right) are essential for diagnosis:

Table 4-42. Module Status Bits in Module Diagnosis

Bit Number Bit Name Description

0 CL1 Class 1 module
1 PSV Module is in passive state
2 DPL Default parameters loaded
3 SPE Sum process error
4 SME Sum module error
5 SSE Sum system error
6 SSB Standby sub-state

If the bit is set to 1, the condition is fulfilled.

For example, if the SPE bit is set to 1, at least one process error exists.

Diag. Counter
The diagnostics counter is currently not supported.
Indicates an error during bus transfer.

3BDS 100 595R401 4-441

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Module State
The module may have one of the following states:

Table 4-43. Module States

State State Name Description

0 Not ready The module is not configured.
1 Ready The module is parametrized and waits for being set
into operational state by the system CPU command.
2 Operational The module is fully configured and operational
(it is active).
3 Error The module is in an error state, diagnosis may be
necessary.
4 Init In this module state the parameters are checked,
some diagnosis is possible.
This state always leads to one of the other states.

System Errors, Module Errors, Process Errors

Each error type is divided into 32 bits. If a bit is set to 1 it indicates an error.
If you select an error bit 1 using the mouse, the corresponding error message in the Error
Messages list box is highlighted, too.

Channel Diagnosis
Activate this button to open the Channel Diagnosis window for the selected channel instance in
the Instances with Errors list box.

Channel Type
The channel or object type is identified by its number.
See Table 4-44 for channel types.
See the following table for channel types:

Table 4-44. Channel Types in Module Diagnosis

Channel Type Description

0 The module itself
1 Firmware FPROM on module
2 I/O diagnosis
3 CPU

4-442 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.23 Controls in Document Windows of Diagnosis

Table 4-44. Channel Types in Module Diagnosis (Continued)

Channel Type Description

4 Station
11 Hardware subsystem channel of PM63x or CT48x
12 Operating subsystem channel of PM63x or CT48x
13 Communication subsystem channel of PM63x or CT48x
32 Digital Input channel
33 Digital Input supervision
34 Digital Output channel
35 Analog Input channel
36 Analog Input limits
37 Analog Output channel
38 Analog Input register
39 Analog Output register
40 High Speed Counter (Pulse Counter)
50 Bus extender
51 Data Set (DS) on CI625
52 MasterFieldbus master
53 Data Set Peripheral (DSP) on CI626
54 Multi Vendor Interface Channel (MVICHAN)
55 Multi Vendor Interface Node (MVINODE)
56 Multi Vendor Interface Data Block (MVB)
57 MasterFieldbus slave
59 Event Handler on DI65x

Total
The total number of channels (instances) per type.

Erroneous
The number of erroneous channels (instances).

3BDS 100 595R401 4-443

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Instances with Errors

In this list box all the erroneous instances of the channel type are displayed. Instances marked
with ‘*’ have already been reported and buffered.
For detailed information about an instance and to open the Channel Diagnosis window, select
the instance here and activate the Channel Diagnosis button, or double-click on the instance.

Error Messages
The error text of system, module, or process errors.
Each line corresponds to one of the 3*32=96 error bits, which indicate an error if it equals to 1.
The error messages are module dependent.
If you select an error message in the list box, the corresponding error bit of System Errors,
Module Errors, or Process Errors is highlighted, too.

4.5.23.5 Channel Diagnosis Window

In this window the Diagnosis program displays diagnostic data of a specific channel (instance)
selected in the Module Diagnosis window.

Figure 4-278. Channel Diagnosis Window of Diagnosis

Inspect and analyze errors occurred in the selected channel (instance).

Window Title
[station, module position | channel type, instance] identify the channel by its address, type, and
instance (number). See Table 4-44 for channel types.

Date, Time
Date and time when the data was read from the target.

4-444 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.23 Controls in Document Windows of Diagnosis

Channel
The channel instance (number), also displayed in the window title together with the channel
type. The channel instance (number) is internally handled as a two-byte word.
To facilitate its evaluation for different channel types, it is displayed in the following forms:
• Decimal form
This is the standard representation. For example, in case of an analog input channel
AIS620 (channel type 36) the number 5 indicates the channel 5.
• Hexadecimal form
This form is useful, for example, in case of MVINODE and MVB (channel types 55 and
56), where numbers less than 8000 (hexadecimal) indicate nodes and data blocks
belonging to MVI channel 1, numbers greater than 8000 (hexadecimal) indicate nodes and
data blocks belonging to MVI channel 2.
• Decimal form, bytewise
This form is useful, for example, in the following cases:
– MVINODE (channel type 55),
where the right byte indicates the node number.
– DSP (channel type 53),
where the left byte indicates the STATION terminal value and
the right byte the IDENT terminal value of the instance.

Module Type
The module type designation and revision index.

Module Status
The module status word is displayed as a 16-bit pattern.
The 7 first bits (on the right) are essential for diagnosis:

Table 4-45. Module Status Bits in Channel Diagnosis

Bit Number Bit Name Description

0 CL1 Class 1 module
1 PSV Module is in passive state
2 DPL Default parameters loaded
3 SPE Sum process error
4 SME Sum module error
5 SSE Sum system error
6 SSB Standby sub-state

If the bit is set to 1, the condition is fulfilled.

For example, if the SPE bit is set to 1, at least one process error exists.

3BDS 100 595R401 4-445

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Diag. Counter
The diagnostics counter is currently not supported.
Indicates an error during bus transfer.

Channel State
The interpretation of channel states depends on the module type.
Channel states for most of the standard modules, for example, AI, AO, DI, DO, DP:

Table 4-46. Channel States for Most Standard Modules

Channel State Designation Comment

0 Active Configured and running
1 Passive Not configured or not activated (ACT=0)

Channel states for MasterFieldbus Master CI671, MasterFieldbus Slave CI670:

Table 4-47. Channel States for MasterFieldbus Master and Slave

Channel State Designation Comment

0 Passive Not configured
1 Active Configured and running and receiving
2 Not receiving Active and not receiving (no communication
between master and slave)
3 Not sending Active and not sending (no communication
between master and slave)

Channel states for Data Set CI626:

Table 4-48. Channel States for Data Set CI626

Channel State Designation Comment

0 Deleted Not configured (initial state)
1 Active Configured and activated and data received
2 Passive Configured and not activated (due to an error)
3 Ready Configured, not yet been activated
4 Configuration Channel configuration is running.
running
5 Configured Configured but no data received
6 Configuration Error Wrong configuration parameters

4-446 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.24 Menu Commands of Diagnosis

System Errors, Channel Errors, Process Errors

Each error type is divided into 32 bits. If a bit is set to 1 it indicates an error.
If you select an error bit 1 using the mouse, the corresponding error message in the Error
Messages list box is highlighted, too.

Error Messages
The error text of system, module, or process errors.
Each line corresponds to one of the 3*32=96 error bits, which indicate an error if it equals to 1.
The error messages are module dependent.
If you select an error message in the list box, the corresponding error bit of System Errors,
Channel Errors, or Process Errors is highlighted, too.

4.5.23.6 Output Window of Diagnosis

The Diagnosis program opens this window if you choose the File | Save As or the File | Print
command. The saved or printed diagnostic data is displayed also here for inspection.

Figure 4-279. Output Window of Diagnosis

4.5.24 Menu Commands of Diagnosis

4.5.25 File Menu of Diagnosis

4.5.25.1 File | Save As

Shortcut: CTRL+S
Use this diagnosis command to save the report or diagnosis in the active document window.
This command is a simple alternative to File | Log.

3BDS 100 595R401 4-447

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Figure 4-280. Save Report/Diagnosis As

• Save in (Directory)
The symbol shows the directory currently browsed for files.
Default is the \LIST subdirectory of the current node.
You can also select a subdirectory in the list box below.
Or go to the directory on the next higher level by clicking on the Up One Level icon.
Click on the Create New Folder icon to create a new subdirectory.

• Up One Level and Create New Folder (Icons)

Click on the Up One Level icon to go to the directory on the next higher level.
Click on the Create New Folder icon to create a new subdirectory.

• List and Details (Icons)

Click on these icons to display the files and subdirectories in corresponding forms.

• Files and Subdirectories

The list box contains all available files and subdirectories in the specified directory, which
correspond to the filter condition. Click on the List and Details icons to display the files
and subdirectories in corresponding forms.

• File Name
Select a file name from the list box or type it here. Or edit here a new filter condition, for
example, MY*.DGN, and press ENTER to make it effective.

• Save as Type
Select a filter condition from the standard filters in this drop-down list box.
If *.DGN is set, DGN (default extension of diagnosis files) will be appended to file name.

• Save
Activate this button to start saving the report or diagnosis in the specified file.

4-448 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.25 File Menu of Diagnosis

The Diagnosis program writes the report or diagnosis in a text file containing title of the
application window, title of the document window, and content of the document window.
If the report or diagnosis contains list boxes, they are saved as simple lists in the file.

4.5.25.2 File | Log

Shortcut: CTRL+L
Use this diagnosis command to log the report or diagnosis in the active document window into a
log file with automatic filename assignment.
To setup the log file, choose the File | Logfile Setup diagnosis command.
The LOG indicator in the Status Bar of the Diagnosis application window shows that the report
or diagnosis is already logged. If your data is already logged and you try to log it again,
the Diagnosis program asks you to append the data or to cancel unnecessary logging.
This command is an alternative to File | Save As.

4.5.25.3 File | Logfile Setup

Use this command to define the type of logging and the automatic filename assignment for the
log files generated by the File | Log diagnosis commands.

Figure 4-281. Setup Logfile

• Directory
Enter a directory where you want to store your log files. The default directory is the LIST
subdirectory of the node, for which you started Diagnosis.
The list box part of this combo box contains the recent directories.

• Logfile
Enter the name of the log file. Default is DIAGnn.LOG where nn starts at 01 and is
incremented by 1 if the file already exists in the current directory.
If you enter a filename which already exists, you are asked to delete the old one or to
append the data to the existing file.
The list box part of this combo box contains the recent log file names.

3BDS 100 595R401 4-449

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

• Log
Select one of the following possibilities of specifying the type of logging:

Table 4-49. Log Types

Type Description
None Disable log
All Reported Errors Automatic logging of all new errors (windows).
Windows that were opened before are not logged.
Report/Diagnosis in Log the report/diagnosis in the active window manually.
Active Window Activate the File | Log diagnosis command to start
logging, or depress the corresponding toolbar button.

4.5.25.4 File | Print

Shortcut: CTRL+P
Use this diagnosis command to start printing a report or diagnosis data.

Figure 4-282. Print Diagnosis

NOTE
Do not mix up this command with File | Print of Function Chart Builder.

• Printer
This static text shows the selected printer.
Activate the Properties button to change the printer and printer connection.

4-450 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.25 File Menu of Diagnosis

• Print Range
Specify the pages you want to print:
All Prints the entire document.
Selection Prints the currently selected text.
Pages Prints the range of pages you specify in the From and To boxes.

• Properties
Activate this button to open the Properties dialog box and change the printer properties.
See the File | Print Setup command for dialog.

• Print to File
Select this check box if you want to store a print file instead of printing on the printer.

• Copies
Edit the number of copies you want to print for the defined page range.

• Collate Copies
Select this check box if you want to print document copies in page number order, instead
of separated multiple copies of each page.
Select this check box for proper sorting of pages in case of multiple copies.
You can follow the progress of printing or abort printing in the Printing dialog box.

4.5.25.5 File | Print Setup

Use this diagnosis command to select a printer and a printer connection.

Figure 4-283. Print Setup of Diagnostics

3BDS 100 595R401 4-451

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

NOTE
This command is very similar to the File | Print Setup of Function Chart Builder.

• Printer
Select one of the current installed printers shown in the drop-down list box you want to
use.
The static text shows status, type, and location of the selected printer.
You install printers and configure ports using the Settings | Printers command of
Windows NT.

• Properties
Activate this button to open the Properties dialog box and change the printer properties.

• Paper Size and Source

Select the size of paper that the document is to be printed on.
Some printers offer multiple trays for different paper sources. Specify the tray here.

• Orientation
Select Portrait or Landscape.

• Network…
Activate this button to connect to a printer at a network location.

4.5.25.6 File | Exit

Use this command to close any open windows of the Diagnosis program and leave it.

NOTE
Do not mix up this command with the File | Exit command of the Function Chart
Builder.

The non- reported erroneous instances of a reported module will be acknowledged.

Related command:
You can also use the Control | Close command in the Application Control menu.

4-452 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.26 Edit Menu of Diagnosis

4.5.26 Edit Menu of Diagnosis

4.5.26.1 Edit | Copy

Shortcut: CTRL+C
Use this command to copy the contents of the active document window into the clipboard.

NOTE
Do not mix up this command with the Edit | Copy command of the Function
Chart Builder.

The window contents are copied as text to the clipboard.

List boxes are copied as simple lists containing only text.
You can paste the clipboard contents to a file in a text editor, then save or print the file.
Copying data to the clipboard replaces the contents previously stored there.

4.5.27 View Menu of Diagnosis

4.5.27.1 View | Status Report

Use this command either to read the data from the connected target or to activate the already
open Status Report window of Diagnosis.
See Section 4.5.23.1, Status Report Window of Diagnosis.

4.5.27.2 View | Error Report

Use this command to view the Error Report of the connected target. The Error Report
window lists max. 8*20=160 erroneous modules (station 0 - 7, module position 1 - 20).
See Section 4.5.23.2, Error Report Window.

4.5.27.3 View | Module List

Use this command to display the Module List to select a module for diagnosis. In contrast to
the Error Report, the Module List displays all modules, not only the erroneous ones.
See Section 4.5.23.3, Module List Window.

4.5.27.4 View | Module Diagnosis

Use this command to select a module for module diagnosis.
The command is active if the Error Report or Module List window is open.

3BDS 100 595R401 4-453

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Select the module in the following dialog box:

Figure 4-284. Select Module

Already reported diagnosis data are marked by ‘*’.

• Position
Edit any (valid) module position in form of station, module_position or select one in the
Pos., Module, State, Errors list box.

• Pos.
The module is defined by the address for different targets as shown in Table 4-40.

• Module
The module type designation.

• State
State of the module:
A Active (in operation)
P Passive (not in operation).

• Errors
List of errors marked by the following flags:
S System Errors
M Module Errors
P Process Errors

4-454 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.27 View Menu of Diagnosis

• List Modules Filter

Set here a filter to select the modules by their type.
Wildcards ‘?’ (for one character) and ‘*’ (for a group of characters) are supported.
The list box part contains the predefined filters *, AI*, AO*, CI*, DI*, and DO*.
Activate the filter by pressing the ENTER key.

• List Modules
Set here a filter to select the modules by their state (in addition to the type filter).
Select one of the following states:
Table 4-50. List Modules State

Module State Function

Any State List modules in any state
Active State ’A’ List modules in active state, only
Passive State ’P’ List modules in passive state only
System Errors ’S’ List modules with system errors
Module Errors ’A’ List modules with module errors
Process Errors ’P’ List modules with process errors
Reported Diagnosis ’*’ List modules with already reported diagnosis data
Without Errors List modules without errors

Activate the OK button after having made all selections. Then the new diagnosis data is read
from the module or the already reported and buffered data is displayed in the Module Diagnosis
window.
See Section 4.5.23.4, Module Diagnosis Window.

4.5.27.5 View | Channel Diagnosis

Use this command to select a channel for channel diagnosis.
The command is active if the Module Diagnosis window is open, that is, a module has already
been selected.

3BDS 100 595R401 4-455

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

Select the channel in the following dialog box:

Figure 4-285. Select Channel

Already reported diagnosis data are marked by ‘*’.

• Module
The module which has been selected in the Module Diagnosis window.

• Channel
Edit a (valid) channel in form of type, instance or select one in the Type, Number, Errors
list box.

• Type and Number

Channel type and number (instance) of the channel.
See Table 4-44 for channel types.

• Errors
Erroneous channels are by the flag ‘E’.

• List Channels
Set here a filter to list only a group of channels in the Type, Number, Errors list box.

4-456 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.27 View Menu of Diagnosis

Select one of the following filters:

Table 4-51. List Channels Options

List Channels Option Description

With errors only List erroneous channels only
Reported '*' with errors List already reported erroneous channels
Reported '*' diagnosis List already reported channels
All channels List all channels

Activate the OK button after having made all selections. Then the new diagnosis data is read
from the module or the already reported and buffered data is displayed in the Channel
Diagnosis window.
See Section 4.5.23.5, Channel Diagnosis Window.

4.5.27.6 View | Toolbar

Toggle switch.
Use this command to display and hide the Toolbar of Diagnosis, which includes buttons for
some of the most common commands in Diagnosis, such as File | Log.

NOTE
Do not mix up this command with the View | Toolbar command of the Function
Chart Builder.

A check mark ‘ ’ appears next to the menu item when the Toolbar is displayed.
See Section 4.5.22.2, Controls in Toolbar of Diagnosis.

4.5.27.7 View | Status Bar

Toggle switch.
Use this command to display and hide the Status Bar of Diagnosis, which describes the action
to be executed by the selected Diagnosis menu item or toolbar button.

NOTE
Do not mix up this command with the View | Status Bar command of the
Function Chart Builder.

A check mark ‘ ’ appears next to the menu item when the Status Bar is displayed.
See Section 4.5.22.3, Indicators in Status Bar of Diagnosis.

3BDS 100 595R401 4-457

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.28 Target Menu of Diagnosis

4.5.28.1 Target | Delete Reported Errors *

Use this command to delete reported errors and diagnosis data marked with ‘*’.
The Diagnosis program displays the following warning message:

Figure 4-286. Diagnosis, Warning Before Deleting Errors

The Diagnosis program displays another warning message if there are non- reported erroneous
instances (channels) of a reported module, showing the module type designation with its
address:

Figure 4-287. Diagnosis, Warning Due to Non- reported Errors

Answer Yes if you want to acknowledge the channels of the corresponding modules, that is,
reset the error buffer.
Answer No if you want to read the channel diagnosis, first.

4.5.28.2 Target | Delete All Reported Errors

Use this command to delete all reported errors, even if you have not yet read them.
The Diagnosis program displays the following warning message:

4-458 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 4.5.29 Window Menu of Diagnosis

Figure 4-288. Diagnosis, Delete All Errors, Warning

• Pos., Module, etc. List (All Reported Errors List)

This list shows all errors you are going to delete.
The errors are listed by module position and sub-position, module type designation,
module state, error type, date and time of occurrence, and corresponding error text.
Answer Yes if you want to reset all error buffers and to close all document windows, except for
the Status Report window. Answer No if you do not want to delete the listed errors.

4.5.29 Window Menu of Diagnosis

NOTE
Do not mix up these commands with the Windows | … commands of the
Function Chart Builder.

4.5.29.1 Window | Cascade

Use this command to arrange all open document windows of Diagnosis in a partly overlapping
fashion.

4.5.29.2 Window | Tile Horizontally

Use this command to arrange all open document windows of Diagnosis one above the other in a
non-overlapping fashion.

4.5.29.3 Window | Tile Vertically

Use this command to arrange all open document windows of Diagnosis side by side in a non-
overlapping fashion.

4.5.29.4 Window | Arrange Icons

Use this command to arrange the icons for minimized windows of Diagnosis at the bottom of its
application window.
NOTE
Some or all of the icons may be covered by open document windows in the
application window.

3BDS 100 595R401 4-459

Function Chart Builder User’s Guide
Chapter 4, Runtime Operation

4.5.29.5 Window | Resize

Use this command to resize the active document window of Diagnosis to its default size.
It makes all texts and controls well visible without the need to scroll.

4.5.29.6 Window | Close All Diagnosis

Use this command to close all Module Diagnosis and Channel Diagnosis windows.
The Diagnosis program closes them without any warning message.
No data is lost because the data buffers store the already reported diagnosis data.

4.5.30 Help Menu of Diagnosis

4.5.30.1 Help | Contents
Use this command to display the Help Topics window of Diagnosis Help.
Its Contents tab lists the available “how to”-type and reference information on the Diagnosis
program. The information is hierarchically ordered.
Click on the book symbols to open them and on help topic symbols to jump to final topics of
interest.
In the Diagnosis Help window you can click the Contents button whenever you want to return
to the Help Topics window.

4.5.30.2 Help | On Context

Shortcut: SHIFT+F1
Use this command to obtain context-specific help on the Diagnosis program.
The mouse pointer changes to an arrow and question mark.
Click to an element of the Diagnosis program windows, such as a command in a menu, a toolbar
button, or a dialog box.
The topic containing help information about this element will be shown in the Diagnosis Help
window.

4.5.30.3 Help | How to Use Help

Use this command for instructions about using on-line help.

4.5.30.4 Help | About Diagnosis

Use this command to display the copyright notice and version number of your copy of
Diagnosis program.

Figure 4-289. About Diagnosis

4-460 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 5.1 Preventive Maintenance

Chapter 5 Maintenance

5.1 Preventive Maintenance

It is a good practice to save and backup data:
• Save your work from time to time during a Function Chart Builder session by using the
File | Save command.
• Backup your source files and all other involved files in due time. Use the File | Copy
commands of the Application Builder, possibly also some packing utility, and save them to
a second device, for example, to diskettes.

5.2 Error Messages

The error messages of the Function Chart Builder appear in dialog boxes containing
• The title Function Chart Builder
• An error message identifier, for example, #12291
• An icon reflecting the severity of the message, for example, a stop sign
• Concise statement of the problem
• A hint to circumvent the problem
• OK button to close the dialog box.
Follow the hint.
In case of error messages of other programs than the Function Chart Builder, consult their
documentation.

5.3 Fault Finding and User Repair

5.3.1 Reporting Problems

If you encounter a problem you cannot solve by reading this manual or the related Advant or
Master documents, contact your ABB distributor or ABB service for Advant and Master
problems.

CAUTION
IF A PROBLEM OCCURS WITH THE FUNCTION CHART BUILDER,
DOCUMENT IT THOROUGHLY BEFORE YOU DO ANYTHING ELSE!

To understand and solve the problem, the exact situation that caused it must be reproduced.

3BDS 100 595R401 5-1

Function Chart Builder User’s Guide
Chapter 5 Maintenance

You have to save all the data pertaining to the problem:

• Data describing the hardware of your engineering station
• Data describing the operating system and the software environment
• Data describing your Advant Engineering components and their settings
• Your project data and libraries.
The data files that are relevant for reporting problems and their generation procedure are listed
for Windows NT in the following tables. The procedures are similar for Windows 2000.

Table 5-1. File Describing Windows NT Environment

Files Description Comment, Generation Procedure

MSDRPT.TXT Describes the hardware and Generate it by the WinMSD program:
system software of your 1. Choose Run from the Start menu.
engineering station.
2. Enter WINMSD and activate the OK button in the
Lists the values of system
Run dialog box.
and user environment
variables. 3. Activate the Print button in the Windows NT Diagnostics
Contains the OS version. dialog box.
4. Select the All tabs, Summary, and File options and activate
the OK button in the Create Report dialog box.
5. Select a directory for the report file MSDRPT.TXT and
activate the Save button in the Save WinMSD Report
dialog.

Table 5-2. Advant Engineering and Project Files for Reporting Problems

Files Description Comment, Generation Procedure

C:\Advabldenv\*.INI Initialization files of Advant C:\Advabldenv may be re-defined by the environment
Engineering product variable ADVABLDENV.
components
project_root\ Project files (node, node You can use the File | New Project and File | Copy
current_project\*.* structure, circuit, and type commands of the Application Builder to copy them.
and all files in all circuit source code, If necessary, derive project_root\current_project from the
subdirectories internal data ObjectDir value in the [Recentfcb_version] section of FCB.INI.
representations, etc.)
To read FCB.INI use AS100-EDIT or some simple editor.)
C:\TCLEV1\*.*, Level1 and level2 type These directories might have been redefined by environment
C:\TCLEV\*.*2 circuit libraries variables TC$LEV1 and TC$LEV2.
C:\PB_LIB\*.* User-defined PROFIBUS This directory might have been redefined by DOS
DB element libraries environment variable PB$LIB.

5-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section 5.3.2 What to Do at Program Halts

Table 5-2. Advant Engineering and Project Files for Reporting Problems

Files Description Comment, Generation Procedure

C:\PC_LIB\*.* Additional PC element This directory might have been redefined by DOS
libraries environment variable PC$LIB.
C:\ADVABNT\FCB\ Target description files Necessary if additional node types and options are used.
release_*\BIN32\*.TEL C:\ADVABNT\FCB\release_*\BIN32 may be re-defined in
C:\Advabldenv\product.INI.

You can copy the data files to diskettes, for example, by the Explorer of Windows, or you send
them directly by electronic mail.
Write down as much as you can remember about how the problem occurred.
Contact your ABB distributor or ABB service and send the files and the problem report.

5.3.2 What to Do at Program Halts

The Function Chart Builder tries to cope with program crashes, prevent them and diminish their
consequences. Program halts and crashes cannot be completely avoided due to the following
factors:
• Windows error conditions may occur if a file cannot be opened, if the printer is not
connected, if there is no more available space on the hard disk, or if there is no more
memory available, and so on.
• Function Chart Builder halt conditions may occur if you try to work with inconsistent or
corrupted project data or internal data representations.
When the Function Chart Builder has halted or crashed, perform the following steps:
1. Try to exit the Function Chart Builder by quitting the error message by pressing ENTER or
SPACE, and by using File | Exit commands.

2. If Step 1 does not work, try to restart the engineering station by pressing the CTRL, ALT, and
DEL keys at the same time. That should reboot your engineering station.

3. If Step 2 does not work, switch off the engineering station and, after 20 seconds, switch it
on to reset and reboot it.
Contact your ABB distributor or ABB service if an error occurs, which is not simple to correct
(for example, by connecting the missing printer), and where you need Steps 2 or 3 to exit.

CAUTION
BEFORE YOU DO ANYTHING ELSE, GATHER THE INFORMATION
LISTED IN Section 5.3.1, Reporting Problems.

ABB needs this information to fix the problem as soon as possible.

If you use a PC of yours as engineering station, check whether your PC hardware and software
fulfill the requirements of the Function Chart Builder before you start working again with the
Function Chart Builder. See the Application Builder User’s Guide and Section 2.2.2,
Compatibility of Software and Source Code.

3BDS 100 595R401 5-3

Function Chart Builder User’s Guide
Chapter 5 Maintenance

5-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section A.1 FCB Directory Structure

Appendix A Function Chart Builder Files

A.1 FCB Directory Structure

A.1.1 Release Directory Structure

C:\Advabldenv
apb.ini, fcb.ini,
product.ini,
foot001.tpx,
abblogo.wmf, etc.

drive:\AdvaBNT FCB release_* BIN32 DB_LIB SOURCE

*.pdf *.exe,*.dll, *.dcl,*.del, *.mdb
*.abu function.ini, *.stl
*.isu *.cnt,*.hlp, PC_LIB
*.bax,*.lis, *.pcl,*.pel,
*.log,*.met, *.ptl
*.tcd,*.tel, etc.
SRC_LIB
*.ba_,*.de_,*.pe_,
C:\Program Files Common Files AdvaBld Shared *.st_,*.tc_,*.te_
*.exe,*.dll,
*.hlp,
*.lo, etc.

C:\Windows System32
*.dll, etc.

Figure A-1. FCB Release Directory Structure

3BDS 100 595R401 A-1

Function Chart Builder User’s Guide
Appendix AFunction Chart Builder Files

A.1.2 Project Directory Structure

CIDATA
PC_LIB *.bax, *.cis, *.ini, *.l??,
*.odb, *.wex, *.wsp, *.w??
PR_CI LIST
*.db, *.dbt, *.dxr,*.lis,
NODES *.pc?,*.pxr, *.syl, *.uci
project1
circuits.dat, LIST
nodes.dat, PR_TC *.db, *.dbt, *.dxr,*.lis,
prjnotes.txt, *.pc?, *.pxr, *,nam
project_root project1.ini,
typecirc.dat, TCDATA
(e.g., C:\PROJ) *.bax, *.ini, *.l??, *.odb,
projroot.ini foot001.tpx
*.tcs, *.wex *.wsp, *.w??
node1
CIDATA
C:\PB_LIB *.dat, *.l??, *.nss,
(or PB$LIB)
project2 *.odb, *.wex
*.mdb,*.ded,
*.ple, *.aax, CONTROL
*.bax, *.gs? node2 *.c00, *.c??, *.ini
*.ini, DBDATA
*.odb, *.bax, *.c00, *.cfx, *.dfl,
C:\PC_LIB *.wsp, *.ls?, *.tbx, *.wex
(or PC$LIB)
*.w?? DOC
*.ped
etc. FORMS
etc. INFO
C:\TCLEV1 LIBDATA release_*\BIN32 DB_LIB
(or TC$LEV1) BUS_nnn
*.ini,*.tel, *.dcl,*.del,
*.tcs COIL*.b??
*.tcd,etc. *.stl
PC_LIB
LIST *.pcl,*.pel,
*.ptl
C:\TCLEV2 *.db,*.dbt,*.dgn,*.dxr,*.ml,*.ol,
(or TC$LEV2) SRC_LIB
*.glx,*.log,*.pc?,*.pxr,*.syl *.ba_,*.de_,
*.tcs
PCDATA *.pe,*.st_,
*.aax, *.c??, *.ls?, *.tc_,*.te_
*.tix, *.wex
SRCE
*.aa, *.ba
TCDATA
*.l??, *.tcs, *.wex
USER
*.tb, *.tc, *.ti, ...

Figure A-2. FCB Project Directory Structure

A-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section A.2 Short Description of FCB Files

A.2 Short Description of FCB Files

The reference directory is C:\Advabldenv unless you redefined it at the installation or later by
the environment variable ADVABLDENV.
FCB related files in reference directory:
• APB.INI = defaults of APB as set recently
• FCB.INI = defaults of FCB as set recently
• PRODUCT.INI = list of installed versions of Advant Engineering product components
• FOOT001.TPX = set of originally delivered templates
• ABBLOGO.WMF = ABB logo for templates.
It contains also files related to other components (*.INI, *.PDF, *.ABU, *.ISU, and other), and
possibly, files of user-defined templates (*.TPX, *.WMF, and other).

Files in the directories drive:\AdvaBNT\FCB\release_*

• RELNOTES.PDF = release notes of FCB
• DEL*.ABU and DEL*.ISU = files generated at installation containing information
necessary for the proper uninstallation of this FCB version at a later time.

The release directory is drive:\AdvaBNT\FCB\release_*\BIN32, where drive = C, D, ….

Files in release directories:
• *.MET = diagnostic text files of AC 100 Series modules
• *.TCD = files containing execution time data for node types *
• BASELIB.DLL, C*.DLL, GLOG.DLL, MF*.DLL, SftTT.DLL, VDOTRA32.DLL,
VLIST.DLL, and so on = dynamic link libraries of FCB
• OPCToF32.DLL = dummy dynamic link library file to be substituted by another file
at the installation of AdvaSoft for Windows
• Executable files of FCB (and of the attached utilities)
COMPIL32.EXE, DIAG32.EXE, DIAGNO32.EXE, FCB32.EXE,PROFIBUS.EXE, ….
• Help files of FCB (and of the attached utilities)
DIAG32.HLP, DIAGNO32.HLP, FCB32.HLP, FCB32.CNT, ….
• FUNCTION.INI = initialization file with supported node types, options, and library types
• TARGCONF.LIS = log file of Setup Add-Ons about the compilation of node types
• COMPILE.LOG = log file of COMPIL32 about the compilation of PC and DB libraries
• TARGET.TEL, TARGET.001 = actual and previous description files for supported targets
• Description files of targets:
– SAC11020.TEL = target description file of AC 110, V2.0,
– SAC11021.TEL = target description file of AC 110, V2.1
– SAC11022.TEL = target description file of AC 110, V2.2

3BDS 100 595R401 A-3

Function Chart Builder User’s Guide
Appendix AFunction Chart Builder Files

– SAC11023.TEL = target description file of AC 110, V2.3

– SAC16010.TEL = target description file of AC 160, V1.0,
– SAC16011.TEL = target description file of AC 160, V1.1
– SAC16012.TEL = target description file of AC 160, V1.2
– SAC16020.TEL = target description file of AC 160, V2.0
– SAC16021.TEL = target description file of AC 160, V2.1 (with PM64x)
– SAC16021PM66x.TEL = target description file of AC 160, V2.1 (with PM66x)
– SAC16022.TEL = target description file of AC 160, V2.2 (with PM64x)
– SAC16022PM66x.TEL = target description file of AC 160, V2.2 (with PM66x)
– SAC41011.TEL = target description file of AC 410 with SW QC01-BAS11*7.0
– SAC41012.TEL = target description file of AC 410 with SW QC01-BAS11*8.0
– SAC41013.TEL = target description file of AC 410 with SW QC01-BAS11*9.0
– SAC41014.TEL = target description file of AC 410 with SW QC01-BAS11*10.0
– SAC41015.TEL = target description file of AC 410 with SW QC01-BAS11*11.0
– SAC4101501.TEL = target description file of AC 410 with
SW QC01-BAS11*11.0/1
– SAC45011.TEL = target description file of AC 450 with SW QC02-BAS21*7.0
– SAC45012.TEL = target description file of AC 450 with SW QC02-BAS21*8.0
– SAC45013.TEL = target description file of AC 450 with SW QC02-BAS21*9.0
– SAC45020.TEL = target description file of AC 450 with SW QC07-BAS41*1.0
– SAC45021.TEL = target description file of AC 450 with SW QC07-BAS41*2.0
– SAC45022.TEL = target description file of AC 450 with SW QC07-BAS41*3.0
– SAC45023.TEL = target description file of AC 450 with SW QC07-BAS41*4.0
– SAC5510.TEL = target description file of AC 55, V1.0
– SAC5511.TEL = target description file of AC 55, V1.1
– SAC7010.TEL = target description file of AC 70, V1.0
– SAC7011.TEL = target description file of AC 70, V1.1
– SAC7012.TEL = target description file of AC 70, V1.2
– SAS10010.TEL = target description file of AdvaSoft for Windows, V1.0
– SAS10011.TEL = target description file of AdvaSoft for Windows, V1.1
– SAS10012.TEL = target description file of AdvaSoft for Windows, V1.2
– SAS10013.TEL = target description file of AdvaSoft for Windows, V1.3
– SEQCON01.TEL = target description for adding SEQCON option to AC 160, V1.0
– SMP20020.TEL = target description file of MP 200/1, V2.0
– SMP20021.TEL = target description file of MP 200/1, V2.1

A-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section A.2 Short Description of FCB Files

– SMP20030.TEL = target description file of MP 200/1, V3.0

– SMP20040.TEL = target description file of MP 200/1, V4.0.

• System DB element libraries of targets:

– QAC40111.BAX = system DBLIB (V1.0) for AC 410 with SW QC01-BAS11*7.0
– QAC40112.BAX = system DBLIB (V1.2) for AC 410 with SW QC01-BAS11*8.0
– QAC40113.BAX = system DBLIB (V1.3) for AC 410 with SW QC01-BAS11*9.0
– QAC40114.BAX = system DBLIB (V1.4) for AC 410 with SW QC01-BAS11*10.0
– QAC40115.BAX = system DBLIB (V1.5) for AC 410 with SW QC01-BAS11*11.0
– QAC4011501.BAX = system DBLIB (V1.5) for AC 410 with
SW QC01-BAS11*11.0/1
– QAC40511.BAX = system DBLIB (V1.0) for AC 450 with SW QC02-BAS21*7.0
– QAC40512.BAX = system DBLIB (V1.2) for AC 450 with SW QC02-BAS21*8.0
– QAC40513.BAX = system DBLIB (V1.3) for AC 450 with SW QC02-BAS21*9.0
– QAC40520.BAX = system DBLIB (V2.0) for AC 450 with SW QC07-BAS41*1.0
– QAC40521.BAX = system DBLIB (V2.1) for AC 450 with SW QC07-BAS41*2.0
– QAC40522.BAX = system DBLIB (V2.2) for AC 450 with SW QC07-BAS41*3.0
– QAC40523.BAX = system DBLIB (V2.3) for AC 450 with SW QC07-BAS41*4.0
– QAS10010.BAX = system DB element library QAS10010 (V1.0) for AdvaSoft for
Windows, V1.0
– QAS10011.BAX = system DB element library QAS10011 (V1.1) for AdvaSoft for
Windows, V1.1
– QAS10012.BAX = system DB element library QAS10011 (V1.2) for AdvaSoft for
Windows, V1.2
– QAS10013.BAX = system DB element library QAS10011 (V1.3) for AdvaSoft for
Windows, V1.3
– S0200.BAX = system DB element library DBLIB (V1.0) for MP 200/1, V2.0
– S0210.BAX = system DB element library DBLIB (V1.0) for MP 200/1, V2.1
– S0300.BAX = system DB element library DBLIB (V1.0) for MP 200/1, V3.0
– S0400.BAX = system DB element library DBLIB (V1.0) for MP 200/1, V4.0.

Files in subdirectory DB_LIB of release directories drive:\AdvaBNT\FCB\release_*\BIN32:

• QAC10010.DEL = DB element library QAC10010 (1.0) for AC 110, V2.0, Base System
• QAC10121.DEL = DB element library QAC10121 (1.0) for AC 110, V2.1, Base System
• QAC10122.DEL = DB element library QAC10122 (1.0) for AC 110, V2.2, Base System
• QAC10123.DEL = DB element library QAC10123 (1.0) for AC 110, V2.3, Base System
• QAC10610.DEL = DB element library QAC10610 (1.0) for AC 160, V1.0, Base System

3BDS 100 595R401 A-5

Function Chart Builder User’s Guide
Appendix AFunction Chart Builder Files

• QAC10611.DEL = DB element library QAC10611 (1.0) for AC 160, V1.1, Base System
• QAC10612.DEL = DB element library QAC10612 (1.0) for AC 160, V1.2, Base System
• QAC10620.DEL = DB element library QAC10620 (1.0) for AC 160, V2.0, Base System
• QAC10621.DEL = DB element library QAC10621 (1.0) for AC 160, V2.1
(with PM64x), Base System
• QAC10621PM66x.DEL = DB element library QAC10621 (1.0) for AC 160, V2.1
(with PM66x), Base System
• QAC10622.DEL = DB element library QAC10622 (1.0) for AC 160, V2.2
(with PM64x), Base System
• QAC10622PM66x.DEL = DB element library QAC10622 (1.0) for AC 160, V2.2
(with PM66x), Base System
• QAC12010.DEL = DB el. lib. QAC12010 (V1.0) for AC 110, V2.0, OPT2 (RCOM)
• QAC12121.DEL = DB el. lib. QAC12121 (V1.0) for AC 110, V2.1, OPT2 (RCOM)
• QAC12122.DEL = DB el. lib. QAC12122 (V1.0) for AC 110, V2.2, OPT2 (RCOM)
• QAC12123.DEL = DB el. lib. QAC12123 (V1.0) for AC 110, V2.3, OPT2 (RCOM)
• QAC12610.DEL = DB el. lib. QAC12610 (V1.0) for AC 160, V1.0, OPT2 (RCOM)
• QAC12611.DEL = DB el. lib. QAC12611 (V1.0) for AC 160, V1.1, OPT2 (RCOM)
• QAC12612.DEL = DB el. lib. QAC12612 (V1.0) for AC 160, V1.2, OPT2 (RCOM)
• QAC12620.DEL = DB el. lib. QAC12620 (V1.0) for AC 160, V2.0, OPT2 (RCOM)
• QAC12621.DEL = DB el. lib. QAC12621 (V1.0) for AC 160, V2.1 (with PM64x),
OPT2 (RCOM)
• QAC12621PM66x.DEL = DB el. lib. QAC12621 (V1.0) for AC 160, V2.1 (with PM66x),
OPT2 (RCOM)
• QAC12622.DEL = DB el. lib. QAC12622 (V1.0) for AC 160, V2.2 (with PM64x),
OPT2 (RCOM)
• QAC12622PM66x.DEL = DB el. lib. QAC12622 (V1.0) for AC 160, V2.2 (with PM66x),
OPT2 (RCOM)
• QAC13010.DEL = DB el. lib. QAC13010 (V1.0) for AC 110, V2.0, OPT3 (Events)
• QAC13121.DEL = DB el. lib. QAC13121 (V1.0) for AC 110, V2.1, OPT3 (Events)
• QAC13122.DEL = DB el. lib. QAC13122 (V1.0) for AC 110, V2.2, OPT3 (Events)
• QAC13123.DEL = DB el. lib. QAC13123 (V1.0) for AC 110, V2.3, OPT3 (Events)
• QAC13610.DEL = DB el. lib. QAC13610 (V1.0) for AC 160, V1.0, OPT3 (Events)
• QAC13611.DEL = DB el. lib. QAC13611 (V1.0) for AC 160, V1.1, OPT3 (Events)
• QAC13612.DEL = DB el. lib. QAC13612 (V1.0) for AC 160, V1.2, OPT3 (Events)
• QAC13620.DEL = DB el. lib. QAC13620 (V1.0) for AC 160, V2.0, OPT3 (Events)
• QAC13621.DEL = DB el. lib. QAC13621 (V1.0) for AC 160, V2.1 (with PM64x),
OPT3 (Events)

A-6 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section A.2 Short Description of FCB Files

• QAC13621PM66x.DEL = DB el. lib. QAC13621 (V1.0) for AC 160, V2.1 (with PM66x),
OPT3 (Events)
• QAC13622.DEL = DB el. lib. QAC13622 (V1.0) for AC 160, V2.2 (with PM64x),
OPT3 (Events)
• QAC13622PM66x.DEL = DB el. lib. QAC13622 (V1.0) for AC 160, V2.2 (with PM66x),
OPT3 (Events)
• QAC14123.DEL = DB el. lib. QAC14123 (V1.0) for AC 110, V2.3, OPT4 (Modbus)
• QAC14612.DEL = DB el. lib. QAC14612 (V1.0) for AC 160, V1.2, OPT4 (Modbus)
• QAC14620.DEL = DB el. lib. QAC14620 (V1.0) for AC 160, V2.0, OPT4 (Modbus)
• QAC14621.DEL = DB el. lib. QAC14621 (V1.0) for AC 160, V2.1 (with PM64x), OPT4
(Modbus)
• QAC14621PM66x.DEL = DB el. lib. QAC14621 (V1.0) for AC 160, V2.1 (with PM66x),
OPT4 (Modbus)
• QAC14622.DEL = DB el. lib. QAC14622 (V1.0) for AC 160, V2.2 (with PM64x), OPT4
(Modbus)
• QAC14622PM66x.DEL = DB el. lib. QAC14622 (V1.0) for AC 160, V2.2 (with PM66x),
OPT4 (Modbus)
• QAC16122.DEL = DB el. lib. QAC16122 (V1.0) for AC 110, V2.2,
Base System (PROFIBUS)
• QAC16123.DEL = DB el. lib. QAC16123 (V1.0) for AC 110, V2.3,
Base System (PROFIBUS)
• QAC16611.DEL = DB el. lib. QAC16611 (V1.0) for AC 160, V1.1,
Base System (PROFIBUS)
• QAC16612.DEL = DB el. lib. QAC16612 (V1.0) for AC 160, V1.2,
Base System (PROFIBUS)
• QAC16620.DEL = DB el. lib. QAC16620 (V1.0) for AC 160, V2.0,
Base System (PROFIBUS)
• QAC16621.DEL = DB el. lib. QAC16621 (V1.0) for AC 160, V2.1 (with PM64x),
Base System (PROFIBUS)
• QAC16622.DEL = DB el. lib. QAC16622 (V1.0) for AC 160, V2.2 (with PM64x),
Base System (PROFIBUS)
• QAC17122.DEL = DB el. lib. QAC17122 (V1.0) for AC 110, V2.2,
OPT7 (PROFIBUS S800)
• QAC17123.DEL = DB el. lib. QAC17123 (V1.0) for AC 110, V2.3,
OPT7 (PROFIBUS S800)
• QAC17620.DEL = DB el. lib. QAC17620 (V1.0) for AC 160, V2.0,
OPT7 (PROFIBUS S800)
• QAC17621.DEL = DB el. lib. QAC17621 (V1.0) for AC 160, V2.1 (with PM64x),
OPT7 (PROFIBUS S800)

3BDS 100 595R401 A-7

Function Chart Builder User’s Guide
Appendix AFunction Chart Builder Files

• QAC17622.DEL = DB el. lib. QAC17622 (V1.0) for AC 160, V2.2 (with PM64x),
OPT7 (PROFIBUS S800)
• QAC40111.DEL = DB element library DBLIB (V1.0)
for AC 410 with SW QC01-BAS11*7.0, Basic System
• QAC40112.DEL = DB element library DBLIB (V1.2)
for AC 410 with SW QC01-BAS11*8.0, Basic System
• QAC40113.DEL = DB element library DBLIB (V1.3)
for AC 410 with SW QC01-BAS11*9.0, Basic System
• QAC40114.DEL = DB element library DBLIB (V1.4)
for AC 410 with SW QC01-BAS11*10.0, Basic System
• QAC40115.DEL = DB element library DBLIB (V1.5)
for AC 410 with SW QC01-BAS11*11.0, Basic System
• QAC40511.DEL = DB element library DBLIB (V1.0)
for AC 450 with SW QC02-BAS21*7.0, Basic System
• QAC40512.DEL = DB element library DBLIB (V1.2)
for AC 450 with SW QC02-BAS21*8.0, Basic System
• QAC40513.DEL = DB element library DBLIB (V1.3)
for AC 450 with SW QC02-BAS21*9.0, Basic System
• QAC40520.DEL = DB element library DBLIB (V2.0)
for AC 450 with SW QC07-BAS41*1.0, Basic System
• QAC40521.DEL = DB element library DBLIB (V2.1)
for AC 450 with SW QC07-BAS41*2.0, Basic System
• QAC40522.DEL = DB element library DBLIB (V2.2)
for AC 450 with SW QC07-BAS41*3.0, Basic System
• QAC40523.DEL = DB element library DBLIB (V2.3)
for AC 450 with SW QC07-BAS41*4.0, Basic System
• QAC5010.DEL = DB element library QAC5010 (V1.0) for AC 55, V1.0, Base System
• QAC5011.DEL = DB element library QAC5011 (V1.0) for AC 55, V1.1, Base System
• QAC5210.DEL = DB element library QAC5210 (V1.0) for AC 55, V1.0, OPT2 (RCOM)
• QAC5211.DEL = DB element library QAC5210 (V1.1) for AC 55, V1.1, OPT2 (RCOM)
• QAC5310.DEL = DB element library for AC 55(V1.0), OPT3 (Events)
• QAC5311.DEL = DB element library for AC 55(V1.1), OPT3 (Events)
• QAC7010.DEL = DB element library QAC7010 (V1.0) for AC 70, V1.0, Base System
• QAC7011.DEL = DB element library QAC7011 (V1.0) for AC 70, V1.1, Base System
• QAC7012.DEL = DB element library QAC7012 (V1.0) for AC 70, V1.2, Base System
• QAC7110.DEL = DB element library QAC7110 (V1.0) for AC 70, V1.0, Event
• QAC7111.DEL = DB element library QAC7111 (V1.0) for AC 70, V1.1, Event
• QAC7112.DEL = DB element library QAC7112 (V1.0) for AC 70, V1.2, Event
• QAC7212.DEL = DB element library QAC7212 (V1.0) for AC 70, V1.2, Modbus
• QAS10010.DEL = DBLIB (V1.0) for AdvaSoft for Windows, V1.0, Base System

A-8 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section A.2 Short Description of FCB Files

• QAS10011.DEL = DBLIB (V1.1) for AdvaSoft for Windows, V1.1, Base System
• QAS10012.DEL = DBLIB (V1.2) for AdvaSoft for Windows, V1.2, Base System
• QAS10013.DEL = DBLIB (V1.3) for AdvaSoft for Windows, V1.3, Base System
• QMP20030.DEL = DBLIB (V1.0) for MP 200/1, V3.0, Basic System
• QMP20040.DEL = DBLIB (V1.0) for MP 200/1, V4.0, Basic System
• XMP20020.DEL = DBLIB (V1.0) for MP 200/1, V2.0, Basic System
• XMP20021.DEL = DBLIB (V1.0) for MP 200/1, V2.1, Basic System
• *.DCL = IO information for *.DEL
• *.STL = DB element statistics list for *.DEL.

File in subdirectory DB_LIB\SOURCE of release directories

drive:\AdvaBNT\FCB\release_*\BIN32:
PROFIBUS.MDB = Model database of PROFIBUS element library.

Files in subdirectory PC_LIB of release directories drive:\AdvaBNT\FCB\release_*\BIN32:

• QLB10010.PEL = PC element library QLB10010 (V1.0) for AC 110, V2.0, Base System
• QLB10121.PEL = PC element library QLB10021 (V1.0) for AC 110, V2.1, Base System
• QLB10122.PEL = PC element library QLB10022 (V1.0) for AC 110, V2.2, Base System
• QLB10123.PEL = PC element library QLB10023 (V1.0) for AC 110, V2.3, Base System
• QLB10610.PEL = PC element library QLB10610 (V1.0) for AC 160, V1.0, Base System
• QLB10611.PEL = PC element library QLB10611 (V1.0) for AC 160, V1.1, Base System
• QLB10612.PEL = PC element library QLB10612 (V1.0) for AC 160, V1.2, Base System
• QLB10620.PEL = PC element library QLB10620 (V1.0) for AC 160, V2.0, Base System
• QLB10621.PEL = PC element library QLB10621 (V1.0) for AC 160, V2.1 (with PM64x),
Base System
• QLB10621PM66x.PEL = PC element library QLB10621 (V1.0) for AC 160,
V2.1 (with PM66x), Base System
• QLB10622.PEL = PC element library QLB10622 (V1.0) for AC 160, V2.2 (with PM64x),
Base System
• QLB10622PM66x.PEL = PC element library QLB10622 (V1.0) for AC 160,
V2.2 (with PM66x), Base System
• QLB11010.PEL = PC element library QLB11010 (V1.0) for AC 110, V2.0,
OPT1 (extended PC elements)
• QLB11121.PEL = PC element library QLB11021 (V1.0) for AC 110, V2.1,
OPT1 (extended PC elements)
• QLB11122.PEL = PC element library QLB11022 (V1.0) for AC 110, V2.2,
OPT1 (extended PC elements)
• QLB11123.PEL = PC element library QLB11023 (V1.0) for AC 110, V2.3,

3BDS 100 595R401 A-9

Function Chart Builder User’s Guide
Appendix AFunction Chart Builder Files

OPT1 (extended PC elements)

• QLB11610.PEL = PC element library QLB11610 (V1.0) for AC 160, V1.0,
OPT1 (extended PC elements)
• QLB11611.PEL = PC element library QLB11611 (V1.0) for AC 160, V1.1,
OPT1 (extended PC elements)
• QLB11612.PEL = PC element library QLB11612 (V1.0) for AC 160, V1.2,
OPT1 (extended PC elements)
• QLB11620.PEL = PC element library QLB11620 (V1.0) for AC 160, V2.0,
OPT1 (extended PC elements)
• QLB11621.PEL = PC element library QLB11621 (V1.0) for AC 160, V2.1 (with PM64x),
OPT1 (extended PC elements)
• QLB11621PM66x.PEL = PC element library QLB11621 (V1.0) for AC 160,
V2.1 (with PM66x), OPT1 (extended PC elements)
• QLB11622.PEL = PC element library QLB11622 (V1.0) for AC 160, V2.2 (with PM64x),
OPT1 (extended PC elements)
• QLB11622PM66x.PEL = PC element library QLB11622 (V1.0) for AC 160,
V2.2 (with PM66x), OPT1 (extended PC elements)
• QLB12612.PEL = PC element library QLB12612 (V1.0) for AC 160, V1.2,
OPT6 (St.Red.+ RSM)
• QLB12620.PEL = PC element library QLB12620 (V1.0) for AC 160, V2.0,
OPT6 (St.Red.+ RSM)
• QLB12621.PEL = PC element library QLB12621 (V1.0) for AC 160, V2.1 (with PM64x),
OPT6 (St.Red.+ RSM)
• QLB12621PM66x.PEL = PC element library QLB12621 (V1.0) for AC 160,
V2.1 (with PM66x), OPT6 (St.Red.+ RSM)
• QLB12622.PEL = PC element library QLB12622 (V1.0) for AC 160, V2.2 (with PM64x),
OPT6 (St.Red.+ RSM)
• QLB12622PM66x.PEL = PC element library QLB12622 (V1.0) for AC 160,
V2.2 (with PM66x), OPT6 (St.Red.+ RSM)
• QLB16611.PEL = PC element library QLB16611 (V1.0) for AC 160, V1.1,
Base System, PROFIBUS
• QLB16612.PEL = PC element library QLB16612 (V1.0) for AC 160, V1.2,
Base System, PROFIBUS
• QLB16620.PEL = PC element library QLB16620 (V1.0) for AC 160, V2.0,
Base System, PROFIBUS
• QLB16621.PEL = PC element library QLB16621 (V1.0) for AC 160, V2.1 (with PM64x),
Base System, PROFIBUS
• QLB16622.PEL = PC element library QLB16622 (V1.0) for AC 160, V2.2 (with PM64x),
Base System, PROFIBUS
• QLB18622.PEL = PC element library QLB18622 (V1.0) for AC 160, V2.2 (with PM64x),
OPT8 (Warm Start)

A-10 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section A.2 Short Description of FCB Files

• QLB18622PM66x.PEL = PC element library QLB18622 (V1.0) for AC 160, V2.2

(with PM66x), OPT8 (Warm Start)
• QLB44111.PEL = PC element library QC01-BAS11 (V7.0)
for AC 410 with SW QC01-BAS11*7.0, Basic System
• QLB44112.PEL = PC element library QC01-BAS11 (V8.0)
for AC 410 with SW QC01-BAS11*8.0, Basic System
• QLB44113.PEL = PC element library QC01-BAS11 (V9.0)
for AC 410 with SW QC01-BAS11*9.0, Basic System
• QLB44114.PEL = PC element library QC01-BAS11 (V10.0)
for AC 410 with SW QC01-BAS11*10.0, Basic System
• QLB44115.PEL = PC element library QC01-BAS11 (V11.0)
for AC 410 with SW QC01-BAS11*11.0, Basic System
• QLB44511.PEL = PC element library QC02-BAS21 (V7.0)
for AC 450 with SW QC02-BAS21*7.0, Basic System
• QLB44512.PEL = PC element library QC02-BAS21 (V8.0)
for AC 450 with SW QC02-BAS21*8.0, Basic System
• QLB44513.PEL = PC element library QC02-BAS21 (V9.0)
for AC 450 with SW QC02-BAS21*9.0, Basic System
• QLB44520.PEL = PC element library QC07-BAS41 (V1.0)
for AC 450 with SW QC07-BAS41*1.0, Basic System
• QLB44521.PEL = PC element library QC07-BAS41 (V2.0)
for AC 450 with SW QC07-BAS41*2.0, Basic System
• QLB44522.PEL = PC element library QC07-BAS41 (V3.0)
for AC 450 with SW QC07-BAS41*3.0, Basic System
• QLB44523.PEL = PC element library QC07-BAS41 (V4.0)
for AC 450 with SW QC07-BAS41*4.0, Basic System
• QLB46111.PEL = PC element library QC01-LIB11 (V7.0)
for AC 410 with SW QC01-BAS11*7.0, Additional PC elements 1
• QLB46112.PEL = PC element library QC01-LIB11 (V8.0)
for AC 410 with SW QC01-BAS11*8.0, Additional PC elements 1
• QLB46113.PEL = PC element library QC01-LIB11 (V9.0)
for AC 410 with SW QC01-BAS11*9.0, Additional PC elements 1
• QLB46114.PEL = PC element library QC01-LIB11 (V10.0)
for AC 410 with SW QC01-BAS11*10.0, Additional PC elements 1
• QLB46115.PEL = PC element library QC01-LIB11 (V11.0)
for AC 410 with SW QC01-BAS11*11.0, Additional PC elements 1
• QLB46511.PEL = PC element library QC02-LIB21 (V7.0)
for AC 450 with SW QC02-BAS21*7.0, Additional PC elements 1
• QLB46512.PEL = PC element library QC02-LIB21 (V8.0)
for AC 450 with SW QC02-BAS21*8.0, Additional PC elements 1
• QLB46513.PEL = PC element library QC02-LIB21 (V9.0)
for AC 450 with SW QC02-BAS21*9.0, Additional PC elements 1

3BDS 100 595R401 A-11

Function Chart Builder User’s Guide
Appendix AFunction Chart Builder Files

• QLB46520.PEL = PC element library QC07-LIB41 (V1.0)

for AC 450 with SW QC07-BAS41*1.0, Additional PC elements 1
• QLB46521.PEL = PC element library QC07-LIB41 (V2.0)
for AC 450 with SW QC07-BAS41*2.0, Additional PC elements 1
• QLB46522.PEL = PC element library QC07-LIB41 (V3.0)
for AC 450 with SW QC07-BAS41*3.0, Additional PC elements 1
• QLB46523.PEL = PC element library QC07-LIB41 (V4.0)
for AC 450 with SW QC07-BAS41*4.0, Additional PC elements 1
• QLB48111.PEL = PC element library QC01-LIB12 (V7.0)
for AC 410 with SW QC01-BAS11*7.0, Additional PC elements 2
• QLB48112.PEL = PC element library QC01-LIB12 (V8.0)
for AC 410 with SW QC01-BAS11*8.0, Additional PC elements 2
• QLB48113.PEL = PC element library QC01-LIB12 (V9.0)
for AC 410 with SW QC01-BAS11*9.0, Additional PC elements 2
• QLB48114.PEL = PC element library QC01-LIB12 (V10.0)
for AC 410 with SW QC01-BAS11*10.0, Additional PC elements 2
• QLB48115.PEL = PC element library QC01-LIB12 (V11.0)
for AC 410 with SW QC01-BAS11*11.0, Additional PC elements 2
• QLB48511.PEL = PC element library QC02-LIB22 (V7.0)
for AC 450 with SW QC02-BAS21*7.0, Additional PC elements 2
• QLB48512.PEL = PC element library QC02-LIB22 (V8.0)
for AC 450 with SW QC02-BAS21*8.0, Additional PC elements 2
• QLB48513.PEL = PC element library QC02-LIB22 (V9.0)
for AC 450 with SW QC02-BAS21*9.0, Additional PC elements 2
• QLB48520.PEL = PC element library QC07-LIB42 (V1.0)
for AC 450 with SW QC07-BAS41*1.0, Additional PC elements 2
• QLB48521.PEL = PC element library QC07-LIB42 (V2.0)
for AC 450 with SW QC07-BAS41*2.0, Additional PC elements 2
• QLB48522.PEL = PC element library QC07-LIB42 (V3.0)
for AC 450 with SW QC07-BAS41*3.0, Additional PC elements 2
• QLB48523.PEL = PC element library QC07-LIB42 (V4.0)
for AC 450 with SW QC07-BAS41*4.0, Additional PC elements 2
• QLB4CC20.PEL = PC element library QC07-COM41 (V1.0)
for AC 450 with SW QC07-BAS41*1.0, Consistent Communication on AF 100
• QLB4CC21.PEL = PC element library QC07-COM41 (V2.0)
for AC 450 with SW QC07-BAS41*2.0, Consistent Communication on AF 100
• QLB4CC22.PEL = PC element library QC07-COM41 (V3.0)
for AC 450 with SW QC07-BAS41*3.0, Consistent Communication on AF 100
• QLB4CC23.PEL = PC element library QC07-COM41 (V4.0)
for AC 450 with SW QC07-BAS41*4.0, Consistent Communication on AF 100
• QLB4FZ21.PEL = PC element library QC07-FUZ41 (V1.0)
for AC 450 with SW QC07-BAS41*2.0, Fuzzy Control

A-12 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section A.2 Short Description of FCB Files

• QLB4FZ22.PEL = PC element library QC07-FUZ41 (V2.0)

for AC 450 with SW QC07-BAS41*3.0, Fuzzy Control
• QLB4FZ23.PEL = PC element library QC07-FUZ41 (V3.0)
for AC 450 with SW QC07-BAS41*4.0, Fuzzy Control
• QLB5010.PEL = PC element library QLB5010 (V1.0) for AC 55, V1.0, Base System
• QLB5011.PEL = PC element library QLB5010 (V1.0) for AC 55, V1.1, Base System
• QLB5110.PEL = PC element library QLB5110 (V1.0) for AC 55, V1.0,
OPT1 (extended PC elements)
• QLB5111.PEL = PC element library QLB5110 (V1.1) for AC 55, V1.1,
OPT1 (extended PC elements)
• QLB7010.PEL = PC element library QLB7010 (V1.0) for AC 70, V1.0, Base System
• QLB7011.PEL = PC element library QLB7011 (V1.0) for AC 70, V1.1, Base System
• QLB7012.PEL = PC element library QLB7012 (V1.0) for AC 70, V1.2, Base System
• QLB7110.PEL = PC element library QLB7110 (V1.0) for AC 70, V1.0,
OPT1 (extended PC elements)
• QLB7111.PEL = PC element library QLB7111 (V1.0) for AC 70, V1.1,
OPT1 (extended PC elements)
• QLB7112.PEL = PC element library QLB7112 (V1.0) for AC 70, V1.2,
OPT1 (extended PC elements)
• QLBASC10.PEL = PC element library PCLIB (V1.0) for AdvaSoft for Windows, V1.0,
AdvaSoft for Windows, V1.1, AdvaSoft for Windows, V1.2, and AdvaSoft for Windows,
V1.3 Base Systems
• QMP20030.PEL = PC element library QMP200 (V5.0) for MP 200/1, V3.0, Basic System
• QMP20040.PEL = PC element library QMP200 (V6.0) for MP 200/1, V4.0, Basic System
• QMP24030.PEL = PC element library QMP24030 (V5.0) for MP 200/1, V3.0,
additional PC elements
• QMP24040.PEL = PC element library QMP24040 (V6.0) for MP 200/1, V4.0,
additional PC elements
• QMP26030.PEL = PC element library QMP26030 (V5.0) for MP 200/1, V3.0,
additional PC elements
• QMP26040.PEL = PC element library QMP26040 (V6.0) for MP 200/1, V4.0,
additional PC elements
• QMP28030.PEL = PC element library QMP28030 (V5.0) for MP 200/1, V3.0,
additional PC elements
• QMP28040.PEL = PC element library QMP28040 (V6.0) for MP 200/1, V4.0,
additional PC elements
• SEQCON01.PEL = PC element library SEQCON (V1.0) for AC 160, V1.0,
option SEQCON
• XMP20020.PEL = PC element library XMP200 (V3.0) for MP 200/1, V2.0, Basic System
• XMP20021.PEL = PC element library XMP200 (V4.0) for MP 200/1, V2.1, Basic System

3BDS 100 595R401 A-13

Function Chart Builder User’s Guide
Appendix AFunction Chart Builder Files

• XMP24020.PEL = PC element library XMP24020 (V3.0) for MP 200/1, V2.0,

additional PC elements
• XMP24021.PEL = PC element library XMP24021 (V4.0) for MP 200/1, V2.1,
additional PC elements
• XMP26020.PEL = PC element library XMP26020 (V3.0) for MP 200/1, V2.0,
additional PC elements
• XMP26021.PEL = PC element library XMP26021 (V4.0) for MP 200/1, V2.1,
additional PC elements
• XMP28020.PEL = PC element library XMP28020 (V3.0) for MP 200/1, V2.0,
additional PC elements
• XMP28021.PEL = PC element library XMP28021 (V4.0) for MP 200/1, V2.1,
additional PC elements
• *.PCL and *.PTL = supplementary information to *.PEL.

Files in subdirectory SRC_LIB of release directories drive:\AdvaBNT\FCB\release_*\BIN32:

• *.TE_ = node type description files in compressed form
• *.TC_ = execution time files in compressed form
• *.BA_ = system DB element files in compressed form
• *.DE_ = DB element library source files in compressed form
• *.ST_ = DB element statistics list files in compressed form
• *.PE_ = PC element library source files in compressed form.

Files in the drive:\Program Files\Common Files\AdvaBld Shared directory:

• *.EXE = Executable files shared by different Control Builder A components
• *.DLL = Dlls shared by different Control Builder A components
• *.HLP = Help files of the corresponding executable files and dlls
• DEAM*.LO = files to be loaded to the Advant Station 100 Series Engineering Board.

Files in the drive:\Windows\System32 directory:

*.DLL such as Imgman31.DLL, H5krnl32.DLL, H5rtf32.DLL = Dlls of third-party
products used by different Control Builder A components.

File in the project data root directory project_root, for example, in C:\PROJ:
PROJROOT.INI = file listing the projects under project_root.

Files in project directories project_root\project*, for example, in C:\PROJ\WATER:

• CIRCUITS.DAT = file listing the circuits of project_root\project*
• FOOT001.TPX = set of templates available for project*
• NODES.DAT = file listing the nodes of project_root\project*

A-14 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section A.2 Short Description of FCB Files

• PRJNOTES.TXT = file with creation note for project*

• project*.INI = defaults for project*
• TYPECIRC.DAT = file listing the type circuits of project_root\project*
• project*.MDB, project*.BCI, project*.TCI,… = Bus Configuration Database of the
project (files of the Bus Configuration Builder).

There are currently no files in the project-specific NODES directory

project_root\project*\NODES, for example, in C:\PROJ\WATER\NODES.

There are currently no files in the project-specific PC element library

project_root\project*\NODES\PC_LIB, for example, in
C:\PROJ\WATER\NODES\PC_LIB. It is reserved for future use.

There are currently no files in the project-specific circuit directory

project_root\project*\NODES\PR_CI, for example, in C:\PROJ\WATER\NODES\PR_CI.

Files in subdirectories of project-specific circuit directory

project_root\project*\NODES\PR_CI, for example, of C:\PROJ\WATER\NODES\PR_CI:
• ..\CIDATA
– DBGENDEF.BAX = optional file containing the DB system defaults (general
defaults) for project-specific CIs *
– *.CIS = source code of project-specific CIs *
– *.INI = information files of CIs *
– *.LIS = symbol information files for CIs *
– *.LS? = list files of the CI backtranslator
– *.ODB = FCB’s internal data representation of CIs *
– *.WEX = files containing detected error locations in CI source files *.CIS
– *.WSP = workspace file containing opened windows, selections, and filters at the
end of the last session for CI *
– *.W00, *.W01, … = files containing workspaces defined for CI *.
• ..\LIST
– *.DB = DB listing generated by printing to file *
– *.DBT = text file containing exported DB section or part of it
– *.DXR = DB cross-reference listing generated by printing to file *
– *.PCF = function chart (document) generated by printing to file *
– *.PCT = tree diagram (document) generated by printing to file *
– *.PXR = PC cross-reference listing generated by printing to file *
– *.SYL = Symbol listing generated by printing to file *
– *.UCI = CI usage listing generated by printing to file *

3BDS 100 595R401 A-15

Function Chart Builder User’s Guide
Appendix AFunction Chart Builder Files

– CIERRORS.LIS = list of incorrect CIs found at FCB start.

There are currently no files in the project-specific type circuit directory

project_root\project*\NODES\PR_TC, for example, in C:\PROJ\WATER\NODES\PR_TC.

Files in subdirectories of project-specific type circuit directory

project_root\project*\NODES\PR_TC, for example, of C:\PROJ\WATER\NODES\PR_TC:
• ..\LIST
– *.DB = DB listing generated by printing to file *
– *.DBT = text file containing exported DB section or part of it
– *.DXR = DB cross-reference listing generated by printing to file *
– *.PCF = function chart (document) generated by printing to file *
– *.PCT = tree diagram (document) generated by printing to file *
– *.PXR = PC cross-reference listing generated by printing to file *
– TCERRORS.LIS = list of incorrect TCs found at FCB start.
• ..\TCDATA
– DBGENDEF.BAX = optional file containing the DB system defaults (general
defaults) for project-specific TCs *
– *.INI = information files of TCs *
– *.LIS = symbol information files for TCs *
– *.LS? = list files of the TC backtranslator
– *.ODB = FCB’s internal data representation of TCs *
– *.TCS = source code of project-specific TCs *
– *.WEX = files containing detected error locations in TC source files *.TCS
– *.WSP = file containing opened windows, selections, and filters at the end of the
last session for TC *
– *.W00, *.W01, … = files containing workspaces defined for TC *.
Files in node directories project_root\project*\NODES\node*,
for example, in C:\PROJ\WATER\NODES\WAT_N1:
– *.INI = information file for node *
– *.ODB = FCB’s internal data representation of node * (resolved and expanded)
– *.WSP = file with windows, filters, and so on, at the end of the last session for node *
– *.W00, *.W01, … = files containing workspaces defined for node *.
Files in subdirectories of node directories project_root\project*\NODES\node*, for example,
of C:\PROJ\WATER\NODES\WAT_N1:
• ..\DOC, ..\FORMS, and ..\INFO
There are currently no files in these directories, they are reserved for future use.
• ..\CIDATA

A-16 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section A.2 Short Description of FCB Files

– *.LIS = symbol information files for CIs *

– *.LS? = list files generated by the NS backtranslator and during expanding node data
– *.NSS = source code of NS *
– *.ODB = FCB’s internal data representation of NS *
– *.WEX = file containing detected error locations in NS source file *.NSS
– CIUSED.DAT = list of CIs located in all NSs.
• ..\CONTROL
– *.C00 = AC 100 Series target code of a retrieved application, DB part
– *.C?? = AC 100 Series target code of a retrieved application, PC part
– DBPCVERS.INI = file containing retrieved time stamps and PC program number of
target code.
• ..\DBDATA
– *.BAX = AMPL source code files for the DB part (in expanded form), optionally
also DBGENDEF.BAX containing node-specific DB system defaults (general
defaults)
– *.C00 = generated AC 100 Series target code, DB part
– *.CFX = command files for dimensioning the data base by the On-line Builder
for AC 400 Series and MasterPiece 200/1 nodes
– *.DFL = display/force list for export and import
– *.LS? = list files generated by the DB backtranslator
– *.TBX = files containing information about the locations of TCs * instantiated in
DB part (in expanded form)
– *.WEX = files containing detected error locations in the source files *.BAX.
• ..\LIBDATA
– FUNCTION.INI = initialization file with supported node types, options, and library
types
– TARGCONF.LIS = log file of Setup Add-Ons about the compilation of node types
– COMPILE.LOG = log file of COMPIL32 about the compilation of PC and DB
libraries
– TARGET.TEL = actual and previous description files for supported targets
– *.TEL, *.TCD = node type description files and execution time files.
– Files in subdirectories of LIBDATA
The node-specific element library files are stored in the subdirectories of LIBDATA
depending on the Function Chart Builder release, to which the libraries pertain and
with which the node is programmed:
..\LIBDATA\release_*\BIN32\SRC_LIB subdirectory contains the sources of node
type descriptions and element libraries in compressed form as *.TE_, *.TC_, *.BA_,
*.DE_, *.ST_, and *.PE_ files.

3BDS 100 595R401 A-17

Function Chart Builder User’s Guide
Appendix AFunction Chart Builder Files

..\LIBDATA\release_*\BIN32\DB_LIB and
..\LIBDATA\release_*\BIN32\PC_LIB subdirectories contain the element libraries
in compiled form as *.DCL, *.DEL, *.STL, *.PCL, *.PEL, and *.PTL files.
• ..\LIST
– *.DB = DB listing generated by printing to file *
– *.DBT = text file containing exported DB section or part of it
– *.DGN = text file containing diagnostic report
– *.DXR = DB cross-reference listing generated by printing to file *
– *.GLX = file containing recorded trend (open with AS100-EDIT or Microsoft Excel)
– *.LOG = text file containing diagnostic log
– *.ML = module address list generated by printing to file *
– *.OL = options list generated by printing to file *
– *.PCF = function chart (document) generated by printing to file *
– *.PCT = tree diagram (document) generated by printing to file *
– *.PXR = PC cross-reference listing generated by printing to file *
– *.SYL = symbol listing generated by printing to file *.
• ..\PCDATA
– *.AAX = AMPL source code files for PC programs (in expanded form)
– *.C?? = generated AC 100 Series target code, PC part
– *.LS? = list files generated by the PC backtranslator
– *.TIX = information about the locations of TCs (in expanded form)
– *.WEX = files containing detected error locations in the source files *.AAX.
• ..\SRCE
– *.AA = AMPL source code files for PC programs (in compressed form)
– *.BA = AMPL source code files for the DB (in compressed form).
• ..\TCDATA
– *.LIS = symbol information files for TCs *
– *.LS? = list files generated at TC instantiation in node mode
– *.TCS = source code of TCs included in element library of the node
– *.WEX = files containing detected error locations in TC source files *.TCS.
• ..\USER
– *.TB = information about the locations of TCs (in compressed form)
– *.TC = source code of TCs (in compressed form)
– *.TI = information about the locations of TCs (in compressed form).

A-18 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section A.2 Short Description of FCB Files

Files in the project-specific BUS_nnn directory project_root\project*\BUS_nnn, for example,

in C:\PROJ\WATER\BUS_002.
COIL*.b?? = Bus configuration information list files of AF 100 bus nnn.

Files in the directory for user-defined PROFIBUS DB element libraries (PB$LIB), for example,
in C:\PB_LIB:
• *.AAX, *.BAX= AC 400 source files serving as template for work with On-line Builder
• *.GS? = Geräte-StammDaten files of PROFIBUS devices
• *.MDB = databases of user defined PROFIBUS DB element libraries
• *.PLE = export files of user defined PROFIBUS DB element libraries
• *.DED = source files of user defined PROFIBUS DB element libraries.

Files in the directory for additional PC element libraries (PC$LIB), for example,
in C:\PC_LIB:
*.PED = additional PC element libraries *.

Files in level1 type circuit directory (TC$LEV1), for example, in C:\TCLEV1:

*.TCS = source code of level1 TCs.

Files in level2 type circuit directory (TC$LEV2), for example, in C:\TCLEV2:

*.TCS = source code of level2 TCs.

3BDS 100 595R401 A-19

Function Chart Builder User’s Guide
Appendix AFunction Chart Builder Files

A-20 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section B.1 Working with an AC 400 or MP 200/1 Node

Appendix B Data Flow in Function Chart Builder

B.1 Working with an AC 400 or MP 200/1 Node

Editors Editors

*.ODB *.ODB

Source Source
FCB Code Code
Generator Backtranslator

*.TIX,*.TBX,*.TCS

*.AAX *.BAX *.AAX *.BAX

Prepare Source Code Prepare Source Code

for ONB for FCB

APB
*.AA *.BA *.TI,*.TB,*.TC *.AA *.BA

ONB TRPCS TRDBS DUPCS DUDBS

AC 400 or MP 200/1

Figure B-1. Working with an AC 400 or MP 200/1 Node

3BDS 100 595R401 B-1

Function Chart Builder User’s Guide
Appendix B Data Flow in Function Chart Builder

B.2 Instantiating Type Circuits in a Node

DB and PC
*.TCS TC Interpreter *.DEL, *.PEL element
library

Editors

*.ODB

Source Source
Code Code
Generator Backtranslator

*.AAX *.BAX *.TIX, *.TBX *.AAX *.BAX *.TIX, *.TBX *.TCS

Figure B-2. Instantiating Type Circuits in a Node

B-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section B.3 Working on Type Circuits

B.3 Working on Type Circuits

DB and PC Working
element *.DEL,*.PEL Editors on a TC
library

*.ODB

TC Code TC Back-
Generator translator

*.TCS

Figure B-3. Working on Type Circuits

3BDS 100 595R401 B-3

Function Chart Builder User’s Guide
Appendix B Data Flow in Function Chart Builder

B.4 Working on Circuits

DB and PC
element *.DEL,*.PEL
library

Type Working
circuits *.TCS Editors on a CI

*.ODB

CI Code CI Back-
Generator translator

*.CIS

Figure B-4. Working on Circuits

B-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section B.5 Working on Node Structures

B.5 Working on Node Structures

DB and PC
element *.DEL,*.PEL
library

Type Working
circuits *.TCS Editors on an NS

Circuits *.CIS *.ODB

NS Code NS Back-
Generator translator

*.NSS

Figure B-5. Working on Node Structures

3BDS 100 595R401 B-5

Function Chart Builder User’s Guide
Appendix B Data Flow in Function Chart Builder

B.6 Expanding Node Data

*.NSS NS Interpreter

*.CIS CI Interpreter *.ODB

*.TCS TC Interpreter

Source
Code
Generator

*.AAX *.BAX *.TIX,*.TBX

Figure B-6. Expanding Node Data

B-6 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section B.7 Advant Controller 100 Series Target Code Generation

B.7 Advant Controller 100 Series Target Code Generation

Editors

FCB *.ODB

Target
Code
Generator

AC 100 Series
Node

Figure B-7. AC 100 Series Target Code Generation

3BDS 100 595R401 B-7

Function Chart Builder User’s Guide
Appendix B Data Flow in Function Chart Builder

B.8 Upgrading to New FCB Release, Regenerating Objects

*.ODB

Working with a
former release
of FCE or FCB Source
Code
Generator

Source files generated by a

former release of FCE or FCB
*.AAX *.BAX etc.

Source
Code
Backtranslator

Working with
the new release
of FCB *.ODB ODBs regenerated for
the new release of FCB

Editors Source
Code
Generator

Source files regenerated by

the new release of FCB
*.AAX *.BAX etc.

Figure B-8. Upgrading to New FCB Release, Regenerating Objects

B-8 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section C.1 Syntax of Symbolic Expressions

Appendix C Syntax of Symbolic Expressions and Formulas

C.1 Syntax of Symbolic Expressions

symbExpression ::= [anyString] ’<’ (symbol | symbExpression) ’>’ [anyString]
symbol is a symbol.
anyString is a constant pertaining to some data type.

NOTES
symbExpression can be only of non-calculated data types, so you can use only the
concatenation operation, but no arithmetical operators.

Nested symbExpressions are interpreted successively until all involved terms are
substituted by constant values, and the concatenations are executed. The data type
of the so evaluated result has to correspond to the data type of the concerned
symbol and terminal, respectively, to which it will be assigned.

3BDS 100 595R401 C-1

Function Chart Builder User’s Guide
Appendix C Syntax of Symbolic Expressions and Formulas

C.2 Syntax of Symbolic Formulas

symbFormula ::= relOperand [relOperator relOperand]
relOperand ::= [’+’ | ’-’] addOperand {addOperator addOperand}
relOperator ::= ’=’ | "<>" | ’<’ | ’>’ | "<=" | ">="
addOperand ::= mulOperand {mulOperator mulOperand}
addOperator ::= ’+’ | ’-’ | OR
mulOperand ::= [ NOT ] expOperand {expOperator expOperand}
mulOperator ::= ’*’ | ’/’ | AND
expOperand ::= constant | ( ’<’ symbol ’>’ ) | ( ’(’ symbFormula ’)’ )
constant ::= TRUE | T | FALSE | F | decimal
decimal ::=( ( ’.’ digit {digit} ) | ( digit {digit} [ ’.’ {digit} ] ) ) [ E [’+’|’-’] digit {digit} ]
digit ::= 0 | 1 | … | 9
expOperator ::= '^'
symbol is a symbol.

NOTES
Nested symbFormulas are interpreted successively until all involved terms are
substituted by constant values, and the operations are executed.

symbFormula can be only of calculated data types CB, CI, CIL, CR.

Operands of all types and all the operators are allowed in a symbFormula, no
matter what is the type of the symbol, the value of which is to be calculated.

The operands are at first converted internally to real values. All operations (also
the Boolean ones!) are then executed with real values. For Boolean operations
0.00 is considered to be FALSE, all nonzero values are considered to be TRUE.
At the end the real result is converted to B, I, or IL or left R depending on the
symbol, the value of which was to be calculated on the basis of the formula.

C-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.1 General

Appendix D Syntax of TC, CI, and NS Source Code

D.1 General

D.1.1 Introduction
This appendix defines the ANSI source code files describing the objects type circuit (TC),
circuit (CI), and node structure (NS).
The source code is part of the interface between Advant Engineering product components and
other tools.
This description serves also as reference for developers of TCs, CIs, and NSs working on source
code level.
TC source code, CI source code, and NS source code are derivatives of the AMPL source code
with closely related syntax and semantics.
The source code descriptions are given as a set of syntax rules in a kind of Backus-Naur-form.

D.1.2 Conventions
Syntax Rules
Each syntax rule defines how to generate the term on the left side of the “::=” sign on the basis
of an expression consisting of terms on the right side, which are grouped by ‘(’ and ‘)’
(parentheses), ‘[’ and ‘]’ (square brackets), and ‘{’ and ‘}’ (braces, curly brackets), and
connected by concatenation and the ‘|’ (OR) operator.
Concatenation means putting terms one next to the other.
The ‘|’ (OR) operator means “take one term, either the one on the left side of the OR operator,
or the one on the right side”.
The OR operator has higher priority than the concatenation.
Two dots between terms stand as shorthand for OR function of all terms in a range.
For example, ‘a’..‘z’ stand for ‘a’ | ‘b’ | … |‘z’.
For simplicity we use also the except operator to limit a term by excepting some of its
constituents.
Parentheses serve to group terms to override the precedence of the concatenation and OR
operation.
Square brackets denote optional terms. These terms can occur once or do not occur;
they can be applied once but they need not to be applied.
Braces denote optional terms that can occur once or several times, or do not occur;
they can be applied once or several times but they need not to be applied.
In some cases figures in parentheses after a term show the maximum length of the term,
for example, tcName(8).
Breaking a rule into two or more lines has no significance. We break the rules into several lines
if the rule is too long, or if we want to make a hint to the usual line breaking in source code.

3BDS 100 595R401 D-1

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

Quotation
Single characters are quoted by intelligent single quotes, for example, ‘a’.
Strings are quoted by intelligent double quotes, for example, “<=”.
Non-printable characters and space are described by their names, in small capitals, for example,
SPACE or FF (form feed).

Miscellaneous
Terminal symbols are the terms that cannot or should not be resolved by further rules.
They begin with a capitalized letter and are written in bold letters.
Or, being single characters or strings, they are enclosed between quotes.
Non-terminal symbols begin with a small letter, they are written in italics.
Division of the syntax into lexical and syntactical part, and use of classes like tokens, keywords,
and so on, reflect a possible implementation of the corresponding source code generators and
backtranslators.
In some cases we give additional information in form of comments to the rules to clear
background and semantic aspects.

Example of a Simple Syntax and Its Use

Suppose the following syntax rules:
1. animals ::= ( singleAnimal {‘,’ singleAnimal} ) | ( animalPair {‘,’ animalPair}
)
2. animalPair ::= ( Hen ‘+’ Cock ) | ( Cow ‘+’ Bull)
3. singleAnimal ::= Dog | Cat
The following sentences can be generated on the basis of the rules, they are correct:
Cat --> use rules 3. and 1.
Cat, Cat, Dog, Cat --> use rules 3. and 1. with option
Cow + Bull, Hen + Cock --> use rules 2. and 1. with option
The following sentences cannot be generated on the basis of the rules, they are incorrect:
Dog Cat --> comma is missing
Dog + Cat --> “Dog + Cat” is not a valid terminal symbol
Cow + Bull, Dog --> mixing singleAnimals and animalPairs is in
no rule contained.

D-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.1.3 Implementation

D.1.3 Implementation

Standard File Name Extensions

TC source code, CI source code, and NS source code files have the standard file name
extensions TCS, CIS, and NSS, respectively.

National Character Sets

Advant Controller 400 Series, MasterPiece 200/1 and the On-line Builder (ONB) use the
following 7 bit ASCII character sets:
• International (US) character set
• German national character set
• Swedish national character set.
Nevertheless, the Function Chart Builder (FCB) represents these characters in *.TCS, *.CIS,
and *.NSS files by their 8 bit ANSI codes.
The Function Chart Builder uses the character set, which is selected for the actual project by the
Application Builder (APB).

Parsers, Editors, Code Generators in the Function Chart Builder

The Function Chart Builder contains several parsers, editors, and code generators implemented
on the basis of the present syntax descriptions.
We summarize them in the following tables:

Table D-1. Parsers in FCB Based on Present Syntax Descriptions

Parser Input File Output File

Type circuit backtranslator *.TCS *.ODB for TC
Circuit backtranslator *.CIS *.ODB for CI
Node structure backtranslator *.NSS *.ODB for NS
Type circuit interpreter *.TCS *.ODB for node
Circuit interpreter *.CIS *.ODB for node

Table D-2. Nested Parsers in FCB Based on Present Syntax Descriptions

Parser Input File Output File

Expander and checker *.NSS -------v
*.CIS -------v
*.TCS ----> *.ODB for node

3BDS 100 595R401 D-3

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

Table D-3. Editors in FCB Based on Present Syntax Descriptions

Editor System I/O FCB File

Editors working on TC Keyboard, mouse, display *.ODB for TC
Editors working on CI Keyboard, mouse, display *.ODB for CI
Editors working on NS Keyboard, mouse, display *.ODB for NS

Table D-4. Source Code Generators in FCB Based on Present Syntax Descriptions

Source Code Generator Input File Output File

TC source code generator *.ODB for TC *.TCS
CI source code generator *.ODB for CI *.CIS
NS source code generator *.ODB for NS *.NSS

You find these backtranslators, editors, and code generators referenced in Appendix B, Data
Flow in Function Chart Builder.

D.1.4 Release History

1. Circuit and node structure handling, thus circuit source code and node structure source
code, have been introduced with Function Chart Editor release 3.0.
2. The following features have been added with Function Chart Editor release 3.1 (and
remained valid also for Function Chart Builder release 4.0, 4.1, 4.2, and 4.3):
– Support of calculated symbols
– Support of manual TC/CI terminal specification.
3. The following features have been added with Function Chart Builder release 4.4:
– Keyword INAME
– Usage of instance names.
4. The following feature has been added with Function Chart Builder release 4.7:
Instantiation (location) of circuits directly in nodes.
The circuit interpreter resolves and expands the circuits at once. The circuit
boundaries become invisible in the node.
The present descriptions correspond to the Function Chart Builder release 4.7 implementation.

D-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.2 Syntax of TC Source Code

D.2 Syntax of TC Source Code

D.2.1 Lexical Part

D.2.1.1 Simple Character Sets

digit ::= ‘0’..‘9’
letter ::= ‘a’..’z’ | ‘A’..’Z’
national ::= () empty if US
| (‘ä’ | ‘Ä’ | ‘ö’ | ‘Ö’ | ‘ü’ | ‘Ü’ | ‘ß’) if German
| (‘ä’ | ‘Ä’ | ‘ö’ | ‘Ö’ | ‘å’ | ‘Å’) if Swedish
special ::= ( ‘!’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘'’ | ‘(’ | ‘)’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘/’
| ‘<’ | ‘>’ | ‘?’ | ‘@’ | ‘_’ | ‘:’ | ‘=’ | ‘{’ | ‘[’ | ‘|’ | ‘\’ | ‘}’ | ‘]’ ) if US
| ( ‘!’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘'’ | ‘(’ | ‘)’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘/’
| ‘<’ | ‘>’ | ‘?’ | ‘@’ | ‘_’ | ‘:’ | ‘=’ ) if German
| ( ‘!’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘'’ | ‘(’ | ‘)’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘/’
| ‘<’ | ‘>’ | ‘?’ | ‘@’ | ‘_’ | ‘:’ | ‘=’ ) if Swedish
Remark: characters except SPACE, ‘"’, ‘,’, ‘;’, ‘`’, ‘^’, ‘~’
specName ::= ( ‘"’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘?’ | ‘@’ | ‘_’
| ‘^’ | ‘~’ | ‘{’ | ‘[’ | ‘|’ | ‘\’ | ‘}’ | ‘]’ ) if US
| ( ‘"’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘?’ | ‘@’ | ‘_’ | ‘^’ )if German
| ( ‘"’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘?’ | ‘@’ | ‘_’
| ‘^’ | ‘~’ ) if Swedish
Remark: except SPACE, ‘!’, ‘'’, ‘(’, ‘)’, ‘/’, ‘<’, ‘>’, ‘,’, ‘:’, ‘;’, ‘=’, ‘`’

D.2.1.2 Compound Character Sets

fileNameChar1 ::= letter | digit | ‘_’
anyChar ::= letter | national | digit | special
dbNameChar2 ::= letter | national | digit | specName
pcNameChar ::= anyChar | ‘;’
printable ::= anyChar | SPACE | ‘"’ | ‘,’ | ‘;’ | ‘^’ | ‘~’
Remark: all printable ANSI characters except ‘`’(apostrophe, accent grave)

1. fileNameChar corresponds to the common set of characters allowed by MS-DOS and VAX/VMS for file names.
2. The limitations of the sets dbNameChar and pcNameChar are mainly consequences of delimiters like ‘:’ or ‘,’ used
in AMPL source code (*.AAX, *.BAX).

3BDS 100 595R401 D-5

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

D.2.1.3 Tokens
integer ::= digit {digit}
fileName ::= fileNameChar {fileNameChar} Remark: max. 8 char
printableString ::= printable {printable}
anyString ::= anyChar {anyChar}
dbName ::= dbNameChar {dbNameChar}
pcName ::= ((letter | national) {letter | national | digit | ‘_’ })
| ‘(’ pcNameChar {pcNameChar} ‘)’

D.2.1.4 Keywords
VERSION | SECTION | HEAD | HEADER
| Design_Ch | Tech_Ref | Resp_Dept | Date | L_Text2 | L_Text3 | L_Text4
| R_Text1 | R_Text2 | R_Text3 | R_Text4 | Rev_ind | Language
| END_SECTION | SYMBOLS | TYPE | QUERY | DB | MODIFY | PC | PCD-PAGE
| INAME | TERMINAL | IN | OUT | FP | DBREF | INVERTABLE
| ADJUST | BLANKLINE | DYNAMIC | INVERTED | SUPCONTROL
| TC | $$IF | NOT | $$END_IF | $$LOOP | $$END_LOOP | $$LOOPCTR
| PC_TYPE | TC_TYPE | SYMBOL | CREATE | CONTROL
| STRUCTURE | ELEMENTS
| PCPGM | CONTRM | FUNCM | SEQ | STEP | MASTER | SLAVEM | ITEM_RANGE
| AND | OR | TRUE | FALSE | F
| B | I | IL | R | T | TR | A* | CB | CI | CIL | CR

D.2.1.5 Comments
::= ( “--” {any} eol ) | ( “(*” {any} “*)” )

D.2.1.6 Specials
eol ::= CR LF | FF
any ::= lexical unit (chain of characters) different from the following one

D-6 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.2.2 Syntactical Part (TCS File)

D.2.2 Syntactical Part (TCS File)

TCS_file ::= {eol}
tcVersion
tcDeclaration
tcType
headerSection
[tcSymbolSection]
[tcDbSection]
[tcPcSection]
{freeSection}
{eol}

tcVersion1 ::= VERSION TC integer(6) eol {eol}

Remark: Since Function Chart Editor version 3.1 TC version 3 is
expected, that is, the first non-comment line of a *.TCS file
must be: VERSION TC 3
tcDeclaration ::= TC tcName(8) eol {eol}
tcName ::= fileName
Remark: tcName must equal the name of the *.TCS file (without drive,
path, and extension).
tcType2 ::= TC_TYPE typeKeyword eol {eol}
typeKeyword ::= [SYMBOL] if symbol section exists
[DB if DB section exists
[MODIFY] if some DB element, which is not created in
this TC, is modified by this TC
[CREATE] ] if some DB element is created by this TC
[PC if PC section exists
(PCPGM | CONTRM | FUNCM | SEQ | STEP
| MASTER | SLAVEM | ELEMENTS)
reflects element(s) on highest level in TC
ITEM_RANGE integer]
number of elements on highest level in TC

1. For *.TCS files generated for Function Chart Editor version 3.0 use the utility UpTcCi to upgrade them.
2. TC_TYPE is a new syntactical element of the *.TCS file since Function Chart Editor version 3.0. It is a direct way
to feed backtranslators with information on TC type, and to increase their performance.

3BDS 100 595R401 D-7

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

headerSection ::= SECTION HEAD eol {eol}

[header]
END_SECTION HEAD eol {eol}
header1 ::= HEADER eol
[Design_Ch headerText(25) eol]
[Tech_Ref headerText(25) eol]
[Resp_Dept headerText(25) eol]
[Date headerText(25) eol]
[L_Text2 headerText(37) eol]
[L_Text3 headerText(37) eol]
[L_Text4 headerText(37) eol]
[R_Text1 headerText(27) eol]
[R_Text2 headerText(27) eol]
[R_Text3 headerText(27) eol]
[R_Text4 headerText(27) eol]
[Rev_ind headerText(3) eol]
[Language headerText(2) eol]
{eol}
headerText ::= printableString

tcSymbolSection::= SECTION SYMBOLS eol {eol}

{ tcTermOrSymbolLine
| ( $$IF2 [NOT] ‘<’ symbol(18) ‘>’ eol {eol}
{ tcTermOrSymbolLine }
$$END_IF eol {eol} )
| ( $$LOOP ‘<’ symbol(18) ‘>’ eol {eol}
{ tcTermOrSymbolLine }
$$END_LOOP eol {eol} )
} END_SECTION SYMBOLS eol {eol}

1. The header is, in fact, the footer of the diagrams.

The Function Chart Builder fills L_Text1 automatically, for example, with “DATABASE LISTING” for data base
listings, with “PC DIAGRAM” for function charts, or with “TREE LISTING” for tree diagrams.
2. Variants and loops ($$IF and $$LOOP) are distinctive advanced features of TC syntax. They are reserved for expert
users working directly on source code level. In the Function Chart Editor (since version 3.1) and Function Chart
Builder, the TC interpreter and the expander/checker support them, as opposed to the TC code generator, TC
backtranslator, and the editors.

D-8 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.2.2 Syntactical Part (TCS File)

symbol ::= anyString

tcTermOrSymbolLine ::= termLine | tcSymbolLine
termLine ::= termName(8) TERMINAL termNumber { flags | eol } termType
[eol] [ defaultConn ] ‘;’ eol {eol}
termName ::= anyString | loopCtrExpr
loopCtrExpr ::= [ anyString ] ‘<’ intLoopCtrExpr ‘>’ [ anyString ]
intLoopCtrExpr ::= addOper { (‘+’ | ‘-’) addOper}
addOper ::= mulOper { (‘*’ | ‘/’) mulOper}
mulOper ::= integer in general case
| $$LOOPCTR only within loop
termNumber ::= integer in general case
| termStartNumber only within loop
termStartNumber::= integer Remark: number of the first terminal created in the loop
flags ::= DBREF | INVERTABLE | ADJUST | BLANKLINE
| DYNAMIC | INVERTED | SUPCONTROL
termType ::= ( IN type ) | ( OUT type ) | ( FP type fpMinMax )
type ::= ( pcDataType [‘*’ pLength] ) | ( A* pLength ) | ( ‘<’ typeSymbol(18) ‘>’ )
pcDataType ::= I | IL | R | B | T | TR
pLength ::= integer | ( ‘<’ lengthSymbol(18) ‘>’ )
lengthSymbol ::= symbol
typeSymbol ::= symbol
fpMinMax ::= ‘(’ signedInteger “..” signedInteger ‘)’
signedInteger ::= [ ‘-’ ] integer
defaultConn ::= “:=” ‘"’ defaultValue ‘"’
defaultValue ::= tcSymbExpression | printableString
Remark: further limitation depending on the type of the symbol
tcSymbExpression1 ::=[anyString] ‘<’
(symbol
| $$LOOPCTR only within loop
| tcSymbExpression)
‘>’ [anyString]

1. The possibly nested tcSymbExpressions are interpreted successively until all involved terms are substituted by
constant values, and the operations are executed. The type of the so evaluated result has to correspond to the type of
the concerned symbol and terminal, respectively.

3BDS 100 595R401 D-9

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

tcSymbolLine ::= symbol(18) TYPE symbolType

( ( QUERY [“:=” tcSymbolVal ] ) if instance-unique (IU) symbol
| ( QUERY “:=” tcSymbolVal ) if variant or loop (VL) symbol
| ( “:=” tcSymbolVal ) ) ‘;’ eol {eol} if project-unique (PU) symbol
symbolType ::= B | CB | I | CI | IL | R | CR | T | TR | ( A* integer )
tcSymbolVal ::= defaultValue | (‘"’defaultValue‘"’)
| symbFormula only for calculated type symbols, that is, for
CB, CI, CIL, CR
symbFormula ::= ( ‘"’ expression ‘"’ ) | expression
expression ::= relOperand [relOperator relOperand]
relOperand ::= [‘+’ | ‘-’] addOperand {addOperator addOperand}
relOperator ::= ‘=’ | “<>” | ‘<’ | ‘>’ | “<=” | “>=”
addOperand ::= mulOperand {mulOperator mulOperand}
addOperator ::= ‘+’ | ‘-’ | OR
mulOperand ::= [ NOT ] tcExpOperand {expOperator tcExpOperand}
mulOperator ::= ‘*’ | ‘/’ | AND
tcExpOperand ::= constant | ( ‘<’ symbol ‘>’ )
| $$LOOPCTR only within loop
| ( ‘(’ expression ‘)’ )
constant ::= TRUE | T | FALSE | F | decimal
decimal ::=( ( ‘.’ digit {digit} ) | ( digit {digit} [ ‘.’ {digit} ] ) [‘E’ [‘+’|‘-’] digit {digit} ]
expOperator ::= ‘^’
tcDbSection ::= SECTION DB eol {eol}
{ dbElement
| ( $$IF [NOT] ‘<’ symbol(18) ‘>’ eol {eol}
{ dbElement }
$$END_IF eol {eol} )
| ( $$LOOP ‘<’ symbol(18) ‘>’ eol {eol}
{ dbElement }
$$END_LOOP eol {eol} )
} END_SECTION DB eol {eol}

D-10 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.2.2 Syntactical Part (TCS File)

dbElement ::= (createDbLine | modifyDbLine) {eol}

{( ‘:’terminalId dbTerminalValue eol {eol} )
| ( $$IF [NOT] ‘<’ symbol(18) ‘>’ eol {eol} if dbElement not in variant/loop
{ ‘:’terminalId dbTerminalValue eol {eol} }
$$END_IF eol {eol} )
| ( $$LOOP ‘<’ symbol(18) ‘>’ eol {eol} if dbElement not in variant/loop
{ ‘:’terminalId dbTerminalValue eol {eol} }
$$END_LOOP eol {eol} ) }
createDbLine ::= ((dbItemDesSup dbCallName(8)) | dbItemDesSub) eol
dbItemDesSup ::= dbRecordType(8) (elementNr(5) | ( ‘*’ [wildCardNr] ) | tcSymbExpression)
dbRecordType ::= “AAB_FILE” | “AI” | “AIC” | … Remark: superior and
independent record types depending on the actual DB element library
elementNr ::= integer | loopCtrExpr Remark: < 32K; loopCtrExpr only within loop
wildCardNr ::= integer | loopCtrExpr Remark: < 32K; loopCtrExpr only within loop
dbCallName ::= “AAB_FILE” | “AI” | “AIPT” | “AITC” | … Remark: superior and
independent call names depending on the actual DB element library
dbItemDesSub ::= dbRecordType(8) (elementNr(5) | ( ‘*’ [wildCardNr] )
| tcSymbExpression) ‘.’ (channelNr(5) | tcSymbExpression)
channelNr ::= integer | loopCtrExpr Remark: < 32K; loopCtrExpr only within loop
modifyDbLine ::= MODIFY dbIdentity eol
dbIdentity ::= dbItemDes | ( dbName(20) [dbCallNameAll(8)] )
Remark: for DS, DSP, and DAT elements only dbName(12)
dbItemDes ::= dbItemDesSup | dbItemDesSub
dbCallNameAll ::= AAB_FILE | AI | AIPT | AIPTS | AIS | … Remark: superior,
independent, and subordinate call names depending on the DB element library
terminalId ::= terminalNr only in PC section; for PC terminals and for
internal1, normally not reachable DB terminals
| terminalName in PC and DB sections, for PC or DB terminals
terminalNr ::= integer | loopCtrExpr Remark: values depending on the actual
element; loopCtrExpr only within loop
terminalName ::= anyChar {anyChar | ‘=’ } Remark: values depending on the element
dbTerminalValue::= tcSymbExpression | loopCtrExpr | printableString
Remark: values depending on the actual element; loopCtrExpr only within loop

1. Only for expert users, not for all node types.

3BDS 100 595R401 D-11

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

tcPcSection ::= SECTION PC eol {eol}

PC_TYPE pcType eol {eol}
{ (pcElement | pagination)
| ( $$IF [NOT] ‘<’ symbol(18) ‘>’ eol {eol}
{pcElement | pagination}
$$END_IF eol {eol} )
| ( $$LOOP ‘<’ symbol(18) ‘>’ eol {eol}
{pcElement | pagination}
$$END_LOOP eol {eol} )
} END_SECTION PC eol {eol}
pcType ::= CONTROL | STRUCTURE | ELEMENTS
pcElement ::= relativeItemDes pcElementCall [pcInstanceName] eol {eol}
{ ( ‘:’terminalId [pcInpTermAssign | pcOutTermAssign] eol {eol} )
| ( $$IF [NOT] ‘<’ symbol(18) ‘>’ eol {eol} if pcElement not in variant/loop
{‘:’terminalId [pcInpTermAssign | pcOutTermAssign] eol {eol} }
$$END_IF eol {eol} )
| ( $$LOOP ‘<’ symbol(18) ‘>’ eol {eol} if pcElement not in variant/loop
{‘:’terminalId [pcInpTermAssign | pcOutTermAssign] eol {eol} }
$$END_LOOP eol {eol} )
relativeItemDes ::= ‘*’ [‘+’ ( integer | loopCtrExpr ) ] {‘.’ ( integer | loopCtrExpr ) } eol
Remark: loopCtrExpr only within loop
pcElementCall ::= pcCallName [‘(’ callParam {‘,’ callParam} ‘)’]
callParam ::= integer | tcSymbExpression1 | loopCtrExpr
Remark: loopCtrExpr only within loop
pcCallName ::= “ABS” | “ADD” | “ADD-MR” | …
Remark: depending on the actual PC element library
pcInstanceName ::= INAME pcName(72)
pcInpTermAssign::= (pcName | loopCtrExpr) | fullTermId | ‘0’ | ‘1’
| (“T=” ‘<’ tcTermName ‘>’ ) ( ( ( [DB] ‘=’ dbIdentity)
| ( (‘D’ | “MD” | “CD” | “MCD” ) ‘=’ pcTermValue) ) [’,’ eol
“N=” (pcName | loopCtrExpr) ] [‘,’ eol “U=” (unit | loopCtrExpr) ] )
Remark: loopCtrExpr only within loop

1. Use of tcSymbExpressions as callParam is reserved for expert users working directly on source code level. In the
Function Chart Editor (since version 3.1) and Function Chart Builder, the TC interpreter and the expander/checker
support it, as opposed to the TC code generator, TC backtranslator, and PC editors.

D-12 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.2.3 On TC Source Code Syntax

fullTermId ::= relativeItemDes ‘:’ terminalId

tcTermName ::= anyString(8) | loopCtrExpr Remark: loopCtrExpr only within loop
pcTermValue ::= tcSymbExpression | loopCtrExpr | printableString
Remark: values depending on the actual PC terminal,
loopCtrExpr only within loop
unit ::= anyString(6)
pcOutTermAssign::= (“T=” ‘<’ tcTermName ‘>’ ) { ‘,’ eol [DB] ‘=’ dbIdentity} [ ‘,’ eol
“N=” (pcName | loopCtrExpr) ] [ ‘,’ eol “U=” (unit | loopCtrExpr) ] )
| ([DB] ‘=’ dbIdentity { ‘,’ eol [DB] ‘=’ dbIdentity} [ ‘,’ eol
“N=” (pcName | loopCtrExpr) ] [ ‘,’ eol “U=” (unit | loopCtrExpr) ] )
| (“N=” (pcName | loopCtrExpr) [’,’ eol “U=” (unit | loopCtrExpr) ] )
| (“U=” (unit | loopCtrExpr))
Remark: loopCtrExpr only within loop

pagination ::= PCD-PAGE [ pageNr ] [ relativeItemDes ] eol

[ ‘"’ printableString(77) ‘"’ eol
[ ‘"’ printableString(2) ‘"’ eol ] ]
pageNr ::= integer[’.’integer]

freeSection1 ::= SECTION noValidSection eol { eol | any }

END_SECTION noValidSection eol {eol}
noValidSection ::= anyString (except (HEAD | SYMBOLS | DB | PC) )

D.2.3 On TC Source Code Syntax

D.2.3.1 On Variants
The variant starts with the $$IF keyword.
The condition for the execution of the lines till $$END_IF is build by an optional inversion
([NOT]) and a variant or loop symbol (VL symbol) that must be of type Boolean and have a
default value.
This symbol must be declared before its usage and must not be placed in a variant or loop.
The variant ends with the keyword $$END_IF.
The user has to take care that the evaluation of all variants (and loops) in a type circuit instance
leads to no double symbols, DB elements, or PC elements.

1. freeSection is a dummy part of *.TCS, it is not evaluated

3BDS 100 595R401 D-13

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

D.2.3.2 Placement of Variants

Variants can be placed in the symbol, DB, and PC section of a type circuit around one or more
terminal or symbol lines, DB elements or DB properties, PC elements or PC terminals,
PCD-PAGE instructions.
You have to meet the following conditions:
• Variants must start after the start of the section and end before the end of the section they
started in.
• Variants must not be nested, nor placed in a loop.
• Variant symbols must be declared before their usage. Take care in symbol section.
• Variant symbols must not be declared in a variant or a loop.

D.2.3.3 On Loops
The loop starts with the $$LOOP keyword and ends with the $$END_LOOP keyword.
The maximum number of repetitions of execution of the lines till $$END_LOOP is build by a
VL symbol that stands after $$LOOP and that must be of type integer and that must have a
default value. This loop symbol must be declared before its usage and must not be placed in a
variant or loop.
With every loop an implicit symbol $$LOOPCTR is created. It is incremented after each
execution of the loop body. The valid range of the loop counter $$LOOPCTR is from 1 to the
default value of the loop symbol.
Within the loop simple expressions may be built by $$LOOPCTR, integer constants, and
arithmetical operators ‘*’, ‘+’, and ‘-’.
$$LOOPCTR can be used only within a loop between $$LOOP and $$END_LOOP.
The user has to take care that the evaluation of all loops (and variants) in a type circuit instance
leads to no double symbols, DB elements, or PC elements.

D.2.3.4 Placement of Loops

Loops can be placed in the symbol, DB, and PC section of a type circuit around one or more
terminal or symbol lines, DB elements or DB properties, PC elements or PC terminals, and
around PCD-PAGE instructions.
You have to meet the following conditions:
• Loops must start after the start of the section and end before the end of the section they
started in.
• Loops must not be nested, nor placed in a variant.
• Loop symbols must be declared before their usage. Take care in symbol section.
• Loop symbols must not be declared in a variant or a loop.

D-14 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.2.3 On TC Source Code Syntax

D.2.3.5 Symbols in Symbol Section of *.TCS and Their Scope

Symbol Kinds
The kind of symbols in the symbol section of *.TCS is one of the following:
• Instance-unique (IU)
• Variant or loop (VL)
• Project-unique (PU)
A symbol is created by its occurrence in the symbol section.

Assignment of Values to IU and VL Symbols

IU and VL symbol values can be assigned upon query during instantiation in a node, or are set
by
{ SET symbol TO symbolVal [NOMODIFY] ‘;’ eol }
lines as part of a TC instantiation in *.CIS and *.NSS files (see description of these files).
IU and VL symbol values are valid locally in the TC instance.

Assignment of Values to PU Symbols

PU symbols must have (local) default values. These symbols are announced by
{ EXPORT symbol [ := symbolVal ] ‘;’ eol }
lines as part of a TC instantiation in *.CIS and *.NSS files.
Here, these values can be overwritten by values of PU, LU, or IU symbols of the same name and
type from the calling *.CIS file and by values of PU symbols of the same name and type from
the calling *.NSS file at each instantiation of the TC. So, PU symbols are global.

D.2.3.6 On Nested Symbolic Expressions

defaultValue, dbItemDesXxx, dbTerminalValue, callParam, pcTermValue may contain nested
tcSymbExpressions. They are interpreted successively until all involved terms are substituted by
constant values, and the operations are executed. The type of the so evaluated result has to
correspond to the type of the concerned symbol and terminal, respectively.

D.2.3.7 On Formulas

Occurrence
A formula can occur as tcSymbolVal only for calculated type symbols:
CB, CI, CIL, CR.

3BDS 100 595R401 D-15

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

Calculating by Formulas
Operands of all types and all the operators are allowed in a formula, no matter what is the type
of the symbol, the value of which is to be calculated.
Steps of calculation:
1. The operands are at first converted internally to real values.
2. All operations (also the Boolean ones!) are then executed with real values.
For Boolean operations 0.00 is considered to be FALSE,
all nonzero values are considered to be TRUE.
3. At the end the real result is converted to B, I, or IL or left R depending on the symbol,
the value of which was to be calculated on the base of the formula.

D.3 Syntax of CI Source Code

D.3.1 Lexical Part

D.3.1.1 Simple Character Sets

digit ::= ‘0’..‘9’
letter ::= ‘a’..’z’ | ‘A’..’Z’
national ::= () empty if US
| (‘ä’ | ‘Ä’ | ‘ö’ | ‘Ö’ | ‘ü’ | ‘Ü’ | ‘ß’) if German
| (‘ä’ | ‘Ä’ | ‘ö’ | ‘Ö’ | ‘å’ | ‘Å’) if Swedish
special ::= ( ‘!’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘'’ | ‘(’ | ‘)’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘/’
| ‘<’ | ‘>’ | ‘?’ | ‘@’ | ‘_’ | ‘:’ | ‘=’ | ‘{’ | ‘[’ | ‘|’ | ‘\’ | ‘}’ | ‘]’ ) if US
| ( ‘!’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘'’ | ‘(’ | ‘)’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘/’
| ‘<’ | ‘>’ | ‘?’ | ‘@’ | ‘_’ | ‘:’ | ‘=’ ) if German
| ( ‘!’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘'’ | ‘(’ | ‘)’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘/’
| ‘<’ | ‘>’ | ‘?’ | ‘@’ | ‘_’ | ‘:’ | ‘=’ ) if Swedish
Remark: characters except SPACE, ‘"’, ‘,’, ‘;’, ‘`’, ‘^’, ‘~’
specName ::= ( ‘"’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘?’ | ‘@’ | ‘_’
| ‘^’ | ‘~’ | ‘{’ | ‘[’ | ‘|’ | ‘\’ | ‘}’ | ‘]’ ) if US
| ( ‘"’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘?’ | ‘@’ | ‘_’ | ‘^’ )if German
| ( ‘"’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘?’ | ‘@’ | ‘_’
| ‘^’ | ‘~’ ) if Swedish
Remark: except SPACE, ‘!’, ‘'’, ‘(’, ‘)’, ‘/’, ‘<’, ‘>’, ‘,’, ‘:’, ‘;’, ‘=’, ‘`’

D-16 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.3.1 Lexical Part

D.3.1.2 Compound Character Sets

fileNameChar1 ::= letter | digit | ‘_’
anyChar ::= letter | national | digit | special
dbNameChar2 ::= letter | national | digit | specName
pcNameChar ::= anyChar | ‘;’
printable ::= anyChar | SPACE | ‘"’ | ‘,’ | ‘;’ | ‘^’ | ‘~’
Remark: all printable ANSI characters except ‘`’(apostrophe, accent grave)

D.3.1.3 Tokens
integer ::= digit {digit}
fileName ::= fileNameChar {fileNameChar} Remark: max. 8 char
printableString ::= printable {printable}
anyString ::= anyChar {anyChar}
dbName ::= dbNameChar {dbNameChar}
pcName ::= ((letter | national) {letter | national | digit | ‘_’ })
| ‘(’ pcNameChar {pcNameChar} ‘)’

D.3.1.4 Keywords
VERSION | SECTION | HEAD | HEADER
| Design_Ch | Tech_Ref | Resp_Dept | Date | L_Text2 | L_Text3 | L_Text4
| R_Text1 | R_Text2 | R_Text3 | R_Text4 | Rev_ind | Language
| END_SECTION | SYMBOLS | TYPE | QUERY | DB | MODIFY | PC | PCD-PAGE
| INAME | TERMINAL | IN | OUT | FP | DBREF | INVERTABLE
| ADJUST | BLANKLINE | DYNAMIC | INVERTED | SUPCONTROL
| CI| PRIVATE | $$TC | EXPORT | SET | TO | NOMODIFY
| CI_TYPE | SYMBOL | CREATE | CONTROL | STRUCTURE | ELEMENTS
| PCPGM | CONTRM | FUNCM | SEQ | STEP | MASTER | SLAVEM | ITEM_RANGE
| NOT | AND | OR | TRUE | FALSE | F
| B | I | IL | R | T | TR | A* | CB | CI | CIL | CR

1. fileNameChar corresponds to the common set of characters allowed by MS-DOS and VAX/VMS for file names.
2. The limitations of the sets dbNameChar and pcNameChar are mainly consequences of delimiters like ‘:’ or ‘,’ used
in AMPL source code (*.AAX, *.BAX).

3BDS 100 595R401 D-17

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

D.3.1.5 Comments
::= ( “--” {any} eol ) | ( “(*” {any} “*)” )

D.3.1.6 Specials
eol ::= CR LF | FF
any ::= lexical unit (chain of characters) different from the following one

D.3.2 Syntactical Part (CIS File)

CIS_file ::= {eol}
ciVersion
ciDeclaration
ciType
headerSection
[ciSymbolSection]
[ciDbSection]
[ciPcSection]
{freeSection}
{eol}

ciVersion1 ::= VERSION CI integer(6) eol {eol}

Remark: Since Function Chart Editor version 3.1 CI version 3 is
expected, that is, the first non-comment line of a *.CIS file
must be: VERSION CI 3
ciDeclaration ::= CI ciName(8) eol {eol}
ciName ::= fileName
Remark: ciName must equal the name of the *.CIS file (without drive,
path, and extension).
ciType2 ::= CI_TYPE typeKeyword eol {eol}

1. For *.CIS files generated for Function Chart Editor version 3.0 use the utility UpTcCi to upgrade them.
2. CI_TYPE is a new syntactical element of the *.CIS file since Function Chart Editor version 3.0. It is a direct way to
feed backtranslators with information on CI type, and to increase their performance.

D-18 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.3.2 Syntactical Part (CIS File)

typeKeyword ::= [SYMBOL] if symbol section exists

[DB if DB section exists
[MODIFY] if some DB element, which is not created in
this CI, is modified by this CI
[CREATE] ] if some DB element is created by this CI
[PC if PC section exists
(PCPGM | CONTRM | FUNCM | SEQ | STEP
| MASTER | SLAVEM | ELEMENTS)
reflects element(s) on highest level in CI
ITEM_RANGE integer]
number of elements on highest level in CI
headerSection ::= SECTION HEAD eol {eol}
[header]
END_SECTION HEAD eol {eol}

header1 ::= HEADER eol

[Design_Ch headerText(25) eol]
[Tech_Ref headerText(25) eol]
[Resp_Dept headerText(25) eol]
[Date headerText(25) eol]
[L_Text2 headerText(37) eol]
[L_Text3 headerText(37) eol]
[L_Text4 headerText(37) eol]
[R_Text1 headerText(27) eol]
[R_Text2 headerText(27) eol]
[R_Text3 headerText(27) eol]
[R_Text4 headerText(27) eol]
[Rev_ind headerText(3) eol]
[Language headerText(2) eol]
{eol}
headerText ::= printableString

1. The header is, in fact, the footer of the diagrams.

The Function Chart Builder fills L_Text1 automatically, for example, with “DATABASE LISTING” for data base
listings, with “PC DIAGRAM” for function charts, or with “TREE LISTING” for tree diagrams.

3BDS 100 595R401 D-19

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

ciSymbolSection::= SECTION SYMBOLS eol {eol}

{ ciTermOrSymbolLine }
END_SECTION SYMBOLS eol {eol}
ciTermOrSymbolLine::= termLine | ciSymbolLine
termLine ::= termName(8) TERMINAL termNumber { flags | eol } termType
[eol] [ defaultConn ] ‘;’ eol {eol}
termName ::= anyString
termNumber ::= integer
flags ::= DBREF | INVERTABLE | ADJUST | BLANKLINE
| DYNAMIC | INVERTED | SUPCONTROL
termType ::= ( IN type ) | ( OUT type ) | ( FP type fpMinMax )
type ::= ( pcDataType [‘*’ pLength] ) | ( A* pLength ) | ( ‘<’ typeSymbol(18) ‘>’ )
pcDataType ::= I | IL | R | B | T | TR
pLength ::= integer | ( ‘<’ lengthSymbol(18) ‘>’ )
lengthSymbol ::= symbol
symbol ::= anyString
typeSymbol ::= symbol
fpMinMax ::= ‘(’ signedInteger “..” signedInteger ‘)’
signedInteger ::= [ ‘-’ ] integer
defaultConn ::= “:=” ‘"’ defaultValue ‘"’
defaultValue ::= symbExpression | printableString
Remark: further limitation depending on the type of the symbol
symbExpression 1 ::=[anyString] ‘<’ (symbol | symbExpression) ‘>’ [anyString]
ciSymbolLine ::= symbol(18) TYPE symbolType
( ( QUERY [“:=” symbolVal ] ) if instance-unique (IU) symbol
| ( PRIVATE “:=” symbolVal ) if location-unique (LU)
symbol
| ( “:=” symbolVal ) ) if project-unique (PU) symbol
‘;’ eol {eol}
symbolType ::= B | CB | I | CI | IL | R | CR | T | TR | ( A* integer )

1. The possibly nested symbExpressions are interpreted successively until all involved terms are substituted by
constant values, and the operations are executed. The type of the so evaluated result has to correspond to the type of
the concerned symbol and terminal, respectively.

D-20 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.3.2 Syntactical Part (CIS File)

symbolVal ::= defaultValue | (‘"’defaultValue‘"’)

| symbFormula only for calculated type symbols, that is, for
CB, CI, CIL, CR
symbFormula ::= ( ‘"’ expression ‘"’ ) | expression
expression ::= relOperand [relOperator relOperand]
relOperand ::= [‘+’ | ‘-’] addOperand {addOperator addOperand}
relOperator ::= ‘=’ | “<>” | ‘<’ | ‘>’ | “<=” | “>=”
addOperand ::= mulOperand {mulOperator mulOperand}
addOperator ::= ‘+’ | ‘-’ | OR
mulOperand ::= [ NOT ] expOperand {expOperator expOperand}
mulOperator ::= ‘*’ | ‘/’ | AND
expOperand ::= constant | ( ‘<’ symbol ‘>’ ) | ( ‘(’ expression ‘)’ )
constant ::= TRUE | T | FALSE | F | decimal
decimal ::=( ( ‘.’ digit {digit} ) | ( digit {digit} [ ‘.’ {digit} ] ) [‘E’ [‘+’|‘-’] digit {digit} ]
expOperator ::= ‘^’

ciDbSection ::= SECTION DB eol {eol}

{ dbElement | tcInstInDb }
END_SECTION DB eol {eol}
dbElement ::= (createDbLine | modifyDbLine) {eol}
{‘:’terminalId dbTerminalValue eol {eol} }
createDbLine ::= ((dbItemDesSup dbCallName(8)) | dbItemDesSub) eol
dbItemDesSup ::= dbRecordType(8) (elementNr(5) | ( ‘*’ [wildCardNr] ) | symbExpression)
dbRecordType ::= “AAB_FILE” | “AI” | “AIC” | … Remark: superior and
independent record types depending on the actual DB element library
elementNr ::= integer Remark: < 32K
wildCardNr ::= integer Remark: < 32K
dbCallName ::= “AAB_FILE” | “AI” | “AIPT” | “AITC” | … Remark: superior and
independent call names depending on the actual DB element library
dbItemDesSub ::= dbRecordType(8) (elementNr(5) | ( ‘*’ [wildCardNr] ) | symbExpression)
‘.’ (channelNr(5) | symbExpression)
channelNr ::= integer Remark: < 32K
modifyDbLine ::= MODIFY dbIdentity eol
dbIdentity ::= dbItemDes | ( dbName(20) [dbCallNameAll(8)] )
Remark: for DS, DSP, and DAT elements only dbName(12)

3BDS 100 595R401 D-21

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

dbItemDes ::= dbItemDesSup | dbItemDesSub

dbCallNameAll ::= AAB_FILE | AI | AIPT | AIPTS | AIS | … Remark: superior,
independent and subordinate call names depending on the DB element library
terminalId ::= terminalNr only in PC section; for PC terminals and for
internal1, normally not reachable DB terminals
| terminalName in PC and DB sections, for PC or DB terminals
terminalNr ::= integer Remark: values depending on the actual element
terminalName ::= anyChar {anyChar | ‘=’ } Remark: values depending on the element
dbTerminalValue::= symbExpression | printableString
Remark: values depending on the actual DB terminal
tcInstInDb ::= $$TC tcTypeName [tcDbInstanceName] eol
{SET symbol TO symbolVal [NOMODIFY] ‘;’ eol}
{EXPORT symbol [“:=” symbolVal] ‘;’ eol} {eol}
tcTypeName ::= fileName
tcDbInstanceName ::= INAME dbName(72)
ciPcSection ::= SECTION PC eol {eol}
PC_TYPE pcType eol {eol}
{ (pcElement | pagination | tcInstInPc }
} END_SECTION PC eol {eol}
pcType ::= CONTROL | STRUCTURE | ELEMENTS
pcElement ::= relativeItemDes pcElementCall [pcInstanceName] eol {eol}
{‘:’terminalId [pcInpTermAssign | pcOutTermAssign] eol {eol} }
relativeItemDes ::= ‘*’ [‘+’ integer ] {‘.’ integer} eol
pcElementCall ::= pcCallName [‘(’ callParam {‘,’ callParam} ‘)’]
callParam ::= integer | symbExpression2
pcCallName ::= “ABS” | “ADD” | “ADD-MR” | …
Remark: depending on the actual PC element library
pcInstanceName ::= INAME pcName(72)
pcInpTermAssign::= pcName | fullTermId | ‘0’ | ‘1’
| (“T=” ‘<’ ciTermName ‘>’ ) ( ( ( [DB] ‘=’ dbIdentity)
| ( (‘D’ | “MD” | “CD” | “MCD” ) ‘=’ pcTermValue) ) [’,’ eol
“N=” pcName ] [‘,’ eol “U=” unit ] )

1. Only for expert users, not for all node types.

2. Use of symbExpressions as callParam is reserved for expert users working directly on source code level. In the
Function Chart Editor (since version 3.1) and the Function Chart Builder, the expander/checker supports it, as
opposed to the CI code generator, CI backtranslator, and the PC editors.

D-22 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.3.3 On CI Source Code Syntax

fullTermId ::= relativeItemDes ‘:’ terminalId

ciTermName ::= anyString(8)
pcTermValue ::= symbExpression | printableString
Remark: values depending on the actual PC terminal
unit ::= anyString(6)
pcOutTermAssign::= (“T=” ‘<’ ciTermName ‘>’ ) { ‘,’ eol [DB] ‘=’ dbIdentity} [ ‘,’ eol
“N=” pcName ] [ ‘,’ eol “U=” unit ] )
| ([DB] ‘=’ dbIdentity { ‘,’ eol [DB] ‘=’ dbIdentity} [ ‘,’ eol
“N=” pcName ] [ ‘,’ eol “U=” unit ] )
| (“N=” pcName [’,’ eol “U=” unit ] )
| (“U=” unit)
tcInstInPc ::= relativeItemDes $$TC tcTypeName [tcPcInstanceName] eol
{SET symbol TO symbolVal [NOMODIFY] ‘;’ eol}
{EXPORT symbol [“:=” symbolVal] ‘;’ eol}
{‘:’tcTerminalId [pcInpTermAssign | pcOutTermAssign] eol {eol} }
tcPcInstanceName ::= INAME pcName(72)
tcTerminalId ::= terminalId
pagination ::= PCD-PAGE [ pageNr ] [ relativeItemDes ] eol
[ ‘"’ printableString(77) ‘"’ eol
[ ‘"’ printableString(2) ‘"’ eol ] ]
pageNr ::= integer[’.’integer]

freeSection1 ::= SECTION noValidSection eol { eol | any }

END_SECTION noValidSection eol {eol}
noValidSection ::= anyString (except (HEAD | SYMBOLS | DB | PC) )

D.3.3 On CI Source Code Syntax

D.3.3.1 Variants and Loops

No variants and no loops are allowed in *.CIS.

1. freeSection is a dummy part of *.CIS, it is not evaluated

3BDS 100 595R401 D-23

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

D.3.3.2 Symbols in Symbol Section of *.CIS and Their Scope

Symbol Kinds
The kind of symbols in the symbol section of *.CIS is one of the following:
• Instance-unique (IU)
• Location-unique (LU)
• Project-unique (PU).
A symbol is created by its occurrence in the symbol section.

Assignment of Values to IU Symbols

IU symbol values are valid locally in a given CI and overwrite the PU symbols with the same
name and of the same type in TC instances within this CI.
So, IU symbols are “downwards” global.
IU symbols are always queried at the location of the CI.
This is reflected by
{ SET symbol TO symbolVal [NOMODIFY] ‘;’ eol }
lines as part of a CI location in *.NSS files. See description of *.NSS file.

Assignment of Values to LU Symbols

LU symbol values are valid locally in a given CI and overwrite the PU symbols with the same
name and of the same type in TC instances within this CI.
So, LU symbols are “downwards” global.
LU symbols are not queried and have always default values.
When located they are confirmed by
{ SET symbol TO symbolVal [NOMODIFY] ‘;’ eol }
lines as part of a CI location in *.NSS files.

Assignment of Values to PU Symbols

PU symbols must have (local) default values and are not queried.
These symbols are announced by
{ EXPORT symbol [ := symbolVal ] ‘;’ eol }
lines as part of a CI location in *.NSS files.
The PU symbol values of CI can be overwritten by values of PU symbols of the same name in
the calling *.NSS file at the location of the CI.
PU symbol values in CI again overwrite the PU symbols with the same name in TC instances
within this CI.
So, PU symbols are global.

D-24 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.3.3 On CI Source Code Syntax

D.3.3.3 On Nested Symbolic Expressions

defaultValue, dbItemDesXxx, dbTerminalValue, callParam, pcTermValue may contain nested
symbExpressions. They are interpreted successively until all involved terms are substituted by
constant values, and the operations are executed. The type of the so evaluated result has to
correspond to the type of the concerned symbol and terminal, respectively.

D.3.3.4 On Formulas

Occurrence
A formula can occur as symbolVal only for calculated type symbols:
CB, CI, CIL, CR.

Calculating by Formulas
Operands of all types and all the operators are allowed in a formula, no matter what is the type
of the symbol, the value of which is to be calculated.
Steps of calculation:
1. The operands are at first converted internally to real values.
2. All operations (also the Boolean ones!) are then executed with real values.
For Boolean operations 0.00 is considered to be FALSE,
all nonzero values are considered to be TRUE.
3. At the end the real result is converted to B, I, or IL or left R depending on the symbol,
the value of which was to be calculated on the base of the formula.

D.3.3.5 TCs Instantiated in CI

Referencing TC Instances in CI
A TC instance is indicated by $$TC.
It must be followed by a full interface specification of the given TC with its IU and VL symbols:
$$TC tcTypeName [ INAME ( pcName(72) | dbName(72) ) ] eol
{ SET symbol TO symbolVal [NOMODIFY] ‘;’ eol }
and value assignments for its PU symbols:
{ EXPORT symbol [ := symbolVal ] ‘;’ eol }
The optional keyword NOMODIFY indicates that the value must not be changed. It is applied
for symbols that change the interface (number, type, name of symbols) of the concerned TC.

3BDS 100 595R401 D-25

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

TC Instances in Different Sections of a CI

The DB section of a CI may have TC instances (possibly several of each type) that contain DB
elements, possibly symbol declarations but no PC related elements. These TC instances contain
PU and/or IU symbols.
The PC section of a CI may have TC instances (possibly several of each type) that contain PC
related elements and possibly symbol declarations and DB elements, too. These TC instances
contain PU and/or IU symbols.
The DB and PC sections contain used symbols.

Distinction of TC Instances
Instantiated TCs can have unique instance names introduced by the keyword INAME.
The different instances of a TC can be distinguished also without instance names in two ways
depending on the section where the TC is instantiated:
• In the PC section every instance has another item designation.
• In the DB section the different instances of one TC must have different IU symbol values.

D.4 Syntax of NS Source Code

D.4.1 Lexical Part

D.4.1.1 Simple Character Sets

digit ::= ‘0’..‘9’
letter ::= ‘a’..’z’ | ‘A’..’Z’
national ::= () empty if US
| (‘ä’ | ‘Ä’ | ‘ö’ | ‘Ö’ | ‘ü’ | ‘Ü’ | ‘ß’) if German
| (‘ä’ | ‘Ä’ | ‘ö’ | ‘Ö’ | ‘å’ | ‘Å’) if Swedish
special ::= ( ‘!’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘'’ | ‘(’ | ‘)’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘/’
| ‘<’ | ‘>’ | ‘?’ | ‘@’ | ‘_’ | ‘:’ | ‘=’ | ‘{’ | ‘[’ | ‘|’ | ‘\’ | ‘}’ | ‘]’ ) if US
| ( ‘!’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘'’ | ‘(’ | ‘)’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘/’
| ‘<’ | ‘>’ | ‘?’ | ‘@’ | ‘_’ | ‘:’ | ‘=’ ) if German
| ( ‘!’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘'’ | ‘(’ | ‘)’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘/’
| ‘<’ | ‘>’ | ‘?’ | ‘@’ | ‘_’ | ‘:’ | ‘=’ ) if Swedish
Remark: characters except SPACE, ‘"’, ‘,’, ‘;’, ‘`’, ‘^’, ‘~’

D-26 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.4.1 Lexical Part

specName ::= ( ‘"’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘?’ | ‘@’ | ‘_’
| ‘^’ | ‘~’ | ‘{’ | ‘[’ | ‘|’ | ‘\’ | ‘}’ | ‘]’ ) if US
| ( ‘"’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘?’ | ‘@’ | ‘_’ | ‘^’ )if German
| ( ‘"’ | ‘#’ | ‘$’ | ‘%’ | ‘&’ | ‘*’ | ‘+’ | ‘-’ | ‘.’ | ‘?’ | ‘@’ | ‘_’
| ‘^’ | ‘~’ ) if Swedish
Remark: except SPACE, ‘!’, ‘'’, ‘(’, ‘)’, ‘/’, ‘<’, ‘>’, ‘,’, ‘:’, ‘;’, ‘=’, ‘`’

D.4.1.2 Compound Character Sets

fileNameChar1 ::= letter | digit | ‘_’
anyChar ::= letter | national | digit | special
dbNameChar2 ::= letter | national | digit | specName
pcNameChar ::= anyChar | ‘;’
printable ::= anyChar | SPACE | ‘"’ | ‘,’ | ‘;’ | ‘^’ | ‘~’
Remark: all printable ANSI characters except ‘`’(apostrophe, accent grave)

D.4.1.3 Tokens
integer ::= digit {digit}
fileName ::= fileNameChar {fileNameChar} Remark: max. 8 char
printableString ::= printable {printable}
anyString ::= anyChar {anyChar}
dbName ::= dbNameChar {dbNameChar}
pcName ::= ((letter | national) {letter | national | digit | ‘_’ })
| ‘(’ pcNameChar {pcNameChar} ‘)’

D.4.1.4 Keywords
VERSION | SECTION | HEAD | HEADER
| Design_Ch | Tech_Ref | Resp_Dept | Date | L_Text2 | L_Text3 | L_Text4
| R_Text1 | R_Text2 | R_Text3 | R_Text4 | Rev_ind | Language
| END_SECTION | SYMBOLS | TYPE | DB | MODIFY | PC | PCD-PAGE
| INAME | NS | $$TC | $$CI | EXPORT | SET | TO | NOMODIFY
| NOT | AND | OR | TRUE | FALSE | F
| B | I | IL | R | T | TR | A* | CB | CI | CIL | CR

1. fileNameChar corresponds to the common set of characters allowed by MS-DOS and VAX/VMS for file names.
2. The limitations of the sets dbNameChar and pcNameChar are mainly consequences of delimiters like ‘:’ or ‘,’ used
in AMPL source code (*.AAX, *.BAX).

3BDS 100 595R401 D-27

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

D.4.1.5 Comments
::= ( “--” {any} eol ) | ( “(*” {any} “*)” )

D.4.1.6 Specials
eol ::= CR LF | FF
any ::= lexical unit (chain of characters) different from the following one

D.4.2 Syntactical Part (NSS File)

NSS_file ::= {eol}
nsVersion
nsDeclaration
headerSection
[nsSymbolSection]
[nsDbSection]
[nsPcSection]
{freeSection}
{eol}

nsVersion ::= VERSION NS integer(6) eol {eol}

Remark: NS version 2 is expected, that is, the first non-comment line
of a *.NSS file must be: VERSION NS 2

nsDeclaration ::= NS nsName(8) eol {eol}

nsName ::= fileName

Remark: nsName must equal the name of the *.NSS file (without drive,
path, and extension).

headerSection ::= SECTION HEAD eol {eol}

[header]
END_SECTION HEAD eol {eol}

D-28 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.4.2 Syntactical Part (NSS File)

header1 ::= HEADER eol

[Design_Ch headerText(25) eol]
[Tech_Ref headerText(25) eol]
[Resp_Dept headerText(25) eol]
[Date headerText(25) eol]
[L_Text2 headerText(37) eol]
[L_Text3 headerText(37) eol]
[L_Text4 headerText(37) eol]
[R_Text1 headerText(27) eol]
[R_Text2 headerText(27) eol]
[R_Text3 headerText(27) eol]
[R_Text4 headerText(27) eol]
[Rev_ind headerText(3) eol]
[Language headerText(2) eol]
{eol}

headerText ::= printableString

nsSymbolSection::= SECTION SYMBOLS eol {eol}

{ nsSymbolLine }
END_SECTION SYMBOLS eol {eol}
nsSymbolLine ::= symbol(18) TYPE symbolType “:=” symbolVal ‘;’ eol {eol}
Remark: Apply only to PU symbols defined in referenced CIs and TCs.
symbol ::= anyString
symbolType ::= B | CB | I | CI | IL | R | CR | T | TR | ( A* integer )
symbolVal ::= defaultValue | (‘"’defaultValue‘"’)
| symbFormula only for calculated type symbols, that is, for
CB, CI, CIL, CR
defaultValue ::= symbExpression | printableString
Remark: further limitation depending on the type of the symbol

1. The header is, in fact, the footer of the diagrams.

The Function Chart Builder fills L_Text1 automatically, for example, with “DATABASE LISTING” for data base
listings, with “PC DIAGRAM” for function charts, or with “TREE LISTING” for tree diagrams.

3BDS 100 595R401 D-29

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

symbExpression 1::=[anyString] ‘<’ (symbol | symbExpression) ‘>’ [anyString]

symbFormula ::= ( ‘"’ expression ‘"’ ) | expression
expression ::= relOperand [relOperator relOperand]
relOperand ::= [‘+’ | ‘-’] addOperand {addOperator addOperand}
relOperator ::= ‘=’ | “<>” | ‘<’ | ‘>’ | “<=” | “>=”
addOperand ::= mulOperand {mulOperator mulOperand}
addOperator ::= ‘+’ | ‘-’ | OR
mulOperand ::= [ NOT ] expOperand {expOperator expOperand}
mulOperator ::= ‘*’ | ‘/’ | AND
expOperand ::= constant | ( ‘<’ symbol ‘>’ ) | ( ‘(’ expression ‘)’ )
constant ::= TRUE | T | FALSE | F | decimal
decimal ::=( ( ‘.’ digit {digit} ) | ( digit {digit} [ ‘.’ {digit} ] ) [‘E’ [‘+’|‘-’] digit {digit} ]
expOperator ::= ‘^’

nsDbSection ::= SECTION DB eol {eol}

{ dbElement | tcInstInDb | ciLocInDb }
END_SECTION DB eol {eol}
dbElement ::= (createDbLine | modifyDbLine) {eol}
{‘:’terminalId dbTerminalValue eol {eol} }
createDbLine ::= ((dbItemDesSup dbCallName(8)) | dbItemDesSub) eol
dbItemDesSup ::= dbRecordType(8) (elementNr(5) | symbExpression)
dbRecordType ::= “AAB_FILE” | “AI” | “AIC” | … Remark: superior and
independent record types depending on the actual DB element library
elementNr ::= integer Remark: < 32K
dbCallName ::= “AAB_FILE” | “AI” | “AIPT” | “AITC” | … Remark: superior and
independent call names depending on the actual DB element library
dbItemDesSub ::= dbRecordType(8) (elementNr(5) | symbExpression)
‘.’ (channelNr(5) | symbExpression)
channelNr ::= integer Remark: < 32K
modifyDbLine ::= MODIFY dbIdentity eol
dbIdentity ::= dbItemDes | ( dbName(20) [dbCallNameAll(8)] )
Remark: for DS, DSP, and DAT elements only dbName(12)

1. The possibly nested symbExpressions are interpreted successively until all involved terms are substituted by
constant values, and the operations are executed. The type of the so evaluated result has to correspond to the type of
the concerned symbol and terminal, respectively.

D-30 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.4.2 Syntactical Part (NSS File)

dbItemDes ::= dbItemDesSup | dbItemDesSub

dbCallNameAll ::= AAB_FILE | AI | AIPT | AIPTS | AIS | … Remark: superior,
independent and subordinate call names depending on the DB element library
terminalId ::= terminalNr only in PC section; for PC terminals and for
internal1, normally not reachable DB terminals
| terminalName in PC and DB sections, for PC or DB terminals
terminalNr ::= integer Remark: values depending on the actual element
terminalName ::= anyChar {anyChar | ‘=’ } Remark: values depending on the element
dbTerminalValue::= symbExpression | printableString
Remark: values depending on the actual DB terminal
tcInstInDb ::= $$TC tcTypeName [tcDbInstanceName] eol
{SET symbol TO symbolVal [NOMODIFY] ‘;’ eol}
{EXPORT symbol [“:=” symbolVal] ‘;’ eol} {eol}
tcTypeName ::= fileName
tcDbInstanceName ::= INAME dbName(72)

ciLocInDb ::= $$CI circuitName [ciDbInstanceName] eol

{SET symbol TO symbolVal [NOMODIFY] ‘;’ eol}
{EXPORT symbol [“:=” symbolVal] ‘;’ eol} {eol}
circuitName ::= fileName
ciDbInstanceName ::= INAME dbName(72)
nsPcSection ::= SECTION PC eol {eol}
{ (pcElement | pagination | tcInstInPc | ciLocInPc }
} END_SECTION PC eol {eol}
pcElement ::= itemDesignation pcElementCall [pcInstanceName] eol {eol}
{‘:’terminalId [pcInpTermAssign | pcOutTermAssign] eol {eol} }
itemDesignation::= “PC” [‘.’ integer {‘.’ integer} ] eol
pcElementCall ::= pcCallName [‘(’ callParam {‘,’ callParam } ‘)’]
callParam ::= integer | symbExpression2
pcCallName ::= “ABS” | “ADD” | “ADD-MR” | …
Remark: depending on the actual PC element library
pcInstanceName ::= INAME pcName(72)

1. Only for expert users, not for all node types.

2. Use of symbExpressions as callParam is reserved for expert users working directly on source code level. In the
Function Chart Editor (since version 3.1) and Function Chart Builder, the expander/checker supports it, as opposed
to the NS code generator, NS backtranslator, and PC editors.

3BDS 100 595R401 D-31

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

pcInpTermAssign::= pcName | fullTermId | ‘0’ | ‘1’

| ( ( ( [DB] ‘=’ dbIdentity)
| ( (‘D’ | “MD” | “CD” | “MCD” ) ‘=’ pcTermValue) ) [’,’ eol
“N=” pcName ] [‘,’ eol “U=” unit ] )
fullTermId ::= itemDesignation ‘:’ terminalId
pcTermValue ::= symbExpression | printableString
Remark: values depending on the actual PC terminal
unit ::= anyString(6)
pcOutTermAssign::= ( [DB] ‘=’ dbIdentity { ‘,’ eol [DB] ‘=’ dbIdentity} [ ‘,’ eol
“N=” pcName ] [ ‘,’ eol “U=” unit ] )
| (“N=” pcName [’,’ eol “U=” unit ] )
| (“U=” unit)
tcInstInPc ::= itemDesignation $$TC tcTypeName [tcPcInstanceName] eol
{SET symbol TO symbolVal [NOMODIFY] ‘;’ eol}
{EXPORT symbol [“:=” symbolVal] ‘;’ eol}
{‘:’tcTerminalId [pcInpTermAssign | pcOutTermAssign] eol {eol} }
tcPcInstanceName ::= INAME pcName(72)
tcTerminalId ::= terminalId
ciLocInPc ::= itemDesignation $$CI circuitName [ciPcInstanceName] eol
{SET symbol TO symbolVal [NOMODIFY] ‘;’ eol}
{EXPORT symbol [“:=” symbolVal] ‘;’ eol}
{‘:’ciTerminalId [pcInpTermAssign | pcOutTermAssign] eol {eol} }
ciPcInstanceName ::= INAME pcName(72)
ciTerminalId ::= terminalId
pagination ::= PCD-PAGE [ pageNr ] [ itemDesignation ] eol
[ ‘"’ printableString(77) ‘"’ eol
[ ‘"’ printableString(2) ‘"’ eol ] ]
pageNr ::= integer[’.’integer]

freeSection1 ::= SECTION noValidSection eol { eol | any }

END_SECTION noValidSection eol {eol}
noValidSection ::= anyString (except (HEAD | SYMBOLS | DB | PC) ).

1. freeSection is a dummy part of *.CIS, it is not evaluated

D-32 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.4.3 On NS Source Code Syntax

D.4.3 On NS Source Code Syntax

D.4.3.1 Variants and Loops

No variants and no loops are allowed in *.NSS.

D.4.3.2 Symbols in Symbol Section of *.NSS and Their Scope

Symbol Kinds
The kind of symbols in the symbol section of *.NSS can only be project-unique (PU).
A symbol is created by its occurrence in the symbol section.

Assignment of Values to PU Symbols

PU symbol values in NS overwrite the PU symbols with the same name and of the same type in
TC instances and located CIs within the NS. (PU symbol values in CI again overwrite the PU
symbols with the same name and of the same type in TC instances within this CI.
So, PU symbols are global.
PU symbols are not queried and have always a default value.

D.4.3.3 On Nested Symbolic Expressions

defaultValue, dbItemDesXxx, dbTerminalValue, callParam, pcTermValue may contain nested
symbExpressions. They are interpreted successively until all involved terms are substituted by
constant values, and the operations are executed. The type of the so evaluated result has to
correspond to the type of the concerned symbol and terminal, respectively.

D.4.3.4 On Formulas

Occurrence
A formula can occur as symbolVal only for calculated type symbols:
CB, CI, CIL, CR.

Calculating by Formulas
Operands of all types and all the operators are allowed in a formula, no matter what is the type
of the symbol, the value of which is to be calculated.

3BDS 100 595R401 D-33

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

Steps of calculation:
1. The operands are at first converted internally to real values.
2. All operations (also the Boolean ones!) are then executed with real values.
For Boolean operations 0.00 is considered to be FALSE,
all nonzero values are considered to be TRUE.
3. At the end the real result is converted to B, I, or IL or left R depending on the symbol,
the value of which was to be calculated on the base of the formula.

D.4.3.5 TCs Instantiated in NS

Referencing TC Instances in NS
A TC instance is indicated by $$TC. It must be followed by a full interface specification of the
given TC with its VL and IU symbols:
$$TC tcTypeName [ INAME ( pcName(72) | dbName(72) ) ] eol
{ SET symbol TO symbolVal [NOMODIFY] ‘;’ eol }
and value assignments for its PU symbols:
{ EXPORT symbol [ := symbolVal ] ‘;’ eol }
The optional keyword NOMODIFY indicates that the value must not be changed. It is applied
for symbols that change the interface (number, type, name of symbols) of the concerned TC.

TC Instances in Different Sections of an NS

The DB section of an NS may have TC instances (possibly several of each type) that contain DB
elements, possibly symbol declarations but no PC related elements. These TC instances contain
PU and/or IU symbols.
The PC section of an NS may have TC instances (possibly several of each type) that contain PC
related elements and possibly symbol declarations and DB elements, too. These TC instances
contain PU and/or IU symbols.
The DB and PC sections contain used symbols.

Distinction of TC Instances
Instantiated TCs can have unique instance names introduced by the keyword INAME.
The different instances of a TC can be distinguished also without instance names in two ways
depending on the section where the TC is instantiated:
• In the PC section every instance has another item designation.
• In the DB section the different instances of one TC must have different IU symbol values.

D-34 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section D.4.3 On NS Source Code Syntax

D.4.3.6 CIs Located in NS

Referencing CIs Located in NS

A CI located in NS is indicated by $$CI. It must be followed by a full interface specification of
the given CI with its IU and LU symbols:
$$CI circuitName [ INAME ( pcName(72) | dbName(72) ) ] eol
{ SET symbol TO symbolVal [NOMODIFY] ‘;’ eol }
and value assignments for its PU symbols:
{ EXPORT symbol [ := symbolVal ] ‘;’ eol }
The optional keyword NOMODIFY indicates that the value must not be changed. It is applied
for symbols that change the interface (number, type, name of symbols) of the concerned TC or
CI.

CIs in Different Sections of an NS

The DB section of an NS may have located CIs (one of each type) that contain DB elements,
possibly symbol declarations but no PC related elements. These CIs contain PU and/or IU
symbols.
The PC section of an NS may have located CIs (one of each type) that contain PC related
elements and possibly symbol declarations and DB elements, too. These CIs contain PU and/or
IU symbols.
The DB and PC sections contain used symbols.

Distinction of Located CIs

Located CIs are always unique in an NS.
They can have unique instance names introduced by the keyword INAME.

3BDS 100 595R401 D-35

Function Chart Builder User’s Guide
Appendix D Syntax of TC, CI, and NS Source Code

D-36 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section E.1 Syntax of PC Names

Appendix E Syntax of Names

E.1 Syntax of PC Names

E.1.1 General
The length of PC instance names is 1 to 72 characters.
The length of a signal names (source names) is 1 to 20 characters.
As names have to be loaded to and from nodes in ABB Master representation (7bit source code),
the character set is limited.
National characters are supported according to the national character setting,
see Table E-1, Character Set of PC Names.

E.1.2 Rules
1. Enclose the names in parentheses ‘(’ and ‘)’ that contain characters other than
a-z, A-Z, 0-9, ‘_’, and national characters ä, ö, ü, ….
2. Names must not start with a digit or an underscore ‘_’.
To avoid offending cases, enclose the whole name in parentheses ‘(’ and ‘)’
3. Names must not hold characters marked as “not allowed” in Table E-1.
4. Names must not equal a PC program item designation, for example, PC2.

E.1.3 Scope
The scope of PC instance names and signal names is the corresponding PC program or—in case
of type circuits and circuits—the PC section, in which it is created.
In fact, PC instance names and signal names share the same PC name pool. Thus both have to be
unique in a PC program (PC section).
A signal name may not be used as instance name and vice versa.
At the instantiation of a type circuit or location of a circuit, internal PC names of the type circuit
(circuit) are copied to the PC name pool of the corresponding PC program or PC section of the
object you are working on.
Thus type circuit instantiation (circuit location) fails if these names are already used.

NOTE
To avoid such conflicts, for example, at multiple instantiation of a type circuit
with internal PC names, use symbolic names, that is, names containing symbols.

3BDS 100 595R401 E-1

Function Chart Builder User’s Guide
Appendix E Syntax of Names

E.2 Character Set of PC Names

Table E-1. Character Set of PC Names

ANSI 7-bit
Printed Remark and National
Name of Character Character Character
Character Character Setting
Number Number
(Control characters, 0 .. 31 - Not allowed
not printable)
Space 32 ‘’ 32 Only if enclosed in ( and )
Exclamation mark 33 ! 33 Only if enclosed in ( and )
Double opening quote 34 “ 34 Only if enclosed in ( and )
Hash mark 35 # 35 Only if enclosed in ( and )
Dollar 36 $ 36 Only if enclosed in ( and )
Percent 37 % 37 Only if enclosed in ( and )
unless you use % to designate
the start and end of a local
symbol in TC/CI/NS source
code
Ampersand 38 & 38 Only if enclosed in ( and )
Single opening quote 39 ‘ 39 Only if enclosed in ( and )
Opening parenthesis 40 ( 40 Only if enclosed in ( and )
Closing parenthesis 41 ) 41 Only if enclosed in ( and )
Asterisk 42 * 42 Only if enclosed in ( and )
Plus sign 43 + 43 Only if enclosed in ( and )
Comma 44 , 44 Only if enclosed in ( and )
Hyphen 45 - 45 Only if enclosed in ( and )
Dot 46 . 46 Only if enclosed in ( and )
Slash 47 / 47 Only if enclosed in ( and )
Zero 48 0 48 Must not be used as first
character
… … … …
Nine 57 9 57 Must not be used as first
character
Colon 58 : 58 Only if enclosed in ( and )

E-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section E.2 Character Set of PC Names

Table E-1. Character Set of PC Names

ANSI 7-bit
Printed Remark and National
Name of Character Character Character
Character Character Setting
Number Number
Semicolon 59 ; 59 Only if enclosed in ( and )
Less then 60 < 60 Only if enclosed in ( and )
unless you use < to designate
the start of a symbol in
TC/CI/NS source code
Equal sign 61 = 61 Only if enclosed in ( and )
Greater then 62 > 62 Only if enclosed in ( and )
unless you use > to designate
the end of a symbol in
TC/CI/NS source code
Question mark 63 ? 63 Only if enclosed in ( and )
At sign 64 @ 64 Only if enclosed in ( and )
A 65 A 65
… … … …
Z 90 Z 90
Left square bracket 91 [ 91 USA(1)
Back slash 92 \ 92 USA(1)
Right square bracket 93 ] 93 USA(1)
Caret 94 ^ 94 Not allowed(1)
Underscore 95 _ 95 Must not be used as first
character
Apostrophe 96 ` 96 Not allowed
a 97 a 97
… … … …
z 122 z 122
Left bracket 123 { 123 USA(1)
Vertical bar 124 | 124 USA(1)
Right bracket 125 } 125 USA(1)
Tilde 126 ~ 126 USA, SWE(1)

3BDS 100 595R401 E-3

Function Chart Builder User’s Guide
Appendix E Syntax of Names

Table E-1. Character Set of PC Names

ANSI 7-bit
Printed Remark and National
Name of Character Character Character
Character Character Setting
Number Number
(Special and national 127, 128, - Not allowed
characters) 130, 131,
133,
135 .. 141,
144 .. 147,
149 .. 152,
155 .. 254
Ae 142 Ä 92 GER, SWE
Oe 153 Ö 92 GER, SWE
Ue 154 Ü 93 GER
Ao 143 Å 93 SWE
ae 132 ä 123 GER, SWE
oe 148 ö 124 GER, SWE
ue 129 ü 125 GER
ao 134 å 125 SWE
ss 225 ß 126 GER
(1) Since FCB release 4.5, these characters are handled in the same manner by the Function Chart Builder and the
On-line Builder in contrast to earlier releases.

E-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section E.3 Syntax of DB Names

E.3 Syntax of DB Names

E.3.1 General
The length of DB instance names of DB elements is normally 1 to 20 characters.
In case of DS, CLOCKSYNCH, START, TERMGENA, and TERMGENB elements of AC 400
Series node types, the length of DB instance names is 1 to 12 characters, in case of BM,
CAPPRI, CAPTERM, CAPXCOM, NETWL, NM, TL, and TU 1 to 6 characters.
In case of DAT(II), PARDAT(II) elements of AC 100 Series node types, the length of DB
instance names is 1 to 19 characters, in case of DAT, DSP, and MVB elements 1 to 12
characters.
The length of DB instance names of type circuits instantiated in the DB section and circuits
located in the DB section is 1 to 72 characters.
As instance names have to be loaded to and from nodes in ABB Master representation
(7bit source code), the character set is limited.
National characters are supported according to the national character setting, see Table E-2,
Character Set of DB Names.

E.3.2 Rules
1. Names must not consist only of numerals, or periods, or numerals and periods (dots).
2. Names must not start or end with a minus sign (hyphen) ‘-’.
3. Names must not hold characters marked as “not allowed” in Table E-2.
4. Names must not equal an item designation, for example, AI1.1, unless it is its own item
designation.
5. Substrings of names must not equal “.Bn”, “.In”, “.ILn”, “.Rn”, where n is a number,
except for names of DAT elements.

E.3.3 Scope
The scope of DB instance names is the corresponding DB section, in which it is created.
DB instance names have to be unique in the DB section. (DB instance names have their own DB
name pool.)
At the instantiation of a type circuit or location of a circuit, internal DB names of the type circuit
(circuit) are copied to the DB name pool of the corresponding DB section of the object you are
working on.
Thus type circuit instantiation (circuit location) fails if these names are already used.

NOTE
To avoid such conflicts, for example, at multiple instantiation of a type circuit
with internal DB names, use symbolic names, that is, names containing symbols.

3BDS 100 595R401 E-5

Function Chart Builder User’s Guide
Appendix E Syntax of Names

E.4 Character Set of DB Names

Table E-2. Character Set of DB Names

ANSI 7-bit
Printed Remark and National
Name of Character Character Character
Character Character Setting
Number Number
(Control characters, 0 .. 31 - Not allowed
not printable)
Space 32 ‘’ 32 Not allowed
Exclamation mark 33 ! 33 Not allowed
Double opening quote 34 “ 34
Hash mark 35 # 35
Dollar 36 $ 36
Percent 37 % 37 Not allowed unless you use %
to designate the start and end
of a local symbol in TC/CI/NS
source code
Ampersand 38 & 38
Single opening quote 39 ‘ 39 Not allowed
Opening parenthesis 40 ( 40 Not allowed
Closing parenthesis 41 ) 41 Not allowed
Asterisk 42 * 42
Plus sign 43 + 43
Comma 44 , 44 Not allowed
Hyphen 45 - 45 Do not use as first or last
character of a name
Dot 46 . 46 Do not combine only numerals
and dots
Slash 47 / 47 Not allowed
Zero 48 0 48 Do not combine only numerals
and dots
… … … …
Nine 57 9 57 Do not combine only numerals
and dots
Colon 58 : 58 Not allowed

E-6 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section E.4 Character Set of DB Names

Table E-2. Character Set of DB Names

ANSI 7-bit
Printed Remark and National
Name of Character Character Character
Character Character Setting
Number Number
Semicolon 59 ; 59 Not allowed
Less then 60 < 60 Not allowed unless you use <
to designate the start of a
symbol in TC/CI/NS source
code
Equal sign 61 = 61 Not allowed
Greater then 62 > 62 Not allowed unless you use >
to designate the end of a
symbol in TC/CI/NS source
code
Question mark 63 ? 63
At sign 64 @ 64
A 65 A 65
… … … …
Z 90 Z 90
Left square bracket 91 [ 91 USA(1)
Back slash 92 \ 92 USA(1)
Right square bracket 93 ] 93 USA(1)
Caret 94 ^ 94 Not allowed(1)
Underscore 95 _ 95 Must not be used as first
character
Apostrophe 96 ` 96 Not allowed
a 97 a 97
… … … …
z 122 z 122
Left bracket 123 { 123 USA(1)
Vertical bar 124 | 124 USA(1)
Right bracket 125 } 125 USA(1)
Tilde 126 ~ 126 USA, SWE(1)

3BDS 100 595R401 E-7

Function Chart Builder User’s Guide
Appendix E Syntax of Names

Table E-2. Character Set of DB Names

ANSI 7-bit
Printed Remark and National
Name of Character Character Character
Character Character Setting
Number Number
(Special and national 127, 128, - Not allowed
characters) 130, 131,
133,
135 .. 141,
144 .. 147,
149 .. 152,
155 .. 254
Ae 142 Ä 92 GER, SWE
Oe 153 Ö 92 GER, SWE
Ue 154 Ü 93 GER
Ao 143 Å 93 SWE
ae 132 ä 123 GER, SWE
oe 148 ö 124 GER, SWE
ue 129 ü 125 GER
ao 134 å 125 SWE
ss 225 ß 126 GER
(1) Since FCB release 4.5, these characters are handled in the same manner by the Function Chart Builder and the
On-line Builder in contrast to earlier releases.

E-8 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section F.1 General

Appendix F Syntax of Template Files

F.1 General
To understand this syntax description, see Syntax Rules in Section D.1.2, Conventions.
The template files are ANSI text files and have the standard file name extension TPX.

F.2 Template File Syntax

templateFile ::= { template }
template ::= BEGIN templateName
globalPart
{ templateField }
END

templateName ::= ‘"’ anystring ‘"’

This parameter is a unique string which defines the template. It consist of following parts:
– Layout style of the footer, for example, IEC, DIN, Standard Master...
– Paper format, for example, US letter, A3
– Paper orientation, landscape or portrait
– Language of the footer fields, copyright info, and so on, for example, English.

globalPart ::= pageSize deskArea

footerFrame
[drawFrames]
[deskAreaLines]
rowsColumns
nameFont
[namePos]
valueFont
[ copyrightFont
copyrightPos
[copyright_1]
[copyright_2]
[copyright_3]

3BDS 100 595R401 F-1

Function Chart Builder User’s Guide
Appendix F Syntax of Template Files

[copyright_4]
[copyright_5] ]
[ sysPageNr
sysNextPageNr
sysDocTitle ]

pageSize ::= PageSize= cardinal ‘,’ cardinal

The 1st parameter is the x-value of the needed paper size in lometric units (0.1 mm).
The 2nd parameter is the y-value of the needed paper size in lometric units.

deskArea ::= DeskArea= cardinal ‘,’ cardinal ‘,’ cardinal ‘,’ cardinal
The 1st parameter is the position of the left edge of the desk area for drawing in lometric
units.
(This is the area that is called “text area” in other parts of this Help.)
The 2nd parameter is the position of the top edge in lometric units.
The 3rd parameter is the position of the right edge in lometric units.
The 4th parameter is the position of the bottom edge in lometric units.

footerFrame ::= FooterFrame cardinal ‘,’ cardinal ‘,’ cardinal ‘,’ cardinal
The 1st parameter is the left edge of the footer frame line in lometric units.
The 2nd parameter is the top edge in lometric units.
The 3rd parameter is the right edge in lometric units.
The 4th parameter is the bottom edge in lometric units.

deskAreaLines ::= DeskAreaLines= NO | YES

If the parameter is set to YES, a frame will be drawn around the desk area.
Else no frame is drawn.

rowsColumns ::= RowsColumns= cardinal ‘,’ cardinal

The 1st parameter is the default setting of used rows for output.
The 2nd parameter is the default setting of used columns for output.

nameFont ::= Fontname= anystring ‘,’ cardinal ‘,’ cardinal ‘,’ cardinal
The 1st parameter is a valid Windows font name to be used for naming the fields in the
footer.
The 2nd parameter is the font height in lometric units.

F-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section F.2 Template File Syntax

The 3rd parameter is the font width in lometric units; a value of zero lets the system define
an appropriate width.
The 4th parameter is the boldness of the font (100 = thin, 300=semibold, 700=bold,
900=ultrabold).

namePos ::= NamePos= cardinal ‘,’ cardinal

The 1st parameter is the x-offset in lometric units relative to the upper left corner of the
field, where the field title (for example, “Based on”) will be written. Valid for all fields in
this footer template.
The 2nd parameter is the y-offset in lometric units relative to the upper left corner of the
field, where the field title will be written. Valid for all fields in this footer template.

valueFont ::= ValueFont= anystring ‘,’ cardinal ‘,’ cardinal ‘,’ cardinal
The 1st parameter is a valid Windows font name to be used for value texts entered and
shown in the footer fields.
The 2nd parameter is the font height in lometric units.
The 3rd parameter is the font width in lometric units; a value of zero lets the system define
an appropriate width.
The 4th parameter is the boldness of the font (100 = thin, 300=semibold, 700=bold,
900=ultrabold).

copyrightFont ::= CopyrightFont= anystring ‘,’ cardinal ‘,’ cardinal ‘,’ cardinal
The 1st parameter is a valid Windows font name to be used for the copyright information
at top of the paper.
The 2nd parameter is the font height in lometric units.
The 3rd parameter is the font width in lometric units; a value of zero lets the system define
an appropriate width.
The 4th parameter is the boldness of the font (100 = thin, 300=semibold, 700=bold,
900=ultrabold).

copyrightPos ::= CopyrightPos= cardinal ‘,’ cardinal

The 1st parameter is the x-offset in lometric units relative to the upper left corner of the
paper, where the first copyright line will be written.
The 2nd parameter is the y-offset in lometric units relative to the upper left corner of the
paper, where the first copyright line will be written.

copyright_1 ::= Copyright_1= anystring

The parameter is any text, usually a copyright information, which will be written at the
copyrightPos position + one line. It can be only one text line.

3BDS 100 595R401 F-3

Function Chart Builder User’s Guide
Appendix F Syntax of Template Files

copyright_2 ::= Copyright_2= anystring

The parameter is any text, usually a copyright information, which will be written at the
copyrightPos position + two lines. It can be only one text line.

copyright_3 ::= Copyright_3= anystring

The parameter is any text, usually a copyright information, which will be written at the
copyrightPos position + three lines. It can be only one text line.

copyright_4 ::= Copyright_4= anystring

The parameter is any text, usually a copyright information, which will be written at the
copyrightPos position + four lines. It can be only one text line.

copyright_5 ::= Copyright_5= anystring

The parameter is any text, usually a copyright information, which will be written at the
copyrightPos position + five lines. It can be only one text line.

sysPageNr ::= SysPageNr= fieldIdentifier

The parameter is a valid field identifier, which is used in this template. The statement
means, that the field with the given identifier will be used as system field, where the
application programs write the actual page number of the document. The user cannot type
any input in a system field.

sysNextPageNr ::= SysNextPageNr= fieldIdentifier

The parameter is a valid field identifier, which is used in this template. The statement
means, that the field with the given identifier will be used as system field, where the
application programs write the page number of the next page of the document. The user
cannot type any input in a system field.

sysDocTitle ::= SysDocTitle= fieldIdentifier

The parameter is a valid field identifier, which is used in this template. The statement
means, that the field with the given identifier will be used as system field, where the
application programs write the title of the document. The user cannot type any input in a
system field.

templateField ::= fieldIdentifier

fieldFrame
[ fieldName ]
[ fieldValueArea ]
[ fieldLogo ]
[ fieldStaticText ]
[ fieldMaxChar ]

F-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section F.2 Template File Syntax

fieldIdentifier ::= ‘[’ footerFieldIdentifier ‘]’

The parameter is a predefined field name, as listed below.

fieldFrame ::= Frame= cardinal ‘,’ cardinal ‘,’ cardinal ‘,’ cardinal
The 1st parameter is the left edge of the field frame line in lometric units, relative to the
upper left corner of the paper.
The 2nd parameter is the top edge of the field frame line in lometric units, relative to the
upper left corner of the paper.
The 3rd parameter is the right edge of the field frame line in lometric units, relative to the
upper left corner of the paper.
The 4th parameter is the bottom edge of the field frame line in lometric units, relative to
the upper left corner of the paper.

fieldName ::= Name= anystring

The parameter is a user defined name for the field. It will be written at the namePos
position relative to the top left corner of the field.

fieldValueArea ::= ValueArea= cardinal ‘,’ cardinal ‘,’ cardinal ‘,’ cardinal
The 1st parameter is the left edge of the area in lometric units for writing the field value.
The 2nd parameter is the top edge in lometric units.
The 3rd parameter is the right edge in lometric units.
The 4th parameter is the bottom edge in lometric units.

fieldLogo ::= Logo= cardinal ‘,’ cardinal ‘,’ anystring [ ‘,’ cardinal ]
The 1st parameter is the x-position (in lometric units, relative to the upper left corner of the
paper) for drawing the logo.
The 2nd parameter is the y-position (in lometric units, relative to the upper left corner of
the paper) for drawing the logo.
The 3rd parameter is the filename (without drive and path specification) of the *.WMF or
*.BMP file containing the logo.
The 4th parameter is only used for *.WMF files. It is the scaling factor to be used for the
logo. A value of 100 means 100%, that is, original size. 200 means double height and
double width.

fieldStaticText ::= StaticText= cardinal ‘,’ cardinal ‘,’ anystring ‘,’ cardinal ‘,’ cardinal ‘,’
cardinal ‘,’ anystring
The 1st parameter is the x-position (in lometric units, relative to the upper left corner of the
paper) for drawing the text.
The 2nd parameter is the y-position (in lometric units, relative to the upper left corner of
the paper) for drawing the text.

3BDS 100 595R401 F-5

Function Chart Builder User’s Guide
Appendix F Syntax of Template Files

The 3rd parameter is a valid Windows font name to be used for the static text in the field.
The 4th parameter is the font height in lometric units.
The 5th parameter is the font width in lometric units; a value of zero lets the system define
an appropriate width.
The 6th parameter is the boldness (100 = thin, 300=semibold, 700=bold, 900=ultrabold).
The 7th parameter is the text string.

fieldMaxChar ::= MaxChar= cardinal

The parameter defines the number of characters, which are allowed to enter in this field.

footerFieldIdentifier ::=Design_ch | Tech_ref | Resp_dept | Date | L_Text2 | L_Text3

| L_Text4 | R_Text1 | R_Text2 | R_Text3 | R_Text4 | Rev_Ind | Language |
IEC_BasedOn | IEC_Prepared | IEC_Approved | IEC_Title1 | IEC_Title2
| IEC_Title3 | IEC_Project1 | IEC_Project2 | IEC_Project3 | IEC_DocDes1
| IEC_DocDes2 | IEC_ItemDes1 | IEC_ItemDes2 | IEC_RespDept
| IEC_RevInd | IEC_DocNo | IEC_Language
| DIN_RevInd1 | DIN_RevInd2 | DIN_RevInd3 | DIN_Revision1
| DIN_Revision2 | DIN_Revision3 | DIN_RevDate1 | DIN_RevDate2
| DIN_RevDate3 | DIN_RevName1 | DIN_RevName2 | DIN_RevName3
| DIN_Date | DIN_Prepared | DIN_Checked | DIN_Approved
| DIN_Project1 | DIN_Project2 | DIN_Project3 | DIN_BasedOn
| DIN_Replaces | DIN_ReplacedBy | DIN_RespDept | DIN_Title1
| DIN_Title2 | DIN_Title3 | DIN_Title4 | DIN_Free | DIN_DocDes1
| DIN_DocDes2 | DIN_DocKind | DIN_Language | DIN_DocNo
| DIN_ItemDes1 | DIN_ItemDes2
| USR_Free1 | USR_Free2 | USR_Free3 | USR_Free4 | USR_Free5
| USR_Free6 | USR_Free7 | USR_Free8 | USR_Free9 | USR_Free10
The first paragraph defines field identifiers, used for Standard Master templates, the
second one defines those for IEC templates, the third one those for DIN templates. The
fourth paragraph defines additional field names that can be used to build up or enhance
own templates with own logos, own field names, another layout, and so on.

F.3 Hints
If you want to modify the standard templates for some project or create your own templates, see
Section 4.4.2.11, Creation of Own Templates.
To inspect an example of a template file, open the C:\Advabldenv\foot001.TPX file using
AS100-EDIT or a simple text editor like Notepad.

F-6 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section G.1 Introduction

Appendix G Configuration of AdvaBuild Communicator

G.1 Introduction

General
The communication of the engineering station and the target is implemented in form of a
DCOM application.
The executable and DLL files are PCommunicator.exe, TargetSupport.dll,
PCommunicatorps.dll, and RoutSrv.dll.
The DCOM application name is AdvaBuild Communicator.
At installation, the AdvaBuild Communicator is registered for the interactive user.

Conditions of Successful Server-Client Operation

1. The Function Chart Builder 4.6/0 or later must be installed on your local engineering
station (“this PC”, the client).
2. The Function Chart Builder 4.6/0 or later must be installed on the server.
3. The user as client must have access and launch permissions for the DCOM application
AdvaBuild Communicator. You may ask your Windows NT / Windows 2000 system
administrator to configure the server accordingly.
4. In case of remote usage of Advant Station 100 Series Engineering Board access and
launch permissions are necessary also for the AdvaBuild Engineering Board Server,
proceed as described in On-line Builder User’s Guide, Chapter 2, Installation.

CAUTION
Be aware that the access to the target is possible for all users that have access and
launch permissions for the DCOM application AdvaBuild Communicator.
For the security of your process control application restrict the permissions to
authorized users and authorized user groups.
The following sections are instructions for Windows NT and Windows 2000 system
administrators.
The procedures are the same for Windows NT and Windows 2000 unless it is explicitly noted.

G.2 Assignment of Access and Launch Permissions

To assign access and launch permissions, proceed as follows:

3BDS 100 595R401 G-1

Function Chart Builder User’s Guide
Appendix G Configuration of AdvaBuild Communicator

1. Start the DCOMCNFG program, for example, by the Run command in the Start menu of
Windows NT.

Figure G-1. Run DCOMCNFG

Activate the OK button.

2. Select AdvaBuild Communicator in the Distributed COM Configuration Properties
dialog box:

Figure G-2. Distributed COM Configuration Properties

Activate the Properties button.

G-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section G.2 Assignment of Access and Launch Permissions

3. The DCOMCNFG program opens the AdvaBuild Communicator Properties dialog box
having four tabs.
Check the General tab and the Location tab:

Figure G-3. General Tab

Figure G-4. Location Tab

Then select the Security tab and select the options as shown:

3BDS 100 595R401 G-3

Function Chart Builder User’s Guide
Appendix G Configuration of AdvaBuild Communicator

Figure G-5. Security Tab

4. Activate the Edit button of the Use custom access permissions group.
The Registry Value Permissions dialog box shows the users currently having permission.
It contains at least the default users INTERACTIVE and SYSTEM and the user that is
currently logged in, in our example LAHARMAT:

Figure G-6. Registry Value Permissions

G-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section G.2 Assignment of Access and Launch Permissions

Activate the Add button.

5. The DCOMCNFG program opens the Add Users and Groups dialog box.
The users and user groups that you want to add belong to some domain or computer.
Select it in the List Names From drop-down list box.
The Names list box contains at first only user groups.
To display also the users, activate the Show Users button.
Select the first user or user group you want to add in the Names list box,
in our example KASOHN:

Figure G-7. Add Users and Groups

Activate the Add button (of the Add Users and Groups dialog box).

3BDS 100 595R401 G-5

Function Chart Builder User’s Guide
Appendix G Configuration of AdvaBuild Communicator

The selected user or user group appears in the Add Names list box:

Figure G-8. Add Users and Groups, Name Added

Proceed with the next user or user group similarly.

So you collect all users and groups in the Add Names list box.
At the end, activate the OK button (of the Add Users and Groups dialog box).

G-6 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section G.2 Assignment of Access and Launch Permissions

6. Check the result in the Registry Value Permissions dialog box.

It shows that also the new users and user groups, in our example also KASOHN,
have permission:

Figure G-9. Registry Value Permissions, User Added

Activate the OK button (of the Registry Value Permissions dialog box).
The AdvaBuild Communicator Properties dialog box regains the focus.

7. Activate the Edit button of the Use custom launch permissions group in the Security tab.
Proceed as in steps 4, 5, and 6. Add exactly the same users and user groups
as you did in steps 4, 5, and 6.
Activate the OK button of the AdvaBuild Communicator Properties dialog box
to close it.
Activate the OK button of the Distributed COM Configuration Properties dialog box
to finish the configuration.

8. Test the target connection to the server PC from a local client by the Target | Connect
command.
If the connection is successful, the Function Chart Builder opens the Status Report
window and fills it with plausible data of the target and no error message appears like
’server_name’ is not configured a communication server
or not available.

In due case double-check steps 1 to 7.

NOTE
In case of remote usage of Advant Station 100 Series Engineering Board
you edit access and launch permissions similarly for the AdvaBuild Engineering
Board Server, see On-line Builder User’s Guide, Chapter 2, Installation.

3BDS 100 595R401 G-7

Function Chart Builder User’s Guide
Appendix G Configuration of AdvaBuild Communicator

G.3 Access Right (Privilege) of AF 100 Interface Software

Parts of the AF 100 Interface software, that is, AF 100 Interface 1.0/0 or AF 100 Interface 1.0/1
or Advant OPC Server for AF 100 1.0/0, require that the user has administrator privileges.
In case of usage of AF 100 Interface on the local engineering station, be sure that the interactive
user gets administrator privileges.
For case of usage of AF 100 Interface on a remote engineering station, be sure that the
interactive user or the user “AdvantServer1”, as applicable, gets administrator privileges.
See next section.

G.4 User On Remote Engineering Station

Registration of AdvaBuild Communicator on the Remote Engineering Station

On the remote engineering station the AdvaBuild Communicator is installed and registered
normally for the interactive user. That means
• Some interactive user must be logged on the remote engineering station.
• In case of usage of AF 100 Interface, this user must have administrator privileges.
• If he logs out, the communication breaks down.
As an alternative, you can register the AdvaBuild Communicator any time for the user
“AdvantServer1” instead of the interactive user. For this proceed as follows:
1. Choose the Start | Run command.
2. Enter in the Run dialog box:
C:\Program Files\Common Files\AdvaBld Shared\pcommunicator
-RegServer -DCOM
3. Activate the OK button.
Now the behavior of the remote engineering station has changed:
• No interactive user needs to be logged on the remote engineering station.
The engineering station must just be switched on.
• In case of usage of AF 100 Interface, only AdvantServer1 must have administrator
privileges.
• Logging in and out of interactive users does not influence the communication.

Giving Administrator Privileges to AdvantServer1

When you are working with Windows NT, proceed as follows:
1. Start the User Manager by the Start | Programs | Administrative Tools (Common) |
User Manager command or in some other way.
2. Double-click on Administrators in the Groups list box of the User Manager dialog box.
The User Manager shows the Local Group Properties dialog box.

G-8 3BDS 100 595R401

 Function Chart Builder User’s Guide
Section G.4 User On Remote Engineering Station

3. Activate the Add button.

The User Manager shows the Add Users and Groups dialog box.
4. Add AdvantServer1 in a similar way as shown in Section G.2, Assignment of Access and
Launch Permissions, step 5.
5. Exit the User Manager by activating the OK buttons and closing all its dialogs.
6. Reboot the remote engineering station to make the changes effective.
When you are working with Windows 2000 instead, proceed as follows:
1. Start the users and passwords manager by the Start | Settings | Control Panel | Users and
Passwords command or in some other way.
2. Click on the Advanced button in the Advanced tab of the Users and Passwords dialog
box.
The users and passwords manager opens the Local Users and Groups window.
3. Select the Groups folder in the left (tree) pane and double-click on the
Administrators item in the right pane.
The users and passwords manager shows the Administrators Properties dialog box.
4. Activate the Add button.
The users and passwords manager shows the Select Users and Groups dialog box.
5. Add AdvantServer1 in a similar way as shown in Section G.2, Assignment of Access and
Launch Permissions, step 5.
6. Exit the users and passwords manager by activating the OK buttons and closing all its
windows and dialogs.
7. Reboot the remote engineering station to make the changes effective.

3BDS 100 595R401 G-9

Function Chart Builder User’s Guide
Appendix G Configuration of AdvaBuild Communicator

G-10 3BDS 100 595R401

 Function Chart Builder User’s Guide
Appendix H Glossary

Appendix H Glossary

ABB Master representation: Way of representing and computing AMPL source code in
On-line Builder (7-bit characters).
Active (for Diagnostics/Diagnosis): A module is active if it is in the operational state.
Address
The Diagnosis program uses the following address to read diagnostic information:
In case of Advant Controller 110 2.0
Station: 0 - 7; module position: 1 - 20,
101 - 120 and 201 - 220 if a subcarrier module is in the subposition 1 and 2, respectively
In case of Advant Controller 70 1.0
Station: 0; module position: 1 - 12
In case of Advant Controller 55 1.0
Unit: 0 - 4; second part of address: 0 (not relevant)
The Diagnostics program uses the following address to read diagnostic information:
In case of Advant Controller 110 2.1 and higher
Bus number: 0 - 255; Station number: 0 - 80;
Module position: 1 - 20 (and for I/O stations:101 - 120, …, 701 - 720);
Subposition (position of the subcarrier module): 0 - 2
In case of Advant Controller 70 1.1 and higher
Bus number: 0 - 255; Station number: 0 - 80;
Module position: 0 - 12 (and for I/O stations:100 - 112, …, 700 - 712);
Subposition: not relevant
In case of Advant Controller 55 1.1
Bus number: not applicable; Station number: not applicable;
Unit number: 0 - 4; Subposition: not applicable
Addressing for Advant Controller 160 is the same as for Advant Controller 110 2.1.
Addressing for Advant Controller 80 is typically the same as for Advant Controller 70 1.1.
Advant Controller: A computerized process control system manufactured by ABB (Asea
Brown Boveri).
AMPL: ABB Master Programming Language. Uses text format to specify MasterPiece and
Advant Controllers data bases and process control programs. The Function Chart Builder
generates AMPL as source code for nodes.
Application data: All data belonging to an entity as project, node, circuit or type circuit.
Application program: A general concept of an assembly of program functions aiming to
realize and to automate an addressed process control functions. Consists of a data base and a
PC part. The PC part (process control part) may be structured into different PC programs.
Attribute: A term used for the following purposes:
• To differentiate modifying DB elements of type circuits and circuits (MOD) in the
DB Section window of type circuits and circuits

3BDS 100 595R401 H-1

Function Chart Builder User’s Guide
Appendix H Glossary

• To differentiate DB elements implicitly created by type circuits, remote I/O elements like
AI810, extended DB elements like AOS, and AF100S DB elements (T, R, X, and S,
respectively) in the DB Section window of nodes
• To define the form of the graphical symbol, which represents the instantiated type circuit
or the located circuit in the function chart (Adjust, Blank Line, Waist)
• To reflect to what kind of terminals a TC/CI terminal is connected within the type circuit
or circuit (Dynamic, DB Reference, Non-Invertible)
• To reference configured AF 100 communication interfaces, and so on, of an AC 100 Series
target of newer node type, such as AC 160, AC 110 2.2 or 2.1, AC 80, AC 70 1.1, or
AC 55 1.1, reported by the Target | Report Attributes command.
AUTOEXEC.BAT: The file that contains the list of commands executed at start-up by an IBM-
compatible personal computer. The commands can set the values of parameters that control the
computer’s operation and install memory resident programs. The file is located in the root
directory of your hard disk.
Backtranslate: Generate the Function Chart Builder’s internal data representation in form of a
*.ODB file from AMPL source code or node structure source code or circuit source code or type
circuit source code.
Base software, basic system: The base software (basic system) is the necessary software of a
node type.
Blocked: The status of an application program in an AC 100 Series target is blocked if its
execution is stopped.
Bus number: Identifies together with station number a controller in a process control network.
Call parameter: Parameter that affects the operation of a PC element.
For example, the cyclicity in milliseconds call parameter sets the cycle time of the program
element execution in milliseconds.
Callname: The name that identifies the function of a PC or DB element, of type circuits or
circuits. For example, the call name of a control module is CONTRM.
Channel Error (for the Diagnosis program): A Channel Error is an error of an object of the
module, for example, an I/O channel of an I/O module.
Check box: A little square box with a label on the right side which can be checked and
unchecked to select and clear a partial function. A check mark ‘ ’ or an ‘X’ in the check box
shows that the corresponding partial function is selected.
CI: Circuit, an object.
Circuit: Process control projects generally deal with process devices like motors, valves, and
sensors controlled by a process control system. A circuit (CI) is a functional piece of software
that runs on the control system and is assigned to a process device. Circuits are the basic object
of function-oriented project engineering.
The Function Chart Builder supports creation, code generation, and location of circuits.
A circuit consists of instructions creating or modifying DB elements, of PC elements, type
circuits, terminal and symbol declarations, and symbol value assignments.
You can locate each circuit only once, that is, you assign values to symbols (parameters) of the
circuit and thereby you fix its functions and the item designations of the constituting elements.

H-2 3BDS 100 595R401

 Function Chart Builder User’s Guide
Appendix H Glossary

Click: You click on an object with the mouse by pointing to it and pressing the left mouse
button (unless the right one is specified) once.
Command file (for the On-line Builder): A file running on the engineering board under the CX
operating system as the On-line Builder commands.
Compatible data types: The Function Chart Builder supports the following groups of
compatible types:
• B (Boolean), CB (calculated Boolean)
• I (integer), CI (calculated integer)
• IL (long integer), CIL (calculated long integer)
• R (real), CR (calculated real)
• T (time)
• TR (time as real)
• A* (array, string).
For example, B is compatible with CB and is incompatible with the types in all other groups.
Concatenation: Concatenation means putting terms one next to the other.
CONFIG.SYS: A DOS system file that tells DOS how to set up the computing environment on
your personal computer when you start it up. The file is located in the root directory of your
hard disk.
Convert (for the Application Builder): To transfer source code files from ABB Master
representation (7-bit characters) to general representation (8-bit characters, ANSI or ISO88591)
and vice versa.
Cursor: An arrow (mouse pointer) pointing to a location on a display screen. It is used to
select a graphical object.
Or a flashing vertical bar (insertion point) pointing to the next letter position for entry in a text
box or a text window.
Or a reverse video bar or rectangle (object cursor) showing the currently selected graphical or
text object.
Data base: The data base contains all information concerning connections to the hardware
(I/O modules, signals, and so on), connections between PC programs (DAT elements), and
connections to operator stations.
Data base element: Data base elements (DB elements) are available for I/O modules, I/O
channels, data value storage, and so on. The MasterPiece data base consists of DB elements.
Data type: The Function Chart Builder supports the following data types:
B (Boolean), CB (calculated Boolean), I (integer), CI (calculated integer), IL (long integer),
CIL (calculated long integer), R (real), CR (calculated real), T (time), TR (time as real),
and A* (array, string).
DB: An abbreviation for data base.
DBDATA: Directory to store data base files and is used mainly by Function Chart Builder.
DB element: An abbreviation for data base element.
DB source code: Data base part of AMPL source code.

3BDS 100 595R401 H-3

Function Chart Builder User’s Guide
Appendix H Glossary

DB system defaults: Default values provided by the element library for DB element properties.
For a given object they can be redefined in a DBGENDEF.BAX file.
Deblocked: The status of an application program in an AC 100 Series target is deblocked if its
execution is started.
Diagram: Graphical and/or text presentation of programs. The Function Chart Builder provides
function chart and tree diagram as two different kinds of diagrams for PC programs. They can
be displayed and printed.
Disintegrate: To disintegrate instantiated type circuits during backtranslation of source code
means that the Function Chart Builder no longer points out the type circuit references in the PC
program of the node. Disintegration of a certain class of type circuits is a prerequisite for
AC 100 Series target code generation.
Display: A device that shows alphanumeric and graphical computer output. Usually a cathode
ray tube (CRT) or a liquid crystal display (LCD).
The Test | Single Display and Test | Cyclic Display commands are part of the Function Chart
Builder’s on-line test functions available for AC 100 Series applications. They serve to monitor
values of PC and DB terminals on-line.
Document texts: Footer texts for documents as source code lists or general project
documentation. Different footer styles are available.
Document window: The window that gives view on document data. More than one document
window can be open.
Examples: the Node List window of the Application Builder, the PC Section window of the
Function Chart Builder, the Error Report window of the Diagnostics program.
DOS: An abbreviation for Disk Operating System, the program that controls the operation of
IBM-compatible personal computers.
Double-click: You double-click on an object with the mouse by pointing to it and quickly
pressing the left mouse button twice.
Download: To transfer data (for example, target code) from the Function Chart Builder to an
on-line connected target.
Drag and drop: You seize a graphical object by moving the cursor with the mouse to point to it,
then pressing the left mouse button and holding it down. You drag the seized graphical object by
moving the mouse. You drop the graphical object in the new position or in resized form by
releasing the left mouse button.
Element libraries: The sets of PC elements, DB elements, or type circuits.
PC and DB element libraries represent target versions. They are bundled to basic systems and
options. They have to be available or installed on your engineering station or PC corresponding
to your targets. Use the Application Builder to select the options for the objects before
programming or processing them by the Function Chart Builder.
Additional PC element libraries may be available in the directory C:\PC_LIB. The name of the
directory can be redefined by the environment variable PC$LIB. Additional PC element
libraries must also be bundled to options.
Additional level1 and level2 type circuit element libraries may be available in the directories
C:\TCLEV1 and C:\TCLEV2. The names of the directories can be redefined by the environment
variables TC$LEV1 and TC$LEV2.

H-4 3BDS 100 595R401

 Function Chart Builder User’s Guide
Appendix H Glossary

Engineering board: Short for Advant Station 100 Series Engineering Board - ISA (DSPU131)
and Advant Station 100 Series Engineering Board - PCI (PU516).
Engineering station: Short for Advant Station 100 Series Engineering Stations
and also for the PC, on which you run the Function Chart Builder and other
Advant Engineering components.
Environment variable: A variable stored in the memory of an IBM-compatible personal
computer and used to control the operation of one or more programs that run in the computer.
The environment variables can be defined and set by the SET command both in batch files
(for example, AUTOEXEC.BAT) or entered from the keyboard after the DOS prompt.
Memory for environment variables is reserved by the SHELL command in CONFIG.SYS.
Executable unit: The PC program can be divided into executable units. An executable unit
contains only one structure element (with specified cycle time) or one structure element and one
or more subordinate PC elements.
Extended DB elements: Complex DB elements with the following properties:
• They allow definition of signals independently of the hardware, also for MMI purposes.
• Encapsulate channel elements.
• Support signal distribution and event transfer on the AF 100.
• Create automatically all the DB elements necessary for the communication (DSP, DAT,
EVS(S), MDAT).
Extension: Part of File name.
Extract (for the Application Builder): To extract a part of a PC program and write
it into a new file. In addition the output file will be converted into ABB Master representation
(7-bit source code). The source code(*.AAX) is transferred from \PCDATA to the SRCE
directory of the same node and changes the file extension to *.AA of the given output file name.
FCB: An abbreviation for Function Chart Builder.
FCE: An abbreviation for Function Chart Editor.
File name: When working in DOS and Windows for Workgroups on IBM-compatible personal
computers, the files have names in the nnnnnnnn[.[xxx]] form, where nnnnnnnn is a file name
one to eight characters long and xxx is the file name extension, one to three characters long.
To maintain compatibility, all versions of the Function Chart Builder use file names according
to the DOS format.
Footer: Lines of text placed at the bottom of each page of a listing or a diagram. Contains
general information about the file or diagram.
Force: The Test | Activate Force Values and Test | Activate All Force Values commands are
part of the Function Chart Builder’s on-line test functions, available for AC 100 Series
applications. They force values of PC and DB terminals on-line.
Function chart: Diagram for the representation of process control programs. It contains
graphical symbols (rectangles) for PC elements, instantiated type circuits, and located circuits
and lines for connections between element terminals.
Function Chart Editor: Predecessor of the Function Chart Builder.

3BDS 100 595R401 H-5

Function Chart Builder User’s Guide
Appendix H Glossary

Function-oriented project engineering: Working method supported by the Function Chart

Builder. The main phases are assigning circuits to process devices, referencing type circuits,
locating circuits in node structures, resolving references, and expanding node data.
General representation: Way of representing and computing AMPL source code in Function
Chart Builder (8-bit ANSI or ISO88591).
Headline: In the Function Chart Builder, the headline specifies a text line to appear in the lower
right-hand corner of the page over the footer in a function chart.
HMI: Abbreviation for human-machine interface.
Use the term Human-System Interface (HSI) instead.
HSI: Abbreviation for Human-System Interface.
Input terminal: Corresponds to one of the input variables of the function represented by the
parent element. See also terminal.
Insertion point: In the general case of a text box or a text window it is a flashing vertical bar
pointing to the next letter position for entry or pasting.
In case of pasting in the PC Section window, the insertion point is normally a selected single PC
element (or instantiated type circuit or located circuit).
In case of pasting a whole PC program there is no need for selecting an insertion point.
Instance: An appearance of, or a reference to, a PC element or DB element or type circuit of a
certain type. The reference is accompanied by actual parameters. A type circuit can be
instantiated, that is, referenced and supplied with parameters, several times.
Instance name: The name of a single PC element, type circuit, or circuit given at its insertion in
a PC program. The name of a single data base element, type circuit, or circuit given at its
creation for the data base.
Instance-unique symbol: A symbol kind. An instance-unique (IU) symbol is unique to a single
instance of a type circuit or to a located circuit. It may have a default value. At the instantiation
or location time, the Function Chart Builder always asks you to enter a value or confirm the
default.
Internal data representation: All data entered via the Function Chart Builder for a node, node
structure, circuit, or type circuit are stored internally in binary representation in files with the
extension ODB.
Invert terminal: Inverting the logical sense of the input to a binary input terminal of a PC
element.
Item designation: Item designations are used for identification of DB elements, PC elements,
located circuits, and instantiated type circuits of an application.
Item designations of DB elements have the following form:
• DB elements
dm[.n]
where d = DB element callname consisting of at least two letters, m = index of DB element
of a kind, and n = channel index of a DB element.
• Circuits located in the DB section and type circuits instantiated in the DB section
dm
where d = $$TC and $$CI, m= index of circuit/type circuit.

H-6 3BDS 100 595R401

 Function Chart Builder User’s Guide
Appendix H Glossary

• Circuits located in the PC section and type circuits instantiated in the PC section, having
also DB part
dm
where d = $$DB_OF_TC and $$DB_OF_CI, m = index of circuit/type circuit.
Item designations of PC elements have the following form:
PCp[.q[.r …]]
where p = PC program number, q, r, … = PC element indexes on 2nd, 3rd, … level.
IU: Abbreviation for instance-unique.
Late instantiation: When you edit a node structure or circuit and locate a circuit or instantiate a
type circuit, the Function Chart Builder applies late instantiation. Initially, it checks only the
interface of type circuits and circuits. It checks their contents later, during expansion of node
structure. This permits you to modify DB elements that do not yet exist or to connect terminals
that do not yet exist.
Locate: To insert a circuit in a node structure referencing the circuit and assigning physical
locations to the I/O channels used in the circuit. A circuit can be located only once.
Location-unique symbol: A symbol kind. A location-unique (LU) symbol is unique to a
particular circuit available within a given project. It always has a default value. You cannot
change the value at location time.
You can have a project-unique symbol in node structure that is identical to the location-unique
symbol of the circuit. In this case, the value is not inherited from node structure to circuit.
LU: Abbreviation for location-unique.
MasterPiece: A computerized process control system manufactured by ABB (Asea Brown
Boveri).
MMI: Abbreviation for man-machine interface.
Use the term Human-System Interface (HSI) instead.
Modeless: If a dialog box is modeless, you need not to close it, nevertheless, you can change to
other tasks, for example, open other windows.
Module Error (for the Diagnosis program): A Module Error concerns the I/O module or the
component on the board. Module Errors indicate, for example, a defective PROM or an invalid
check-sum in the parameters of the PROM or RAM.
Mouse: A pointing device that enables you to enter commands and data into a computer without
typing on a keyboard. A trackball is a functionally equivalent device.
Name: A name is a unique string of characters.
In the PC section, you can use PC names.
• An instance name with length of 1 to 72 characters is used as alias for a PC item
designation.
• A signal name with length of 1 to 20 (in some cases only to 6, 12, 19) characters is used as
alias for a source in connections, that is,
– Either for an output terminal of a PC element
– Or for a constant or a DB element terminal connected to an input terminal of a PC
element in an existing connection.

3BDS 100 595R401 H-7

Function Chart Builder User’s Guide
Appendix H Glossary

The scope of a PC name is the PC program or—in case of type circuits and circuits—the PC
section, in which it is created.
The PC name carries the data type and kind of the source, for which it stands.
In the DB section, you can use DB names.
• An instance name of a DB element with length of 1 to 20 characters is used as alias for its
DB item designation. It is equal to the value of its NAME input terminal. The default value
of NAME is the of the DB element.
• An instance name of a type circuit (circuit) instantiated (located) in the DB section with
length of 1 to 72 characters is used as alias for their DB item designation.
The scope of a DB name is the DB section, in which it is created.
National characters: Set of characters, to ensure compatibility between the tools and to display
nation-specific characters (national language characters) of the Swedish and the German
languages. The US character set is the standard character set.
Node: Physically, a node is a process station of a process control network. The final target of
application programs prepared by the Function Chart Builder is a (physical) node, that is, an
Advant Controller or a MasterPiece.
In the Function Chart Builder, node denotes a program concerning a physical node. It has all
references resolved, the referenced parts are expanded, and it is fully checked. A node consists
of process control elements (PC elements) and data base elements (DB elements), and of type
circuits resolved at instantiation.
Node structure: A node structure (NS) is the location list for a certain process station.
The Function Chart Builder supports the creation and code generation of node structures.
A node structure consists of located circuits, symbol value assignments, and also of glue logic,
such as instructions creating or modifying DB elements and PC elements, even instantiated type
circuits.
The node structure is an aspect of the node. It emphasizes the structure of the node and
references the located circuits and instantiated type circuits rather than containing them with full
content.
Node type: Stands for the type of controllers, operator stations, an engineering station, or
process stations. Each node type has a specific version, which is named behind the node type
name.
NS: Node structure, an object.
Object: The Application Builder and the Function Chart Builder supports the objects node,
node structure (NS), circuit (CI), and type circuit (TC).
Object cursor: Reverse video bar or rectangle that shows the currently selected item in a list
box or the currently selected graphical object in a function chart or in a tree diagram.
Off-line: The counterpart of on-line.
On-line: A Function Chart Builder operation is on-line if it involves direct data transfer to
and/or from a connected (AC 100 Series) target.
Options: Extend the base software functionality of a node type.
OR operator: The ‘|’ (OR) operator means “take one term, either the one on the left side of the
OR operator, or the one on the right side”.

H-8 3BDS 100 595R401

 Function Chart Builder User’s Guide
Appendix H Glossary

Output terminal: Corresponds to one of the output variables of the function represented by the
PC element (or type circuit or circuit). See also terminal.
Page division: Denotes the start of a new page of the function chart. The PC element, to which
the page division is attached, is on the top of this page.
Pane: Some windows may be divided into panes by a horizontal and a vertical split bar.
You can move the bars and so change the division into panes.
The usual numbering and position of panes is:
1 - left; 2 - upper right; 3 - lower right.
Passive (for the Diagnostics/Diagnosis program): A module is passive if it is not in the
operational state. This can be caused by any of the following:
• A serious device error
• A missing process connector
• Missing or inconsistent parameters
• The fact that the module was not set into operation by the system CPU.
Paste buffer: Special buffer of the Function Chart Builder containing the recently cut or copied
PC elements (or instantiated type circuits or located circuits) with their connections, names,
units, and symbol values.
PC: Abbreviation for both personal computer and process control.
PC element: Abbreviation for process control element. Part of a process control program.
They represent elementary or compound process control functions.
The Function Chart Builder shows PC elements by rectangles in function chart and by
corresponding callnames in tree diagram.
PC program: Abbreviation for process control program.
PC source code: Process control part of AMPL source code.
PCDATA: Directory to store PC program files and is used mainly by Function Chart Builder.
Point: You point to an object with the mouse by moving the mouse pointer onto the object with
the mouse.
Print file: A computer file to be sent to a printer and to be printed as a listing or diagram.
Contains all the controls and data necessary for the printer to print according to the printer
parameters configured in the Function Chart Builder.
Process Error (for the Diagnosis program): A Process Error concerns the process to be
controlled or monitored.
A Process error can be caused by
• Missing process connector between the I/O module and the external process to be
controlled or monitored
• Missing power control
• Exceeding parameter values of the process connector, and so on.

3BDS 100 595R401 H-9

Function Chart Builder User’s Guide
Appendix H Glossary

Project: The job of programming a process control system covering several Advant Controller
or MasterPiece nodes.
Also used to describe the environment for programming a process control system covering
several Advant Controller or MasterPiece nodes with all the disk directories and data files used
to create the process control data base and programs.
Project defaults: Are default values, valid for one project as set in the Application Builder,
that is, default node types, default comments, default parts of node names and so on.
Project root: Is an environment to store all data of projects. The project root name can be up to
160 characters long. UNC paths in form of \\server_name\share_name can serve as project root.
(You do not need to map \\server_name\share_name to a network drive.)
Project-unique symbol: A symbol kind. A project-unique (PU) symbol is global for all type
circuits or circuits that are used within a given project. It always has a default value. At the
instantiation or location, you can change the parameter value.
You can have identical project-unique symbols in node structure, circuits, and type circuits.
In this case, the value is inherited from node structure to circuits and from circuits to type
circuits.
PU: Abbreviation for project-unique.
Release: Different releases, or versions, of a software product have different capabilities and
may function differently in certain situations. Knowing the release number, for example, of your
Function Chart Builder version enables ABB customer service engineers to help you solve
problems faster.
The Help | About product command displays the release number of the corresponding Advant
Engineering product component in the copyright notice.
SET command: A DOS command that enables you to define and set environment variables in
your personal computer. Your AUTOEXEC.BAT file often includes SET commands that set up
the personal computer’s serial ports, printer ports, or screen.
Source code: Program code in text format. The Function Chart Builder uses AMPL source code
and its derivatives to specify data base and process control programs. See AMPL.
AMPL source code: PC source code serves to specify process control programs of nodes and
DB source code serves to specify data base of nodes.
Type circuit source code serves to specify data base, process control program, symbols, and
terminals of type circuits.
Circuit source code serves to specify data base, process control program, symbols, and terminals
of circuits.
Node structure source code serves to specify data base and the structure of process control
programs, that is, node structures.
SRCE: Directory used mainly by On-line Builder. Important files on this directory are source
code files (ABB Master representation, 7-bit characters) and dump files.
Structure element: PC elements structuring PC programs such as PCPGM, CONTRM,
FUNCM, MASTER, SEQ, and SLAVEM. Only they can have subordinate PC elements.

H-10 3BDS 100 595R401

 Function Chart Builder User’s Guide
Appendix H Glossary

Symbol: Symbols are used in type circuits and circuits as parameters for definition of item
designations, signal names, and so on, and as internal variables. Symbols are used in node
structures to parametrize located circuits and instantiated type circuits. Formally, TC/CI
terminals are denoted also by symbols.
A symbol is a unique string of 1 to 18 characters. For example, PARAM3.
The kind (scope) of the symbols can be different, they can be instance-unique (IU) or project-
unique (PU) or location-unique (LU). Symbols have always a defined symbol (data) type.
See data type.
Symbolic expression: A symbolic expression is a string containing one or more symbols, which
may also be nested, and constants.
Symbolic formula: A symbolic formula is a string containing one or more symbols and
constants, which are connected by arithmetical, logical, and relational operators, such as +,
NOT, >=, (, and ). If the values of the symbols are substituted, the value of the formula can be
calculated and applied.
System Error (for the Diagnosis program): A System Error can be caused by wrong or missing
configuration parameters.
Target, target system: A physical location in an Advant Controller or MasterPiece process
control network. A target or (physical) node usually contains an intelligent device like an
Advant Controller or a MasterPiece.
Target code: Code generated by the Function Chart Builder that can be loaded directly to an
AC 100 Series target and executed there.
TC: Type circuit, an object.
TC/CI terminal: TC/CI terminal is the abbreviation for terminals of type circuits and circuits.
In the function chart the Function Chart Builder shows the TC/CI terminals as short lines
leading to or from the graphical symbol of an instantiated type circuit or located circuit.
The name of a TC/CI terminal is a unique string of 1 to 8 characters, for example, IN2.
The kind of the TC/CI terminals can be input (IN), output (OUT), or function parameter (FP).
The TC/CI terminal has always a defined TC/CI terminal (data) type.
TCDATA: Directory to store type circuit files and is used mainly by Function Chart Builder.
Terminal: Connection point of an element.
A PC terminal is a short line leading to or from the graphical symbol of a PC element (or
instantiated type circuit or located circuit) in the function chart. It corresponds to one of the
input or output variables of the function represented by this element.
A DB terminal is a short line leading to or from the graphical symbol of a DB element in the
Edit DB Terminal Values dialog box. It corresponds to one of the input or output variables
(properties) of the function represented by the DB element.
A type circuit terminal or circuit terminal (shortly TC/CI terminal) is a short line leading to or
from the graphical symbol of an instantiated type circuit or located circuit in the function chart.
It corresponds to one of the input or output variables of the function represented by this element.
It is represented by a maximum 8 character long list element in the TC/CI Terminal Section
window.

3BDS 100 595R401 H-11

Function Chart Builder User’s Guide
Appendix H Glossary

Terminal set: A group of terminals of a PC element controlled by the same call parameter.
Tool version: Each tool of Advant Engineering, that is, components that are builders or utilities,
has a version. Different versions of Advant Engineering products may be installed on the same
engineering station.
Tree diagram: Diagram for the representation of process control programs. The tree diagram
shows the process control programs’ structure.
Type circuit: A standard solution for a special process control problem, usually well tested and
documented. The Function Chart Builder supports the creation, code generation, and
instantiation of type circuits (TCs).
A type circuit consists of symbol declarations, instructions creating or modifying DB elements,
and PC elements. A type circuit can be instantiated several times within a node, node structure,
or circuit. By assigning different values to its parameters at instantiation, you vary the function
of each type circuit instance.
Unit: The unit denotes the dimension of the values on the source, to which it is attached.
A unit is a unique string of 1 to 6 characters, for example, kW/h. It can be attached in the PC
section to a source, that is, either for an output terminal of a PC element, or for a constant or a
DB element terminal connected to an input terminal of a PC element in an existing connection.
The units are not processed in any way by the Function Chart Builder, they just enhance the
readability of source code or function chart.
Upload: To transfer data (for example, parameter values) from an on-line connected target to
the Function Chart Builder.
USER: Directory used mainly by On-line Builder.
Variant or loop symbol: A symbol kind occurring in type circuits edited directly on source
code level (only for expert users).
A variant or loop symbol is an instance-unique symbol that carries the condition of a variant or
the number of repetitions of a loop body.
Virtual connection: Connection to an element that is already specified but does not exist yet
(virtual element).
Virtual element: Element that is already specified but not yet implemented.
VL: Abbreviation for variant or loop.
Workspace: Sum of general parameters such as position and size of the Function Chart Builder
application window, view options, zoom factor, sort order, and preferences, and of object-
specific workspace parameters such as number, status, position, and size of the windows, sort
order, recent selections, and filters.

H-12 3BDS 100 595R401

 Function Chart Builder User’s Guide
Index

INDEX
Symbols *.LS1 A-15 to A-18
# (hash mark) 4-14, 4-207, 4-217, 4-333, 4-365 to 4-366, 4- *.LS2 A-15 to A-18
372, 4-378, 5-1 *.MDB A-15, A-19
$$CI 4-115, 4-319, D-31 to D-32, D-35 *.MET A-3
$$DB_OF_CI 4-115, 4-319 *.ML 4-288, A-18
$$DB_OF_TC 4-111, 4-319 *.NSS 4-291, A-17, D-28
$$IF D-8 *.ODB 4-94, 4-244, 4-278, A-15 to A-17
$$LOOP D-8 command 4-410
$$LOOPCTR 4-196, D-9 window 4-212
$$TC 4-111, 4-319, D-22 to D-23, D-25, D-31 to D-32, D- *.OL 4-291, A-18
34 *.PCF 4-287, A-15 to A-16, A-18
* (asterisk) 4-16 to 4-17, 4-20 to 4-21, 4-59, 4-108, 4-113, *.PCL A-14, A-18
4-120, 4-135, 4-167, 4-169, 4-191 to 4-192, 4-209, 4-212 *.PCT 4-287, A-15 to A-16, A-18
to 4-213, 4-215, 4-217 to 4-218, 4-220, 4-222, 4-225, 4- *.PE_ 4-98, A-14, A-17
229, 4-300, 4-304, 4-320, 4-333, 4-378, 4-385 to 4-386, 4- *.PED A-19
416, 4-436, 4-438, 4-444, 4-454, 4-458 *.PEL 2-2, A-9, A-18
*.AA 4-142, A-18 *.PLE A-19
*.AAX 4-141, 4-269, A-18 to A-19 *.PTL A-14, A-18
*.ABU A-3 *.PXR 4-289, A-15 to A-16, A-18
*.BA 4-142, A-18 *.ST_ A-14, A-17
*.BA_ A-14, A-17 *.STL A-9, A-18
*.BAK 4-345 *.SYL 4-288, A-15, A-18
*.BAX 4-141, A-5, A-17, A-19 *.TB 4-142, A-18
*.C?? 4-255, 4-278, 4-392, A-17 to A-18 *.TBX 4-141, 4-265, A-17
*.C00 4-255, 4-278, 4-392, A-17 *.TC 4-142, A-18
*.CFX A-17 *.TC_ A-14, A-17
*.CIS 4-114, A-15, D-18 *.TCD A-3, A-17
*.CNT A-3 *.TCS 4-110, 4-141, 4-179, A-16, A-18 to A-19, D-7
*.DAT A-14 *.TE_ 4-98, A-14, A-17
*.DB 4-285, A-15 to A-16, A-18 *.TEL 2-2, 5-3, A-3, A-17
*.DBT A-15 to A-16, A-18 *.TI 4-142, A-18
*.DCL A-9, A-18 *.TIX 4-141, 4-265, A-18
*.DE_ 4-98, A-14, A-17 *.TPX 4-103, 4-179
*.DED A-19 *.UCI 4-291, A-15
*.DEL 2-2, A-5, A-18 *.W00, *.W01, ... A-15 to A-16
*.DFL 4-406 to 4-407, A-17 *.WEX A-15 to A-18
*.DGN A-18 *.WMF 4-103
*.DLL A-3, A-14 *.WSP A-15 to A-16
*.DXR 4-290, A-15 to A-16, A-18 / (slash) 4-304
*.EXE A-3, A-14 : (colon) 4-215, 4-217, 4-220, 4-222, 4-225, 4-229
*.GLX A-18 < (less) 4-20
*.GS? A-19 <> (not equal) 4-48, 4-240 to 4-241, 4-434
*.HLP 4-412, A-3, A-14 > (greater) 4-20, 4-243
*.INI 4-179, 5-2, A-3, A-15 to A-17 ? (question mark) 4-218, 4-220, 4-222, 4-225, 4-320, 4-378,
*.ISU A-3 4-416, 4-436
*.LIS A-15 to A-18 _ (underline) 4-243
*.LOG A-18 __INAM__ 4-197

3BDS 100 595R401 i

Function Chart Builder User’s Guide
Index

… (ellipsis) 4-243 All Elements 4-336

Allow confirmation by mouse for target control 4-345
Numerics AMPL 1-12
1, 2, … (Activate Diagnostics Windows) 4-430 AMPL PC and DB Element Libraries 4-91
1, 2, … (Activate Section Windows) 4-410 APB 1-11
Application
A program 4-239, 4-434
abblogo.WMF 4-103 documentation 4-31, 4-33
About retrieval 4-99, 4-178, 4-254, 4-277, 4-392
Diagnosis 4-460 window
Diagnostics 4-431 of Diagnosis 4-242
Function Chart Builder 4-413 of FCB 3-7
About On-line and Off-line States 4-143 Application Builder 1-11, 4-4, 4-91, 4-105, 4-141
AC 100 Series 1-10, 4-166 to 4-167, 4-169, 4-171, 4-174 to Application Checksum 4-165, 4-396
4-176, 4-193, 4-385 to 4-386, 4-388, 4-398 to 4-399, 4-401 Arrange Icons 4-408
to 4-405, 4-407 in Diagnosis 4-459
AC 110 1-10 in Diagnostics 4-430
AC 160 1-10 Assignment of Access and Launch Permissions G-1
AC 166 4-91 Attributes of TC/CI terminals 4-206
AC 400 Series 1-10
AC 55 1-10 B
AC 70 1-10 Backtranslate
AC 80 1-10, 4-91 source code 4-269
Accelerator keys 4-87 target code 4-277
Accessing module diagnosis Backtranslate Source 4-269
via Error Report Backtranslate source code 4-140
in the Diagnosis program 4-188 Backtranslate Target Code 4-277
in the Diagnostics program 4-183 Backup 5-1
via Module List Base software 4-241, 4-411
in the Diagnosis program 4-189 identification of 4-49
in the Diagnostics program 4-184 BCD 1-11
Activate All Force Values 4-403 Block Program 4-391
Activate Force Values 4-401 Blocking the application program 4-53
Activate section windows 4-410 Bus Configuration Builder 4-256
Activate windows in Diagnostics 4-430 Bus Configuration Database 1-11, A-15
Actual value 4-196, 4-202 Bus Configuration Interface 1-11
Additional node type 2-2, 4-243, 4-255 BUS_nnn directory A-19
Address
in Diagnosis 4-437, 4-439, 4-454 C
in Diagnostics 4-417 to 4-418 Cable 4-46
Administrator G-1 Calculated symbol 4-203, 4-329
AdvaBuild Communicator G-1 Call Parameters 4-321
AdvaBuild Engineering Board Server G-1, G-7 Cascade 4-45, 4-408
Advant Controller 100 Series 1-10 in Diagnosis 4-459
Advant Controller 400 Series 1-10 in Diagnostics 4-430
Advant Fieldbus 100 4-212 Change order of PC elements 4-120, 4-356
Advant Station 100 Series Engineering Station 1-1, 1-10 Channel
AF 100 1-10, 4-256 states 4-446
AF100 OPC 1-11 types 4-442

ii 3BDS 100 595R401

 Function Chart Builder User’s Guide
Index

Channel Diagnosis Conventions 4-192

Diagnosis command 4-455 Copy 4-132, 4-311
window 4-444 in Diagnosis 4-453
Check PC Source 4-268 Copyright 4-413
Check source code 4-142, 4-268 of Diagnosis 4-460
Checksum 4-98, 4-165, 4-396 of Diagnostics 4-431
CI57x LON Interface Generator 3-8 Correct paste conflicts 4-133
CIERRORS.LIS 4-114, A-16 COTL0000.C00 4-255
Circuit 3-1, 4-35, 4-90, 4-113 to 4-114, B-4 CRC 4-165, 4-396
directory A-15 Create 4-299
source code syntax D-16 circuit 4-38
CIUSED.DAT A-17 DB element 4-16, 4-135, 4-302
Clear PROM 4-393 DB section 4-16
Client G-1 force value 4-385
Close All 4-409 to 4-410 node structure 4-40
Close All Diagnosis 4-460 object 4-91
COIL*.b?? A-19 PC element 4-11, 4-299
Cold start of target 4-393 PC program 4-9, 4-245
Compatibility of software and source code 2-1 PC section 4-9
COMPILE.LOG A-3, A-17 project 4-91
Computing Time 4-358 section 4-245
Configuration of AdvaBuild Communicator G-1 source code BAK files 4-345
Confirmation before delete 4-348 symbol 4-136, 4-305
Connect TC/CI terminal 4-137, 4-307
target 4-47, 4-388 Test Table entry 4-310
terminal 4-25, 4-121, 4-123, 4-374, 4-377 type circuit 4-20, 4-37
Connect (common) 4-374 unit 4-383
Connect AS 100ES to an AC 100 Series Target 4-151 Creation of Own Templates 4-103
Connect Selected 4-377 Cross Ref. of sel. DB Elem 4-341
Connection rules 4-192 Cross Ref. of sel. PCElem 4-341
Consistency of diagnosis Cross Reference (view) 4-339, 4-341
with the Diagnosis program 4-190 Cut 4-131, 4-311
with the Diagnostics program 4-185 to 4-186 Cycletime 4-399
Contents Cyclic Display 4-398 to 4-399
of Diagnosis Help 4-460
of Diagnostics Help 4-430 D
of Help 4-411 Data flow of FCB B-1
context menu 4-125, 4-214 Date 4-394
Context-sensitive help 4-411 DB 1-11
in Diagnosis 4-460 DB element 4-135, 4-412
in Diagnostics 4-431 DB element library 4-91, 4-98, 4-179, A-5
Control menu 4-208 DB Element Reference 4-412
Controls DB Section window 4-217
in Title Bar 4-208 DB Terminal Values 4-323
of Diagnosis 4-432 DB_LIB A-5
of Diagnostics 4-414 DBGENDEF.BAX 4-93, 4-244, 4-263, A-15 to A-17
in Toolbar 4-209 DBPCVERS.INI A-17
of Diagnosis 4-432 DCOM G-1
of Diagnostics 4-414 DCOMCONF G-2

3BDS 100 595R401 iii

Function Chart Builder User’s Guide
Index

Deactivate All Force Values 4-404 project A-14

Deactivate Force Values 4-402 project root A-14
DEAM*.LO A-14 reference A-3
Deblock Program 4-391 release A-3
Deblocking the application program 4-52 structure A-1
Declare symbol 4-20 type circuit A-16
Default value 4-196, 4-202 Disconnect 4-382, 4-391
Define TC/CI terminal 4-23 target 4-391
Delete terminal 4-126, 4-382
connection 4-126 Disintegrate type circuits 4-111, 4-141, 4-255
DB element 4-19, 4-319 Display
element 4-318 adapter 4-101
force value 4-387 terminals 4-61, 4-167
last PC element 4-126 Document
multiple PC elements 4-318 of application program 4-31, 4-33
object 4-105 parts 4-139, 4-283
PC element 4-126, 4-318 windows 4-212
PC program 4-247 Document Texts 4-335
PC terminal 4-387 Dynamic link library A-3
project 4-105
section 4-247 E
symbol 4-319 Edit
TC/CI terminal 4-319 call parameters 4-321
Test Table entry 4-319 circuit 4-114
unit 4-384 DB element 4-135
Delete All (force values) 4-387 DB terminal values 4-18, 4-323
Delete All Reported Errors 4-458 document text 4-335
Delete Name 4-323 force value 4-385
Delete Reported Errors (in Diagnostics) 4-429 menu 4-299
Delete Reported Errors * (in Diagnosis) 4-458 of Diagnosis 4-453
Delete Section 4-247 node 4-107
Diagnose Module 4-428 node structure 4-116
Diagnosis symbol 4-136, 4-326
program 4-55, 4-397, 4-432 symbol value 4-328
text file A-3 TC/CI terminal 4-137, 4-331
Diagnostic procedures TC/CI terminal attributes 4-308
with the Diagnosis program 4-186 type circuit 4-20, 4-109
with the Diagnostics program 4-181 unit 4-383
Diagnostics Editors 4-3
command 4-397 Electromagnetic compatibility 4-86
program 1-12, 4-55, 4-82, 4-397, 4-414 Element libraries 4-91
Diagrams 4-3 Element Library Handling 4-98
Directory EMC 4-86
BUS_nnn A-19 engineering board G-1, G-7
circuit A-15 Environmental requirements 1-1
level1 type circuit A-19 Error messages 5-1
level2 type circuit A-19 Error Report 4-397
node A-16 Diagnosis command 4-453
NODES A-15 window 4-55, 4-242

iv 3BDS 100 595R401

 Function Chart Builder User’s Guide
Index

of Diagnosis 4-436 Generate BCD Data 4-256

of Diagnostics 4-416 Generate Source 4-257
Evaluate symbols 4-199 Generate Target Code 4-252, 4-255
Executable Goto (PC terminal) 4-373
file A-3 Goto Element 4-352
unit 4-74, 4-193 Goto Page 4-354
Execution Order 4-356
Exit 4-297 H
in Diagnosis 4-452 Headline 4-103, 4-365, 4-367
in Diagnostics 4-427 Help 4-7
Expand node data 4-42, 4-117, 4-267, B-6 file A-3
Expand Node Structure 4-267 menu 4-411
Export (Test Values) 4-407 of Diagnosis 4-460
Export DB Section 4-279 of Diagnostics 4-430
Expression C-1 on context 4-411
Extended DB Elements 1-11 on node 4-411
How to Use Help 4-411
F in Diagnosis 4-460
FCB 1-11 in Diagnostics 4-431
directory structure A-1
files A-3 I
release and version 4-413 Identification
File | Print, DB Names Included 4-291 of application program 4-239, 4-434
File | Print, PC Names Included 4-292 of base software 4-49, 4-241
File menu 4-244 of options 4-49, 4-241
of Diagnosis 4-447 IF D-13
of Diagnostics 4-421 Import (Test Values) 4-405
Files A-3 Import DB Section 4-280
Find 4-319 Indicators
Fixed page number 4-365, 4-372 in Status Bar 4-211
FOOT001.TPX 4-103, A-14 of Diagnosis 4-433
Footer 4-103, 4-335 of Diagnostics 4-415
Force terminals 4-169 Initialization file A-3, A-17
Force Value 4-385 Initialize 4-244
Formula C-2 internal data representation 4-5
Function object 4-101
chart 4-216 Insert
parameter 4-308 PC element 4-119
Function Chart 4-335 PC terminal 4-387
Function Chart Builder 1-11 to 1-12 Installation 2-1
Function Chart Editor 1-11 Instance name 4-194
Function-oriented project engineering 4-35, 4-89 Instantiate a type circuit 4-28, 4-109, B-2
Internal data representation 4-2, 4-212
G Invert 4-387
Generate Item Designations 4-338
source code 4-27, 4-140, 4-257
on exit 4-297, 4-344 K
target code 4-45, 4-252, B-7 Keep PC connections as virtual connections 4-346
for additional node type 4-255 Keyboard 4-86

3BDS 100 595R401 v

Function Chart Builder User’s Guide
Index

L of Diagnosis 4-453
Late instantiation 4-1, 4-41, 4-116 of Diagnostics 4-427
Layout 3-7, 4-5, 4-101, 4-364 Window 4-408
template 4-5, 4-296 of Diagnosis 4-459
Level1 type circuit directory A-19 of Diagnostics 4-429
Level2 type circuit directory A-19 Menu Bar 4-243
List file 4-320 Minimize output while working 4-344
List Modules 4-428 Modify Item Destination 4-356
Listing Module Diagnosis
of download 4-52 Diagnosis command 4-453
of target code generation 4-45 window 4-440
Load Application 4-391 Module Diagnostics window 4-419
Load application to AC 55, 70, or 110 4-50, 4-166 Module List
Locate a circuit 4-41, 4-114 Diagnosis command 4-453
Log window
in Diagnosis 4-449 of Diagnosis 4-438
in Diagnostics 4-423 of Diagnostics 4-418
Log report or diagnosis 4-423 Monitor terminals 4-61, 4-167
in Diagnosis 4-449 Mouse 1-1, 4-82
Logfile Setup MP 200/1 1-11
of Diagnosis 4-449 Multiple selection
of Diagnostics 4-423 by keys 4-87
logo 4-103 by mouse 4-83
Loop 4-90, D-14 contiguous 4-128
of partial subtree on lower level 4-130
M of PC elements 4-127, 4-355
Maintenance 5-1 of whole executable unit 4-129
Manuals 4-412 to 4-413
Mark 4-374 N
MB 300 1-11 NAM 4-292
MB300 OPC 1-11 Name 4-193, 4-322
Memory Calculation 4-362 Name Table
Menu command 4-410
Edit 4-299 window 4-224
of Diagnosis 4-453 National character sets D-3
File 4-244 Navigate
of Diagnosis 4-447 in Error Report and Module List
of Diagnostics 4-421 of the Diagnosis program 4-189
Help 4-411 of the Diagnostics program 4-184
of Diagnosis 4-460 in Function Chart Builder 4-81
of Diagnostics 4-430 New Section 4-245
Options 4-343 New Window 4-408
PC-Section 4-352 Node 3-4, 4-89, 4-107, B-1
PC-Terminal 4-373 directory A-16
Target 4-388 type 4-411
of Diagnosis 4-458 additional 2-2, 4-243, 4-255
of Diagnostics 4-428 Node structure 3-3, 4-35, 4-89, 4-116, B-5
Test 4-398 source code syntax D-26
View 4-335 NODES directory A-15

vi 3BDS 100 595R401

 Function Chart Builder User’s Guide
Index

Node-specific element library A-17 PC element 4-119 to 4-120, 4-126, 4-412

Non-calculated symbol 4-202, 4-329 PC element library 4-91, 4-98, 4-179, A-9
additional A-19
O project-specific A-15
Object 4-1, 4-91, 4-101, 4-105, 4-107 PC Element Reference 4-412
structure 4-3 PC Section window 4-213
ODB password 4-94, 4-250 PC_LIB A-9
On Context 4-411 PC-Section menu 4-352
in Diagnosis Help 4-460 PC-Terminal menu 4-373
in Diagnostics Help 4-431 Phys. Addresses 4-338
On Node 4-411 Power supply 4-46
On-line Preferences 4-343
editing Preparations in APB 4-4
of data base 4-77 Prepare
of PC program 4-75 circuit 4-113
rules 4-193 documentation 4-31, 4-33
mode 4-60, 4-86, 4-88, 4-143 terminals for display 4-58, 4-70
On-line Builder 1-12, 4-141, G-1, G-7 terminals for forcing 4-65
On-line Mode 4-248 type circuit 4-107
On-line Preparation Mode 4-248 Prepared Variables 4-337
Open Preventive maintenance 5-1
object list 4-91 Print 4-138, 4-281
PC program 4-246 in Diagnosis 4-450
project 4-91 in Diagnostics 4-424
Open Section 4-246 Print Setup 4-295
Options 2-2, 4-241, 4-411 in Diagnosis 4-451
identification of 4-49 in Diagnostics 4-426
menu 4-343 Print This Page 4-140
Options Report 4-397 Print This View 4-140
window 4-48, 4-241 Printer 4-101
Output Process Conflict 4-320
command 4-410 Product
window 4-223 name 2-2
of Diagnosis 4-447 verification 2-2
Overwrite source code 4-344 version 2-2
PROFIBUS library A-19
P PROFIBUS Library Editor 3-8
Page division 4-14, 4-364 PROFIBUS.MDB A-9
Page Division Rules 4-206 Project
Page Layout 4-364 directory A-14
Page Number 4-365 root directory A-14
Page Setup 4-296 PROJROOT.INI A-14
PARDAT 4-333 PROM 4-53, 4-392 to 4-393
Parsers D-3 Prompt before saving ODB 4-344
Password 4-94, 4-163, 4-250, 4-395 Protection 4-94, 4-163, 4-250, 4-395 to 4-396
Paste 4-132, 4-311
buffer 4-131 Q
conflict 4-320 quick connect by mouse 4-125
options 4-312 Quick connect by right mouse button 4-345

3BDS 100 595R401 vii

Function Chart Builder User’s Guide
Index

R Save in PROM 4-392

RAM 4-53, 4-392 to 4-393 Saving application in target 4-53
Read new diagnostic data with the Diagnosis program 4-192 Scroll 4-86, 4-88
Rebuild Element Types 4-244 sections 4-118
Redo 4-299 Select for Display 4-385
Reference directory A-3 Select PC elements 4-355
Regenerate objects 4-105, B-8 Separator for automatically created DATs 4-346
Release Series 1-12
directory A-3 Server G-1
notice 4-413 Set Cycletime 4-399
notice of Diagnosis 4-460 Set Date and Time 4-394
notice of Diagnostics 4-431 Set DB Value 4-404
release notes of FCB A-3 Set Password
Remote access protection 4-166 in ODB 4-250
Remove on target 4-395
connection 4-126 Setup Add-Ons 3-8
object 4-105 Setup logfile
Renumber 4-357 of Diagnosis 4-449
Renumber Lower Level 4-357 of Diagnostics 4-423
Replace names, etc., at pasting 4-133, 4-312 Shortcuts 4-87
Report Errors 4-397, 4-428 Show implicitly created comm. DB elements 4-345
Report Options 4-397 Signal name 4-194
Report problems 5-1 Single Display 4-398
Report Status 4-397 Skip Modifications 4-249
REPORT.MSD 5-2 Slide 4-86, 4-88, 4-409
Requirements, environmental 1-1 Soft page number 4-365, 4-372
Resize 4-408 Sort by Item Designation 4-342
in Diagnosis 4-460 Sort by Name 4-342
in Diagnostics 4-430 Sort by Number 4-342
Restart 4-393 Sort order 4-227
Restart personal computer 5-3 SOURCE A-9
Restriction of network programming 4-166 Source code 4-2, 4-140, 4-257, 4-269
Resulting value 4-196, 4-202 Specify layout 4-101
RETL0000.Cpp 4-255 SRC_LIB A-14
Retrieve Application from an AC 100 Series Target 4-178 Start
Rotary switch 4-46 Diagnosis 3-8
Routing via AC400 Series nodes 4-211, 4-388 FCB 3-6, 4-5
Rules Utilities 3-8
of connection 4-192 Start-up of Function Chart Builder 4-92, 4-99
of editing on-line 4-193 State of FCB 4-243
of symbol evaluation 4-199 Status Bar 4-63, 4-211
command 4-342
S Diagnosis command 4-457
Save 4-19, 4-249, 5-1 Diagnostics command 4-427
Save and Load 4-249 of Diagnosis 4-433
Save and restore recent selection 4-344 of Diagnostics 4-415
Save As Status Report 4-397
in Diagnosis 4-447 Diagnosis command 4-453
in Diagnostics 4-421 window 4-48, 4-239

viii 3BDS 100 595R401

 Function Chart Builder User’s Guide
Index

of Diagnosis 4-434 Template 4-5, 4-103, 4-179, 4-296

Stop Display 4-399 Test
Straightforward method 4-89 functions 4-57
Structure Elements 4-336 menu 4-398
Substitute symbols in default connections of TC/CI Test Table
terminals 4-346 command 4-410
Support Virtual Connections 4-345 window 4-65, 4-227
Symbol 4-20, 4-22, 4-136, 4-195, 4-199, 4-202, 4-204, 4- Thumbwheel switch 4-46
326 Tile Horizontally 4-408
evaluation rules 4-199 in Diagnosis 4-459
Symbol Section window 4-220 in Diagnostics 4-430
Symbol Values 4-328 Tile Vertically 4-408
Symbolic in Diagnosis 4-459
expression C-1 in Diagnostics 4-430
formula C-2 Time 4-394
Synchronization of target 4-49 Title Bar 4-75, 4-208
Syntax Toolbar 4-209
of *.TPX Files F-1 command 4-342
of circuit source code 2-1, D-16 Diagnosis command 4-457
of names E-1 Diagnostics command 4-427
of node structure source code D-26 of Diagnosis 4-432
of symbolic expressions C-1 of Diagnostics 4-414
of symbolic formulas C-2 Top of Page Elements 4-336
of TC, CI and NS source code D-1 Trackball 4-86
of type circuit source code D-5 Transfer source code 4-141
rules D-1 Tree diagram 4-216
System administrator G-1 Tutorial 4-4
System DB elements 4-5, A-5 Type circuit 3-2, 4-19, 4-23, 4-90, 4-107, 4-109, B-2 to B-3
classes for AC 100 Series 4-111
T directory A-16
TAB (tabulator) 4-280 for AC 100 Series 4-111
TARGCONF.LIS A-3, A-17 frame 4-266
Target source code syntax D-5
code 4-252, 4-255, 4-277, 4-392
description file 2-2, A-3 U
menu 4-388 underline 4-243
of Diagnosis 4-458 Undo 4-299
of Diagnostics 4-428 paste 4-133
password 4-163, 4-395 replace 4-317
synchronization of 4-49 Unit 4-224, 4-383
Target Access Protection 4-163 Unmark 4-374
Target Password Protection 4-163 Unselect (terminal for display) 4-385
TARGET.001 A-3 Unselect All (terminal for display) 4-385
TARGET.TEL A-3, A-17 Update function chart on apply 4-343
TC/CI Terminal 4-331 Update Slave 4-393
TC/CI terminal 4-23, 4-137, 4-205 Upgrade to new FCB release B-8
attributes 4-308 Upload 4-332
TC/CI Terminal Section window 4-222 Upload Application 4-392
TCERRORS.LIS 4-110, A-16 Upload DB Force List 4-404

3BDS 100 595R401 ix

Function Chart Builder User’s Guide
Index

Upload parameter 4-176 Window

UpTCCI 2-1, 4-105 *.ODB 4-212
Use Channel Diagnosis 4-444
circuit 4-90 DB Section 4-217
commands 4-7 Error Report 4-242
Diagnostics (Diagnosis) program 4-55 of Diagnosis 4-436
help 4-7 of Diagnostics 4-416
keyboard instead of mouse 4-86 menu 4-408
mouse 4-82 of Diagnosis 4-459
names 4-193 of Diagnostics 4-429
symbol 4-22, 4-197, 4-204 Module Diagnosis 4-440
TC/CI terminal 4-205 Module Diagnostics 4-419
type circuit 4-90 Module List
of Diagnosis 4-438
V of Diagnostics 4-418
Validate source code 4-142, 4-268 Name Table 4-224
Value of symbol 4-202 Options Report 4-241
Variant 4-90, D-13 Output 4-223
View of Diagnosis 4-447
all elements 4-336 PC Section 4-213
Channel Diagnosis 4-455 Status Report 4-239
Cross Reference 4-339, 4-341 of Diagnosis 4-434
Error Report 4-453 Symbol Section 4-220
function chart 4-335 TC/CI Terminal Section 4-222
item designations 4-338 Test Table 4-227
menu 4-335 Windows NT 2-1
of Diagnosis 4-453 Working
of Diagnostics 4-427 on a circuit B-4
Module Diagnosis 4-453 on a node structure B-5
Module List 4-453 on a type circuit B-3
physical addresses 4-338 with AC 100 Series B-7
prepared variables 4-59, 4-337 with AC 400 or MP 200/1 node B-1
Status Bar 4-342 Workspace 4-348
of Diagnosis 4-457
of Diagnostics 4-427 X
Status Report in Diagnosis 4-453 XDB 1-12
structure elements 4-336
Toolbar 4-342 Z
of Diagnosis 4-457 Zoom 4-337
of Diagnostics 4-427
top of page elements 4-336
Virtual
connection 4-345 to 4-346
element 4-1, 4-116, 4-192
terminal 4-116

W
Warning at referencing an undefined symbol or TC/CI
terminal 4-348

x 3BDS 100 595R401

aaaaa
3BDS 100 595R401
April 2003