Preface, Content

S7 Project
1
BRAUMAT/SISTAR Classic 5.3
SIMATIC Module 2
Configuration
3
Automation system Individual control
4
BRAUMAT/SISTARClassic V5.3
Analog functions
Engineering with Braumat 5
based on S7 Excel import/export for external
parameterization 6
Manual User interfaces
7

This manual is part of the documentation

package with the order number:
6FD7680-0PH03

Edition 11/2007
A5E00239377-04
Safety Guidelines
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring to property damage only have no safety alert symbol. The notices shown below are
graded according to the degree of danger.

! Danger
indicates that death or severe personal injury will result if proper precautions are not taken.

! Warning
indicates that death or severe personal injury may result if proper precautions are not taken.

! Caution
with a safety alert symbol indicates that minor personal injury can result if proper precautions are not
taken.

Caution
without a safety alert symbol indicates that property damage can result if proper precautions are not
taken.

Attention
indicates that an unintended result or situation can occur if the corresponding notice is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.

Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning and
operation of a device/system may only be performed by qualified personnel. Within the context of the safety
notices in this documentation qualified persons are defined as persons who are authorized to commission,
ground and label devices, systems and circuits in accordance with established safety practices and standards.

Prescribed Usage
Note the following:

! Warning
This device and its components may only be used for the applications described in the catalog or the
technical description, and only in connection with devices or components from other manufacturers
which have been approved or recommended by Siemens.
Correct, reliable operation of the product requires proper transport, storage, positioning and assembly
as well as careful operation and maintenance.

Trademarks
All names identified by ® are registered trademarks of the Siemens AG.
The remaining trademarks in this publication may be trademarks whose use by third parties for their own
purposes could violate the rights of the owner.

Copyright Siemens AG 2007 All rights reserved Disclaimer of Liability

The distribution and duplication of this document or the utilization We have reviewed the contents of this publication to ensure
and transmission of its contents are not permitted without express consistency with the hardware and software described. Since
written permission. Offenders will be liable for damages. All rights, variance cannot be precluded entirely, we cannot guarantee full
including rights created by patent grant or registration of a utility consistency. However, the information in this publication is reviewed
model or design, are reserved regularly and any necessary corrections are included in subsequent
editions.

Siemens AG
Automation and Drives
Postfach 4848, D- 90327 Nuernberg, Germany ©Siemens AG 2007
Technical data subject to change.
Siemens Aktiengesellschaft A5E00239377-04
Preface
Purpose of the Manual

In this instruction manual the Engineering with BRAUMAT/SISTAR Classic 5.3 based on S7
is described and it gives you an overview of the following topics:
¾ Establish S7-Projects
¾ BRAUMAT/SISTAR Classic 5.3 Module
¾ Configuration
¾ Individual control
¾ Analog processing
¾ User Interfaces
This manual is intended for those responsible for configuring, commissioning and servicing
automation systems.
Required Basic Knowledge

You require a general knowledge in the field of automation engineering to be able to

understand this manual.
In addition, you should know how to use computers or devices with similar functions (e.g
programming devices) under Windows 2000 Prof./Windows 2000 Server or Windows XP
Prof./Windows Server 2003 operating systems. Since BRAUMAT/SISTAR Classic V5.3 is
based on the STEP 7 software, you should also know how to operate it. This is provided in
the manual "Programming with STEP 7 V5.3".
Please read always the file “readme.wri” to the current version of BRAUMAT/SISTARClassic
before an installation of BRAUMAT/SISTARClassic components.
Where is this Manual valid?

This manual is valid for the software package BRAUMAT/SISTARClassic

from Version V5.3 SP2.
The offered electronic manual is most largely identical with the contents of the on-line help.
Due to a technically necessary editorial deadline for the generation of electronic manuals
occasionally smaller deviations can give up opposite the on-line helps.
The statements in the on-line helps are primary to those of the manual.
Place of this Documentation in the Information Environment

This manual forms part of the BRAUMAT/SISTAR Classic V5.3 documentation package.
The following schematic of the document architecture show the individual manuals as well
as their thematic grouping within the entire program package

BRAUMAT/SISTAR Classic 5.3 iii

Engineering based on S7
A5E00239377-04
Document structure

Description of the
System Installation and
Configuration

Administration

Communication

Engineering Recipe System

'based on S7'

EPE-creation
Batch-
processing

Dosing and Serve & Watch

Weigher 'based on S7'
Operation &
Control batches

Application for
Batch curves 'based on S7'

Logging Message

Building block Building block

library : library: Route
Basics Control

Building block Serve & Watch

description S7 Routes

Building block
description S5 Engineering of the
Route Control

iv BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
Further Support
If you have any technical questions, please get in touch with your Siemens representative or
agent responsible.
You will find your contact person at:
http://www.siemens.com/automation/partner
You will find a guide to the technical documentation offered for the individual SIMATIC
Products and Systems here at:
http://www.siemens.com/simatic-tech-doku-portal
The online catalog and order system is found under:
http://mall.automation.siemens.com/
Training Centers
Siemens offers a number of training courses to familiarize you with the SIMATIC S7
automation system. Please contact your regional training center or our central training center
in D 90327 Nuremberg, Germany for details:
Telephone: +49 (911) 895-3200.
Internet: http://www.sitrain.com
Technical Support

