AdvantController 400 Series

Advant® OCS $03/&RQILJXUDWLRQ
with Master software Advant® Controller 400 Series
Reference Manual
3BSE 002 417R601
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, MasterAid, MasterBus, MasterPiece, and MasterView are registered trademarks of ABB Asea Brown Boveri Ltd.,
Switzerland.
MasterGate, MasterFieldbus, and MasterNet are trademarks of ABB Asea Brown Boveri Ltd., Switzerland.
Advant, AdvaBuild, and AdvaInform are registered trademarks of ABB Asea Brown Boveri Ltd., Switzerland.
AdvaCommand, AdvaSoft, Advant Station, AdvaBuild On-line Builder, Advant Controller, and Advant Fieldbus are trademarks
of ABB Asea Brown Boveri Ltd., Switzerland.
IBM and all IBM-products mentioned in this publication are registered trademarks of International Business Machines Corp.
Microsoft, MS-DOS, and Windows are registered trademarks, Windows NT is a trademark of Microsoft Corporation.
Adobe and Acrobat are trademarks of Adobe Systems Incorporated.
NOTICE
The information in this document is subject to change without notice and should not be construed as a commitment by ABB
Industrietechnik GmbH. ABB Industrietechnik GmbH assumes no responsibility for any errors that may appear in this
document.
In no event shall ABB Industrietechnik 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 Industrietechnik 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 Industrietechnik 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 Industrietechnik GmbH 1999.

3BSE001264/E
Template: 3BSE001286/E
3BSE 002 417R601

AMPL Configuration $GYDQW® Controller 400 SeriesReference Manual
Table of Contents
TABLE OF CONTENTS
Chapter 1 - Introduction
1.1 General Information................................................................................................. 1-1
1.2 Manual Organization ............................................................................................... 1-1
1.3 Conventions ............................................................................................................. 1-1
1.4 Related Documentation............................................................................................ 1-2
1.5 Release History ........................................................................................................ 1-2
1.6 Terminology............................................................................................................. 1-3
1.6.1 Volumes and Segments ........................................................................... 1-3
1.7 Differences between the Hardware Platforms ......................................................... 1-4
Chapter 2 - Outline Description

2.1 Introduction.............................................................................................................. 2-1
2.2 Data Base ................................................................................................................. 2-2
2.2.1 General.................................................................................................... 2-2
2.2.2 Identifying Data Base Elements ............................................................. 2-5
2.2.2.1 User-defined Names......................................................... 2-6
2.3 PC Programs ............................................................................................................ 2-8
2.3.1 Execution Control ................................................................................... 2-8
2.3.1.1 Choosing Cycle Times ..................................................... 2-8
2.3.1.2 Altering the Default Set of Cycle Times........................ 2-10
2.3.1.3 Scanning Process Inputs................................................. 2-12
2.4 Working Modes of Advant Controller 400 Series ................................................. 2-13
2.5 Ordering Working Modes ...................................................................................... 2-14
2.6 Start Modes ............................................................................................................ 2-14
2.7 Relationship between Start Modes and Working Modes....................................... 2-15
2.8 Relationship between On-line Builder Commands and Working Modes.............. 2-17
2.8.1 Enable CONFIGURATION Mode........................................................ 2-17
2.8.2 Disable CONFIGURATION Mode ...................................................... 2-18
2.8.3 Resetting the Controller ........................................................................ 2-19
2.9 Starting Advant Controller 400 Series................................................................... 2-20
2.9.1 Programmed Start ................................................................................. 2-21
2.9.1.1 Start Module................................................................... 2-22
2.9.1.2 Programmed Restart after Power Failure....................... 2-22
2.9.1.3 Example ......................................................................... 2-25
2.9.2 Overview of Programmed Start ............................................................ 2-26
3BSE 002 417R601 i

Table of Contents
CONTENTS (continued)
Chapter 3 - Application Building
3.1 Application Building................................................................................................ 3-1
3.2 Data Base Handling.................................................................................................. 3-1
3.2.1 Dimensioning the Data Base................................................................... 3-1
3.2.1.1 Dialog Handling ............................................................... 3-2
3.2.1.2 Dimensioning Parts of the Data Base............................... 3-4
3.2.1.3 Memory Space.................................................................. 3-8
3.2.1.4 Memory Requirements for certain Functions................... 3-9
3.2.1.5 TransferringtheDimensioningDatatotheAdvant Controller 400 Series
3-11
3.2.1.6 Quitting DIMDB ............................................................ 3-12
3.2.2 Editing the Data Base............................................................................ 3-12
3.2.2.1 Creating Data Base Elements ......................................... 3-12
3.2.2.2 Modifying Existing Data Base Elements ....................... 3-16
3.2.2.3 Deleting Data Base Elements ......................................... 3-17
3.2.3 Data Base Documentation..................................................................... 3-17
3.2.3.1 Creating a Data Base Printout ........................................ 3-17
3.2.3.2 Listing a Data Base Diagram.......................................... 3-17
3.2.3.3 Listing the Group Alarm Members ................................ 3-19
3.2.4 Compressing the Data Base Backup ..................................................... 3-20
3.2.5 Default Values for Data Base Handling ................................................ 3-21
3.3 Structuring PC Programs........................................................................................ 3-21
3.4 PC Dimensioning ................................................................................................... 3-22
3.4.1 Dimensioning the Space for PC Programs............................................ 3-22
3.4.2 Modifying the Size of the Symbol Table .............................................. 3-23
3.5 Entering and Editing PC Programs ........................................................................ 3-25
3.5.1 General .................................................................................................. 3-25
3.5.2 Enabling the BUILD Mode ................................................................... 3-26
3.5.3 Inserting PC Elements........................................................................... 3-26
3.5.3.1 Dialog Handling ............................................................. 3-26
3.5.3.2 Graphic/Non-graphic Presentation ................................. 3-29
3.5.3.3 Assigning a name ........................................................... 3-30
3.5.4 Connecting PC Elements....................................................................... 3-30
3.5.4.1 Dialog Handling ............................................................. 3-31
3.5.4.2 Graphic/Non-graphic Presentation ................................. 3-32
3.5.4.3 Connecting PC Element Inputs ...................................... 3-32
3.5.4.4 Connecting PC Element Outputs.................................... 3-33
3.5.4.5 Assigning Name and Unit .............................................. 3-34
ii 3BSE 002 417R601

Table of Contents
3.5.4.6 Disconnecting a Terminal .............................................. 3-36

3.5.4.7 Long Dialog-Short Dialog ............................................. 3-37
3.5.5 Deleting PC Elements........................................................................... 3-38
3.5.6 Listing PC Programs............................................................................. 3-39
3.6 Disabling the BUILD ModeDIBM ........................................................................ 3-41
3.7 Connecting Unconnected Inputs............................................................................ 3-41
3.8 Creating Security Copies ....................................................................................... 3-41
Chapter 4 - Commissioning and Testing

4.1 Modify Permission................................................................................................... 4-1
4.1.1 Enabling the Modify Permission ............................................................ 4-2
4.1.2 Disabling the Modify Permission ........................................................... 4-2
4.1.3 Listing the Modify Permission ............................................................... 4-2
4.2 PC Program Tests..................................................................................................... 4-3
4.2.1 Listing Variables ..................................................................................... 4-3
4.2.2 Blocking the PC Program Execution ...................................................... 4-5
4.2.3 Deblocking the PC Program Execution .................................................. 4-5
4.2.4 Listing the Status of PC Programs.......................................................... 4-6
4.2.5 Reading and Modifying a Variable Value ............................................... 4-7
4.2.6 Modifying the Name of a Statement or Variable .................................... 4-9
4.2.7 Displaying a PC Element with Variable Values.................................... 4-12
4.2.8 Displaying the Variable Values in a Table ............................................ 4-15
4.3 System Load .......................................................................................................... 4-17
4.3.1 Blocking on Overload........................................................................... 4-18
4.4 Switching running PC Programs............................................................................ 4-19
Chapter 5 - Changing an Application Program On-line

5.1 Modifying PC Programs On-line............................................................................. 5-1
5.1.1 Inserting PC Elements ............................................................................ 5-1
5.1.2 Connecting PC Elements ........................................................................ 5-2
5.1.3 Deleting PC Elements............................................................................. 5-3
5.1.4 Important Notes for On-line Changing................................................... 5-4
5.1.4.1 Modifying a Blocked Control Module............................. 5-4
5.1.4.2 Modifying Executing PC Elements.................................. 5-5
5.1.5 Adding a Step in a Sequence ................................................................ 5-12
5.1.6 Removing a Step in a Sequence............................................................ 5-14
5.1.7 Adding a Slave Module ........................................................................ 5-15
5.1.8 Removing a Slave Module.................................................................... 5-15
3BSE 002 417R601 iii

Table of Contents
5.1.9 Removing an Execution Unit ................................................................ 5-15

5.2 Modifying the Data Base On-line .......................................................................... 5-16
5.2.1 General Information .............................................................................. 5-16
5.2.2 Modifying an I/O Module On-line ........................................................ 5-16
5.2.2.1 Modifying a Data Base Parameter.................................. 5-16
5.2.2.2 Modifying an I/O Board Type ........................................ 5-17
5.2.2.3 Adding I/O Modules and Signals ................................... 5-17
5.2.2.4 Deleting I/O Modules and Signals ................................. 5-17
5.2.3 Changing Controllers along Advant Fieldbus 100................................ 5-17
5.2.4 Changing Controllers along MasterFieldbus ........................................ 5-18
5.2.5 Changing the Data Base Part of Functional Units On-line ................... 5-18
5.2.6 Changing other Data Base Elements On-line........................................ 5-18
Chapter 6 - Documentation
6.1 Selection of Output Device ...................................................................................... 6-1
6.2 Selecting the Presentation Form............................................................................... 6-1
6.3 Setting Page Size...................................................................................................... 6-2
6.4 Page Division and Numbering ................................................................................. 6-2
6.4.1 Generating Page Divisions Automatically .............................................. 6-3
6.4.2 Modifying the Page Division Manually .................................................. 6-3
6.4.3 Modifying Page Numbering.................................................................... 6-6
6.4.4 Listing the Page Number......................................................................... 6-6
6.5 Hard and Soft Page Breaks ...................................................................................... 6-7
6.6 Headlines.................................................................................................................. 6-9
6.7 Document Texts ..................................................................................................... 6-10
6.8 Printing a PC Program Structure............................................................................ 6-11
6.9 Printing a PC Program List .................................................................................... 6-15
6.10 Printing a PC Diagram ........................................................................................... 6-17
Chapter 7 - Backup and Transfer of Application Data

7.1 General ..................................................................................................................... 7-1
7.2 Data Storage Description ......................................................................................... 7-2
7.2.1 Maximal Segment Size ........................................................................... 7-2
7.2.2 USER Volume ......................................................................................... 7-3
7.2.2.1 List of User Disk Application Segments .......................... 7-5
7.2.2.2 User Disk Application Segments Backup Handling ........ 7-6
7.2.2.3 Backup Commands........................................................... 7-8
7.2.2.4 User Disk Application Segments Mismatch .................. 7-11
iv 3BSE 002 417R601

Table of Contents
7.2.3 SRCE Volume ........................................................................................7-11

7.3 Total Backup ...........................................................................................................7-11
7.3.1 Dumping the Complete Application ..................................................... 7-12
7.3.2 Loading the Complete Application....................................................... 7-13
7.4 Dumping and Loading for Redimensioning .......................................................... 7-14
7.4.1 Dumping the Data Base ........................................................................ 7-15
7.4.2 Dumping PC Programs ......................................................................... 7-16
7.4.3 Loading the Data Base.......................................................................... 7-16
7.4.4 Loading PC Programs........................................................................... 7-17
7.5 Data Transfer via Source Code .............................................................................. 7-18
7.6 Loading AAB Files................................................................................................ 7-19
7.7 Summary of Dump Commands ............................................................................. 7-20
Chapter 8 - General Commands

8.1 Help Function ...........................................................................................................8.1
8.2 Adjusting Date and Time ..........................................................................................8.2
8.3 Getting the Last Item Designation ............................................................................8.3
8.4 Repeating the Previous Command............................................................................8.4
8.5 Hardcopy...................................................................................................................8.4
8.6 Terminating a Session ...............................................................................................8.4
8.7 Choosing Graphical or Non-graphical Presentation .................................................8.4
8.8 Listing Text Segments ..............................................................................................8.5
8.9 Locking/Unlocking PC Programs.............................................................................8.6
Chapter 9 - Communication Between PC Programs and Nodes

9.1 General..................................................................................................................... 9-1
9.2 Example 1: Transferring Data to Another Node using DS Elements ...................... 9-4
9.3 Example 2: Expanding a Data Set ........................................................................... 9-9
9.4 Example 3: DAT DB Elements Present but no DS DB Elements ......................... 9-10
Chapter 10 - Event Set Handling

10.1 Configuration of Event Set .................................................................................... 10-1
10.1.1 Event Set Overview .............................................................................. 10-1
10.1.2 Configuration of Event Set in Advant Controller 400 Series ............... 10-5
10.1.2.1 Dimension the Data Base for Event Set Handling ......... 10-5
10.1.2.2 Create the Event Channel Elements AIEV, DIEV ......... 10-5
10.1.2.3 Create the Event Set Element EVS(R)........................... 10-7
3BSE 002 417R601 v

Table of Contents
Appendix A - Working Example

1.1 Working Example.................................................................................................... A-1
vi 3BSE 002 417R601

$03/&RQILJXUDWLRQ$GYDQW&RQWUROOHU6HULHV5HIHUHQFH0DQXDO
6HFWLRQ *HQHUDO,QIRUPDWLRQ
Chapter 1 Introduction
1.1 General Information

This manual applies to AMPL configuration of the Advant Controller 410 and Advant
Controller 450. The Advant Station 100 Series Engineering Stations serve as engineering
stations for AMPL configuration with the On-line Builder. You can also perform some of the
described functions with the Function Chart Builder (see Function Chart Builder User’s Guide).
1.2 Manual Organization

Chapter 2, Outline Description is a general overview of functions and characteristics of the
Advant Controller 400 Series and the engineering tools from the configuration point of view.
Chapter 3, Application Building describes the main steps of application building.
The remaining chapters describe other aspects of configuration in detail as well as necessary
commands and how to use them.
1.3 Conventions
Keyboard Interaction
When you read You should
<F4> Press the key labeled F4.
<Ctrl-Break> Press the Ctrl key while pressing the key labeled Break.
Syntax
In this manual, the syntax of each command is described in the form of the command name,
followed by the arguments that are to be specified. The arguments are separated with symbols
such as the comma “,”, slash “/”, semicolon “;” or right angle bracket “>”. To carry out a
command, enter the command syntax and press the Enter key.
• Bold strings are the command names and arguments; type them as they appear.
• Italic strings represent substitutable arguments.
• Brackets “[ ]” around an argument name indicate that the argument is optional.
• Arguments to use alternatively are indicated by a vertical bar (in some syntax descriptions,
alternative choices are represented by an italic string and a separate explanation of its
substitutions).
The following conventions are used in examples of screen dialogs:
• Bold strings represent input from the user.
• Normal strings represent dialog text from the Advant Controller 400 Series or the
engineering station.
3BSE 002 417R601 1-1

&KDSWHU ,QWURGXFWLRQ
1.4 Related Documentation

A list of related documents follows below:
Table 1-1. Related Documentation
Manual Description
Advant Controller 410 Contains a description of Advant Controller 410 and its
User’s Guide functions.
Advant Controller 450 Contains a description of Advant Controller 450 and its
User’s Guide functions.
On-line Builder Describes all On-line Builder commands. Command sets
Reference Manual and working methods are described as well as
command file handling aspects.
Function Chart Builder Contains a description of the configuration of AMPL
User’s Guide application programs graphically.
AMPL Application Building Manual on the ABB MasterProgramming Language
Reference Manual (AMPL).
PC Elements Data for all PC elements in Advant Controller 410/450.
Advant Controller 400
Series
Reference Manual
Data Base Elements Data for all data base elements in
Advant Controller 400 Advant Controller 410/450.
Series
Reference Manual
MasterView 320 Complete manual for MV 320 containing descriptions,
User’s Guide operating instructions, linkages to PC programs,
descriptions of error messages and a table of ASCII
codes.
Source Code Handling Contains descriptions and instructions for use of AMPL
Reference Manual source code for application programs and data bases.
Advant Station 500 Series Manual for Advant Station 500 Series Operator Station.
Operator Station
User’s Guide
1.5 Release History

Version 3BSE 002 417R0001 is the initial version.
Version 3BSE 002 417R0201 contains information about S800 and Master Fieldbus 100.
Version 3BSE 002 417R0301: smaller additions only.
1-2 3BSE 002 417R601

6HFWLRQ 7HUPLQRORJ\
Version 3BSE 002 417R0401: Instance names added.

Version 3BSE 002 417R0501: Profibus dimensioning added.
Version 3BSE 002 417R601: Additions for AC450 2.2 and AC410 1.4.
1.6 Terminology
Advant Controller 100 Series/AC 100 Series

The terms “Advant Controller 100 Series” and “AC 100 Series” are used for Advant
Controller 110.
Advant Controller 400 Series/AC 400 Series

The terms “Advant Controller 400 Series” and “AC 400 Series” are used for Advant
Controller 410 and Advant Controller 450.
AF 100
The abbreviation “AF 100” is used for Advant Fieldbus 100.
DB
The term “DB” is used for the Advant Controller 400 Series data base.
1.6.1 Volumes and Segments

The On-line Builder has access to two volumes, SRCE and USER. On the engineering station,
a set of these two volumes exists in order to store any target-specific data for each defined
target. Depending on the target selection on the engineering station, the corresponding set of
volumes (SRCE and USER) are available and refer to the directories within the directory
structure of the selected target.
It is recommended that you use the SRCE volume, which is the default volume when you work
with the On-line Builder, rather than the USER volume. The USER volume contains different
segments with various application data for internal use of the On-line Builder. See also Section
7.2, Data Storage Description.
Each volume may contain a number of segments. A segment is a given quantity of data or
AMPL source code which is grouped together. A segment is handled as a unit by the mass
storage and has a segment name, which corresponds with a file on the appropriate directory.
A segment has the following segment identifier containing a colon and a period as separators:
volume:segment.extension.
The following characters are valid (other characters may appear in volume names given by the
system):
Volume = Four ASCII characters; A-Z, a-z, 0-9
Segment = One to eight ASCII characters; A-Z, a-z, 0-9
3BSE 002 417R601 1-3

