6AT8010-6DA00-0AA0 - SIEMENS

BRAUMAT compact

V3.0 SP1

Engineering Manual

09/2012

A5E02608507B-02

General

GeneralGeneral

General

Installation

InstallationInstallation

Installation

Demo

DemoDemo

Demo

Project

ProjectProject

Project

System

SystemSystem

System

Overv

OvervOverv

Overview

iewiew

iew

Create

CreateCreate

Create

New

NewNew

New

Project

ProjectProject

Project

Excel

ExcelExcel

Excel

Addin

AddinAddin

Addin

Trending

TrendingTrending

Trending

Recipe

RecipeRecipe

Recipe

Configuration

ConfigurationConfiguration

Configuration

Scheduler

SchedulerScheduler

Scheduler

Batch

BatchBatch

Batch

Data

DataData

Data

Export

ExportExport

Export

and

ndnd

Report

ReportReport

Report

1010

Technologi

TechnologiTechnologi

Technological

calcal

cal

Hierarch

HierarchHierarch

Hierarchy

1111

Connection

ConnectionConnection

Connection

ofof

CFC

CFCCFC

CFC

PlPl

Plans

ansans

ans

1212

Control

ControlControl

Control

Modules

ModulesModules

Modules

1313

User

UserUser

User

ARCHIVES

PCS 7 BOX

RTX OS

RUNTIME

(WINAC

RTX2010) (250

PO)

Braumat

compact

WINCC/USER

ARCHIVES

SINGLE STATION

V7.1 (PO 1000)

Braumat compact

2 x WINCC/USER

ARCHIVES

SINGLE STATION

REDUNDANCY V7.1

(PO 1000)

2x Braumat compact

WINCC/USER

ARCHIVES

SERVER V7.1

(PO 1000)

CLIENT V7.1

Braumat compact

BRAUMATcompact Installation

Engineering Manual, 06/2010, A5E02608507B-02 Page 18

Notes on license

In addition licenses for the WinCC User Archives are required; they are contained on

the license key memory stick as well.

The license according to the General License Conditions for Software Products for

Automation and Drives for Customers with a Seat or Registered Office in

Germany/outside Germany (hereinafter each "License Conditions") allows the use of

the User Archives only within the use of the product BRAUMAT compact according to

license. Siemens is not liable for any use over and beyond this limitation. Transfer of

license to a third party is not permitted as independent transaction but only within

transfer of rights according to the License Conditions of the product BRAUMAT

compact.

Missing Licenses:

 Microsoft Excel

 Web Client

 PCS7 Engineering Licenses

Microsoft Excel must be installed and licensed by the user for exporting the batch data

and for the engineering of BRAUMAT compact.

Demo Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 19

3 Demo Project

Retrieve it under …\Siemens\STEP7\EXAMPLES_MP\BRC_DEMO.zip. with the

SIMATIC Manager and save it in the project directory e.g. in SIMATIC S7 project

directory (S7Prj).

Open the demo project in SIMATIC Manager.

3.1 Configurations

3.1.1 SIMATIC S7 Hardware Configuration

Open the HW-Configuration and adjust the hardware to the hardware on hand.

Compile the alteration and reload the CPU.

3.1.2 SIMATIC S7 Netpro-Configuration

Open Netpro and adjust the network addresses to their conditions.

3.1.3 Configuration Station Configuration Editor

Use the Station Configuration Editor to enter the different components in the same manner as

in the demo project (see HW configuration).

3.2 S7 Compile and Load Program

Open an arbitrary CFC chart and compile the entire program.

3.3 Generate OS

Compile the entire OS with master reset. After that start the OS runtime.

Per each unit in OS runtime must

1.) The control matrix Engineering Faceplate be opened and the data of the user

archive be read. After that the control matrix data must be written to the PLC.

2.) The button Parameter is to be pushed once for each unit. In the parameter type

dialogue the data must be read from the archive first and then written. Thereby the

parameter type data is transferred to the control.

The demo should be executable now. Start a recipe e.g. Pils on the mill.

BRAUMATcompact System Overview

Engineering Manual, 06/2010, A5E02608507B-02 Page 20

4 System Overview

4.1 System Plan 



 Unit Sequence

4.1.1 System Plan

The CFC plan system is available for an installation as central component, containing

several units. The system plan contains 3 blocks. Each of these blocks is connected to

a block of the unit. Each of the blocks provides a central service.

4.1.1.1 Recipe Manager (FB_RECM):

Image 4: Recipe Manager Block

The recipe manager block (RECIPE of Type BRC_REC) of every unit requests the

recipe parameter at a recipe start from the user archive ARCH_1<EQM_ID><Recipe

type> (e.g. ARCH_10401 for parameter archive for unit 04 (=EQM_ID) with recipe type

01). As soon as the data are received, they are provided at the output REC_ST.

The recipe manager is triggered by the corresponding unit (output REQ_ST at the

recipe block BRC_REC)) at the recipe start on the input REQ0<EQM_ID>_S.

The inputs REC_REQ (=Request active) and REC_FIN (=Request completed) show

the current hand shake state with the OS server.

Maximal 99 units can be connected.

System Overview BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 21

The recipe manager is also used for loading the set points. Therefore the inputs

REQ_100_S and greater are used (see chapter 15.4 Master Unit- Configure

Referencing Unit).

4.1.1.2 BatchID-Generator (BRC_BAID):

Image 5: BatchID-Generator Block

The BatchID-Generator generates an unique batch number beyond all connected

systems.

The BatchID-Generator is triggered by the corresponding unit (output QREQBAID at

the unit manager block SB_IF)) at the recipe start (via Scheduler, Start button of unit)

at the input REQ0<EQM_ID>_ST.

The batch number is provided at the output BAID_ST. Thereby the batch number

consists of the value at the input AS_NO and 5 digit of a consecutive number.

The next used batch number will be displayed at the input COUNT.

The current value for the next batch number is set via the input START_PV and a

positive edge at the input SET.

BRAUMATcompact System Overview

Engineering Manual, 06/2010, A5E02608507B-02 Page 22

4.1.1.3 Archive Manager (FB_ARCHM):

Image 6: Archive Manager Block

The archive manager block writes the recipe archive data of the batch in the user

archives ARCH_<EQM_ID> and ARCH_2<EQM_ID>. Thereby the archive manager of

each unit is triggered via the inputs REQxxx_S. The archive manager receives for each

unit 2 data types.

1. Header Data:

The header data are provided per each unit by the block ARCH_HEAD. Thereby

the header data are transferred by the block ARCH_HEAD once at the recipe

start (starting time) and once at the recipe end (ending time). The archive

manager writes these data on a data record in the user archive

ARCH_2<EQM_ID> via the data server.

2. Step Data:

The step data are provided per each unit by the block ARCH_STEP. Thereby

the step data are transferred after 18 consecutive steps and at the end of the

unit by the ARCH_STEP block to the archive manager. The archive manager

writes these data via the OS server on a data record in the user archive

ARCH_<EQM_ID>.

System Overview BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 23

4.2 Unit Plan

The unit plan or Sequence plan processes exactly one unit. The Sequence plan

consists of 6 partitions

1. Partition A:

Connection of the first 32 Control Modules and basic configuration of the unit

2. Partition B:

Connection of the second 32 Control Modules

3. Partition C:

Connection of the third 32 Control Modules

4. Partition D:

Connection of the fourth 32 Control Modules

5. Partition E:

24 Parameter blocks for the set point handling

6. Partition F:

controls the recipe on the unit and consists of the sequence control (1), the

interface blocks to the system plan (4,5) and interface blocks to the parameters

(2,3).

4.2.1 Unit 



 Control module (Partition A , B , C and D)

The Control Modules are connected to the unit in the Partition A, B ,C and D. Thereby

4 connection blocks are available.

There is also a connection block available for the analogue values of the unit in

partition F (2,3).

Each Control Module receives internally a virtual ID between

1 and 32 (first 32 Control Modules)

or between 65 and 96 (second 32 Control Modules)

or between 97 and 128 (third 32 Control Modules).

or between 129 and 160 (fourth 32 Control Modules).

These virtual Control Module ID is used for defining the input resp. output on the 4

connection blocks.

BRAUMATcompact System Overview

Engineering Manual, 06/2010, A5E02608507B-02 Page 24

4.2.1.1 Feedback (FB_CM , FB_CMY ,FBc_CMW , FBd_CMZ)

Image 7: Connection Feedback Control Module

The feedback output of the control module is connected to the feedback blocks. This is

QOPENED for a valve, QRUN for a motor, or Q for a sensor.

System Overview BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 25

4.2.1.2 Manual/Automatic Response (FB_AUTO , FB_AUTOY , FBc_AUTOW ,

FBd_AUTOZ)

Image 8: Connection Feedback Control Module

On the manual/automatic respond blocks the manual/automatic response of the control

modules is connected. This is QMAN_AUT for a valve or motor. In case of a sensor

this access remains idle.

BRAUMATcompact System Overview

Engineering Manual, 06/2010, A5E02608507B-02 Page 26

4.2.1.3 Interlock Response (FB_LOCK , FB_LOCKY , FBc_LOCKW ,

FBd_LOCKZ)

Image 9: Connection Interlock Control Module

The interlock response of the control module is connected at the interlock response

blocks. This is V_LOCK for a valve and LOCK for a motor. In case of a sensor this

access remains idle.

System Overview BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 27

4.2.1.4 Triggering (CMD , CMDY , cCMDW , dCMDZ)

Image 10: Connection Triggering Control Module

The triggering of the control modules is connected to the trigger blocks. This is

AUTO_OC for a valve and for a motor. In case of a sensor this access remains idle.

BRAUMATcompact System Overview

Engineering Manual, 06/2010, A5E02608507B-02 Page 28

4.2.1.5 Analogue Values (Input AVxx on U_U_SYN)