You can reach the Technical Support for all A&D products
• Via the Web formula for the Support Request
http://www.siemens.com/automation/support-request
• Phone: + 49 180 5050 222
• Fax: + 49 180 5050 223
Additional information about our Technical Support can be found on the Internet pages
http://www.siemens.com/automation/service
Service & Support on the Internet
In addition to our documentation, we offer our Know-how online on the internet at:
http://www.siemens.com/automation/service&support
where you will find the following:
• The newsletter, which constantly provides you with up-to-date information on your
products.
• The right documents via our Search function in Service & Support.
• A forum, where users and experts from all over the world exchange their experiences.
• Your local representative for Automation & Drives.
• Information on field service, repairs, spare parts and more under "Services".

BRAUMAT/SISTAR Classic 5.3 v

Engineering based on S7
A5E00239377-04
Content
1 S7 Project 1-1
1.1 Establish the S7-Project.............................................................. 1-1
2 BRAUMAT/SISTAR Classic 5.3 Module 2-1
2.1 Structure ..................................................................................... 2-1
3 Configuration 3-1
3.1 Overview configuration ............................................................... 3-1
3.2 Parameter types.......................................................................... 3-1
3.3 Structure of the parameter records ............................................. 3-2
3.4 Connection of parameters........................................................... 3-3
3.5 Block names ............................................................................... 3-4
4 Individual control 4-1
4.1 General to the individual control ................................................. 4-1
4.2 System functions......................................................................... 4-2
4.3 Interrelations ............................................................................... 4-2
4.4 Function block final controlling elements .................................... 4-3
5 Analog functions 5-1
5.1 Block for S7................................................................................. 5-1
5.1.1 General ........................................................................... 5-1
5.1.2 ANA (FB734)................................................................... 5-1
5.1.3 ANAU (FB731) ................................................................ 5-1
5.1.4 DREIP (FB744) ............................................................... 5-1
5.1.5 INKU (FB729) ................................................................. 5-1
5.1.6 KURVSW (FB747) .......................................................... 5-1
5.1.7 MEKO (FB728) ............................................................... 5-1
5.1.8 MESS (FB727)................................................................ 5-2
5.1.9 MULT (FB732) ................................................................ 5-2
5.1.10 PID (FB730) .................................................................. 5-2
5.1.11 POLY (FB735) .............................................................. 5-2
5.1.12 DFM 0, 1, 2, 3 (FC736, 737, 738, 739) ......................... 5-2
5.1.13 Example ........................................................................ 5-2
6 Excel import/export for external parameterization 6-1
6.1 Installation and functionality........................................................ 6-1
6.2 Application .................................................................................. 6-2
6.3 Table structure ............................................................................ 6-3
6.4 Keywords .................................................................................... 6-5
7 User interfaces 7-9
7.1 Block description......................................................................... 7-9
7.1.1 System blocks................................................................. 7-9
7.1.2 User- and Option blocks ................................................. 7-9
7.1.3 Create user description................................................. 7-10
7.1.4 Diagnosis with erroneous description files .................... 7-14
BRAUMAT/SISTAR Classic 5.3 vii
Engineering based on S7
A5E00239377-04
 7.1.5 User description in CSV files .........................................7-15

viii BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 S7 Project

1 S7 Project

1.1 Establish the S7-Project

Procedure:

For establishing a S7-Project see instruction manual ‘Installation & Configuration’.

BRAUMAT/SISTAR Classic 5.3 1-1

Engineering based on S7
A5E00239377-04
 BRAUMAT/SISTAR Classic 5.3 Module

2 BRAUMAT/SISTAR Classic 5.3

Module

2.1 Structure
A BRAUMAT/SISTAR Classic 5.3 module consists of:
¾ A data record in the SIMATIC
All instances of a module are filed in a data block.
You could enter data via the application ‚Parameterization‘. One instance is
specified explicitly by PCU number and instance number. The instance number
starts with 1 and goes to the maximum value.
¾ One FB, which process data.
¾ One name for each instance
All names are stored in a text data file on OS. Text could be entered via the
application ‚Text parameterization‘. There is one line in a text file for each instance
name. The line number corresponds to the instance number.
¾ One description of each instance
All descriptions are stored in a text data file on OS: You could enter text via the
application ‚Text parameterization‘.
¾ One Input- / Output allocation of each instance
¾ Location description of each instance
¾ One assigned process image to each instance
¾ One note to each instance

BRAUMAT/SISTAR Classic 5.3 2-1

Engineering based on S7
A5E00239377-04
 Configuration

3 Configuration

3.1 Overview configuration

See the manual ‘Application based on S7’.
To the basic properties counts, that different properties of blocks, constant values etc. are
filed in special list.
These lists are built up with structures. Each list displays a data block (DB) in the sense of
SIMATIC or a file in the file system of the IOS. In the dialog the plant-related parameter can
be adapted in the corresponding lists.
Plant-related parameter are final controlling names, measured value names, sort names,
dimensions etc.

3.2 Parameter types

Type Meaning
B1 1 Bit
HEXA8 Hexa-number with 8 Bit width
HEXA Hexa-number with 16 Bit width
HEXA32 Hexa-number with 32 Bit width
I8 Integer number with 8 Bit width
I16 Integer number with 16 Bit width
I32 Double-Integer number with 16 Bit width
QUEL Address of a data source
STEP Command in the Notation of STEP 5 / STEP 7

BRAUMAT/SISTAR Classic 5.3 3-1

Engineering based on S7
A5E00239377-04
Configuration

3.3 Structure of the parameter records

The parameter records which are assembled in a list, correspond to a data block in the
SIMATIC-System.
Although the user doesn't access to individual parameters by the help with data block
number (DBn) and the data word number (DWn), the general list structure should be
explained.
As example the block MESS in the S7 (DB727) has been used.

