BRAUMAT Readme V7.1 (online)ucc.colorado.edu/siemens/BM-readme_en-US.pdf · SIMATIC BRAUMAT BRAUMAT Readme V7.1 (online) Readme Version: 2016-08-04 (Online) 09/2016 A5E38794248-AA

SIMATIC

BRAUMATBRAUMAT Readme V7.1 (online)

Readme

Version: 2016-08-04 (Online)

09/2016A5E38794248-AA

Security information 1

Overview 2

Installation instructions 3

Notes on Use 4

Upgrade of plants < V7.0 5

Virtualization 6

Siemens Controls

https://industrialautomation.co/product-category/siemens/page/10797/

Legal informationWarning notice system

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 only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger.

DANGERindicates that death or severe personal injury will result if proper precautions are not taken.

WARNINGindicates that death or severe personal injury may result if proper precautions are not taken.

CAUTIONindicates that minor personal injury can result if proper precautions are not taken.

NOTICEindicates that property damage can result if proper precautions are not taken.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 PersonnelThe product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems.

Proper use of Siemens productsNote the following:

WARNINGSiemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed.

TrademarksAll names identified by ® are registered trademarks of 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.

Disclaimer of LiabilityWe have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.

Siemens AGDivision Process Industries and DrivesPostfach 48 4890026 NÜRNBERGGERMANY

A5E38794248-AAⓅ 09/2016 Subject to change

Copyright © Siemens AG 2016.All rights reserved

Table of contents

1 Security information......................................................................................................................................5

2 Overview.......................................................................................................................................................7

3 Installation instructions.................................................................................................................................9

3.1 Delivery format.........................................................................................................................93.1.1 Delivery package......................................................................................................................93.1.2 BRAUMAT licenses and quantity structures............................................................................9

3.2 Hardware requirements..........................................................................................................123.2.1 PC hardware..........................................................................................................................123.2.1.1 Recommended PC hardware configuration...........................................................................123.2.1.2 Network..................................................................................................................................133.2.2 AS hardware..........................................................................................................................143.2.2.1 HW versions...........................................................................................................................14

3.3 Software requirements/installation.........................................................................................193.3.1 Software installation...............................................................................................................193.3.1.1 Requirements.........................................................................................................................193.3.1.2 Notes on installing the software.............................................................................................233.3.2 Shutting down Windows, standby mode / hibernation...........................................................253.3.3 Use of virus scanners.............................................................................................................253.3.4 Using Microsoft Office............................................................................................................26

4 Notes on Use..............................................................................................................................................27

4.1 What's new as of V7.1?..........................................................................................................274.1.1 New "Batch management" application...................................................................................274.1.2 HMI improvements.................................................................................................................284.1.3 Engineering............................................................................................................................294.1.4 Configuration and administration...........................................................................................304.1.5 BRAUMAT Lean on IPC427D Microbox RTX........................................................................324.1.6 S7-AS blocks..........................................................................................................................36

4.2 Phased out functions as of V7.1............................................................................................414.2.1 Obsolete functions.................................................................................................................41

4.3 What's new as of V7.0.1?.......................................................................................................424.3.1 S7-AS blocks..........................................................................................................................424.3.2 "MES API" option...................................................................................................................444.3.3 "BRAUMAT SQL Adapter" option..........................................................................................454.3.4 Miscellaneous........................................................................................................................48

4.4 What's new as of V7.0?..........................................................................................................504.4.1 Product presentation and Windows Standards......................................................................504.4.2 Expanded quantity framework................................................................................................524.4.3 HMI improvements.................................................................................................................534.4.4 Engineering............................................................................................................................544.4.5 Batch trending........................................................................................................................564.4.6 Cellar management................................................................................................................57

BRAUMAT Readme V7.1 (online)Readme, 09/2016, A5E38794248-AA 3

Siemens Controls


4.4.7 Profinet IO..............................................................................................................................59

4.5 Phase-outs as of V7.0............................................................................................................624.5.1 Obsolete functions.................................................................................................................62

4.6 BRAUMAT SQL adapter option.............................................................................................634.6.1 Notes on Use.........................................................................................................................634.6.2 Upgrading earlier project solutions.........................................................................................64

5 Upgrade of plants < V7.0............................................................................................................................67

5.1 Upgrades with new functions in use.......................................................................................67

5.2 Upgrades with no new functions in use..................................................................................68

5.3 IOS migration.........................................................................................................................69

6 Virtualization...............................................................................................................................................73

6.1 General..................................................................................................................................73

6.2 Hardware and software requirements....................................................................................75

6.3 Licensing................................................................................................................................77

6.4 Project-specific virtualization..................................................................................................78

Table of contents

BRAUMAT Readme V7.1 (online)4 Readme, 09/2016, A5E38794248-AA

Security information 1Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines and networks.

In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial security concept. Siemens’ products and solutions only form one element of such a concept.

Customer is responsible to prevent unauthorized access to its plants, systems, machines and networks. Systems, machines and components should only be connected to the enterprise network or the internet if and to the extent necessary and with appropriate security measures (e.g. use of firewalls and network segmentation) in place.

Additionally, Siemens’ guidance on appropriate security measures should be taken into account. For more information about industrial security, please visit:http://www.siemens.com/industrialsecurity

Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer’s exposure to cyber threats.

To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under:http://www.siemens.com/industrialsecurity


Siemens Controls


Security information


Overview 2Note

Read these notes carefully; they contain information that will be important to you and additions regarding BRAUMAT.

The information given in this Readme file takes precedence over all the BRAUMAT manuals.

You have received the BRAUMAT software version V7.1.

BRAUMAT provides you with convenient solutions for automating intermittent batch processes in the brewery sector.

BRAUMAT is the proven process control system for breweries in the Siemens "Totally Integrated Automation" concept● Based on robust SIMATIC S7 and IPC hardware and software components complying with

industry standards

● Flexible and simple integration of field devices and drives on the basis of PROFIBUS and PROFINET

● Modular structured and scalable process control system

● Openness at all levels

● Modern, distributed client-server architecture

● Greater availability due to server redundancy

● Scalable from a small laboratory system to networks of plants

● Efficient, plant-wide engineering

● Simple and quick system expansion and optimization in runtime

We wish you every success and hope you enjoy working with BRAUMAT

Your BRAUMAT Team


Siemens Controls


Overview


Installation instructions 33.1 Delivery format

3.1.1 Delivery packageWhen you order one of the products listed in the following section, you will also receive one of the following individual components:

● Certificate of License CoL

● BRAUMAT V7.1 DVD - depending on order number

● BRAUMAT V7.1 license key ALM USB memory stick - depending on order numberThe license keys required to operate the software for the supplied product are located on the USB memory stick.To simplify your license management, you can also save the license keys for other SIMATIC products on this memory stick.

3.1.2 BRAUMAT licenses and quantity structuresThe following table describes the available BRAUMAT products along with their functional properties:

Product Version Article num‐ber

Basic license type / License typeScope of deliv‐ery

Activated function / application

BRAUMAT IOS Server V7.1 6DL5210-1BX17-0YA0

SingleDVD, CoL, ALM stick

PCU server, recipe server, trend server, order system serverFor redundancy this license is required on both IOS server PCs.Operation for all applications with engineering appli‐cations

BRAUMAT Upgrade Package IOS Server

V7.0 → V7.1

6DL5210-1BX17-0YE0

BRAUMAT Upgrade Package IOS Server

V6.0 → V7.0

6DL5210-1BX07-0YE0

BRAUMAT Client V7.1 6DL5210-1CX17-0YB5

FloatingCoL, ALM-Stick

PCU server (client), recipe client, trend client, order system client, and RCS clientOperation for all applications with engineering appli‐cationsThere must be an RCS server when operating RCS client

BRAUMAT Upgrade Package IOS Client

V7.0 → V7.1

6DL5210-1CX17-0YE5

BRAUMAT Upgrade Package IOS Client

V6.0 → V7.0

6DL5210-1CX07-0YE5


Siemens Controls





BRAUMAT engineering V7.1 6DL5210-0AX17-0YA5

FloatingDVD, CoL, ALM stick

Parameter assignment/text parameter assignment, image design, measured value editor, curve entry, ZL synchronization, Excel import/export

BRAUMAT Upgrade Package Engineering

V7.0 → V7.1

6DL5210-0AX17-0YE5

BRAUMAT Upgrade Package Engineering

V6.0 → V7.0

6DL5210-1AX07-0YE5

BRAUMAT RCS Server V7.1 6DL5210-1DX17-2YB0

SingleCoL, ALM-Stick

RCS serverFor redundancy this license is required on both IOS server PCs.

BRAUMAT Upgrade Package RCS Server

V7.0 → V7.1

6DL5210-1DX17-2YE0

BRAUMAT Upgrade Package RCS Server

V6.0 → V7.0

6DL5210-1DX07-2YE0

BRAUMAT PCU V7.1 6DL5210-1EX17-0YB0

Single / Count relevantCoL, ALM-Stick

S7 connection for 1 PCUNote: ● For the number <n> PCUs are <n> licenses are

required per IOS server, which means 2 x <n> licenses for a redundant server pair.

● If more than <n> PCUs are configured in the plant configuration, the connection setup is prevented.

BRAUMAT Upgrade Package PCU

V7.0 → V7.1

6DL5210-1EX17-0YE0

BRAUMAT Upgrade Package PCU

V6.0 → V7.0

6DL5210-1EX07-0YE0

BRAUMAT SQL Adapt‐er IOS

V7.1 6DL5210-1FX17-2YB0


IOS SQL Adapter ApplicationThis license is required on each IOS server in case of a redundant server pair.

BRAUMAT Upgrade Package SQL Adapter IOS

V7.0 → V7.1

6DL5210-1FX17-2YE0

BRAUMAT Upgrade Package SQL Adapter IOS

V6.0 → V7.0

6DL5210-1FX07-2YE0

BRAUMAT SQL Adapt‐er Server

V7.1 6DL5210-1GX17-2YB0

SingleCoL

SQL DB Host Application

BRAUMAT Upgrade Package SQL Adapter Server

V7.0 → V7.1

6DL5210-1GX17-2YE0

Installation instructions3.1 Delivery format





BRAUMAT Lean (IOS, PCU, ES)

V7.1 6DL5210-1HX17-0YA0


1 x IOS, 1 x PCU and 1 x Engineering included in limited form. The following limitations apply if only BRAUMAT Lean is discovered and no BRAUMAT IOS server license:● 1 x S7 connection is permitted (PCU server

connection established), even without a PCU license

● Engineering is permitted on this IOS, including where no Engineering license is present

● No RCS server is started (RCS port = disabled), including where there is an RCS license present

● Any potential redundancy switching or server synchronization is prevented

● Any IOS server license which may be present at the same time is ignored

● IOS client access (with own/floating client licensing as relevant) is not restricted

● Engineering licenses (with own/floating client licensing as relevant) are not restricted

● New as of V7.1:The number of units is limited to 16. The parameter assignment of the "SEQUENCE" class is checked accordingly on the recipe server, and use is limited to instances 1..16.

BRAUMAT Upgrade Package Lean (IOS, PCU, ES)

V7.0 → V7.1

6DL5210-1HX17-0YE0

BRAUMAT Lean → IOS Server ConversionPack

V7.1 6DL5210-1HX17-0YD0


Converts a BRAUMAT Lean license into a BRAUMAT IOS Server license.

BRAUMAT MES API IOS

V7.1 6DL5210-1JX17-2YB0


API (Application Programming Interface) for MES ap‐plications; BRAUMAT IOS componentThis license is required on each IOS server in case of a redundant server pair.

BRAUMAT Upgrade Package MES API (IOS)

V7.0 → V7.1

6DL5210-1JX17-2YE0

BRAUMAT MES API Server

V7.1 6DL5210-1KX17-2YB0

SingleCoL

API (Application Programming Interface) for MES ap‐plications; SQL DB Host

BRAUMAT Upgrade Package MES API (Server)

V7.0 → V7.1

6DL5210-1KX17-2YE0

See alsoEngineering (Page 29)

Installation instructions3.1 Delivery format


Siemens Controls


3.2 Hardware requirements

3.2.1 PC hardware

3.2.1.1 Recommended PC hardware configuration

Recommended basic hardware configurationWe recommend the following configuration for PC components (the higher the quality of the equipment, the better):

Parameters IOS Server, IOS Lean, SQL DB Host with server operating system

IOS Client, IOS Lean

Basic PC (see catalog) SIMATIC IPC 847C / 847D / 647C / 647D / 547D / 547EProcessor min. INTEL Core 2 Duo; >=2.4GHz, INTEL Core 2 Quad Work memory (RAM) >= 8 GB (64-bit operating system) >=4 GB (64-bit operating system)Hard diskPartition size

>=200 GB HDD / SSDC:\ 100GB


Network adapter/com‐munications interfaces ● For terminal bus

communication● For plant bus

communication

● RJ45 on-board gigabit Ethernet ● CP1613 A2 / CP 1623 or BCE

network card

● RJ45 on-board gigabit Ethernet● CP1613 A2 / CP 1623 or BCE

network card

Opt. drive DVD +/-RW DVD-ROM

Parameter BRAUMAT Lean on IPC 427D Microbox RTX

Basic PC (see catalog) SIMATIC IPC427D with Windows Embedded Standard 7 SP1 and WinAC RTX 2010 SP2

Processor Intel Core i7-3517UEClock rate >=1.2 GHzWork memory (RAM) 4.0 GBHard disk partition size


Network adapter/com‐munications interfaces

● 2 x RJ45 on-board Gigabit Ethernet● On-board PROFIBUS CP 5611 / CP 5622● On-board PROFINET CP 1616

