3BSE002417R601 en AMPL Configuration Advant Controller 400 Series Reference Manual PDF

Advant OCS
with Master software
$03/&RQILJXUDWLRQ
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 GmbHs 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.
3BSE 002 417R601
3BSE001264/E
Template: 3BSE001286/E
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
1.7
Volumes and Segments ........................................................................... 1-3
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
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.9
2.8.1
Enable CONFIGURATION Mode........................................................ 2-17
2.8.2
Disable CONFIGURATION Mode ...................................................... 2-18
2.8.3
Resetting the Controller ........................................................................ 2-19
Starting Advant Controller 400 Series................................................................... 2-20

2.9.1
2.9.2
3BSE 002 417R601
User-defined Names......................................................... 2-6
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
Overview of Programmed Start ............................................................ 2-26

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
3.2.2
3.2.3
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
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
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.5
3.4.1
Dimensioning the Space for PC Programs............................................ 3-22
3.4.2
Modifying the Size of the Symbol Table .............................................. 3-23
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.4
ii
Dimensioning the Data Base................................................................... 3-1
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
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
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
4.2
4.3
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
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
System Load .......................................................................................................... 4-17

4.3.1
4.4
Blocking on Overload........................................................................... 4-18
Switching running PC Programs............................................................................ 4-19
Chapter 5 - Changing an Application Program On-line

5.1
3BSE 002 417R601
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
iii

Table of Contents
5.1.9
5.2
Removing an Execution Unit ................................................................ 5-15
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
iv
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
3BSE 002 417R601

Table of Contents
7.2.3
7.3
7.4
SRCE Volume ........................................................................................7-11
Total Backup ...........................................................................................................7-11

7.3.1
Dumping the Complete Application ..................................................... 7-12
7.3.2
Loading the Complete Application....................................................... 7-13
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
3BSE 002 417R601
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

Table of Contents
Appendix A - Working Example
1.1
vi
Working Example.................................................................................................... A-1
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 Users 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:
3BSE 002 417R601
Bold strings represent input from the user.
Normal strings represent dialog text from the Advant Controller 400 Series or the
engineering station.
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

Users Guide
Contains a description of Advant Controller 410 and its

functions.

Users Guide
Contains a description of Advant Controller 450 and its

functions.
On-line Builder
Reference Manual
Describes all On-line Builder commands. Command sets

and working methods are described as well as
command file handling aspects.
Function Chart Builder

Users Guide
Contains a description of the configuration of AMPL

application programs graphically.
AMPL Application Building

Reference Manual
Manual on the ABB MasterProgramming Language

(AMPL).
PC Elements
Series
Reference Manual
Data for all PC elements in Advant Controller 410/450.
Data Base Elements

Series
Reference Manual
Data for all data base elements in

Advant Controller 410/450.
MasterView 320
Users Guide
Complete manual for MV 320 containing descriptions,

operating instructions, linkages to PC programs,
descriptions of error messages and a table of ASCII
codes.
Source Code Handling

Reference Manual
Contains descriptions and instructions for use of AMPL

source code for application programs and data bases.
Advant Station 500 Series

Operator Station
Users Guide
Manual for Advant Station 500 Series Operator Station.
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):
3BSE 002 417R601
Volume
= Four ASCII characters; A-Z, a-z, 0-9
Segment
= One to eight ASCII characters; A-Z, a-z, 0-9
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
Data Base
Output Signals
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
6LJQDO
DI Board Signals
DI5.32
Digital Input Board No. 5

Signal 1
Digital Input Board No. 5
DI5.4
DI5.3
DI5.2
DI5
DI5.1
DI board (4.5)
Digital Input
$GGU
(8.129)
14
15
2
X1
5
6
7
8
9
27
IMPL
SERVICE
TYPE
SCANT
ACFILT
FILTA
FILTB
FILTC
FILTD
P_CATCH
> DI5.1
1
0
0
0
0
17
3
ERR
ADDR
1
4
7
25
27
11
NAME
ACT
BLOCKED
INV
TESTED
ERR_CTRL
VALUE
ERR
UPDATED
S2
Operator functions
E3
Group Alarm
12
5
6
Figure 2-2. Example of Board DB Elements and Signal DB Elements

Examples of the various categories of data base elements are given below.
1.
3BSE 002 417R601
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
(Analog Input module; S800)
AI8<nn>
AO8<nn>
(Analog Output module; S800)
DI8<nn>
(Digital Input module; S800)
DO8<nn>
(Digital Output module; S800)
<nn> stands for different S800 I/O series modules, for example AI810, DI811,AO820
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
3BSE 002 417R601
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).
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
DI board (4.5)
Addr: 0110 0100
14
15
2
X1
5
6
7
8
9
27
IMPL
SERVICE
TYPE
SCANT
ACFILT
FILTA
FILTB
FILTC
FILTD
P_CATCH
DI5.1/ VENT_OP
Digital Input
(8.129)
ERR
ADDR
17
3
> VENT_OP 1
4
1
7
0
25
0
27
0
11
0
NAME
ACT
BLOCKED
INV
TESTED
ERR_CTRL
VALUE
ERR
UPDATED
S2
Operator function
E3
Group Alarm
12
5
6
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:
2-6
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.
3BSE 002 417R601
6HFWLRQ ,GHQWLI\LQJ'DWD%DVH(OHPHQWV
Table 2-1. Permitted Characters

Name of Character
Printed
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
0 ... 9
Do not combine only numerals

and dots
Zero ... Nine

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
3BSE 002 417R601
Remark
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)
2-7
Table 2-1. Permitted Characters (Continued)

Name of Character
Printed
Character
Remark
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
Place 1
Place 2
10
20
Place n
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
3BSE 002 417R601
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
2-9
DIMENSION PC
Free space in system
Allocated PC area
Available PC area
Allocated interpreter area
555
100
10
2
kb
kb
kb
kb
100 kb
Size of PC pgm tables
(Min. 3 kb)
10
Number of PC programs
(Min. 1)
50
50
50
Number of scan places in interpreter

A
B
C
Interpreter cycle times (ms)

10
20
40
A
50 100
200
B
250 500 1000 2000
C
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:
2-10
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.
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.
> 10
50
250
5
500
2000
512
Interpreter cycle times

(ms)
10
20
40
A
Default
(ms)
50
100
200
B
Default
C
250
500 1000 2000 (ms)
Default
Slow signal scan times
Default
10
5
30
60 (s)
D
(minutes)Default
5
10
Data set communication scan times
(ms)
Default
500
DSC
(ms)
Default
2000
MVI_DSC
(ms)
Default
DSP
512
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
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)
DI (S100 I/O,
S800 I/O) (1) (2)
10
30
60
300
600
(1)
(2)
(3)
(4)
(5)
(6)
SCANT determined for each board.

IN = Interrupt; is not possible for DI8* (DI810,...
SCANT determined for each channel.
SCANT determined for each board.
SCANT determined for each channel.
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.
(7) SCANT determined for each channel.
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
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 = STOP
3 = CLEAR
4 = OFFLINE
2
1
3
4
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
Start Mode Selector:

(AUTO) 1
3
4
3 (CLEAR)
(STOP) 2
4 (OFFLINE)
(Compulsory
setting)
Actions executed
by the Controller
Resulting
Working Mode
-Install system
SW
-Clear applic.
area
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)
(AUTO) 1
Start cond.:
OPERATION
mode
Actions executed
by the Controller
Resulting
Working Mode
3 (CLEAR)
4
3
4
4 (OFFLINE)
CONFIG. mode
-Initialize and
start applic.
OPERATION
mode (P1)
-Install system
SW
-Erase applic.
CONFIG.
mode (P2)
STOPPED
mode (P3)
OFFLINE
mode (P4)
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

(AUTO) 1
Actions executed
by the Controller
Resulting
Working Mode
(Compulsory
setting)
2
3
1
4
3 (CLEAR)
4
(STOP)
2
3
4
2
1
4 (OFFLINE)
Stop
application
OPERATION
mode (P1)
CONFIG.
mode (P2)
STOPPED
OFFLINE
mode (P3)
mode (P4)
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
Start mode selector:
2
(AUTO) 1
Actions executed
by the Controller
Resulting
Working Mode
(Compulsory
setting)
3
2
4
1
3 (CLEAR)
4
(STOP) 2
1
3
4
4 (OFFLINE)
Initialize and
start
application
OPERATION
mode (P1)
CONFIG.
mode (P2)
STOPPED
mode (P3)
OFFLINE
mode (P4)
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
2
(AUTO) 1
(Compulsory
setting)
2
3
1
4
Actions executed
by the Controller
Resulting
Working Mode
3 (CLEAR) (STOP) 2
4
4 (OFFLINE)
-Install
system SW
-Erase
application
OPERATION
mode (P1)
CONFIG.
mode (P2)
STOPPED
OFFLINE
mode (P3)
mode (P4)
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:
2-20
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.
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.
PC Program for Programmed Start Control program of
Data Base Element
the process
Values of the terminals of the data base

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

programmed
restart after
power failure
Blocking of alarm
Control of ON
inputs
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

Definition of start modules
(CLEAR_C is not relevant for AC 400)
Time limits for

restart option
Restart option
after power fail
START
2
0
0
1
CONTRM
ST1/START
START
(192.1)
Start module for

programmed
restart after
power failure
NAME
PC_PGM
CLEAR_C
AUTO_C
RESTA_C
time
time
start mode
start mode
start mode
SHORT_T
LONG_T
SHT_T_ST
MED_T_ST
LNG_T_ST
MP_SP_T
CON_SP_T
SP_TIME
SP_DATE
Power failure data

Outputs can be connected
to PC
Value of restart option SHT_T_ST: Value of restart option MED_T_ST:
Value of restart option LNG_T_ST:
- AUTO,
- CLEAR,
- STOP or
- RESTART
- AUTO,
&/($5
- STOP or
- RESTART
Power down time < SHORT_T
- AUTO,
- CLEAR,
- STOP or
- RESTART
SHORT_T < Power down time < LONG_T
6+257B7
time
Power down time > LONG_T
/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
set to STOP. The controller stops after initializing.
CLEAR
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:
2-24
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.
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
START
START
2
0
1
0
NAME
PC_PGM
CLEAR_C
AUTO_C
RESTA_C
SHORT_T
LONG_T
SHT_T_ST
MED_T_ST
LNG_T_ST
PCPGM (C1, C2)
(192.1)
1
2
ON
RUN
Values of inputs and call

parameters for these
elements are not
significant.
PC2.1
CONTRM
(C1, C2)
MP_SP_T
CON_SP_T
SP_TIME
SP_DATE
1
2
3
ON
> SINGLE
RUN
MODP
Outputs of this element

must not be used.
.1
MOVE
(B, 3)
NOTE: The blockings that

are made must be
reset when the startup is complete
D=0
D=0
D=1
21
22
23
1
2
3
DAT2:VALUE
DAT2:VALUE2
DAT2:VALUE3
PC1
PC3.1
PC3.2
.2
MOVE
(B, 4)
D=1
D=1
D=1
D=1
1
2
3
4
21
22
23
24
DI1.2:AL_P_BLK
AI1.3:AL_P_BLK
AI1.4:AL_P_BLK
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:
Starting-point:
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.
Controller containing an application and executing in working mode

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

AUTO
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
setting)
2
(AUTO) 1
Actions executed
by the controller
3
4
Programmed start
Initialize and start
application
3 (CLEAR) (STOP) 2
1
4
3
4
4 (OFFLINE)
-Install
system SW
-Erase
application
A
Resulting
working mode
OPERATION
P1
CONFIG.
P2
STOPPED
-3
OFFLINE
-4
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
2
(AUTO) 1
Actions executed
by the controller
(Compulsory
setting)
2
3
1
4
3 (CLEAR) (STOP) 2
4
3
4
4 (OFFLINE)
Programmed start
Initialize and start
application
A
Resulting
working mode
OPERATION
P1
CONFIG.
P2
STOPPED
-3
OFFLINE
-4
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
Spare area in data base
>
556 kb
133 kb
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:
3-2
>
<
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.
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
Allocated data base
4801 kb
114 kb
905 kb
> 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>
3BSE 002 417R601
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.
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
Allocated data base
4801 kb
114 kb
905 kb
> 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

Allocated data base
4801 kb
114 kb
905 kb
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

Allocated data base
4801 kb
114 kb
905 kb
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 Users Guide.
DIMENSION DATA BASE

Allocated data base
4801 kb
114 kb
905 kb
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

Allocated data base
4801 kb
114 kb
905 kb
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
Allocated data base
4801 kb
114 kb
905 kb
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

Allocated data base
4801 kb
114 kb
905 kb
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

Allocated data base
556 kb
133 kb
1 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 bases 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,

implementation with
SC520 and CS513
10 000 (number of SC520)
Advant Controller 450,

implementation with
SC510 and CS513
4 000 (number of CS513)
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
MVI Data Set (MS)
148 (number of MS) (3)
Text Data Set (TS)
96
MVI ports
122 (number of configured MVI ports) (4)
Time-tagged data (TTD)
6000 + N1 (4P1 + 20) +

N2 (4P2 + 20) +
Nx (4Px + 20)
(number of DSP)
(number of TS)
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
A15 =
PIDCONA
(number of data base elements that the user

is creating)
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
(logical file, logical record)
Item Designation
Default Values
To go to next
Element, use
the directive >>
<1
1
DSDI 110
INTERRUPT
0
10
10
10
10
NO
14
15
2
X1
5
6
7
8
9
27
DI1
DI board (4.1)
Addr: 0110 0100
IMPL
SERVICE
ERR
TYPE
ADDR
SCANT
ACFILT
FILTA
FILTB
FILTC
FILTD
P_CATCH
Address to be
Strapped on Board
17
3
0
96
? >>
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.
3BSE 002 417R601
>>
Moves to the next DB element.
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.
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
1
DSDI_110
INTERRUPT
0
10
10
10
10
NO
? >>
14
15
2
X1
5
6
7
8
9
27
IMPL
SERVICE
TYPE
SCANT
ACFILT
FILTA
FILTB
FILTC
FILTD
P CATCH
ERR 17
3
ADDR
0
0
Proceed to next element
Figure 3-12. Parameters of the First DI Board
Signal file
record
Item designation
DI1.1
Digital Input
(8.1)
>DI1.1
1
0
0
0
0
? >>
1
4
7
25
27
11
NAME
ACT
BLOCKED
INV
TESTED
ERR CTRL
S2
Operator functions
E3
Group Alarm
VALUE
ERR
UPDATED
12
5
6
0
0
0
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
0
0
0
0
1
4
7
25
27
11
NAME
ACT
BLOCKED
INV
TESTED
ERR CTRL
S2
Operator functions
E3
Group Alarm
VALUE
ERR
UPDATED
12
5
6
0
0
0
and so on for all
signals of the
board
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.
3BSE 002 417R601
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.
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:
3-16
<<
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>.
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