The class ‘amount’ indicates, how many parameter records are in the list. The length of the
data record is 64 byte, i.e. that one parameter record is 64 byte long. The Offset to the 1.DS
indicates the starting point of the first data record. The maximum DS amount indicates the
maximum amount of the possible objects of the class. The Offset to the running time copy
indicates the address in the data block where the corresponding data record is copied that is
processed at the running time.

The first parameter record extends from line 1 until 21, the second connects itself directly
behind.

3-2 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 Configuration

3.4 Connection of parameters

The System blocks can also withdraw values, excluding the own parameter records. This
method is called "Linking" of parameters, whereby parameters are always fetched and are
never sent.
In the parameter record of the fetching blocks the address of the destination parameter,
which is calculated by the indication of block names, parameter record number, parameter
name/parameter number of the user program.
This type of the block connection has the advantage that user needn't to know the absolute
memory locations. (Data block/data word). Connecting blocks in order to realize special
tasks is comparable with a wiring list as it is used in the analog circuit design.
In the window "Linking" a Linking can be deleted.

Example: PID – controller with measured value recording, analog output transferable to
controller or fixed value.

Linking should be clarified at the example of the PID – controller:

The block PID 1 fetches its Xist from the output of the block MESS1.

This is clarified in the graphic by the connection line between the 2 blocks.

BRAUMAT/SISTAR Classic 5.3 3-3

Engineering based on S7
A5E00239377-04
Configuration

3.5 Block names

A plant-related name can be given to each technological block or module. The blocks can be
identified easily by the technologies.
These block names are listed in a block-related text-file on the harddisk accordingly.
The input of these names can be executed individually as well as directly in the text file.

3-4 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 Individual control

4 Individual control

4.1 General to the individual control