Opt. drive External via USBPurpose BRAUMAT Lean based on SIMATIC IPC427D released for AS and OS oper‐

ation.

Installation instructions3.2 Hardware requirements


NoteNote the following:● For IOS server and SQL DB host systems, only the Windows Server operating system

versions (64-bit) are supported.

Additional information PCS 7 catalog Internet link (https://www.automation.siemens.com/mcms/infocenter/content/en/Pages/order_form.aspx?HTTPS=REDIR&nodeKey=key_518272&infotype=1&linkit=null)

3.2.1.2 Network

Network configurationThe network for the BRAUMAT systems must be isolated by switches, routers or gateways so that no external interference can intrude on the BRAUMAT network.

Recommendations for this can be found in the document:

● BRAUMAT system documentation chapter 1 "Safety instructions"

See alsoSecurity concept PCS 7 & WinCC (Basic) (http://support.automation.siemens.com/WW/view/en/60119725)



Siemens Controls

https://www.automation.siemens.com/mcms/infocenter/content/en/Pages/order_form.aspx?HTTPS=REDIR&nodeKey=key_518272&infotype=1&linkit=null


http://support.automation.siemens.com/WW/view/en/60119725



3.2.2 AS hardware

3.2.2.1 HW versions

BRAUMAT AS CPU typesFor BRAUMAT AS, the CPU types of the S7-400 family (with the exception of the CPU-410) are generally permitted.



NotePlanning and selection of the CPU type● For performance reasons, use of the BRAUMAT PCU V7 is only recommended as of CPU

version 05.● However, the full configuration limit in connection with the PCU V7 cannot be used with all

CPU types.● We strongly recommend careful planning of the application (new plant or upgrade) and

dimensioning of the configuration limit in connection with the CPU selection.The following restrictions apply to the PCU V7 when using CPU types 414 in general as well as CPU 416/417 < version 07:● With CPU 414, only 2 MB RAM is available for data. However, the complete BRAUMAT

basic system already takes up 1750 KB in the delivery project. This means that the delivery project should be reduced to the necessary range of functions prior to configuring to create sufficient space for user and control recipe DBs.

● The use of up to 128 units and up to 9 BLR groups can overload the BRAUMAT 100 ms time slices TS01...TS10 in the case of very extensive configurations and result in faults in the recipe procedure.Solution: Reduce number of units in the affected PCU (Parameter assignment / "Sequences" class / Global data / Set "Count" <= 64) Disable BLR groups that are not used (Parameter assigment / "BLR1"..."BLR9" class / Global data / Set "DS_CountAct" = 0) Disable TANK and LINE instances that are not in useLimit the unit user programs, e.g. avoid comprehensive copying instructions

● SLB (seat lifting with double seat valve) and PULSE class must not be called in the 100 ms OB 35 "FB 1224"

Any restrictions are mainly dependent on the size of the TA-/ EOP- user programs as well as the use of the BLR-groups. The configuration engineer needs to assess based on real HW whether the use of the relevant CPU type is possible for the required BRAUMAT application and make sure that the available resources, CPU RAM and CPU performance, are adequate. Measuring the CPU cycle times in "STEP 7" as well as the BRAUMAT time slice loads ("CyclMeas" class) under "PLCSim" leads to incorrect results.

Upgrading existing plants

When upgrading from PCU V6 to PCU V7, a dedicated assessment and evaluation of the following points is necessary:● Upgrading with or without using new functionalities and configuration limits (now and in the

future)● Complexity of the previous configuration● Continued use of existing CPU types For questions regarding performance requirements and CPU selection, contact your Presales representative (AE SO B) or SIMATIC Customer Support.



Siemens Controls


Table 3-1 Performance data CPU version 05:

CPU type Work memory code / data

Max. number of DBs / FBs / FCs

CPU processing timesBit-Word-INT / REAL

CPU 414-3 PN/DP 2.0 MB / 2.0 MB 6000 / 3000 / 3000 45 ns / 135 nsCPU 416-2 2.8 MB / 2.8 MB 10000 / 5000 / 5000 30 ns / 90 nsCPU 416-3 5.6 MB / 5.6 MB 10000 / 5000 / 5000 30 ns / 90 nsCPU 416-3 PN/DP 8.0 MB / 8.0 MB 10000 / 5000 / 5000 30 ns / 90 nsCPU 417-4 15.0 MB / 15.0 MB 16000 / 8000 / 8000 18 ns / 54 ns

Table 3-2 Performance data CPU version 07:

CPU type Work memory code / data

Max. number of DBs / FBs / FCs

CPU processing timesBit-Word-INT / REAL

CPU 414-3 PN/DP 2.0 MB / 2.0 MB 6000 / 3000 / 3000 18.75 ns / 37.5 nsCPU 416-2 4.0 MB / 4.0 MB 10000 / 5000 / 5000 12.5 ns / 25 nsCPU 416-3 8.0 MB / 8.0 MB 10000 / 5000 / 5000 12.5 ns / 25 nsCPU 416-3 PN/DP 8.0 MB / 8.0 MB 10000 / 5000 / 5000 12.5 ns / 25 nsCPU 417-4 16.0 MB / 16.0 MB 16000 / 8000 / 8000 7.5 ns / 15 ns

A guide to memory requirements for typical BRAUMAT applications can be found in the following table:

(Information on earlier CPU versions can be found in earlier Readme files)

Table 3-3 BRAUMAT requirements for CPU version 05

Memory requirement for data

CPU 414-3 PN/DP

CPU 416-2 CPU 416-3 CPU 416-3 PN/DP

CPU 417-4

CPU RAM data 2000 KB 2800 KB 5600 KB 8000 KB 15000 KBBRAUMAT Basic System PCU V7static / without control rec‐ipe DBs

1750 KB 1750 KB 1750 KB 1750 KB 1750 KB

BRAUMAT RCS option Not possible 300 KB(30 routes)

700 KB(150 routes)

700 KB(150 routes)

1200 KB(300 routes)

Reserve for user and con‐trol recipe DBswithout RCS

250 KB 1050 KB 3850 KB 6250 KB 13250 KB

Reserve for user and con‐trol recipe DBsWith RCS option

Not possible 800 KB 3150 KB 5550 KB 12050 KB



Table 3-4 BRAUMAT requirements for CPU version 07

Memory requirement for data

CPU 414-3 PN/DP

CPU 416-2 CPU 416-3 CPU 416-3 PN/DP

CPU 417-4

CPU RAM data 2000 KB 4000 KB 8000 KB 8000 KB 16000 KBBRAUMAT Basic System PCU V7static / without control rec‐ipe DBs

1750 KB 1750 KB 1750 KB 1750 KB 1750 KB

BRAUMAT RCS option Not possible 300 KB(30 routes)

700 KB(150 routes)

700 KB(150 routes)

1200 KB(300 routes)

Reserve for user and con‐trol recipe DBswithout RCS

250 KB 2250 KB 6250 KB 6250 KB 14250 KB

Reserve for user and con‐trol recipe DBsWith RCS option

Not possible 1950 KB 5550 KB 5550 KB 13050 KB

CPU local data of the priority classesThe local data settings in "HW Config / CPU properties / Memory" should be made, depending on the CPU type, according to the table below:

Priority class CPU 414-xDefault / recommended

CPU 416-xDelivery project

CPU 417-4Default

Priority 1 758 / 1024 1024 1024Priority 2 256 / 256 1024 1024Priority 3 256 / 256 256 1024Priority 4 256 / 256 256 1024Priority 5 256 / 256 256 1024Priority 6 256 / 256 256 1024Priority 7 0 / 0 1024 1024Priority 8 0 / 0 1024 1024Priority 9 758 / 1024 1024 1024Priority 10 758 / 1024 1024 1024Priority 11 256 / 1024 1024 1024Priority 12 758 / 1024 1024 1024Priority 13 0 / 0 1024 1024Priority 14 0 / 0 1024 1024Priority 15 0 / 0 1024 1024Priority 16 256 / 256 1024 1024Priority 17 256 / 256 256 1024Priority 18 256 / 256 256 1024Priority 19 256 / 256 256 1024Priority 20 0 / 0 256 1024Priority 21 0 / 0 256 1024



Siemens Controls


Priority class CPU 414-xDefault / recommended

CPU 416-xDelivery project

CPU 417-4Default

Priority 22 0 / 0 256 1024Priority 23 0 / 0 256 1024Priority 24 256 / 256 1024 1024Priority 25 256 / 256 1024 1024Priority 26 758 / 1024 1024 1024Priority 27 758 / 1024 1024 1024Priority 28 256 / 1024 1024 1024Priority 29 256 / 256 256 1024Occupies xxx bytes 8132 / 11264 20480 29696of max. bytes 8192 / 16384 *) 22000 32768

*) Maximum value must be adjusted prior to changing the priority classes

Adjust CPU cycle monitoring time (HW Config / CPU properties / cycle clock memory)The OB1 cycle monitoring time in "HW Config / CPU properties / Cycle / Clock memory" should be set to 6000 ms for all CPU types.

Additional informationPCS 7 catalog Internet link (https://www.automation.siemens.com/mcms/infocenter/content/en/Pages/order_form.aspx?HTTPS=REDIR&nodeKey=key_518272&infotype=1&linkit=null)





3.3 Software requirements/installation

3.3.1 Software installation

3.3.1.1 Requirements

Released operating systemsThe following operating systems are supported in BRAUMAT V7.1 :

● Windows Embedded Standard 7 SP1 (32Bit)

● Windows 7 Ultimate/Enterprise SP1 (64Bit)

● Windows 10 Enterprise 2015 LTSB (64Bit)

● Windows Server 2008 R2 SP1 Standard Edition (64 Bit)

● Windows Server 2012 R2 Standard Edition (64 Bit)

NoteUse of Windows 10 Enterprise 2015 LTSB 64-bit1. Use of a redundant, high-availability terminal bus (based on SOFTNET-IE RNA or INTEL

Teaming) is not possible. Using such a terminal bus requires an operating system based on Windows 7.

2. When you are using two network cards, one of which was configured with and one without default gateway address, the following problem can occur:– The Ethernet card without default gateway address can stop attempting to establish a

connection to a communication partner over the IP protocol (when the communication partner cannot be reached temporarily) after multiple attempts to do so.

– The communication partner cannot be reached in this case until the ARP cache is reset. To correct this, the cumulative update for Windows 10 (KB3156387) must be installed.– Internet link (https://support.microsoft.com/en-US/kb/3156387)

Released processor architecturesOnly the x64 platform is used for processor architectures which support 64-bit memory addressing.Systems with Intel Itanium CPU architecture (IA64) are not supported.

Installation instructions3.3 Software requirements/installation


Siemens Controls

https://support.microsoft.com/en-US/kb/3156387


Not all configurations are suitable for every operating system. The following table shows the relationship of the permissible BRAUMAT configurations to the operating systems.

BRAUMAT PC station Windows Embedded Standard 7 32bit SP1

Windows 7 Ultimate / Enterprise64bit SP1

Windows 10Enterprise 2015 LTSB

64bit 1) 2)

Windows Server

2008 R2 Standard

64bit SP1

Windows Server

2012 R2 Standard

64bit 2)

IOS-Lean X X XIOS-Lean Single Station AS & OS(IPC 427D / WinAC RTX 2010 SP2)

X

IOS-Server X XIOS-Client X X X XSQL-DB Host X X

1) Redundant terminal bus not possible over Intel teaming adapter2) SIMATIC STEP 7 V5.5 SP4 not possible

Released Simatic SW versionsNote:

The Simatic software stated here is not supplied with the BRAUMAT system and must be provided and installed by the customer.

BRAUMAT V7.0 has been tested with the following versions:

● SIMATIC STEP 7 V5.5 SP4 Required as an option if the Simatic S7 programming is to be implemented on an IOS station (→ not possible in combination with Windows 10!)

● SIMATIC NET IE-Softnet S7 V13 SP2Only required on IOS servers or IOS lean / single station for connection of the process bus to the IOS ↔ AS communicationIf the SIMATIC STEP 7 V5.5 package is already installed on this IOS then SIMATIC NET IE-Softnet S7 is not required.

Microsoft SQL Server 2012 SP1 (64-bit) / Microsoft SQL Server 2014 (64-bit)Note:

The Microsoft SQL Server software is not part of the "BRAUMAT SQL Adapter Server" or "BRAUMAT MES API" option package and must be provided and installed by the customer.

● The Microsoft SQL Server must be installed before one of these option packages is installed. The "Standard" and "Enterprise" editions are tested and recommended.

● The computer name must be set before SQL Server is installed.

● The computer name should not be changed afterwards.(if this is absolutely necessary then special knowledge of SQL is required for this)



Microsoft .NET 4.5.2The "BRAUMAT SQL Adapter Server" or "BRAUMAT MES API" option package is based on the operating system functions of Microsoft ".NET 4.5.2". If this version of .NET is not available on the DB Host PC then it is also automatically installed as part of the set-up program.

Notes on installation of the Windows operating systemIf the operating system for BRAUMAT has not been installed on the PC station yet, reinstall the PC. This requires the operating system to be changed. The use of tools such as Windows Easy Transfer to transfer data and settings between different operating systems or to perform a direct upgrade from Windows Vista to Windows 7 has not been approved.

The following Windows features are not released for use with BRAUMAT:

● XP mode (only available with Windows 7)

● HomeGroup (only available with Windows 7 and Windows 10)

● Parental Control (only available with Windows 7 and Windows 10)

● Windows Defender

● Bit Locker

● Fast user switching The use of this feature can be disabled by the administrator via a group policy. You can find additional information regarding the procedure on the BRAUMAT CD in the folder _Manuals\English "bm70manual_b.pdf in section 3.1.1.6 "How to disable user switching"