&KDSWHU ,QWURGXFWLRQ
Extension = Two ASCII characters; A-Z, a-z, 0-9

Example:
USER:ABCD.AA
In syntax definitions, the extension of a segment is not mentioned, but is a part of “segment.”
See the On-line Builder Reference Manual for information about wildcards.
1.7 Differences between the Hardware Platforms

The different hardware platforms of Advant Station 100 Series Engineering Stations result in
some implementation differences for the On-line Builder software. The user interface described
in this manual applies to the On-line Builder for Advant Station 100 Series Engineering Stations
with the Engineering Board DSPU131. The differences in implementation are described in the
On-line Builder Reference Manual.
1-4 3BSE 002 417R601

6HFWLRQ ,QWURGXFWLRQ
Chapter 2 Outline Description
2.1 Introduction
The application program of an Advant Controller 400 Series is stored in its read/write memory.
Applications realized with ABB MasterPiece Language (AMPL) contain a data base (DB) part
and up to 99 PC programs which communicate with the data base. Dividing the memory into a
part containing DB and a part containing PC is necessary for application building and is defined
as DB dimensioning and PC dimensioning, respectively.
A redimensioning procedure can be required in order to displace the memory amounts of
dimensioned functions, or of the DB part (PC part) as a whole (see Section 2.8.3, Resetting the
Controller), if the internal structure of the application (for example, the number of PC programs
or the number of I/Os) changes in a wider range than expected.
Figure 2-1 shows schematically how the process, the data base and a PC program interact to
control the process.
Input Signals Output Signals
Data Base PC Program Data Base
Process
Figure 2-1. Interaction between Data Base, PC Program, and the Process
3BSE 002 417R601 2-1

&KDSWHU 2XWOLQH'HVFULSWLRQ
2.2 Data Base
2.2.1 General
In the Advant Controller 400 Series, the data base is used for a number of purposes:
• Definition of the I/O system, definition of buses, etc.
• Intermediate storage of data which is to be transferred between:
– I/O system and PC programs
– PC programs
– Advant Controller 400 Series controllers
– Advant Controller 400 Series and the Advant Station 500 Series Operator Station
– Advant Controller 400 Series and third-party devices.
The Advant Controller 400 Series data base can be populated (filled) with data base elements.
Different kinds of data base elements exist for different purposes. The number of DB elements
of one kind is identical to the number of times it is used in an application and can be
distinguished by its data base item designation (see Section 2.2.2, Identifying Data Base
Elements).
A data base element consists of one or more sections and expansions which contain terminals.
Each terminal of a DB element represents an interface to outside the DB element which can be
used to connect the DB element or to define a value of a specific kind. One expansion or one
section is expanded at a time to present its terminals in order to define them. The others (if there
are more than one) are compressed. Terminals are indicated by a number, compressed (closed)
sections are indicated by an “S”, followed by the number of the section and an expansion is
indicated by an “E”, followed by the number of the expansion.
When the Advant Controller 400 Series is delivered, its data base is almost empty. Only some
special DB elements exist, the system DB elements, within the data base. After the first start
(see Section 2.9, Starting Advant Controller 400 Series), you must specify the number of I/O
boards and I/O signals, the number of locations for data transfer, etc. Use the DIMDB command
to do this.
You can populate the data base after dimensioning on the basis of how the Advant
Controller 400 Series is equipped and how you want it to operate.
Consider, for example, a 32-signal digital input board. This board is represented in the data base
by one DB element, which contains the board-specific data. Another 32 DB elements exist and
define the signal characteristics. The 32 DB elements for the signals are related to the DB
element for the board and they are subordinated DB elements.
2-2 3BSE 002 417R601

6HFWLRQ *HQHUDO
DI Board DI Board Signals 6LJQDO
DI5.32
Digital Input Board No. 5

Digital Input Board No. 5 Signal 1
DI5.4
DI5.3
DI5.2
DI5
DI5.1
DI board (4.5)
$GGU Digital Input
(8.129)
14 IMPL
15 SERVICE > DI5.1 1 NAME VALUE 12
ERR 17
2 TYPE 1 4 ACT ERR 5
ADDR 3
X1 SCANT 0 7 BLOCKED UPDATED 6
5 ACFILT 0 25 INV
6 FILTA 0 27 TESTED
0 11 ERR_CTRL
7 FILTB
8 FILTC S2 Operator functions
9 FILTD
27 P_CATCH E3 Group Alarm
Figure 2-2. Example of Board DB Elements and Signal DB Elements
Examples of the various categories of data base elements are given below.
• DB elements to describe the I/O boards and signals and to transfer data to/from the
PC programs:
– AI (Analog Input board)
– DI (Digital Input board)
– AO (Analog Output board)
– DO (Digital Output board)
– AIS (Analog Input Signal)
– DIS (Digital Input Signal)
– AOS (Analog Output Signal)
– DOS (Digital Output Signal)
1
– AI8<nn> (Analog Input module; S800)
– AO8<nn> (Analog Output module; S800)
– DI8<nn> (Digital Input module; S800)
– DO8<nn> (Digital Output module; S800)
1. <nn> stands for different S800 I/O series modules, for example AI810, DI811,AO820
3BSE 002 417R601 2-3

• DB elements, with values calculated by a PC program, that have the same characteristics
as, for example, an AIS DB element:
– AIC (Analog input, calculated)
– AOC (Analog output, calculated)
– DIC (Digital input, calculated)
– DOC (Digital output, calculated).
• DB elements to transfer data between PC programs and between nodes:
– DAT(B) (To transfer Boolean data)
– DAT(I) (To transfer integer data)
– DAT(IL) (To transfer long integer data)
– DAT(R) (To transfer data in the form of real numbers)
– Data Set (For communication with another node)
– MVB (MVI data blocks).
• DB elements of Functional Units (having a DB part and a PC part):
– PIDCON (Process controller)
– PIDCONA (Autotuned process controller)
– MANSTN (Manual station)
– RATIOSTN (Ratio station).
• DB elements to configure Advant Fieldbus 100:
– CI520 (AF 100 Fieldbus).
• DB elements representing stations at Advant Fieldbus 100:
– AC110 (Advant Controller 110)
– AC70 (Advant Controller 70)
– AF100S (Advant Station connected to Advant Fieldbus 100)
– CI810 (DB element representing an I/O station at Advant Fieldbus 100).
• DB elements representing Drives connected via CI810:
– DRISTD (Standard Drive)
– DRIENG (Engineered Drive).
For complete descriptions of all types of data base elements, see the Data Base Elements
Advant Controller 400 Series Reference Manual.
2-4 3BSE 002 417R601

6HFWLRQ ,GHQWLI\LQJ'DWD%DVH(OHPHQWV
In formal terms, the DB elements of the data base can be divided into four categories.
• Superior DB elements. These DB elements control their subordinated DB
elements. Example: I/O board DB elements, DI1, AO2...
• Subordinate DB elements. These DB elements are controlled by their superior DB
elements. Example: I/O signal DB elements, DI1.1, AO2.1...
• Independent DB elements. These DB elements are independent of other DB elements.
Example: AIC1, DIC2, PIDCON1...
• System DB elements. They are needed during start up of the Advant
Controller 400 Series. Example: MasterBus 300 DB element.
2.2.2 Identifying Data Base Elements

There are three ways to identify data base elements.
• By name: Most DB elements have a terminal “NAME”. The string that you specify for this
terminal is its name, and this name can be used to identify the DB element (see
Section 2.2.2.1, User-defined Names).
• By data base item designation: The item designation of a DB element contains a textual
part and a numerical part. No general rule for the item designation can be given. It depends
on the element type and can be different compared to the element type.
Example:
Element type: CI520
DB Item designation: AF100_1
• By data base index (not recommended): The data base index (LF.LR) is represented by the
two numbers included in parentheses and separated by a period (see Figure 2-3). The first
number is the logical file (file number in data base) and the second number is the logical
record (record number).
3BSE 002 417R601 2-5

DI Board
DI Board Signals
DI5.32
User-defined Name DB Item Designation DI5.4
DI5.3
DI5.2
DI5
Data Base Index DI5.1/ VENT_OP
DI board (4.5)
Addr: 0110 0100 Digital Input
(8.129)
14 IMPL
15 SERVICE > VENT_OP 1 NAME VALUE 12
ERR 17
2 TYPE 1 4 ACT ERR 5
ADDR 3
X1 SCANT 0 7 BLOCKED UPDATED 6
5 ACFILT 0 25 INV
6 FILTA 0 27 TESTED
0 11 ERR_CTRL
7 FILTB
8 FILTC Operator function
S2
9 FILTD
27 P_CATCH E3 Group Alarm
Figure 2-3. Identification of the Data Base Signal
2.2.2.1 User-defined Names

The default name of a DB element is the DB item designation.
You can change the default name and define own names for (most types of) elements in the data
base. There are a number of rules to be followed when doing this, and compliance with these
rules is checked when you define the name. The rules are as follows:
• Each element in the data base must have an unique name
• Names must not consist only of numerals, or periods, or numerals and periods (dots).
• Names must not start or end with a hyphen
• Names must not be equal to an item designation, for example AI1.1, unless it is its own
item designation
• Substrings of names must not equal ".Bn", ".In", ".ILn", ".Rn", where n is a number,
except for names of DAT elements
• There are also limits on the permitted length of the name, and these vary from one DB
element type to another. Usually the length of a name is limited to 20 characters.
See the Data Base Elements Advant Controller 400 Series Reference Manual.
• Characters according to Table 2-1 are permitted.
2-6 3BSE 002 417R601

6HFWLRQ ,GHQWLI\LQJ'DWD%DVH(OHPHQWV
Table 2-1. Permitted Characters
Printed
Name of Character Remark
Character
Double opening quote "
Hash mark #
Dollar $
Ampersand &
Asterisk *
Plus sign +
Hyphen - Do not use as first or last

character of a name
Dot . Do not combine only numerals

and dots
Zero ... Nine 0 ... 9 Do not combine only numerals

and dots
Question mark ?
At sign @
A ... Z A ... Z
Left square bracket [ USA (1)

Back slash \ USA (1)
Right square bracket ] USA (1)
Caret ^
Underscore _
a ... z a ... z
Left brace { USA (1)

Vertical bar | USA (1)
Right brace } USA (1)
Tilde ~ USA, SWE (1)

Adieresis Ä GER, SWE (1)
Odieresis Ö GER, SWE (1)
Udieresis Ü GER, SWE (1)
Aring Å SWE (1)
adieresis ä GER, SWE (1)
3BSE 002 417R601 2-7

Table 2-1. Permitted Characters (Continued)
Printed
Name of Character Remark
Character
odieresis ö GER, SWE (1)
udieresis ü GER, SWE (1)
aring å SWE (1)
germandbls ß GER (1)

(1) Allowed only, if the specified character set is selected for the project in the Application
Builder (USA=US english, GER=german, or SWE=swedish).
2.3 PC Programs
The ABB MasterPiece Language (AMPL) supports extensive structuring of application
programs. Up to 99 PC programs can be created and structured internally by structure PC
elements. The functional PC elements are subordinated to the structure PC elements and
perform the functions of the application.
Most structure PC elements are allowed to manage and execute that part of the PC program
separately and independently, which is referred to as execution control. Those structure PC
elements are called execution units. The execution units can be given different cycle times and
priorities by defining the call parameters, so that both fast and slow control operations can be
managed by the same PC program.
2.3.1 Execution Control
2.3.1.1 Choosing Cycle Times

A PC program is executed cyclically, PC element by PC element, within the relevant PC
program part. The time from the beginning of one cycle to the next is known as the cycle time
and can be defined individually for each execution unit: PCPGM, CONTRM, MASTER and
SEQ.
For altering the values of the default set of cycle times, see Section 2.3.1.2, Altering the Default
Set of Cycle Times.
Three internal interpreter programs organize the execution. The purpose of these programs is
that each execution unit is processed with the required cycle time.
Associated with the interpreter are a number of cycle timetables that specify which execution
units have a given cycle time. When a cycle time is chosen, an internal reference to the unit is
stored in the corresponding cycle time table. The call parameter “place in cycle time table” in
the PC element means that the reference is stored at a given place in the table. The order
between different execution units with the same cycle time is determined in this way.
2-8 3BSE 002 417R601