Tasks of the individual control are triggering, interlocking, monitoring and signaling of final
controlling elements like valves, motors, pumps, flags, slide valves, etc. ..
Triggering commands can come from
¾ The equipment operations of the Units
¾ Connection programs
¾ Any other automatic programs (which aren't part of the System) or
¾ Screen operation

Interlocking programs guarantee that the necessary operation interlockings are considered.
These are effective for each type of triggering, i.e. in the automatic- and in the manual
operation.
Basic logics like the interlocking of product- and cleaning valve, the dry safety of pumps,
agitator, etc, need to be filed only one time. Equipment operations, connection programs
and any other concerning the individual final controlling are shorter and have much more
overview by that.
However, the basic interlocking isn't a substitute for safety interlockings, which are to be
realized outside of the control.
With a non-fulfilled operation interlocking commands are sent to all final controlling elements
for a "OUT"- position:
¾ Motor, Pump: "OUT"
¾ Valve, flap, solid: "Closed"
Triggering commands aren't considered.
On each position command the actuator must react within a individually presetting time by a
corresponding acknowledgement. (1..255 Seconds). Either this reaction is executed
¾ Not at all
¾ delayed, or
¾ the reaction signal disappears without the corresponding command again
an actuator fault is recognized. This one is filed in the actuator state for the display and a
disturbance message is sent for the released operating systems. (OSs).

BRAUMAT/SISTAR Classic 5.3 4-1

Engineering based on S7
A5E00239377-04
Individual control

4.2 System functions

The System makes the block ICM individual final controlling element available.
This one includes the controlling-, locking-, monitoring- and signal logic.
Organization of the instances available for this block:
ICM1: 255 final control elements of ICM group 1
ICM 2: 255 final control elements of ICM group 2
ICM 3: 255 final control elements of ICM group 3
ICM 4: 255 final control elements of ICM group 4
Furthermore there is the possibility to configure closing and off delays for controlling ICMs.
This delays are only active, if the final controlling element is in the automatic operation.
The configuration of the closing- and off delays has to be done in the data record of the ICM
block.
Independent of the individual control by the System an external manual level is realizable.
The System enables the bumpless transfer from and to the external manual level.

4.3 Interrelations
The operation of the ICMs is executed by the OS.
Controlling the ICM – blocks is executed in the AS:
¾ In the automatic program of the Units by the equipment operations
¾ Per operation via the screen
¾ By any other connection programs
In the ASes control-independent connection programs guarantee, that the necessary
interlocks are considered.
The conditions of the final controlling element are transferred to the operation System (OS)
by the coupling for visualization.
The operation System (OS) itself transmits operation commands for the final controlling
elements via coupling to the underlaid Systems (AS).

4-2 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 Individual control

OS Operation
level

Work station
ICM

Coupling

AS Automatic Partial
level recipe EOP
procedure

Interlock
level Interlock
program

Individual
control
level ICM

Process

4.4 Function block final controlling elements

See instruction manual ‘Blocks S7’

BRAUMAT/SISTAR Classic 5.3 4-3

Engineering based on S7
A5E00239377-04
 Analog functions

5 Analog functions

5.1 Block for S7

See instruction manual ‘Blocks S7’

5.1.1 General
For processing analog sizes in the frame of process automation the System makes a
sequence of standard blocks available. By the corresponding configuration of the blocks and
interconnection of blocks among each other the most different functions are realizable.
The blocks FBs are called by the System program. The FCs for the DFMs must be called by
the Project Manager!
The following blocks are included in the System.(in alphabetical order):

5.1.2 ANA (FB734)

One allocated analog value per operation. It is used as setpoint or limiting value. It is
comparable with a potentiometer in the function.

5.1.3 ANAU (FB731)

Convert an allocated setpoint in electrical units and transfer it by the analog output module.

5.1.4 DREIP (FB744)

Block for three point controller for simple arrangements.

5.1.5 INKU (FB729)

It is calculated the duration of open- or close commands and starts one of two time steps
accordingly.

5.1.6 KURVSW (FB747)

Allocation of setpoint curves (represented graphically or in tabular form). This setpoints can
be transmitted to e.g. a controller by a curve scanning.

5.1.7 MEKO (FB728)

Monitors an allocated value on two limits.

BRAUMAT/SISTAR Classic 5.3 5-1

Engineering based on S7
A5E00239377-04
Analog functions

5.1.8 MESS (FB727)

Reads a value from the analog input block and makes that one in a adapted form available
as physical size of different blocks.

5.1.9 MULT (FB732)

Depending on the selected function a output value is formed by two input values or a flag bit
is manipulated. Different functions are available.

5.1.10 PID (FB730)

Controller block, which forms from setpoint W, actual value X and influencing quantity Z a
manipulated variable Y.

5.1.11 POLY (FB735)

Adapt a input value via six support couples. It is used for linearizing as curve trace computer
for indirect measurements.

5.1.12 DFM 0, 1, 2, 3 (FC736, 737, 738, 739)

It includes the required functions in the scope of the step process ‘Limiting value step’ for
forming step enabling criterias and ‘Setpoint steps’ for the appropriation of recipe values for
different blocks.

5.1.13 Example

Monitoring a measured value of 2 fixed limits

Solution by connection of a block MESS with a block MEKO. The both comparison results
(Limit 1 is violated or limit 2 is violated) and are available as flag for the step enabling
processing.

Result
Measured flag
value

Monitoring of a measured value on an external limit

Solution by connection of a block MULT with the function LI+ with two blocks MESS for
actual value and limiting value. The comparison result is available as flag.

5-2 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 Analog functions

Measured
value

Result
flag

Limit value

Monitoring a measured value on a recipe-dependent limit and formation of a step

enabling criteria

Solution by connection of a block MESS with a block DFM and evaluation of the comparison
in a equipment operation.

Recipe

Measured
value Result EOP

Monitoring of the deviation on a fixed limit

Solution by connection of the block PID with the block MEKO.

Result
flag

Continous controller with a fixed setpoint

Solution by the useage of a block MESS for the actual value, of a block AFIX for the setpoint
, of a PID-block and a block ANAU for the manipulated variable output.

BRAUMAT/SISTAR Classic 5.3 5-3

Engineering based on S7
A5E00239377-04
Analog functions

manipu-
lated
variable

Actual
value

Continous controller with recipe-dependent setpoint

Solution by the useage of a block MESS for the actual value, of a block DFM for the
setpoint, of a PID-block and a block ANAU for the manipulated variable output.

Manipula-
ted
Actual variable
value

Step controller with external setpoint

Solution by the useage of three blocks MESS for the actual value, setpoint and position
acknowledgement, of a PID-block, of a block INKU and one part of the program.

5-4 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 Analog functions

Actual
TAUF
value
TZU FB-Unit

Setpoint

Position

BRAUMAT/SISTAR Classic 5.3 5-5

Engineering based on S7
A5E00239377-04
Analog functions

Controller with Back-Up

Solution by the useage of two blocks MESS for the actual value and compensating value, of
a PID-block, of a ANAU-block for the allocation of the manipulated variable and one
TELEPERM-D controller.

Actual
value
Program

UYR RB CB YN
Actual TELEPERM-D controller Manipulated
value value

5-6 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 Analog functions

Ratio Control

It is requested, that two controllers should accept one adjustable proportion of a setpoint
each
Solution with two blocks AFIX (one for the number 100, and one for the setpoint of the
controller 1), five blocks MULT (two DIV, two MUL, one SUB)..

Setpoint
Controller 1

Setpoint
Controller 2

Anteil 1

100

Explanation of the circuit:

As proportion 1 + proportion 2 has always to be 100, the proportion 1 is filed as value and
can be changed as operation. The operation program has to be consider the limit 0 ≤
proportion 1 ≤ 100 has to consider the operation program.
Setpoints are calculated in the following form:
¾ Setpoint Controller 1 = Setpoint x proportion1 / 100
¾ Setpoint Controller 2 = Setpoint x (100 - proportion1) / 100

BRAUMAT/SISTAR Classic 5.3 5-7

Engineering based on S7
A5E00239377-04
Analog functions

Selection of one out of 4 measured values, dependent of a selection counter

Solution with four blocks MESS, three blocks MULT in the function ASL and one part of the
program.

A B C
Bit 0
Program
Bit 1

The following logic is valid for the program:

Bit 0 Bit 1 MESS A B C
0 0 14 0 0 0
0 1 15 1 0 0
1 0 16 X 1 0
1 1 17 X X 1

5-8 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 Analog functions

Selection of the biggest value of three

Solution with two blocks MULT with the function MAX.

Value 1
Value 2

biggest
Value 3 value

Temperature- or pressure control with switching controller (On/Off or Open/Closed)

Solution by the useage of a block MESS for the actual value, one block ANA for the setpoint,
of a THREP-block and of a user program.

Actual
value

Open
Program
Closed

Time

In the user program one of the outputs OPEN or CLOSED are controlled by queries of the
Timers Control-bits (ANST) .
Example:
Timer runs and ANST = 1 OPEN = 1, CLOSED = 0

Timer runs and ANST = 0 OPEN = 0, CLOSED = 1

Timer doesn't run OPEN = 0, CLOSED = 0

BRAUMAT/SISTAR Classic 5.3 5-9

Engineering based on S7
A5E00239377-04
 Excel import/export for external parameterization

6 Excel import/export for

external parameterization

6.1 Installation and functionality

To use the functionality described here, the following Excel files are supplied on the
BRAUMAT/SISTAR Classic V5.3 CD in the
‘..\sis_sys.53\SISTAR.530_V0503xxxx\windcs32.usr\EXCEL’ directory. Copy these into a
subdirectory of their own in the Braumat/Sistar system directory, like for example,
“..\windcs\EXCEL“.

File Function
Global_10.xls Excel template file for ‘entity’ configuration
Macro.xls Excel file that includes the Excel macros listed in the following. With
that, the user can trigger different import/export functions.
Param_PCU001_0.xls Excel template file for PCU001 with 26 work sheets including a
cover sheet. Here the basic Braumat plant configuration
(technological objects of the equipment) is covered:
(FIXV, AOUT, SEQS, DFM0-3, THREESTEP, ICM1-4, MVC,
ALARM, AIN, MULT, PID, SEQU, SPEVAL, TIMER01-02, XC-JOB,
EPE.INI, EPAR.INI, SEQUENCE.INI)
Caution:
The supplied Excel Templates supports Simatic S7-PCUs only
because the class/attribute names are based on the
„ParamS7.0xx“ Definition file.
Later on, the template is copied by the user for each PCU and
parameterized in the correction sheet at the accompanying PCU
no. Æ refer to Chapter “Application”.
Param_PCU001_1.xls English language version

The Excel file “Macro.xls” includes the macros described in the following table:
Macro Function
ExportAll() One after the other all the object classes are exported to the
SISTAR data layer (see below for details)
ExportAll_D() Same function, but German sheet names
Import All() One after the other all the object classes are exported out of the
SISTAR data layer (see below for details)
ImportAll_D() Same function, but German sheet names
CompareAll() One after the other all the sheets are compared with SISTAR. The

BRAUMAT/SISTAR Classic 5.3 6-1

Engineering based on S7
A5E00239377-04
Excel import/export for external parameterization

results of the comparison are written in a log file. All the errors and
warnings are entered in this
CompareAll_D() Same function, but German sheet names
ExportOneTable() The current table (= object class) is exported to SISTAR. At the end,
all the errors and warnings are entered in a log file (file “Export.txt”
in the current directory)
CompareOneTable() The current table is compared with SISTAR. The results of the
comparison are written in a log file. All the errors and warnings are
entered in this
ImportOneTable() The current table is imported from SISTAR. In the end a log file is
opened. All the errors and warnings are entered in this. Then the
current table is completed with the imported data

ExportCSV() -Internal use only-

ExportCS_() -Internal use only-

The system “Export.dll” is required to execute this macros, which was installed in the
directory ..\windcs\sys upon installation of BRAUMAT/SISTAR Classic V5.3. This realizes
the actual import/export functions of the configuration data from or in the (binary) offline
block files or INI files of the Braumat system. All the above-mentioned macros access this
DLL.

6.2 Application
The following configuration course – separate for each PCU – can be executed using the
above-mentioned macros:
¾ Import the Braumat offline configuration to Excel; an Excel sheet is completed for
each object class
¾ Configure/change the object properties using all Excel means and possibilities
¾ Compare the configured data with the (offline) configuration in the Braumat project
path
¾ Export (also selectively) the configured tables in the offline DBs and INI files
In a further step, the user must ensure the download in the respective PCU
The following procedure is recommended for application:
¾ Launch MS-Excel
¾ First of all, open the macro file “Macro.xls” and activate Macros. In doing so, the
Excel security setting should be “medium” or “low” (menu ExtrasÆMacroÆSecurity)
¾ Now open a PCU-specific project file, e.g. “xyz_Anlage_PCU010_de.xls”. Upon first
call, the template file (e.g. “Param_PCU001_0.xls”) should open. As this is write-
protected, it must be immediately saved under a new name.
¾ The call of the macros takes place as standard via the menu Extras->Macro-
>Macros. However, the user can also define call buttons for the most frequently
used functions (refer to MS-Excel documentation)
Caution:

It is recommended in particular in the case of a new or unknown Excel file, to carry on

always a ‘ImportAll’ for first action and store this Excel sheet seperately. So one prevents,
that at the next one -maybe inadvertent- export step the project engeneering is overwritten
with undefined values.

6-2 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 Excel import/export for external parameterization

6.3 Table structure

Table Header:
A B C D E F G H
1 PCU 1
2 Class AIN
3 Amount 1
4 Max 256
5 Export E*) DB,N,A**)
6
7 Def No NAME DigX_ DigX_ XANF XEND UNTGR
ANF END
8
9 Filter AIN no. Name Xxx
*)
10 E 1 AIN1 0 100