Windows Software Update Service (WSUS)The WSUS cannot install software versions that are not described in this document as a minimum system requirements. This includes service packs for Microsoft operating systems, SQL Server, Office or new versions of Internet Explorer.

Operating system languagesWe recommend the following Windows MUI operating systems (Multilingual User Interface) with the following languages and corresponding regional settings:

● German

● English

● Spanish

● Chinese (PRC)

When you use BRAUMAT you will have to set the required language and region at every point in the Windows language settings. This affects all the settings available under "Regional and Language Options".



Siemens Controls


If you use BRAUMAT in Chinese, make the following settings in the Windows regional and language options:

● For the "Language version of the non-Unicode programs" select "Chinese (PRC)"

● For the "Language used in menus and dialogs", select "English" if you have set the BRAUMAT language to English.

● For the "Language used in menus and dialogs", select "English" or "Chinese (PRC)" if you have set the BRAUMAT language to Chinese.

● For the "Standards and formats", select "Chinese (PRC)".

You need to make these settings before installing the BRAUMAT software.

Rules for computer namesThe selection of the computer name is critical for the entire project configuration:

● Invalid characters: . , ; : ! ? " ' ^ ´ ` ~ - + = / \ ¦ @ * # $ % & § ° ( ) [ ] { } < > space character, underscore ("_")

● Max. 15 characters

● The first character must be a letter.

It is always advisable that only alphanumeric characters are used for the computer name. You should choose a name consisting of uppercase Latin letters (A-Z) and digits (0-9) only, starting with a letter and containing a maximum of 15 characters.

Security settingsYou can find information about the security settings on the BRAUMAT CD in the folder _Manuals\English "bm70manual_b.pdf" in section 3.1.1.4 "Security settings for the PC configuration".

Trouble-free operation of the BRAUMAT software requires specific settings to be made in the registry and in the exception list of the Windows firewall.

Before the installation begins, the "Setup - System Settings" dialog appears. There, the system settings to be changed are listed. To continue the setup, you need to agree to the change to these system settings.

Note

Please note the following:● The settings in the exception list of the Windows firewall are applied to the area of the local

network (subnet). If your PC stations are located in different networks (subnets), you need to change this area.

● If you need to make individual changes to any of the firewall settings, they should be adapted afterwards.

● The settings in the exception list of the Windows firewall are made when the Windows firewall is disabled.



Additional informationSIMATIC Process Control System PCS 7 Security Concept PCS 7 & WinCC (Basic)This document is available for download in the Industry Online Support under Entry ID: 60119725.