Image 11: Connection Analogue Values

Analogue values are linked to the unit via the unit interface block (U_U_SYNC).

System Overview BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 29

4.2.2 Unit 



 Parameter (Partition E)

For each unit are 24 parameter blocks available. During the runtime the parameter

blocks evaluate the certain parameterized function step-respectively (actual value >=

set point, actual value = set point, time expired, counted measured reached, ...)

compared to the set point.

Image 12: Parameter Block

The set point is transferred to the parameter block (SP_VAL_A) with every step switch

via the recipe block RECIPE. As soon as the current data are available at the

parameter block, a positive edge is generated at REC_OKP, thereby SP_VAL_A is

written on Q_SP_VAL and evaluated. If the parameter is a counter or timer, the

counting /timing process is started via the input TIME_REL. Thereby the use of the

parameter (=Starting process) is configured in the recipe.

The current analogue value for comparison is available at the input for the comparison

set point with analogue value.

Q_RESULT shows if the parameter conditions are fulfilled (=1) or not (=0). This value

will be evaluated as forward condition.

BRAUMATcompact System Overview

Engineering Manual, 06/2010, A5E02608507B-02 Page 30

4.2.3 Unit Number

A basic component of BRAUMAT compact is that every unit must receive a unique ID

(EQM_ID). This will be

1. Entered at the unit interface block U_U_SYNC at the input EQM_ID.

2. In the text library (Worksheet 2) of the EXCEL ADDIN 02_TextLib_Unit.xls.

3. Used in the archive configuration for different archives (see 5.4.1.2 File WinCC

User Archive)

Via the unit number the texts are read from the text library during runtime. Thereby the

EQM_ID is multiplied by 1000. The step names, logic names, operating requests,

parameter names including the dimension and the name of the analogue values follow

after the complete 1000th entry in the text library.

The user archives for the batch data and set points contain each the EQM_ID in their