The bold entries are keywords for the export function. They must be entered at the positions
shown here in the sheet.
Description of the header keywords:
Keyword Function
Class Class and/or technolog. Blockname for that this worksheet is processed; must
correspond exactly to the class name in the ‘param.pcu‘ file
Amount Import: Shows the number of the imported instances; only the area in fact
configured in the block is imported up to the max. line count in the table; for too
many data records are in the table, warnings into the logging file window are
issued.
Export: Debit-number of the instances/lines to be exported; this number is
taken over into the block-parameterization, that is where appropriate this
increases/decreases data records in the block parameterization; if Amount is
larger than the filled number of lines, data records in the block parameterization
are filled with default values
Therefore be carefully at modification of the former imported value!
Max Additional and more prior possibility for limitation of function import/export (next
to Amount); should correspond normally to the max. value from the ‘param.pcu
file’
Export E (*)) shows which lines should be exported. Only the lines that have the
character stipulated in the cell B5 in column A are exported.
The character sequence DB,N,A (*)) indicates which attribute groups are to be
exported. If these are not stated, all (as with DB,N,A) are exported. Otherwise,
those groups that are stipulated separately with “ , “ are exported.
A: export the new attributes: address/location/description/image
DB: export the DB-related attributes
N: export the name
Def Definition of the class attributes; see below for futher information