● Download Link Manual (http://support.automation.siemens.com/WW/view/en/60119725)

Hyper-Threading TechnologyHyper-Threading has been approved for BRAUMAT.

Setting the permissions for restarting the systemWhen using Windows Server operating systems, users without administrator rights must be provided authorization for "System Shutdown".

Without these rights, the system cannot be restarted.

As an administrator, you can set the permission for other user groups using a group policy as follows:

1. In the Windows Start menu, open the "Run" dialog box and enter gpedit.msc.

2. In the "Group Policy Object Editor" dialog box, select the folder "Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment."

3. Add the required user groups for the "System Shutdown" object.

3.3.1.2 Notes on installing the software

Prior to installationThe following points must be observed prior to the BRAUMAT V7.1 installation:

● If an earlier version of the BRAUMAT software is already installed then the following components must be uninstalled via "Programs and Features" in the Windows Control Panel:

– BRAUMAT/SISTAR Classic V6.0 SP... Upd ...

– BRAUMAT/SISTARClassic SQL V6.0 + SP2

– ILS RCS OFFLINE_SERVER V6.0. The dialog box "Remove shared file?" appears during the uninstall process - confirm this with "Yes to All" / confirm check query again

● The Windows Firewall must be active = Windows standard setting

● The Windows UAC ("User Account Control") must be active = Windows standard setting, third stage

● Important: Both the setup as well as subsequent operation should be executed in all cases as a Windows standard user and not as administrator. A user of this type must be created if not already present.



Siemens Controls



● The Admin User prompt is displayed automatically for all installation/configuration actions that require Admin rights.

● Ensure that no updates are being performed for antivirus software or the Windows Software Update Services (WSUS) during the BRAUMAT installation. You can ensure this by temporarily disabling the corresponding options in each program.

● A Windows UAC query should appear shortly after executing "Setup.exe". If it does not appear then there is something wrong with the call environment and the setup may not be able to execute all system registrations.

● The setup installs the required sub-components (Microsoft VC/.NET Runtime Libraries as well as Siemens Automation License Manager ALM).

● However, the process bus connection (via STEP 7 or SIMATIC NET Softnet IE) must be installed separately.

● Earlier BRAUMAT SoftCP drivers are no longer supported and should be uninstalled in Windows LAN-Connections / Properties.

● Documentation

– The current manual is on the installation data carrier in the folder "<lw>:\_Manuals\English\bm70manual_b.pdf" (for reference prior to installation).

– For further information on the Windows installation see manual section 3.1.1.

– For further information on the BRAUMAT installation see manual section 3.1.2.

– See manual section 3.1.3. for advice on system/project separation and on incorporating projects from previous versions and project switching.

Installation via network When performing a network installation of BRAUMAT on computers with an operating system based on Windows 7 and Windows Server 2008, ensure that access is guaranteed to the setup procedure, even if the computer reboots during the BRAUMAT setup. There the computer is not in a domain, you must enter the sign-in information of the user in order to access the network share for the server in the Windows Credential Manager.



After the installation

NoteThe following points must be observed before starting BRAUMAT:● Information on separating the system from the project and on taking over projects from

previous versions with the "Management / System settings" tool can be found in section 3.1.3 of the manual.→ Failure to observe this information may cause system components of the earlier BRAUMAT version to remain on the PC. These can interfere with the operation of the new version.

● The following entries are available in the Start menu following the installation:– Start→All Programs→Siemens Automation→SIMATIC→BRAUMAT→Application Center

(=previously "NewMenu.exe")– Start→All Programs→Siemens Automation→SIMATIC→BRAUMAT SQL-Adapter→

Service Tool (with corresponding selection in setup)● The BRAUMAT Desktop symbol is now called the "Application Center". Symbols from old

installations should be deleted.● BRAUMAT licensing takes place principally using ALM Licenses (see manual section

3.1.4.) ● If there are no ALM licenses available then DEMO mode is activated (with an indication).

This is limited to 4 hours.● The BRAUMAT system is now located in the Windows programs folder (standard = 'c:

\Program Files (x86)\Siemens\Braumat').

3.3.2 Shutting down Windows, standby mode / hibernationWhenever you shut down Windows on your BRAUMAT computers, use the command "Start > Shutdown Computer" and then select "Shutdown" or "Restart". Do not use "standby mode" and "idle state".

3.3.3 Use of virus scanners

Approved virus scannersThe following virus scanners have been tested for compatibility with BRAUMAT V7.0 and can be installed at a later time in case of an existing installation:

● Trend Micro OfficeScan V11.0 SP1 (Windows 10 clients are only supported as of this service pack)

You can find more detailed information on the administration of virus scanners in the "Industry Online Support" under the following entry:

● Internet link (https://support.industry.siemens.com/cs/ww/en/view/38625951)

Statements regarding "PCS 7 and WinCC" also apply to BRAUMAT!



Siemens Controls

https://support.industry.siemens.com/cs/ww/en/view/38625951


Here you need to pay special attention to the section "Configuration of virus scanners".

3.3.4 Using Microsoft OfficeThe following versions of Microsoft Office have been tested for compatibility with BRAUMAT V7.1.

● Microsoft Office Professional 2010 32-bit SP2 (Excel)

● Microsoft Office Professional 2016 32-bit (Excel)

Note:

NoteUsing MS Excel● There is a restriction applied to the BRAUMAT function "Excel Import/Export for external

parameter assignment" in that only the 32-bit version of Microsoft Office is supported. This can also be executed on 64-bit operating systems.

● Any access to BRAUMAT archive files in dBase format ( *.dbf) with MS Excel should be avoided at all costs.Reason:dBase files opened with MS Excel cannot be used simultaneously by BRAUMAT server processes (protocol handler) and there is a risk of data loss.

● MS Office should not be used on OS servers (recipe and RCS servers) on account of a considerable deterioration in performance.

● Running MS Office applications on OS client systems can also cause significant damage to performance.



Notes on Use 44.1 What's new as of V7.1?

4.1.1 New "Batch management" application

Core statementTo make the order creation and monitoring processes more efficient for the plant manager, the new "Batch Management" application has been integrated into the system. It has a completely new design, based on dockable windows such as the navigation area (orders), the working area (batches), and the parameter area.

● Navigation area:In the navigation area, you can access the following views of the connected AREA via two tabs:

– Order categories and current orders

– Order archive sorted by production year, order categories, and orders

● Working area:The batches filtered according to the selection in the navigation area are displayed in the working area. The working area has a table structure. Each batch occupies one row. Multiple worksheets can be opened. Multiple selection of batches for a subsequent menu or shortcut menu operation is possible.

● Batch parameters:The batch parameters of the selected batch are displayed and input here. This view can be fixed ("docked") or moved freely ("undocked").

The new application replaces the previous "batch list" ("BaliEdit" application), which will remain in the system for the time being and can continue to be used for special functions on an individual basis.

Information on migrating project-specific menu settingsIf the "BM_AppCenter.ini" file is found in the project directory when the "ApplicationCenter" is started, this is input and interpreted instead of the "<sys-path>\Braumat\texte.x\BM_AppCenter.ini" system file. To also activate the new "Batch management" application for this case, the line "App3=9;<...........>;baliedit.exe" must be replaced by the corresponding line from the "<sys-path>\Braumat\texte.x\BM_AppCenter.ini" system file.


Siemens Controls


4.1.2 HMI improvements

Core statementBRAUMAT V7.1 contains some enhancements that are particularly valuable to users.

Expanded display of the DFM type bit fieldThe actual value is now also displayed when using the DFM type "Bit field" (e.g. batch parameters, plant overview, UnitCtrl). This is done via background color, which means:

● green → actual value = setpoint

● pink → actual value ≠ setpoint

Enhancement "Text variable" visualization objectThe "Text variable" visualization object has been expanded in the "Biko" and "Lzsys" applications so that it can be interconnected to the following SW types:

● Text - Text file selectable (PCU-related or global); interconnection to any data object

● Material - Text file fixed "Material.txt" (global); interconnection preferably to DFM (recipe setpoint)

● Tank - Text file fixed "Tank.txt" (PCU-related); interconnection preferably to DFM (recipe setpoint)

● Tank location - Text file fixed "rcs_loc.txt" (global); interconnection preferably to DFM (recipe setpoint)

● Text (Bitfield) - Text file selectable (PCU-related or global); interconnection preferably to DFM (recipe setpoint)

Enhancements for improved display:

● Alignment (Left aligned/Centered/Right aligned) → default = left aligned

● Calculated size (active/inactive) → default = active (behavior prior to V7.1). In case of "inactive", the text field frame can be changed later.

Enhancement of the visualization objects "Integer/Real", "Hexadecimal", "Static Text"These visualization objects have been expanded by the following attributes for improved display:

● Calculated size (active/inactive)

● "Integer/Real" and "Hexadecimal": Alignment (Left aligned/Centered/Right aligned)

Reason:The width of the text field has so far been exclusively based on a standard character width according to the selected font and the number of characters. For specific text contents, the text field frame can now be adjusted by deactivating "Calculated size" to get a better result.

Notes on Use4.1 What's new as of V7.1?


The following default settings apply to all existing process pictures as well as to new object instances (and therefore the previous text frame size and alignment):

● "Calculated size = active"

● "Alignment = Left aligned" for text variable

● "Alignment = Right aligned" for Integer/Real and Hexadecimal

EditRec/Controlrec filter functionA partially qualified string is now possible as filter for the filter functions in the tree view and in the RP GOP overview.

4.1.3 Engineering

BasicsAn overview of the new functions and system properties in the configuration environment can be found below.

New system classes

SLB (max. 436 instances for each PCU V7 are possible)You use the "Seat Lifting Block (SLB)" function to control double seat valves (DSV).

Typical applications are:

● Separate activation of the main valve and the seat liftings

● Interlocks for main valve and seat liftings

● Configurable I/O assignment with adjustable end position monitoring

● External pulse/pause mode for synchronized purging of the double seat valves in groups

● Internal pulse/pause mode for individual purging

PULSE (max. 96 instances for each PCU V7 are possible)The "PULSE" function allows the generation of binary pulse sequences.

Typical applications are:

● Purging of various CIP valves / double seat valves

● Pulse for the injection of substances (injection on/off)

● Switching ON of outputs (one by one)

● Changing subsequent pulses depending on the selected mode (activate/deactivate specific outputs)



Siemens Controls


2nd RCS interface in the SEQENCER data recordTo enable dynamic switchover in the user program (TA FBs, EOPs) over the sequencer interface in the future, a second "SEQ.uRCS2" data structure has been introduced in the sequencer data record.

Excel configuration● The new classes and attributes of the V7.1 enhancements for SLB and PULSE have also

been added to the Excel configuration.

"ZL Synchronizer" application● During transfer of the BRAUMAT instance names to the STEP 7 symbol table (transfer

direction "←"), the option "Reduce to 24 characters" can be selected. The configuration engineer must ensure that the STEP 7 symbols (on the left) are unique.

BRAUMAT Lean (IOS, PCU, ES) – limited to max. 16 UNITs

Note

As of BRAUMAT V7.1, the number of active UNITs for this license is limited to a maximum of 16 (see section BRAUMAT licenses and quantity structures (Page 9)).

A reduction to a maximum of 16 PCU sequences is necessary to comply with the license terms. Verification takes place during the recipe server run-up. Ensure the following parameter assignment before starting BRAUMAT:● Application parameter assignment / "Sequences" class / "Online (PCU)" data source /

Global data / Set "Count" attribute ≤ 16

4.1.4 Configuration and administration

Central user administrationBasics:

● The user and function level definitions are only located on the redundant servers of an AREA and are therefore AREA-specific. They are synchronized by the system between the two IOS servers (master/standby).

● All IOS clients automatically use the server definitions, which means any local user definitions that deviate from these definitions are no longer supported.

● A transfer or synchronization by the system between different AREAs is not supported.

For multi-client access as well as for process pictures with access to different AREAs, the user rights are taken into account by the respective IOS server.



IOS-related user and/or function level definitions (analogous to 'IOS-related pictures') can be set up as follows:

1. Copy the existing definition file "<proj-path>\Admin\bm_user.dat" and/or "bm_levels.ini" manually to the servers into a separate IOS directory ("<proj-path>\IOS.xxx\Admin\").

2. Then edit this file from the respective IOS with the "User administration" application.

Migration from earlier versions takes place as follows:● The function levels are automatically imported from the "sys.ini" file when the server is

started for the first time.

● The user definitions can be imported through a separate note dialog when the user administration on a server is called for the first time.

● When deviating local user definitions were configured on IOS clients, these must be transferred manually to the server user administration (global or IOS-related).

Unique project identification with project IDThe project ID is used to check the file access paths between IOS stations of a project. The project ID is assigned in the "Adminstration/Configuration" application by pressing the "Generate new project ID" button in the "Factory settings" dialog. The new project ID must be distributed to the other IOS stations in a second step.

NoteThe project ID is mandatory as of V7.1.

It is mandatory to assign the unique identification by means of a project ID when upgrading. An empty project ID or one that does not match blocks the PCU server connections between the IOS stations.

PCU server security: Monitoring of the TCP/IP addresses of server and clientPreviously, the PCU server and the TrendManager accepted incoming WinSock connections from all network cards available on the IOS server. If a second LAN adapter with in-house network connection (or even Internet connection) exists in addition to the actual terminal bus adapter, which is prohibited according to the security recommendations, an "unwanted" client connection could be established over the second LAN adapter. This is now prevented through the following changes:

● The TCP/IP ports on the server are only opened for the local TCP/IP address configured in the configuration (SiteCfg).

● The TCP/IP address used is displayed in the status bar of the PCU server and TrendManager.

● In case of a deviating TCP/IP address in the configuration of the Windows LAN adapter, the PCU server outputs a corresponding note when it is started and the IP address has a yellow background in the status bar.

● The PCU server and the TrendManager only accept client TCP/IP addresses that are defined in the configuration.



Siemens Controls


NotePlease note the following for upgrading as well as for configuration changes:

The TCP/IP address configuration must be set up and distributed without errors and consistent with the LAN adapter configuration on all IOS stations during plant configuration.

4.1.5 BRAUMAT Lean on IPC427D Microbox RTX

What is BRAUMAT Lean on IPC 427D Microbox RTX?BRAUMAT Lean on IPC 427D Microbox RTX is a complete process control system comprising the following components:

● Hardware: SIMATIC IPC427D Microbox PC with pre-installed software bundle:Windows Embedded Standard 7, 32-bit operating system WinAC RTX 2010 SP2 automation system (internal AS) SIMATIC NET V12 SP2

● Software: BRAUMAT Lean (IOS, PCU, ES) - 1 x IOS, 1 x PCU and 1 x Engineering included in limited form.

● Optional: Distributed I/O

This configuration lets you implement a complete process control system with all necessary components and the BRAUMAT standard software at a reasonable price.

Fields of application of BRAUMAT Lean on IPC427D Microbox RTXBRAUMAT Lean on IPC427D Microbox RTX can be used in the following fields of application:

● Autonomous small plants in which multiple AREAs and server redundancy are not required

● Package units with integrated operator control and monitoring unit

● Testing and training plants

● Technical center

You can take advantage of all benefits offered by BRAUMAT through complete integration in BRAUMAT. This mainly applies to the following applications:

● Setup of a complete BRAUMAT "all-in-one" solution comprising of an IOS single station and a PCU V7

● Connection of an external SIMATIC STEP 7 engineering station

● Setup of BRAUMAT AS-AS cross connection over process bus



Connection to the process busThe BRAUMAT "all-in-one" solution described here requires both standard gigabit ports (RJ45) of the IPC427D Microbox PC for the connection between BRAUMAT IOS and BRAUMAT PCU. These must be connected either over a switch (when connecting additional process bus stations) or by means of a crossover patch cable.

A process bus connection as "double bus" is not possible with this solution.

Connection to a separate terminal busIf a separate terminal bus is to be used for connecting additional BRAUMAT IOS clients to a BRAUMAT Lean Microbox RTX, the Microbox PC must be equipped with an additional PCIe interface with Ethernet LAN adapter. Two additional PCIe interfaces with so-called "teaming capable" Intel LAN adapters are required for a redundant terminal bus.

Note:This must be taken into consideration when ordering the IPC427D Microbox PC because PCIe interface cards cannot be installed at a later time.

Installation and configuration - IPC427D Microbox PCThe IPC427D Microbox PC for BRAUMAT is usually delivered with the pre-installed system configuration "SIMATIC Embedded Bundles RTX". The special features of this system configuration are described in the supplied operating manual "embedded_bundles_ipc_4x7d_operating_manual_<language>.pdf". Only the "pre-configuration RTX" is valid for operation with BRAUMAT.

The necessary steps for manual installation are described in the supplied operating instructions "winac_rtx_2010_manual_<language>.pdf".

The recommended settings for operation with BRAUMAT are described below for both cases:

SIMATIC NET settings:● In the Windows Control Panel / "Set PG/PC Interface" , set the S7ONLINE access point to

"TCP/IP(Auto) -> Intel(R) 82574LM Gigabit Network Connection". This is the standard connection method for automation systems based on WinAC RTX.

Settings in the station configuration editor:● The WinLC RTX controller must be installed in slot 2. An Ethernet controller (e.g. "IF2 -

Intel(R) 82574L Gigabit Network Connection for WinLC RTX") must be configured in the submodules of this controller.

● The station name must correspond to the Windows computer name of the IPC427D.

● The Windows LAN Adapter (e.g. "Intel(R) 82574LM Gigabit Network Connection") must be installed as "IE General" in slot 3.

● Any pre-installed OPC server in slot 1 can remain here but it is not required for BRAUMAT.

Settings in the WinLC RTX Control PanelThe settings for operation of the soft PLC can be made in the menu CPU / Properties... The available settings or properties are also described in the operating instructions



Siemens Controls


"winac_rtx_2010_manual_<language>.pdf". Below, we will focus on the special features for operation with BRAUMAT:

General tab

● none

Data Storage tab

● Activate the option "Save to disk....".Reason: The retentive data cannot be saved to NVRAM because the BRAUMAT PCU system blocks already take up more than 128 KB. This means the retentive data can only be saved to a hard disk with BRAUMAT.

● For data security, a UPS is mandatory when saving the retentive data to the hard disk. All steps required for buffering in case of a power failure with SITOP DC UPS are described in the Simatic Online Support portal FAQ entry ID 52311477.

PLC memory tab

● none

Security tab

● none

Submodule tab

● The submodules are best configured in the station configuration editor (see above).

Installation and configuration - BRAUMATInstallation takes place with the setup program and is the same as for other IOS stations (see section Notes on installing the software (Page 23)).

The following components must be configured in the BRAUMAT Administration / Configuration:

● IOS with the settings:Name = Windows computer name = station name in the station configuration editorUse the TCP/IP address of the Windows network adapter (identical with station configuration editor IE General in slot 3)Route control = inactive, additional options depending on project requirements

● PCU with the settings:Route control = inactiveConnection / slot = 2Type of connection = TCP/IPUse the TCP/IP address of the Ethernet controller of the WinLC RTX submodule (e.g. "IF2 - Intel(R) 82574L Gigabit Network Connection for WinLC RTX").



Note

As of BRAUMAT V7.1, the number of active UNITs for this license is limited to a maximum of 16 (see section BRAUMAT licenses and quantity structures (Page 9)).

A reduction to a maximum of 16 PCU sequences is necessary to comply with the license terms. Verification takes place during the recipe server run-up. Ensure the following parameter assignment before starting BRAUMAT:● Application parameter assignment / "Sequences" class / "Online (PCU)" data source /

Global data / Set "Count" attribute ≤ 16

Configuration in the STEP 7 project● The IPC427D Microbox PC must be inserted as "SIMATIC PC station" component into the

project.

● Its station/computer name must be used as object name for the SIMATIC PC station.

● The slot and address information in HW Config must match the settings in the station configuration editor.

● A controller of the type "WinLC RTX" must be installed in slot 2 with the same submodules as in the station configuration editor (without OPC server).

● The Windows LAN adapter must be installed as CP Industrial Ethernet of the type "IE General" in slot 3.

● The TCP/IP addresses of the two LAN adapters (Windows and WinLC RTX) can be adjusted in the respective setting dialogs.

NoteSettings of the CPU properties of the "WinLC RTX" controller for operation with BRAUMAT

The option "Acknowledgement-triggered reporting of SFB 33-35" must not be selected for BRAUMAT. ● Open the properties dialog of WinLC RTX and select the tab [Diagnostics/Clock]. ● If necessary, disable the option [Acknowledgement-triggered reporting of SFB 33-35].

The "clock memories" must be activated for BRAUMAT. ● Open the properties dialog of WinLC RTX and select the tab [Cycle/Clock memory]. ● If necessary, select the option [Clock memory].

Connection configuration with NetProYou can configure the required subnets with NetPro as well as any required AS-AS cross connections for the WinLC RTX automation system in the usual way.



Siemens Controls


Setting the PG/PC interfaceFor the download function of STEP 7, HW Config and NetPro on the engineering PC, it is important that the target address on the IPC427D Microbox PC can also be reached.

● If S7ONLINE is set to TCP/IP, one of the two TCP/IP addresses of the Microbox PC can be selected during downloading.

● If S7ONLINE is set to ISO, only the MAC address of the Windows LAN adapter can be selected during downloading.

AS installation

Only the PCU version V7 has been tested and released for the "WinLC RTX" controller.Compile the AS software as described in the BRAUMAT system documentation for the SIMATIC S7-400 standard CPUs (see section "3.2 AS Installation").

NoteBlocks of the BRAUMAT V7 delivery project not supported by the "WinLC RTX" controller

The following blocks are not supported by the soft PLC controller:● OB 81 PS_FLT● OB 87 COMM_FLT● OB 101 RESTART

After copying the blocks from the source folder (e.g. Delivery project/"BM_SYS" folder) to the target folder of the "WinLC RTX" controller, these blocks should be deleted to prevent error messages during loading.

4.1.6 S7-AS blocks

Core statementAll changes made to blocks of the S7 AS since the last product version BRAUMAT V7.0.1 are listed below. The AS delivery project BM_AS_V07010000 also includes the corrections of the previous updates for V7.0.1.



Update information V7.1

BM_USR block folderPCU V7 DBs that may already include user configurations:

● DB 100 ("RC_CFG")Regeneration due to time stamp inconsistency, no interface change. For reasons of consistency, the block is to be copied to the program folder of the STEP 7 user project. Download to the AS is not required.

● DB 701 ("SYS")New attribute in the UDT 701: "xDisableSlbMsg" - Message lock for seat lifting block "SLB"Regeneration due to UDT update, no interface change. For reasons of consistency, the block is to be copied to the program folder of the STEP 7 user project. Download to the AS is not required.

● DB720 ("SCHEDULE")The assignment of the classes to the time slices has been optimized. Please apply any existing user configurations ("Disable" flags). The block must be loaded in AS Stop.Changed instance texts for PCU V7:The edited Scheduler data record texts should be applied to the user program. To do this, copy the following text files from the template project to the corresponding PCU V7 text directories of your project (…\pcu.nnn\texte.x\... x=0, 1, 2, 14 when engineering languages are used):<sys-path>\Braumat\!BM_Proj\pcu.001\texte\ScheduleV7.txt

● DB725 ("SEQ") → only when using the new functionality "2nd uRCS interface in the SEQ data record" in UDT 725Notice: update required in the project → see text section below

● DB726 ("ICM1"), DB 743 ("ICM2), DB 748 ("ICM3"), DB 749 ("ICM4")→ only when using the new status bit in UDT 726:

– au(x).xFbk0WithError - Feedback off/closed, error active

– au(x).xFbk1WithError - Feedback on/opened, error active

– au(x).xFbk0NoError - Feedback off/closed, no error

– au(x).xFbk1NoError - Feedback on/opened, no error

● DB2111 ("BLR1") to DB2119 ("BLR9") The default value "DS_CountAct" in DB2115 ("BLR5") was set to 128 because only a maximum of 128 instances are required for the TA continuous condition. The other BLR DBs are only included here for reasons of consistency, because all BLR DBs are based on the same UDT and would otherwise result in time stamp inconsistencies. The blocks should only be copied to the program folder of the STEP 7 user project. Download to the AS is not required.

● DB 2120 ("SLB" - New as of V7.1)

● DB 2121 ("PULSE" - New as of V7.1)



Siemens Controls


BM_SYS block folderPCU V7 FBs, FCs, UDTs which must be adapted or added:

Number Name Date changed AS stopDB 721 BmSchedulerIDB 2016-08-01 YesFB 706 BmSchedulerFB 2016-08-01 NoFB 725 BmSeqFB 2016-03-21 NoFB 726 BmIcmFB 2016-03-31 NoFB 727 BmMessFB 2016-08-03 NoFB 2120 BmSlbFB 2016-03-31 NoFB 2121 BmPulseFB 2016-06-22 NoFC 505 BmCallMain 2016-03-21 NoFC 696 BmManGroupSwitchFC 2016-07-04 NoFC 716 BmMsgToFifoFC 2016-03-21 NoFC 727 BmIcmUsrCallFC 2016-07-11 NoFC 750 BmGetRefValBoolFC 2016-06-21 NoFC 751 BmGetRefValByteFC 2016-08-01 NoFC 752 BmGetRefValWordFC 2016-08-01 NoFC 753 BmGetRefValIntFC 2016-08-01 NoFC 754 BmGetRefValDWordFC 2016-08-01 NoFC 755 BmGetRefValDintFC 2016-08-01 NoFC 756 BmGetRefValRealFC 2016-06-21 NoFC 762 BmSetRefValBoolFC 2016-08-01 NoFC 769 BmSetRefValGener‐

icFC2016-08-01 No

FC 772 BmGetSampleTimeFC 2016-03-21 NoFC 773 BmExecSlbFC 2016-07-11 NoFC 774 BmExecPulseFC 2016-07-11 NoUDT 701 SYS_UDT 2016-03-21 NoUDT 714 BmMainRecordUDT 2016-03-21 NoUDT 715 BmSeqInternUDT 2016-03-21 NoUDT 716 BmSeqCtrlUDT 2016-03-21 NoUDT 725 SEQ_UDT 2016-03-21 NoUDT 726 ICM_UDT 2016-03-31 NoUDT 2120 SLB_UDT 2016-03-31 NoUDT 2121 PULSE_UDT 2016-06-20 No

BM_RCS_USR block folderPCU V7 DBs that may already include user configurations:

● DB 91, 92, 93, 94, 95 ("RC_REMOTE1...5")

● DB 96 ("RC_LE_FIELD")

● DB 97 ("RC_PE_FIELD")



● DB 98 ("RC_SE_FIELD")

● DB 99 ("RC_CE_FIELD")

● DB 1099 ("RC_BM_CE")

BM_RCS_SYS block folderPCU V7 FBs, FCs, UDTs which must be adapted or added:

Number Name Date changed AS stopFB 801 RC_ROUTE 2016-03-21 NoFB 803 RC_ROUTE_RCE_ON 2016-03-21 NoFB 804 RC_ROUTE_RCE_OFF 2016-03-21 NoFB 806 RC_ROUTE_XC_SEN

D2016-03-21 No

FB 816 RC_ROUTE_XC_SND_ORDER

2016-03-21 No

FB 817 RC_ROUTE_XC_PE_ACTIV

2016-03-21 No

FB 818 RC_ROUTE_GET_EXT_PE

2016-03-21 No

FB 821 RC_IF_REMOTE_CE 2016-03-21 NoFB 830 RC_TR_ROUTE_UNIT 2016-03-21 NoFB 831 RC_IF_RE‐

MOTE_SEND2016-03-21 No

FB 832 RC_REMOTE_SEND 2016-03-21 NoFB 833 RC_IF_RE‐

MOTE_RECV2016-03-21 No

FB 834 RC_REMOTE_RECV 2016-03-21 NoFB 842 RC_IF_REMOTE_SE 2016-03-31 NoFB 843 RC_IF_REMOTE_PE 2016-03-21 NoFB 850 RC_TR_ROUTE2_UNI

T2016-03-21 No

FC 818 RC_IF_SE_BM_SIG 2016-03-21 NoFC 819 RC_IF_SE_BM_ICM 2016-03-21 NoFC 825 RC_ROUTE_LE_DGRA

M2016-03-21 No

FC 838 RC_UpdateIcmUnit 2016-03-21 NoUDT 98 RC_SE_FIELD_UDT 2016-03-21 NoUDT 99 RC_CE_FIELD_UDT 2016-03-21 No

Updating DB725 ("SEQ") in the projectWe recommend the following procedure for updating with an existing configuration in DB725:



Siemens Controls


Caution: A unit must not run in the respective PCU during the following steps.● Make sure that DB 725 is current on the IOS (offline DBs); if necessary, back it up with

block transfer PCU→IOS.

● The existing configuration of the DB 725 must be imported into the MS Excel configuration / "Sequences" sheet.

● Copy DB 725 from V7 AS delivery project to the STEP 7 project / block folder and download to AS.

● Back up new DB 725 with block transfer from PCU→IOS.

● Export to Excel configuration / "Sequences" sheet, i.e. transfer configuration to the new offline DB 725.

● Download new offline DB 725 including configuration with block transfer from IOS→PCU.

See alsoS7-AS blocks (Page 42)



4.2 Phased out functions as of V7.1

4.2.1 Obsolete functions

Discontinued functionsThe following functions or compatibilities of the previous versions are no longer supported as of BRAUMAT V7.1:

Material datagrams (PCU<V7)● The setting data records in the material management could be modified by the PCU with

datagram type 21.

● The datagrams were sent by calling the block FC770.FC770 ("MAT_CONTROL_FC") DB799 ("MAT_CONTROL_DB")

● The following functions were possible: Enable/disable process input Request weigher dataset (w/ or w/o enable) Back up/restore data block

Note

If included in the project, frame type 21 must be removed from the FIFO parameter assignment.

PCU server configuration "Datagram forwarding".● Activation took place with the following entry in the configuration file "...\PCU_SERV.INI":

[Protocol];List of computers that are to receive telegrams of type x;x=IOS1,IOS2

Notes on Use4.2 Phased out functions as of V7.1


Siemens Controls


4.3 What's new as of V7.0.1?

4.3.1 S7-AS blocksAll changes made to blocks of the S7 AS since the last product version BRAUMAT V7.0 are listed below. The blocks of the previous correction deliveries (V7.0 Update1, V7.0 Update1+Patch1) are also included in the complete AS delivery project V7.0 SP1. These must also be taken into consideration when upgrading the S7 AS, if not already done so.

Update information V7.0 Upd 1The following blocks from BM_USR were adapted with this update; they may already have contained user-defined configurations:

● DB720 ("SCHEDULE") The processing of the classes BLR6 to BLR9 has been added. The block must be loaded in AS Stop!

● DB725 ("SEQ") For reasons of consistency, the blocks are to be copied to the program folder of the Step 7 user project. They do not need to be loaded!

● DB2100 ("TANK") For reasons of consistency, the blocks are to be copied to the program folder of the Step 7 user project. They do not need to be loaded!

● DB2111 ("BLR1") to DB2115 ("BLR5") The technical classes associated with the DBs have not been changed. They are only included here for reasons of consistency, because all BLR DBs are based on the same UDT and would otherwise result in time stamp inconsistencies.

● DB2116 ("BLR6") to DB2119 ("BLR9") The technical classes associated with the DBs are processed cyclically in the Scheduler with SP 1. To keep the cycle load of the AS as low as possible, the initial value of the attribute "xPeriodicUpdate" has been changed from TRUE to FALSE in the DBs. For reasons of consistency, the blocks are to be copied to the program folder of the user project. They should only be downloaded to the AS, if no BLR configurations exist there yet. If BLR configuration already exist, the attribute "xPeriodicUpdate" should be reset for all instances in the parameter assignment in case of cycle time problems. An active periodic update is not "harmful" to the consistency of the user program, it only increases the cycle load.

● Changed instance texts for PCU V7: The Scheduler data record and ICM address identifiers upgraded in SP1 should be copied to the user program, if no configurations exist there yet. To do this, copy the following text files from the template project to the corresponding PCU-V7 text directories of your project (…\pcu.nnn\texte.x\... x=0, 1, 2, 14 when engineering languages are used):

– <sys-path>\Braumat\!BM_Proj\pcu.001\texte\ScheduleV7.txt

– <sys-path>\Braumat\!BM_Proj\pcu.001\texte\S7_sym.txt

– <sys-path>\Braumat\!BM_Proj\pcu.001\texte\S7_sym_DE.txt

– <sys-path>\Braumat\!BM_Proj\pcu.001\address.x\esg1.txt – esg4.txt (system language x= 0, 1, 2, 14)

Notes on Use4.3 What's new as of V7.0.1?


List of changed blocks PCU V7

Number Name Date changed AS StopDB 720, UDT 706 SCHEDULE 2014-09-08 YesDB 725, UDT 725 SEQ 2014-09-08 DB 2100, UDT 2100 TANK 2014-09-08 NoDB 2111 - DB 2119UDT 2111

BLR1 - BLR10 2014-09-08 No

FB 714 BmSeqRunEopFB 2014-11-12 NoFB 724 BmTimerFB 2014-11-19 NoFB 725 BmSeqFB 2014-09-08 NoFB 727 BmMessFB 2014-07-11 NoFB 731 BmAnauFB 2014-09-08 NoFB 737 BmDfm1FB 2014-08-04 NoFB 738 BmDfm5FB 2014-09-08 NoFB 2100 BmTankFB 2014-09-08 NoFC 716 BmMsgToFifoFC 2014-09-08 NoFC 769 BmSetRefValGenericFC 2014-09-08 No

The blocks are also included in the current delivery project

Update information V7.0 Upd 1 Patch 1The following blocks from the BM_SYS were updated with this patch:


Number Name Date changed AS StopFB 713 BmSeqTelegramFB 2015-01-19 NoFB 726 BmIcmFB 2015-01-19 NoFB 727 BmMessFB 2015-01-21 No

The blocks are also included in the current delivery project

Update information V7.0 SP1The following blocks from BM_SYS were adapted with this SP:

● DB 670, 671, 672 DB 690, 691, 692 ("BmFifo1 ...BmFifo6") The blocks must be loaded in AS Stop!

The following blocks from BM_USR which may already have contained user-defined configurations were adapted with this SP:

● DB2100 ("TANK") , UDT 2100For reasons of consistency, the blocks are to be copied to the program folder of the Step 7 user project. They do not need to be loaded. Only the default parameter value for „InventoryCyleTime“ of 0 -> 60 sec. was changed.



Siemens Controls



Number Name Date changed AS StopDB 713 BmSeqTele5 2015-04-15 NoDB 670, 671, 672DB 690, 691, 692UDT 670

BmFifo1 ... BmFifo3BmFifo4 ... BmFifo6

2015-03-16 Yes

DB 2100, UDT 2100 TANK 2015-05-13 NoFB 713 BmSeqTelegramFB 2015-04-15 NoFB 2100 BmTankFB 2015-05-13 NoFB 2102 BmBlrFB 2015-04-30 NoFC 700 BmUsrRouteDataInFC 2015-02-05 NoFC 771 (new) BmTriggerUsrStepLogFC 2015-04-20 No

Delivery project: <LW inst.data storage medium>:\86_BRAUMAT__V7.0\BM_AS_V07000100

List of changed blocks PCU < V7

Note

You only need to update the following blocks of PCU version V5.x when you are using the "BRAUMAT SQL Adapter" option package.

These blocks implement an expansion of the step log telegram required for this update.

Number Name Date changed AS StopDB 713 TA_FIFO_T5 2015-04-15 NoFB 713 TA_FIFO_FB 2015-04-15 No

Delivery project: <LW inst.data storage medium>:\86_BRAUMAT__V7.0\BM_AS_V06000200

4.3.2 "MES API" optionFor planning and releasing production batches by a higher-level MES/ERP system, we are providing the "BRAUMAT MES API" option package for the first time with BRAUMAT version V7.0.1. The order is made using two new MLFBs (see BRAUMAT licenses and quantity structures (Page 9)):

1. BRAUMAT MES API Server - API (Application Programming Interface) for MES applications on the SQL DB host

2. BRAUMAT MES API IOS - API (Application Programming Interface) for MES applications / BRAUMAT IOS component This license is required on each IOS server in case of a redundant server pair.



Installation:1. The installation takes place on the BRAUMAT SQL Server computer with the "BRAUMAT

MES API Package" program package. The associated resource "Siemens.Sistar.Api.dll" is installed in the "Windows Global Assembly Cache GAC" in the directory "c:\Windows\Microsoft.NET\assembly\Gac_msil\Siemens.Sistar.Api".

2. The IOS component of the MES API, which means the execution of the API calls in the BRAUMAT order system, is included in the BRAUMAT SQL adapter and is installed as a system component with the package.The associated ALM license "BRAUMAT MES API IOS" must be transferred to all IOS servers involved with the ALM tool.

Licensing:When the IOS application "SQL Adapter" starts up, the system checks to see if the ALM license "BRAUMAT MES API IOS" exists and displays this information in the window ("MES API: enabled"). If no valid ALM license is found, an error message is sent to the corresponding API call and an entry is generated in the BRAUMAT change log (Global Logging).

4.3.3 "BRAUMAT SQL Adapter" option

Extension of the engineering and runtime tablesDue to functional expansions in the SQL interface, changes and expansions were implemented in the engineering and runtime tables compared to the previous versions (V6.0.2, V7.0). In the process, we introduced new tables and expanded existing ones with new columns. Existing column names were not changed.

● When using the SQL adapter option for the first time in the project, the tables/columns of the "SistarData" database are created immediately according to this new schema. The sequence of the columns corresponds to the documentation of the "SQL DB Host / Table descriptions" manual.

● When you are upgrading, the expansions in "SistarData" are usually executed in the background and invisible to the user when the "SQL Archiver Service" is started for the first time after the installation. New columns are appended to already existing ones in this case and the sequence of columns deviates slightly from the documentation.

NoteProject-specific additions and expansions to the "SistarData" database

If expansions (e.g. views, trigger) were configured in the "SistarData" DB by the project, these need to be manually adapted to the new structure of the system tables during the upgrade.



Siemens Controls


Table changes in SQL DB "SistarData"The changes are listed below in abbreviated form. A more detailed description is available in the corresponding sections of the "SQL DB Host / Table descriptions" manual.

● sistar_eng_xxxxx (all engineering data) → update_timestamp

● sistar_eng_recipes → product_id, recproc_name

● sistar_rt_batches → recproc_no, product_id, product_name

● sistar_rt_batch_params → display_name, uom

● sistar_rt_steps → rop_id, user_prot_id, event_time, recipe_no, recproc_no, product_id, product_name

● sistar_rt_step_params → rop_id, user_prot_id, epar_no (DFM-number)

● sistar_rt_matmovs → recproc_no, rop_id, user_prot_id, event_time

● sistar_rt_changelog → value_old, value_new / stringlength 32 → 64

● sistar_rt_unit_history → recproc_no, recproc_name, rup_no, rup_name

New tables in SQL DB "SistarData"New functions of the "BRAUMAT SQL Adapter" option in abbreviated form (a detailed description is available in the corresponding sections of the "SQL DB Host / Table descriptions" manual).

● sistar_eng_materials → includes the materials configured in the recipe system

● sistar_eng_matgroups → includes the material groups configured in the recipe system

● sistar_eng_tank → includes the tank master data. Each tank instance has one line (1...128)

● sistar_rt_tank_history → includes the tank allocation data.

– All tank instances (1...128) are transferred with the current data during run-up of the PCU server.

– Additional cells are added in case of changes in the tank or quality status or changes in the level. Requirement: The update of the inventory telegrams is enabled in the parameter assignment of the TANK instances.



NoteConfiguration of the inventory telegrams in BRAUMAT engineering● The inventory telegrams are sent to the SQL DB host according to the configuration of the

update attributes in the BRAUMAT TANK instances of the participating PCUs and entered in the table "sistar_rt_tank_history" with INSERT. These attributes do, however, also determine the update rates in the TANK selection dialog of the BRAUMAT order system for parameter type "Tank" or "Tank location" (PCU V7 or higher).

● The user/project engineer has to keep an eye on a sensible and necessary number of update telegrams during the configuration, especially of the attributes "InventoryQuantityHyst", "FireInventoryOnChange" and "InventoryCycleTime".

● An incorrect configuration or one that has not been adjusted, can increase the data volume in the SQL table significantly and have a negative effect on the entire coupling performance.

New ROP ID in recipe procedures● The ROP ID is used as unique ID of an ROP within the recipe procedure in the sense of a

"technological step".

● In case you install an EOP multiple times in the recipe procedure, the ROP ID distinguishes them from one another.

● The ROP ID is generated automatically in the recipe editor and cannot be influenced by the user. It is displayed in the setpoint list.

● The ROP ID is also applied to the step log and saved when the batches are running.

Application case:● The ROP ID is also transferred to the step log archives of the SQL database when you use

the "BRAUMAT SQL Adapter" option.

● This means the step log data of individual ROPs can be clearly identified as technological steps.

● This way it is easier to extract so-called KOPs (key operating parameters) in the reports of the MES/ERP application.

NoteBehavior after update of existing plants● Missing or non-unique ROP IDs are detected when recipe procedures are opened. ● If the recipe procedure is not write-protected (status <> "Production release"), this status

is automatically corrected and signaled by a dialog box (RP in change status). The newly assigned ROP IDs become with effective with the first "save".

● There is not check and change with released RPs, because they are write-protected and cannot be changed.

● To use the ROP-ID in connection with the SQL adapter, all RPs should be opened once and set to the status <> "Production release", if not already done so. Missing/invalid ROP-IDs are detected in the process and changed with "Save".



Siemens Controls


User step logs● It may be desirable for longer-running technical operations to already record step logs

triggered by the user program during the EOP runtime in addition to the automatically recorded step log data records at the end of the EOP.

● These give you the option for a detailed analysis of the setpoints and actual values of the recipe in the step log tables of a connected SQL database.

● Additional step telegrams can be triggered at any time by calling the new FC 771 "BmTriggerUsrStepLogFC" in the EOP FCs.(see manual chapter "AS configuration with STEP 7 / Create equipment operations (EOP) as function / User step log")

4.3.4 Miscellaneous

Other innovations ...

Windows settings in the system setting tool:The following Windows options can be easily configured in the "System settings" (BM_Config) application. In previous versions, these options had to be configured directly in the Windows registry and policy settings.

● Lock BRAUMAT Application Center as shell / desktop

● Enable automatic logon

● Lock Task Manager

● Prevent fast user switching.

The documentation is available in the manual in the chapter "System installation and configuration / OS Installation / Starting the system / BRAUMAT/WINDOWS system settings"

BLREdit:● A zoom function was integrated in the logic view by means of buttons or Ctrl+mouse wheel.

● References to attributes of user objects are now always displayed as symbols (before partially absolute).

● A confirmation prompt appears when you download the changes to the AS. It can be enabled/disabled with the menu command "Options/Confirm download".

TANK / LINE ControlThe display options in the list view have been expanded as follows:

● In the layout dialog, the list of properties has been expanded by line, column, alignment and text width.

● This means the text fields can now have multiple columns.

Statusbyte Control● All system classes with USINT (byte) and ENUM parameters as well as user classes can

now be interconnected.



Archive display● Sorting and filter are now saved and are valid again with the next call.

● If the archive viewer is started from the PCU server, only the message list and the last message is displayed at the top. Sorting by date/time.

Step log display● Additional step telegrams can be triggered at any time by calling the new FC 771

"BmTriggerUsrStepLogFC" in the EOP FCs.(see manual chapter "AS configuration with STEP 7 / Create equipment operations (EOP) as function / User step log")

● These can be hidden or shown in the step log display.



Siemens Controls


4.4 What's new as of V7.0?

4.4.1 Product presentation and Windows Standards

Basic principlesBRAUMAT V7.0 offers the following new system functionalities:

Licensing with SIMATIC standard "Automation License Manager" (ALM)● The Simatic Automation License Manager is used for this BRAUMAT version.

● The ALM components (32-bit or 64-bit) are installed automatically through the setup in accordance with the operating system version available.

● The licenses required in accordance with the plant configuration are supplied with the BRAUMAT products in the form of USB license keys and must be transferred to the IOS stations following the BRAUMAT installation (see BRAUMAT licenses and quantity structures (Page 9)).

Please note:● No mixed licensing for V5.x/6.x (Prod32.dll) and V7.0 (ALM)

● Upgrade packages V6.0 → V7.0 contain the ALM licenses of the respective full product. In the case of upgrades, these licenses must be acquired again based on the current plant configuration (with reference to the old licenses).

New setup in accordance with SIMATIC Standard● The new setup has been adapted to the standard setup frame for SIMATIC products.

● The option of uninstalling the BRAUMAT-related product(s) is also linked to this.

● The setup takes into consideration the path specifications (program directory) of the currently supported Windows versions.

System/project path separation● The BRAUMAT system is installed in the standard "program" directory.

● All configuration, engineering and process data for a BRAUMAT project is stored in a separate project directory ("windcs" up to now).



● There may be multiple project directories present, with only one of these capable of being declared as a current project at all times.

● Setup installs the new "Management / System settings" tool for easy configuration. The allows the following basic settings to be made easily:

– Setting or switching of the project to be activated when BRAUMAT is next started.

– Setting or switching of the BRAUMAT network share for the active project "BM_PROJ"

– Setting of the Windows file/directory authorizations (NTFS) for the active project

– For upgrades: Checking and where necessary cleaning of the "windcs" directory for use with BRAUMAT as of version V7

User rights, Windows User Account Control (UAC)● BRAUMAT no longer requires administrator rights in order to run.

● The BRAUMAT standard functions are also released for a Windows user who is merely a member of the "Users"user group.

● An Administrator login is requested for the setup program as well as the system setting tool and the BRAUMAT "User Management".

● Windows User Account Control (UAC) is fully supported with the standard security settings.

● A BRAUMAT group is created in Windows by the setup which allows write access to the project directory.

● New Windows users have to be assigned to this BRAUMAT group (this may take place via "System settings").

"English S88" interface language● The separate language number 10 (English ISA-88) existing up to now ceases to apply.

The content of the system texts is adopted from language 1 (English).

● This makes English ISA-88 the standard content.

● For migrations it must be noted that all Text.10 directories cease to exist. Any potential user texts can be copied to "Text.1" with "System settings".

User texts / text length 32 characters● All identifiers of technological objects have been expanded to a maximum text length of 32

characters (for Chin. language 16 characters).

● The corresponding table and text definition files have been changed accordingly in the "<sys-path>\!BM_Proj\..."delivery project.

● With existing receipts as well as with other dbf tables produced by the system there is an automatic conversion to the new format upon saving.



Siemens Controls


● There is no conversion for existing long-term archives (messages, step protocols) from previous versions. New archives are automatically created with 32 characters. The applications involved in archiving are able to process both the old as well as the new format.

● All strings in user-definable dbf tables (e.g. free protocols) must be converted manually where needed.

Documentation● The current system documentation is located (for purposes of viewing before the

installation) on the installation data carrier in the following directories:

– DE = „...\_Manuals\Deutsch\..."

– EN = „...\_Manuals\English\...“

● The earlier individual manuals have been consolidated into one manual with a new outline structure.

4.4.2 Expanded quantity framework

BasicsThe configuration limits have been expanded for the technological classes of the PCU as of version V7 as well as for the OS variables.

However, the existing figures and functionalities still apply for existing PCU versions prior to V7.

AS configuration limitsFor PCU version V7, the number of instances of the following objects has been expanded:

● THREESTEP: 96 → 128

● EOP: 999 → 1999

● ICM 255 → 256

● MELD: 1024 → 2048

● AIN: 256 → 512

● SEQUENCE: 64 → 128

● Step setpoints: 20 → 24

OS configuration limits● The maximum number of standard variables per process image has been increased from

512 to 1200.

● The number of curve groups is set at 240 per AREA.



4.4.3 HMI improvements

BasicsThe following enhancements have been implemented for the BRAUMAT operating and monitoring components.

Image design● Undo/redo function

Undo/redo image amendments (10 stages)

● Image levels, presentation sequenceDisplay/hide/block image elements or groups in the Editor window (image design)

● Indirect connectionNew, integrated dbf editor dialog for the source definitions

● Positioning of the object infoCorrection of the runtime info fields (block, installation location, address) following delays in the Editor

● Search for installation location in the image designSearch function also fully/partially qualified via the process images (such as LzSys)

● EMF format (vector graphics) for image symbols"Zoomable" image symbols without loss of quality

Controls (OCX) enhancements● Modeless operation

The runtime dialogs are now "multi-instance enabled", i.e. multiple blocks can be opened at the same time

● Uniform symbol identifiers in runtime for interlock, simulation, manual, notice (new) for all control types

● Symbol identifiers can be set for each block instance in the properties dialog (default setting can be defined for each class in 'Controls.ini')

● Entity-OCX font can be set

● New controls for tank/pipe status block

● New OCX symbols (emf/vector graphics)

Plant overview (SeqCtrl)● New self-explanatory unit status symbols

● Display column for recipe category for the current batch for each unit



Siemens Controls


4.4.4 Engineering

Basic principlesAn overview of the new functions and system properties in the configuration environment can be found below.

New system classes

BLRBinary logic operations can be modeled in a stand-alone object that can be configured graphically and undergo operator control and monitoring. This type of BLR ("Binary Logic Result") object is suitable for use as:

● Interlock of an ICM

● Permanent condition of a plant unit

● Step-enabling condition of a step block (EOP-FC)

DFM4Simple configuration limit expansion of DFM1 functionality.

DFM5 to DFM8Expansion of DFM1 functionality with practically the same functions, but based on REAL data type.

Changes to system classes

General● All analog signal-processing blocks use the REAL data type.

● The "Reference" data type replaces QUEL.

AOUT● The process I/O is incorporated based on a reference. The "AOUT_PW" allocation class

previously responsible for this is omitted.

THREESTEP● Configuration limit increase to 128 instances

ICM ● "Configuration limit increase" to 256 instances

● The new group signal "Ready to start" is available in order to simplify AS programming.

● The I/O connection can be released from the standard mapping by using references for acknowledgments and control output.



MSG● Configuration limit increase to 2048 instances

AIN● Configuration limit increase to 512 instances

● The process I/O is incorporated based on a reference. The "AIN_PW" allocation class previously responsible for this is omitted.

● The measured value can be smoothed.

SEQUENCE● Configuration limit increase to 128 instances

● Permanent condition is freely configurable (reference)

TIMER ● The process connection can be released from the standard mapping by using references

for input and output signals.

"Parameterization" application

New data types● DT (S7 data type DATE_AND_TIME)

● ENUM (enumerations based on system or project text files)

● OREF (Object reference, comparable with the previous QUEL data type)

● GREF/PREF ("Get/Put-Reference": Data connection to any PCU memory areas)

Operation● Copying and pasting of values of the same data type or a related data type ("Copy & Paste")

● Character-by-character editing of existing values (ALT+F2)

● F3 now opens an instance list, and a change of data record is now made using NUM+/NUM-.

New recipe DFM types

Text (bit field)Individual bits of a double word with texts can be linked in the context of DFM usage (e.g. recipe editor, plant overview).

Excel configuration● The Excel add-in has been provided with a password level for read and write access.

● The new classes and attributes of the V7 enhancements have also been added to the Excel configuration.



Siemens Controls


"ZL Synchronizer" applicationThe process for selecting BRAUMAT object classes for synchronization with the Step 7 symbol table has been enhanced. The following system classes are now available:

● SEQS, DFM0-3, THREESTEP, ICM1-4, MVC, ALARM, AIN, MULT, PID, EOP (technical operation), sequences, TIMER1/2

System time synchronizationWhen required, this is handled in BRAUMAT as of version V7 using the system's own functions for time-of-day synchronization. These are handled via the communications relations defined in the plant configuration ("SiteCfG") and can also be activated there for the relevant station.

(see system documentation chapter 3.3.6 IOS settings)

4.4.5 Batch trending

Batch trendingThe new path system for the BRAUMAT base system has also been incorporated on the batch trending and or the Trend Manager (no longer any special setting for "Trendman.ini").

Measured value description lists● Multi-client function: The application has an area selection dialog.

● Changes are now automatically saved on both servers for an area in all cases.Upgrading: If there have been 2 different MWBL files (measdesc.dbf, digidesc.dbf) on both servers for an area up to now, then the user must decide which should be the 'Master' lists before working with "MeasEdit.exe" for the first time. These must then be manually synchronized once on both servers.

Trendman.ini● Configuration of the "Trendman.ini" configuration file is no longer generally required for the

purposes of recording batch trending.

● The available measured value trend servers are set out in SiteCfg → IOS settings → 'Trendmanager' release

● Recording trend curve data is now only possible on IOS servers. The possible client/server configurations are identical to all other BRAUMAT functions with this. There is now no separate description for these configurations for the trend recording as a result.

● Trendman.exe starts automatically → no configuration is required for ProSched.

● The path for the trend data is now at 'BM_ARCH' by default (as with MSG, STEP and GlobLog).This path can be amended in SiteCfg → IOS Settings → Remote Paths (should only be required in exceptional cases).

● The trend may be recorded redundantly. This means that the measured value is recorded on two servers, with both recordings running independently of each other.



Data storage / paths:● The measured value description lists and images remain in the project path as before, which

is defined via 'BM_PROJ'.

● The trend data is in the new trend path, which points to 'BM_ARCH' by default.

Kurven.exe● The application also now has an area selection dialog.

● New command row parameter: Area=x

● Image storage: The 'SynchonizeFiles' window no longer exists → Trend images are now in all cases saved on the server(s) (SynchonizeFiles=1).

● The dialog 'File → Edit → Analog measured values' now contains a filter function for selecting the measured values.

Upgrading existing plants

1st case: Trends have already been recorded on servers● Engineering: Enable function in SiteCfg for the corresponding servers

● Data storage: Copy existing data 'BM_ARCH' if necessary (only if 'BM_ARCH' differs from 'BM_PROJ').

2nd case: Trends have been recorded by the client● Engineering:

The function must be enabled in SiteCfg for the corresponding servers.The IOS number must be corrected accordingly in all trend images.

● Data storage: Copy existing data from the client to 'BM_ARCH' on the server where necessary.

4.4.6 Cellar management

Basic principlesA series of objects and functions are provided in the new version of the system which are able to simplify and standardize the engineering as well as operation and monitoring for some of the typical application cases in the cellar area.

Tank status block● This function block manages the tank and container statuses and provides runtime

monitoring with interfaces and alarms for process and quality status for this purpose, including an operating and monitoring interface.

● Based on the general approach the block can be used for a large variety of different container types, e.g. silos, buffer tanks, etc.



Siemens Controls


● The process status allows up to 255 (10 upon delivery) tank statuses to be managed and can be operated via OS faceplate and/or control inputs.

● The process status allows up to 255 (4 upon delivery) tank statuses to be managed and can be operated via OS faceplate and/or control inputs.

● There are 3 separate timers available for monitoring the remaining runtimes for material quality, tank cleaning, and tank sterility.

● The material is selected in the OS faceplate on the basis of the materials defined in the material configuration dialog.

● Up to 8 temperature sensors can be connected to the block and be activated/deactivated (via configured references or via user allocation). The display in the faceplate and the calculation of the average temperature value occur based on the activation information.

Line status block● This function block manages the pipeline statuses and provides runtime monitoring with

interfaces and alarms for the process status for this purpose, including an operating and monitoring interface.

● Based on the general approach the block can be used for a large variety of different line types.

● The process status allows up to 255 (10 upon delivery) line statuses to be managed and can be operated via OS faceplate and/or control inputs.

● There is a timer available for monitoring the remaining runtime for any desired process status.

● The material is selected in the OS faceplate on the basis of the materials defined in the material configuration dialog.

Material management● The recipe editor dialog ‘Configuration →Material management→Materials and groups' is

available for configuring the different materials. The materials to be transported and the group to which they belong are defined here.

● The new dialog ‘Configuration→Material management→Material order’ is available for defining the material order relations.possible material order relations:

– Material to material

– Material to group

– Group to material

– Group to group

Material compatibilityA matrix of the material sequence relationships can be used at the RCS level to check whether the source product is suitable for the target product.



In addition, a check of the material compatibility can also be made in the following scenarios:

● Order planningWhen a tank is being selected for a batch parameter, the tanks with unsuitable content or status can be filtered out using a new online dialog.

● For the batch sequence in the plant unit (sequential control)A new interface for the material checks on the sequencer block in the AS allows 2 material IDs to be checked for compatibility:

– 1. Predecessor material, e.g., current material of a tank block

– 2. Successor material, e.g., product of the batch

– 3. A control bit is set in the GOP-FC in order to stop the recipe and activate the material check in the recipe server

– 4. A data word via which the recipe server signals the result of the material check

In the GOP-FC the result must be used to decide whether the recipe is continued, or e.g. a control request is triggered.

4.4.7 Profinet IO

BasicsThe compatibility of SIMATIC NET ProfiNET hardware components including the associated ProfiNET communication as a process bus TCP/IP, I/O bus ProfiNET I/O and S7-S7 cross coupling TCP/IP with BRAUMAT has been tested and is released as of version V7.

Hardware componentsThe fundamental hardware requirement complies with the BRAUMAT hardware basis currently released (see section "Hardware requirements").

The following ProfiNET hardware components are supported:

ProfiNET automation system:

● SIMATIC S7-400/CPU416-3 PN

ProfiNET I/O:

● SIMATIC ET 200M/IM 153-4 PN



Siemens Controls


Supported configurationsThe following communication variants are supported in connection with the CPU SIMATIC S7-400/CPU416-3 PN/DP:

● Process bus for Industrial Ethernet ISO Communication between IOS server and CPU416-3 PN/DP with additional communication processor(s) – CP443-1 and Industrial Ethernet ISO protocol With this the process bus can be designed as a "single" process bus or as a "dual" process bus.

● Process bus Industrial Ethernet TCP/IPCommunication between IOS server and CPU416-3 PN/DP with the CPU internal ProfiNET interface and Industrial Ethernet TCP/IP protocol With this the process bus can be designed as a "single" process bus or as a "dual" process bus.

● I/O bus ProfiNET I/OI/O communication between CPU416-3 PN/DP and a distributed ET200M-PN with typical digital and analog I/O modules, whereby the I/O bus uses the CPU internal ProfiNET interface and the ProfiNET I/O protocol.

● S7-S7 cross coupling TCP/IPBRAUMAT S7-S7 cross coupling between CPU416-3 PN/DP and an additional CPU41x with typical cross-coupling jobs, whereby the process bus uses the CPU internal ProfiNET interface and Industrial Ethernet TCP/IP protocolThe S7-S7 cross coupling using TCP/IP protocol can be designed in combination with a process bus with Industrial Ethernet ISO (CP443-1) as well as with Industrial Ethernet TCP/IP protocol (CPU-PN).

NoteUnsupported ProfiNET functions

Additional features of the ProfiNET hardware such as "ProfiNET diagnostics functions" are not actively supported by BRAUMAT.

However, in this regard the user can fall back on the online functionality of engineering software SIMATIC STEP7 V5.5.3.0 or the components contained in this, such as SIMATIC Manager, hardware configuration, NetPro among others.

Simultaneous operation of process bus TCP/IP and ProfiNET I/O● With the CPU 416-3 PN/DP used simultaneous operation is possible of process bus

communication with TCP/IP protocol and I/O bus communication with ProfiNET I/O using the two available CPU internal ProfiNET ports.

● Additional CP443-1 communication processors could be abandoned as a result.

● However, no dual process bus is permitted due to the limited number of ProfiNET ports for each CPU, and there is a restriction in place of one process bus with Industrial Ethernet TCP/IP protocol across the plant.

● only possible in process bus with Industrial Ethernet ISO with an additional CP443-1. This must be taken into account with plant extensions in particular which already have a process bus with Industrial Ethernet ISO.



Special features when configuring ProfiNET I/O devicesThe process for configuring ProfiNET I/O stations is similar in principle to that for PROFIBUS I/O devices.

Apart from the fact that TCP/IP addresses are issued here instead of PROFIBUS addresses, the following special features must also be taken into account.

● Configuration identification - plant identifier Configuration of an identification and/or a plant identifier is also required for PROFINET I/O via "HW Config" in the PN-CPU.

● Configuration of the ProfiNET I/O topologyConfiguration of the ProfiNET I/O topology is also required for PROFINET I/O via "HW Config" in the PN-CPU. There is a separate Topology Editor available for this.

Further information can be found in the STEP 7 documentation.



Siemens Controls


4.5 Phase-outs as of V7.0

4.5.1 Obsolete functions

Discontinued functionsThe following functions or compatibilities of the previous versions are no longer supported as of BRAUMAT V7:

● Windows XP & Server 2003 operating system versions

● Controllers of the SIMATIC S5 series

● BRAUMAT Soft-CP network driver for process bus communication with AS Simatic S5

● SIWAREX M weighing system

NoteSIWAREX FTA

The successor product SIWAREX FTA can be incorporated in specific projects. Support is offered for this from the Support Center for Breweries.

Please contact SIMATIC Customer Support for questions on incorporating SIWAREX M scales.

Internet link to support pages (http://support.automation.siemens.com).

Hand data archives● The so-called hand data archives are no longer actively supported.

● The application "Archedit.exe" for displaying and entering hand data has been eliminated.

● Any "Archive type=Hand archive" attributes still available in the measured value description list are merely displayed but no longer have any function.

Message displays and archiving via "Meldarch.exe"The earlier "Message archive" application has been replaced with the following applications or functions as relevant:

● Messages can be archived using the "Archives Manager" application.

● Messages can be selected and displayed using the "Archive Viewer" application.

Old AREA.ini formatThe so-called "Old AREA.ini format" is no longer supported. Before upgrading to version V7, any plants still running with this AREA configuration must be converted with the "SiteCfg.exe" tool available with this version.

Notes on Use4.5 Phase-outs as of V7.0


http://support.automation.siemens.com

4.6 BRAUMAT SQL adapter option

4.6.1 Notes on Use

SQL Adapter on the BRAUMAT IOS● After installation/update of the BRAUMAT IOS server, a new "Configuration" application

with SQL adapter settings as well as the actual IOS component "SQL Adapter" is available.

● The IOS component is only started once the configuration has been completed and BRAUMAT has been rebooted.

● The SQL adapter reads data from BRAUMAT dBase files. You must avoid opening these files with independent programs such as Microsoft Excel in runtime, as these programs block write access to the files by the BRAUMAT server processes, which can result in data being lost.

SQL-Adapter on the database serverThe following configuration tools are available in the Start menu following installation on the DB host:

● Start→All Programs→Siemens Automation→SIMATIC→BRAUMAT SQL-Adapter→ BRAUMAT SQL Proxy Manager

● Start→All Programs→Siemens Automation→SIMATIC→BRAUMAT SQL-Adapter→BRAUMAT SQL Service Configuration

Using the SQL database● The structure of the SQL database (tables, columns, data types, etc.) is set up by

BRAUMAT programs and must not be modified by the user, since otherwise there is a risk of data loss, inconsistencies and data transmission by the SQL adapter which no longer works.

● User applications may only have read access to the BRAUMAT SQL database, since otherwise there is a risk of data loss, inconsistencies and data transmission by the SQL adapter which no longer works.

● As BRAUMAT SQL tables may change as part of product expansions, user applications and reports should not have direct access to these tables. Defining views is recommended instead for example, so that only these views need to be amended in the event of any changes.

IT security→ Notes on Windows system and user accounts as well as SQL server settings are available in the "SQL DB Host" manual, chapter "Installation and configuration / Setup program".

Notes on Use4.6 BRAUMAT SQL adapter option


Siemens Controls


BRAUMAT configuration changes

NoteChange of instance names and identifiers in the BRAUMAT parameter assignment● Names of recipes, plant units, etc. are never used as unique identifiers in BRAUMAT. They

can be changed at random and at any time because identification always takes place by means of unique instance IDs.

● We generally recommend to only use this BRAUMAT instance ID as identifier in higher-level systems (MIS/MES/ERP).

● We also recommend that you do not change the instance names after commissioning because the non-unique and non-constant names may be used for reporting.

4.6.2 Upgrading earlier project solutions

Compatibility, upgrading earlier project solutionsPrior to the version BRAUMAT/SISTARClassic V6.0 SP2 certain plants/customers used the following database connections not released as a product:

1. the so-called CIS interface

2. BRAUMAT MIS interface (SISTAR SQL connection) - a project-specific predecessor to the new "BRAUMAT SQL Adapter" product option presented here.

3. BRAUMAT MES interface (SISTAR-API) - incorporation of data from an MES system into BRAUMATClassic.

These application solutions used prior to BRAUMAT/SISTARClassic V6.0 SP2 are expressly incompatible with the product option presented here on account of interface and database changes.

For 1 and 2:● In the event that this type of plant is upgraded to BRAUMAT V7.0.1 any existing database

connection must be migrated to the "BRAUMAT SQL Adapter" product option for BRAUMAT V7.0.1. Any customer-specific database application must be adapted accordingly.

● No automatic migration of the database application or of the database itself can be offered for upgrades.

For 3:● There has been no adaptation or test of the MES interface for BRAUMAT V7.0.1.

● Upgrading a plant to BRAUMAT V7.0.1 is only possible without the MES interface until further notice. Conversely any upgrade to BRAUMAT V7.0.1 must be abandoned if the MES interface is to continue in operation.



General:Upgrades for plants with the listed MIS/MES connections (prior to V6.0 SP2) require customer-specific implementation and must be supported by the Support Center for Breweries where necessary.

Please contact SIMATIC Customer Support for questions on upgrades for database connections prior to BRAUMAT/SISTARClassic V6.0 SP2.

Internet link to support pages (https://support.automation.siemens.com)



Siemens Controls

https://support.automation.siemens.com




Upgrade of plants < V7.0 55.1 Upgrades with new functions in use

● Existing S7 - PCUs must be migrated to the new PCU-V7

● Existing S5 - PCUs must be migrated to Simatic S7 and to PCU-V7

● Gradual migration of multiple S5 – PCUs to S7 with intermediate recipe/batch sequence tests (mixed operation) is not possible.

● There is no support for the PCU migration to V7 or from Simatic S5 to Simatic S7 from the BRAUMAT product itself.

Recommendation:Upgrades for plants with Simatic S5 PCUs require customer-specific implementation and must be supported by the Support Center for Breweries where necessary.

Please contact SIMATIC Customer Support for questions on upgrades for previous BRAUMAT versions with Simatic S5.

Internet link to support pages (http://support.automation.siemens.com).


Siemens Controls



5.2 Upgrades with no new functions in use● Existing S7 - PCUs can be retained irrespective of the PCU version

● Existing S5 - PCUs must be migrated to Simatic S7. Version < V7 can be selected as the PCU version.

● If there is to be a gradual migration of multiple S5 – PCUs to S7 with intermediate recipe/batch sequence tests, then this is only possible via the previous BRAUMAT versions ( < V7). The upgrade to V7 then takes place on IOS stations.(→ operating system must be observed).

● There is no support for the PCU migration to V7 or from Simatic S5 to Simatic S7 from the BRAUMAT product itself.

Recommendation:Upgrades for plants with Simatic S5 PCUs require customer-specific implementation and must be supported by the Support Center for Breweries where necessary.

Please contact SIMATIC Customer Support for questions on upgrades for previous BRAUMAT versions with Simatic S5.

Internet link to support pages (http://support.automation.siemens.com)

Upgrade of plants < V7.05.2 Upgrades with no new functions in use



5.3 IOS migration

BasicsFor the IOS stations there are different directories for the system and the project data in the new system version. Existing "windcs" directories can be cleaned using the "BM_Config.exe" migration tool also supplied. The following procedure is recommended for this:

● Complete the BRAUMAT V7 IOS installation via the new setup program

● Backup the existing "windcs" directory beforehand before renaming it

● Call the BM_Config up and select the new project path

● The windcs directory originating from the previous version can be adapted to a project in version V7 using the "Check" function (delete system resources).

● Update the plant configuration with "SiteCfg.exe"

Also note the following if there is an existing S5-PCU:

● Change PCU Type S5 → S7 in "SiteCfg.exe"

● Create the PCU directories for new PCUs of the S7 type using SiteCfg.exe.

● Check and adapt the overall configuration for existing S5 data references.

Note

Additional important information and notes in connection with upgrading existing plants is also available in the previous subsections of "Instructions for use":● What's new as of V7.1? (Page 27)● Phased out functions as of V7.1 (Page 41)● What's new as of V7.0.1? (Page 42)● What's new as of V7.0? (Page 50)● Phase-outs as of V7.0 (Page 62)● BRAUMAT SQL adapter option (Page 63)

Upgrade of plants < V7.05.3 IOS migration


Siemens Controls


BRAUMAT basic menu - project-specific adaptation of the basic menu● The BRAUMAT basic menu is now opened via a new "Application Center" desktop icon or

via a Start menu entry of the same name. The content and structure of the tabs are determined by the system's own definition file "<sys-path>\Siemens\Braumat\Texte.x\BM_AppCenter.ini". If project-specific settings are to be transferred when a plant is upgraded, these must be selectively copied from the existing "menuV460.ini" file to the new definition file.

● For this purpose, the definition file "BM_AppCenter.ini" from the "<sys-path>\Siemens\Braumat\Texte.x\..." directory must be copied to the project directory "<proj-path>\Texte.x\..." (x = language number, e.g. Text.0 = German texts, Text.x = Spanish or English) and adapted accordingly.

● If the "BM_AppCenter.ini" file is found in the project directory when the "ApplicationCenter" is started, this is input and interpreted instead of the system's own configuration file. If any existing user-specific adjustments from earlier versions ("MenuV460.ini") are to be incorporated in the upgrade, these must be entered accordingly into the new "<proj-path>\Texte.x\BM_AppCenter.ini" configuration file.

BRAUMAT SchedulerAll path information in the project-specific Scheduler configuration file "<proj-path>\sys\ProShed.ini" must be migrated to the new paths of the system <sys-path> or project <proj-path> by the user, if this path information is still needed at all.

● For example, the following BRAUMAT Scheduler entries are obsolete and should be completely removed:All application calls of "Trendman.exe", "Time.bat", "Transtime.exe", "sistar_adp.exe"

● Paths must be changed for:All application calls of "transbst.exe", "userstart.exe"

Free protocols - modified example MDB● Due to the changed license structure and the separation of the "System" and "Project"

paths, the integrated MS Access macros in the supplied example MDB "<sys-path>\!BM_Proj\Access32\PI_CHA32.MDB" had to be adapted.

● Existing project-specific MS Access applications for "free protocols" from earlier BRAUMAT versions must be upgraded manually with the current Access macros.

● For this, the full MS Access product is required.

New concept for time synchronization● The time synchronization is carried out in BRAUMAT as of version V7 on request using the

system's own time synchronization functions.

● These are controlled using the communication relationships defined in the "SiteCfg" configuration tool and can also be activated there for the relevant station.(→ see BRAUMAT System Manual, section 3.4.6.11)



● The previous BRAUMAT Scheduler solution with „TRANSTIME.exe“ (IOS→PCU synchronization) and „Time.bat“ (IOS→IOS synchronization) is thus omitted and must be eliminated when the new „SiteCfg“ settings are activated (see section "BRAUMAT-Scheduler").

● Using the "change system time" selection box in the "BM_Config.exe" configuration tool, the right to change the PC system time is entered in the Windows group policy for the "BRAUMAT Group" user group. This is necessary if the time synchronization between the IOS stations is to be performed using BRAUMAT's own mechanisms.

Definition of the system messagesThe BRAUMAT system messages now have a fixed definition in the system with regard to structure and message texts. This yields the following consequences:

● The "Meld.def" message definition file no longer exists.

● The "melddef.txt" definition file is no longer located in the project path and can no longer be edited by the user.

RCS material sequencesThe rule valid in previous BRAUMAT versions that materials of a material group are automatically allowed as successor is no longer valid.

As a result of the following new rules, significantly greater flexibility is achieved:

● If the material's own group is configured as a successor, these materials are allowed as successors.

● If the material's own group is not configured as a successor, these materials are not allowed as successors.

This enables the configuration engineer to create a suitable material sequence configuration according to requirements.

NoteChecking of the material groups and material sequences● When the project is upgraded, the existing material definitions, material groups, and

material sequence relationships are transferred 1:1 initially. ● These must be checked according to project requirements in connection with the new rules

and adapted, if necessary. In particular, if materials of a group are to have automatic predecessor/successor relationships with one another, this group must be configured explicitly as a "successor to itself".

● The configuration is made in the recipe editor (BRAUMAT basic menu / Production / Recipes ) with the new dialogs in the "Configuration / Material management..." menu.



Siemens Controls




Virtualization 66.1 General

Fundamentals

Note

VMware, the VMware logo and design, Virtual SMP and VMotion are registered trademarks of the VMware, Inc. in the United States and/or other countries. All other labels and names mentioned in this document may be subject to trademark protection.

Note

Problems that occur with operation on virtual machines are remedied by Siemens, if they can be reproduced on the standard runtime environment approved for BRAUMAT (real, not virtual operating environment). Otherwise we have to assume that the problem was caused by the virtualization software or the hardware components. Unfortunately, Siemens is not able to remedy the problem in this case. Make sure to take this aspect into consideration during plant configuration, and contract for the corresponding support services with your supplier of hardware components and virtualization software.

Regardless of this release for operation on virtual machines, the preferred use of BRAUMAT is still in real and not virtual operating environments. If any behavior should occur when using BRAUMAT in a virtual environment that deviates from standard operation in a real, non-virtual environment, it is only documented by FAQ.

What is virtualization?A virtual machine is a software computer on which operating systems and applications are running as on a physical computer. The operating system installed on a virtual machine is referred to as host operating system.

Because any virtual machine is a stand-alone computing environment, you can use it as desktop or workstation environment and as test environment or for consolidation of server applications.

Virtual machines are run on ESX server hosts. A host can run multiple virtual machines. The following concept shows the supported and approved virtualization of client IOS stations for BRAUMAT.


Siemens Controls


Virtualization6.1 General


6.2 Hardware and software requirements

Virtualization environmentThe infrastructure required for virtualization of BRAUMAT IOS clients is based on a so-called server-based virtualization with the following VMware products:

● VMware ESXi V4.1.0 or higher with VMware vCenter Server V4.1.0 or higher

● VMware vSphere Client V4.1.0 or higher

ESX serverThe ESX server provides the necessary or allocated hardware resources for operation of the virtual machines. Virtual machines can be created, cloned and configured with the "VMware vCenter Server" management tool.

The ESX server should meet the following hardware requirements:

● Sufficient main memory for operation of all virtual machines without memory swapping.

● Sufficient hard disk memory for operation of all virtual machines.

● Sufficient network cards for distribution of the load and configuration of isolated pools of related virtual machines.

The ESX server should come equipped with at least two network cards to separate the communication load on the client bus as well as on the BRAUMAT terminal bus.

● Network adapter 1: VMware client bus communication

● Network adapter 2: BRAUMAT terminal bus

Joint operation on a shared LAN adapter may result in interferences in the BRAUMAT IOS client / IOS server communication and is therefore not recommended.

VMware vSphere clientThe VMware vSphere client software is installed and executed on a standard Windows PC. Any machine from the inventory list of the ESX server can be switched on and operated with this application. You can also change the VM-specific settings.

Thin ClientA "Thin Client" can be used as alternative to the Windows PC with VMware vSphere client software. This is a basic system with screen, keyboard and mouse that can be used to visualize and operate a specific VM. The internal configuration of the Thin Client determines which virtual machine is going to be connected.

Virtual networkA virtual network mainly consists of a pool of related VMs, a virtual switch and a real network card of the ESX server. The configuration of the ESX server determines which elements belong to the virtual network.

Virtualization with BRAUMATBRAUMAT supports the virtualization of IOS clients. IOS servers must be run on real computers.

Virtualization6.2 Hardware and software requirements


Siemens Controls


The software and hardware requirements of a virtual IOS client basically correspond to those of a real IOS client.

In addition, the following requirements and restrictions apply to virtual IOS clients:

Stand-alone BRAUMAT environmentPlease note the following for trouble-free operation of the BRAUMAT plant and for external faults to not have any effect on the network of BRAUMAT systems:

● All virtual IOS clients should form a virtual pool of virtual machines that is connected to or configured with a separate virtual switch and a separate network card of the ESX server.

● This network card of the ESX server should only be connected to the real switch of the BRAUMAT terminal bus.

VMware settingsRecommended VMware settings for operation of a BRAUMAT IOS client:

CPU: 2 = Number of virtual processors (vCPU)

RAM: 2048 MB

Hard disk 1: Virtual hard disk with 50 GB

Hard disk 2: Virtual hard disk with 10 GB (minimum)

CD/DVD drive 1: Client device / ESX server device

Network adapter 1: VM network

USB connection 1: Client device / ESX server device

Host operating systemThe following host operating systems are supported for a virtual BRAUMAT IOS client:

Microsoft Windows 7 Ultimate SP1 (32-bit or 64-bit)

BRAUMAT installation on a VMThe installation and configuration of BRAUMAT for a virtual machine is the same as for a real computer. A requirement is that the host operating system of the virtual machine can be connected to a CD/DVD drive and a USB port. This connection can either be made by using USB drives on the ESX server or locally on the client device.

Virtualization6.2 Hardware and software requirements


6.3 LicensingThe licensing of a BRAUMAT software installation is the same for a virtual machine and for real hardware (SIMATIC Industrial Workstation). This means you have to license each BRAUMAT software installation on a virtual machine as you would on a real machine.

Virtualization6.3 Licensing


Siemens Controls


6.4 Project-specific virtualizationIn addition to virtual OS clients, the following virtual systems can be implemented project-specific with BRAUMAT under VMware ESXi:

● IOS server and IOS Single Station

● Communication with more than 8 automation systems

A special project approval is required which due to the technical operating conditions is based on a detailed analysis of the required configuration.

This project-specific approval is to ensure that the necessary hardware and software requirements have been met.

For parameter assignment of the virtual machines consult the hardware recommendations in chapter Hardware requirements (Page 12).

You can also monitor all virtual BRAUMAT stations through central administration of the ESXi servers.

Virtualization6.4 Project-specific virtualization


Documents

BRAUMAT Readme V7.1 (online)ucc.colorado.edu/siemens/BM-readme_en-US.pdf · SIMATIC BRAUMAT BRAUMAT Readme V7.1 (online) Readme Version: 2016-08-04 (Online) 09/2016 A5E38794248-AA