name. (ARCH_<EQM_ID>, ARCH_2<EQM_ID>, ARCH_1<EQM_ID><recipe type>.

The proper allocation between user archive and unit is made via the naming and

EQM_ID.

The EQM_ID serves as key in the user archive BRC_UNI_PARAMETER and

BRC_UNIT.

4.3 Unit Sequence 



 Text Allocation

All texts for the step names, logic names, operating requests, parameter names

including the dimension and the names of the analogue values are entered for each

unit in an available Excel file e.g.MK_TextLib_Unit.xls.

When opening the control matrix Engineering Faceplate (Step sequences

configuration), the according configuration display is opened and the texts are read and

written in the text library. This process is carried out only for the currently active

language.

4.3.1 Unit Sequence 



 Recipe Configuration

Up to 32 recipes can be defined in the WinCC Runtime. Thereby each recipe receives

a internally unique ID between 1 and 32.

Step sequences (1 to 32) are configured for each unit. Whereas the first step sequence

is allocated to the 1

recipe, the 2

step sequence to the 2

recipe etc, i.e. the recipe

consists of the step sequences of the involved units.

All step sequences are stored in the PLC and in the user archive. In order that the

recipe data are available also after a complete loading, they have to be read back in

the CFC plan via the plan read back (Designated Parameters).

System Overview BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 31

4.3.2 Scheduler 



 Unit

Image 13: CFC Scheduler

The scheduler plan contains a block (BRWP) centrally, which contains and controls all

orders. A batch is started to each order via the START block.

Thereby a scheduler is always connected to exactly one unit (the so called start unit of

a brew line). That way the scheduler starts exactly this unit. All following units are

started via a running unit depending on the recipe.

BRAUMATcompact System Overview

Engineering Manual, 06/2010, A5E02608507B-02 Page 32

4.4 Sequencer with Status Diagram

The following image shows the status diagram of the sequencer

Image 14: Status diagram Sequencer Control

The initial position of each sequencer of each unit is the idle state.

Status transitions with Self completing (sc) and Continuous as known from the

SIMATIC Batch are not available in the BRAUMAT compact.

System Overview BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 33

The state of the status diagram can be changed by the user, by application and the

BRAUMAT compact library.

Image 15: User interface status diagram

Image 16: Application interface status diagram

BRAUMATcompact System Overview

Engineering Manual, 06/2010, A5E02608507B-02 Page 34

4.4.1 



 Status Transition Idle 



 Starting

The status transition Idle  Starting is carried out via



The operator prompt when the user pushes start



The application in the P_UINT.Start is equal TRUE (e.g. Scheduler or USTA

FB)



The application sets U_A_PREV.Start or U_B_PREV.Start equal TRUE.

The batch ID and the parameters are read, before the unit transfers from idle into

starting.

4.4.2 



 Status transition Starting 



 Running

The status transition Starting –> Running is carried out automatically by the BRAUMAT

compact blocks as soon as the sequencer Starting finished its last step.

The sequencer for Starting is carried out in the status Starting.

4.4.3 



 Status transition Running 



 ready to complete

The status transition Running –> ready to complete is carried out automatically by the

BRAUMAT compact blocks as soon as the sequencer Running finished its last step.

The sequencer for the recipe is carried out in the status Running.

4.4.4 



 ready to complete 



 Completing

The status transition Ready to Complete –> Completing is carried out automatically by

the BRAUMAT compact blocks.

The status Ready to Complete is pending only for one cycle.

4.4.5 5

5 Completing 



 Completed

The status transition Completing –> Completed is carried out automatically by the

BRAUMAT compact blocks, as soon as the sequencer Completing finished its last

step.

The sequencer for Completing is carried out in the status Completing.

4.4.6 



 Completed 



 Idle

The status transition Completed –> Idle is carried out automatically by the BRAUMAT

compact blocks.

4.4.7 



 Running 



 Holding

The status transition Running  Holding is carried out by



The operator prompt when the user pushes Hold



The application sets the input connector I_HOLD at the block

4.4.8 



 Holding 



 Held

The status transition Holding –> Held is carried out automatically by the BRAUMAT

compact blocks, as soon as the sequencer Holding finished its last step.

The sequencer for holding is carried out in the status holding.

System Overview BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 35

4.4.9 



 Held 



 Resume

The status transition Held  Resume is carried out by



the operator prompt when the user pushes Resume



the application sets the input connector I_RESUME at the block

4.4.10 







 Resume 



 Running

The status transition Resume –> Running is carried out automatically by the

BRAUMAT compact blocks, as soon as the sequencer Resume finished its last step.

The sequencer for Resume is carried out in the status Resume.

4.4.11 



 … 



 Abort

The status transition …  Abort is carried out by



The operator prompt when the user pushes Abort



The application sets the input connector I_ABORT at the block

The input connector I_ABORT operates only in Starting, Running, Holding,

Held, Resume, and Completing.

4.4.12 







 Aborting 



 Aborted

The status transition Aborting –> Aborted is carried out automatically by the BRAUMAT

compact blocks, as soon as the sequencer Aborting finished its last step.

The sequencer for Aborting is carried out in the status Aborting.

4.4.13 







 Aborted 



 Idle

The status transition Aborted –> Idle is carried out automatically by the BRAUMAT

compact blocks.

4.4.14 







 … 



 Stopping

The status transition …  Stopping is not addressable in the BRAUMAT compact.

4.4.15 



5

5 Stopping 



 Stopped

The status transition Stopping  Stopped is carried out automatically by the

BRAUMAT compact blocks, as soon as the sequencer Stopping finished its last step.

The sequencer for Stopping is carried out in the status Stopping.

4.4.16 







 Stopped 



 Idle

The status transition Stopped –> Idle is carried out automatically by the BRAUMAT

compact block.

BRAUMATcompact System Overview

Engineering Manual, 06/2010, A5E02608507B-02 Page 36

4.5 Options of step behavior

4.5.1 Behavior at the command Resume after Hold

Via the input connector I_RESMODE at the block U_U_SYN you can configure

between two versions at the command Resume. If the input is configured on 1, the

previous function will be continued after the Resume command. If a 0 is configured at

the input, the step sequence starts from the beginning.

4.5.2 Reset of the Aggregates

At the step switch can basically 2 modes per unit be configured. All aggregates remain

in the state of the previous step at a step switch, or are reset.

The according behaviour is set in the CFC plan of the according unit in the A5 at the

block U_U_SYN at the input I_TRNSMDE (1= reset all aggregates, 0=all aggregates

remain in the state of the previous step. Thereby aggregates are switched shock-freely,

when they are accessed in two consecutive steps.

Image 17: PhaseCon settings

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 37

5 Create New Project

Basic knowledge in SIMATIC PCS 7 is required for this chapter. Therefore SIMATIC

PCS 7 offers a training (SYSTEM course) as well as a starter documentation like e.g.

Getting Started.

5.1 General

A ready to use demo project is installed on each bundle

Basically the filing of a project is carried out via the PCS 7 usual standard. It is

recommended to use the PCS 7 assistant “New Project“.

Three levels should be used for the technological hierarchy in the PCS 7 wizard “New

Project“. SFC plan objects are not used.

Image 18: Configuration of PCS 7 Assistant “New Project“

The message numbers are recommended unambiguously in the entire CPU.

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 38

5.1.1 SIMATIC Manager

Name the PC station after your computer name.

5.1.2 Create user text library

The text library with the corresponding message texts must be copied from BRAUMAT

compact Library in the user project. The following steps are to be followed:

1. Open the BRAUMAT compact Library CM_Vxx in the SIMATIC Manager via :

File>Open> Select Tab Libraries > CM_Vxx

2. Select the folder text libraries and copy the entire folder in the S7-Program-

Container of your user project.

5.1.3 HW Configuration

In the HW Configuration the communication data like IP address of the CP are to be

carried out at the corresponding network (is newly generated with this configuration),

possibly the DP address of the CPU and if requested in the project, further

configurations like time synchronisation.

Compile and load the configuration.

5.1.4 Netpro

Insert the corresponding communication card (already carried out automatically at Box

PC) for the PC station in the Netpro and set up the network address at the

corresponding network.

A connection must be inserted for the WinCC application, if not already existing.

Compile and load of the configuration.

5.2 Technological Hierarchy

The automatically generated names are to be adjusted in the plant view. They should

be renamed as follows:

System(1)  e.g. brew house or cellar

Unit(1)  e.g. lauter tub

Function(1)  Sequence

Parallel to the hierarchy file Sequence a hierarchy file CM is generated for the control

module. Further information to the structure of the system hierarchy are in the chapter

“7 Trending“.

The technological hierarchy should be filed completely at the beginning of the project.

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 39

5.3 CFC Plans

In the following subchapters the generating of a unit and the BRAUMAT compact

system-depending plans are described. Thereby this unit has no control modules yet.

Those are explained later in the chapter “13 Control Modules“.

Miscellaneous basic settings referring the storage assignment of the CPU and the

compile process of the CFC plans are needed for a BRAUMAT compact application.

The Compiler settings are opened via the menu Options  Customize 

Compile/Download… .

Image 19: Open Compile Options CFC

In the following dialogue “Settings for Compilation/Download“ the settings for the “FC

numbers from:“ are to be adjusted on 1 to 1100.

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 40

Image 20: Compiler Settings CFC

The local data memory of the CPU must possibly be adjusted as well. The needed

storage allocation can be determined via the plan reference data dialogue in the

display local data.

Image 21: Local data

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 41

If the local data need is higher than the offline projected storage memory, then the

settings in the HW Configuration are to be adjusted in the tab Memory in the properties

dialogue of the CPU.

Image 22: Memory Adjusting of the CPU

5.3.1 System Charts

First a BRAUMAT compact application needs comprehensive plans, which are used

over all units.

The CFC plans and pictures are loaded from the BRAUMAT compact library. This is

visible the best from the plant view.

Next to the CFC plans SYSTEM and SCHEDULER the engineering picture

(Engineering.pdl) is copied from the library. A possible existing picture in the hierarchy

file of the system must be deleted.

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 42

Image 23: Filing of SYSTEM CFC Plans

5.3.1.1 System

The CFC plan SYSTEM will be filed in the hierarchy folder of the system e.g. brew

house.

The CFC plan SYSTEM contains the archive manager, the recipe manager, and the

BATCH-ID generator for this system and is used centrally by all units. The connecting

is carried out later via the unit.

5.3.1.2 Scheduler

The CFC plan SCHEDULER will be filed in the hierarchy file of the system e.g. brew

house.

The CFC plan SCHEDULER contains the scheduler and the start switch of the first

unit, which should be started from the scheduler. The connecting is carried out later via

the unit.

5.3.2 Unit

In order to include an unit in BRAUMAT compact, the CFC plan UNIT_PHCON from

the BRAUMAT compact library of the hierarchy file Sequence will be copied in the

hierarchy file Sequence of the unit. Possibly existing pictures, reports and/or CFC

plans must be deleted.

The CFC plan is renamed in e.g. unit abbreviation + Seq, e.g. ML_SEQ for the unit

mill.

See also Chapter “7 Trending“.

The connection of the unit with the system plans is carried out via the process object

view. The text file Unit_2_System_Connection is used as template data.

The CFC plan of the unit is opened in the process object view with the tab Parameter.

By means of the text file Unit_2_System_Connection the connections are edited.

The detailed process with the configuration of the connections via the process object

view is explained in the chapter “12.1 Connection via Process Object View“.

In the Sequence Control CFC plan on page A5 the number of the unit must be entered

on the input ”EQM_ID“ at the block “U_U_SYN“. This must be unambiguous and

correspond with the unit number of the Excel sheet 2 02_TextLib_Unit.xls (see chapter

“5.4.1.6 Adjust Configuration Picture“)

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 43

Image 24: Unit number in the CFC plan

5.3.3 Link the Units Together

The units must be linked together. These connections are realized via the block

“U_U_SYN“ in the sequence control CFC plan.

The inputs “U_A_PREV“ / “U_B_PREV“ establish the connection to the up streaming

and the outputs “U_A_NEXT“ / „U_B_NEXT“ to the following units.

Image 25: Connection Predecessor and Successor Units

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 44

At the block of the “first“ unit the output “U_B_NEXT“ is connected firmly on the own

input “U_A_PREV“ / “U_B_PREV“.

At all other units, which do not have two predecessors, the parameter “U_B_NEXT“ is

connected firmly on the own not used inputs “U_A_PREV“ / “U_B_PREV“.

Image 26: Short of the Predecessors Internal Connect

The following picture shows an example for the connection of the units.

Image 27: Example Connection of Units

5.4 WinCC Engineering

The WinCC Configuration is divided in two parts. The first part must be executed each

time when generating a new project. The second part is executed in the project for

each system, unit, aggregate, … .

5.4.1 Project-Specified Configuration

5.4.1.1 General Configuration

Adjustment by the user ES/OS

OS-

Client

1. Copy the file

…\Siemens\WinCC\BRAUMAT_compact\ScriptAct with the

files DateTime.act, SetDateTime.act and SetUserMachine

in your OS project directory …\wincproj\OS\ScripotAct.

 

2. Copy the folder Braumat from the directory

…\Siemens\WINCC\BRAUMAT_compact\ in your OS-Project

directory …\wincproj\OS\.

 

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 45

3. Edit the file BRC_UA2XLS.ini (contained in the Braumat folder)

and enter the path to your batch export directory at the

parameter Path=… It must be a valid directory.

 

4. Copy all picture files (*.pdl) from the directory

…\Siemens\WINCC\BRAUMAT_compact\GraCS in your OS

project directory …\wincproj\OS\ GraCS

 -

5. Copy all picture files (@*.pdl) from the directory

…\Siemens\WINCC\BRAUMAT_compact\GraCS in your OS-

project directory …\wincproj\OS\ GraCS

 

6. In case you want to use trend pictures with a 1600x1200

resolution, copy all picture files (@*.pdl) from the directory

…\Siemens\WINCC\BRAUMAT_compact\GraCS\1600x1200

in your OS project directory …\wincproj\OS\ GraCS

 

BRAUMAT compact provides an application to an automatic generating of the needed

internal variable and the row data variable per unit and function.

These variables are configured in the data file BR_TAGGEN.ini. The tag generator

application (BRC_TagGen.exe) should be configured in the start-up of the WinCC

project, so that the needed variables are generated automatically.

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 46

Image 28: Configure Tag Generator in WinCC Start-up

5.4.1.2 File WinCC User Archive

The User Archive must be selected in the feature dialogue of the computer under the

Tab start-up.

Image 29: Activate User Archive for OS

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 47

5.4.1.3 Starting BRAUMAT compact Table Generator

After installation of BRAUMAT compact is placed a symbol in the WinCC Explorer.

Through right mouse click, is opening following selection.

Image 30: Start Table Generator

It is possible to choose between 2 sheet “User Archives” and “Excel Addin”.

Image 31: Table Generator – Selection “Excel Addin”

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 48

Image 32: Table Generator – Selection “User Archives”

Button “Fill / Clear” Recipe Head Parameter: Each recipe can consist of up to 10

recipe types. Via this action the head parameter for each recipe type are generated

only once. At the moment only the recipe type 1 is supported. If it becomes necessary

to use further recipe types (see 8.2 Recipe Types), this step must be carried out for

each recipe type. Enter the recipe type number in this line to create the recipe head

parameter archive.

Button “Fill / Clear” Recipe Data: Herewith a table (e.g. 10801 for the unit 8 recipe type

1) is generated once in the user archive for the stated unit and for the stated recipe

type. If the table is already existing, the action is stopped with an error. The entered

recipe values are stored in these archives.

This step must be executed for each unit with corresponding unit number.

If it becomes necessary to use further recipe types (see 8.2 Recipe Types), the

corresponding units must be generated with the assigned recipe type number. A unit

can only be connected with a recipe type number.

Additionally recipe data must be generated for the import and export handling.

Therefore the unit 0 and the recipe type 0 must be used and the recipe data must be

generated with these values. As result the archive ARCH_10000 is created. This

archive is used for importing recipes only.

Button Batch Data / Batch Head Parameter: For each unit a archive must be filed

once for each batch and batch head parameter.

This step must be executed for each unit with corresponding unit number.

Button Units / PHCON Tables / Unit Parameter / Set point Trends / User Table /

Redundancy: These actions must be executed only once at the generating of the

project.

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 49

The archive for redundancy cannot be generated until the redundancy is activated in

the WinCC explorer.

The archive names are each generated automatically after the entry in the white arrays

and updated in the according grey text array (in the middle of the image). Furthermore

the status of the archive is controlled and displayed in the colored array to the right.

The colouring should communicate fast and easily to the setter as well as the operator,

if a user archive is generated correctly.

The following states are possible:

• 0 (red)

Archive does not exist, but is needed for the correct operation of the BRAUMAT

compact. Therefore the corresponding button is released and generates after operating

this, archive and if necessary pre allocated data sets.

• 1 (yellow/green)

Archive exists, however does not contain data sets. This is required for the following

archives, and therefore displayed in green:

The remaining receive in this case a yellow status symbol, i.e. the pre allocated data

sets are missing in this archive. Therefore the corresponding button is released and

must be operated.

• 2 (green)

Archive exists and contains data sets. Nothing needs to be done, therefore the

corresponding button is deactivated.

The following archives are generated as result. Here on the example for 7 units.

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 50

Image 33: User Archive for 7 units

The report data in the user archives (ARCH_<UnitID> and ARCH_2<UnitID) are

archived automatically. For further information please refer to chapter 15.20 Batch data

export and supervision of the batch archive.

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 51

5.4.1.4 Adjust Engineering Picture

The objects are filed in a own Typical.PDL with the name “@BRC_Typicals.PDL“.

The objects are copied from here in the picture “Engineering.PDL“ and connected with

the Dynamic Wizard “Connect Picture Block with Test Point“.

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 52

Image 34: Unit configuration

For the connection of the picture objects to the structure variable the CFC plan of the

unit is selected under Sequence in the variable dialogue of the Dynamic Wizard. The

procedure and run-time picture object is connected to the variable PL and the

information picture object to the variable U_U_SYN and for jump set point to the

variable PL_JP.

5.4.1.5 Project Process Picture

The aggregates as well as pipelines and tank of the current unit are in the process

picture. These are placed there and connected with the known methods.

Furthermore, it is recommended to set up a status resp. operating bar for the current

unit on the upper picture margin. Moreover, the status bars of the up resp. down

streaming unit(s) can be set up there.

The objects are filed in a own Typical.PDL with the name “@BRC_Typicals.PDL“.

From there the objects are copied in the corresponding process picture and connected

with the Dynamic Wizard.

Image 35: Status bar for current on unit

In order to connect the picture object on the structure variables the CFC plan of the unit

is selected under Sequence in the variable dialogue of the Dynamic Wizards and linked

on the variable PL.

A block view of the unit is available as a further object, which is generated and linked

identically to the status bar.

*_SEQ/PL

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 53

Image 36: Example for a Unit Block

A further object for the unit is available with this recipe display. In this object the recipe

steps are displayed at a running recipe. Should there be more steps projected than

shown in the unit recipe block, the current step (with a green background) is displayed

in the visible array. The unit recipe block scrolls automatically.

The number of visible lines can be adjusted via the property „LineNumbers“ between

10 and 32.

Image 37: Example for an Unit Recipe Block

5.4.1.6 Adjust Configuration Picture (Excel Addin – 02_TextLib_Unit.xls)

In the sheet 02_TextLib_Unit.xls of the unit are the texts filed, which appear later in the

parameter dialogue.

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 54

Image 38: Text Configuration for Unit

In general there are some “special signs“ resp. expansions to be considered:

Expansion Name Description

,se Sensor Panels of the type Sensor can only be enquired.

An installation of the sensor is not possible.

,- Isolator / Reserve

This line is shown in the dialogue unlike ,hide,

however cannot be operated.

,hide Invisible This panel is not shown in the dialogue.

,ac Actuator Panels of the type actuator can only be set. An

enquiry of the result is not possible.

,timer Time Reserved for later version.

,< Group Start Start of the group. Is written behind the first

element of the group. Can be combined with + and

–.

,< Group End End of a group. Is written behind the last element

of the group. Cannot be combined with + and –.

,<+ Grouped Start of the group. Is written behind first element of

the group. Group is closed at the opening of the

dialogue.

,<- Open Group Start of group. Is written behind the last element of

the group. Group is opened at the opening of the

dialogue.

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 55

The number (TA-No.:) and the text (Name_ in the title panel of the configuration picture

define the unit with unit number and in the clear text. Thus the text also appears in the

dialogues. The number of the unit is entered in the CFC plan of the unit (under

Sequence) in FB U_U_SYN on the Parameter EQM_ID.

Image 39: Excel Addin – Sheet 2

All aggregates of this unit are listed in the panel Control Modules. The sequence and

position of the texts must correspond to the sequence of the connection on the

sequence control blocks (FB_CM).

Image 40: Aggregate Text

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 56

In the panel Units Before / After the units are entered, which are connected with the

block “U_U_SYN“ in the sequence control CFC.

Image 41: Text Configuration Predecessor and Successor of a Unit

A successive unit is started automatically via the connection with entry in 37 resp. in

39. Via the entries in 38 resp. 40 the units can be synchronized additionally. Thereby

the units are always connected in pairs e.g. entry 37 / 38 with 35 / 36 of the successive

unit.

Unit after (Entry 37 resp. 39) Unit before (Entry 33 resp. 35)

Icon

Meaning Icon

Meaning

Start of the successive unit Confirm running of unit

Start of the successive unit and

check that this has started

Check that successive unit has

started.

Unit after (Entry 38 resp. 40) Unit before (Entry 34 resp. 36)

Icon

Meaning Icon

Meaning

Report reaching of the

synchronisation point to

successive unit

Report reaching of synchronisation

point to prior unit

Report reaching of

synchronisation point to

successive unit and wait for

feedback.

Waiting for reaching of the

synchronisation point of the prior

unit and then report this one back

Check if successive unit reached

the synchronisation point and

report

Waiting for reaching of the

synchronisation point of the prior

unit

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 57

In the panel Parameter Names all texts are entered that appear later in the recipe

parameter dialogue.

Image 42: Configuration of Parameter Texts

Icon

Meaning Icon

Meaning

without function Reset and start:

Parameter of the type time

Reset timer and start

Parameter of the type counter:

Reset counter value and if self-

counting start counter.

Without function Reset, start and request feedback:

Check all parameter types except

for report for feedback = set point.

Request Feedback:

Waiting for cooling down

(Temperature not fulfilled

anymore)

Request Feedback:

Check all parameter types except

for report for feedback = set point.

It is recommended to group the parameters.

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 58

The entire number of functions must be entered in the array “Number of Functions“. A

maximum of 64 functions is projectable.

The number of used logics is parameterized in the array “Number of Logics“. The texts

appear later in the right-mouse-menu in “PhaseControl“.

The logics themselves are generated to runtime. This is described in the user manual.

mage 43: Configuration of function texts and logics

All connected analogue values of this unit are listed in the array analogue value

names. The sequence and position of the texts must correspond to the sequence of

the interconnections at the sequence – control block (U_U_SYN).

Image 44: Configuration of analogue texts

The number of the analogue values must be entered. The selection box for the

analogue value in the parameter type dialogue is configured in its size (number of

displayed analogue values) via the number of analogue values.

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 59

All operator requests for this unit are listed in the array texts for the operator request.

An operator request can be reserved for each function. The first operator request can

be used in the first function step, the second in the second function step, etc. With the

check on visible the button „Information“ for the respective operator request is switched

on. The presetting UNIT_PHCON_ORX.pdl e.g. 08_PHCON_OR2, unit 8, operator

request 2 is here available for the user. The examples can be deleted from the image.

mage 45: Configuration operator request

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 60

5.4.2 Runtime Configuration

The configuration of the parameter types, the recipe and the parameter is carried out in

the OS Runtime.

5.4.2.1 Parameter Types

For each unit the according type can be configured per each configured parameter.

 The parameter types are transferred to the control via this dialogue. There is no

other way to transfer these data to the PLC.

Image 46: Parameter type dialog

For each parameter:



Display type: Number of the decimal places, time format, …



Function: function of the corresponding parameter e.g. time forwards

automatically one in each cycle.

The hysteresis (down/up) is available in the function set point/actual value

comparison. The hysteresis is not editable in all other functions.



Minimal Value: value that can be entered minimally in different dialogues of the

system. If this step is undercut, a warning note is given out and the entry cannot

be accepted.



Maximal Value: Value that can be entered maximally in different dialogues of the

system. If this step is exceeded, a warning note is given out and the entry will

not be accepted.



Hyst. down: If a function with set point/actual value comparison is selected, the

set point regulation in the interval of the set point minus lower hysteresis is

considered as fulfilled.

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 61



Hyst. up: If a function with set point /actual value comparison is selected, the set

point regulation in the interval of the set point plus upper hysteresis is

considered as fulfilled.

 The edit windows can be released via ESC.

The following table shows all functions and their mode of operation in the function

block BRC Real.

Image 47: BRC_REAL Block

Id Function Mode of Operation Hysteresis

00 Off Parameter is not used (=no function) No

01 Counter

forward Increases the actual value per each cycle (!) by INC

times ACT_VAL (only valid for AV_SRC = 0) No

02 Integrator Increases the actual value for each cycle by INC times

SAMPLE_T times ACT_VAL (only valid for AV_SRC =

0).

03 Counter

backwards Decreases the actual value for each cycle(!) by INC

times ACT_VAL (only valid for AV_SRC = 0) No

04 Time

forward Increases the actual value of each cycle by SAMPLE_T

(=> time forward) No

05 Time

backward T Increases the actual value of each cycle by SAMPLE_T

(=> time forward) but will not reset on step change No

06 Time

backward Decreases the actual value per each cycle by

SAMPLE_T (=> time forward) No

07 Set point =

Actual Value

Checks the analogue value with the set point

considering the hysteresis Yes

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 62

08 Actual Value

>= Set point Compares the analogue value to the set point with

greater than No

09 Actual Value

<= Set point Compares the analogue value to the set point with

smaller than No

10 Protocol Is only shown in the report. The result is always TRUE No

11 Integrator

with Hold Integrator analogue Function 02 Integrator, however it

holds the value in the cycle Hold  Held  Resume.

Therewith this parameter has the same value at the

abandoning and reentry of the status Running.

12 reserved Reserved for later versions No

5.4.2.2 Recipe step sequence

The recipe step sequence is defined in the cross points recipe with step by a single

click. Thereby the step counter (=number that appears in the square generated by a

single click) increases automatically with every click.

Image 48: Step Sequence Configuration

In the upper left corner of the matrix are click squares for deleting (x) increasing (+)

and decreasing (-) the steps by 1, 5 or 10steps.

5.4.2.3 Recipe Steps

Via switching the button ->> you can switch from recipe display to step display. For

each control module (pump, valve, motor, sensor, …) the triggering is set in the step

display and the feedback is evaluated. Furthermore, parameters are defined for this

step (see also chapter 5.4.1.6).

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 63

The following settings can be provided for each cross point by repeated single click.

Between 0 and 1 can be switched with the right mouse click.

Image 49: Color Display of the Control States.

Symbol Meaning Description

Force and

Feedback Control Module is started/opened/fulfilled and the

response is checked

Force and

Feedback Control Module is stopped/completed and the

response checked

Force Control Module is started/opened/fulfilled.

The response is not(!) checked

Force Control Module is stopped/completed.

The response is not(!) checked

Check The response is checked for started/opened/fulfilled.

A triggering does not occur.

Check The response is checked for stopped/completed.

A triggering does not occur.

5.4.2.4 Recipe parameter

The current recipe parameters are loaded in the recipe parameter dialogue via the

recipe parameter button ( ). Via the single click on the step name (1) the

corresponding step appears in the recipe parameter dialogue with name (2) and

number (3). The unit name (4), recipe name (5), and the recipe type (6) are displayed

as information.

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 64

Image 50: Recipe Parameter Configuration

5.4.2.5 Edit Logic in a recipe

The control matrix supports the condition based logic in recipes.

The logic is configured in the engineering faceplate. Click right on a rectangle in the

logic no column. Choose the logic that should be used.

Image 51: Select logic

In the control matrix right mouse click on any cross point in the row with logic then you

can choose:

1. Switch depending on logic

The control module is activated as soon and as long the logic is true. Feedback

is not used for next step condition.

2. Switch depending on logic and wait for feedback on

The control module is activated as soon and as long the logic is true. The step

waits for a feedback to go to next step.

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 65

Image 52: Select logic as enabling condition

The logic itself is configured via right mouse click on the control module name. This

changes the view to the logic view.

BRAUMATcompact Create New Project

Engineering Manual, 06/2010, A5E02608507B-02 Page 66

Image 53: Configure Logic

Left click on logic gutter switches between OR or AND logic. (figure xx, section 1). In

section 2 the logic is configured via right mouse click. The result used for the

corresponding control module is build at the top of this logic tree. With go back you

come back to recipe configuration. Logic data is saved with normal save of the recipe.

Create New Project BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 67

5.5 Control modules

5.5.1 Insert and connect control modules

In the BRAUMAT compact library is a series of typicals, which can be copied manually

or via IEA assistant in the project. This should be filed in the file “CM“ below the unit.

Image 54: Available control modules in BRAUMAT compact

The needed control module is copied from the BRAUMAT compact library and in the

corresponding CM hierarchy file of the unit.

The connection to the periphery as well as the connection to the control block in the

plan sequence can be established manually or with the process object view (see

chapter “12.1.2 Aggregate“).

Then the control modules must only be connected to the physical inputs and outputs of

the periphery.

In chapter “13 Control Modules“ the available control modules of BRAUMAT compact

are explained explicitly.

5.5.2 Connection / Import via IEA-Assistant

See PCS 7 manual and PCS 7 Online documentation

BRAUMATcompact Excel Addin

Engineering Manual, 06/2010, A5E02608507B-02 Page 68

6 Excel Addin

6.1 General

It is obligatory for the parameterization of the text library and the user archives.

Furthermore, this Excel Addin enables the import and export of configuration and

recipe parameters.

6.1.1 Requirements

6.1.1.1 Software

• Microsoft Excel 2003/2007

• Min. WinCC 6.2



Microsoft Excel is not included and must be installed and licensed by oneself !

6.1.1.2 Hardware

• Minimum Requirements

o Processor : Inter Core2Duo

o Clock rate : 2,4 GHz

o Main storage: 1,0 GB

o Hard drive : 250 GB SATA

6.1.2 Development Environment

The Excel Addin is based on Microsoft Excel and consists of four Excel –

workbooks.

The workbooks can be given unit specific names. This enables an unit granular

projection and archiving.

The workbooks „01_TextLib_General.xls“, “01_TextLib_Recipetypes.xls”,

“01_TextLib_RecName_for_Rectype1.xls” and „02_TextLib_Unit.xls“ are used

for the parameterization of the text library.

„03_Archive_Unit_Para.xls“ and „04_Archive_Unit.xls“ are used for the import

and export of the configuration and recipe parameters from the user archives.

Excel Addin BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 69

6.1.3 General Settings in order to work with the Workbooks

The setting „Macro Security“ must be set on „low“. This must be changed in the

workbook in Extras/ Options in the tab „Security“ at the feature „Macro Security“.

Image 55: Macro Security

BRAUMATcompact Excel Addin

Engineering Manual, 06/2010, A5E02608507B-02 Page 70

6.1.4 Online - / Offline - Mode

In the workbooks 03_Archive_Unit_Para.xls“ and „04_Archive_Unit.xls“ is an

Online - / Offline – Mode available.

In the online mode the unit texts (e.g. unite name, function names, logic names,

etc.) are loaded from the WinCC text library and linked in the workbook.

The online mode can only be used, when the respective WinCC project is

opened.

 With the start of the workbook the stated unit with the corresponding recipe

type is loaded e.g. unit 2 with recipe type 1. If a different unit is selected after

afterwards, the readout of the function names and the control module be

updated with the button ‘Update texts’.

Image 56: Workbook „Online Mode“

Excel Addin BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 71

In the offline mode default values can be embedded in the workbook.

Image 57: Workbook „Offline Mode“

For the steps and parameters the altered texts are replaced by step 1…64 resp.

parameter 1…24 and dim 1…24 by using the button “Generate default texts“.

Image 58: Default Texts

BRAUMATcompact Excel Addin

Engineering Manual, 06/2010, A5E02608507B-02 Page 72

The setting Online /Offline Mode is carried out in the workbook features in the

tab ‚user defined’.

 This is only possible when the workbook is closed.

Image 59: „Online - Offline Settings“

Excel Addin BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 73

6.1.5 Workbook - 01_TextLib_General.xls

Worksheet 1 “General“:

The entries in the text library and for the parameterization of the recipe type

names can be generated here in German, English and a selectable third

language.

The button “Generate Entries“ opens a form for the generation of a text library

entries.

The generation gets started with the button „Preconfigure textlibrary“.

This is a one-time, mandatory step at the generation of a new project. This

action takes up to 20 minutes.

 If a text library exists already, an error will be generated .

“The TextId - range(>=1000) is already occupied by a different application!!“

Image 60: Workbook 01_TextLib_General.xls

BRAUMATcompact Excel Addin

Engineering Manual, 06/2010, A5E02608507B-02 Page 74

6.1.6 Workbook - 01_TextLib_ Recipetypes.xls

Worksheet 1 “Recipe Types“:

The recipe type names can be parameterized in German, English and a

selectable third language.

The button “Write recipetypes to textlib“ starts the download to the text library.

Image 61: Workbook 01_TextLib_ Recipetypes.xls

Excel Addin BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 75

6.1.7 Workbook - 01_TextLib_RecName_for_Rectype1.xls

Worksheet 1 “Recipe Types“:

The recipe type names can be parameterized in German, English and a

selectable third language.

The button “Write recipenames to textlib“ starts the download to the text library.

Image 62: Workbook 01_TextLib_RecName_for_Recipe type1.xls

BRAUMATcompact Excel Addin

Engineering Manual, 06/2010, A5E02608507B-02 Page 76

6.1.8 Workbook 2 - 02_TextLib_Unit.xls

This workbook is used for the generation of unit parameter.

Worksheet 1 “Cover sheet“:

Parameterized are:

• Unit name (German/English)

• Unit number

• Number of units

• Number of control modules

• Number of functions

• Number of logics

• Unit is master or referencing

• Number of the master unit (only possible if unit is set in the “Referencing“

mode)

The unit text library can be generated and read with the two arrays.

Image 63: Workbook 02_TextLib_Unit.xls „General“

Excel Addin BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 77

Worksheet 2 „Parameter Unit“:

• Name of control modules

• Name of functions

• Texts for operator request

• Logic names

• Analogue value names

Image 64: Workbook 02_TextLib_Unit.xls „Parameter Unit“

Worksheet 3 „Parameter Unit“:

The parameters are entered in the worksheet 2 for English.

BRAUMATcompact Excel Addin

Engineering Manual, 06/2010, A5E02608507B-02 Page 78

6.1.9 Workbook 3 - 03_Archive_Unit_Para.xls

This workbook is used for the import and export of recipe parameters (set

points).

This data file can be used for the parameterization and for the archiving of unit

parameters.

Worksheet 1 “Cover sheet“:

• Unit number

• Recipe type of this unit

With the selection of the unit number and the recipe type the archive that is to be

read out is generated automatically e.g. Unit:2 ; Recipe type:1  ARCH_10201

The button “Write in User Archive“ starts the loading from the Excel file in the

unit user archive.

The button “Read from User Archives“ starts the loading from the unit user

archive in the Excel file.

 If a user archive of a selected unit does not exist, the read out resp. writing is

aborted with an error message.(error number:101)

Image 65: Workbook 03_Archive_Unit_Para.xls „General“

Excel Addin BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 79

Worksheet 2-33 „Recipe 1“ to „Recipe 32“:

Each work sheet stands symbolically for a unit recipe. 24 parameters are

parameterized for each of the 32 steps.

The yellow marked texts are read out directly from the text library when opening

the workbook, if the online mode is selected.

Image 66: Workbook 03_Archive_Unit_Para.xls „Recipe“

BRAUMATcompact Excel Addin

Engineering Manual, 06/2010, A5E02608507B-02 Page 80

6.1.10 Workbook 4 - 04_Archive_Unit.xls

This workbook is used for the import and export of the unit parameterization.

Control strategies, functions, and logics of a unit are displayed here.

This file can be used for the parameterization and for the archiving of unit

parameters.

Worksheet 1 “Cover Sheet“:

• Unit number

• Recipe type of this unit

• Plan - Name

The user archives PHCON_CS2,PHCON_FCT2 and PHCON_LOGIC2 are read

out:

Image 67: User Archive PHCON_FCT2

The button “Write in User Archives“ starts the loading in the user archive of the

unit.

The button “Read from User Archives“ starts the loading from the unit user

archive in the Excel file.

 If an incorrect plan name is stated, e.g. the read out is displayed with the error

number 104.

Image 68: Workbook 04_Archive_Unit.xls „General“

Excel Addin BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 81

Work sheet 2 „CS“:

• The chain sequence of the steps in the recipes is parameterized here.

• They must be parameterized numerically increasingly. Furthermore, steps may not be

selected double and all values must be provided in the sequence of numbers.

Image 69: Workbook 04_Archive_Unit.xls „CS“

Worksheet 3 „FCT“:

• The triggering of the control modules in the steps.

Image 70: Workbook 04_Archive_Unit.xls „FCT“

BRAUMATcompact Excel Addin

Engineering Manual, 06/2010, A5E02608507B-02 Page 82

WinCC Command =

0 Command =

_____________

Excel Addin BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 83

Worksheet 4 “Logic“:

• If a logic is used for the a unit, the provided logic number must be entered at the control

module.

Image 71: Workbook 04_Archive_Unit.xls „Logic“

BRAUMATcompact Excel Addin

Engineering Manual, 06/2010, A5E02608507B-02 Page 84

Worksheet 5 to 37 “Logic 1“ to “Logic 32“:

•

Each worksheet stands symbolically for a unit logic.

Image 72: Workbook 04_Archive_Unit.xls „Logic1 “

Excel Addin BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 85

6.1.11 Possible Error Sources

6.1.11.1 03_Archive_Unit_Para

• Connection is set up to the data base?

• WinCC Project in Runtime?

• User Archive Editor is started?

• User archives exist?

• Correct unit is selected?

• Correct recipe type is selected?

• Correct CFC plan name is entered?

• Data records existing?

o Is a data record with the CFC plan name existing in the user archive

PHCON_CS2?

o Is a data record with the CFC plan name existing in the user archive

PHCON_FCT2?

o Is a data record with the CFC plan name existing in the user archive

PHCON_LOGIC2?

6.1.11.2 04_Archive_Unit

• Connection is set up to the data base?

• WinCC Project in Runtime?

• Or is User Archive Editor started?

• User archives exist?

• Correct unit is selected?

• Correct recipe type is selected?

• Correct CFC plan name is entered?

• Data records existing?

o Is a data record with the CFC plan name existing in the user archive

PHCON_CS2?

o Is a data record with the CFC plan name existing in the user archive

PHCON_FCT2?

o Is a data record with the CFC plan name existing in the user archive

PHCON_LOGIC2?

BRAUMATcompact Trending

Engineering Manual, 06/2010, A5E02608507B-02 Page 86

7 Trending

The picture BR_TREND_OV.pdl is used for the trending.

For example this can be added via WinCC Picture Tree Manager or an own virtual unit

in the technological view can be added for the reports.

Image 73: Trending in the plant view

The picture does not need any further configuration.

For each unit a further picture @BR_TREND_UNIT_xx.pdl must be configured.

Therewith xx is replaced by the unit number. The same unit number as in the CFC plan

of the unit in the parameter EQM_ID of the FB U_U_SYN (see chapter “5.3.2 Unit“)

and as in the text configuration picture of the unit in the caption is entered (see chapter

“5.4.1.6 Adjust Configuration Picture“).

The picture @BR_TREND_UNIT_01.pdl from the BRAUMAT compact library is used

as template for the trend picture @BR_TREND_UNIT_xx.pdl.

The variables for the trending for the corresponding units must be entered in the trend

control in the WinCC Graphic Designer. Below the trend control the name of the unit is

entered in the static text.

 The picture name @BR_TREND_UNIT_xx.pdl can also be renamed in an individual

name like TREND_Mill.pdl. This name must then be entered manually in the user

archive BRC_UNIT (see also chapter “14.2 Contents and Settings“)

Recipe Configuration BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 87

8 Recipe Configuration

The recipe configuration prepares the recipe name contribution in the runtime

environment.

Image 74: Recipe Configuration

The dialogues recipe types and recipe names are described in the following chapters.

8.1 Recipe configuration

The recipe names are configured in the dialogue recipe names in the OS Runtime.

8.2 Recipe Types

Recipe types are used, when two areas of a brewery are controlled with one

BRAUMAT compact system e.g. brew house and cellar. In this case the same recipes

are available at the same recipe type for both areas. Recipes of the brewery cannot be

executed in the cellar and vice versa. Therefore, the recipes can be grouped in

different recipe type’s e.g. brew house and cellar.

A user archive must be generated for each recipe type via the table generator (see

also chapter 5.4.1.2 File WinCC User Archive paragraph „Button “Fill / Clear” Recipe

Head Parameter:“).

The recipe types are configured in the OS Runtime in the prompt for recipe types.

However, only those recipe types are shown in this online view, for which a

corresponding archive was generated before in the user archives. All others are not

valid.

A unit can only be connected with a recipe type number. The recipe type is configured

in the CFC plan SCHEDULER in the function block START of the type BRC_USTA

BRAUMATcompact Recipe Configuration

Engineering Manual, 06/2010, A5E02608507B-02 Page 88

Image 75: Recipe Type Settings

For further recipe types the archives must be filed for each unit in the dialogue for

archive generating (see also chapter “5.4.1.2 File WinCC User Archive”).

A unit can only be connected with a recipe type number.

8.3 Start units with different recipes

In the standard connection in the units CFC plans the following unit is started with the

same recipe number as the accessed unit. If a following unit should be started with

another recipe number, this can be done via the function block BRC_USTA. The

connection of the function block BRC_USTA for the following unit is described in the

chapter “15.1.2 Units: BRC_USTA: (TA starter FB1108)“.

In order to start a different recipe on a following unit, the according recipe number must

be configured at the input connector RECTID.

Image 76: Default recipe number

Recipe Configuration BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 89

Typically this is used to start CIP from a unit. One recipe CIP (e.g. No 20) is available

in all units. There is a recipe for each unit that should be cleaned in the unit CIP (e.g.

recipe 01: CIP mill, recipe 02: CIP mashing tub, …). In the according unit the recipe

number is to be entered definitely for the CIP unit.

8.4 Different recipe types in the brewery

Different recipe types are used in different areas (e.g. brew house, CIP, cellar) need

different recipes. In the brew house the recipes are e.g. 01: Pils, 02: Wheat, 03:Lager,

… and in CIP 01: Clean mask cooker, 02: Clean worth pool, 03: Clean lauter tub.

8.4.1 Assign recipe type to unit

Each unit can be assigned to one recipe type only.

The recipe type is configured in sequence chart at input RECT_ASS from block

U_U_SYN. Default 1 is configured.

Figure 77: Recipe type 2 configured in sequence chart

BRAUMATcompact Recipe Configuration

Engineering Manual, 06/2010, A5E02608507B-02 Page 90

8.4.2 Start unit with different recipe type

Is the unit started via block BRC_USTA block (see Chapter 15.1.2) then the recipe type

has to be configured fix. Also the recipe number should be configure at the

BRC_START block. Alternative the recipe number can be connect to a dedicated

parameter.

Figure 78: Start unit with configured recipe type and recipe number

For configuration with scheduler see chapter 8.2 Recipe Types Image 75: Recipe Type

Settings

 Before using the recipe type the WinCC user archives must be created. How to

proceed see chapter 5.4.1.2 File WinCC User Archive especially the Button “Fill /

Clear” Recipe Head Parameter: and the Button “Fill / Clear” Recipe Data: are used.

Scheduler BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 91

9 Scheduler

9.1 CFC Plan

The scheduler is implemented in the CFC plan SCHEDULER. The CFC plan scheduler

can be copied from the BRAUMAT compact library.

The scheduler has in A2 a START block for the connection of the units, which should

get started. This unit starts the remaining process via successor units.

Image 79: Connection of Scheduler to the Process

BRAUMATcompact Scheduler

Engineering Manual, 06/2010, A5E02608507B-02 Page 92

The parameter P_UNIT in the block START is connected internally to the block 1 (Type

BRC_UIF). This connection must be disconnected and the block 1 (Type BRC_UIF)

can be deleted.

The parameter P_UNIT in the block START is connected only to the unit, which should

get started. Therewith this parameter is connected to the parameter P_UNIT of the

block U_U_SYNC in the CFC plan of the unit (filed in Sequence).

9.2 WinCC Engineering

The picture BR_WOP.pdl is used for the scheduler.

This can be added e.g. via the WinCC Picture Tree Manager or a own virtual unit in the

technologic view can be added for the scheduler.

Image 80: Trending in the plant view

The following internal variables are needed by the scheduler and filed in automatically.

All internal variables should be generated in the group BRAUMAT_Scheduler

Name Type

WinCCPath Text variable 8-bit symbol set

WP_ActDateTime 16-bit value w/o prefix

WP_ActUserMachine

16-bit value w/o prefix

Windows_DateTime Text variable 8-bit symbol set

WP_PrefixDate Text variable 8-bit symbol set

WP_PrefixUser Text variable 8-bit symbol set

ProjectEnableName Text variable 8-bit symbol set

Following image shows an example.

Scheduler BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 93

Image 81: Example Internal Scheduler Variables

The variable names for the scheduler must be entered in the BR_WOP.pdl. The tag

name consists of scheduler CFC plan followed by the corresponding structures.

All three tag names of the „Interface blocks tag prefix“ must be configured according to

the scheduler CFC name

Image 82: Variables Connection in the scheduler

Captions and texts of the scheduler can be adjusted in the green area, however, these

data are already provided executable.

Further adjustments are not necessary for the scheduler.

BRAUMATcompact Batch Data Export and Report

Engineering Manual, 06/2010, A5E02608507B-02 Page 94

10 Batch Data Export and Report

10.1 Batch Export

The batch export copies and processes the batch data from the WinCC archives in

Excel via an application. For starting the batch export, a button “Export Data“ is

available in the @BRC_TYPICALS.pdl in the area Export Data. This button must be

copied in a picture.

In order to assure the export, the export functionality needs a data directory available

from the local computer. This directory is entered in the data file BRC_UA2XLS.ini

under Settings in the parameter Path.

Image 83: Example for BRC_UA2XLS.ini

Further configurations are not needed for the export of data.

The exported data are filed under the configured path in the subdirectory

01_Output/01_BatchReports/<CalendarYear>/<CalendarWeek>.

The batch report is always generated for the entire system with all units. For this a unit

must be configured as Master. As recommendation this should be the same unit as the

one started by the Scheduler.

For the configuration of the reference unit, the image @BRC_ExportBatchData.pdl is

opened in the Grahpics Designer and the unit ID of the reference unit must be entered

in the array IO ReferenceUnit.

Batch Data Export and Report BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 95

Image 84: Configuration of the reference unit

10.2 Batch Report

The batch report is generated via Microsoft Excel. Thereby a template, generated in

EXCEL, can be used again in BRAUMAT compact.

The function batch report needs a valid entry for the path in the file <WinCC Project

Path>BRAUMAT/BRC_UA2XLS.ini. This entry must be in the operating system. The

following entry structures are filed after the first export:

Image 85: Report Structure

Thereby the report is filed in the folder <Calendar Year> and there in <Calendar

Week>.

BRAUMATcompact Batch Data Export and Report

Engineering Manual, 06/2010, A5E02608507B-02 Page 96

The generating of the template is created from an existing batch export. After opening

the batch export in EXCEL a new table can be pasted. In this new table a batch report

according to demands and creation requests of the customer must be generated. This

altered batch export is then filed as EXCEL template under the path configured in the

BRC_UA2XLS.ini in the sub-directory 00_Templates (see Image 85: Report Structur).

Thereby the data name must be identically (case sensible) to the recipe name, which

was entered in the picture BRC_REC01_NAME in the BRAUMAT compact. If more

languages are configured in the picture BRC_REC01_NAME, a template must be filed

with the corresponding name for each language.

Technological Hierarchy BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 97

11 Technological Hierarchy

The hierarchic structure in the project should reflect the technological structure of the

system. The units (mill, mashing tub, …) form the first hierarchy level. In the next level

are two further hierarchy files (control modules or also only CM and sequence). In the

file Control Modules are the CFC plans of the single aggregates. In the file Sequence is

a CFC plan containing the control blocks. The aggregates of the units are controlled

according to sequence and recipe via this block. Furthermore, a configuration picture is

filed there. In this block are several texts deposited.(see also chapter “5.4.1.4 Adjust

Engineering Picture“)

Both CFC plans (Scheduler and System) are not assigned to a hierarchy.

Image 86: Example Hierarchy Brewery

If a unit should or must be separated in two (sub) units, a further hierarchy level is

installed below the unit. Each of these (sub) units than has the function hierarchy file

Sequence and CM again.

If several facilities e.g. brewery and cellar are implemented in a PLC, two system

hierarchy files are generated in the root level as well.

The corresponding hierarchy file as well as two sub files are generated for the new

unit.

Image 87: Hierarchy of a Unit

BRAUMATcompact Technological Hierarchy

Engineering Manual, 06/2010, A5E02608507B-02 Page 98

The file “CM” should later contain the plans for the single aggregates (valve, motor,

sensor, …). The file “Sequence“ is provided for the CFC .

The CFC for the sequence controller are copied from the BRC library in the

corresponding hierarchy file and renamed.

Image 88: Unit CFC and text configuration picture

Hereby the unit abbreviation (here e.g. MC) of the hierarchy must be included in the

name of the CFC plan resp. the control picture.

The name of the control picture consists of the name of the CFC plan + the ending

_NAME. This convention must be kept.

Connection of CFC Plans BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 99

12 Connection of CFC Plans

12.1 Connection via Process Object View

12.1.1 Unit

The blocks of the sequence controller must be connected with the recipe resp. archive

manager block. The connection via the process object view (PO view) is explained first.

First the sequence CFC (here e.g. TA_SEQ) is opened in the PO view, and then the

tab Parameter. Subsequently it is useful to sort the table according to links and then

enter the following texts in the table Connection.

SCHEDULER\BR_CLOCK.YEAR

SYSTEM\ARCHM.REQxxx_ST xxx  next free input on the connecting block

001 for first unit

003 for second unit etc.

SYSTEM\ARCHM.REQxxx_ST xxx  next free input at the connecting block

002 for first unit

004 for second unit etc.

SYSTEM\RECM.REQxxx_ST xxx  next free input on the connecting block

001 for first unit

002 for second unit etc.

SYSTEM\RECM.REC_ST

SYSTEM\BA_ID.REQxx_ST xxx  next free input on the connecting block

001 for first unit

002 for second unit etc.

SCHEDULER\BR_WP_CW.CW

SYSTEM\BA_ID.BAID_ST

SYSTEM\ARCHM.QARCH_ST

BRAUMATcompact Connection of CFC Plans

Engineering Manual, 06/2010, A5E02608507B-02 Page 100

Image 89: Connection via Process Object View (Unit No. 1)

A text file (Unit_2_System_Connection) storing the connection strings, is in the library.

These can be copied in the PO view.

The file is altered for the first unit e.g. as follows:

Image 90: Configuration Data for Process Object View (unit No. 1)

12.1.2 Aggregates

The single aggregates must be connected to the control blocks in the sequence CFC.

It is important that the single aggregate is always connected with all sequence blocks

on the same(!) “channel number“.

Connection of CFC Plans BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 101

At the connection via the process object view ( PO view) is carried out for all aggregate

types according to the same schema.

First the CFC of the aggregate is opened in the PO view in the tab Parameter and the

corresponding text is entered under Connection.

Here on the example Valve:

XX  Abbreviation of unit

xx  next free number on the control blocks

Link Connection

V_LOCK XX_SEQ\FB_LOCK.FB_xx

QOPENED XX_SEQ\FB_CM.FB_xx

QMAN_AUT XX_SEQ\FB_AUTO.FB_xx

CM_INFO XX_SEQ\U_U_SYN.QCM_INFO

AUTO_OC XX_SEQ\CMD.CMD_xx

Image 91: Connection Aggregate of the Unit MC_SEQ on Channel 08

There is a corresponding text file for each aggregate, which describes the needed

interconnection and can be used as master copy. For example the text file

BRT_V_FBCL_CONN.TXT in the BRAUMAT compact library for the valve

Here on the example motor:

XX  Abbreviation of unit

xx  next free number on the control blocks

BRAUMATcompact Connection of CFC Plans

Engineering Manual, 06/2010, A5E02608507B-02 Page 102

Link Connection

QRUN XX_SEQ\FB_CM.FB_xx

QMAN_AUT XX_SEQ\FB_AUTO.FB_xx

CM_INFO XX_SEQ\U_U_SYN.QCM_INFO

AUTO_OC XX_SEQ\CMD.CMD_xx

Image 92: Connection Aggregate of the Unit MC_SEQ on the Channel 05

See also the text file BRT_M_CONN.TXT in the library

12.1.3 Use of Configuration Text Data

The configuration file has 3 different areas:

Section 1 gives a brief overview over the functional contents.

Section 2 explains the required steps for each aggregate.

Section 3 contains a master copy with all relevant connections.

Image 93: Example of a Configuration File

Connection of CFC Plans BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 103

After the copying of the file, the file should be adjusted according to Section 3.

XX_SEQ is the CFC plan of the unit, which is filed in the sequence hierarchy file.

Xx explains the channel number for the aggregate.

Image 94: Example for a Configuration File

This configuration file connects the aggregate with the unit ConcStandardise_PHCON

with the channel 11 in the block FB_CM.

Image 95: Example of Executed Connections on Channel 11

The Section 3 is copied in the process object view column Connection via the

clipboard. Thereby the instructions in Section 2 are used.

BRAUMATcompact Connection of CFC Plans

Engineering Manual, 06/2010, A5E02608507B-02 Page 104

12.2 “Manual“ Connection of Aggregate

Instead of the connection via process object view, the connections can also be

established step by step in the CFC plans.

In the sequence control CFC on page A1 is the block FB_CM. The responses of the

aggregates are connected to its inputs.

Image 96: Connection FB_02 to QOPENED

The output “QOPENED“ is linked e.g. from the valve block and the output “QRUN“ from

the motor block.

In the sequence control CFC on page A2 is the block FB_AUTO. The confirmations of

the aggregates for manual/automatic are to be linked on this block.

Image 97: Connection from FB_02to QMAN_AUT

The output “QMAN_AUT“ is connected via the valve block as well as via the motor

block.

In the sequence control CFC on page A3 is the block FB_LOCK. It is confirmed to the

block, if the valve is locked.

Connection of CFC Plans BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 105

Image 98: Connection from FB_02 to V_LOCK

The output “V_LOCK“ is linked from the valve block.

The block CMD is on page A4 in the sequence control CFC. The single aggregates are

triggered via this block.

Image 99: Connection from CMD_02 to AUTO_OC

The block is connected with the input “AUTO_OC“ on the valve resp. motor block.

The block U_U_SYN is on pageA5 in the sequence control CFC. The single analogue

inputs are connected via this block.

BRAUMATcompact Connection of CFC Plans

Engineering Manual, 06/2010, A5E02608507B-02 Page 106

Image 100: Connection from AV02 to V

The inputs “V“ of the analogue channel driver are connected with the inputs “AV0x“ of

the block.

The input “CM_INFO“ of the respective aggregate must be connected on the output

“QCM_INFO“.

Control Modules BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 107

13 Control Modules

13.1.1 List of the Templates (acc. Master Plans)

The following list shows all premade templates.

• BRT_CNT_V2_0 Counter

• BRT_DIN_V2_0 Digital Input

• BRT_DMOF_V2_0 Monitoring function

• BRT_DMON_V2_0 Monitoring function

• BRT_M_V2_0 Motor with feedback on

• BRT_MEAS_V2_0 Analog measurement

• BRT_MOF_V2_0 Monitoring function

• BRT_MSC_MSS_MV2_0 Motor with feedback on MSS and

Maintenance

• BRT_PID_V2_0 PID controller

• BRT_PUPA_V2_0 Intervallblock

• BRT_V_FBCL_OP_V2_0 Valve with feedback open and closed

• BRT_V_FBCL_V2_0 Valve with feedback closed

• BRT_V_FBOP_V2_0 Valve with feedback open

• BRT_VDS_FBCL_OP_V2_0 Double seat valve with feedback closed /

open

• BRT_VDS_FBCL_V2_0 Double seat valve with feedback closed

• BRT_VDS_FBCL_OP_O_V2 Double SEAT valve with feedback closed and

open and without seat lifting

• BRT_VMAN Manual Valve

• BRT_MREV_CMD_U_D_V2_0 Reverse motor with commands UP and

DOWN

• BRT_MREV_CMD_S_D_V2_0 Reverse motor with commands START and

DIRECTION

• BRT_M_MSS_M_V2_0 Motor with feedback on MSS and

Maintenance

and with speed control

• BRT_AMON_V2_0 Analogue measurement

13.1.2 Functionality

All templates are described briefly below. A detailed documentation of the functionality

of the templates can be taken from the blocks Online Help.

To each template the corresponding object resp. the object group form the

@@Template _BRAUMAT_V2_0.pdl is listed additionally. The group is stated

respectively. Within the group any object can be used. The object differ within a group

only by the external display.

BRAUMATcompact Control Modules

Engineering Manual, 06/2010, A5E02608507B-02 Page 108

BRT_CNT Counter

This template contains a counter. This can count forwards as well as backwards via

impulse inputs.

Object group: BRT_CNT

BRT_DIN Digital Input

This template contains the block “BRT_DIN“. Digital signals can have a switch on and

off delay. The signal stat is shown in the WinCC via a faceplate. The signal can then be

simulated.

Object group: BRT_DIN

BRT_DMOF Monitoring Function

This template must be set immediately with the BRT_DIN template. The block,

however, has an additional alarm function. A TRUE signal on the input I generates a

TRUE signal on the output Q and generates simultaneously an alarm. The block has

an output Q_ACK, which turns TRUE, when the alarm is acknowledged by WinCC.

Object group: BRT_DMOF

BRT_DMON Monitoring Function

This template is to be set simultaneously with the BRT_DMOF template. However, this

block does not have an Q_ACK output.

Object group: BRT_DMON

BRT_M Motor With Feedback On

This template contains a motor. A standard PCS 7 MOTOR is here integrated

expanded by specific functions like operating hours, runtime switch, expanded

cascading and cascaded operation lock.

Object group: BRT_M

BRT_MEAS Analog measurement

This template administers an analog measurement.

Object group: MEAS_MON

BRT_MOF Monitoring Function

This template contains a BRT_MOF block. This block has a alarm function and via this

signals can have a switch on and off delay. Additionally, the block provides a WinCC

confirmation.

Object group: ?

BRT_MSC Motor With Feedback On

This template expands the PCS 7 Standard MOTOR by simulation values,

maintenance expansions, and parameter.

Object group: BRT_MSC

BRT_PID PID Controller

This template provides a PID controller

Control Modules BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 109

Object group: CTRL_PID

BRT_PUPA Interval Block

This template provides a block for synchronizing of up to 10 Control Modules.

Object group: BRT_PUPA

BRT_V_2Q_FBCL Valve With Feedback Closed and 2 Outputs

This template contains a Standard PCS 7 valve with expansion for interlock, delayed

starting and stopping and BATCH Handling. The valve has 2 output signals still stand

and still stand inverted.

Object group: BRT_V

BRT_V_FBCL_OP Valve With Feedback Open and Closed

This template contains a Standard PCS 7 valve with Open-Close feedback and

expansions for interlock, delayed starting and stopping and BATCH Handling.

Object group: BRT_V

BRT_V_FBCL Valve With Feedback Closed

This template contains a Standard PCS 7 valve with Close feedback and expansion for

interlock, delayed starting and stopping and BATCH Handling.

Object group: BRT_V

BRT_V_FBOP Valve With Feedback Open

This template contains a Standard PCS 7 valve with Open feedback and expansion for

interlock, delayed starting and stopping and BATCH Handling.

Object group: BRT_V

BRT_V_NOFB Valve without feedback

This template contains a Standard PCS 7 Valve without Feedback and expansion for

interlock, delayed starting and stopping and BATCH Handling.

Object group: BRT_V

BRT_VDS_FBCL_OP Double Seat Valve With Feedback Closed / Open

This template contains a Standard PCS 7 Valve with Open-Close Feedback and

expansion for interlock, delayed starting and stopping and BATCH Handling and

double seat positioning.

Object group: BRT_VDS

BRT_VDS_FBCL Double seat valve with feedback closed

This template contains a Standard PCS 7 Valve with Close Feedback and expansion

for interlock, delayed starting and stopping and BATCH Handling and double seat

positioning.

Object group: BRT_VDS

BRAUMATcompact Control Modules

Engineering Manual, 06/2010, A5E02608507B-02 Page 110

13.1.3 CM Info

Almost all templates contain one or more blocks, which have the input “CM_INFO“.

This is to be connected generally with the output „QCM_INFO“ of the block

„U_U_SYN“ of the respective unit.

User Archives BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 111

14 User Archives

14.1 Archives

The following image shows the archives filed in BRAUMAT compact.

Image 101: Archives in BRAUMAT compact

This image shows the archives for 3 units with one recipe type. Further archives

develop with projects with further units. For each unit the following archives are added:

+ ARCH_XX with XX of the unit number (EQM_ID in FB U_U_SYN resp. in text

configuration picture of the resp. unit). Thereby single-digit units are filed only

single-digit e.g. ARCH_4 for unit 4)

+ ARCH_1xx01 with xx of the unit number (EQM_ID in FB U_U_SYN resp. in text

configuration picture of the resp. unit).

+ ARCH_2xx with xx of the unit number (EQM_ID in FB U_U_SYN resp. in text

configuration picture of the resp. unit).

Description of the archives, see next chapter.

BRAUMATcompact User Archives

Engineering Manual, 06/2010, A5E02608507B-02 Page 112

14.2 Contents and Settings

ARCH_XX

with XX of the unit number (EQM_ID in FB U_U_SYN resp. in text configuration picture

of the resp. system). Thereby single digit units are only filed with a single digit e.g.

ARCH_4 for unit 4)

The batch data are stored in the archive ARCH_XX after finishing a batch. Thereby

also the batch information with recipe name, start and end time,… of the batch as well

as the data of each executed step with step start and end time, parameter values and

analog value respond are stored.

ARCH_1xx01

with xx of the unit number (EQM_ID in FB U_U_SYN resp. in text configuration picture

of the resp. system).

The parameter of the recipes Function Step are stored granular in the archive

ARCH_1xx01. These data are edited by the user via the parameter dialogue in the

engineering faceplate of the unit.

ARCH_2xx

wit xx of the unit number (EQM_ID in FB U_U_SYN resp. in text configuration picture

of the resp. system).

The attribution of a batch to year and calendar week is stored in the archive

ARCH_2xx.

ARCH_901

In the archive ARCH_901 a trend with 128 value pairs (time  value) can be entered

in each line. These data can then be used in a BRAUMAT compact application via the

block BRC_SPT.

Thereby the ID of the column REC_ID must correspond to the parameter TR_ID on the

block.

ARCH_951

In the archive ARCH_951 exactly one trend is stored. Thereby each line represents a

value pair time  value. This archive is used for the lauder curve and is included in

recipe import/export

BRC_REC01

Is currently not used. Is maintained of compatibility reasons.

BRC_RECTYPE

Is currently not used. Is maintained of compatibility reasons.

BRC_UNIT

In the archive BRC_UINT the unit number of the unit name and the corresponding

trend picture are attributed.

User Archives BRAUMAT compact

Engineering Manual, 06/2010, A5E02608507B-02 Page 113

All values are generated executable at the configuration. Thereby the units are filed as

Unit_xx (column UNIT_NAME) and the trend pictures as @BR_TREND_Unit_xx

(column PDL_NAME) with xx of the unit number. The contents of both columns can be

adjusted manually.

BRC_UNIT_PARAMETER

In the archive BRC_UNIT_PARAMETER the parameter types of each unit are stored.

The data are entered by the user in the parameter dialogue in the engineering

faceplate via the button ”Parameter”.

PHCON_CS

The step sequence configuration is stored in the archive PHCON_CS. These data are

entered by the user in the engineering faceplate in the left PHCON Control.

PHCON_FCT

The step configuration for each step and unit is stored in the archive PHCON_FCT.

These data are entered by the user in the engineering faceplate in the right PHCON

Control.

PHCON_FCT_NAME

Is currently not used. Is maintained of compatibility reasons.

PHCON_LOGIC

The logic configuration is stored in the archive PHCON_LOGIC. These data are

entered by the user in the engineering faceplate in the Logic Control via the logic

mechanism (see also chapter 5.4.1.6 Adjust Configuration Picture).

BRC_REDUNDANCY

This is an auxiliary user archive and serves for the transfer of texts between two

redundant servers. Text data (e.g. recipe name, recipe type name) are transferred from

the OS Servers, on which the data was modified, to the redundant partner by the user