For some classes the header attributes are restricted as follows:

Class PCU Class Amount Max Export
Entity_Group -- 3 3 -- 3
Entity -- 3 -- -- 3

BRAUMAT/SISTAR Classic 5.3 6-3

Engineering based on S7
A5E00239377-04
Excel import/export for external parameterization

MasterTagList -- 3 -- -- 3
Entity_Template -- 3 3 -- 3
Template_Parameter -- 3 -- -- 3

For the plant sections/sequences class the header attributes are expanded as follows:
A B C
1 PCU 1
2 Class_RecV3 Plant sections
2 Class_RecV5 Sequences
3 Amount
4 Max 64
5 Export E*) DB,N,A**)
6
7 Def_RecV3 No NAME
8 Def_RecV5 No NAME

This enables both access to RecipeV3 plant sections data records, as well as RecipeV5
sequence data records. The following lines move accordingly.
Definition line

A definition line must follow the head of the table. It must be possible to assign each cell an
attribute of this class in accordance with the global “param.pcu” file. The entries are case
sensitive.
If this is not the case, a fault message occurs. (Def_RecV3/V5 work dynamically depending
on the recipe version). If a cell and with that the entire column is not taken into account, an
“_” underline must explicitly be entered.
The keyword “Def” must be entered in the cell A7. The keyword “No” must be entered in the
cell B7. With two-stage addressing, B7/C7 is used with an extended token (e.g. for
EntityClass NoTemplate/NoEntity). Continue as you wish for the further sequence of
attributes.
You do not have to position the definition line as the 7th line; the definition line must however
exist before the data records.
User-supporting entries can be entered in line 9 (also this line number is not compelling).
The keyword “Name” is entered as the name of the data record.
Line 9 is comment.
Notice:

The chosen columns in the provided Excel standard templates correspond to those
attributes of the respective Braumat classes/text files that are relevant to the plant
configuration. They will not be covered any further at this point, as they represent “general
Braumat engineering know-how” and this is already described in the standard manuals.
However, for a better orientation and overview, comment fields are entered in the definition
cells, and these include information regarding the respective associated data element of the
Braumat configuration.
Additional columns

After the B columns, columns that cannot be exported can also be added to the table. The
condition for this is that the attribute does not exist in the ‘param.pcu’-file and doesn’t
represent any other keyword.

6-4 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 Excel import/export for external parameterization

6.4 Keywords
Other keywords are recognized alongside the attributes of the param.pcu.
Module Keyword Export to
All Name Name of the data record; is
exported in the text file of the
module (see param.pcu);
All No. Number of the data record;
must be stipulated in the first
exportable column;
DFMGr.DF.MNo. must be
stated with SW-INI/EPAR.INI,
All apart from EXT_CLASS Addr Text for address, stored in
PCU.x\Address.L
displayed in Faceblade
All apart from EXT_CLASS Desc Text for description, stored in
PCU.x\Desc.L
displayed in Faceblade
All apart from EXT_CLASS Image Path for process image, stored
in PCU.x\Image.L
displayed in Faceblade
All apart from EXT_CLASS Loc Text for location, stored in
PCU.x\Location.L
displayed in Faceblade
ENTITY BaseAdrByte Byte of the basic address for
relative addressing
ENTITY BaseAdrDB DB of the basic address for
relative addressing
ENTITY BaseAdrPCU PCU of the basic address for
relative addressing
ENTITY ID ID of the entity (globally
understandable!)
ENTITY NoEntity Entity number (relative to type)
ENTITY NoEntityGroup Number of entity type
ENTITY NoTemplate Number of template to be
assigned
Entity_Group EntityAmount Number of entities of this type
Entity_Group Name See above
Entity_Group NoEntityGroup Number of entity type
Entity_Template Name Name of template
Entity_Template NoTemplate Template number
Entity_Template ParameterAmount Amount of parameters of a
template
ICM1 ... ICM4 Entity Assignment of ESG to entity;
several values can be entered,
separated by a comma
MasterTagList EntityID Globally understandable entity
ID
MasterTagList Tag Understandable instance name
for TAG to be assigned
MSG Incoming Meldkom.txt
MSG Outgoing Meldgeh.txt
Sp.Value Comment Comment

BRAUMAT/SISTAR Classic 5.3 6-5

Engineering based on S7
A5E00239377-04
Excel import/export for external parameterization

Sp.Value Dim Dimension