data base will be
printed
/'%'6(/ $//
element type
All elements of a given

type will be printed
/'%'6(/ ',&
Lists all DI calculated.
/'%'6(/ $,
Lists all AI boards with

associated signals.
A specific element will

be printed
/'%'6(/ ',&
Lists the element with

item reference DIC3.
element identity
/'%'6(/ $,
Lists the first AI board and

associated signals
A number of elements
of a given type will be
printed
/'%'6(/ ',&!
name
The element with the

name NAME will be
printed
/'%'6(/ 02725
Lists the element with the

name MOTOR.
wildcard *
The wildcard character

will be replaced by any
possible combination
of characters. Those
elements that fit will be
printed. The wildcard
* is allowed at the
end of the selection
string only.
/'%'6(/ $,
Lists all AI boards (S100)

and AI modules (S800)
group
Lists DIC3, DIC4...DIC7.

The first element specified
must exist.
/'%'6(/ $
Lists all elements starting

with A, e.g. AI, AO, AIPT,
AIC
The following three parameters control page numbering:

Table 3-4. Other Parameters of Command LDBD
Parameter
3-18
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.
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.
3BSE 002 417R601
page_interv:
According to the corresponding LDBD parameter.
EXP:
Keyword providing expanded output including node, logical file and logical
record.
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:
3-22
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 -99x 99.
3BSE 002 417R601
6HFWLRQ 0RGLI\LQJWKH6L]HRIWKH6\PERO7DEOH
DIMENSION PC
Allocated PC area
Available PC area
Allocated interpreter area
4
5
6
100 kb
Size of PC pgm tables
555
100
10
2
kb
kb
kb
kb
(Min. 3 kb)
(Min.1)
10
Number of PC programs
50
50
50

A
B
C
Interpreter cycle times (ms)

40
A
10
20
B
50
100
200
250
500 1000 2000
C
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
IMPOSSIBLE
#067$%6
MINIMUM SIZE
MAXIMUM SIZE
SYMBOL TABLE
SYMBOL TABLE
3-24
DISC SPACE: TRY COMPRESS; OTHERWISE MODIFICATION
(Symbol-table already used) : 60

(Available disc space)
: 225
SIZE (BLOCKS) = 85 =
SUCCESSFULLY MODIFIED.
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
EBM
DIBM
PC Program in BLOCKED
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:
3-26
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.
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
PC1 PCPGM
IS PC 1.1.3
PC1 PCPGM
PC1 PCPGM
PC1 PCPGM
.1 CONTRM
.1 CONTRM
.1 CONTRM
.1
.2
.3
.4
.5
.6
.7
.1
.2
.3
.4
.5
.6
.1
.2
.3
.7
.4
.5
.6
.2
.2
.2
.1
.2
.3
.4
a) Existing PC
program structure
.1
.2
.3
.4
b) Addition to
PC program
IS PC 1.1; END
.1 CONTRM
.1
.2
.3
.4
.5
.6
.7
.2
.1
.2
.3
.4
c) Addition to
PC program
.1
.2
.3
.4
d) Addition to
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 ?
PC1.1.1
PC1.1.2
PC1.1.3
CONTRM(250)
? AND(3)
? OR(2)
? !
Figure 3-18. Example of Inserting PC Elements with Graphic Presentation

3BSE 002 417R601
>G
Changes from non-graphic to graphic presentation.
>NG
Changes from graphic to non-graphic presentation.
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&
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
3BSE 002 417R601
Processes the terminal with assigned variable_name
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
D=0
>?
1
2
3
CONNECTIONS MODIFIED
:2
IB ?
:2 d=0
:3
IB ?
:3
&
20
<0>-
ELEMENT BEING DISPLAYED : PC1.1.1
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:
3-32
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.
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

(the value is to be assigned to more than one
input)
MD=value
Constants
CD=value
Constants used several times (the constant is

to be assigned to more than one input)
MCD=value
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:
3-34
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.
3BSE 002 417R601
Table 3-7. Allowed Characters

Name of Character
3BSE 002 417R601
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
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
Must not be used as

first character
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.
3-36
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.
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:
Item Designation
Terminal Number
#&3&
Local data: 99%
Element Name
PC1.1.2
TON
:1
I
IB
PC1.1.1:20
1
:1
:2
TD IT
?
:2
'
PC Diagram Page
:5
0
OB
where connected
Data Type
Terminal can be found
:5
PC1.1.1:1
:6
TE OT
Connected Terminal
:6
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
17
#LS PC4.1.1;5
PCD-PAGE :
PC4.1.1
:1
:2
:20
16
MUL (R,2)
IR
IR
OR
=AI1.2
D=1.040
=AI1.2 G
liter
=AO1.2
1
:1
:10
:11
:12
:20
:21
COMP-R (2,2)
I
IR
HHYS
IR
H1
IR
H2
IR
I<H1
OB
I>=H1
OB
:22
I<=H
OB
:30
:31
:32
:40
:41
:42
LHYS
L1
L2
I>L1
I<=L1
I<=L2
IR
IR
IR
OB
OB
OB
PC4.1.2
15
14
13
PC4.1.1:20
D=100.000
H_LIM_1
H_LIM_
liter
liter
liter
liter
1
D=700.000
D=900.000
ABOVE_H_LIM_1
=DO1.5
ABOVE_H_LIM_2
=DO1.5 P
2
D=100.000
D=100.000
D=200.000
=AO1.2 P
PC4.1.2:I
8
9
10
PC4.1.3:2
N
liter
liter
liter
=DO1.4
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
3-40
Connections to data base ...................9
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
designation and
terminal number
Details of
operational
parameter or
constant
Command
given with
variable name
Details of:
PC program
Variable name
Page number and

identity of terminal
Data type
#LV PC1.1.1:1
PC1,START
MD=1
1
1
2
2
2
PC1.1.1:1
PC1.1.1:2
PC1.1.2:2
PC1.1.3:R
PC1.1.3:L
#LV START
PC1,START
MD=1
1
1
2
2
2
PC1.1.1:1
PC1.1.1:2
PC1.1.2:2
PC1.1.3:R
PC1.1.3:L
1
2
PC1.1.1:20 S
PC1.1.2:1
PC4:ON
PC6.7.9:R
PC7.2.1.3:2
PC4:ON
PC1
PC6
PC7
PC1
PC2
Command
given with data
base identity, the
DB terminal
VALUE
#LV =VENT OPEN
is used
=VENT OPEN
by default
=DI5.3
=8.131:12
Information
on source
#LV PC4,=VENT OPEN

=VENT OPEN
=DI5.3
=8.131:12
B
Command
given with database identity, the
DB terminal
ERR is used
#LV =DO1.16:5
=AdjustControl
=DO1.16
=9.16:5
B
Up to three alternative identities

for a data base terminal are shown
The connections of a data base terminal are

shown in detail for the PC program
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.
1
0
Call Parameters:
1
2
PC2
PCPCM(1.1)
ON
RUN
R
1
2
3
.1
CONTRM(1.1.)
ON
RUN
SINGLE
MODP
R
Cycle Time Parameter
Position Parameter
1
0
0
PC Variable
5
6
.1
Function Parameter
F=1
F=1
F=1
D=2
CD=11
?
?
F1
F2
F3
1
2
3
4
PRINT(1,1,72)
BUSY
FIRST
REPNO
LAST
ERR
FF
NODE
NETW
PRID
ACT
D=FAULT REPORT
11
TEXT1
Operational
Parameter
Constant
5
6
7
1 & 20
?2
Figure 4-2. Example with the MV Command
Table 4-1. Values that can be handled by the MV Command

3&9DULDEOHV
Value can be
read/
modified in
service
Operational
parameters
FDQEHUHDG
\HV
FDQEHFKDQJHG
\HV
from
element
output
from
element
input
connected
to data
base
\HV
\HV
QR
QR
'HVLJQ3DUDPHWHUV
Constants
Call parameters
Function
parameters
\HV
\HV
\HV
QR
F\FOHWLPHSDUDPHWHUV for
PCPGM, CONTRM, MASTER
and SEQ under the same PC
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
.3
.2
.19
.20
.21
FUEL
.1
.2
.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:
4-10
<,>
The angle brackets < and > work in the same way as in the MV (Modify
Value) command.
Terminates the command.
Deletes the name.
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.
2.
3.
3BSE 002 417R601
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.
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.
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.
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:
4-12
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 valuePC 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
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
2.307
0.000
3.434
1.762
0.400
1
0.000
1000.000
-1000.000
1
2
3
4
5
6
7
8
9
RAMP
I
O
STEP+
O=HL
STEPO=LL
SLOPE+ ERR
SLOPEBAL
BALREF
OHL
OLL
10
11
12
13
0.000
0.000
0.000
0.000

?IV
Figure 4-4. Screen Display on Updating Variable Values
3BSE 002 417R601
4-13
Example:
#*(3&'3&
? *6
PC1.1.5
0
1
1
2
&
20

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

?
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.
0
0 1
2
1 1
1
2
.1
1
20
0 1
1 2
.3
&
20
1
0 1
2
.2
&
20
0
1 1
2
.4
1
.5
&
20 0
20
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
1
2
&
20

?
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
0
1
2
20

?
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
=AI1.5
=AO1.3
=DO1.1
PC4.1.3:5
=AI1.1
PC4.1.2:21
=AO1.1
R
R
R
R
R
R
R
R
85.600
32.800
0.000
0
1
0.000
1
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:
4-18
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.
3BSE 002 417R601
6HFWLRQ 6ZLWFKLQJUXQQLQJ3&3URJUDPV
4.4 Switching running PC Programs

DANGER
Switching the executing PC program may affect the process as soon as the change is
carried out. Do not switch the execution from one PC program to another unless you are
thoroughly familiar how the process will be affected by the change.
In Advant Controller 400 it is possible to have a PC program executing which reads its input
values to PC elements from the data base and therefore from the process itself but without
writing the PC element output to the data base; this means the output values are blocked.
This is a useful function if you want to test and tune your application program. If you are
satisfied with the new PC program you can switch over from one PC program to another which
means that writing the output values of the original program is blocked and writing of the output
values of the new program is deblocked.
The Switch Blocking commands are used to perform a switch over from one PC program to
another. It allows you to test a modified version of a PC program with the real process.
If you want to load, test and activate a modified PC program (for example PC99) you must
perform the following steps:
1.
Create the modified version of the PC program in source code format.
2.
Translate the source code of the modified PC program.
3.
Set the "Inhibit" flag for the modified program which disables resetting the PC element
output terminals
(SEIF PCnn, for example set the flag for PC99: SEIF PC99)
4.
Disable the build mode for the modified PC program

(for example DIBM PC99)
5.
Start the modified program with all DB outputs blocked (BL DB,PCnn,
for example BL DB,PC99).
6.
Test and tune the new version of the program.
7.
Use "SWBL" to let the new program takeover. (SWBL DB,PCnn/PCmm,

for example switch over from PC1 to PC99: SWBL DB PC99/ PC1)
DANGER
The modified version of the new application program is only blocked for
database output. PC elements writing directly to I/O devices cannot be
prevented from writing using the command "BL DB,PCnn.".
Note that the CPU load increases during the period where the two programs
are running in parallel. If the controller get into an overload situation, the
process be disturbed and the controller may stall.
3BSE 002 417R601
4-19
4-20
3BSE 002 417R601
6HFWLRQ 0RGLI\LQJ3&3URJUDPV2QOLQH
Chapter 5 Changing an Application Program On-line
DANGER
Changing an executing PC program or the data base may affect the process as soon as the
change is carried out. Do not make changes in PC programs that are executing or in the data
base 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.
5.1 Modifying PC Programs On-line

The ability to make modifications in PC programs on-line is extremely valuable in situations
where a stop in production would be very expensive.
You can make on-line changes to a PC program according to three levels of ambition:
1.
Modification of a PC program that is in BUILD mode while other PC programs are

executing.
2.
Modification of a blocked control module while the rest of the PC program is executing.
3.
Modification of executing PC elements.
The procedure to modify on the first complexity level is described in Section 3.5, Entering and
Editing PC Programs. This chapter describes how to change the PC program on the second and
third levels.
Changes in a PC program (EXECUTION mode) require the modify permission, i.e., MODP = 1
of the execution-controlling PC elements in that PC program.
NOTE
When the Advant Controller 400 Series is in CONFIGURATION mode, the PC
program can only be modified when the PC program is in BUILD mode.
5.1.1 Inserting PC Elements

The dialog begins with a warning that the PC program in question is executing.
When PC elements with function parameters are to be inserted, a dialog to define the value of
these is performed. (Examples of PC elements with function parameters are TEXT and PI.)
A letter F before the terminal in question in the data sheets shows that a PC element has
function parameters. You can interrupt this dialog with the Ctrl-Break command.
3BSE 002 417R601
5-1
&KDSWHU &KDQJLQJDQ$SSOLFDWLRQ3URJUDP2QOLQH
Example:
#,63&
Local data: 100%
PC1.1.1 ? 7(;75
TEXT (R,1,1,6)
:F1 FORM1 F1 F=?
:F1
:F2 FORM2 F1 F=?
:F2
PC1.1.2. ?
#
Execution-controlling PC elements (for example, CONTRM, MASTER or SEQ) are inserted in
the blocked state and, as a result, PC elements inserted under these are not executed before
CONTRM, etc., are deblocked (command DBL). Other PC elements inserted are influenced by
their execution-controlling PC element: if this is not blocked, execution of the inserted PC
elements starts directly.
Remember that the position of the PC element in the PC program structure influences the result
of the PC program, i.e., for input data to a PC element to be fresh, the PC element that calculates
these input data must be positioned before the PC element using the data.
5.1.2 Connecting PC Elements

The dialog begins with a warning that the PC program in question is executing. After this,
the commands C and CU operate as though the PC program was in BUILD mode.
The following take place upon disconnection of terminals in executing PC programs.
When outputs, which are tied to the data base, are disconnected, the corresponding data
base values stay unaffected, i.e., they are not changed until some other PC elements change
them. (Some values in the data base are also cleared when the Advant Controller 400
Series is switched into CONFIGURATION mode.)
Upon disconnection of outputs that are connected to the inputs of other PC elements,
the inputs of these PC elements are reset.
When inputs are disconnected, the values of these inputs are reset.
When PC elements with function parameters are to be connected, a dialog to define these values
is performed.
5-2
3BSE 002 417R601
6HFWLRQ 'HOHWLQJ3&(OHPHQWV
Example:
Example of dialog for modification of function parameters in TEXT PC element
#&3&
WARNING: PCPGM is not in BUILD mode: CONTINUE? (Y/N)<
Available space in area PC: 98 kbyte, DB connection: 99%,
Local data: 99%
PC1.1.2
TEXT (B,2,2,2)
:F1 FORM1
FI
F=6
MODIFICATION STARTS RESET EXECUTION (WARM START) OF PC ELEMENT!
:F1
OK TO RESET EXECUTE PC ELEMENT (WARM START), Y/N? <
:F2 FORM2
FI
F=6
MODIFICATION STARTS RESET EXECUTION (WARM START) OF PC ELEMENT!
:F2
OK TO RESET EXECUTE PC ELEMENT (WARM START), Y/N? <
:1
EN
IB
D=0
:1

#
5.1.3 Deleting PC Elements

The dialog begins with a warning that the PC program in question is executing.
Upon modifications on-line, the command DS works as though the PC program were in BUILD
mode, with the following exceptions:
You cannot delete an entire PC program. (For example you cannot give the command DS
PC2.)
You cannot delete a STEP in a sequence or an interval containing a STEP PC element.
When PC elements are removed, the following happens to the terminal of the outputs (the data
base or another PC element):
Removal of PC elements, which are tied to the data base, does not affect the data base
values concerned, i.e., the values are not changed until some PC elements change them.
(Some values in the data base are also cleared when the Advant Controller 400 Series is
put into CONFIGURATION mode.)
The input of a PC element that is using a PC element which is being deleted is reset and
can be reconnected to another PC element or to the data base. The inputs of these PC
elements can be found with CU for the PC program in question.
If instance names are assigned to a PC element this name is removed, too.
3BSE 002 417R601
5-3
5.1.4 Important Notes for On-line Changing

As mentioned at the beginning of the chapter, modifications to PC programs on-line should be
divided up into three levels of complexity:
1.
Modification of a PC program that is in BUILD mode while other PC programs are

executing.
2.
Modification of a blocked control module while the rest of the PC program is executing.
3.
Modification of executing PC elements.
The first two levels are easy to handle, but the third level is more advanced and requires a deep
knowledge of the process.
For the second and third levels, remember that the commands themselves and the modifications
to the PC program affect the load on the CPU. Where the CPU is highly loaded, therefore, PC
programming on-line should be avoided.
5.1.4.1 Modifying a Blocked Control Module

If it is possible to block a control module without critical process disturbance. You can use
different arguments for the blocking command (BL), which are described in Section 4.2.2,
Blocking the PC Program Execution. During blocking, the data base for the outputs of the
control module will, of course, not be updated.
For example:
1.
Block the control module with BL DB, PC1.1 (BLock Data Base).
2.
Make the modifications in the control module.
3.
Use the CU (Connect Undefined) command (Section 3.7, Connecting Unconnected

Inputs) to check that all inputs are connected.
4.
Check that the modification is as intended, for example, by using the GEPCD (GEnerate
PC Diagram) command (Section 4.2.7, Displaying a PC Element with Variable Values).
5.
Deblock the control module with the DBL (DeBLock) command (see Section 4.2.3,
Deblocking the PC Program Execution).
You can also create a blocked copy of the control module on which to make the modifications.
It is important to realize that the copy will cold start when it is deblocked. This can cause bumps
in the output signals.
5-4
3BSE 002 417R601
6HFWLRQ ,PSRUWDQW1RWHVIRU2QOLQH&KDQJLQJ
5.1.4.2 Modifying Executing PC Elements

Modifications in a running PC program require a deep knowledge of the process. They should
be made only if you are absolutely sure of what will happen to the process as a result of the
modification.
When a new PC element is being inserted, all inputs of the PC element must always be
connected before the outputs of the PC elements are connected.
To achieve bumpless transmission of the signal upon changing over, change-overs must be
made in different ways depending on the switching situation (see Table 5-1).
Switching PC element SW-C gives bumpless transmission on change-over and ensures that
all users have the same input signal and that the new signal has been calculated at
connection.
Table 5-1. How to use the SW-C PC Element in various Switching Situations
6ZLWFKLQJ6LWXDWLRQ
0HWKRG
Use a SW-C switching element temporarily.
Insert the element in the PC program directly
after the element where the new signal has
been calculated; see example 1.
Connection to data base
The source
Connection to Connection to The source
PC element:
one or more
PC elements PC elements
PC elements: are located in: are executed
under:
,03257$17
In Cases 1, 2 and 3, the switching must
begin at the input of the source PC element
without first disconnecting the old signal.
Case 1
One PC
element
Other
execution unit
Same
interpreter
Connect the new signal directly from the input

on the source PC element. Check that the new
signal has been calculated before you switch
over.
Case 2
Several PC
elements
Same or other
execution unit
Same
interpreter
Use a SW-C switching PC element temporarily

as shown in example 2 below, case 2.
Case 3
One or more
PC elements
Other
execution unit
Other
interpreter
Use a SW-C switching PC element temporarily

as shown in example 2 below, case 3.
3BSE 002 417R601
5-5
Example 1: Connection to the Data Base

In the first example, we are required to replace an AND (2) element connected to the data base
with an AND (3) element.
1.
First, connect the old and new output signals to the SW-C element. Select ACT so that the
old signal is switched to the output.
.1
1
2
&
20
DO1.1

.6
.5
1
2
3
&
20
SW-C
(B,1)
D=1 1 ACT
11
12
13
Figure 5-1. On-line change of a DB Connection using the SW-C PC Element

2.
Connect the output of SW-C to the data base.
3.
Disconnect the old link to the data base.

.1
1
2
&
20
.5
1
2
3
&
.6
20
SW-C
(B,1)
D=1 1 ACT
11
12

P
13
DO1.1
Figure 5-2. Example 1 using the SW-C PC Element (continued)
5-6
3BSE 002 417R601
4.
Select ACT so that the new signal is connected to the data base.
5.
Connect the new signal directly to the data base (not via the SW-C element).
.1
1
2
&
20

.5
1
2
3
&
20

=DO1.1
=DO1.1
.6
SW-C
(B,1)
D=0 1 ACT
11
12
13

6.
3BSE 002 417R601
Remove the SW-C element and the old AND element.
5-7
Example 2: Switching Case 2

In the example, the AND (2) element should be replaced by an AND (3) element. The two
source PC elements are located in the same execution unit.
1.
First, connect the old and new output signals to the SW-C element. Select ACT so that the
old signal is switched to the output.
.1
1
2
&
20
.5
1
2
3
&
.6
SW-C
(B,1)
ACT
20
D=1
1
11
12
13
.1
.3
1
2
20
Figure 5-4. Example 2 using the SW-C PC Element

2.
Connect the input of the using PC elements, one at a time, to the output of the SW-C
elements.
3.
When all signals have been switched, select ACT so that the new signal 5:20 is connected
to the output.
.1
1
2
&
20

.5
1
2
3
&
20
D=0
.6
1
11
12
.1
SW-C
(B,1)
ACT
1
13
.3
1
2
20
5-8
3BSE 002 417R601
4.
Connect all using PC element inputs, one at a time, directly to the new signal.
.1
1
2
&
20
.6
.5
1
2
3
&
SW-C
(B,1)
ACT
20
D=0 1
11
12
13
.1
1
1

.3
1
2
20

5.
3BSE 002 417R601
5-9
Example 3: Switching Case 3

In the example, an AND (2) element should be replaced by an AND (3) element, as in case 2.
But in this example, the signal from the new (3) element in control module PC1.2 source must
be linked to two (receiving) PC elements (PC1.1.1 and PC1.1.2) in another execution unit,
PC1.1. The two execution units are under different interpreters. To ensure that all receiving
elements have the same signal, a SW-C element is used and will be executed before one of the
receiving elements is executed.
1.
Insert SW-C element PC1.1.7 before the receiving elements.
2.
Connect the old and new output signals to the SW-C element. Select ACT so that the old
signal is connected to the output.
.1
1
2
3
1
0
0
CONTRM(20.2.0)
ON
RUN
MODP
SINGLE
R
5
6

D=1
1-PC1.2.1:20
1-PC1.2.2:20
.7
SW-C
(B,1)
ACT
1
11
12
13
Signal
Receiving
.1
1
.2
=DI1.10
1
2
20
EXECUTION ORDER: 7 1 2
.1
.2
1
0
0
1
2
3
CONTRM(2000.1.0)
RUN
ON
MODP
SINGLE
R
5
6
.1
=DI1.1
=DI1.2
G
G
1
2
&
20
P-1
20
P-1
.2
=DI1.3
1
2
3
&
Figure 5-7. Example 3 using the SW-C PC Element
5-10
3BSE 002 417R601
3.
Connect the inputs of the using elements to the outputs of SW-C.
4.
When all signals have been reconnected and the input of the SW-C element for the new
signal has the correct value (check with GEPCD, for example) change ACT so that the
new signal is switched to the output.
.1
1
2
3
1
0
0
CONTRM(20.2.0)
ON
RUN
MODP
SINGLE
R

.7
SW-C
(B,1)
D=0 1 ACT
11
12
1-PC1.2.1:20
1-PC1.2.2:20
=DI1.10
5
6
.1
1
1
13
.2
1
2
20
.1
.2
1
0
0
1
2
3
CONTRM(2000.1.0)
RUN
ON
MODP
SINGLE
R
5
6
.1
=DI1.1
=DI1.2
G
G
1
2
&
20
P-1
20
P-1
.2
=DI1.3
=DI1.3
1
2
3
&
3BSE 002 417R601
5-11
5.
Connect the inputs of all using PC elements directly to the new signal.
6.

.1
1
0
0
1
2
3
CONTRM(20.2.0)
ON
RUN
MODP
SINGLE
R
5
6

.7
D=1
1-PC1.2.1:20
1-PC1.2.2:20
SW-C
(B,1)
ACT
1
11
12
13
.1
1
.2
=DI1.10
1
2
20
.1
.2
1
0
0
1
2
3
CONTRM(2000.1.0)
RUN
ON
MODP
SINGLE
R
5
6
.1
=DI1.1
=DI1.2
G
G
1
2
&
20
P-1
20
P-1
.2
=DI1.3
1
2
3
&
5.1.5 Adding a Step in a Sequence

You can add a new step in a sequence. Proceed as follows to prevent the sequence from locking:
5-12
Make sure that the condition for the new step to be run is not satisfied before the step is
inserted, connected and ready.
Prevent the previous step from being run, i.e., set COND=0 for the step and prevent any
jumps (call parameter C2 of the step PC element) to the step. Jumps can be avoided by
preventing the execution of the step from which the jump starts.
3BSE 002 417R601
6HFWLRQ $GGLQJD6WHSLQD6HTXHQFH
Example:
You have a sequence containing three already existing steps, step 1, step 2 and step 3
(see Figure 5-10). Insert a new step 4 between step 2 and step 3.
.1
STEP(0,0,0,0,0,0,0,0)
F=0
F1
1
STEPNO
COND
RUN
.2
STEP(0,0,0,0,0,0,0,0)
F=0
F1
STEPNO
COND
RUN
.3
STEP(0,0,0,0,0,0,0,0)
F=0
F1
STEPNO
COND
RUN
Figure 5-10. Example of how to add a Step in a Sequence
1.
Prevent step 2 from running (set terminal COND=0).
2.
Check that step 2 does not run (e.g., with the GEPCD command).
3.
Insert the new step 4 below step 2.
4.
Insert and connect the subordinated elements of step 4.
5.
Remove COND=0 of step 2 and reconnect the COND terminal as it was before.
6.
Connect the COND terminal of step 4.

NOTE
The name of a step is defined as its item designation. The succession of the step
execution is always the execution order of the step elements in a PC program,
if no jumps are implemented (call parameter C2). In this example, the resulting
execution order is: Step 1, step 2, step 4, step 3.
The terminal STEPNO is an alternative way to name a step. This takes place if
you are using jumps (call parameter C2). STEPNO works then as a jump address
instead of giving an item designation.
3BSE 002 417R601
5-13
5.1.6 Removing a Step in a Sequence

It is not permissible to remove a step in the sequence on-line. Instead, the contents of the step
can be deleted and the step short-circuited, as in the following example. The short-circuited
step then gives the stepping condition for the next step. This causes step-changing to be delayed
by the length of one cycle.
Example:
Remove step 4.
.1
STEP(0,0,0,0,0,0,0,0)
F=0
F1
STEPNO
COND
RUN
.2
STEP(0,0,0,0,0,0,0,0)
F=0
F1
1
STEPNO
COND
RUN
.4
STEP(0,0,0,0,0,0,0,0)
F=0
F1
1
STEPNO
COND
RUN
.3
STEP(0,0,0,0,0,0,0,0)
F=0
F1
1
STEPNO
COND
RUN
Figure 5-11. Example of how to Remove a Step in a Sequence
5-14
1.
Stop execution of step 4 (set terminal COND=0).
2.
Remove the PC elements under step 4.
3.
Connect the COND condition for step 3 to the COND input terminal of step 4.
4.
Connect the COND input terminal of step 3 to the RUN output terminal of step 4.
3BSE 002 417R601
6HFWLRQ $GGLQJD6ODYH0RGXOH
5.1.7 Adding a Slave Module

Proceed as follows to add a slave module to a PC structure:
1.
If possible, set the ON input of the MASTER input to 0 to reduce the load. If this is not
possible, proceed directly to the next step.
2.
Add the new slave module and its PC elements.
3.
Connect the PC elements of the slave module.
4.
Set the ON input of the MASTER PC element as it was before step 1.
5.1.8 Removing a Slave Module

Proceed as follows to remove a slave module in a PC structure:
1.
If possible, set the ON input of the MASTER input to 0 to reduce the load. If this is not
possible, proceed directly to step 2.
2.
Remove the slave module.
3.
Set the ON input of the MASTER PC element as it was before step 1.
5.1.9 Removing an Execution Unit

Control module PC1.6 below is to be removed.
1
D=0
0
0
.6
CONTRM(40.4.0)
RUN
1 ON
SINGLE
2
MODP
3 R
5
6
Figure 5-12. Example of how to remove an Execution Unit
3BSE 002 417R601
1.
Set the on input of the control module head to 0.
2.
Remove the control module with the command DS PC1.6.
5-15
5.2 Modifying the Data Base On-line

5.2.1 General Information
The data base in the Advant Controller 400 Series consists of a number of data base elements.
Each one of these is described in the Data Base Elements Advant Controller 400 Series
Reference Manual.
Some examples of on-line changes:
Change of data base parameter, e.g., the scaling of an analog signal
Change of board type
Addition or removal of modules and signals to/from the data base.
Since you can change the data base on-line, it is important that PC programs have access to the
data base for read and write operations. The accessibility of the data base parameters for read
and write operations is described in the Data Base Elements Advant Controller 400 Series
Reference Manual.
The possibilities for changing the data base on-line are wide ranging. Essentially, the only
limitation is that data base redimensioning cannot be done on-line. A more detailed description
of possible on-line changes follows.
5.2.2 Modifying an I/O Module On-line

5.2.2.1 Modifying a Data Base Parameter
Wherever applicable, the data base parameters for modules and signals are divided into three
functional parts:
Basic functions
Limit value functions
Operator station functions.
Normally, you can change the parameters for the basic and limit value functions using the MDB
(Modify Data Base) command or by connection to a PC program.
The part containing the operator station parameters reflects the status of the module or the signal
as presented to the process operator. Consequently, these parameters should not be changed by
way of a PC program. However, NORM_TR, which controls the event handling of the signal, is
an exception.
5-16
3BSE 002 417R601
6HFWLRQ &KDQJLQJ&RQWUROOHUVDORQJ$GYDQW)LHOGEXV
5.2.2.2 Modifying an I/O Board Type

You can change process signal board type, for example AI, if the new board contains as many
signals as the old one. If the change also implies a change in the number of signals, you must
first delete the old board from the data base before the new board is installed. Before
commencing to delete a board, see Section 5.2.2.4, Deleting I/O Modules and Signals.
NOTE
You cannot change the module type for Series 800 I/O modules (for example DI820); you have
to delete the instance and create a new one with the new call name (for example DI821).
5.2.2.3 Adding I/O Modules and Signals

New modules and signals require additional space in the data base. If the dimensioning is
adequate, you can create and activate the new module using the command CRDB (CReate Data
Base) otherwise the create procedure fails.
5.2.2.4 Deleting I/O Modules and Signals

Before deleting DB elements from the data base, it is important that you be aware of the
following.
PC programs contain direct references to the data base. They are not automatically made
aware of such deletions.
The functions for the Advant Station 500 Series Operator Station of the Advant
Controller 400 Series (performed by the option module) create direct references to
terminals in the data base that are included on any display of any operator station in the
system. There is no automatic check of any on-line deletion from the data base.
Since neither the PC programs nor the Advant Station 500 Series Operator Station discover
deletions from the data base, both functions continue to address nonexisting DB elements.
If a new DB element is created, it may fall into the slot vacated by a deleted DB element.
This may lead to inadvertent reading from, or writing to, the new DB element.
When deleting I/O modules with I/O signals, it is recommended that you follow this procedure:
1.
Make sure the module and its signals are not used by any PC program or Advant
Station 500 Series Operator Station display. If it is, delete all remaining references to it.
You can use the LDBD/XREF command to identify any connection between the data base
and the PC programs.
2.
Delete the module and its signals using the command DDB (Delete Data Base).
5.2.3 Changing Controllers along Advant Fieldbus 100

For every Advant Fieldbus 100 there is a data base element which identifies the fieldbus
interface. Be aware that a change in any of these DB elements may directly affect other DB
elements, e.g., DSP elements.
Fieldbus interface elements cannot be deleted; they are deactivated by setting the ACT terminal
to 0.
3BSE 002 417R601
5-17
5.2.4 Changing Controllers along MasterFieldbus

For every controller along the MasterFieldbus, there is a data base element. Be aware that a
change in any of these DB elements may directly affect other PC elements, e.g., COM-MP51
elements.
5.2.5 Changing the Data Base Part of Functional Units On-line

The following data base elements are parts of functional units:
AIC, AOC, DIC, and DOC
GENBIN, GENCON, GENNOV, GENUSD, MMCX, and SEQ
MANSTN, VALVECON, MOTCON, PIDCON, PIDCONA, and RATIOSTN.
The following changes are possible:
Create new boards and signals using the CRDB command.
Delete boards using the DDB command. Make sure that the signals removed are not
referenced by any PC program or Advant Station 500 Series Operator Station (see
Section 5.2.2.4, Deleting I/O Modules and Signals).
Change parameters using the MDB command or by connection to PC programs.

The possibilities available for connection of the various DB elements are described in the
Data Base Elements Advant Controller 400 Series Reference Manual.
5.2.6 Changing other Data Base Elements On-line

Clock Synchronization
The parameters of the data base element CLOCK_SYNCH are all changeable on-line.
DS
New DS DB elements (Data Set) require dimensioned space in the data base dimensioning and
may be added. On the other hand, a DS DB element cannot be deleted on-line. You can modify
existing DS DB elements, e.g, new references to DAT DB elements can be added. DS DB
elements are modified as follows:
5-18
Set ACT to false.
Make the change (MDB).
Set ACT to true.
3BSE 002 417R601
6HFWLRQ &KDQJLQJRWKHU'DWD%DVH(OHPHQWV2QOLQH
DAT
New DAT DB elements require dimensioned space in the data base dimensioning.
Create new DAT DB elements using the CRDB command.
Modify existing DAT DB elements using the MDB command.
Remove existing DAT DB elements using the DDB command. Make sure that the
elements removed are not referenced from any PC program or Advant Station 500 Series
Operator Station (see Section 5.2.2.4, Deleting I/O Modules and Signals). A DAT DB
element can be referenced by different sources or destinations.
PC programs
Advant Station 500 Series Operator Station
MasterView 320
EXCOM.
If these references are not deleted, you may encounter symptoms as described in Section
5.2.2.4, Deleting I/O Modules and Signals.
Misc. Boards
Changes to the data base for Misc. boards affect the system status displays for the node
concerned the next time they are shown by the Advant Station 500 Series Operator Station.
MasterView 320
The data base for MasterView 320, TERMPAR, TERMGEN, TERMDIS, TERMDYN,
TERMREF, and TERMSTR is not intended to be changed in any way other than through the
MasterView 320 dialog. For a description of an exception to this rule, see the MasterView 320
Users Guide.
PRINT, EXCOM, TERM
PRI_01, XCOM_1, XCOM_2, XCOM_3, TERM_1, TERM_2, TERM_3, and TERM_4 are
system DB elements of the Advant Controller 400 Series data base. Consequently, you cannot
add or delete any instances. It is possible, however, to change the parameters of these data base
elements on-line using the MDB command. After you have made the change, i.e., when you are
exiting MDB, you are asked to activate the DB element with the new parameters. If the answer
is yes, the instance is restarted. This means that the function is disabled for the duration of the
restart, typically 5 s.
START
The parameters of the data base element START can be changed on-line.
3BSE 002 417R601
5-19
TTD
The TTD function claims large memory areas for storage of logged values. This means that if
you change the TTD data base too much, the memory may eventually become fragmented.
To rectify this situation, you need a cold start. This becomes a problem if the pool of spare RAM
is small. The size of the pool is shown by the command DIMDB as Free space in the system.
The extent to which the TTD data base is changeable during operation is set out in the
Advant Station 500 Series Operator Station Users Guide.
5-20
3BSE 002 417R601
6HFWLRQ 6HOHFWLRQRI2XWSXW'HYLFH
Chapter 6 Documentation
6.1 Selection of Output Device

SEOM
Use the SEOM (SEt Output Medium) command to choose the output medium: screen on
engineering station, printer or both. This function is available in the Advant Station 100 Series
Engineering Station only.
Syntax:
6(20 [&[,3]]
6(20 [3[,&]]
This command enables you to select the console, the printer or both as the output medium.
C stands for the screen (console) and P stands for a printer.
6.2 Selecting the Presentation Form

You can select the form of presentation for DB element terminals and data base identities in the
document that is to be listed.
SLSYM
Use the SLSYM (SeLect SYMbolic) command to select symbolic identities. This is the default
setting.
Syntax:
6/6<0
SLNUM
Use the SLNUM (SeLect NUMeric) command to select numeric presentation.
Syntax:
6/180
SERN
Use the SERN (SEt Real Notation) command to define the number of decimal places for a value
of data type Real (R).
Syntax:
6(51
3BSE 002 417R601
Output format - exponential or not.
Number of decimal places to be presented.
6-1
&KDSWHU 'RFXPHQWDWLRQ
The number of decimal places can be up to 13 for non-exponential format and six for
exponential format.
If the value is greater than one million, the value is always presented in exponential format
regardless of what you select.
6.3 Setting Page Size

SEPS
The SEPS command invokes the PAGE SETUP dialog. For an explanation see the On-line
Builder Users Guide.
6.4 Page Division and Numbering

This section describes the functions of five commands:
GEPD for automatic page division and numbering
MPD for manual page division and numbering
MPN for changing page numbering
GPN and LPN for listing page numbering.
The pages concerned are pages in the PC diagram. PC diagram pages are also shown as
supplementary information on printed listings. These page numbers are included for easy crossreferencing between diagram and listing and to make the listing easier to refer to.
The size of a PC diagram page is determined by the first and last PC elements on the page.
Which PC elements are included on a page is then given by the execution order. If the automatic
function GEPD (GEnerate Page Division) is not used, the page division and the page numbering
are defined manually using the commands MPD (Modify Page Division) and MPN (Modify
Page Number). The existing page division can be listed with the commands GPN (Get Page
Number) and LPN (List Page Number).
The commands that have the PC diagram page in the printout (LS, LV and LPCL, among
others) also work even if you have not defined a page division (page table). In this case, the
entire PC program is assumed to be located on one diagram page with page number 1.
This makes it possible to postpone page division until the entire PC program is complete.
All page numbers between 0.1 to 9999.9 are permitted as page numbers. There is an entirely
free choice of page numbering within the stated limits. The sequence of pages is determined by
the execution order of PC elements and so is not linked to page number.
The data of the page division and page numbering are stored in a segment with extension .AP
and are located on the USER volume.
The page division is controlled by so called page breaks. Two different types of page breaks
exist:
6-2
Soft page breaks and
Hard page breaks.
3BSE 002 417R601
6HFWLRQ *HQHUDWLQJ3DJH'LYLVLRQV$XWRPDWLFDOO\
A hard page break fixes a page exactly to the number you have specified. When you load source
code which includes soft page breaks, a new page will be used and for the page number the next
consecutive number will be used. The next consecutive number is obtained by adding an
increment of one to the current page number.
With this feature you can structure the layout of your documentation according to your special
needs: You can position some PC elements at certain pages with fix numbers, e.g. PC 1 at page
100, PC 2 at page 200 etc. For other elements you can introduce a page break, only. Then the
next consecutive number will be used, e.g. for PC 1.2 page 102. How to introduce hard or soft
page breaks is explained in Section 6.5, Hard and Soft Page Breaks.
6.4.1 Generating Page Divisions Automatically

GEPD
The GEPD (GEnerate Page Division) command is issued together with a parameter.
The parameter defines which PC program to divide into pages. Before GEPD is invoked, you
must define the page format using the SEPS (SEt Page Size) command (see Section 6.3, Setting
Page Size).
Syntax:
*(3' pc_pgm
Example:
#*(3'3&
GEPD can only divide the entire PC program into pages. To divide parts of it, use the MPD
command.
If you issue the command with regard to a PC program which has already been divided, a check
query is output asking whether the current page division should be deleted. If there is no page
division, a page table is automatically created which is completed during the course of the
current page division.
The page numbering starts with 10 and increases in increments of 10. If you desire another
numbering scheme, you can easily arrange it afterwards using the command MPN (see
Section 6.4.3, Modifying Page Numbering).
6.4.2 Modifying the Page Division Manually

MPD
The MPD (Modify Page Division) command enables you to define page division and page
numbering in the PC diagram for a page. If there is no page numbering table for the PC program
in question, you can create a table with this command.
Syntax:
03' item_des_1 [>item_des_2] = page_nr [/+]
03' item_des_1 [;number_of_elements] = page_nr [/+]
3BSE 002 417R601
6-3
The following working examples show what to do if you want to:
Define or modify page division by defining a number of PC elements that are to be located
on a specified page.
Modify an existing page division so that a new page is created from the stated item
designation (inclusive) to the end of the page on which it appears.
Examples (3)
Example 1:
Define a number of PC elements on a given page (PC1.2 and PC1.3 on page 1.5).
#03'3&!3&
PC1.2
PC1.3
Page 1.5
Figure 6-1. Example 1 of how to change a Page Division
Example 2:
Define the page for single elements (three elements starting with PC1.2 on page 2).
#03'3&
PC1.1
PC1.3
PC1.5
PC1.1
PC1.2
PC1.3
PC1.2
PC1.4
PC1.4
Page 1
Page 2
Page 3
Page 1
Page 2
6-4
3BSE 002 417R601
6HFWLRQ 0RGLI\LQJWKH3DJH'LYLVLRQ0DQXDOO\
Example 3:
Modify an existing page division so that a new page is created from the stated item designation
to the end of the page on which it appears (new page 1.5 starting with PC1.2).
#03'3&
PC1.1
PC1.3
PC1.1
PC1.2
PC1.3
PC1.2
Page 1
Page 2
Page 1
Page 1.5
Page 2

When the previous page division is modified, those pages included entirely in the interval
disappear. The PC elements that remain before and after the interval retain their old page
numbers. There is one exception, however, which is if the interval falls within one page and
there are PC elements both before and after the interval on the page. This is an illegal page
division and an error message is given. Before the new page division is performed, the system
checks that the new page number is free. If the numbers are entirely included in the intervals
stated in the command, the page number can be used, since the old page disappears. You can
also use the command to define a headline text (see Section 6.6, Headlines).
/H
To define a text to a new page, use the /H (Headline) at the end of the
command.
Example:
Create a new page with headline text Error handling.
#03'3& +
ENTER NEW HEADLINE
(UURUKDQGOLQJ
Example:
Combine two old pages (15, 16), each with its own headline. Give the new page the number 15
with the old headline.
#03'3&!3&
HEADLINE ALTERNATIVES AVAILABLE FOR NEW PAGE:
1. NO HEADLINE
2. NEW HEADLINE
3. OLD HEADLINE FROM PAGE 15:
Value check
4. OLD HEADLINE FROM PAGE 16:
Value check (contd)
SELECT ONE:
3BSE 002 417R601
6-5
6.4.3 Modifying Page Numbering

Pages can disappear after changes in the page division; pages can be inserted between, for
example, page 1 and page 2, etc.
MPN
You can use the MPN (Modify Page Numbering) command to change the page numbers of
existing pages for a PC diagram.
Syntax:
031 [pc_pgm,] page_nr [>page_nr] = page_nr [;interv]
031 [pc_pgm,] page_nr [;number_of_pages] = page_nr [;interv]
Use the command to change the page numbering
Of a page. This page will get a hard page break.
Of a range of consecutive pages. The selected pages will get new numbers in ascending
order and with the given interval. A hard page break must belong to the first and last page
number of the specified range.
If interval is omitted, the pages are numbered in directly ascending order.

Examples:
#031
changes page number 1.5 to number 2.
#031!
or
#031
page numbers 5 up to 10 get new numbers in directly ascending order beginning at number 7.
Previous page numbers: 5, 6, 7, 8, 9, 10; new page numbers: 7, 8, 9, 10, 11, 12.
#031!
page numbers 1 up to 10 get new numbers in ascending order with an interval of three beginning
at number 1.
6.4.4 Listing the Page Number

You can list the current page division using the commands GPN (Get Page Number) and
LPN (List Page Number).
GPN
GPN displays the page number of the page containing the specified PC element (item
designation). The first PC element of the diagram page is also displayed.
Syntax:
*31 item_des
6-6
3BSE 002 417R601
6HFWLRQ +DUGDQG6RIW3DJH%UHDNV
LPN
The LPN (List Page Number) command prints out the total number of pages and page numbers
in the PC program and the first PC element on each page specified by the command.
Syntax:
/31 [pc_pgm,] [page_nr [>page_nr]]
/31 [pc_pgm,] [page_nr [;number_of_pages]]
Using this command, you can:
List the first PC element on each page in the entire PC program
List the first PC element on the specified pages.
You can omit the PC program item designation in the command, in which case the system
assumes that the you mean the most recently used PC program.
Example:
#/313&
lists the number of pages and the first PC element on each page of PC program 1.
Example:
#/313&
lists the total number of pages in PC1 and the first PC element of page number 2 up to 10.
6.5 Hard and Soft Page Breaks

Page breaks can be inserted in two different ways:
With the On-line Builder command Insert Statement (IS) or
Via source code generated for example by the Function Chart Builder.
Inserting Page Breaks with the IS Command:

Syntax of the subcommand P:
3
3x
3+
3x+
P introduces a soft page break. The new page will get the next consecutive page number.
Px generates a new page with fix page number x. /H adds a new headline. You will be asked
to specify the headline text.
The following examples visualizes the different handling:
# ,63&
P1
AND(2)
AND(2)
P
OR(2)
3BSE 002 417R601
6-7
The first subcommand of the IS command inserts a hard page break. The new page is fixed to
number 1. The page break command in line 5 consists of a P only: this introduces a soft page
break.
Page Breaks in Source Code:
In source code each page break is represented by a PCD-PAGE line. For a hard page break the
page number is added.
Hard page break:PCD-PAGE 1
Soft page break:PCD_PAGE
Commands that Modify Page Breaks:
MPN:
All soft page breaks will be substituted by hard page breaks.
Example:
0313&
MPD:
All soft page breaks will be substituted by hard page breaks. One exception exists to this rule: If
you modify only the first item designation a soft page break is assigned to, this page break will
not be converted to a hard page break.
Example:
The following situation may appear on page 4 (a soft page break is assigned to PC8.1.5):
PC8.1.5
PC8.1.6
PC8.1.7
#03'3&!3&
The soft page break will be modified to a hard one.
#03'3&
The soft page break will be modified to a hard one.
#03'3&
The soft page break will stay as soft page break.
GEPD:
This command generates a new page division. All page breaks will be hard page breaks.
6-8
3BSE 002 417R601
6HFWLRQ +HDGOLQHV
Commands that show the Type of Page Breaks:

LPN:
This command marks soft page breaks with #. For hard page breaks the hash sign is omitted.
LTREE:
This command marks soft page breaks with #. For hard page breaks the hash sign is omitted.
Other commands display the page number only without specifying the type of the page break.
These commands are: C, CU, GPN, LDBD, LPCD, LPCL, LS, LV.
6.6 Headlines
You can define a headline (up to 79 characters) for each page of a PC diagram. It is printed out
at the bottom of the page, directly above the document footer.
You can freely use the headline to describe, for example, the function of the PC program
section, special process considerations to bear in mind or the construction of the PC program.
MPH
Use the MPH (Modify Page Headline) command to define or modify a headline. You can also
do this using the MPD command (see Section 6.4.2, Modifying the Page Division Manually).
Since each headline is associated with a given page, the LPN and GPN commands also show
the contents of the headline (see Section 6.4.4, Listing the Page Number).
Syntax:
03+ [pc_pgm,] page_nr_1 [>page_nr_2] [=page_nr_3]
03+ [pc_pgm,] page_nr_1 [;number_of_pages] [=page_nr_3]
Use this command to
Modify a headline for a single page.
Modify the headlines for several pages where the range of pages can be specified either
from page_nr_1 to page_nr_2 or
from page_nr_1 for a number_of_pages.
Modify a headline for one or more pages with the text being copied from another page. If
several pages are specified, they are all given the same text copied from another page
(=page-nr_3).
Example:
Insert a new headline for page 1 of PC1.
#03+3&
ENTER NEW HEADLINE ON PAGE 1
Drying lin control
3BSE 002 417R601
6-9
Modify the text of previous example and insert text on the next page as well, which is page
number 1.6.
#03+
HEADLINE TO BE MODIFIED ON PAGE 1
Drying lin control
ENTER NEW HEADLINE ON PAGE 1.6
7HPSHUDWXUHFRQWURO
Copy the headline on page 1 to pages 10 to 20 inclusive.
#03+3&!
6.7 Document Texts

MDT
MDT (Modify Document Texts) allows you to read or modify the document texts for either a
PC program or data base listings.
Syntax:
0'7 pc_pgm [>pc_pgm] [=pc_pgm]
0'7 '%
Description:
With MDT you can read, copy or modify the document texts for either PC or data base listings.
If the third parameter is specified, the associated document texts will be copied to the
destination given with the first or second parameter. If the third parameter is omitted, you can
enter the new document texts within a dialog.
Examples:
Copy the texts from PC5 to all PC programs PC7, PC8, and PC9:
#MDT PC7>PC9=PC5
6-10
3BSE 002 417R601
6HFWLRQ 3ULQWLQJD3&3URJUDP6WUXFWXUH
Modify the document text of PC program 7:

#MDT PC7
Choose Document Texts dialog under Edit in the menu bar to specify the text fields of the
document text; the dialog layout depends on the selected template (for example Standard
Master, IEC or DIN template) for a PC program or the database:
Figure 6-4. Edit Document Texts (Standard Master Template)

Document texts appear at the bottom of each page of the documentation. The dialog box shows
only a part of the document texts, use the scroll box to see the other parts of it.
Press <tab> or <shift+tab> (for the opposite direction) to move the cursor to the text fields of
the template and type the text you wish to appear in the document texts.
6.8 Printing a PC Program Structure

LTREE
Use the command LTREE (List TREE) to list a tree structure of the specified part(s) of PC
program(s).
Syntax:
/75(( item_des[>item_des][/mode]
/75(( item_des[;number_of_elements][/mode]
3BSE 002 417R601
6-11
The following arguments for mode are available:

Normal mode: All PC elements.
S
Short mode: Structural PC elements + PC diagram headlines and page No.
Long mode: All PC elements with their instance names + PC diagram

headlines and page No.
Normal disk mode: Normal mode + segment. (Explanation to disk mode: A

printout is also stored on a volume for subsequent documentation. The
command prompts for volume and segment names.)
SD
Short disk mode: Short mode + segment.
LD
Long disk mode: Long mode + segment.
Use the LTREE command to list the following structures:
A specified item designation with subordinate PC elements
From one item designation to another item designation, inclusive
From an item designation forward a number of PC elements.
Example:
#/75((3&
)LJXUH Example of a Printout of a PC Program Structure
6-12
3BSE 002 417R601
6HFWLRQ 3ULQWLQJD3&3URJUDP6WUXFWXUH
Example for short mode:
)LJXUH Example of a Printout in Short Mode
3BSE 002 417R601
6-13
Example for long mode:

#/75((3&/
)LJXUH Example of a Printout in Long Mode
6-14
3BSE 002 417R601
6HFWLRQ 3ULQWLQJD3&3URJUDP/LVW
6.9 Printing a PC Program List

LPCL
Use the LPCL (List PC List) command to print a functional list of one or more PC programs.
First define the format of the PC list using the SEPS (SEt Page Size) command.
Syntax:
/3&/ pc_pgm [>pc_pgm] [=page_nr]
You can list
A PC program
A PC program with a request for the page numbering to begin at a given number
Several consecutive PC programs with a request for the page numbering to begin at a given
number.
Examples:
#/3&/3&!3&
lists PC programs PC1 to PC5 inclusive. The first document page is page number 1.
#/3&/3&!3&
lists PC programs PC3 to PC5 inclusive. The first document page is page number 15.
3BSE 002 417R601
6-15
#/3&/3&
Produces the following printout:
ABB Automation and Drives PCD PAGE:

IDENTITY
NAME
PC4
:1
:2
:5
PC4.1
:1
:2
:3
:5
:6
PC4.1.1
:1
:2
:20
TYPE
PCPGM (10,2)
ON
IB
R
IB
RUN
OB
CONTRM (100,2)
ON
IB
SINGLE IB
R
IB
RUN
OB
MODP
OB
MUL (R,2)
IR
IR
OR
SOURCE
UNIT
PAGE
=VENT_OPEN
0
:1
:10
:11
:12
:20
:21
:22
:30
:31
:32
:40
:41
:42
PC4.1.3
:1
:2
:3
:5
PC4.1.4
:1
:2
:3
:5
PC4.2
:1
:2
:3
:5
:6
COMP-R
I
HHYS
H1
H2
I<H1
I>=H1
I>=H2
LHYS
L1
L2
I>L1
I<=L1
I<=L2
OSC-B
EN
TP
TC
O
OSC-B
EN
TP
TC
O
CONTRM
ON
SINGLE
R
RUN
MODP
(2,2)
IR
IR
IR
IR
OB
OB
OB
IR
IR
IR
OB
OB
OB
NOTES
=DI5.3
1
0
0
=AI1.2
D=1.040
=AI1.2 G
liter
=AO1.2
PC4.1.2
PC4.1.1:20
D=100.000
D=700.000
D=900.000
=AO1.2 P
PC4.1.2:1
=DO1.5 P
PC4.1.3:1
liter
liter
liter
liter
=DO1.5
D=100.000
D=100.000
D=200.000
liter
liter
liter
=DO1.4
IB
IT
IT
OB
PC4.1.2:22
D=0.5 s
D=1
=DO1.7
IB
IT
IT
OB
(50,5)
IB
IB
IB
OB
OB
PC4.1.2:42
D=0.5 s
D=1
=DO1.7
=DI1.8
D=0
=DI1.9
=DO1.8
Design ch: Design_ch

Tech ref: Tech_ref
Resp dept: Resp_dept

Date: Date
PC LIST
L_Text2
L_Text3
L_Text4
R_Text1
R_Text2
R_Text3
R_Text4
=DO1.7 P
=DO1.7 P
=DI1.8
=DI1.9
=DO1.8 P
Language: L
Rev ind: R_I
Sheet: 1
Cont: -
Figure 6-8. Example of a Printout using the LPCL Command
6-16
3BSE 002 417R601
6HFWLRQ 3ULQWLQJD3&'LDJUDP
6.10 Printing a PC Diagram

The PC diagram is the graphical representation of a PC program. The PC diagram is either
printed out graphically or alphanumerically at a selectable quality level, depending on the
selection made during initiation of the printer.
LPCD
Use the LPCD (List PC Diagram) command to produce a printout of the PC diagram.
Syntax:
/3&'
/3&'
/3&'
/3&'
[pc_pgm,] page_nr [>page_nr]

[pc_pgm,] page_nr [;number_of_pages]
pc_pgm [>pc_pgm]
pc_pgm [;number_of_pc_pgms]
You can use it to give PC diagram printout of
A specified page of an entire PC program
A number of pages
An entire PC program
A number of PC programs.
Before running LPCD, use the commands
3BSE 002 417R601
SEOM to set output medium to printer and/or console
SEPS to set the page size for the PC diagram
MPD and MPN to define page divisions
SLNUM or SLSYM to select numeric or symbolic references.
6-17
COMMON IDENTITY :
D=1
D=0
PC1
PCPCM(20.1)
1 ON
RUN
2 R
.1(Sample InstanceName for CONTRM )

CONTRM(100.1.0)
1 ON
RUN
5
P-=DO1.1/CONTRM RUN
2
SINGLE
MODP 6
3 R
=DI1.1
=DI1.2
=DI1.3
=DI1.4
ABB Automation and Drives 1993-12-12/07:07:04
G
D=1
1
2
3
.1
&
20
P-=DO1.2/FLASH
EXECUTION ORDER: 1
.1 (Sample InstanceName for CONTRM)
PC1
Design ch: Design ch
Tech ref : Tech ref
Resp dept: Resp dept

Date
:Date
PC DIAGRAM
L Text2
L Text3
L Text4
R
R
R
R
Text1
Text2
Text3
Text4
Language:
L
Rev ind : R I
Sheet:
1
Cont :
-
Figure 6-9. Example of a PC Diagram using the LPCD Command

For each PC diagram page, a document header and footer are generated with the details of item
designation, order number, installation name and similar information.
The PC elements are represented by their diagram symbols and if appropriate the name for this
element (the instance name), the connections between them are represented by interconnection
lines. Input variables are connected from the left and output variables are taken out to the right.
Each input variable is accompanied by a page reference and variable name or, if there is no
variable name, terminal identity for the output that generates the value of the variable.
Each output variable is accompanied by page references and, where appropriate, the variable
name of the receiving PC element. This applies if the output variable has been connected to
another PC element. If it has been connected to the data base, the relevant data base identity is
shown. The order of execution between PC elements is also shown on the diagram page.
References that do not fit into the left-hand or right-hand parts of the page are shown in a field at
the bottom of the page.
If there is not enough space on a page for the PC elements with the MPD command (see
Section 6.4.2, Modifying the Page Division Manually), an error message appears on the page.
The command then continues with the next diagram page. Finally, the page numbers of those
pages without enough space for the specified PC elements are printed out.
6-18
3BSE 002 417R601
6HFWLRQ *HQHUDO
Chapter 7 Backup and Transfer of Application Data
7.1 General
For various purposes, different dump types are available:
Total Backup
For long-term storage and backup copying of the application in an Advant Controller 400
Series, dump the PC programs and the data base in a total dump. Use the DUAP and LOAP
commands for this purpose. For more information, see Section 7.3, Total Backup.
Dumping and Loading for Redimensioning
When you need to have more space for DB elements or PC programs, a redimensioning
procedure is necessary. To redimension the data base or the PC part, the application must first
be dumped and then reloaded after redimensioning. For this purpose, use the commands
DUTDB/LOTDB and DUTPT/LOTPT. For more information, see Section 7.4, Dumping and
Loading for Redimensioning.
Data Transfer via Source Code
You can use the source code handling function to move a complete application between
different engineering tools and different target systems. Four commands are available for the
data transfer: DUDBS/TRDBS and DUPCS/TRPCS. For more information, see Section 7.5,
Data Transfer via Source Code.
NOTE
Only the total backup (DUAP) can contain the data of the User Disk Application
Segments (see Section 7.3, Total Backup) that are needed to handle the Advant
Controller 400 Series with the engineering station and to reidentify Type Circuits
from Function Chart Builder (see Section 7.2.2, USER Volume). No other dump
types - except source code - contain the complete User Disk Application
Segments.
Mismatch problems between the User Disk Application Segments on the
engineering station and the application programs on the Advant Controller 400
Series may arise if you do not pay attention to the User Disk Application
Segments when you are loading dumps (see Section 7.2.2.4, User Disk
Application Segments Mismatch).
Nevertheless, the application programs (PC programs and data base contents) on
the Advant Controller 400 Series are sufficient for normal operation.
3BSE 002 417R601
7-1
&KDSWHU %DFNXSDQG7UDQVIHURI$SSOLFDWLRQ'DWD
Consider the following recommendations when working with dumps without the
User Disk Application Segments data:
Create a backup of the User Disk Application Segments. Copy the User Disk
Application Segments on the engineering station to a backup medium.
Between saving the User Disk Application Segments and creating the dump,
no changes to the application are allowed.
Use the backup copy of the User Disk Application Segments you saved
separately and copy the data to the USER volume on the engineering station.
This means:
You overwrite existing data on the USER volume which do not fit with the
dump data, or
You transfer the data of the USER volume to a newly created node on the
7.2 Data Storage Description

When working with On-line Builder two volumes are available for each node you have created.
These volumes are named USER and SRCE. Both volumes reside on the engineering station
and belong to a node.
When you select a node in the Node List of Application Builder or of On-line Builder, the
corresponding volumes USER and SRCE are assigned to this node. While you are working, Online Builder commands will read from or write to these volumes. If you switch to another node
with the SLTARG command, USER and SRCE will also be reassigned to the corresponding set
of volumes of the selected node. (If you want to work always with the same set, you can
configure that behavior in the On-line Builder Setup menu.)
7.2.1 Maximal Segment Size

The maximal size of On-line Builder segments is increased from 1 MByte to 2 MByte. The new
maximal segment size enables you to use more PC variable names, which are stored in the
segment PCMASS.SM. Nevertheless, not only the segment PCMAS.SM is affected by this
limit, but all segments. The new size is supported by On-line Builder of version 2.2/0 or greater.
The new maximal segment size may lead to some inconvenience when you try to store those
segments on a diskette. If the actual segments size exceeds 1.4 MByte then perform one of the
following procedures:
compress the segment with a utility like Compress/Expand from Microsoft or PKZIP
(shareware), or
distribute the segment to more than one diskette using the MS-Backup utility.
If for any reason you want to work with the maximal segment size of 1 MByte of the foregoing
On-line Builder versions, you have to add the following line to the section Setup of the file
ONBBIOS.INI:
CXFileSize=1023
7-2
3BSE 002 417R601
6HFWLRQ 86(59ROXPH
After the modification the section may look like this:

[SETUP]
SINGLEPAGE=0
...
...
CXFileSize=1023
If you want to return later on the default size of 2 MByte, remove the line from the file
ONBBIOS.INI or set the value to 2047.
You can find the file ONBBIOS.INI in the directory C:\advabldenv.
7.2.2 USER Volume

The USER volume contains important information about your application programs, e.g. PC
variable names, PC program pagination etc. But nevertheless the USER volume is a normal
volume like SRCE: you can store segments you like at this volume. To distinguish between
those segments that carry the important information about the internals of your PC programs
and other segments you have stored at USER, we call the PC program related segments User
Disk Application Segments. It is the intention that only the User Disk Application Segments
shall be stored at USER.
You can store a copy of the User Disk Application Segments in an Advant Controller 400 Series
as a backup. If you have the actual information about your application programs stored in the
Advant Controller 400 Series, you are independent on the engineering station, where the User
Disk Application Segments are stored: you can connect for example with another engineering
station to the Advant Controller 400 Series, retrieve the User Disk Application Segments from
the backup and continue working.
The most important segment of the User Disk Application Segments is the segment PCMASS.
If for a certain node no PCMASS exists, you will be asked to create one when you switch to PC
level with the aid of the SLLEV command. PC level is the level for working with application
programs.
The following message will be displayed:
Cannot find the segment PCMASS on the Volume USER.
Type <CR> to create a new segment with the name PCMASS
Or enter a new segment name and type <CR>
Or type Q <CR> to quit
If you plan to retrieve the User Disk Application Segments from the backup on the controller,
you still have to create now a new PCMASS. The RUDAS command will overwrite it later on.
You can decide whether you want
3BSE 002 417R601
To work only with the User Disk Application Segments stored under the volume USER on
the engineering station or
To have a backup on the Advant Controller 400 Series, additionally.
7-3
If you decide to use the backup facility, the On-line Builder commands will nevertheless work
with the information stored under the engineering stations USER volume (see Figure 7-1).
Two commands will perform the backup copy to the controller automatically:
SLTARG for selection of another node and
TSESS for termination of the current session.
You can force the backup with the SUDAS command, additionally. For the backup handling
three commands are available: SUDAS, RUDAS and SHUDAS (see Section 7.2.2.3, Backup
Commands).
User Disk Application Segments Backup Area

User Disk Application Segments
Engineering Station
USER
volume
AS
SUD
AS
RUD
Advant
Controller
400 Series
)LJXUH User Disk Application Segments and their Backup

When the backup feature is active, the User Disk Application Segments are stored at two
different places:
On the engineering station and
On the Advant Controller 400 Series.
To avoid a mismatch between both versions the information is tagged with an identifier.
All commands that read from or write to the User Disk Application Segments check these
identifiers to be equal.
Nevertheless, it can happen that the information stored at both places is different. To overcome a
mismatch situation, you can replace the information stored on the Advant Controller 400 Series
with that under the USER volume or vice versa. Such a situation can occur for example if the
hard disk of the engineering station fails or you switch off your engineering station without
terminating the On-line Builder.
7-4
3BSE 002 417R601
6HFWLRQ 86(59ROXPH
7.2.2.1 List of User Disk Application Segments

The User Disk Application Segments can consist of different segments. They are produced
during various application-building activities:
PCMASS.SM
PC variable names defined by the user (see Section 4.2.6, Modifying the
Name of a Statement or Variable).
Document texts for DB diagrams, PC diagrams and PC lists (see Section 6.7,
Document Texts).
Headline texts for PC diagrams (see Section 6.6, Headlines).
Parameter settings for printout control (Section 6.3, Setting Page Size).
List of selected variables for the GETAB command (see Section 4.2.8,
Displaying the Variable Values in a Table).
PCMASS*.AP
PC diagram pagination (see Section 6.4, Page Division and Numbering).
P1PCMASS.NI Instance names (see Section 3.5.3.3, Assigning a name)

USERID.UI
Network and node number as well as version of the USER volume.
*.TI
Type Circuit information files, created by Function Chart Builder only.

They are stored on the Backup Area on the node and belong to corresponding
*.AA files. They are needed to reconstruct Type Circuits.
*.TB
Type Circuit data base files, created by Function Chart Builder only.
They are stored on the Backup Area of the node and belong to corresponding
*.BA files. They are needed to reconstruct Type Circuits.
*.TC
Type Circuit source code files, created by Function Chart Builder only.
They are stored on the Backup Area of the node and belong to corresponding
*.AA files. They are needed to reconstruct Type Circuits.
Restrictions for User Disk Application Segments:

The following restrictions apply to User Disk Application Segments:
Number of PC variable names:

Starting with version 2.2/0 of On-line Builder the number of possible PC variables names
is increased. This is valid for Advant Controller 400 Series only.
The modification results in a new internal structure of the segment PCMASS.SM.
The restriction of only 32 kByte memory for all names starting with a certain character,
e.g. A or B is no longer valid. This is true for PCMASS segments created with Online Builder of version 2.2/0 or greater. For Master Piece 200/1 the old structure will be
used.
If you continue to work with an application that was created with On-line Builder of a
version less than 2.2/0, the old 32 kByte restriction is still valid, because the segment
PCMASS.SM was created with the old structure.
3BSE 002 417R601
7-5
If you want to overcome for a certain application the restriction of 32 KByte, perform the
following steps:
Dump the source code of the application (DUDBS, DUPCS)
Delete the PC programs (DS)
Delete PCMASS and page tables (DELETE USER:PCMASS*.*)
Create a new PCMASS (e.g. SLLEV PC, then type <CR>)
Translate source code (TRDBS, TRPCS).
If for compatibility reasons you want to work with the 32 kByte restriction, you must edit
the file C:\AS100ES\ONBBIOS.INI. In the SETUP section set the value of
HashTableVersion to 0:
HashTableVersion=0
Then the old PCMASS structure will be used.
NOTE
You cannot use On-line Builder of version less than 2.2/0 together with a segment
PCMASS.SM which has been created by On-line Builder of version 2.2/0.
To see the maximum size of the segment PCMASS.SM use the command
MSTABS.
The maximum number of segments that can be stored on the Advant Controller 400 Series
Backup Area is restricted to 400. You can see the total number of existing segments with
the SHUDAS command (see Section 7.2.2.3, Backup Commands).
7.2.2.2 User Disk Application Segments Backup Handling

You can save User Disk Application Segments on the Advant Controller 400 Series for backup
purposes. Using this function (User Disk Application Segments backup) is recommended.
The function then automatically updates the backup of the User Disk Application Segments on
the Advant Controller 400 Series each time either one of the commands SLTARG or TSESS is
used. You can also update the backup manually using the command SUDAS.
A version identifier exists to check the consistency of the User Disk Application Segments and
their backup on the controller. Each time you start a new session - that is after a SLTARG or
after a TSESS command - and perform commands that will modify the User Disk Application
Segments, the version identifier of the User Disk Application Segments will be incremented by
one. When you generate now the backup copy with the SUDAS command, the version identifier
of the User Disk Application Segments Backup Area on the controller will be the same as that
of the User Disk Application Segments on the engineering station. If later on commands will
again modify the User Disk Application Segments, the version identifier on the engineering
station will be incremented, too. Then another SUDAS or an SLTARG or TSESS command is
necessary for consistency.
The version of the User Disk Application Segments and of their backup on the Advant
Controller 400 Series must be identical.
7-6
3BSE 002 417R601
6HFWLRQ 86(59ROXPH
If, for any reason, they are not identical, the mismatch is detected and you define the data on the
engineering station or the data on the Advant Controller 400 Series as the valid data. Using the
command RUDAS, you can copy the data from the Advant Controller 400 Series manually to
the engineering station. This procedure will update the version identifier, too.
In addition to the backup itself, an advantage of this function is that the User Disk Application
Segments backup may be included in the DUAP dump, see Section 7.3, Total Backup. A further
advantage is that the network and node number are compared to check that the correct node is
selected on the engineering station, which makes your work more secure.
Advant Controller 400 Series configuration requires the following operations to activate the
backup of User Disk Application Segments:
Activate the Backup function (User Disk Application Segments backup function) with the
DIMPC command.
Be sure that the node selected on the engineering station (Node List) belongs to the
connected Advant Controller 400 Series (working on the correct User Disk Application
Segments).
When you are loading source code (DB source code, PC programs or parts of PC
programs) in order to exchange already existing source code, first delete the parts that
already exist (command DS). In doing so, you also delete the variable names, document
description headings and page divisions from the User Disk Application Segments.
Every time you want to transfer a dump, the User Disk Application Segments must also be
copied. This is not necessary for the DUAP dump, if the backup function was activated and
the data were saved before performing the dump.
Dimensioning the Backup Area

The backup feature is switched off by default. When you activate the it with the DIMPC
command you have to dimension the User Disk Application Segments Backup Area on the
Advant Controller 400 Series. The size needed depends strongly
On the size of your application programs,
On the number of PC variables used,
On the length of the names of the PC variables
On the length and number of Instance names
On the number of PC programs.
The minimum size is 51 kilobytes to use the function.

As the *.SM segments may grow (see MSTABS) the area needed may grow, too. For each PC
program add at least 1 kByte for the storage of the *.AP segments.
If you also want to save Type Circuits created by the Function Chart Builder, increase the
memory space appropriate to the number of Type Circuits and their size (*.Ti, *.TB, *.TC).
If the function is switched off, then the size is zero. See also Section 3.4, PC Dimensioning.
3BSE 002 417R601
7-7
The amount of memory needed may be quite unclear when you start your application
programming. Therefore it may be necessary to redimension this area later on.
The redimensioning of the Backup Area can be performed in the following manner:
Dump the data base and the application programs with the DUTDB and DUTPT
commands.
Perform a RECONFIG of the Advant Controller 400 Series.
Load the data base with the LOTDB command.
Load the application programs with the LOTPT command and specify Redimension = yes.
Enter a bigger value for the User Disk Application Segments Backup Area.
For more information see Section 7.4, Dumping and Loading for Redimensioning.
CAUTION
The following operations can cause loss of data.
When problems occur with the User Disk Application Segments, you can:
Use the RUDAS command (only if the backup is available).
If you have a backup of your hard disk, try to get an older version of the User Disk
Application Segments (see Section 7.2.2.4, User Disk Application Segments Mismatch).
Initialize the User Disk Application Segments contents (after RECONFIG or a cold start).
This can be performed in two alternative ways:
Delete the PCMASS.SM, PCMASS*.AP and *.UI files on SYSTEM level (SLLEV
SYST) on the USER volume.
Create a new node with the Application Builder on the engineering station.
The corresponding USER volume is in its initial state.
It is up to you to decide whether to use an earlier version of the User Disk Application Segments
or to create new segments. Only you can estimate the difficulties arising, which depend on how
many changes have been made to the earlier User Disk Application Segments since they were
created.
7.2.2.3 Backup Commands

NOTE
In the following USER DISK is used in examples of screen displays as short
form for User Disk Application Segments and BACKUP USER AREA as
short form for User Disk Application Segments Backup Area.
Saving the User Disk Application Segments (SUDAS)
The command SUDAS (Save User Disk Application Segments) copies the contents of the User
Disk Application Segments to the connected Advant Controller 400 Series.
7-8
3BSE 002 417R601
6HFWLRQ 86(59ROXPH
Syntax:
68'$6
The SUDAS command displays information about versions and dates of the backup on the
connected Advant Controller 400 Series and the engineering station.
#68'$6
USER DISK
Net, Node: 12,3
Version: 41
Time: 1993-07-22/15:01:23
BACKUP USER AREA Net, Node: 12,3

Continue (Y/N)?
Version: 42
Time: 1993-07-22/16:18:02
Figure 7-2. Example of the SUDAS Screen Display

You can update the backup by answering Y. The User Disk Application Segments are then
copied to the connected Advant Controller 400 Series, overwriting any existing backup copy.
If an insufficient amount of memory is dimensioned for the backup copy in the Advant
Controller 400 Series, a redimensioning procedure (DIMPC) is necessary (see Section 7.4,
Dumping and Loading for Redimensioning).
Retrieve the User Disk Application Segments(RUDAS)
The command RUDAS (Retrieve User Disk Application Segments) copies the User Disk
Application Segments from the connected Advant Controller 400 Series back to the User Disk
Application Segments on the engineering station.
Syntax:
58'$6
The RUDAS command displays information about versions and dates of the backup on the
connected Advant Controller 400 Series and the engineering station.
#58'$6
USER DISK
BACKUP USER AREA
Continue? (Y/N)
Net, Node: 12,3

Net, Node: 12,3
Version: 41 Time: 1993-07-27/08:01:23

Version: 38 Time: 1993-07-22/16:18:02
Figure 7-3. Example of the RUDAS Screen Display

You can copy the data from the connected Advant Controller 400 Series back to the User Disk
Application Segments on the engineering station by answering Y, thereby overwriting
existing User Disk Application Segments data.
3BSE 002 417R601
7-9
Showing the Version of the User Disk Application Segments (SHUDAS)

The command SHUDAS (SHow User Disk Application Segments) shows data such as the
Advant Controller 400 Series node identity, version number and the time stamp of the User Disk
Application Segments on the engineering station, and the backup on the Advant Controller 400
Series.
Syntax:
6+8'$6 [/7$5*]|[/86(5]
Description:
/TARG
Adds a list of all segments stored in Backup Area on the controller.
/USER
Adds a list of the User Disk Application Segments on the engineering station.
When you use this command without an activated backup function, the engineering station will
display an error message.
#6+8'$6
USER DISK
Net, Node: 12,3
51260 Bytes
Used size:
Version: 41
Version: 38
Time: 1989-04-22/15:01:23
Time: 1989-04-20/16:18:01
Figure 7-4. Example of the SHUDAS Screen Display

.
#6+8'$67$5*
USER DISK
Net, Node: 12,3
Used size :
51260 Bytes
Version: 41
Version: 38
Time: 1989-04-22/15:01:23
Time: 1989-04-20/16:18:01
------------------------------------------------------1. Segment stored on target = USER:PCMASS.SM

2. Segment stored on target = USER:PCMASS95.AP
------------------------------------------------------Figure 7-5. Example of the SHUDAS /TARG
Used size is for all variants of the SHUDAS command the size of the User Disk Application
Segments Backup Area on the controller.
7-10
3BSE 002 417R601
6HFWLRQ 65&(9ROXPH
7.2.2.4 User Disk Application Segments Mismatch

Mismatch problems between the User Disk Application Segments and the Advant Controller
400 Series may arise if the corresponding node is not selected.
Variable Names
Variable names may be missing in the User Disk Application Segments when they should be
present, or may be present on the volume but do not have a corresponding variable in the PC
program. The variable name may even have become attached to a different variable from the one
it originally belonged to, as a consequence of modifications that you may have made without
using the correct User Disk Application Segments. For corrections of this type, see Section
4.2.6, Modifying the Name of a Statement or Variable.
Pagination Problems
The pagination may have been disturbed if PC elements have been removed without the correct
User Disk Application Segments. Since pagination information is stored in the form of the item
designation on the first PC element of the page, problems arise if a PC element that is first on a
page is removed. This is because its identity is not present in the Advant Controller 400 Series,
but is present in the User Disk Application Segments.
Do as follows:
Insert a PC element with the same item designation as the PC element that has been
removed. Insert it one step before the first PC element on the page following the erroneous
one.
Delete the PC element. The page of this element disappears as well.
7.2.3 SRCE Volume

The SRCE volume is a general purpose volume. It is as the USER volume available for each
node. Commands that read or write source code use SRCE as data storage. It is the intention that
you store your data belonging to the selected node rather on SRCE than on USER.
7.3 Total Backup

For long-term storage and backup copying of the application, dump the PC programs and the
data base in a total dump. To do this, use the DUAP command to dump and the LOAP
command to load the application.
The contents of the User Disk Application Segments is included in the DUAP dump if the
USER volume backup function is active (see Section 7.2.2.3, Backup Commands) and the
contents has been saved using the SUDAS command. Otherwise, you must copy and save the
User Disk Application Segments separately.
3BSE 002 417R601
7-11
7.3.1 Dumping the Complete Application

DUAP
Use the command DUAP (DUmp Application Programs) to create a backup dump of an Advant
Controller 400 Series. The DUAP dump contains all data base and PC programs present in the
target. The command works on SYSTEM level or PC level.
The dump consists of one to 16 segments and can have 257, 513, 1025, etc., kilobytes. The last
segment may be smaller or larger than the standard-sized segment.
Syntax:
'8$3 dump_name[,volume][;options]
where
dump_name
One to seven alphanumeric characters
options
A string of one or more option identifiers
volume
SRCE or USER.
The following arguments for options are available:

D:
(Delete) automatically deletes from the volumes all existing segments having
the same names as the new dump segments are to have. By default, in dialog
mode, deletion requires the operators permission. In parameter mode, the
command terminates if a duplicate segment is found.
F:
Forces the segment size to be 257 kilobytes.
I:
(Information) gives more progress text than by default.
N:
(No questions) suppresses the prompting for dump message texts. By default,
the operator is prompted for two text messages (dialog and parameter mode).
The command uses the default volume SRCE and can be used in OPERATION mode or in
CONFIGURATION mode. If possible, use CONFIGURATION mode, since the time required
for dumping is shorter.
The segment names of the dump consist of the given name, one or more zeros, and a sequential
number (corresponding to the order between segments).
The type (extension) of the segments is AD.
Example:
A dump named APPL is stored under the following segment names:
APPL0001.AD;
and
APPL0002.AD.
The padding zeros are generated automatically.
7-12
3BSE 002 417R601
6HFWLRQ /RDGLQJWKH&RPSOHWH$SSOLFDWLRQ
You can enter a dump description (one single line, maximum 80 characters) and a message to
the person who loads the dump later on (maximum eight lines of 80 characters). The dump
messages can be used for information about the dump, which system it belongs to, etc.
A DUAP dump can only be loaded to that system it was dumped from.
You can use the LIST command to investigate a dump (see Section 8.8, Listing Text Segments).
To terminate the command, press <Ctrl-Break> or <Q>.
NOTE
All communication ports for MasterBus 300, as well as those for RCOM, GCOM
and Modbus, must be started before you dimension the data base. This is to
enable reloading of the dump.
7.3.2 Loading the Complete Application

LOAP
Use the command LOAP (LOad APplication) to load a DUAP backup dump into an Advant
Controller 400 Series. The DUAP dump contains all data base and PC applications from the
dumped target as well the backup data from the User Disk Application Segments, if the backup
function was activated. The command works in CONFIGURATION mode on SYSTEM level or
on PC level. A DUAP dump can only be loaded to that system it was dumped from. After
loading, the system is dimensioned as it was during the dump.
Syntax:
/2$3 dump_name[,volume][;options]
where:
dump_name
One to seven alphanumeric characters
options
A string of one or more option identifiers
volume
SRCE or USER.
The dump is loaded from the volume SRCE if volume is not specified. The dump description
appears on the screen and you decide whether to continue with loading.
The following arguments for options are available:
I:
Gives more progress texts than by default.
U:
Allows loading even if network/node numbers differ in dump and target.

By default, the network/node numbers must agree.
When using the LOAP command, two different situations may occur:
The dump contains the backup of the User Disk Application Segments.
The dump does not contain the User Disk Application Segments.
In the first case, use the RUDAS command to retrieve the User Disk Application Segments
(after loading the dump). Then you have the valid User Disk Application Segments on the
3BSE 002 417R601
7-13
In the second case, use the backup copy of the User Disk Application Segments you saved
separately at the same time as the DUAP dump (see Section 7.3, Total Backup) and copy the
data to the USER volume on the engineering station.
7.4 Dumping and Loading for Redimensioning

WARNING
Risk of malfunctions. The RAM is cleared after a cold start or when the command
RECONFIG is used. This means that the process control application ceases
immediately.
PC programs and the data base must be reloaded.
Data Base
Redimensioning of the data base is necessary if the previously dimensioned data base is too
small to create all needed DB elements. You can redimension the data base as follows.
Case 1
Enough spare area is left.
Use the command DIMDB to increase the number of the additionally needed DB element type
(see Section 3.2.1.3, Memory Space). Redimensioning the data base in this way is only
permitted if the PC part is not dimensioned.
Case 2
Not enough spare area is left and the PC part is not dimensioned.
1.
Perform a data base dump (DUTDB).
2.
Cold start the system. Set the start mode selector to CLEAR and press the ENTER button
or use the RECONFIG command (see Section 2.8.3, Resetting the Controller).
3.
Load the data base dump (LOTDB) and redimension the data base (see Section 7.4.3,
Loading the Data Base).
Case 3
Not enough spare area is left and the PC part is dimensioned.
7-14
1.
Perform a data base dump (DUTDB) and a PC dump (DUTPT).
2.
3.
Load the data base dump (LOTDB) and redimension the data base (see Section 7.4.3,
Loading the Data Base).
4.
Load the PC dump (LOTPT) (see Section 7.4.4, Loading PC Programs).
3BSE 002 417R601
6HFWLRQ 'XPSLQJWKH'DWD%DVH
PC Part
Redimensioning of the PC program space is necessary if the previously dimensioned PC part is
too small for all PC programs or the User Disk Application Segments backup function. You can
redimension the PC part as follows:
1.
Perform a data base dump (DUTDB) and a PC dump (DUTPT).
2.
If the reason for redimensioning is that you need more space for the User Disk Application
Segments backup function, use the SHUDAS command to check out how much memory
space is at least required.
3.
4.
Load the data base dump (LOTDB) (if necessary, also redimension the data base) (see
Section 7.4.3, Loading the Data Base).
5.
Load the PC dump (LOTPT) (see Section 7.4.4, Loading PC Programs).

NOTE
The User Disk Application Segments are not affected and does not have to be
involved in redimensioning. (If, for some reason, you use DUTDB and DUTPT
instead of DUAP to make a security copy of the application program, also copy
the User Disk Application Segments separately.)
7.4.1 Dumping the Data Base

DUTDB
Use the command DUTDB (DUmp Total Data Base) to create a total dump of the data base in
the Advant Controller 400 Series.
Syntax:
'87'% [dump_name]
dump_name:
one...six characters
All data base concepts within the target system are included in the dump. The command dialog
is self-instructive and the valid answers are listed within the prompting text of every question.
You can terminate the command by pressing <Ctrl-Break> or, during the dialog, by entering
the answer Q to any question. You can enter a message with a maximum of 10 text lines
which are stored on the dump volume.
During the dump process, messages are given to the effect that dumping has started, that it is in
progress and whether it has been correctly performed or has failed.
3BSE 002 417R601
7-15
7.4.2 Dumping PC Programs

DUTPT
Dump PC programs with the command DUTPT (DUmp Total Program Tables).
Syntax:
'8737 [dump_name]
'8737 [dump_name, volume]
dump_name
six characters
volume
four characters
The command operates in dialog mode. It compresses the PC area automatically before the
dump takes place (Advant Controller 400 Series). For other types of systems, use the CSPT
(CompreSs Program Tables) command before dumping. You can enter a message that is stored
on the dump volume. The text is printed out before the loading procedure starts and makes it
easy to identify the correct PC dump. Press <Ctrl-Break> to leave the function.
All blocked PC elements in the PC program are automatically deblocked when the PC
program is loaded back into the Advant Controller 400 Series.
Dumping can be done with the PC programs in any state.
Any blocking disappears when the PC program is reloaded.
The dump covers all PC programs of the Advant Controller 400 Series. The User Disk
Application Segments are not included in the dump (see Section 7.1, General).
The volume SRCE is used as default volume for the dump.
7.4.3 Loading the Data Base

LOTDB
Use the command LOTDB (LOad Total Data Base) to load a total dump of a data base into the
Advant Controller 400 Series. The receiving Advant Controller 400 Series must be identical to
the Advant Controller 400 Series from which the dump is taken.
Syntax:
/27'% [dump_name]
dump_name:
one...six characters
The dialog is self-instructive and the valid answers are listed within the prompting text of every
question.
The load command prompts for the following:
COMPRESS DATA BASE DUMP? (Y/N/Q) =
REDIMENSION? (Y/N/Q) =
For the redimension dialog, please refer to the DIMDB command for instructions (type HELP
DIMDB). Compression is intended for use when the data base population is finalized.
By compression, any spare memory space is released and made available for other purposes,
e.g., for PC programs.
7-16
3BSE 002 417R601
6HFWLRQ /RDGLQJ3&3URJUDPV
If you want to redimension the Advant Controller 400 Series, invoke the dimensioning
command (see Section 3.2.1, Dimensioning the Data Base). Using this command, you can
dimension the data base for the required size. You can combine the commands COMPRESS
and REDIMENSION.
During the loading process, messages are given to the effect that dumping has started, that it is
in progress and whether it has been correctly performed or has failed.
7.4.4 Loading PC Programs

LOTPT
Use the LOTPT (LOad Total Program Tables) command to load the PC programs previously
dumped. The receiving Advant Controller 400 Series must be identical to the Advant
Controller 400 Series from which the dump is taken.
Syntax:
/2737 [dump_name]
/2737 [dump_name, volume]
dump_name
six characters
volume
four characters.
The volume SRCE is used as default volume for the dump.
The Advant Controller 400 Series must be in CONFIGURATION mode and PC must be
undimensioned. The data base must be populated (loaded).
The command operates in dialog mode and asks for the dump name if not specified.
Press <Ctrl-Break> to leave the function.
The LOTPT command checks that the PC dump is taken from the same type of Advant
Controller 400 Series as the system to which the load attempt is being made. If this is not the
case, an error message appears and execution of the command is terminated.
As previously mentioned, the PC dump also includes information on the PC area at the time of
dumping and how the area is used.
The load command offers the option of redimensioning the PC area as follows:
RE-DIMENSION? (Y/N/Q)
If you want to redimension, answer Y, and the dimensioning command is started. With its
help, you can then dimension the PC area to the required size (but not less than the area required
by the dump) or increase the number of PC programs. If the User Disk Application Segments
backup function must be redimensioned, dimension it as the SUDAS command responded,
when the saving procedure failed. When dimensioning is finished, the load command continues
to load the PC area of the Advant Controller 400 Series.
If you do not want to redimension the PC, answer N and the Advant Controller 400 Series
uses the old dimensioning.
If you answer Q, the command terminates.
After loading is complete, the loaded PC programs are checked. If the backup function for the
User Disk Application Segments is activated, the first backup to the Advant Controller 400
Series can be performed.
3BSE 002 417R601
7-17
7.5 Data Transfer via Source Code

You can use the source code handling function to move a complete application (one or more PC
programs, and the data base) or only a data base between:
Different engineering tools
On-line Builder
Function Chart Builder.
Different target systems
MasterPiece 200/1 process stations
MasterPiece 200 process stations
Advant Station 500 Series Operator Station (a subset of data base elements only)
MasterView 800/1 Operator Station (a subset of data base elements only).
The following commands are available to work with source code:
TRDBS (TRanslate Data Base Source). This command translates and loads the data base
source code into the target system.
DUDBS (DUmp Data Base Source). This command dumps the data base source code.
TRPCS (TRanslate PC Source). This command translates and loads the PC source code
(one or more PC programs) into the target system.
DUPCS (DUmp PC Source). This command dumps the PC source code (one or more PC
programs).
The source code dumps contain all of the applications important data, but not the *.TC, *.TB
and *.TI files (see Section 7.2.2.1, List of User Disk Application Segments). See the Source
Code Handling Users Guide for more information on the above commands and the source code
definitions.
NOTE
Data tables belonging to a data base element of type TBL_CLASS are only
included if the parameter /TBL is selected when creating the DB source code
dump. Otherwise, if the application contains such tables, you can transfer them
using the DUDB and LODB commands. The logical file 302 contains these tables
and the concept name is TBL_DATA.
7-18
3BSE 002 417R601
6HFWLRQ /RDGLQJ$$%)LOHV
7.6 Loading AAB Files

For Dumping and Loading of AAB Files the following commands are available:
DAABF - DUMP AAB FILE
LAABF - LOAD AAB FILE.
DUMPFILE
LOADFILE.
DAABF - DUMP AAB FILE

Syntax:
DAABF [volume]:segment,name
Description:
"volume"
destination volume; default is SRCE
"segment"
Name of the segment to be dumped
"name"
Name of the database element from which the data should be dumped.
Name can be either the element name or the element id.
This command is used to dump an instance of database element AAB_FILE to an AAB file on
the harddisk. If the command is given without parameters, parameters are requested in a dialog.
LAABF - LOAD AAB FILE
Syntax:
LAABF [volume]:segment,name/option
Description:
volume
source volume; default is SRCE
segment
segment to be loaded
name
Name of the database element to which the data should be loaded.

Element_name can be either the element name or the element id
option
UNLOCK - unlock a file that is still locked.
This command is used to copy an AAB file to the database. If the command is given without
parameters, parameters are requested in a dialog.
LOADFILE
Syntax:
LOADFILE name[,filename] [/option]
where
name
Name of the data base element of type AAB_FILE into which filename shall
be loaded.
filename
Either: volume:segment.extension
Or: a valid DOS path and filename.
3BSE 002 417R601
7-19
option
FUZZYCON - tells the command that the file contains a configuration for the
fuzzy control PC element.
The LOADFILE command loads the contents of filename into the data base element name of
type AAB_FILE. This command is needed, when - for example - User Defined PC Elements
shall be loaded to Advant Controller 400 Series. For more information see User Defined PC
Elements Users Guide.
DUMPFILE
Syntax:
DUMPFILE filename[,name]
where
filename
Volume:segment.extension
name
Name of the data base element of type AAB_FILE which shall be dumped.
The DUMPFILE command dumps the contents of data base element name of type AAB_FILE
into the segment filename. This command is needed, when - for example - User Defined PC
Elements shall be dumped from Advant Controller 400 Series. For more information see User
Defined PC Elements Users Guide.
7.7 Summary of Dump Commands

You can dump your application programs - as described in the foregoing sections - with several
commands. But it may be necessary to store other segments in addition to the dump segments,
e.g. if you want to transfer the dump to another node. A DUAP dump for example does not
include the User Disk Application Segments, if the User Disk Application Segments Backup
Area is not dimensioned. Therefore it is necessary if you want to store a complete application
program, to store the DUAP dump and the User Disk Application Segments together.
Complete
Application
Program
Dump
Segment(s)
eventually
other
Segment(s)
Table 7-1 shows which additional segments exist for a certain dump. Each row represent a
complete set of application data. If you want to save the additional segments, use the RUDAS
command, then backup the segments. The Additional Segments (ONB) are segments that are
produced by On-line Builder commands, for example when you modify document texts.
The segments listed under Additional Segments (FCB) are originally produced by the Function
Chart Builder and then converted to ABB Master representation. They contain information
about type circuits. For more information see Function Chart Builder Users Guide.
7-20
3BSE 002 417R601
6HFWLRQ 6XPPDU\RI'XPS&RPPDQGV
Table 7-1. Summary of Dump Commands

Dump Type
Source Code
DB Segments
PC Segments
Additional Segments Additional Segments

(ONB)
(FCB)
Command: DUDBS Command: DUPCS

SRCE:*.BA
SRCE:*.AA
For Redimensioning Command: DUTDB Command: DUTPT
USER:PCMASS.SM,
PCMASS*.AP,
P1PCMASS.NI
These segments
include:
Segments forType
Circuits
USER:*.TB,*.TC,
*.TI
Segments forType
Circuits
USER:*.TB,*.TC,
*.TI
PC instance names,
PC variable names,
Document texts,
Page layout,
ONB printer
parameters,
Variables used by
GETAB
DUAP; Backup Area Command DUAP
not dimensioned
USER:PCMASS.SM,
PCMASS*.AP
P1PCMASS.NI
These segments
include:
Segments forType
Circuits
USER:*.TB,*.TC,
*.TI
PC instance names,
PC variable names,
Document texts,
Page layout,
ONB printer
parameters,
Variables used by
GETAB
DUAP with
dimensioned
Backup Area
3BSE 002 417R601
Command DUAP
7-21
7-22
3BSE 002 417R601
6HFWLRQ +HOS)XQFWLRQ
Chapter 8 General Commands
8.1 Help Function

HELP
The HELP command gives you information about the commands that are available. It covers
syntax definition, description and a number of examples. The examples include comments for
clarification.
Syntax:
+(/3 [+(/3|/&200$1'6|/&0'|/$//]
+(/3 [command_name]
Examples:
To get general information about HELP, enter:
#+(/3
or
#+(/3 +(/3
To get a list of available commands, enter:
#+(/3 /&200$1'6
or
#+(/3 /&0'
To get a list of available commands and keywords, enter:
#+(/3 /$//
To get the help text of a command, for example LDBD, enter:
#+(/3 /'%'
To get the help text of a keyword, for example LEXICALS, enter:
#+(/3 /(;,&$/6
You can get a list of available PC elements or DB elements (when
connected with an Advant Controller 400 Series):
#+(/3'%(/
#+(/33&(/
3BSE 002 417R601
8-1
&KDSWHU *HQHUDO&RPPDQGV
8.2 Adjusting Date and Time

RTIME
Use the RTIME (Read Time) command to display the current system time.
STIME
You set the system time with the STIME (Set Time) command. If minutes and seconds are
omitted, they are set to zero.
Syntax:
57,0(
Syntax:
67,0( hour:[minute]:[second]
This command sets the system time.
hour
is hours (0 to 23)
minute
is minutes (0 to 59)
second
is seconds (0 to 59)
Example:
#57,0(
TARGET SYSTEM:
#67,0(
TIME INSTALLED
#57,0(
TARGET SYSTEM:
TIME (HH:MM:SS)=15:23:10
RDATIME
Use the RDATIME (Read DAte and TIME) command to read the current date and time of the
system.
Syntax:
5'$7,0(
SDATIME
The SDATIME (Set DAte and TIME) command sets the date and time of the system.
Syntax:
6'$7,0( year-month-day/hour:[minute]:[second]
8-2
3BSE 002 417R601
6HFWLRQ *HWWLQJWKH/DVW,WHP'HVLJQDWLRQ
This command sets the system date and time.

year
is year (a four-digit integer like 1993)
month
is month (1...12)
day
is date (1...31)
hour
is hours (0...23)
minute
is minutes (0...59)
second
is seconds (0...59)
If either minute or second is unspecified, it is set to zero.

Example:
#5'$7,/0(
TARGET SYSTEM: DATE (YYYY-MM-DD)
=1984-08-16
#6'$7,0(
DATE AND TIME INSTALLED
ADTIME
Use the ADTIME (ADjust TIME) command to adjust the system clock. The clock can be
adjusted by +/- 100 seconds.
Syntax:
$'7,0( offset
To ensure that the process control is disturbed as little as possible, this adjustment is done
gradually over an interval about 10 times as long as the requested adjustment. For this reason, an
RTIME requested immediately after an ADTIME may give an incorrect reading.
8.3 Getting the Last Item Designation

GLID
The GLID (Get Last Item Designation) command displays the last item designation given in a
PC command.
Syntax:
*/,'
This command displays the last referenced item designation in a PC program. It can be useful in
establishing the item designation if you use only a partial designation in a command.
For example, if GLID is PC1.3.4 and you only specify .5 as the designation in the next
command, the system assumes that the entire designation is 1.3.5.
3BSE 002 417R601
8-3
8.4 Repeating the Previous Command

; (Semicolon)
The semicolon key (;) repeats the previous command.
Syntax:

You can even recall the last entered 24 commands using the arrow (arrow up, arrow down) keys.
8.5 Hardcopy
HARDCOPY
The HARDCOPY command gives you a printout of the current screen display. This command
is not available for all On-line Builder implementations.
Syntax:
+$5'&23< [21|2))]
Description:
You can use this command to route data from the engineering station screen to the printer
connected to it. It can be used in three ways:
1.
Copy current contents of screen to printer.
2.
From now on, copy all incoming data to printer.
3.
Stop copying data to printer.
8.6 Terminating a Session

TSESS
Use the TSESS (Terminate SESSion) command to terminate the current session and to choose
other alternatives from the start-up menus afterwards.
Syntax:
76(66
8.7 Choosing Graphical or Non-graphical Presentation

SLG, SLNG
The SLG (SeLect Graphical mode) and SLNG (SeLect Non-Graphical mode) commands
interfere with the IS, C and CU commands. The default setting is graphical presentation.
Syntax:
6/*
6/1*
8-4
3BSE 002 417R601
6HFWLRQ /LVWLQJ7H[W6HJPHQWV
8.8 Listing Text Segments

LIST
The LIST command provides output to the console screen and/or to the printer from one or
more text segments (files) on a volume. Examples of text segments are command files, source
code files and DUAP dumps.
Syntax:
/,67 [volume]:[segment]=line1][>line2][;option]
This command lists a segment. Segment may contain wildcards.
volume:
If this parameter is omitted, it invokes the default value, but a specified

parameter value does not update the default value. The : delimiter after this
parameter must always be specified in the LIST command.
segment:
If this parameter is omitted, it invokes the default value, but a specified

parameter value does not update the default value. A segment set is specified
by one or more wildcards in this parameter field.
line1:
Specifies the segment line from which the output is to start. If this parameter
is omitted, the first segment line is taken as the first output line. A line1
parameter value must be preceded by the = delimiter.
line2:
Specifies which segment line will be the last output line. If this parameter is
omitted, the last segment line is taken as the last output line. A line2 parameter
value must be preceded by the > delimiter and the line1 parameter.
option:
This parameter comprises keywords as follows:
Console screen is the output medium.
Printer is the output medium. The default output medium is C.
Specifies the addition of line numbers to the output.
Prevents the standard output of file header and the initial form feed.
The first option keyword must be preceded by the ; delimiter. Several keywords must be
separated by the , delimiter.
Examples:
#/,6765&(3&$$3
#/,6765&( $ !3&1
3BSE 002 417R601
8-5
8.9 Locking/Unlocking PC Programs

LOCK, UNLOCK
Syntax:
/2&. pc_pgm
You can use this command to set a password on a PC program to avoid unauthorized listing,
reading and changing of the PC program. One or more PC programs can be locked without
disturbing the execution. A password must be at least four, but no longer than 10, characters.
Digits, uppercase and lowercase letters, and underscores are allowed in a password. Uppercase
and lowercase letters are not considered equal.
Syntax:
81/2&. pc_pgm
You can use this command to unlock a PC program that has been locked with the LOCK
command. On a locked PC program, you can perform the following actions:
Dump and load the PC program using the commands DUTPT, LOTPT, DUAP and
LOAP.
Enter and exit BUILD mode, as well as deblock and block the entire PC program, using
the commands EBM, DIBM, DBL, BL and BLRS.
List the status of the PC program by issuing the command LSS. A locked PC program is
listed as a whole. No information is obtained about execution units.
The commands prompt for the password which must consist of at least four, and at the most 10,
characters. Uppercase and lowercase characters are deemed different.
Example:
You want to print out the PC diagram of the locked PC program PC1.
Example:
#81/2&.3&
PASSWORD:

PROGRAM IS UNLOCKED
#/3&'3&
....
#/2&.3&
PASSWORD:

VERIFICATION:
PROGRAM IS LOCKED
#
8-6
3BSE 002 417R601
6HFWLRQ *HQHUDO
Chapter 9 Communication Between PC Programs and Nodes
9.1 General
Special data base elements (DAT, TEXT, DS, DSP, MS and TS) are available in the Advant
Controller 400 Series to set up communication between different PC programs or between
different nodes. Use DAT or TEXT data base elements of the needed data type to communicate
between PC programs of one node. When you want to send data to another Advant
Controller 400 Series node, the DS, MS or TS communication DB element is necessary in
addition. You can use the DSP or MS communication DB element when communicating with an
Advant Controller 100 Series.
In addition to standard DSP communication fast DSP communication is available as an
alternative. The PC elements DSP-S and DSP-R are used for a fast communication between the
AF100 interface module CI520 and the PC program.
Use the MS communication DB element when communicating with nodes of other types.
The communication elements define a packet of several DAT DB elements, except the TS DB
element, which only references one TEXT DB element, to transfer them as a set to the other
node (see Data Base Elements Advant Controller 400 Series Reference Manual).
The following characteristics apply:
3BSE 002 417R601
Data Set communication requires the DS, DSP, MS or TS data base element at the sending
node and the corresponding data base element at the receiving node.
The set of DAT DB elements at the node being communicated with is of the same type and
number and is sorted in a way identical to the way it is sorted at the sending node.
The TEXT DB element in the sending and the receiving nodes must be of the same type.
The data transfer runs cyclically between the data bases at different nodes, except for Text
Set, where the data is sent event-driven.
All DS, DSP, MS or TS DB elements must be numbered in unbroken sequence starting at

number one, i.e., DS1 and MS1. Pay particular attention to this during source code
handling of the data base.
9-1
&KDSWHU &RPPXQLFDWLRQ%HWZHHQ3&3URJUDPVDQG1RGHV
PC 1
DAT
PC 2
B
I
IL
R
TEXT
20
48
72
Figure 9-1. Communication between PC Programs
PC program
PC program
Data Base
Data Base
AI
AO
AI
AO
DI
DO
DI
DO
TEXT DAT
20, 48, 72
DAT TEXT
B, I, IL, R
DS
20, 48, 72
B, I, IL, R
MasterNet
Comm.
MasterNet
Comm.
TS
DS
TS
Figure 9-2. Data Set and Text Set Communication via MasterNet
9-2
3BSE 002 417R601
6HFWLRQ *HQHUDO
PC program
PC program
Data base
Data base
AI
AO
AI
AO
DI
DO
DI
DO
DAT
DAT
B, I, IL, R
DSP
Advant
Fieldbus
Comm.
B, I, IL, R
Advant
Fieldbus
Comm.
DSP
Figure 9-3. Data Set Peripheral Communication via Advant Fieldbus 100
Advant Controller 100 or 400 Series
PC program
PC program
Data base
Data base
AI
AO
AI
AO
DI
DO
DI
DO
DAT
DAT
B, I, IL, R
RCOM
RCOM
Comm.
Comm.
MS
B, I, IL, R
MS
Figure 9-4. MVI Data Set Communication via RCOM
3BSE 002 417R601
9-3
The following sections provide examples of how to use the DS DB element in different
situations. The examples are, to a large extent, applicable for the other Data Set data base
elements DSP, MS and TS.
The TS data base element differs from the other data base elements when it contains only one
reference to TEXT data and does not include a terminal for setting of the transmission interval.
Instead, the PC element SENDREQ is used when requesting transmission of a TS element.
With that exception noted, you can use the first example as a recipe for the necessary steps to
take to set up a Text Set communication.
9.2 Example 1: Transferring Data to Another Node using DS Elements

This example is to a large extent applicable for the DSP, MS and TS data base elements. See the
Data Base Elements Advant Controller 400 Series Reference Manual for differences between
the data base elements.
Assume the following situation:
Node 1
Network11
DAT (B)
DAT (I)
DAT (IL)
DAT (R)
Figure 9-5. DAT DB Elements in Node 1, Network 11

In node 1, network 11, there are a number of DAT DB elements you want to send to another
node.
Create the DS DB element and define the DAT packet and the destination node identification
number (in the receiving mode, the number of the node sending the packet is defined in the
same way).
When creating the DS DB element, you also state parameters that control the function of the
Data Set.
When the DS DB elements are created, references are automatically linked to the DAT DB
elements that are to be included in the packet sent. These are shown in the DS DB element (see
Section 9.3, Example 2: Expanding a Data Set).
9-4
3BSE 002 417R601
6HFWLRQ ([DPSOH7UDQVIHUULQJ'DWDWR$QRWKHU1RGHXVLQJ'6(OHPHQWV
There are seven steps in setting up communication for this example:

1.
Configure MasterNet for both nodes.
2.
Dimension the data base at node 1.
3.
Create DS DB elements at node 1.
4.
Dimension PC at node 1.
5.
Build the PC program at node 1.
6.
Perform steps 2, 3, 4 and 5 for node 2.
7.
Start communication.
DO 1.1
DO 1.1
DI 1.1
1
2
AND
(2)
DAT1
20
DS1
Network 11,
Node 1
DS1
DAT1
1
D=0 2
DAT2
DS2
Network 11,
Node 2
DS2
OR
(2)
DAT2
Node 2
Node 1
Figure 9-6. Data Transmission via MasterNet

The steps are described in detail below:
1.
Configure MasterNet for both nodes. Follow the instructions in 0DVWHU1HW8VHUV*XLGH.
2.
Dimension the data base at node 1 (see Figure 3-1 and Figure 3-4):
#',0'%
a.
State the relevant number of I/O boards and signals in the same way as in
Appendix A, Working Example.
b.
Expand section S2 and state the number of DAT DB elements and the number of DS
DB elements.
There are four types of DAT DB elements:
3BSE 002 417R601
DAT(B)
Where 32 Boolean values can be stored in each DAT(B) DB element.
DAT(I)
Where one value of the data type integer can be stored in each DAT(I) DB
element.
DAT(IL)
Where one value of the data type integer, long word can be stored in each
DAT(IL) DB element.
DAT(R)
Where one value of the data type real number can be stored in each DAT(R)
DB element.
9-5
In the example shown here, two Boolean values are handled, one from AND(2) and one from
OR(2). As a precaution, you can dimension for future needs and specify 20 DAT, for instance:
? 0
Number of DAT values:0 New value:
In this example two DS DB elements are neededone DS DB element to send data to node 2
and one to receive data from node 2. Here too, you can dimension for future needs and specify
20 DS, for instance:
Number of DS:0 New value:
Transfer the dimensioning to the target system with the DIM subcommand.
3.
Create DS DB elements at node 1:
#CRDB DS
DS1
Data Set Descr
(109.1)
DS1
0
0
0
0
0
0
0
RECEIVE
0
1
1
4
YES
1
2
3
4
5
6
7
9
10
12
13
14
15
18
NAME
ACT
IDENT
NO BREC
NO INT
NO INTL
NO REAL
USER
SOURCE
BLOCKED
NET
NODE
SCAN_FTR
SORT REF
S2
Value references
S3
Value references
VALID
ERR
Figure 9-7. A DS DB Element

a.
Enter the identity (terminal IDENT) and the number of DAT(B) DB elements to be
sent (terminal NO_BREC). Two Data Sets that communicate with each other must
have the same identity. In this example, IDENT=1. Fill in USER=1 for Data Set
communication.
? (QWHU!
? (QWHU!
? 0(QWHU!
IDENT:0
NO_BREC:0
NO_INT:0
NO_INTL:0
NO_REAL:0
USER=
9-6
New
New
New
New
New
value:
value:
value:
value:
value:
3BSE 002 417R601
6HFWLRQ ([DPSOH7UDQVIHUULQJ'DWDWR$QRWKHU1RGHXVLQJ'6(OHPHQWV
Fill in the other terminals of the DB element:

b.
SOURCE must have the value S (Send) for sender and R (Receive) for receiver.
c.
NET gives the network number (1 - 127) for the node to which the message is being
sent (or is being transferred from, if DS is a receiver).
d.
NODE gives the node (1 - 127) to which the message is being sent (or is being
transferred from, if DS is a receiver).
e.
SCAN_FTR influences the transmission interval. A scan factor of 4, for example,

gives a transmission time four times as long as a scan factor of 1. It is important to
distinguish between scan factor (SCAN_FTR) and the basic cycle time of DS, which
is 0.5 seconds (by default). The interval on transmission is equal to the basic cycle
time multiplied by the scan factor.
When everything is filled in, use the subcommand >> or END to proceed. The subordinate
DAT DB elements are then created. In this example, it is one DB element, DAT 1, according to
the definition of the number of DAT DB elements given when the number of NO_BRECs was
filled in.
DAT1/DS1.B1
Boolean Data
(110.1)
> DAT1
S2
NAME
VALID
VALUE
VALUE2
VALUE3
VALUE4
VALUE5
VALUE6
VALUE7
VALUE8
VALUE9
VALUE10
VALUE11
VALUE12
VALUE13
VALUE14
VALUE15
VALUE16
2
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
When Data Set

communication
is started, the
Boolean value
sent is
shown here.
VALUE17--VALUE32
Figure 9-8. A DAT DB Element

Create DS2 and DAT2 in the same way. DS2 at node 1 (see Figure 9-6) has identity 2 and is the
receiver (SOURCE = R). The sending node is stated at the NODE input, i.e., NODE=2.
The network number (=11) of the sending node is stated at the NET input. The other terminals
are filled in as for DS1.
4.
3BSE 002 417R601
Dimension PC at node 1 with DIMPC (see Section 3.4, PC Dimensioning).
9-7
5. Build the PC program at node 1.

#,63&
Local data: 100%
PC1 ?
3&3*0
PC1.1 ? &21750
PC1.1.1 $1'
PC1.1.1 ?
#&3&
PC1
:1 '
:2 '
:5
PC1.1
:1 '
:2 '
:3 '
:5
:6
PC1.1.1
:1 =',
:2 -='$7
:20 =''$7
6.
Perform steps 2, 3, 4 and 5 for node 2. Carry out dimensioning, populating the data base
and building the PC program in the same way as for node 1.
7. Start communication. Do the following at both nodes:

#',&21),*
#',%03&
#'%/3&
Activate the DS DB elements to start transmission of data between the systems. Begin by
activating the receiving DB elements.
Modify DS1 and DS2 in node 1 and in node 2: Set terminal ACT=1.
Node 1
#0'%'6
...
Node 2
#0'%'6
...
Node 1
#0'%'6
...
Node 2
#0'%'6
...
9-8
3BSE 002 417R601
6HFWLRQ ([DPSOH([SDQGLQJD'DWD6HW
9.3 Example 2: Expanding a Data Set

In this example, an existing Data Set is expanded.
Node 1
Network 11
Node 2
DS1
Network 11
DS1
DAT1/DS1.B1
DAT1/DS1.B1
AND
DAT2/DS1.R1
DAT2/DS1.R1
DATXX
DAT10
S
Figure 9-9. Expanded Data Set

The values DS1.B1 and DS1.R1 are sent to DS1.
The value DAT10 is to be added to this Data Set.
Procedure at node 1:
#0'%'6
3BSE 002 417R601
9-9
Change to DAT10:
DS1
Data Set Descr
(109.1)
&KDQJHWR
'$7
S1
DS1.B1
DS1.R1
>
8(1)
8(2)
8(3)
8(4)
8(5)
8(6)
8(7)
8(8)
8(9)
8(10)
8(11)
8(12)
S3
Base part
REF1
REF2
REF3
REF4
REF5
REF6
REF7
REF8
REF9
REF10
REF11
REF12
Value references
Figure 9-10. Expanded Section 2 of a DS DB Element

?0
REF3 : 0 New value :'$7
Procedure at node 2:
1.
Create a new DAT DB element.
2.
Enter the command:

0'%'6
3.
Connect the newly created DAT DB element to the first free REF terminal.
9.4 Example 3: DAT DB Elements Present but no DS DB Elements

When data is to be sent to another node, it is likely there are DAT DB elements already.
A DS DB element that sends data to the receiving node, however, must be created. Do the
following:
1.
Create a DS DB element with CRDB DS. Set the terminals NO_BREC to NO_REAL=0 to
prevent new DAT DB elements from being created automatically. Fill in the other
parameters as in Example 1.
2.
Link the existing DAT DB elements to the newly created DS DB element. Use the
command MDB DS1, go down to the first segment VALUE REFERENCES and fill in:
? 0
REF1
REF2
8(1)
8(2)
9-10
: 0 New value :'$7

: 0 New value :'$7
REF1 = '$7
REF2 = '$7

etc.
3BSE 002 417R601
6HFWLRQ &RQILJXUDWLRQRI(YHQW6HW
Chapter 10 Event Set Handling
10.1 Configuration of Event Set

The Event Set is used to transport time tagged events from the Advant Controller 100 Series to
the Advant Controller 400 Series using Advant Fieldbus 100 or RCOM. Time synchronization
messages are sent over the communication bus (Advant Fieldbus 100 or RCOM) so time is
synchronized in all communicating stations/nodes.
Each Event Set can handle up to 32 event channels. The event can be of analog or digital type.
The event channels can be mixed in arbitrary order.
10.1.1 Event Set Overview

Event Set (EVS) elements group a set of event channels for sending and receiving events.
EVS elements must be configured in both the Advant Controller 400 Series (receive) and in the
Advant Controller 100 Series (send).
The EVS(R) element is used in the Advant Controller 400 Series to receive Event Set.
One Advant Controller 400 Series can handle up to 511 EVS(R) elements.
EVS(S) is used in the Advant Controller 100 Series to send Event Set. EVS(T) is used in the
Advant Controller 100 Series to transit (receiving and sending) an Event Set when the sending
Event Set is physically located in another node not reachable from the Advant Controller 400
Series. The Advant Controller 100 Series then acts as a transit node. EVS(T) is only applicable
when you are using hierarchical RCOM communication. One Advant Controller 100 Series can
handle up to 16 EVS(S) or EVS(T) elements.
The EVS(R) element refers to the opposite sending EVS(S) or EVS(T) element. The EVS(T)
element refers to the opposite sending EVS(S) element. This is done by specifying the address
(bus/net and station/node number) and the identity of the EVS(S) or EVS(T) element.
See Figure 10-1 for an overview of the EVS data base elements relationships.
AC 400 Series
AC 100 Series
EVS(R)
EVS(T)
EVS(R)
EVS(S)
AC 100 Series
EVS(S)
Figure 10-1. Event Set (EVS) Element Relationship
3BSE 002 417R601
10-1
&KDSWHU (YHQW6HW+DQGOLQJ
It is important to specify the same event type (AI or DI) on the corresponding reference terminal
(REF1 - REF32) on both sides (Advant Controller 100 Series and Advant Controller 400 Series)
in the Event Set elements EVS(R) and EVS(S). The EVS(T) element does not contain any
references to event channel elements when it only transits the Event Set further.
The EVS(R) element contains references to channel elements receiving events (AIEV and
DIEV). The EVS(S) element contains references to the channel elements performing the time
tagging (AIC and DIC), channel elements reading time tagged data from a hardware module
(i.e., DI650), or event data received from MasterPiece 40 (AIMVB and DIMVB).
See Figure 10-2 for an overview of the relationship between event channels in the Advant
Controller 400 Series and event channels in the Advant Controller 100 Series.
AC 400 Series
AC 100 Series
AIEV
AIC
AIEV
AIMVB
DIEV
DIC
DIEV
DIMVB
DIEV
DIS65x
Figure 10-2. Event Channel Relationship

The allowed configuration alternatives for Event Set depend on the chosen communication
(Advant Fieldbus 100 or RCOM).
Advant Fieldbus 100 allows for communicating Event Sets from Advant Controller 100 Series
stations to Advant Controller 400 Series stations on the same bus. It does not allow for a
hierarchical communication structure (no EVS(T)). See Figure 10-3 for a configuration example
using Advant Fieldbus 100.
RCOM allows for communicating Event Sets hierarchically between nodes. The EVS(T)
element is used in the middle node to transit an Event Set further. See Figure 10-4 for a
configuration example using RCOM.
10-2
3BSE 002 417R601
6HFWLRQ (YHQW6HW2YHUYLHZ
AC 400 Series
AC 100 Series
AIEV1
80
11
AIC1
AIEV
DIEV1
From station 11
DIEV
AIC
EVS1
EVS1
DIC3
EVS(R)
EVS(S)
DIC
DIEV2
DI1001.1
DIEV
DIS650
DIEV3
AF 100
DIEV
AC 100 Series
From station 12
DIEV4
EVS2
DIEV
EVS(R)
12
DI1002.4
From station 21
AIEV2
EVS3
AIEV
EVS(R)
DIS650
EVS1
DIC5
EVS(S)
DIC
AC 100 Series
21
EVS1
AIC1
EVS(S)
AIC
EVS element communication and relationship

AF 100 communication
Figure 10-3. Overview, Event Set Configuration using Advant Fieldbus 100
3BSE 002 417R601
10-3
AC 400 Series
AC 100 Series
AIEV1
AIC1
11
AIEV
From node 11
AIC
DIEV1
EVS1
DIEV
EVS(R)
EVS1
DIC3
EVS(S)
DIC
DIEV2
DI1001.1
DIEV
DIS650
DIEV3
RCOM
DIEV
AC 100 Series
From node 12
DIEV4
EVS2
DIEV
EVS(R)
DI1002.4
12
From node 21
via node 12
AIEV2
EVS3
AIEV
EVS(R)
DIS650
EVS1
DIC5
EVS(S)
DIC
EVS2
EVS(T)
From node 21
RCOM
AC 100 Series
21
EVS1
AIC1
EVS(S)
AIC
EVS element communication and relationship

RCOM communication
Figure 10-4. Overview, Event Set Configuration using RCOM
10-4
3BSE 002 417R601
6HFWLRQ &RQILJXUDWLRQRI(YHQW6HWLQ$GYDQW&RQWUROOHU6HULHV
10.1.2 Configuration of Event Set in Advant Controller 400 Series

This section gives a detailed description of how to configure Event Set in the Advant
Controller 400 Series. You can find information about configuration of Event Set in the Advant
Controller 100 Series in the corresponding documentation for the Advant Controller 100 Series.
The following sections describe how to:
1.
Dimension the data base for Event Set handling.
2.
Create and configure the event channel elements AIEV and DIEV.
3.
Create and configure the Event Set Receive element EVS(R).
10.1.2.1 Dimension the Data Base for Event Set Handling

The first step is to dimension the data base with the planned number of Event Sets EVS(R) and
the event channel elements of type AIEV and DIEV. There is an dimensioning entry in the
DIMDB picture for Event Sets (see Figure 3-4)
Fill in the terminal Number of EVENT SETS with the number of Event Sets to be received
from other stations/nodes. Up to 511 EVS(R) elements can be configured in the Advant
Controller 400 Series. To dimension for the EVS(R) elements in Figure 10-3 or Figure 10-4,
three should be entered.
Add the total number of analog event channels, planned for all Event Sets, to terminal Number
of AI_SIGNALS. To dimension for the AIEV elements in Figure 10-3 or Figure 10-4, two
more AI signals should be added. If 32 AI signals were planned before, the new figure should be
34 instead.
Add the total number of digital event channels, planned for all Event Sets, to terminal Number
of DI_SIGNALS. To dimension for the DIEV elements in Figure 10-3 or Figure 10-4, four
more DI signals should be added. If 108 DI signals were planned before, the new figure should
be 112 instead.
10.1.2.2 Create the Event Channel Elements AIEV, DIEV

Create one data base element for each individual event channel to receive an event from, for
example, one data base element (AIEV or DIEV) per event channel (source) delivering time
tagged events. Use the AIEV element if an analog event type is to be received and the DIEV
element if digital event type is to be received.
It is not accidental that the AIEV and DIEV elements look like the AIC and DIC elements.
There is, however, one main difference between the elementsthe VALUE terminal is not
updated by the Event Set handler. The VALUE, ERR and other related terminals are included to
make it possible to transfer the dynamic process value separately, i.e., by using the Data Set.
3BSE 002 417R601
10-5
Peripheral (DSP) communication on Advant Fieldbus 100 and MVI Data Set (MS)
communication on RCOM.
AIEV1
AI Event
(6.1)
AIEV1
1
0
%
0
1
21
24
3
44
NAME
ACT
BLOCKED
UNIT
TESTED
Limit
check
S2
VALUE
ERR
UPDATED
19
22
23
S3 Operator functions
S4 Operator functions
E5 Group Alarm
Figure 10-5. Base part of Data Base Element AIEV in Advant Controller 400 Series
Fill in the name of the event channel on terminal NAME, preferably the same name as in the
corresponding event channel (event source) element in the Advant Controller 100 Series. You
can fill in the other terminals within the Base part section where applicable.
You can fill terminals in the Limit check section if the VALUE terminal is updated separately by
an application program using the DSP or MS communication for data transfer.
The Operator functions sections contain terminals to configure the treatment and handling of the
event channel in the operator station. The LIM_1_TR and LIM_2_TR for AIEV and
VALUE_TR for the DIEV element are, by default, set to report the received events as an event,
but not as an alarm. If you want alarm handling, these terminals must be updated. The other
terminals in these two sections can be configured where applicable to the application (object
display, process sectioning, treatment and more).
10-6
3BSE 002 417R601
6HFWLRQ &RQILJXUDWLRQRI(YHQW6HWLQ$GYDQW&RQWUROOHU6HULHV
10.1.2.3 Create the Event Set Element EVS(R)

The next step is to create the EVS(R) elements, refer to the above created event channel
elements and connect EVS(R) to the opposite EVS(S) element.
EVS4
EVent Set (Receive)
(351.4)
EVS4
1
19
NAME
ACT
WARNING
22
ERR
20
IDENT
15
QUEUE
S_USER
S_BUS
S_STN
NO_AI
17
S_IDENT
NO_DI
16
S2
Event References
S3
Event References
Figure 10-6. Base Part of Data Base Element EVS(R) in Advant Controller 400 Series
Fill in terminal S_USER with the communication type being used, 0 (=Advant Fieldbus 100) or
3 (=RCOM). Terminal S_BUS and S_STN specify the source for this Event Set (EVS(S) or
EVS(T)) in AC110. Fill in the terminals with the bus and station numbers for Advant
Fieldbus 100 or the net and node numbers for RCOM. S_IDENT specifies the identity, terminal
IDENT within the EVS(S) and EVS(T) elements in the Advant Controller 100 Series. See
Figure 10-6 for an example of the EVS(R) element.
The NO_AI and NO_DI terminals indicate the number of filled-in references to AIEV and
DIEV, respectively. These numbers are automatically calculated by the engineering station when
references are added. Corresponding terminals are included in the EVS(S) element to ease the
verification that the same number of AI and DI event channels are referenced. Verification of the
type on each reference terminal must be done manually.
3BSE 002 417R601
10-7
EVS4
EVent Set (Receive)
(351.4)
S1
AIEV4
DIEV1
EV_21
DIEV7
30(1)
30(2)
30(3)
30(4)
30(16)
S3
Base part
REF1
REF2
REF3
REF4
REF16
Event References
Figure 10-7. Reference Part of Data Base Element EVS(R) in Advant Controller 400 Series
Fill in the reference terminals (REF1 to REF32) with references to channel elements of type
AIEV or DIEV. The name of the event channel element is specified as the reference, see
Figure 10-7. It is important to specify the same type of channel (AI or DI) in EVS(R) and
EVS(S).
If the channel type referenced on terminal REF1 in EVS(S) is an AIC or AIMVB, then the
corresponding element referenced in the EVS(R) element will be of type AIEV. If the channel
type is DIS650, DIS651, DIS652, DIC or DIMVB in EVS(S), the type will be DIEV in EVS(R).
Also see Figure 10-2 for the event channel relationship.
10-8
3BSE 002 417R601

Section 1.1 Working Example
Appendix A Working Example
1.1 Working Example

The following working example shows some basic AMPL configuration steps. The emphasis is
on w Controller 400 Series handling. It begins, however, with a few topics relating to planning
and design.
1.
Define the control task and specify the Advant Controller 400 Series.
2.
Make a draft PC diagram, choosing the PC elements from the PC Elements Advant
Controller 400 Series Reference Manual.
PC1
PCPGM(20)
DI1.1
DI1.2
DI1.3
1
2
3
CONTRM(20)
RUN
ON
SINGLE MODP
R
DI1.4
D=1
1
2
3
DO1.1/
CONTRM_RUN
5
6
.1
&
20
DO1.2/
FLASH
Figure A-1. Part of a Draft PC Diagram

3.
3BSE 002 417R601
Start the Advant Controller 400 Series:
The start mode selector must be set to CLEAR (cold start) if the system has not been
configured.
Switch on the power at the main switch of the cabinet.
When the display on the processor board shows P2, set the start mode selector to
AUTO.
Press the ENTER button. The display shows P2.
4.
Connect the engineering station to the Advant Controller 400 Series.
5.
Start the engineering station by following the instructions in the appropriate users guide.
6.
Dimension the data base with the command DIMDB (see Figure 3-1).
A-1

Perform the following inputs:

?
?
?
? 0
Number of DI BOARDS: 0
Number of DO BOARDS: 0
Number of AI SIGNALS: 0
Number of AO SIGNALS: 0
Number of DI SIGNALS: 0
Number of DO SIGNALS: 0
New
New
New
New
New
New
Value:
Value:
Value:
Value:
Value:
Value:

The data base is dimensioned for digital input signals and digital output boards. For this,
one digital input board with, for example, 32 signals and one digital output board with 16
signals are needed. Note that you must dimension for all signals of a board, even if only
some of them are currently used. Use the subcommand M to go to modify mode.
To return to basic mode, use the subcommand !. Transfer the dimensioning details to the
data base of the target system with the subcommand DIM (see Figure 3-1 for the DIMDB
initial mode picture).
? ',0
Specify wanted spare area size
SPARE AREA = 0kb =
Dimension 100 kilobytes for increasing the data base later on. The Advant Controller 400
Series indicates that dimensioning of the data base has started and that it has been
successfully completed.
7.
Populate the data base using the command CRDB (CReate Data Base).
You can change the default values presented by the system. Use the subcommand M
to change to modify mode. Use the subcommand ! to return to basic mode. You also
generate all subordinated DB elements by giving the subcommand END (or ALL).
Perform the following inputs:
#&5'%'2
?
?
? 0
TYPE:DSDO_110 New value: '6'2B
? !!
? 0
NAME: DO1.1 New value: &21750B581
? !!
? 0
NAME: DO1.2 New value: )/$6+
? (1'
Also create one DI board:
#&5'%',
? (1'
8.
A-2
Create a data base dump with the DUTDB (Dump Total Data Base) command.
3BSE 002 417R601

9.
Dimension the space for PC programs with the command DIMPC (DIMension PC).
Dimension the Advant Controller 400 Series for one PC program (see Figure 3-1):
#',03&
Updating PC data sizes in PC1-PC10
?
? 0
? 10: New value or command:
? ',0
10. Enter the PC elements with the command IS (Insert Statement):
#,63&
Available space in area PC: 489 kbyte DB connection:100%
Local data: 100%
PC1? 3&3*0
PC1.1? &21750
PC1.1.1? $1'
PC1.2?
PC1 PCPGM(20,1)
.1 CONTRM(20,2,0)
.1 AND(3)
.2 ?
PC1?PCPGM(20,1)
PC1.1?CONTRM(20,2)
PC1.1.1?AND(3)
PC1.1.2?!
Figure A-2. Example of the IS Command

11. Connect the PC elements with the command C (Connect). See the following three figures.
&3&
>?
?
PC1
PCPCM(20,1)
1 ON
RUN
2 R
ELEMENT BEING DISPLAYED : PC1
Figure A-3. Example of the Connect Command
3BSE 002 417R601
A-3


PC1
:1 '
:2 '
:5
>?
?
?
.1
CONTRM(20,2,0)
1 ON
RUN
2
SINGLE
MODP
3 R
5
6
ELEMENT BEING DISPLAYED : PC1.1
Figure A-4. Example of the Connect Command (continued)

PC1.1
:1
:2
:3
:5
:6
=',
=',
=',
=&21750B581
.1
>?
?
?
1
2
3
&
20
ELEMENT BEING DISPLAYED : PC1.1

PC1.1.1
:1
Figure A-5. Example of the Connect Command (continued)

PC1.1.1
:1 =',
:2 '
:3 3&
:20 =)/$6+
A-4
3BSE 002 417R601

12. Document the PC program
Initialize printout to printer and console SEOM (SEt Output Medium).
#6(203&
(P= printer, C= console)
In the example, we choose symbolic presentation SLSYM (SeLect SYMbolic

identities).
#6/6<0
Select printout format and number of decimal places SERN (SEt Real Notation).
#6(51
EXPONENTIAL FORMAT? (Y/N)= 1
NUMBER OF DECIMALS =
Set page size SEPS (SEt Page Size).
#6(36
PRINTER WIDTH = 90 =
PAGE HEIGTH = 90 =
Paginate the PC program MPD (Modify Page Division).
#03'3&
PAGE NUMBER TABLE NOT FOUND;
SHOULD ONE BE CREATED? (Y/N) <
13. Document the PC program in the form of a PC diagram with LPCD (List PC Diagram).
#/3&'3&
3BSE 002 417R601
A-5

COMMON IDENTITY :
D=1
D=0
PC1
PCPCM(20,1)
1 ON
RUN
2 R
.1
CONTRM(100,1,0)
1 ON
RUN
5
2
SINGLE
MODP
6
3 R
=DI1.1
=DI1.2
=DI1.3
=DI1.4
1993-12-11/07:07:04
G
D=1
1
2
3
.1
&
P-=DO1.1/CONTRM RUN
20
P-=DO1.2/FLASH
.1
PC1
Figure A-6. Resulting PC Diagram

To test the PC program, switch from CONFIGURATION mode to OPERATION mode.
14. Exit from CONFIGURATION mode with the DICONFIG (DIsable CONFIGuration)
command. Use the DIBM (DIsable Build Mode) command to check that all inputs are
connected.
#',&21),*
OK TO START TARGET SYSTEM? Y/N <
THE TARGET SYSTEM IS NOW IN OPERATION MODE
#',%03&
15. Check the PC program as described in Section 3.6, Disabling the BUILD ModeDIBM and
in Section 3.7, Connecting Unconnected Inputs.
A-6
3BSE 002 417R601

Index
INDEX
A
AAB Files 7-19
AC 100 Series 1-3
AC 400 Series 1-3
ADTIME 8.3
Advant Controller 100 Series 1-3
Advant Controller 400 Series 1-3
Advant Fieldbus 100 5-17
AF 100 1-3
Alternative choices 1-1
ANPER 4-17
APP 2-10
Arguments 1-1
AUTO mode 2-14
B
BAckup of User Disk Application Segments 7-3
BL 4-5
Block 4-5
BLRS 4-5
Bold strings 1-1
Bold strings in screen dialogs 1-1
Brackets 1-1
BUILD mode 3-26
C
C 3-30
CLEAR mode 2-14
Clock Synchronization 5-18
Comma 1-1
Command syntax 1-1
CONFIGURATION mode 2-13, 2-17
Connect 3-30
Connect undefined 3-41
Conventions 1-1
CRDB 3-12
CU 3-41
Cycle time 2-8
Subordinate 2-5
Superior 2-5
System 2-5
DBL 4-5
DDB 3-17
Delete Statement 3-38
DIBM 3-41
DICONFIG 2-18
DIMDB 3-1
Dimension the Backup Area 7-7
Dimension the data base 3-1
DIMP 4-2
DIMPC 3-22
Disable Modify Permission 4-2
DS 3-38
DUAP 7-12
DUTDB 7-15
DUTPT 7-16
DV 4-12, 4-16
E
EBM 3-26
ECONFIG 2-17
EMP 4-2
Enable Modify Permission 4-2
ENTER button 2-14
Enter key 1-1
Event Set 10-1
F
Functional Units 2-4
G
Generate PC Diagram 4-12
GEPCD 4-12
GEPD 6-3
GETAB 4-15
GLID 8.3
GPN 6-6
D
Data Set communication 9-1
Data Storage 7-2
Date 8.2
DB 1-3
DB elements
Independent 2-5
3BSE 002 417R601
H
Hard Page Break 6-2, 6-7 to 6-8
HARDCOPY 8.4
Headline 6-7
HELP 8.1

Index
I
I/O board 2-3
Modifying 5-17
Insert Statement 3-26
Instance Name 4-9
IS 3-26
Italic string 1-1
K
Keyboard Interaction 1-1
MV 4-8
N
Normal strings in screen dialogs 1-1
Numbering 6-2
O
OFFLINE mode 2-13 to 2-14
On-line changes 5-1
OPERATION mode 2-13, 2-18
Options. See Arguments 1-1
L
LDBD 3-17
LGAM 3-19
LIST 8.5
List Modify Permission 4-2
List Special Status 4-6
List statement 3-40
List variable 4-3
LMP 4-2
LOAP 7-13
LOCK 8.6
LOTDB 7-16
LOTPT 7-17
LPCD 6-17
LPCL 6-15
LPN 6-7
LS 3-39
LSS 4-6
LTREE 6-11
LV 4-3
P
P1 2-13
P2 2-13
P3 2-13
P4 2-13
Page Break 6-2, 6-7 to 6-8
Page Division 6-2
Pagination Problems 7-11
Parameters. See Arguments 1-1
Previous command 8.4
R
RDATIME 8.2
RECONFIG 2-19
Redimensioning 7-1
Restrictions for User Disk Application Segments 7-5
Right angle bracket 1-1
RMD 4-13, 4-16
RTIME 8.2
RUDAS 7-9
M
MasterFieldbus 5-18
MasterView 320 5-19
MDB 3-16
MDT 6-10
Memory space 3-9
Misc. Boards 5-19
MNV 4-10
MNV Command and the User Disk Application
Segments 4-11
Modify Name of Variable 4-10
Modify Permission 4-1
Modify Variable 4-8
MPD 6-3
MPH 6-9
MPN 6-6
MSTABS 3-24
ii
S
SAVE 4-16
Screen dialogs 1-1
SDATIME 8.2
Segments 1-3
Semicolon 1-1
SEOM 6-1
SEPS 6-2
SERN 6-1
Session 8.4
SHUDAS 7-10
Slash 1-1
SLG 8.4
SLLEV SYST 2-19
SLNG 8.4
3BSE 002 417R601

Index
SLNUM 6-1
SLSYM 6-1
Soft Page Break 6-2, 6-7 to 6-8
Source Code 7-18
SRCE Volume 7-11
SRCE volume 1-3
Start Modes 2-14
Start module 2-22
Starting Advant Controller 400 Series 2-20
STIME 8.2
STOPPED mode 2-13 to 2-14
Substitutions 1-1
SUDAS 7-8 to 7-9
Switches. See Arguments 1-1
Symbol table 3-24
Syntax 1-1
T
Text Set 9-1
Time 8.2
Total Backup 7-1
TSESS 8.4
U
UNLOCK 8.6
User Disk Application Segments 7-3, 7-5
USER volume 1-3, 7-3
V
Variable Names 7-11
Vertical bar 1-1
Volumes 1-3
W
Working Modes 2-13
3BSE 002 417R601
iii

Index
iv
3BSE 002 417R601
TEXT
3BSE 002 417R601

February 1999
Advant OCS
$03/&RQILJXUDWLRQ
Reference Manual
3BSE 002 417R601
Arial @ 10,0 pt 1iv, 24

Arial @ 12,0 pt 5-5
Arial @ 14,0 pt 1, 4-16, 34
Arial @ 16,0 pt 2-3, 2-6, 2-21
Arial @ 18,0 pt 1, 34
Arial @ 6,0 pt 2, 2
Arial @ 8,0 pt 2-3, 2-6, 2-9, 2-13, 3-27, 5-12
Arial @ 9,0 pt 2-1, 2-3, 2-6, 2-102-11, 2-13, 2-152-19, 2-23, 2-25, 3-2, 3-8, 3-13, 4-4, 4-14, 9-10
Courier @ 10,0 pt 1-31-4, 2-10, 2-172-19, 3-29, 4-13, 7-97-10
Courier @ 8,0 pt 2-3, 2-23, 2-25, 3-143-15, 3-32, 4-4, 4-134-15, 5-6, 5-105-14, 6-16, 9-10, A-6
Courier New @ 10,0 pt 3-2, 3-113-12, 3-14, 3-163-20, 3-22, 3-24, 3-26, 3-283-32, 3-34, 3-373-41, 424-3, 4-54-6, 4-84-17, 5-25-3, 6-1, 6-36-12, 6-146-17, 7-27-3, 7-6, 7-97-10, 7-127-13, 7-15717, 7-21, 8.18.6, 9-59-6, 9-89-10, A-2A-6
Courier New @ 8,0 pt 2-3, 2-6, 2-102-11, 2-21, 4-15
Courier New @ 8,73 pt 3-40
Courier New @ 9,0 pt 3-23-8, 3-133-15, 3-23, 3-27, 3-29, 3-32, 3-37, 3-39, 4-4, 4-7, 4-9, 4-134-16, 565-15, 6-16, 6-18, 9-69-7, 10-6, 10-8A-1, A-3A-4, A-6
Garamond @ 8,0 pt 2-3
HELVETICA @ 10,0 pt i1-3, 2-1, 2-3, 2-62-7, 2-92-21, 2-23, 2-253-1, 3-3, 3-8, 3-103-19, 3-22327, 3-293-30, 3-323-33, 3-353-41, 4-24-17, 5-55-14, 5-186-11, 6-157-1, 7-5, 7-77-17, 7-197-21,
8.18.6, 10-110-4, 10-6iv
HELVETICA @ 12,0 pt i, iiiv, 2-6, 2-8, 2-10, 2-12, 2-22, 2-25, 3-2, 3-4, 3-83-12, 3-163-17, 3-19, 3-26,
3-293-34, 3-363-37, 5-45-5, 5-165-17, 7-57-6, 7-8, 7-11, 10-5, 10-7, iiii
HELVETICA @ 14,0 pt i, 1-12-2, 2-5, 2-8, 2-132-15, 2-172-21, 2-26, 3-1, 3-12, 3-17, 3-203-23, 3253-26, 3-30, 3-383-39, 3-41, 4-14-3, 4-54-7, 4-9, 4-12, 4-15, 4-174-19, 5-15-4, 5-12, 5-145-18,
6-16-3, 6-66-7, 6-96-11, 6-15, 6-17, 7-17-3, 7-117-20, 8.19-1, 9-4, 9-910-1, 10-5, A-1, i
HELVETICA @ 16,0 pt 1-1, 2-1, 3-1, 4-1, 5-1, 6-1, 7-1, 8.1, 9-1, 10-1, A-1
HELVETICA @ 2,0 pt 5-15
HELVETICA @ 8,0 pt 2-82-9, 2-122-13, 3-10, 3-36, 10-7
HELVETICA @ 9,0 pt 2-1, 2-3, 2-62-9, 2-12, 2-152-19, 2-21, 2-23, 2-252-28, 3-8, 3-133-15, 3-23, 325, 3-27, 3-37, 3-40, 4-4, 4-7, 5-10, 5-15, 6-46-5, 7-4, 9-29-5, 9-7, 9-9, 10-110-4
Symbol @ 10,0 pt 2-112-13, 3-3, 3-13, 3-22, 4-13
Symbol @ 12,0 pt 3-10
Advant OCS
$03/&RQILJXUDWLRQ
Reference Manual
3BSE 002 417R601
Symbol @ 8,0 pt 4-15

Symbol @ 9,0 pt 4-14, 5-85-12
TIMES @ 10,0 pt 13-41, 4-14-19, 5-17-21, 8.12
TIMES @ 11,0 pt 1
TIMES @ 12,0 pt 3-43-8, 34
TIMES @ 2,0 pt 2-16, 2-18, 3-11, 5-5, 7-10, 10-4
TIMES @ 4,0 pt 7-20
TIMES @ 7,0 pt 7-20
TIMES @ 8,0 pt 2-3
TIMES @ 9,0 pt 3-33-8
Times New Roman @ 10,0 pt 1-1A-1
Times New Roman @ 12,0 pt 3-39
Times New Roman @ 14,0 pt 10-610-8
Times New Roman @ 18,0 pt 1, 34

3BSE002417R601 en AMPL Configuration Advant Controller 400 Series Reference Manual PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3BSE002417R601 en AMPL Configuration Advant Controller 400 Series Reference Manual PDF

Uploaded by

Copyright:

Available Formats

Advant OCS

with Master software

Use of DANGER, WARNING, CAUTION, and NOTE

Hazards which could result in severe personal injury or death

Hazards which could result in personal injury

Hazards which could result in equipment or property damage

Alerts user to pertinent facts and conditions

Copyright ABB Industrietechnik GmbH 1999.

3BSE 002 417R601

AMPL Configuration $GYDQW Controller 400 SeriesReference Manual

General Information................................................................................................. 1-1

Manual Organization ............................................................................................... 1-1

Conventions ............................................................................................................. 1-1

Related Documentation............................................................................................ 1-2

Release History ........................................................................................................ 1-2

Volumes and Segments ........................................................................... 1-3

Differences between the Hardware Platforms ......................................................... 1-4

Chapter 2 - Outline Description

Data Base ................................................................................................................. 2-2

Identifying Data Base Elements ............................................................. 2-5

PC Programs ............................................................................................................ 2-8

Execution Control ................................................................................... 2-8

Choosing Cycle Times ..................................................... 2-8

Altering the Default Set of Cycle Times........................ 2-10

Scanning Process Inputs................................................. 2-12

Working Modes of Advant Controller 400 Series ................................................. 2-13

Ordering Working Modes ...................................................................................... 2-14

Start Modes ............................................................................................................ 2-14

Relationship between Start Modes and Working Modes....................................... 2-15

Relationship between On-line Builder Commands and Working Modes.............. 2-17

Enable CONFIGURATION Mode........................................................ 2-17

Disable CONFIGURATION Mode ...................................................... 2-18

Resetting the Controller ........................................................................ 2-19

Starting Advant Controller 400 Series................................................................... 2-20

3BSE 002 417R601

User-defined Names......................................................... 2-6

Programmed Start ................................................................................. 2-21

Start Module................................................................... 2-22

Programmed Restart after Power Failure....................... 2-22

Example ......................................................................... 2-25

Overview of Programmed Start ............................................................ 2-26

AMPL Configuration $GYDQW Controller 400 SeriesReference Manual

Application Building................................................................................................ 3-1

Data Base Handling.................................................................................................. 3-1

Dialog Handling ............................................................... 3-2

Dimensioning Parts of the Data Base............................... 3-4

Memory Space.................................................................. 3-8

Memory Requirements for certain Functions................... 3-9

TransferringtheDimensioningDatatotheAdvant Controller 400 Series

Quitting DIMDB ............................................................ 3-12

Editing the Data Base............................................................................ 3-12

Creating Data Base Elements ......................................... 3-12

Modifying Existing Data Base Elements ....................... 3-16

Deleting Data Base Elements ......................................... 3-17

Data Base Documentation..................................................................... 3-17

Creating a Data Base Printout ........................................ 3-17

Listing a Data Base Diagram.......................................... 3-17

Listing the Group Alarm Members ................................ 3-19

Compressing the Data Base Backup ..................................................... 3-20

Default Values for Data Base Handling ................................................ 3-21

Structuring PC Programs........................................................................................ 3-21

PC Dimensioning ................................................................................................... 3-22

Dimensioning the Space for PC Programs............................................ 3-22