6HFWLRQ ([HFXWLRQ&RQWURO
Interpreter
A B C
Place 1
Place 2

Place n
10 20 40 50 100 200 250 500 1000 2000 ms
Figure 2-4. Cycle Time Tables
In systems where there is a big difference between the shortest and the longest possible
execution time, it must be possible to lay down internal priorities to enable short, quick
subprograms to temporarily interrupt long, slow ones. This is why there are three interpreters,
A, B, and C, where A has top priority and the shortest cycle time.
The required number of places in the cycle time tables (scan places) in interpreters A, B and C is
specified when you are dimensioning the space for PC programs (see Section 3.4.1,
Dimensioning the Space for PC Programs).
Table 2-2. Available Cycle Times
Default Cycle Time
Interpreter A Interpreter B Interpreter C
10 ms 50 ms 250 ms
20 ms 100 ms 500 ms
40 ms 200 ms 1000 ms
- - 2000 ms
3BSE 002 417R601 2-9

DIMENSION PC
Free space in system 555 kb
Allocated PC area 100 kb
Available PC area 10 kb
Allocated interpreter area 2 kb
100 kb Size of PC pgm tables (Min. 3 kb)
10 Number of PC programs (Min. 1)
50 Number of scan places in interpreter A

50 Number of scan places in interpreter B
50 Number of scan places in interpreter C
Interpreter cycle times (ms)
A 10 20 40
B 50 100 200
C 250 500 1000 2000
0 kb Size of USER disk application seg area
Figure 2-5. Number of Places in the Cycle Time Tables for Interpreters A, B, and C
2.3.1.2 Altering the Default Set of Cycle Times

You can use the APP command to change the cycle times of the interpreters. This function is
only needed for special purposes.
APP
The command APP (Alter Product Parameter) presents and/or alters miscellaneous cycle (scan)
times in the connected Advant Controller 400 Series.
Use the APP command to change to a suitable cycle time if the default setting is not satisfactory.
Execute the APP command prior to all application programming. The cycle times, however, can
always be displayed.
Syntax:
APP
Subcommands:
M Opens the line at the cursor (>) for modification.
> The cursor moves down one step after you press Enter.
< The cursor moves up one step after you press Enter.
= The cursor does not move after you press Enter.
! Switches from the modify mode to the initial mode.
DIM The requested dimensioning is transferred to the Advant Controller 400 Series
with the subcommand DIM.
PRINT Gives a printout of the screen contents.
2-10 3BSE 002 417R601

6HFWLRQ ([HFXWLRQ&RQWURO
QUIT Leaves the APP command without any alterations.

<Ctrl-Break> Leaves the APP command without any alterations.
END Alters the cycle times and leaves the APP command.
If the cycle times in the connected Advant Controller 400 Series can be altered, the screen
display below is provided. Otherwise, a similar presentation featuring a screen display but no
dialogs is provided. The cycle times of the interpreters A, B, and C are built up by increasing
scan time values without overlap.
Interpreter cycle times

> 10 A 10 20 40 (ms) Default
50 B 50 100 200 (ms) Default
250 C 250 500 1000 2000 (ms) Default
Slow signal scan times
5 D 5 10 30 60 (s) Default
5 10 (minutes)Default
Data set communication scan times
500 DSC 500 (ms) Default
2000 MVI_DSC 2000 (ms) Default
512 DSP 512 (ms) Default
CYCLE_A (5 - 100):
Figure 2-6. Screen Display of the Command APP
Allowed values for interpreter A:

5 ms ≤ scan_A ≤ 50 ms
Allowed values for interpreter B:
4*scan_A (25 ms max.) ≤ scan_B ≤ scan_C/4 (995 ms max.)
Allowed values for interpreter C:
4*scan_B (105 ms max.) ≤ scan_C ≤ 4000 ms
Allowed values for slow signal scan times:
1 s ≤ scan_D ≤ 6 s
Allowed values for DSC:
50 ms ≤ DSC ≤ 1000 s
Allowed values for MVI_DSC:
500 ms ≤ MVI_DSC ≤ 1000 s
Allowed values for DSP:
32, 64, 128, 256, 512, 1024, 2048, 4096ms.
An “A” cycle time is a parameter in the PC element PCPGM. An “A”, “B” or “C” cycle time is
a parameter in the PC element CONTRM. An “A”, “B”, “C” or “D” cycle time is a parameter in
a data base element AIx.y, etc. The DSC cycle time is the basic cycle time for a parameter in the
data base element Data Set. The DSP cycle time is the basic cycle time for a parameter in the
data base element Data Set Peripheral. The MVI_DSC cycle time is the basic cycle time for a
parameter in the data base element MVI Data Set.
3BSE 002 417R601 2-11

On the screen display, there is a cursor to a cycle time group with a valid value range specified at
the bottom of the display. A valid cycle time value must be an integer multiple of 5 ms and must
be unique.
If a cycle time group is not implemented in the connected Advant Controller 400 Series,
the corresponding terminal value is NOT USED.
2.3.1.3 Scanning Process Inputs

All analog and digital process inputs are scanned cyclically by defining a value of SCANT for
the relevant data base element.
For S100 I/O and S800 I/O, as an alternative, you can use interrupt control scanning of digital
input by setting SCANT to INTERRUPT.
You can choose the following values of SCANT:
Table 2-3. Scan Times of various Board Types
Allowed SCANT Values
Signal Type (IN=INTERRUPT, times in milliseconds) (Times in seconds)
IN 10 20 40 50 100 200 250 500 1 2 5 10 30 60 300 600
DI (S100 I/O, • • • • • • • • • • •
S800 I/O) (1) (2)
Pulse inputs • • • • • • • • • •
(S100 I/O) (3)
DI (S400 I/O) (4) • • • • • • • • • •
AI (S100 I/O, S800 I/O), • • • • • • • • • • • • • • • •
except temperature
measurement boards (5)
AI (S100 I/O), • • • • • • • • • • • • • • • •
temperature
measurement boards (6)
AI (S400 I/O) (7) • • • • • • • • • • • •
(1) SCANT determined for each board.
(2) IN = Interrupt; is not possible for DI8* (DI810,...
(3) SCANT determined for each channel.
(4) SCANT determined for each board.
(6) All indicated SCANT values are allowed, but these boards have slower A/I converters than other AI boards. SCANT down to 200 ms
can be used without difficulty in systems with a net frequency of 20-60 Hz and a 12-13 bit resolution requirement.
2-12 3BSE 002 417R601

6HFWLRQ :RUNLQJ0RGHVRI$GYDQW&RQWUROOHU6HULHV
For S800 I/O you can specify how often data will be written to or read from Advant
Fieldbus 100. INSCANT defines the cycle time for reading data from the bus, OUTSCANT for
writing to the bus. For example, INSCANT = 50 ms means that all 50 ms data will be fetched
from the bus by the board. See Table 2-4 for available values.
Table 2-4. Scan Times on Advant Fieldbus 100
$OORZHG9DOXHVRI,16&$17DQG2876&$17
6LJQDO7\SH (IN=INTERRUPT, times in milliseconds)
IN 1 2 4 8 16 32 64 128 256 512 1024 2048 4096
AI8<nn>(1) • • • • • • • • • • • • •
AO8<nn> • • • • • • • • • • • • •
DI8<nn> • • • • • • • • • • • • •
DO8<nn> • • • • • • • • • • • • •
(1) <nn> stands for different S800 I/O series modules, for example AI810, DI811,AO82.
2.4 Working Modes of Advant Controller 400 Series

The Advant Controller 400 Series has four working modes:
• OPERATION mode
• CONFIGURATION mode
• STOPPED mode
• OFFLINE mode.
The LED display on the processor module front indicates the working mode with the codes
P1, P2, P3 and P4.
OPERATION mode (P1):

The controller executes the application program(s). This is the normal status of an Advant
Controller. The system can then perform control tasks and control the process outputs.
CONFIGURATION mode (P2):

The controller does not execute the application program(s). You can configure the controller
system and build the application.
STOPPED mode (P3):

The controller does not execute at all. The process outputs have defined states (zero). The main
CPU performs self-tests to check the controller function.
OFFLINE mode (P4):

The controller executes low-level fault-tracing commands only. Usually performed by ABB
personnel. The process outputs have defined states (zero).
3BSE 002 417R601 2-13

2.5 Ordering Working Modes

You can order operating mode in either of the following ways:
• Use a start mode (see Section 2.6, Start Modes).
• Use On-line Builder commands (see Section 2.8, Relationship between On-line Builder
Commands and Working Modes).
2.6 Start Modes

The processor module has a start mode selector with four positions:
1 = AUTO 2 3
2 = STOP 1 4
3 = CLEAR
4 = OFFLINE
Figure 2-7. Start Mode Selector
AUTO:
Warm start, i.e., the application program is restarted and not changed. This is the normal
position of the selector.
• If the controller was in CONFIGURATION mode, it remains in CONFIGURATION
mode.
• If the controller was in OPERATION mode, it remains in OPERATION mode.
STOP:
Selects the STOPPED mode.
CLEAR:
Cold start, i.e., clears the RAM (the controller system configuration and whole application are
erased). The controller is then in CONFIGURATION mode.
If you want to erase an existing application, the corresponding User Disk Application Segments
of the engineering station must be initialized as well (see Section 2.8.3, Resetting the
Controller).
OFFLINE:
Selects the OFFLINE mode.
The controller reads the start mode selector position at the following occasions:
• When you press the ENTER button on the processor module front
• At power up.
The controller then starts.
2-14 3BSE 002 417R601

6HFWLRQ 5HODWLRQVKLSEHWZHHQ6WDUW0RGHVDQG:RUNLQJ0RGHV
2.7 Relationship between Start Modes and Working Modes

The relationship between start modes and working modes is described as follows:
• First power up (the system has never been configured), see Figure 2-8
• Power up of controller which contains an application, see Figure 2-9.
Start Condition: Uninitialized controller,

e.g., newly delivered controller or controller without memory backup voltage.
Event: Power up
3 (CLEAR) (STOP) 2 2
Start Mode Selector: 2 3 2 3 3
(AUTO) 1 4 1 4 1 4 1 4 (OFFLINE)
(Compulsory
setting)
Actions executed -Install system

by the Controller SW
-Clear applic.
area
Resulting
Working Mode OPERATION CONFIG. STOPPED OFFLINE
mode (P1) mode (P2) mode (P3) mode (P4)
Figure 2-8. First Power Up
3BSE 002 417R601 2-15

Start Condition: Controller containing an application,

in OPERATION mode or CONFIGURATION mode.
Power fail and subsequent power up

Event: User presses ENTER button
(STOP)
Start Mode Selector: 2 2 3 (CLEAR) 2 2
3 3 3
(AUTO) 1 4 1 4 1 4 1 4 (OFFLINE)
Start cond.:
OPERATION CONFIG. mode
mode
Actions executed -Initialize and -Install system

by the Controller start applic. SW
-Erase applic.
Resulting
mode (P1) mode (P3) mode (P4)
mode (P2)
Figure 2-9. Power Up of Controller which contains an Application
2-16 3BSE 002 417R601

6HFWLRQ 5HODWLRQVKLSEHWZHHQ2QOLQH%XLOGHU&RPPDQGVDQG:RUNLQJ0RGHV
2.8 Relationship between On-line Builder Commands and Working Modes
2.8.1 Enable CONFIGURATION Mode
ECONFIG
Use the ECONFIG command (Enable CONFIGuration) when you want to change to the
CONFIGURATION mode.
Syntax:
ECONFIG
You are asked whether you want to exit OPERATION mode. The LED display on the processor
module front shows “P2” to indicate the CONFIGURATION mode.
Start Condition: Controller executing in

OPERATION mode
User enters command

Event : ECONFIG
(Compulsory (STOP)
setting) 2
Start Mode Selector: 2 2 3 (CLEAR) 2
3 3 3
(AUTO) 1 4 1 4 1 4 1 4 (OFFLINE)
Actions executed
by the Controller Stop
application
Resulting
Figure 2-10. CONFIGURATION Mode resulting from the ECONFIG Command
3BSE 002 417R601 2-17

2.8.2 Disable CONFIGURATION Mode
DICONFIG
Use the DICONFIG command (DIsable CONFIGuration) when you want to change to the
OPERATION mode.
Syntax:
DICONFIG
You are asked whether the controlled process is to be put into OPERATION mode. The LED
display on the processor module front shows “P1” to indicate the OPERATION mode.

CONFIGURATION mode
User enters command

Event : DICONFIG
(Compulsory
Start mode selector: setting) (STOP) 2
2 3 2 3 (CLEAR) 3 2 3
(AUTO) 1 4 1 1 4 1 4 (OFFLINE)
4
Actions executed Initialize and

by the Controller start
application
Resulting
Figure 2-11. OPERATION Mode resulting from the DICONFIG Command
2-18 3BSE 002 417R601

6HFWLRQ 5HVHWWLQJWKH&RQWUROOHU
2.8.3 Resetting the Controller
RECONFIG
The RECONFIG (RECONFIGuration) command performs a cold start of the system and
requires the CONFIGURATION mode.
Syntax:
RECONFIG
You are asked whether all PC programs and the data base are to be removed. The RECONFIG
command deletes all application programs in the connected Advant Controller 400 Series.
The RECONFIG command, however, does not delete the corresponding data of the User Disk
Application Segments. To delete the corresponding data of the User Disk Application Segments,
change to SYSTEM level using the SLLEV SYST command. Delete the files *.SM, *.AP, *.UI,
if present, to avoid mismatching of the User Disk Application Segments with the target system.
The result of this procedure is an initial USER volume. Perform a SLLEV PC command
directly afterwards. For more information about the User Disk Application Segments, see
Section 7.2.2, USER Volume.

CONFIGURATION mode
User enters command

Event: RECONFIG
(Compulsory
Start mode selector: setting) 3 (CLEAR) (STOP) 2
2 2 3
2 3 3
(AUTO) 1 1 4 4 1 4 (OFFLINE)
4 1
Actions executed -Install

by the Controller system SW
-Erase
application
Resulting
Figure 2-12. Cold Start resulting from the RECONFIG Command
3BSE 002 417R601 2-19

2.9 Starting Advant Controller 400 Series

You can start the Advant Controller 400 Series in four different start modes, depending on the
position of the start mode selector (see Section 2.6, Start Modes). The operation of the system
can also be software-controlled at start-up, so that you can determine how the process control
system is to start (see Section 2.9.1, Programmed Start).
Use the ENTER button on the processor module front to manually start and restart the system.
At start, the system starts in the mode selected with the start mode selector.
WARNING
Risk of operational malfunctions.
At power on, the system is automatically initialized (start mode: AUTO). If the
system is powered on in the start mode CLEAR, the RAM is reset. PC programs
and the data base must then be reloaded.
First Start of the Controller:

1. Set the start mode selector to the start mode CLEAR.
2. Switch on the power. Wait until the processor module display indicates the
CONFIGURATION mode (P2).
3. Set the start mode selector to the start mode AUTO, thereby assuring that a power fail will
not erase the application (AUTO is the normal position of the start mode selector).
4. Connect the engineering station to the Advant Controller 400 Series, switch on the power
and start the On-line Builder.
5. Build your application.
6. Use the On-line Builder command DICONFIG to order the controller to the
OPERATION mode (the process control application is running).
Further Starts of the Controller:

1. If you need to do further configuration work, use the On-line Builder command
ECONFIG to order the controller to the CONFIGURATION mode.
2. Change your application.
3. Use the On-line Builder command DICONFIG to order the controller to the
OPERATION mode.
2-20 3BSE 002 417R601

6HFWLRQ 3URJUDPPHG6WDUW
2.9.1 Programmed Start

In the Advant Controller 400 Series, you can determine how the process control starts up.
You define this using the data base element START and with a PC program for programmed
start-up. A specified control module, called “start module,” is executed (see Section 2.9.1.1,
Start Module).
You can also use the START data base element to specify how the system is to restart after a
power failure (CLEAR, STOP, AUTO or RESTART). See Section 2.9.1.2, Programmed Restart
after Power Failure.
Data Base Element PC Program for Programmed Start Control program of

the process
Values of the terminals of the data base PC2

element define PC programs and start modules
PCPGM
ST1/START .1
Blocking of alarms
START (192.1) CONTRM
START NAME
Control of ON
2 PC_PGM Start module inputs
0 CLEAR_C for AUTO start
1 AUTO_C
2 RESTA_C
Control of restart
.2
after power failure
CONTRM
Blocking of alarm
Start module for

Control of ON
programmed inputs
restart after
power failure
Figure 2-13. Start Module
In the start module, you can block the alarms that the system may generate when the I/O boards
are initialized. You can also determine how the process is to start by controlling the ON inputs
on execution units of the following types: PCPGM, CONTRM, MASTER and SEQ in the PC
program(s) that control(s) the process. You can also define a special start module for restart after
power failure. Data (date and time) of the power failure are available at the outputs of the data
base element.
3BSE 002 417R601 2-21

2.9.1.1 Start Module

A start module is a control module whose item designation (see AMPL Application Building
Reference Manual) has been specified in the data base element START. The item designation
must be on the level directly below the level of the PC program header. You can create the start
module after you create the data base element.
A start module is executed only when the system starts. If the module is in BUILD mode at
start-up, it is regarded as undefined.
It is not permissible to read or write data from or to VALUE terminals on the data base elements
on the I/O boards. (The module is executed before the modules are initialized.)
Input terminals and call parameters on the PC program header (PCPGM) and control module
header (CONTRM) for a start module are without meaning.
2.9.1.2 Programmed Restart after Power Failure

For programmed restart after power failure, always set the start mode selector to AUTO. When
the power returns, the Advant Controller 400 Series starts according to the three restart options,
depending on how long the power has been down. Each one of the start modes (CLEAR, STOP,
AUTO or RESTART) can be specified as a restart option. If the selector is not set to AUTO, the
system starts in the mode indicated by the selector.
2-22 3BSE 002 417R601

PC Program for Programmed Restart

PC2
PCPGM
.1
Data Base Elements
ST1/START CONTRM
Definition of start modules
(CLEAR_C is not relevant for AC 400) START (192.1)
Start module for
START NAME programmed
2 PC_PGM restart after
0 CLEAR_C power failure
Time limits for 0 AUTO_C
restart option 1 RESTA_C
time SHORT_T
time MP_SP_T
LONG_T
Restart option start mode SHT_T_ST CON_SP_T Power failure data
start mode MED_T_ST SP_TIME Outputs can be connected
after power fail start mode SP_DATE to PC
LNG_T_ST
Value of restart option SHT_T_ST: Value of restart option MED_T_ST: Value of restart option LNG_T_ST:
- AUTO, - AUTO, - AUTO,
&/($5 - CLEAR, - CLEAR,
- STOP or - STOP or - STOP or
- RESTART - RESTART - RESTART time
Power down time < SHORT_T SHORT_T < Power down time < LONG_T Power down time > LONG_T
6+257B7 /21*B7
Figure 2-14. Programmed Restart after Power Failure (example)
If you select restart using the RESTART mode, the start module specified is executed with the
value at the terminal RESTA_C in the data base element.
3BSE 002 417R601 2-23

You can start from the following start modes for the three restart options.
WARNING
Loss of RAM contents. The RAM is reset in the CLEAR start mode. PC program
and data base must be reloaded.
AUTO Corresponds to manual start with the start mode selector on the processor unit
set to AUTO (warm start in OPERATION or CONFIGURATION mode).
STOP Corresponds to manual start with the start mode selector on the processor unit
set to STOP. The controller stops after initializing.
CLEAR Corresponds to manual start with the start mode selector on the processor unit
set to CLEAR.
RESTART Is performed as follows:
1. Execution of PC elements that were being executed when the power went down is
completed. The values produced are output internally in PC, but not in the data base.
2. That start module specified by data base element terminal RESTA_C is executed (if
present).
3. Execution of the PC programs begins with the values and internal states that existed when
the power went down.
4. Other parts of the Advant Controller 400 Series, e.g., communication, MasterView 320,
etc., start as in the AUTO mode.
After power failure, data about the power failure are available to any PC program at the
following terminals on the START data base element:
MP_SP_T Controller (MasterPiece) StoP Time indicates the length of time (in seconds)
the power has been down.
CON_SP_T CONtrol StoP Time indicates the length of time (in seconds) the process has
been without control. This time is longer than MP_SP_T.
SP_TIME StoP TIME indicates the time on the clock when the power went down.
SP_DATE StoP DATE indicates the date when the power went down.
2-24 3BSE 002 417R601

2.9.1.3 Example
In the example in Figure 2-15, control module PC2.1 is specified as the start module.
The MOVE PC element PC2.1.1 is connected via a DAT DB element to the ON inputs on PC
program header PC1 and the control module headers PC3.1 and PC3.2. The MOVE PC element
PC2.1.2 is used to block event printouts in the Advant Station 500 Series Operator Station.
Blocked modules must be reset when the start-up is complete.
Data Base Elements

PC2
ST1/START
PCPGM (C1, C2)
START (192.1)
START NAME 1 ON
2 PC_PGM 2 R RUN
0 CLEAR_C
1 AUTO_C
Values of inputs and call
0 RESTA_C PC2.1 parameters for these
elements are not
SHORT_T CONTRM significant.
MP_SP_T
LONG_T (C1, C2)
SHT_T_ST CON_SP_T
MED_T_ST SP_TIME 1 ON RUN Outputs of this element
LNG_T_ST SP_DATE 2 > SINGLE MODP must not be used.
3 R
.1
MOVE
(B, 3)
D=0 1 21 DAT2:VALUE PC1

NOTE: The blockings that D=0 2 22 DAT2:VALUE2
are made must be PC3.1
D=1 3 23 DAT2:VALUE3
reset when the start- PC3.2
up is complete
.2
MOVE
(B, 4)
D=1 1 21 DI1.2:AL_P_BLK
D=1 2 22 AI1.3:AL_P_BLK
D=1 3 23 AI1.4:AL_P_BLK
D=1 4 24 DIC33:AL_P_BLK
Figure 2-15. Example for Programmed Start
3BSE 002 417R601 2-25

2.9.2 Overview of Programmed Start

The following illustrations provide you with an overview when you are using the programmed
start function:
• Figure 2-16 is an overview of programmed restart at power fail - power up.
• Figure 2-17 describes programmed start at AUTO - ENTER (when you press the ENTER
button while the start mode selector on the processor module front is in the position
AUTO).
• Figure 2-18 describes programmed start when you use the DICONFIG command.
Starting-point: Controller containing an application and executing in working mode

OPERATION or CONFIGURATION
Power-fail - Power-up
Event : (Recommended
Start mode selector: setting)
(STOP) 2
2 3 2 3 (CLEAR) 3 2 3
(AUTO) 1 4 1 1 4 1 4 (OFFLINE)
4
Starting
point: CON S
OP
C
Actions executed -Install
by the controller Programmed start system SW
-Erase
Initialize and application
start application
R A
Resulting
working mode OPERATION CONFIG. STOPPED OFFLINE
P1 P2 -3 -4
R Programmed start, option RESTART
A AUTO
C
CLEAR
S
STOP
Figure 2-16. Programmed Restart at Power Fail
2-26 3BSE 002 417R601

6HFWLRQ 2YHUYLHZRI3URJUDPPHG6WDUW
Starting-point: Controller executing in working mode

OPERATION
User presses ENTER button

Event :
(Recommended
2 3 2 3 (CLEAR) (STOP) 2 3 2 3
(AUTO) 1 4 1 1 4 1 4 (OFFLINE)
4
Actions executed Programmed start -Install

by the controller system SW
-Erase
Initialize and start application
application
A
Resulting
P1 P2 -3 -4
A Programmed start, option AUTO
Figure 2-17. Programmed Start at AUTO - ENTER
3BSE 002 417R601 2-27

Starting-point: Controller executing in working mode

CONFIGURATION
User enters engineering station

Event : command DICONFIG
(Compulsory
2 3 (CLEAR) (STOP) 2 2 3
2 3 3
(AUTO) 1 4 1 4 4 1 4 (OFFLINE)
1
Actions executed Programmed start

by the controller
Initialize and start

application
A
Resulting
P1 P2 -3 -4
A Programmed start, option AUTO
Figure 2-18. Programmed Start at DICONFIG
2-28 3BSE 002 417R601

6HFWLRQ $SSOLFDWLRQ%XLOGLQJ
Chapter 3 Application Building
3.1 Application Building

The application is made up of the data base and several PC programs. Follow these
recommended main steps when configuring an Advant Controller 400 Series:
1. Introduce a new target system on the engineering station (target system setup).
2. Start up an AC 400 session using the start-up menu.
3. Activate those MasterBus 300, RCOM, GCOM, and Modbus that are to be included in the
system.
4. Dimension the data base.
5. Populate the data base.
6. Dimension the PC.
7. Build up the PC programs.
8. Take a backup of the entire system.
Data base elements are described in the Data Base Elements Advant Controller 400 Series
Reference Manual. PC elements are described in the PC Elements Advant Controller 400 Series
Reference Manual. PC programming aspects are described in the AMPL Application Building
Reference Manual.
3.2 Data Base Handling
3.2.1 Dimensioning the Data Base

When the Advant Controller 400 Series is delivered, the data base is almost empty and most of
its files are not dimensioned. When you dimension the data base, you define the size necessary
to accommodate the DB elements that will be created when you populate the data base.
Dimensioning defines the number of process I/O boards, process signals, objects, etc.
NOTE
Note that all communication ports for MasterBus 300, as well as those for
RCOM, GCOM, and Modbus, which are supposed to be included in the system,
must be started before you dimension the data base.
DIMDB
Dimension the data base using the command DIMDB (DIMension Data Base). The picture on
thescreenshowsthevariouspartsofthedatabase(S1-S7)thataretobedimensioned.During
dimensioning, the Advant Controller 400 Series must be in
CONFIGURATION mode (see Section 2.4, Working Modes of Advant
3BSE 002 417R601 3-1

&KDSWHU $SSOLFDWLRQ%XLOGLQJ
Controller 400 Series). The figures in this book are showing the DIMDB
dialog for AC450 with system software QC07 version 3.0. For target systems
with other system software, the dialog may look different.
Syntax:
',0'%
DIMENSION DATA BASE

Allocated data base 133 kb
Spare area in data base 1 kb
> S1 PROCESS I/O
S2 DATA TRANSFER & COMMUNICATION
S3 MASTERVIEW 300
S4 DATA TABLES & TREND DATA
S5 FUNCTIONAL UNITS & GROUP ALARM
S6 DRIVES
S7 FIRE AND GAS
Figure 3-1. DIMDB, Initial Mode
3.2.1.1 Dialog Handling

When you use the DIMDB command, the screen is divided into two sections (split screen). The
upper part of the screen shows the dimensioning details that you can change. In the lower part of
the screen (four lines), you conduct a dialog with the engineering station. The “?” prompt in the
lower part of the screen shows that the PC program is ready to receive a subcommand. The
cursor “>” indicates which part of the data base is currently at work. You can control how the
cursor moves.
Subcommands:
S The part of the data base currently indicated by the cursor “>” can be
expanded with the subcommand S.
Sx Use the subcommands S1-S7 to choose the part of the data base to expand.
Only one part of the display can be expanded at a time. When another part of
the display is expanded, the previously expanded part contracts.
S0 Starts the dimensioning display in initial mode with all parts of the display
contracted (Figure 3-1). To change the dimensioning details displayed, you
must switch from the initial mode (the mode reached after reaching the initial
command DIMDB) to the modify mode.
3-2 3BSE 002 417R601

6HFWLRQ 'LPHQVLRQLQJWKH'DWD%DVH
There are two subcommands that open a dimensioning detail for modification:
M Opens the line at the cursor “>” for modification.
Mx Moves the cursor to the dimensioning detail with number x in the
dimensioning display and opens the detail for modification.
MWx Moves the Window, whereas -99≤ x ≤99.
DIMENSION DATA BASE

> 0 ——————— L181 ——— Number of MFB UNITS
0 ——————— L286 ——— Number of REDUNDANT/OBJECT_BOARDS
5 ——————— L325AI —— Number of S800 AI MODULES
6 ——————— L325AO—— Number of S800 AO MODULES
3 ——————— L325DI —— Number of S800 DI MODULES
4 ——————— L325DO—— Number of S800 DO MODULES
1 ——————— L325DP—— Number of S800 DP MODULES
0 ——————— L2 ———— Number of AI_BOARDS
0 ——————— L3 ———— Number of AO_BOARDS
0 ——————— L4 ———— Number of DI_BOARDS
0 ——————— L5 ———— Number of DO_BOARDS
200 ——————— L6 ———— Number of AI_SIGNALS
200 ——————— L7 ———— Number of AO_SIGNALS
200 ——————— L8 ———— Number of DI_SIGNALS
200 ——————— L9 ———— Number of DO_SIGNALS
————————————— S2 ———— DATA TRANSFER & COMMUNICATION
————————————— S3 ———— MASTERVIEW 300
————————————— S4 ———— DATA TABLES & TREND DATA
————————————— S5 ———— FUNCTIONAL UNITS & TREND DATA
————————————— S6 ———— DRIVES
————————————— S7 ———— FIRE AND GAS
------------------------------------------------------------------------
?M
Number of MFB UNITS: 0 New value:
Figure 3-2. DIMDB, Modify Mode
When the Advant Controller 400 Series is in modify mode, the name and current value of the
dimensioning detail appear on the bottom line of the display.
<Enter> You can enter a new value directly or leave the existing value unchanged.
Every time you press the Enter key, the cursor moves through the
dimensioning details one step at a time in the chosen direction (< or >). If the
dimensioning detail is incorrect, the system puts up an error message at the
bottom of the screen and asks for a new value.
3BSE 002 417R601 3-3

! Switches from modify mode to initial mode.

* An asterisk (*) to the left of the dimensioning detail shows that the value
displayed temporarily differs from the value in the data base of the control
system.
3.2.1.2 Dimensioning Parts of the Data Base

Subcommands:
S1 Use the subcommand S1 to dimension the process I/O part of the data base
(S100 I/O and S400 I/O). The specified number of signals of each type must
be equal to or greater than the sum of the number of available signals on the
boards/units in use. Even if not all signals on a S100 I/O board or S400 I/O
unit are being used, they must be counted when you dimension the data base.
DIMENSION DATA BASE

> 0 ——————— L181 ——— Number of MFB UNITS
0 ——————— L286 ——— Number of REDUNDANT/OBJECT_BOARDS
5 ——————— L325AI —— Number of S800 AI MODULES
6 ——————— L325AO—— Number of S800 AO MODULES
3 ——————— L325DI —— Number of S800 DI MODULES
4 ——————— L325DO—— Number of S800 DO MODULES
2 ——————— L325DP—— Number of S800 DP MODULES
0 ——————— L2 ———— Number of AI_BOARDS
0 ——————— L3 ———— Number of AO_BOARDS
0 ——————— L4 ———— Number of DI_BOARDS
0 ——————— L5 ———— Number of DO_BOARDS
200 ——————— L6 ———— Number of AI_SIGNALS
200 ——————— L7 ———— Number of AO_SIGNALS
200 ——————— L8 ———— Number of DI_SIGNALS
200 ——————— L9 ———— Number of DO_SIGNALS
————————————— S2 ———— DATA TRANSFER & COMMUNICATION
————————————— S3 ———— MASTERVIEW 300
————————————— S6 ———— DRIVES
————————————— S7 ———— FIRE AND GAS
Figure 3-3. Dimensioning Process I/O
3-4 3BSE 002 417R601

S2 Use the subcommand S2 to dimension the data base for the number of DAT
and DS DB elements. This dimensioning offers the possibility of network
communication and/or data transfer between PC programs.
DIMENSION DATA BASE

————————————— S1 ———— PROCESS I/O
0 ——————— L110 ———— Number of DAT
0 ——————— L109 ———— Number of DS
0 ——————— L298 ———— Number of MS
0 ——————— L297 ———— Number of TEXT
3 ——————— L296 ———— Number of TS
4 ——————— L335 ———— Number of DSP
0 ——————— L351 ———— Number of EVENT SETS
0 ——————— L344 ———— Number of MVI MODULES
0 ——————— L356 ———— Number of MVI CHANNELS
0 ——————— L357 ———— Number of MVI NODES
0 ——————— L358 ———— Number of MVI BLOCKS
0 ——————— L333 ———— Number of AF 100 FIELDBUSES
0 ——————— L334 ———— Number of AF 100 STATIONS
0 ——————— L333PB——— Number of PROFIBUS FIELDBUSSES
0 ——————— L334PB——— Number of PROFIBUS SLAVES
0 ——————— L361 ———— Number of PBS DESCRIPTIONS
————————————— S3 ———— MASTERVIEW 300
————————————— S6 ———— DRIVES
————————————— S7 ———— FIRE AND GAS
Figure 3-4. Dimensioning Data Transfer and Communication
3BSE 002 417R601 3-5

S3 Use the subcommand S3 to dimension the MasterView 300 part of the data
base.
DIMENSION DATA BASE

————————————— S1 ———— PROCESS I/O
————————————— S2 ———— DATA TRANSFER AND COMMUNICATION
0 ——————— L147 ———— Number of DISPLAYS
0 ——————— L148 ———— Number of VARIABLES
————————————— S6 ———— DRIVES
————————————— S7 ———— FIRE AND GAS
Figure 3-5. Dimensioning MasterView 300
S4 Use the subcommand S4 to dimension the data tables and the trend data part
of the data base. The dimensioning of trend data is described in detail in the
AdvaCommand Basic Functions User’s Guide.
DIMENSION DATA BASE

————————————— S1 ———— PROCESS I/O
————————————— S3 ———— MASTERVIEW 300
0 ——————— L80 ———— Number of TTD_LOGS
0 ——————— L193 ———— Number of TTD_VARIABLES
0 ——————— L299 ———— Number of TBL_CLASSES
0 ——————— L301 ———— Number of TABLES
0 ——————— L300 ———— Number of TBL_PARAMETERS
0 ——————— L302 ———— Size of DATA TABLES (kB)
0 ——————— L323 ———— Number of FILE ELEMENTS
0 ——————— L324 ———— Size of FILE DATA (kB)
————————————— S6 ———— DRIVES
————————————— S7 ———— FIRE AND GAS
Figure 3-6. Dimensioning Table Handling and Trend Data Functions
3-6 3BSE 002 417R601

S5 Dimension the function units and group alarm part of the data base using the
subcommand S5.
DIMENSION DATA BASE

————————————— S1 ———— PROCESS I/O
————————————— S3 ———— MASTERVIEW 300
0 ——————— L52 ———— Number of SEQ_CTRL
0 ——————— L117 ———— Number of GENOBJ
0 ——————— L217 ———— Number of MMCX
0 ——————— L62 ———— Number of PIDCON
0 ——————— L342 ———— Number of PIDCONA
0 ——————— L77 ———— Number of MANSTN
0 ——————— L78 ———— Number of RATIOSTN
0 ——————— L111 ———— Number of GRPALARM
0 ——————— L112 ———— Number of GRPMEMB
————————————— S6 ———— DRIVES
————————————— S7 ———— FIRE AND GAS
Figure 3-7. Dimensioning Function Units and Group Alarm
S6 Dimensioning DB elements for Drives.
DIMENSION DATA BASE

————————————— S1 ———— PROCESS I/O
————————————— S3 ———— MASTERVIEW 300
————————————— S5 ———— FUNCTIONAL UNITS & GROUP ALARM
0 ——————— L325DRS ———— Number of DRISTD
0 ——————— L325DRE ———— Number of DRIENG
————————————— S7 ———— FIRE AND GAS
Figure 3-8. Dimensioning Drives DB Elements
3BSE 002 417R601 3-7

S7 Dimensioning DB elements for fire and gas applications (for more

information about the DB elements, see ABB Master Safeguard
documentation, supplied by ABB Industri AS, Norway).
DIMENSION DATA BASE

————————————— S1 ———— PROCESS I/O
————————————— S3 ———— MASTERVIEW 300
————————————— S5 ———— FUNCTIONAL UNITS & GROUP ALARM
————————————— S6 ———— DRIVES
0 ——————— L305 ———— Number of GI_BOARDS
0 ——————— L306 ———— Number of FI_BOARDS
0 ——————— L307 ———— Number of GI_SIGNALS
0 ——————— L308 ———— Number of FI_SIGNALS
Figure 3-9. Dimensioning Fire and Gas DB Elements
3.2.1.3 Memory Space

At the top of the display, the amount of free RAM (Figure 3-10), the total data base size (2) and
the reserved spare area in the data base (3) are shown. This information is given in kilobytes.
DIMENSION DATA BASE

2 Allocated data base 133 kb
Figure 3-10. Memory Space
3-8 3BSE 002 417R601

The amount of memory space that has been used is updated and shown in the dimensioning
display.
Before quitting dimensioning mode, you can create a spare area in the data base. You can use
the spare area as a simple way of increasing the number of places in any of the parts of the data
base.
You can use DIMDB to increase the number of places directly if spare area is available. Without
sufficient spare area, a dumping/loading procedure for redimensioning is necessary (see
Section 7.4, Dumping and Loading for Redimensioning). You must first dump the data base
contents with the DUTDB command (see Section 7.4, Dumping and Loading for
Redimensioning), after which the size of the data base must be increased and the contents
loaded back with LOTDB (see Section 7.4.3, Loading the Data Base).
For all dimensioning of the data base, the Advant Controller 400 Series must be in
CONFIGURATION mode (see Section 2.8.1, Enable CONFIGURATION Mode).
Having a generous amount of spare area saves time, especially during the application-building
phase, when the data base is being populated but PC has not yet been dimensioned. When
populating of the data base is complete and the data base has been dumped, the spare area can
finally be reduced when the data base is reloaded. (LOTDB removes all of the data base’s spare
area unless new spare area is expressly requested during dimensioning.)
NOTE
Redimensioning using spare area is only permissible before the PC part has been
dimensioned.
In addition to the data base and PC, there are certain functions in the Advant Controller 400
Series that must have access to RAM (see Section 3.2.1.4, Memory Requirements for certain
Functions). Sufficient memory space must be left for those functions.
3.2.1.4 Memory Requirements for certain Functions

All functions in the Advant Controller 400 Series require RAM. Most functions reserve this
memory at system start-up (i.e., when the system goes into CONFIGURATION mode after
starting via CLEAR on the start mode selector or the RECONFIG command) or upon
dimensioning space for the data base and the PC programs. There are, however, a number of
functions that reserve parts of their RAM upon exiting from CONFIGURATION mode (if the
function was selected with the system in CONFIGURATION mode) or, alternatively, when the
function is selected (when the Advant Controller 400 Series is in OPERATION mode).
You must take this late memory reservation into account when using DIMDB (see
Section 3.2.1.3, Memory Space) and DIMPC (see Section 3.4.1, Dimensioning the Space for
PC Programs)—sufficient memory space must remain for those functions. Exceptions to this are
the communication functions (e.g., MasterBus 300). They allocate their memory if they are
included in the system before the data base is dimensioned.
Table 3-1 and Table 3-2 show the extra memory space that must be reserved for these functions.
You can see the actual memory consumption when using DIMDB even in operation mode. In
this mode you cannot modify the dimensioning, but you can inspect the actual values. This may
work as an alternative to calculating the extra memory space needed.
3BSE 002 417R601 3-9

Table 3-1. Extra Memory Requirements
Function Memory Requirement in Bytes

MasterBus 300 or (1)
MasterBus 300E
•Advant Controller 450, 10 000 • (number of SC520)
implementation with
SC520 and CS513
•Advant Controller 450, 4 000 • (number of CS513)
implementation with
SC510 and CS513
•Advant Controller 410
4 000 • (number of CS513)
MasterView 320 86 • (1 + number of events in event list) (2)
Data Set (DS) 148 • (number of DS)
Data Set Peripheral (DSP) 36 • (number of DSP)
MVI Data Set (MS) 148 • (number of MS) (3)
Text Data Set (TS) 96 • (number of TS)
MVI ports 122 • (number of configured MVI ports) (4)
Time-tagged data (TTD) 6000 + N1 (4P1 + 20) +
N2 (4P2 + 20) +
•
•
Nx (4Px + 20)
Nx =number of variables for log number x

Px = number of values that can be stored per variable in
log number x (x ≤ 15)
Symbolic names 6 • number of Symbolic names
Symbolic names for objects in the Advant Controller selectable

from the Operator Station
(1) MasterBus 300E allocates this memory at first start-up (CLEAR-INIT or RECONFIG) or later when SC520 or CS513 is
inserted.
(2) If there are several event lists, sum up the numbers of events in all event lists.
(3) Only when submodules CI532Vxx are used.
(4) Only when submodules CI534Vxx are used (two ports (channels) per submodule).
3-10 3BSE 002 417R601

Table 3-2. Extra Memory Requirements if Operator Functions are used
Function Memory Requirement in Bytes

Functional Units 12.2 (A1 + A2 + .. + A6) + 12.4 (A7 + A8) +14 (A9 + A10 + .. + A14) +
7160(A15) + 12 • (number of different functional units)
A1 ... A15 is the number of functional units that have been dimensioned
A1 = No of AI
A2 = AO
A3 = DI
A4 = DO
A5 = TEXT
A6 = GRPALARM
A7 = DAT
A8 = GENBIN + GENCON + GENUSD
A9 = SEQ
A10 = PIDCON
A11 = MANSTN
A12 = RATIOSTN
A13 = MOTCON + VALVECON
A14 = MMCX (number of data base elements that the user
is creating)
A15 = PIDCONA
3.2.1.5 Transferring the Dimensioning Data to the Advant Controller 400 Series
Subcommand:
DIM When dimensioning is complete, transfer the information to the data base of
the Advant Controller 400 Series using the DIM subcommand.
Example:
? ',0
Specify wanted spare area size
SPARE AREA = 0 KB =
If the Advant Controller 400 Series has not been dimensioned before, there is no memory area
reserved for the data base. Before a memory area is reserved, the system asks how much spare
area is required. You can use this spare area to redimension the data base, provided it is done
before PC is dimensioned.
3BSE 002 417R601 3-11

3.2.1.6 Quitting DIMDB

You can stop dimensioning with either of the subcommands END or QUIT (Q). You can also
press Ctrl-Break to end it.
END and QUIT produce the same result, except when redimensioning LOTDB (see
Section 7.4.3, Loading the Data Base).
Subcommands:
END Terminate dimensioning with the subcommand END. Where redimensioning
using LOTDB is in progress, loading is performed as if no redimensioning
had been requested.
QUIT or Q Terminate dimensioning with the QUIT subcommand. Where redimensioning
using LOTDB is in progress, LOTDB is also ended.
<Ctrl-Break> If an activity is in progress, the system asks you for confirmation. If you
confirm, the activity is ended.
3.2.2 Editing the Data Base

There are three commands for editing the data base in an Advant Controller 400 Series:
• CRDB (CReate Data Base).
• MDB (Modify Data Base). For modification of the values of one or more terminals in
existing DB elements.
• DDB (Delete Data Base).
You can use CRDB in CONFIGURATION mode and in OPERATION mode. The Advant
Controller 400 Series, however, must be taken out of OPERATION mode if certain types of
created DB elements are to be made active.
You can use MDB in CONFIGURATION mode and in OPERATION mode, but not all
characteristics can be modified in OPERATION mode.
You can use DDB only in CONFIGURATION mode.
3.2.2.1 Creating Data Base Elements

Since the data base of the Advant Controller 400 Series is almost empty on delivery, it must be
populated by the user. During populating of the data base, the DB elements are displayed on the
screen of the engineering station with default values.
The default values are chosen by the system in such a way that, normally, you can use them
without adjustment.
CRDB
You can create elements in the data base with the CRDB (CReate Data Base) command.
Syntax:
&5'%
&5'% element-type
3-12 3BSE 002 417R601

6HFWLRQ (GLWLQJWKH'DWD%DVH
This command enables you to add:

• One DB element
• A number of DB elements that are related to each other, e.g., one I/O board DB element
and its signal DB elements.
The DB element for the specified DB element type appears on the screen.
Data Base Index

Item Designation (logical file, logical record)
DI1 Address to be
DI board (4.1) Strapped on Board
Addr: 0110 0100
Default Values <1 14 IMPL
1 15 SERVICE 17 0
DSDI 110 2 ERR
TYPE ADDR
INTERRUPT X1 SCANT 3 96
0 5 ACFILT
10 6 FILTA
10 7 FILTB
10 8 FILTC
To go to next 10 9 FILTD
Element, use NO 27 P_CATCH
the directive >>
? >>
Figure 3-11. Example of a Created DB Element: DI
The DB element that is created is placed at the first free space in the corresponding file.
When a superior DB element type (e.g., board DB element) is created, a number of subordinate
DB elements (signal DB elements) of the corresponding type are also created.
The cursor “>” appears in line with the terminal being processed. You can control the movement
of the cursor:
If you wish to change the board type proposed by the system, the change must
be made before the subordinate signal DB elements are created. Board type
cannot be changed after the signals have been created.
>> Moves to the next DB element.
E Expands a subordinated data base element having an E.
En Calls input terminal, e.g., E7. The parameter “n” is the terminal number.
MWx Moves Window, whereas -99≤ x ≤99.
3BSE 002 417R601 3-13

Example:
This diagram shows how all subordinated DB elements of the superior DB element DI1 are
created. The number of subordinate DB elements, in this case DI signals, is automatically
determined by the number of signals of the board type chosen:
&5'%',
DI1
DI board (4.1)
Addr: 0110 0000
<1 14 IMPL
1 15 SERVICE ERR 17 0
DSDI_110 2 TYPE ADDR 3 0
INTERRUPT X1 SCANT
0 5 ACFILT
10 6 FILTA
10 7 FILTB
10 8 FILTC
10 9 FILTD
NO 27 P CATCH
? >> Proceed to next element
Figure 3-12. Parameters of the First DI Board
Item designation Signal file

record
DI1.1
Digital Input
(8.1)
>DI1.1 1 NAME VALUE 12 0
1 4 ACT ERR 5 0
0 7 BLOCKED UPDATED 6 0
0 25 INV
0 27 TESTED
0 11 ERR CTRL
S2 Operator functions
E3 Group Alarm
? >> Proceed to next element
Figure 3-13. Parameters of the First Signal
3-14 3BSE 002 417R601

6HFWLRQ (GLWLQJWKH'DWD%DVH
DI1.2
Digital Input
(8.2)
>DI1.2 1 NAME VALUE 12 0
1 4 ACT ERR 5 0
0 7 BLOCKED UPDATED 6 0
0 25 INV
0 27 TESTED and so on for all
0 11 ERR CTRL signals of the
S2 Operator functions board
E3 Group Alarm
Figure 3-14. Parameters of the Second Signal
There are two subcommands for changing the displayed segment of the DB element:
S Expands the section at the cursor.
Sx Expands the segment number x.
In order to change the displayed default values, you must switch from the initial mode that you
reach after you give the CRDB command to the modify mode. There are two subcommands that
open a terminal for modification:
M Opens the line at the cursor for modification.
Mx The cursor moves to the terminal with number x and opens it for modification.
When the system is in modify mode, the name and current value of the
terminal are displayed at the bottom of the screen.
<Enter> You can enter a new value directly or leave the value unchanged. Every time
you press the Enter key, the cursor moves one step in the chosen direction
(<,> or =) among the connections.
If you are in modify mode, you move to a non-expanded segment. The window changes
automatically so that the non-expanded segment is expanded instead. Its first terminal is
indicated by the cursor (>) and modify mode is retained.
! Returns from modify mode to initial mode.
END Starts population of the target data base. The subordinate DB elements are
created and filled in with changed values or default values proposed by the
system. You can then create a new superior DB element.
<Ctrl-Break> To end populating the data base, press Ctrl-Break. An incomplete activity is
completed before populating of the data base is ended. If creation of a board is
in process, the DB element in question is deleted.
3BSE 002 417R601 3-15

ALL Starts automatic population of the subordinate DB elements as the

subcommand END, but the screen scrolls quickly through all subordinate DB
elements. The DB element you are leaving is then updated in the data base
with the modified values. If the system rejects the value at any input, no
updating takes place, and the rejected values are marked with a question mark
(?) instead of an asterisk (*), a symbol that indicates a change in the value.
ERROR Shows an explanatory error message for a value not approved by the system
(connection marked with “?”). Move the cursor (>) to the connection and
enter: ERROR.
3.2.2.2 Modifying Existing Data Base Elements
MDB
You can modify existing DB elements with the command MDB (Modify Data Base). If the
command is used with the Advant Controller 400 Series in OPERATION mode, the changes are
implemented terminal by terminal after approval. In OPERATION mode, however, only a small
number of characteristics can be modified. If the Advant Controller 400 Series is working in
CONFIGURATION mode, the modifications are only carried out when the entire DB element
has been processed.
Syntax:
0'%
0'% element-name
0'% item-des
0'% logic-file.logic-rec
0'%address-specification
After you press Enter, the specified DB elements appear on the screen. The MDB command
has the same subcommands as the CRDB command, except that the ALL subcommand is
missing and the following have been added:
<< Moves to the preceding DB element.
>> Moves to the next DB element.
RET (only for group alarm) Returns to the superior data base element from a
subordinated data base element (see the E subcommand in Section 3.2.2.1,
Creating Data Base Elements). When returning to the superior data base
element, the subordinated one is updated.
RESTORE Updates the data base element values displayed on the screen, thereby
showing the current state of the data base.
GVD Works like RESTORE, with the exception that the values are updated
dynamically until you press <Ctrl-Break>.
3-16 3BSE 002 417R601

6HFWLRQ 'DWD%DVH'RFXPHQWDWLRQ
3.2.2.3 Deleting Data Base Elements

DDB
You can delete existing DB elements in the data base using the command DDB (Delete Data
Base). DDB can only be used in CONFIGURATION mode.
Syntax:
''%
''% element-name
''% item-des
''% logic-file.logic-rec
''%address-specification
“Element-name” can also be a superior DB element, which means that all of its subordinate DB
elements are also removed.
3.2.3 Data Base Documentation
3.2.3.1 Creating a Data Base Printout

These functions are available in the Advant Station 100 Series Engineering Station only.
When you are working with the DIMDB, CRDB or MDB command, you can obtain a hard
copy of the upper part of the screen display by giving one of the following subcommands:
PRINT Gives a printout of the screen contents at the instant when the subcommand
was given.
PON Creates a printout every time there is a change in a display window.
POFF Cancels PON.
3.2.3.2 Listing a Data Base Diagram

LDBD
Use the command LDBD (List Data Base Diagram) to document the contents of the data base.
You can list the entire data base or parts of the data base. It is also possible to print out
cross-references to the PC elements connected to the data base terminals concerned.
The DB element is displayed with the default parameter values. Thereafter, a list of the
deviations from the default values is output, DB element by DB element. Two categories of
terminals are listed in the deviation list: On one hand, those which differ from the default
settings are listed and, on the other hand, those which are connected to a PC element are listed.
The latter only applies if a cross-reference listing is requested. Finally, a summary is output of
all the DB elements covered by the document.
Syntax:
/'%'
/'%' 6(/=select[=start][,interv][,gap][/;5()[;PCm[>PCn]]]
You can give the command with or without parameters. If the command is given without
parameters, the system prompts for them. You must specify which DB element types are to be
listed. You can do this with the parameter “select” in one of five ways, Table 3-3 refers.
3BSE 002 417R601 3-17

Table 3-3. Parameter “select” of Command LDBD
Parameter “select” Meaning Example

ALL All elements in the /'%'6(/ $//
data base will be
printed
element type All elements of a given /'%'6(/ ',& Lists all DI calculated.
type will be printed /'%'6(/ $, Lists all AI boards with
associated signals.
element identity A specific element will /'%'6(/ ',& Lists the element with
be printed /'%'6(/ $, item reference DIC3.
Lists the first AI board and
associated signals
group A number of elements /'%'6(/ ',&! Lists DIC3, DIC4...DIC7.
of a given type will be The first element specified
printed must exist.
name The element with the /'%'6(/ 02725 Lists the element with the
name NAME will be name MOTOR.
printed
wildcard “*” The wildcard character /'%'6(/ $, Lists all AI boards (S100)
will be replaced by any and AI modules (S800)
possible combination
of characters. Those /'%'6(/ $ Lists all elements starting
elements that fit will be
with “A”, e.g. AI, AO, AIPT,
printed. The wildcard
AIC
“*” is allowed at the
end of the selection
string only.
The following three parameters control page numbering:
Table 3-4. Other Parameters of Command LDBD
Parameter Use
start Used if the first page number of the listing
is to be other than 1.
interv Used if an interval greater than 1 is
required in the page numbering for an
element type.
gap Used if an interval greater than 1 is
required in the page numbering between
different element types.
3-18 3BSE 002 417R601

6HFWLRQ 'DWD%DVH'RFXPHQWDWLRQ
Examples:
#/'%' 6(/ ',&
Lists all DB elements of the type “DI Calculated”, starting on page 10.
#/'%'6(/ $//
Lists all elements in the data base. The first page is numbered 100, the following pages are
numbered 110, 120, etc. The page numbering is increased by 50 between DB element types.
#/'%'6(/ ',&!
Lists the first three DB elements of the type DIC.... Individual subordinate DB elements (e.g.,
AI1.1) cannot be listed. You must list the superior DB element with all subordinate DB
elements. For example, to list AI3.4, you must list AI3. AI3 and AI3.1...AI3.16 are then listed.
For control of the cross-reference printout, use the following parameters:
Table 3-5. Parameter XREF of Command LDBD
Parameter Function
XREF Cross-referencing is required
PCm If cross-referencing to one or several (but
not all) PC programs is required, the item
designation of the first one is stated here.
PCn If cross-referencing to one or several (but
not all) PC programs is required, the item
designation of the last one is stated here.
Example:
#/'%'6(/ 3,'&21;5()
#/'%'6(/ 3,'&21;5()3&!3&
3.2.3.3 Listing the Group Alarm Members

LGAM
Use the command LGAM (List Group Alarm Members) to list all members belonging to the
specified alarm group.
Syntax:
/*$0
/*$0 [6(/=select[=[start_page_numb][,page_interv]][/(;3]]
When the command LGAM is issued without parameters, it changes over to
dialog mode.
select: According to the corresponding LDBD parameter.
start_page_numb:According to the corresponding LDBD parameter.
page_interv: According to the corresponding LDBD parameter.
EXP: Keyword providing expanded output including node, logical file and logical
record.
3BSE 002 417R601 3-19

You can use this command to list:

• All data base elements in Group Alarm category (SEL=ALL)
• Arrangement of Group Alarm DB elements (e.g., SEL=GRPALARM1>4)
• One specific data base element (e.g., SEL=GRPALARM6).
LGAM is an interactive command and prompts for all required input, including the initial
parameters, if omitted.
Examples:
List all Group Alarm DB elements; First page = 10:
#/*$06(/ $//
List Group Alarm DB elements 1-5; First page = 100; Page interval = 10:
#/*$06(/ *53$/$50!
List all Group Alarm DB elements; First page = 10; Expanded list:
#/*$06(/ $// (;3
3.2.4 Compressing the Data Base Backup

After you have dimensioned and populated the data base in CONFIGURATION mode
(including final entry of NAME and DESCR, if possible), dump and reload the data base with
compression to minimize the memory space occupied. See Section 7.4.1, Dumping the Data
Base.
Use the command DUTDB to create a data base dump (see Section 7.4.1, Dumping the Data
Base). Load it using the command LOTDB (see Section 7.4.3, Loading the Data Base). If you
dump the data base prior to dimensioning the PC area, you can use the space gained there.
Note that you can only create or load a data base dump when the Advant Controller 400 Series
is in CONFIGURATION mode. If the PC programs are dimensioned and entered, they must
also be dumped and reloaded in connection with compression or redimensioning of the data
base (see Section 7.1, General).
During compression, a little spare space is left for extension of the entries to the connections
NAME and DESCR of the data base elements, should this prove necessary later on. If you run
out of space, there are two ways of getting more. Which one you choose depends upon how
much more space you need.
If the requirement is limited, you can dump and reload the data base again, with compression
but without redimensioning. In this way, more space is created for NAME and DESCR.
If you need more space, dump and reload the data base not only with compression, but also with
redimensioning to reserve space for more DB elements of the type where the shortage occurred.
This is the only recourse available, even if more DB elements are not required, and only
additional space for the existing NAMEs and DESCRiptions is required. After you enter the
new character strings, you can regain the memory space not used by dumping the data base and
reloading it with compression. As before, a little spare space is left for future extension of
NAME and DESCR.
3-20 3BSE 002 417R601

6HFWLRQ 'HIDXOW9DOXHVIRU'DWD%DVH+DQGOLQJ
In a similar way, compression removes the space needed to refer to an AI signal for the terminal
AI_ERR on the PIDCON DB element. If you want such space, you must redimension for more
AI_SIGNALS, as described above. After you have entered such references, you can once again
compress the data base.
As the data base is populated, make security copies on diskette at regular intervals. For final
security copying, use a DUAP dump; this covers both the data base and the PC programs.
It is, of course, possible to temporarily use the DUTDB dump for this purpose instead (see
Chapter 7, Backup and Transfer of Application Data).
3.2.5 Default Values for Data Base Handling

For populating and documenting the contents of the data base with data base elements, there is a
set of default values for every DB element type. This means that you do not have to fill in values
for the terminals whose default values are suitable for the application.
In a similar way, the data base diagram is simplified and compressed by separate listing of only
those terminals whose values deviate from the default values.
By means of source code handling, you can choose your own default values for this purpose and
for normal data base handling as well.
If the default values given by the system, the system defaults, are not suitable for your
requirements, you can define default values for each DB element type and store them in a
segment. These are known as general defaults.
Terminals for which no general default is given are subject to system default in the usual way.
CRDB and LDBD use such descriptions if they are stored in a segment with the name
DBGENDEF.BA. You can create a text segment like this with an editor. The procedure is
described in the manual for source code handling.
3.3 Structuring PC Programs

The ABB MasterPiece Language (AMPL) supports extensive structuring of application
programs, making it is easy for you to structure PC programs that mirror the process to be
controlled. It is advisable for you to make use of this feature when you are developing PC
programs.
There are, however, certain internal system limitations in terms of the maximum size of the
tables which store PC programs. For every PC program, there are five different internal tables.
For four of them, 32 kilobytes is the maximum size. Furthermore, the User Disk Application
Segments hold two other tables per PC program, the size of which is also 32 kilobytes.
Due to these limitations, it is important to divide up the entire control task in such a way that no
single PC program becomes too large. In other words, it is better to use several small PC
programs than one large PC program. The commands are also executed faster with small PC
programs.
3BSE 002 417R601 3-21

There is no easy way to specify in advance the maximum size of PC programs which can be
developed within the framework of these four tables. The space requirement is governed by such
things as the number of outputs on the PC elements, how they are interconnected, how they are
connected to the data base, the number of control parameters, the number of constants and the
number of measurement units allocated to variables. As you develop the PC programs, however,
information on the memory space still available is provided by each of the commands IS, C, CU
and DS. Information is provided on both the total space for PC programs and the space within
the current PC program for internal connections and data base connections.
3.4 PC Dimensioning
3.4.1 Dimensioning the Space for PC Programs

When an Advant Controller 400 Series is started for the first time, the PC area must be
dimensioned. You specify the number of PC programs, the number of places in the cycle
timetable (scan places) in the interpreter and the total memory space for PC programs. Further
on, you can activate a function to save the contents of the User Disk Application Segments in
the Advant Controller 400 Series for backup reasons.
To dimension and design PC programs well, you must be aware of certain size limitations
applicable to such PC programs. These limitations are described in Section 3.3, Structuring PC
Programs.
In addition to the data base and PC, there are certain functions in the Advant Controller 400
Series that require access to RAM (see Section 3.2.1.4, Memory Requirements for certain
Functions). Sufficient memory space must remain for those functions.
Dimensioning is carried out with the Advant Controller 400 Series in CONFIGURATION mode
(see Section 2.4, Working Modes of Advant Controller 400 Series).
DIMPC
When you use the command DIMPC, the screen display is divided. The upper part of the screen
shows the dimensioning details that you can change. On the lower part of the display, you
conduct a dialog with the engineering station.
Syntax:
',03&
Subcommands:
M Opens the line at the cursor (>) for modification.
! Switches from the modify mode to the initial mode.
DIM Transfers the requested dimensioning to the Advant Controller 400 Series.
PRINT Gives a printout of the screen contents.
END Ends DIMPC.
MWx Moves the Window, whereas -99≤x ≤99.
3-22 3BSE 002 417R601

6HFWLRQ 0RGLI\LQJWKH6L]HRIWKH6\PERO7DEOH
DIMENSION PC 1
Allocated PC area 100 kb
Available PC area 10 kb 2
Allocated interpreter area 2 kb
100 kb Size of PC pgm tables 3
4 (Min. 3 kb)
10 Number of PC programs (Min.1)
5
50 Number of scan places in interpreter A
50 Number of scan places in interpreter B
6 50 Number of scan places in interpreter C
7
Interpreter cycle times (ms)
A 10 20 40
B 50 100 200
C 250 500 1000 2000 8
0 kb Size of USER disk application seg area
Updating PC data sizes in PC1-PC10

?
Figure 3-15. Screen Display of the Command DIMPC
1. Free memory space in the Advant Controller 400 Series.

2. Size of memory area allocated for PC programs.
3. Amount of allocated PC area remaining.
4. Total memory area for PC programs.
5. Number of PC programs in the Advant Controller 400 Series.
6. Number of places in the cycle timetable (scan places) for interpreters A, B and C.
7. Cycle times for interpreters A, B, and C.
8. The contents of the User Disk Application Segments can be saved in the Advant
Controller 400 Series for backup reasons (USER disk application segments backup).
See Section 7.2.2.2, User Disk Application Segments Backup Handling.
3.4.2 Modifying the Size of the Symbol Table

The User Disk Application Segments hold a symbol table in which items such as PC variable
names, document texts and headline texts are stored. This symbol table is filled in gradually as
you load PC programs. It is stored in one of the User Disk Application Segments on the USER
volume (normally named PCMASS.SM). If the symbol table becomes full, it may be necessary
to make it larger. If the symbol table is larger than necessary, some of the space can be released
on the volume.
3BSE 002 417R601 3-23

MSTABS
Use the command MSTABS (Modify Symbol TABle Size) to modify the size of the symbol
table and its available space.
Syntax:
067$%6
The command displays the minimum and maximum new sizes and the current size. You can
enter the new size required here. Size is specified in numbers of blocks for the User Disk
Application Segments; this is equal to number of kilobytes.
Even if the total symbol table space available can be increased, there are certain limitations per
PC program which cannot be circumvented. The space for variable names is limited to 32
blocks (kilobytes) per letter as follows: Variable names starting with an “A” can be stored up to
32 blocks as well as variable names starting with a “B”, etc. It is advisable to limit the size of PC
programs and to consider the naming conventions with this in mind. The maximum size of the
PCMASS.SM segment is 1Mbyte.
Examples
Example 1:
You want to change the size from 49 to 85 blocks:
#067$%6
MINIMUM SIZE (Symbol-table already used) : 37
MAXIMUM SIZE (Available disk space) : 143
SYMBOL TABLE SIZE (BLOCKS) = 49 =
SYMBOL TABLE SUCCESSFULLY MODIFIED
Example 2:
If you have filled in the symbol table to 60 blocks (of the 85 possible) and wish to reduce the
table to this size, you will not succeed since there is not a sufficiently large uninterrupted area
on the volume. Of the 143 adjacent blocks initially available, 85 were used in the change in
Example 1.
#067$%6
INSUFFICIENT DISC SPACE: TRY COMPRESS; OTHERWISE MODIFICATION
IMPOSSIBLE
#067$%6
MINIMUM SIZE (Symbol-table already used) : 60
MAXIMUM SIZE (Available disc space) : 225
SYMBOL TABLE SIZE (BLOCKS) = 85 =
SYMBOL TABLE SUCCESSFULLY MODIFIED.
3-24 3BSE 002 417R601

6HFWLRQ (QWHULQJDQG(GLWLQJ3&3URJUDPV
3.5 Entering and Editing PC Programs
3.5.1 General
The first stage in PC programming is to prepare a PC program on paper. Next, enter the PC
program from this draft. The PC elements to be used in the PC program are defined first.
Then the various chosen PC elements are connected to each other. A check routine looks for
unconnected inputs. When all or part of the PC program has been entered, you can list it on a
printer and make a PC program dump.
The loading and editing commands include functions for loading, deletion and modification of
the function PC elements and structure PC elements in a PC program.
DANGER
Danger of personal risk! Risk of malfunctions!
A change in an executing PC program may affect the process as soon as it is carried out. Do not
make changes in PC programs that are executing unless you are thoroughly familiar with the
procedure for making PC program modifications on-line and know how the current PC program
and process will be affected by the change.
PC Program in BUILD
Mode
EBM DIBM
PC Program in BLOCKED
EBM Mode
BL DBL
PC Program in EXECUTION
Mode
Figure 3-16. BUILD, BLOCKED and EXECUTION Mode of a PC Program
The normal sequence when using these commands is:

1. Identify the PC programs in which PC elements are to be added, deleted or modified.
2. Place these PC programs in BUILD mode (for existing PC programs). Alternatively,
you can modify the PC program in EXECUTION mode (see Chapter 5, Changing an
Application Program On-line).
3. Perform the modifications.
4. Disable the BUILD mode (DIBM). The PC program(s) will be blocked when they have
gone through the check.
5. Deblock the PC program(s).
When a new PC program is loaded, all parts of the PC program are automatically placed in
BUILD mode.
3BSE 002 417R601 3-25

3.5.2 Enabling the BUILD Mode
EBM
Use EBM (Enable Build Mode) to make changes and additions in existing PC programs.
Since the command interrupts the execution of the PC program that is to be changed, you must
often place several interacting PC programs in BUILD mode.
Syntax:
(%0 pc_pgm [>pc_pgm]
Examples:
Enable BUILD mode in PC14:
#(%03&
Enable BUILD mode in PC18, PC19, PC20, PC21:
#(%03&!3&
3.5.3 Inserting PC Elements

Start editing by inserting the PC elements that are included in the PC program. The insertion of
PC elements starts with the command IS (Insert Statement).
If the PC program is not in BUILD mode, a message warns you about modifying the PC
program in EXECUTION mode. You should not modify PC programs that are executing unless
you are thoroughly familiar with the procedure for making PC program changes in
EXECUTION mode (see Chapter 5, Changing an Application Program On-line) and know how
the PC program is affected by such changes. To start with, the command produces a display
which states the amount of memory available.
IS
Syntax:
,6 item_des [;(1']
With the command IS you can:
• Construct a new PC program.
• Enter one or more statements into an existing PC program after the specified item
designation (item_des).
• Enter one or more statements into an existing PC program at the end of the specified item
designation. To do this, use ;END in the command line.
3-26 3BSE 002 417R601

6HFWLRQ ,QVHUWLQJ3&(OHPHQWV
The following subcommands are available:

<Enter> Moves to the next item designation (within the proposed level).
<< Moves up to a higher PC program level.
! Ends the dialog.
NOTE
The item designation chosen does not affect the sequence in the PC program, for
example, on execution and documentation. Where PC elements have function
parameters, you are prompted for these function parameters.
IS PC 1.1 IS PC 1.1.3 IS PC 1.1; END
PC1 PCPGM PC1 PCPGM PC1 PCPGM

PC1 PCPGM
.1 CONTRM .1 CONTRM .1 CONTRM
.1 CONTRM
.1 .7 .1
.1
.2 .1 .2
.2
.3 .2 .3
.3
.4 .3 .7
.4
.5 .4 .4
.5
.6 .5 .5
.6
.6 .6
.7
.2 .2 .2
.2
.1 .1 .1
.1
.2 .2 .2
.2
.3 .3 .3
.3
.4 .4 .4
.4
a) Existing PC b) Addition to c) Addition to d) Addition to

program structure PC program PC program PC program
Figure 3-17. How to Insert PC Elements (Statements)
When you use the IS command, the system starts a dialog and shows the next available item
designation on the level below. Every proposed item designation ends with the command “?”
and the system waits for a response.
3BSE 002 417R601 3-27

The following examples (5) show different ways to work with IS.
Example 1:
#,6 3&
Available space in area PC: 489 kbyte DB connection: 100%
Local data: 100%
PC1? 3&3*0
PC1.1? &21750
A new PC program is generated. The PC element is specified by its name and the call
parameters.
Example 2:
#,63&
Local data: 100%
PC1? 3&3*0
PC1.1? &21750
PC1.1.1?
PC1.1.5?
This example shows that you can choose an alternative item designation (PC1.1.5) instead of the
next free item designation proposed by the system (must be on the same level).
Example 3:
#,63&
Local data: 100%
PC1? 3&3*0
PC1.1? &21750
PC1.1.1? <Enter!
PC1.1.2? <Enter!
PC1.1.3? <Enter!
PC1.1.4? <Enter!
PC1.1.5?
You can move to the required item designation (within the proposed level) by pressing the Enter
key.
Example 4:
PC1.1.4? $1'
PC1.1.5?
PC1.2?
Use the subcommand “<<” to move up to a higher PC program level.
Example 5:
PC1.1.4? $1'
PC1.1.5? 3+
PC1.1.6?
3-28 3BSE 002 417R601

6HFWLRQ ,QVHUWLQJ3&(OHPHQWV
Perform page division and insertion of headings.

If no page number is specified, the page number is advanced by an increment of one.
Consequently, if the previous PC element is part of page 123.4, then the next PC element will be
allocated to page 124.4. If the request is repeated, again without specifying the page number,
said number is increased incrementally to 125.4, etc.
If the qualifier /H is issued, a subordinated dialog is obtained, where you can enter a header for
the current page.
3.5.3.2 Graphic/Non-graphic Presentation

This section concerns the Advant Station 100 Series Engineering Station only.
When keying in a PC program, you can choose whether to work with graphic or non-graphic
presentation on the screen. In graphic presentation, the top 27 lines of the screen of the
engineering station are used for graphic diagrams, and the bottom four lines are used for dialog.
Example:
#,63&
Available space in area PC: 489 kbyte
DB connection: 99% Local data: 99%
PC1? 3&3*0
PC1.1? &21750
PC1.1.1? $1'
PC1.1.2? 25
PC1.1.3?
Presentation on the screen:
PC1 PCPGM
.1 CONTRM(250,1)
.1 AND(3)
.2 OR(2)
.3 ?
PC1.1 ? CONTRM(250)
PC1.1.1 ? AND(3)
PC1.1.2 ? OR(2)
PC1.1.3 ? !
Figure 3-18. Example of Inserting PC Elements with Graphic Presentation

>G Changes from non-graphic to graphic presentation.
>NG Changes from graphic to non-graphic presentation.
3BSE 002 417R601 3-29

3.5.3.3 Assigning a name

Instance names are used to improve the engineering by defining (instance) names for PC
elements. To define a name use the >S directive while inserting PC elements. Instance names
must be unique within one PC program.
Example:
#,63&
Available space in area PC: 489 kbyte
DB connection: 99% Local data: 99%
PC1? 3&3*0
PC1.1? &21750 !6
INAME 6RPH%LQDU\/RJLF
PC1.1.1? $1'
PC1.1.2? 25 !6
INAME 7KLV256WDWHPHQW
PC1.1.3?
3.5.4 Connecting PC Elements
C
Use the command C (Connect) to connect PC elements in a PC program. If the PC program is
not in BUILD mode, text is displayed warning you about modifying an executing PC program.
You should not modify PC programs that are executing unless you are thoroughly familiar with
the procedure for making on-line changes (see Chapter 5, Changing an Application Program
On-line) and know how the PC program is affected by such changes. To start with, the command
produces a display which states the amount of memory available.
Syntax:
& item_des [:terminal]
& item_des [:function_parameter]
& [pc_pgm,] variable_name
Most of the PC elements, which have been chosen by insert statement, have inputs and outputs
which can be connected in one of the following ways.
Input terminals to:
• An output terminal of another PC element
• An input from the data base
• A constant
• An operational parameter.
Output terminals to:
• One or more PC element inputs
• One or more outputs of the data base.
If a variable name but no PC program number is given, the command assumes the last
PC program used.
3-30 3BSE 002 417R601

6HFWLRQ &RQQHFWLQJ3&(OHPHQWV
A removed connection produces one of the following results if

• The source is a PC element output, then the name and the unit are retained
• The source is a constant or operational parameter, then it ceases to exist, along with its
name and unit, when the last user is disconnected
• The source is a point in the data base, then the data base remains unchanged, but the PC
variable reflecting the value of the data base point ceases to exist; the “local” name and
unit also disappear.
Example:
#&3&
#&3&
#&3&)
#&$SSURYHG
#&3&$SSURYHG
The connect command is used to make connection, but can also be used when you want to
assign name and/or unit to a PC variable, constant or operational parameter. An unconnected
input cannot be assigned a name or unit. It is not possible to modify a name or unit in the data
base with this command.

When the C command has been started, you can use the following subcommands in the dialog
that follows:
! Ends the dialog.
> Processes the next terminal and the dialog continues after you press
Enter.
< Processes the previous terminal and the dialog continues after you
press Enter.
>> Processes the first terminal of the next PC element after you press
Enter.
<< Processes the first terminal of the previous PC element after you press
Enter.
= Processes the same terminal after you press Enter. The cursor does not
move.
>PRINT Gives a printout of the screen contents on a printer.
>[item_des]:terminal Processes the terminal with terminal number <:terminal> of the PC
element item_des and the dialog continues after you press Enter. If
item_des is omitted the current PC element is used.
>[item_des]:<name> Processes the terminal with name <name> of the PC element item_des
and the dialog continues after you press Enter. If item_des is omitted
the current PC element is used.
>>variable_name Processes the terminal with assigned variable_name
3BSE 002 417R601 3-31

When you order connection at the proposed terminal, the dialog automatically continues in the
specified direction (>, <) after you press Enter.
The subcommands can be specified as separate responses in the dialog, or at the end, as in the
following examples:
:5 (separate response)
:5 PC1.1.5:1 (subcommand at end)
3.5.4.2 Graphic/Non-graphic Presentation

When connecting PC elements, you can choose whether to work with graphic or non-graphic
presentation on the screen. In graphic presentation, the upper part of the screen of the
engineering station are used for graphic diagrams, and the bottom four lines are used for dialog.
PC1.1.1
PC1.1:5 1 & 20 <0>-
D=0 2
>? 3
CONNECTIONS MODIFIED ELEMENT BEING DISPLAYED : PC1.1.1

:2 IB ?
:2 d=0
:3 IB ?
:3
Figure 3-19. Connection of PC Elements with Graphic Presentation

>G Changes from non-graphic to graphic presentation.
>NG Changes from graphic to non-graphic presentation.
3.5.4.3 Connecting PC Element Inputs

An input can be connected to:
• An output of a PC element in the same PC program
• The data base
• A constant
• An operational parameter
• An input that is already connected.
3-32 3BSE 002 417R601

An output that is to be connected to an input can be identified by its variable name or its
terminal identity. For example, the output of an AND-gate can be identified either as
PC1.11.4:20 or by a variable name assigned by the user, e.g., MOTOR_1.
Connect a PC element terminal to a DB element terminal by specifying the identity of the DB
element (DB item designation) or the user-defined name, followed by a colon (:) and the name
of the required terminal. If you want to connect the PC element to the “VALUE” terminal of the
data base element, the terminal name and the colon can be omitted. The engineering station then
uses the “VALUE” terminal. Enter first “DB=” or just “=” followed by DOOR_CLOSED or
DI1.3, for example (see Section 2.2.2, Identifying Data Base Elements).
Values are assigned to terminals as follows:
Table 3-6. PC Element Inputs
Description Value
Operational parameters D=value
Operational parameters used several times MD=value
(the value is to be assigned to more than one
input)
Constants CD=value
Constants used several times (the constant is MCD=value
to be assigned to more than one input)
Boolean constants 0 or 1
Operational parameters and constants at inputs can be negated (inverted) with the minus
sign (-). The negation is specified at a PC element input. Outputs cannot be negated.
For operational parameters and constants that have not been named, it is possible to achieve
multiple use of the same operational parameter/constant. To do this, you specify the identity of
an input in the same PC program that is already connected to the relevant operational
parameter/constant.
3.5.4.4 Connecting PC Element Outputs

An output can be connected to
• Inputs of the same PC program which are not connected
• The data base.
An input or data base identity that is to be connected to an output is identified in the same way
as an output or data base identity upon connection of inputs (see Section 3.5.4.3, Connecting PC
Element Inputs), except that inputs cannot be identified with variable names.
Negation is specified after the identity of the connected input, since negation is always linked to
an input.
3BSE 002 417R601 3-33

An output can be connected to several terminals. These can be entered at the same time,
separated by commas and with data base identities at the end of the enumeration, if applicable.
Example:
3&3&'%
An output can also be connected to several terminals, one by one, using the subcommand “=”
(see Section 3.5.4.1, Dialog Handling).
3.5.4.5 Assigning Name and Unit

The following subcommand is available:
>S A terminal is assigned a name or unit as follows.
Example:
#&3&
Local data: 99%
PC1.1.2
:1 I IB PC1.1.1:20
:1
:2 TD IT D=30
:2 !6
NAME:= 7,0(
UNIT:=
. A previously specified name or unit can be removed with the subcommand “.”
(period).
Example:
:2 !6
NAME:= TIME = .
UNIT:= KG = .
The following rules apply for names and units:

• Names must not start with a digit or an underscore
• Names must not be equal to a PC program item designation, for example PC2.
• Allowed characters see Table 3-7 below.
3-34 3BSE 002 417R601

Table 3-7. Allowed Characters
Name of Character Printed Character Remark

Space ’’
Exclamation mark !
Double opening quote "
Hash mark #
Dollar $
Ampersand &
Single opening quote ’
Opening parenthesis (
Closing parenthesis )
Asterisk *
Plus sign +
Comma ,
Hyphen -
Dot .
Slash /
Zero ... Nine 0 ... 9 Must not be used as
first character
Colon :
Semicolon ;
Equal sign =
Question mark ?
At sign @
A ... Z A ... Z
Left square bracket [ USA (1)
Back slash \ USA (1)
Right square bracket ] USA (1)
Underscore _ Must not be used as
first character
a ... z a ... z
3BSE 002 417R601 3-35

Table 3-7. Allowed Characters (Continued)
Name of Character Printed Character Remark

Left brace { USA (1)
Vertical bar | USA (1)
Right brace } USA (1)
Tilde ~ USA, SWE (1)
Adieresis Ä GER, SWE (1)
Odieresis Ö GER, SWE (1)
Udieresis Ü GER, SWE (1)
Aring Å SWE (1)
adieresis ä GER, SWE (1)
odieresis ö GER, SWE (1)
udieresis ü GER, SWE (1)
aring å SWE (1)
germandbls ß GER (1)
(1) Allowed only, if the specified character set is selected for the project in the Application
Builder (USA=US english, GER=german, or SWE=swedish).
3.5.4.6 Disconnecting a Terminal

When you connect an already connected input to another terminal, the previous connection
disappears automatically. When you want to disconnect an output, use the subcommand “.”
(period). You are asked which connection(s) is/are to be removed.
When a connection is split apart, the result depends on the source.
• If the source is a PC element output, then the output retains the name and the unit.
• If the source is an operational parameter or a constant, then it ceases to exist when the last
user is removed. The name and the unit disappear.
• If the source is a terminal in the data base, then the data base itself remains unchanged, but
the PC variable that reflects the value at the terminal in the data base ceases to exist, and
the “local” name disappears as well.
3-36 3BSE 002 417R601

3.5.4.7 Long Dialog-Short Dialog

>SM Changes to short dialog mode
>LM Changes to long dialog mode
When the initial mode for the command has been defined, you can choose
between working with dialog in short mode (SM) or dialog in long mode
(LM) when there is a response in the dialog. Unless otherwise instructed,
the system works with dialog in long mode.
When you are working with an input or an output, the system shows its
number and, if the command is being used in the long mode, the name of the
terminal and details relating to the current connection. In the short mode, only
the number is displayed before the system continues with the processing of the
input/output.
Example for long dialog:
#&3&
Local data: 99% Element Name
PC1.1.2 TON
:1 I IB PC1.1.1:20 1
:1
Item Designation :2 TD IT ?
:2 '
PC Diagram Page
:5 0 OB Data Type where connected
:5 PC1.1.1:1 Terminal can be found
Terminal Number
:6 TE OT
:6 Connected Terminal
Terminal Name
Example for short dialog:

#&3&
Available space in area PC: 489 kbyte DB connection 99%
Local data: 99%
PC1.1.2
:1
:2 '
:5 3&
:6
3BSE 002 417R601 3-37

3.5.5 Deleting PC Elements

DS
Use the DS (Delete Statement) command to remove one or more PC elements from a PC
program. If the PC program is not in BUILD mode, a text warns you about modifying an
executing PC program. You should not modify PC programs that are executing unless you are
thoroughly familiar with the procedure for making PC program on-line changes (see Chapter 5,
Changing an Application Program On-line) and know how the PC program is affected by such
changes. The command produces a display which states the amount of memory available.
Syntax:
'6 item_des [>single_level_item_des]
You can use the DS command to delete a single statement or a group of statements. The start
and end item designations must be on the same level in the PC program structure; any
intermediate item designations must also be on this, or a lower, level.
Use this command to delete:
• Single PC elements.
• All PC elements from a given item designation to another given item designation inclusive.
The rules for choosing deletion limits are:
• The first and last item designation must be on the same level in the PC program structure.
• Intervening PC elements on a higher level are not permitted.
• Intervening PC elements on a lower level are permitted.
A “single_level_item_des” is an item designation in the shortened form that is permitted within
one level in the PC program structure.
Example:
3-38 3BSE 002 417R601

6HFWLRQ /LVWLQJ3&3URJUDPV
PC20
.1
.1
.2
.2
.1
.1
.2
.3
.2
.3
Figure 3-20. Example of PC program Structure
#'63&!
deletes all PC elements in the structure
#'63&!
deletes two PC elements
#'63&!
deletes PC elements PC20.2.1, PC20.2.1.1, PC20.2.1.2, PC20.2.1.3 and PC20.2.2.
3.5.6 Listing PC Programs

LS
Use this command to list
• A single statement
• All statements between and including the two item designations
• A number of statements beginning with the item designation specified.
Syntax:
/6 item_des [>item_des]
/6 item_des [;number_of_elements]
3BSE 002 417R601 3-39

Examples
Example 1:
List statements PC1.1 to PC1.1.6:
#/63&!3&
Example 2:
List four statements starting with PC1.1.1:
#/63&
1 2 3 4 5 6 7
#LS PC4.1.1;5
17 PCD-PAGE : 1
PC4.1.1 MUL (R,2)
:1 IR =AI1.2 =AI1.2 G
:2 IR D=1.040
:20 OR liter
16 =AO1.2 =AO1.2 P
1 PC4.1.2:I
PC4.1.2 COMP-R (2,2)
:1 I IR PC4.1.1:20 liter 1
15 :10 HHYS IR D=100.000 liter
:11 H1 IR H_LIM_1 liter D=700.000
:12 H2 IR H_LIM_” liter D=900.000 8
:20 I<H1 OB 9
:21 I>=H1 OB ABOVE_H_LIM_1
=DO1.5 =DO1.5 P 10
14 :22 I<=H OB ABOVE_H_LIM_2
2 PC4.1.3:2
N
13 :30 LHYS IR D=100.000 liter
:31 L1 IR D=100.000 liter
:32 L2 IR D=200.000 liter
:40 I>L1 OB
:41 I<=L1 OB =DO1.4
:42 I<=L2 OB
12 11
Figure 3-21. Example of Printout with the LS Command
The list contains the following information:
Table 3-8. Explanations of the Example of Printout with the LS Command
For each Element For each Input For each Output

Item designation ................................17 Terminal number ...............................15 Terminal number ...............................14
Call name ............................................1 Terminal name ..................................16 Terminal name ..................................13
Call parameter ....................................2 Data type ..........................................11 Data type ...........................................12
Variable name .....................................3 Variable name .....................................8
Terminal identity and page number Terminal identities of users and

in PC diagram of source ......................5 page number in PC diagram .............10
Unit ......................................................7 Unit ......................................................6
Connections to data base ...................4 Connections to data base ...................9
3-40 3BSE 002 417R601

6HFWLRQ 'LVDEOLQJWKH%8,/'0RGH',%0
3.6 Disabling the BUILD ModeDIBM

Use the DIBM (DIsable Build Mode) command to end building of one or more PC programs.
Syntax:
',%0 pc_pgm [>pc_pgm]
The PC program(s) are blocked afterwards and can be changed to EXECUTION mode using the
DBL command (see Section 4.2.3, Deblocking the PC Program Execution).
If non-connected inputs exist, they are listed and the BUILD mode is not concluded. Connect
those unconnected inputs and repeat the DIBM command.
3.7 Connecting Unconnected Inputs

CU
Inputs specified as unconnected must be connected. To do this, use the CU (Connect Undefined)
command, which follows the same pattern as the C (connect) command.
Syntax:
&8
&8 item_des [:terminal]
&8 item_des [:function_parameter]
&8 [pc_pgm,] variable_name
The difference between C and CU:

• C processes all the inputs and outputs for a PC element.
• CU processes only inputs that have not been connected.
3.8 Creating Security Copies

Create security copies of the entered data base and PC programs at regular intervals. For best
results, use the DUAP command (see Section 7.3, Total Backup).
Additionally, create a security copy of the associated USER volume. This is only needed if the
User Disk Application Segments are not saved on the Advant Controller (see Section 7.2.2.2,
User Disk Application Segments Backup Handling) or if you are using another dump type.
3BSE 002 417R601 3-41

3-42 3BSE 002 417R601

6HFWLRQ 0RGLI\3HUPLVVLRQ
Chapter 4 Commissioning and Testing
When you switch a PC program from BUILD mode to EXECUTION mode, use the command
DIBM first to reach BLOCKED mode. Execution of the PC program begins after the command
DBL (DeBLock), but only if inputs of the execution unit have not been assigned parameters that
prevent them from starting.
4.1 Modify Permission

For each execution unit (i.e., CONTRM, MASTER or SEQ), the modify permission must be
enabled to allowed it to block execution (BL and BLRS commands). For modifications in
EXECUTION mode and modifications in BUILD mode, the modify permission for each
execution unit in the PC program must be enabled (the EBM, IS, D and DS commands).
The modify permission is enabled with the EMP (Enable Modify Permission) command (not
for locked PC programs).
The modify permission can be enabled or disabled
• When modify permission is enabled, tests and modifications of all kinds are permitted.
• When modify permission is disabled, all PC commands that in any way change the state of
the system, except modification of the values of operational parameters, are forbidden (and
prevented).
One way of utilizing the status of the modify permission is to use it to indicate the testing status
of the relevant execution unit. You can use it during commissioning to flag the parts of the PC
program that have been fully tested.
Those commands that are forbidden when modify permission is disabled are ineffective on
execution units with modify permission disabled. In particular, commands in which the scope is
specified with an interval (from one designation to another, inclusive) are executed only if all
execution units in the range have modify permission enabled.
The modify permission is enabled in the initial mode, i.e., when an execution unit has just been
entered.
The state of the modify permission can be read with the command LMP (see Section 4.1.3,
Listing the Modify Permission). On each execution unit, there is an output MODP. A 1 at this
output corresponds to modify permission enabled.
3BSE 002 417R601 4-1

&KDSWHU &RPPLVVLRQLQJDQG7HVWLQJ
4.1.1 Enabling the Modify Permission

EMP
The EMP (Enable Modify Permission) command enables the modify permission for one or
more execution units.
Syntax:
(03 item_des [>item_des]
This command activates the modification permission for one or more execution units (item_des
stands for execution units). The two item designations must refer to a PC program or an
execution unit (PCPGM, CONTRM, MASTER, or SEQ).
Example:
#(033&!3&
modifies permission of PC1.1 to PC1.5.
4.1.2 Disabling the Modify Permission

DIMP
If you wish to prevent all PC commands that change the state of the system, you can disable
modify permission with the DIMP (DIsable Modify Permission) command.
Syntax:
',03 item_des [>item_des]
This command deactivates the modification permission for one or more execution units
(PCPGM, CONTRM, MASTER or SEQ). If an execution unit concerned does not satisfy the
requirements for deactivation, the command is not executed and a message indicates which
execution unit has not satisfied the requirement. The two item designations must refer to a PC
program or an execution unit.
4.1.3 Listing the Modify Permission

LMP
The command LMP (List Modify Permission) causes the system to indicate whether the modify
conditions are enabled or disabled for one or more execution units.
Syntax:
This command displays if the modify permission is enabled or disabled in one or more
execution units. The two item designations must refer to a PC program or an execution unit
inclusive.
4-2 3BSE 002 417R601

6HFWLRQ 3&3URJUDP7HVWV
4.2 PC Program Tests

The test functions contain the functions needed when a PC program is being tested during
design, commissioning, troubleshooting or maintenance. There are six types of test functions:
• Listing of variables (LV)
• Blocking (BL, BLRS, DBL, LSS)
• Modification of variables (MV)
• Modification of variable names (MNV)
• Display of PC element symbol with current values at the connections (GEPCD)
• Tabulation of the values of a number of variables (GETAB).
4.2.1 Listing Variables

LV
Use the command LV (List Variable) to list the variables that are connected to the given
terminal. This can be a PC variable or a terminal in the data base. If you ask for the connection
of a data base terminal and enter a PC program designation, the command returns a detailed list
for the PC program chosen. If the given terminal is also used in other PC programs, these PC
programs are also included in the list, without information as to where in the PC program the
terminal is used.
If a PC program designation is not supplied, the command returns detailed lists of all the PC
programs concerned.
Syntax:
/9 item_des:terminal
/9 [pc_pgm,] variable_name
/9 [pc_pgm,] ['%] =data_base_identity
You can list
• A PC variable
• A data base item.
You enter the data_base_identity as
data_base_instance:terminal.
If you omit the DB terminal the VALUE terminal is used as default.
Figure 4-1 gives examples for usage of LV command.
3BSE 002 417R601 4-3

Command given
with PC element item Details of:
designation and PC program Page number and
terminal number Variable name
Data type identity of terminal
Details of
operational
parameter or
constant
#LV PC1.1.1:1
PC1,START
MD=1 B 1 PC1.1.1:1
Command 1 PC1.1.1:2
given with 2 PC1.1.2:2
variable name 2 PC1.1.3:R
2 PC1.1.3:L
#LV START
PC1,START
Command MD=1 B 1 PC1.1.1:1
given with data 1 PC1.1.1:2
base identity, the 2 PC1.1.2:2
DB terminal 2 PC1.1.3:R
2 PC1.1.3:L Information
VALUE #LV =VENT OPEN
is used =VENT OPEN on ‘source’
by default =DI5.3
=8.131:12
B
1 PC1.1.1:20 S
2 PC1.1.2:1
PC4:ON
PC6.7.9:R
PC7.2.1.3:2
#LV PC4,=VENT OPEN
=VENT OPEN
=DI5.3
=8.131:12
B
Command 1 PC4:ON
PC1
given with data- PC6
base identity, the #LV =DO1.16:5 PC7
DB terminal =AdjustControl
ERR is used =DO1.16
=9.16:5
B
1 PC1
PC2
The connections of a data base terminal are

Up to three alternative identities shown in detail for the PC program
for a data base terminal are shown
given in the command
The connections of a data base terminal are shown in

detail. If no PC program designation is
supplied with the command, the connections in
all PC programs are listed.
Figure 4-1. Example of Printout with the LV Command
4-4 3BSE 002 417R601

6HFWLRQ %ORFNLQJWKH3&3URJUDP([HFXWLRQ
4.2.2 Blocking the PC Program Execution

Only complete PC programs or execution units, i.e., PCPGM, CONTRM, MASTER, or SEQ,
can be blocked. Blocking of an entire PC program has the automatic consequence that all
execution units in the PC program are blocked, after which the blocking can be canceled for the
entire PC program or for one unit at a time.
BL
To facilitate PC program testing, use the BL (BLock) command when:
Syntax:
%/
%/ ['%,] pc_pgm [> pc_pgm]
%/ ['%,] item_des
You can block
• One or all PC programs
• One execution unit (PCPGM, MASTER, CONTRM, or SEQ) or all execution units in one
or more PC programs
• Output to the data base (but not execution) from the specified execution unit or PC
program(s)
• Blocking of output data to the data base from all execution units in several PC programs.
BLRS
The BLRS (BLock and ReSet) command works in the same way as BL, but resets the execution
units (resets the outputs to the data base) after they have been run through for a last time.
Examples:
#%/56'%3&
blocks and resets the outputs of PC1.2.3
#%/563&
blocks and resets the outputs of all execution units of PC1.
4.2.3 Deblocking the PC Program Execution

DBL
This command removes the blocked status from executing units (PCPGM, MASTER,
CONTRM and SEQ) and places those units in the active status.
Syntax:
'%/ pc_pgm [> pc_pgm]
'%/ item_des
3BSE 002 417R601 4-5

You can use this command to deblock

• A PC program
• An execution unit
• Several PC programs
• Data base updates.
4.2.4 Listing the Status of PC Programs

LSS
Use the LSS (List Special Status) command to list parts of PC programs that are blocked
(BLOCKED mode). The list shows the units that are in BUILD mode, blocked or blocked for
output of data to the data base.
Syntax:
/66
This command enables you to list the special status for
• A single execution unit (PCPGM, MASTER, CONTRM, or SEQ)
• A group of execution units
• All execution units in the system.
The special status types are:
• EXECUTION mode (Complete PC program)
• BUILD mode (Complete PC program)
• BLOCKED mode
• BLOCKED for data base.
The working mode of the Advant Controller 400 Series (CONFIGURATION mode or
OPERATION mode) is also listed.
4-6 3BSE 002 417R601

6HFWLRQ 5HDGLQJDQG0RGLI\LQJD9DULDEOH9DOXH
4.2.5 Reading and Modifying a Variable Value

Figure 4-2 and Table 4-1 show which values can be modified and read.
PC2 Call Parameters:

PCPCM(1Ø.1)
1 1 ON RUN 5 Cycle Time Parameter
0 2 R
Position Parameter
.1
CONTRM(1ØØ.1.Ø)
1 1 ON RUN 5 PC Variable
0 2 SINGLE MODP 6
0 3 R
.1
Function Parameter PRINT(1,1,72) 1 & 20
F=1 F1 FIRST BUSY 5 ?2
F=1 F2 LAST REPNO 6
Operational F=1 F3 FF ERR 7
D=2 1 NODE
Parameter CD=11 2 NETW
? 3 PRID
? 4 ACT
Constant D=’FAULT REPORT’ 11 TEXT1
Figure 4-2. Example with the MV Command
Table 4-1. Values that can be handled by the MV Command
3&9DULDEOHV 'HVLJQ3DUDPHWHUV
Value can be Opera- from

read/ tional element Con-
from Function
modified in para- input stants
element Call parameters para-
service meters connected
output meters
to data
base
FDQEHUHDG \HV \HV \HV \HV \HV \HV
F\FOHWLPHSDUDPHWHUV for
PCPGM, CONTRM, MASTER
and SEQ under the same PC
FDQEHFKDQJHG \HV QR QR QR interpreter QR
SRVLWLRQSDUDPHWHUV for
PCPGM, CONTRM, MASTER
and SEQ
3BSE 002 417R601 4-7

All these types of values can be read while the PC program is being executed, but only certain
types can be modified.
The only call parameters that can be modified are position parameters (place in cycle timetable)
and cycle time parameters for PCPGM, CONTRM, MASTER and SEQ. For cycle time
parameters, only cycle times under the same priority (same PC interpreter) are accessible.
MV
Use the MV (Modify Variable) command to modify or read the value of a variable.
Syntax:
09 [pc_pgm,] variable name
09 item_des : terminal
09 item_des : call parameter
This command permits the reading and in some cases, changing, of the value of
• A PC variable
• An operational parameter
• A constant
• A call parameter
• A function parameter.
When the system returns the character “=” after a displayed value, this means that the value can
be modified. Call and function parameters cannot be referred to by name. They must be
specified by their number preceded by a “C” or “F”, respectively.
Example:
#093&&
The system displays the current value and the unit (if any). You can leave the value as it is or
specify a new value.
>,< The angle brackets “>” and “<” operate as they do in other commands, but the
meaning of next or preceding depends on the type of terminal or design
parameter you are dealing with.
Examples:
#09)8(/
PC1.1.2:20=1 =!
PC1.1.2:21=0 =
When you use the name of a variable, the next terminal of the PC element that is the source of
the variable is referenced (PC1.1.2:21).
#093&
PC1.1.3:1 =!
PC1.1.3:3=1 =
4-8 3BSE 002 417R601

6HFWLRQ 0RGLI\LQJWKH1DPHRID6WDWHPHQWRU9DULDEOH
If you use the next command “>” on the destination PC element PC1.1,3,1, it ignores the
existence of :2 and jumps directly to :3, which in turn can be modified.
PC1.1
.2 .3
.19 .1
.20 FUEL .2
.21 .3
Figure 4-3. Example of Variables for different PC Elements
< When you use the subcommand “<” at a terminal identity and the value of the
first terminal is displayed, the last function parameter in the PC element is
displayed after you press Enter.
Example:
#093&
PC1.1.1:1=1
PC1.1.1:F3=1
Correspondingly, when the value of the first function parameter is displayed, the value of the
last call parameter is displayed after you press Enter.
Example:
#093&)
PC1.1.1:F1=0
PC1.1.1:C3=4
> The opposite applies when you use the “>” subcommand (right angle bracket).
If the PC element has no function parameters, the system advances from
displaying the value of the last call parameter to the value of the first terminal
when you use the “>” subcommand. If you use the “<” subcommand, the
system jumps from the first terminal value to the last call parameter value.
! The command is terminated with the subcommand “!”.
4.2.6 Modifying the Name of a Statement or Variable

You can define the names of PC statements (instance names) or names of PC variables in PC
programs. Such names are stored permanently in the User Disk Application Segments that
belong to the Advant Controller 400 Series (see Section 7.2.2, USER Volume).
You can use instance names to improve your engineering by giving PC statements unique
names. They can be introduced by the MNV or IS (see Section 3.5.3.3, Assigning a name)
command
You can use the PC variable name instead of the terminal identity for identification. If a named
PC element output is connected to a PC element input, the variable name of the output is also
stated at the input of that element. On disconnection, however, the name stays at the output only.
3BSE 002 417R601 4-9

Variable names can be assigned with three different commands:

• MNV, the complete command
• C (see Section 3.7, Connecting Unconnected Inputs)
• CU (see Section 3.7, Connecting Unconnected Inputs).
The reason why C and CU have also been given this facility is that it may be useful to enter
names at the same time as connection work is being carried out. Compared with C and CU,
MNV has an additional function, which is used to rectify any mismatch between the User Disk
Application Segments and their backup on the Advant Controller 400 Series (see Section
7.2.2.4, User Disk Application Segments Mismatch). This function is described at the end of
this section.
MNV
Use the MNV (Modify Name of Variable) command to read or modify an instance name or to
read, modify, enter and delete variable names.
Syntax for defining instance names:
019 item_des
019 [pc_pgm,] instance_name
Instance names are used to assign names to PC statements.
Syntax for defining Variable names:

019 item_des : terminal
019 [pc_pgm,] variable_name
Variable names can be defined for:
• PC element outputs
• Operational parameters and user-defined constants
• Inputs coupled to the data base (not the structure PC element inputs).
Subcommands:
<,> The angle brackets “<” and “>” work in the same way as in the MV (Modify
Value) command.
! Terminates the command.
. Deletes the name.
4-10 3BSE 002 417R601

6HFWLRQ 0RGLI\LQJWKH1DPHRID6WDWHPHQWRU9DULDEOH
Examples:
#0193&
/=StartOfSecondControlLoop
gices PC1.1.1 the instance name StartOfSecondControlLoop
#0193&
PC1.1.1:2 = $
gives PC1.1.1:2 the variable name A5
#0193&
PC1.1.1:2/A5=
reads the variable name of PC1.1.1:2
#0193&
PC1.1.1:2/A5= $
reads and modifies PC1.1.1:2
#0193&
PC1.1.1:2/A7=
reads and deletes the variable.
The MNV Command and the User Disk Application Segments:

In addition to inserting and removing variable names in standard cases, this command has an
additional function. Due to handling errors or malfunctions, a mismatch can, in rare cases, occur
between the symbol table stored in the User Disk Application Segments and the flag in the
system that indicates whether a variable has a name.
You can correct three different types of mismatches with the MNV command.
1. In the system, there is an indication that the name exists, but it is absent from the symbol
table. If MNV is performed on such a variable, an error text appears first, stating that there
is a mismatch. After this, you can choose one of the following options:
a. Enter a period (.) to delete the flag (which indicates a named variable).
b. Enter a variable name. The name is stored in the symbol table.
2. There is a name in the symbol table, but the system has no flag to indicate that the
corresponding variable is named. You can choose one of the following options:
a. Enter a period (.). The name is deleted from the symbol table.
b. Enter a variable name (a new name or the old one). The name is stored in the symbol
table and at the same time a flag is set in the system to indicate that the variable is
named.
3. In the symbol table there is a name, but the corresponding variable does not exist in the
system. After the explanatory error text, enter a period (.). The name is deleted from the
symbol table.
3BSE 002 417R601 4-11

4.2.7 Displaying a PC Element with Variable Values
GEPCD
Use the GEPCD (GEnerate PC Diagram) command to display a single PC element and the
values of its terminals.
Syntax:
*(3&' [item_des]
*(3&' ' [, item_des]
This command is used to display the current values of inputs and outputs of a PC element.
The values can be both statically and dynamically updated and diagnosed, and the connections
can be traced backwards. There are a number of different ways of choosing which PC element is
to be displayed. At the beginning of the command, either the specified PC element is displayed
or, if the command is given without item designation, the PC element most recently displayed is
displayed again. If a “D” is entered as a parameter, all values are inserted and displayed with
dynamic updating. Use <Ctrl-Break> to get back to the command level with context-sensitive
subcommands. The following subcommands are available for GEPCD:
HELP, ?, IV, GVD, MV, DV, GS, DIAG, GEPCD, MW, PRINT, RMD, !, END
Subcommands:
HELP or ? displays available subcommands.
IV (Insert Value) inserts the current values of a selected terminal or variable on
the display.
syntax: ,9 [variable_identity]
GVD (Get Values Dynamically) displays the status of variables dynamically.
syntax: *9'
MV (Modify Value) enables the modification of operational parameter and, in
some cases, call parameter values (see Section 4.2.5, Reading and Modifying
a Variable Value).
syntax: 09 variable_identity
syntax: 09 item_des : call parameter
DV (Delete Value) deletes the current values of all or selected terminals on the
display.
syntax: '9 [variable_identity]
GS (Get Source) displays the source terminals for the selected input terminal.
syntax: *6 terminal
DIAG (DIAGnose) traces back the source and diagnoses the cause of a particular
output terminal value—PC elements displayed or those which have more than
one input (they can cause the status of the specified connection) and those
which are connected to the data base.
syntax: ',$* terminal
GEPCD (GEnerate PC Diagram) displays the PC element selected. If a “D” is entered
as a parameter, values are inserted and displayed with dynamic updating.
syntax: *(3&' ', item_des
4-12 3BSE 002 417R601

6HFWLRQ 'LVSOD\LQJD3&(OHPHQWZLWK9DULDEOH9DOXHV
MWx Moves the Window, whereas -99≤ x ≤99.

PRINT Outputs a copy of the current display on the printer.
syntax: 35,17
RMD (ReMove Display) terminates the GEPCD command and removes the display
from the screen. If you start GEPCD again, the system starts from the PC
element that was displayed before RMD. If you have terminated the GEPCD
command with the subcommand “!”, the PC element on the screen can be
removed with the RMD (ReMove Display) command.
! Terminates the command and leaves the display on the screen, but the variable
values are not updated.
END Terminates the GEPCD command and removes the display from the screen.
Example:
#*(3&'3&
#*(3&''3&
PC1.3.3
RAMP
2.307 1 I O 10 0.000
0.000 2 STEP+ O=HL 11 0.000
3.434 3 STEP- O=LL 12 0.000
1.762 4 SLOPE+ ERR 13 0.000
0.400 5 SLOPE-
1 6 BAL
0.000 7 BALREF
1000.000 8 OHL
-1000.000 9 OLL
ELEMENT BEING DISPLAYED : PC1.3.3

?IV
Figure 4-4. Screen Display on Updating Variable Values
3BSE 002 417R601 4-13

Example:
#*(3&'3&
? *6
PC1.1.5
0 1 & 20 0
1 2

?
Figure 4-5. Screen Display before Command GS is used
PC1.1.4
0 1 ≥1 20 1
1 2

?
Figure 4-6. Screen Display after Command GS is used
Example of the DIAG subcommand:

You want to know which element of those shown in Figure 4-7 is causing a “0” at the output of
PC1.1.5.
.1
0 ≥1 20
0 1
2
.2
0 1 & 20
1 2 .5
0 &
1 1 20 0
2
.3
1 1 & 20
1 .4
2 1 ≥1 20
0 1
2
Figure 4-7. Example with the DIAG Command
4-14 3BSE 002 417R601

6HFWLRQ 'LVSOD\LQJWKH9DULDEOH9DOXHVLQD7DEOH
Call the PC element PC1.1.5 and use the DIAG subcommand as follows:
"',$*
PC1.1.5
0 1 & 20 0
1 2

?
Figure 4-8. Example with the DIAG Command (continued)
The values of the terminals are displayed. Use the DIAG subcommand again for terminal 1:
"',$*
PC1.1.1
0 1 ≥1 20 0
0 2

?
Figure 4-9. Example with the DIAG command (continued)
The result of the DIAG command above is displayed in Figure 4-9. Element PC1.1.1 has two
inputs with “0”, which cause the “0” output value of element PC1.1.5.
4.2.8 Displaying the Variable Values in a Table
GETAB
Syntax:
*(7$%[table_name] [/LT]
Use this command to display the current values of terminals in PC programs and the data base in
a table or in a graphical diagram. The values can be both statically and dynamically updated.
With dynamically updating subcommands, use <Ctrl-Break> to get back to the command level.
The following data types can be presented: B, IB, I, IL, R, T, TR.
The following subcommands are available for GETAB:
GVD, PRINT, HELP, ?, MV, IV, DV, RMD, SAVE, !, END
3BSE 002 417R601 4-15

Subcommands:
GVD (Get Values Dynamically) displays the status of variables in the table
dynamically.
syntax: *9'
PRINT Outputs a copy of the current display on the printer. This subcommand is only
available when using the table display.
HELP or ? Displays available subcommands.

MV (Modify Value) enables the modification of operational parameter and, in
some cases, call parameter values. The MV subcommand starts with a dialog
(see Section 4.2.5, Reading and Modifying a Variable Value).
syntax: 09 variable_identity
syntax: 09 item_des : call parameter
IV (Insert Value) inserts the current values of a selected terminal on the display.
syntax: ,9 variable_identity
syntax: ,9 ['%] =data_base_identity
DV (Delete Value) deletes the current values of all or selected terminals on the
display.
syntax: '9 [variable_identity]
syntax: '9 ['%] =data_base_identity
RMD (ReMove Display) terminates the GETAB command and removes the display
from the screen.
SAVE Save the contents of the current table in a file. This subcommand is only
available when using the graphical display mode.
! Terminates the command and leaves the display on the screen, no updates of
the variables take place.
END Terminates the GETAB command and removes the display from the screen.
=AI1.4 R 85.600
=AI1.5 R 32.800
=AO1.3 R 0.000
=DO1.1 R 0
PC4.1.3:5 R 1
=AI1.1 R 0.000
PC4.1.2:21 R 1
=AO1.1 R 0.000
Figure 4-10. Example with the GETAB Command
4-16 3BSE 002 417R601

6HFWLRQ 6\VWHP/RDG
After you give the GETAB command, a dialog begins. The dialog contains a number of
subcommands that make it possible to
• Resume dynamic display
• Remove individual values from the table
• Add values to the table
• Print out the table on a printer
• Change the values of operational parameters
• Terminate the command.
Both values of variables in PC (also in several PC programs simultaneously) and values in the
data base can be included in the table. One variable at a time is specified, and each newly
specified variable is added to the old table. A maximum of one screen page of variables can fit
into this table. For every additional variable specified, the oldest variable is deleted from the
table.
The values can be displayed either with or without periodic updating. In the initial state, after
each additional variable is added to the table, display is static.
When you give the command, the most recent selection is shown again. Upon additions to the
table, the command also starts from the most recent table. The table is stored in the symbol table
(User Disk Application Segments) when the command is running. At the same time, this means
that the table can be saved between two activities.
The table that is generated consists of data base identity or variable identity and data type, value
and unit.
4.3 System Load

When the Advant Controller 400 Series is executing the PC programs, the CPU load depends
mainly on the size and nature of the PC programs and, above all, on the cycle times chosen for
the various execution units.
ANPER
Use the ANPER (ANalyze PERformance) command to investigate the actual load of the Advant
Controller 400 Series. Using its indications of the system load as a basis, you can adjust, for
example, the chosen cycle times and thereby optimize the use of the available performance.
Syntax:
$13(5
The command is made up of a number of menu options. The first choice is between analysis of
the load of the entire Advant Controller 400 Series (system load) or the load per system part
(task load). The second of these options is intended for analysis in special circumstances and is
not described here. It is assumed that the SYSTEM LOAD option will be requested.
3BSE 002 417R601 4-17

After this, you can choose from three different ways of displaying the load:
• Load at time of reading
• Graphic display of load
• Tabulated display of load.
<Ctrl-Break> If you choose graphic or tabular display of the load, a permanent display
which persists until you clear it with Ctrl-Break is obtained. With these two
types of display, you must first choose the interval at which the value is to be
updated (one, 10 or 100 seconds). The updating interval is the same as the
time used in the mean value calculation.
If, for example, updating every 10 seconds is requested, a value that is the mean value of the
load over the last 10 seconds is displayed at each updating.
The readings obtained must be correctly interpreted. It is important that you recognize that it is
normal for the load of the Advant Controller 400 Series to vary greatly with time and as a
function of the situation. The shorter the period for which the load is observed, the more it will
appear to vary. Conversely, mean-value calculation over a longer time conceals load variation
details and appears to smooth out temporary variations.
What is meant by “short” and “long” in this context, and how high can a system load be
and still be acceptable for a “short” time? No detailed, general answer can be given to this,
but it can be said broadly that upon certain events in the process, or when an operator at an
Advant Station 500 Series Operator Station communicates with the Advant Controller 400
Series, the load may go up to 100 percent for several seconds — sometimes for more than
10 seconds — without the Advant Controller 400 Series being overloaded. The long-term load,
however, should be at a reasonable distance from 100 percent.
4.3.1 Blocking on Overload

This function is available on the Advant Station 100 Series Engineering Station only.
As a result of the overload, the digital display on the CPU of the Advant Controller 400 Series
shows the number “09” and the Advant Controller 400 Series stops. You can use the BL
(BLock) command (see Section 4.2.2, Blocking the PC Program Execution) on overloading as
follows:
1. Connect the engineering station directly to the relevant Advant Controller 400 Series.
2. Start the Advant Controller 400 Series off-line (start mode selector set to OFFLINE).
3. Start the engineering station via the start-up menu “Advant Controller 400 overload
blocking”.
4. Start the BL command without parameters. All PC programs are now blocked.
5. Warm start Advant Controller 400 Series (start mode selector set to AUTO).
6. Start the engineering station in the normal way and reduce the system load, e.g., by
prolonging cycle times.
4-18 3BSE 002 417R601

AdvantController 400 Series

Uploaded by

Copyright:

Available Formats

AdvantController 400 Series

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AdvantController 400 Series

Uploaded by

Copyright:

Available Formats

Advant® OCS $03/&RQILJXUDWLRQ

with Master software Advant® Controller 400 Series

Copyright © ABB Industrietechnik GmbH 1999.

3BSE 002 417R601

Chapter 2 - Outline Description

3BSE 002 417R601 i

ii 3BSE 002 417R601

3.5.4.6 Disconnecting a Terminal .............................................. 3-36

Chapter 4 - Commissioning and Testing

Chapter 5 - Changing an Application Program On-line

3BSE 002 417R601 iii

5.1.9 Removing an Execution Unit ................................................................ 5-15

Chapter 7 - Backup and Transfer of Application Data

iv 3BSE 002 417R601

7.2.3 SRCE Volume ........................................................................................7-11

Chapter 8 - General Commands

Chapter 9 - Communication Between PC Programs and Nodes

Chapter 10 - Event Set Handling

3BSE 002 417R601 v

Appendix A - Working Example

vi 3BSE 002 417R601

1.1 General Information

1.2 Manual Organization

3BSE 002 417R601 1-1

1.4 Related Documentation

Table 1-1. Related Documentation

1.5 Release History

1-2 3BSE 002 417R601

Version 3BSE 002 417R0401: Instance names added.

Advant Controller 100 Series/AC 100 Series

Advant Controller 400 Series/AC 400 Series

1.6.1 Volumes and Segments

3BSE 002 417R601 1-3

Extension = Two ASCII characters; A-Z, a-z, 0-9

1.7 Differences between the Hardware Platforms

1-4 3BSE 002 417R601

Chapter 2 Outline Description

Input Signals Output Signals

Data Base PC Program Data Base

3BSE 002 417R601 2-1

2.2 Data Base

2-2 3BSE 002 417R601

DI Board DI Board Signals 6LJQDO

Digital Input Board No. 5

Figure 2-2. Example of Board DB Elements and Signal DB Elements

3BSE 002 417R601 2-3

2-4 3BSE 002 417R601

2.2.2 Identifying Data Base Elements

3BSE 002 417R601 2-5

User-defined Name DB Item Designation DI5.4

Figure 2-3. Identification of the Data Base Signal

2.2.2.1 User-defined Names

2-6 3BSE 002 417R601

Table 2-1. Permitted Characters

Hyphen - Do not use as first or last

Dot . Do not combine only numerals

Zero ... Nine 0 ... 9 Do not combine only numerals

Left square bracket [ USA (1)

Right square bracket ] USA (1)

Left brace { USA (1)

DI Board DI Board Signals 6LJQDO