Sp.Value Type Type of special variable
Sp.Value Value Value of special variable
SW.INI/EPAR.INI Comment Comment
SW.INI/EPAR.INI Dec Decimal point of the set value 0
-7
SW.INI/EPAR.INI Dim Dimensions
SW.INI/EPAR.INI File File name; only necessary and
useful for TEXT type
SW.INI/EPAR.INI Max Maximum input value (without
decimal point)
SW.INI/EPAR.INI Min Minimum input value (without
decimal point)
SW.INI/EPAR.INI Name Is ignored (in the DFMs)
SW.INI/EPAR.INI Type Type of set value:
SW, TEXT, 16Bit, 32Bit
GOP.INI/EPE.INI Age 2-255
GOP.INI/EPE.INI ATTID_GOP_COMMENT Comment for GOP/EPE
GOP.INI/EPE.INI DFM1 ... DFM13 Set value; in doing so, the DFM
can be stated as an absolute
figure 1-1023 or as 0.1 – 3.255;
an “e” after the DFM indicates
that the set value cannot be
edited
GOP.INI/EPE.INI JumpName String MaxLen 8
GOP.INI/EPE.INI Label 1-255
GOP.INI/EPE.INI Name Is exported in the
gop.txt/epe.txt
GOP.INI/EPE.INI OpReq Text for operator request,
exported in gop.ini
GOP.INI/EPE.INI OpReqFlags 0..configuration OPReq
GOP.INI/EPE.INI Unit Plant section assignment,
“Kzuo”; if the cell is empty then
nothing is exported for this Gop
TEILANL.INI/SEQUENCE.INI Name Is ignored (is in
teilanl.txt/sequence.txt)
TEILANL.INI/SEQUENCE.INI DFM1 ... DFM13 The DFMs that are displayed in
step 0.
TEILANL.INI/SEQUENCE.INI Name Export in Teilanl.ini as
“Comment=”
TEILANL.INI/SEQUENCE.INI RecType Separated with commas, the list
of authorized recipe types for
the start of a recipe
Template_Parameter Byte_Bit Dbyte/Dword/DDWord/Bit
Template_Parameter DB DB with absolute address (0
otherwise)
Template_Parameter DecimalPoint Number of decimal points
Template_Parameter Dimension Dimension
Template_Parameter File Display text
Template_Parameter IsStatus 1 if the parameter is the status
parameter,
0 otherwise

6-6 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 Excel import/export for external parameterization

Template_Parameter Max Maximum

Template_Parameter Min Minimum
Template_Parameter Name Name of parameter
Template_Parameter NoParameter Number of parameter
Template_Parameter PCU PCU with absolute address (0
otherwise)
Template_Parameter Type Type of parameter
SW/TEXT/HEX/BIN

BRAUMAT/SISTAR Classic 5.3 6-7

Engineering based on S7
A5E00239377-04
 User interfaces

7 User interfaces

7.1 Block description

7.1.1 System blocks

All blocks are defined via a description file for the System. This file is loaded on the OS by
the Object Manager (OM). The OM makes information available to all Clients.
Especially, configuration has to be emphasized. Via this application only the parameter
which are listed in a description file can be modified.
A corresponding description is delivered for all System blocks.
These files are in the folder‚\windcs\param.pcu‘. In the delivery condition these are the files:
¾ params5.xxx (xxx stands for the language identifier)
Description for SIMATIC S5 blocks
¾ params7.xxx (xxx stands for the language identifier)
Description for SIMATIC S7 blocks

7.1.2 User- and Option blocks

Besides of the description of the System blocks, USER- and/or PCU-specific descriptions of
blocks can be created. It isn't important, if all descriptions are distributed in one or several
files. The files must have the extension‚ "*.pcu" and should normally be in the folder
\PCU.XXX, otherwise they won't be considered by reading in.
Global ‘User Param.pcu’ files for Simatic S7:
S7-User-Param-Files may be stored as global definitions in folders
..\Param.pcu\usrfiles.xxx instead of the PCU-specific folders.
The following steps have to be considered:
1. Activate appropriate INI switches
File: “om.ini”
[Config]
;Enable global user parametrization files
GlobalUserParamFiles=1 (default is 0!)
2. Create specific folders:
..\Param.pcu\usrfiles.000 german
..\Param.pcu\usrfiles.001 english
..\Param.pcu\usrfiles.002 spanish
...

BRAUMAT/SISTAR Classic 5.3 7-9

Engineering based on S7
A5E00239377-04
User interfaces

3. Store User-Files in the according folders

..\Param.pcu\usrfiles.000\xyz.pcu

7.1.3 Create user description

For the description of a user block a Syntax has to be considered.
Structure of the description:
¾ Line for the class description
¾ General data
¾ Block head data
¾ Description of a data record
¾ Description of an attribute
Comment

(* Text *)

comment.vsd

The comment need to be framed by keys‚ ‘(*‘ and ‘*)’. The comment may be a maximum of
44 signs long.
Class description

object Blank Name = DB Number ; Comment

class.vsd
object: Key word
Name: Name of the block / Class (maximum of 10 signs)
DB: Key word
Number: Number of the data block
Example

object Sequence=DB725; (*Sequencer Control*)

General data

The general data should begin directly after the class description in the following line. Each
line has to be finished with a semicolon. (" ; ") .
The following general attributes need to be allocated:
¾ CID=
Indication of an explicit class ID (1000 – 2000)
¾ max=
Maximum data record amount
¾ offset=
Byte address of the first data record
¾ length=
data record length in Byte

7-10 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 User interfaces

¾ number=
Indication of a fixed amount of data records or address indication
¾ filename=
Optional indication of a file name for the names of the instances. If the input is
missing, the names are expected in a file which has the name of the block.
¾ classtype=
Indication of the class type
¾ version=
Indication of the version
Type of classes

For the display in the configuration the block can be assigned to a class type. The following
types are delivered by the System:
¾ 0: Display of all types
¾ 1: Technology
¾ 2: Periphery
¾ 3: System
¾ 4: Route Control
¾ 5: Weighers
¾ 6: Cross coupling
The type of classes can be extended by the user types.
File: \windcs\texte.x\classtype.txt
The file has to be edited via the text configuration.

Data block description

global attribute Attribute description

{ struct }
description of the data record

dataset.vsd
The data block description is started via a clippy bracket. After the bracket there are the
global attribute descriptions line per line. The description of a data record is started with the
key word ‚struct‘. After that the attribute descriptions of the data record follow. The data
block description is closed with a clippy bracket.

BRAUMAT/SISTAR Classic 5.3 7-11

Engineering based on S7
A5E00239377-04
User interfaces

Address indication

DBB

Byte
DBW
address

DBD

Byte Bit
DBX .
address address

address.vsd

The data record description can include a maximum of 200 attributes.

Attribute description

WinCC

Attribute
Name ( , Addresse ,
ID

Type of
Data type , ) Comment
access

Upper
Low limit ,
limit

attribut.vsd

The sections of the attribute description are separated by comma.

¾ Name
The name of the attribute can be a maximum of 10 signs. It may not include any
special characteristics.
¾ Attribute ID
Within the block an explicit ID must be assigned to each attribute.
¾ WinCC
This indication is optional. In this way the attribute is marked as exportable to
WinCC.
¾ Address of the attributes
¾ Low limit
Lower value for the input in the configuration. This value is optional. If no limiting
values are indicated, the maximum values for the data type are valid.

7-12 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 User interfaces

¾ Upper limit
Upper limit for the input in the configuration.
¾ Data type
B1: Bit value
I8: 8 Bit value afflicted without signs
I16: 16 Bit value afflicted without signs
I32: 32 Bit value afflicted without signs
STEP: STEP 7 command
QUEL: Source indication
HEXA8: 8 Bit value
HEXA: 16 Bit value
HEXA32: 32 Bit value
¾ Type of access
RD The value can only be read via the configuration.
HI The value is in the section‚ hidden attributes‘
HR The value is only readable and in the section ‚hidden Attributes‘
Example

object Karlheinz=DB10;(*testKH*)
CID=1920;
max=128;
offset=100;
length=100;
number=DBW8;
filename=KHtest;
version=1;
{
Offset (3 ,DBW2 ,I16)=100; (*Offset zum 1.Datensatz*)
Satz_Lae (2,DBW4,I16)=100; (*Satzlaenge*)
SILO_Anz (1,DBW8,I16,RD); (*Silo-Anzahl*)
struct
Bit1 (1,DBX1.0,B1)=0; (*Bitwert*)
Int8 (2,DBB2,I8); (*8 Bit*)
Int1 (3,DBW3,I16); (*16 Bit*)
Int32 (4,DBD5,I32); (*32 Bit*)
STEP7 (5,DBW10,STEP); (*S7 Befehl*)
QUELLE (6,DBD20,QUEL); (*Quellenangabe*)
HEXA_8 (7,DBB12,HEXA8); (*HEXA 8*)
HEXA_16 (8,DBW13,HEXA); (*HEXA 16*)
HEXA_32 (9,DBD15,HEXA32); (*HEXA 32*)
}

Note

It can be created a help file to each PLC-block, that can be displayed with activating the F1
key in the configuration.
The file has to be filed in the folder \Help.x . The name of the file must be identical with the
block name. An underscore character ‚_‘ must be prefixed to the file name.

BRAUMAT/SISTAR Classic 5.3 7-13

Engineering based on S7
A5E00239377-04
User interfaces

7.1.4 Diagnosis with erroneous description files

If faults occur with reading in, the total block is rejected by OM. In order to receive a
diagnosis for the IOS, the OM diagnosis window can be overlayed. The text in the window is
only in German.
File: \windcs\sys\om.ini
Entry: [Config]
Key: bTracingDialog=1
After this adjustment BRAUMAT/SISTAR Classic 5.3 applications have to be closed and the
PCU-Server has to be started new.

Functions of the diagnosis window

¾ Listbox Delete
With this button all inputs in the list are deleted.
¾ Read in again
With the button all descriptions are read in again.
¾ Open Browser
With this button a further dialog is opened in which all classes (= Blocks) and their
attributes can be displayed.
¾ Configure OM
With this button a further dialog is opened in which adjustments for the diagnosis
could be made.
¾ Close OM
With this button the diagnosis window is closed.

7-14 BRAUMAT/SISTAR Classic 5.3

Engineering based on S7
A5E00239377-04
 User interfaces

¾ Help/Info
With this button a dialog with important information to the Object Manager is
opened.
¾ Switch on Tracing
With this connector the trace function can be switched on and off.
¾ All actions of the OM are displayed in the list. Via the dialog ‚Configure OM‘ the
display can be restricted to errors and warnings.

Initial memory capacity of the OM

The Object Manager is only started one time per IOS and holds the necessary block
descriptions for all BRAUMAT/SISTAR Classic 5.3. One fixed memory location is used for
this central function. This memory location can't be enlarged. Therefore it is started from a
presetting quantity of this memory location. If the consumption of the memory should be
increased due to additional description files over this limit, the presetting will be changed
consequently.

7.1.5 User description in CSV files

One dataset with a fixed length is reserved for each instance of a standard BRAUMAT
object. However, you can also work with instance DBs, where an instance corresponds
precisely with a DB of a fixed length.
Each *.PCU file is allocated a *.CSV file, which you can either create manually or generate
in PCS7, for example.
The CVS file contains one line per instance. The Object Manager converts this information
as usual into BRAUMAT objects.

Class description

object: keyword
Name: Fixed name DB_CFC

Example

object FIFO_CFC=DB_CFC; (*.....*)

CSV syntax

Name; instance name; object name from *.PCU; DB number; identifier

Example

FIFO;FIFO 1;FIFO_CFC;DB 670;instance DB

FIFO;FIFO 2;FIFO_CFC;DB 671; instance DB
FIFO;FIFO 3;FIFO_CFC;DB 672; instance DB
FIFO;FIFO 4;FIFO_CFC;DB 690; instance DB
FIFO;FIFO 5;FIFO_CFC;DB 691; instance DB
FIFO;FIFO 6;FIFO_CFC;DB 692; instance DB

BRAUMAT/SISTAR Classic 5.3 7-15

Engineering based on S7
A5E00239377-04