BRAUMAT-SISTAR Classic Administration (Function Manual)

Preface 1
Basic Menu 2
Language transfer 3
SIMATIC Access authorization,
Password 4
BRAUMAT/SISTAR Classic
Administration Data backup 5
Block transfer 6
Function Manual
Synchronization 7
Scheduler 8
Appendix 9
BRAUMAT/SISTAR Classic V6.0 SP2
11/2012
A5E00239375-09
Legal information
Warning 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.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates 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 Personnel
The 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 products
Note the following:
WARNING
Siemens 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.
Trademarks
All 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 Liability
We 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 AG A5E00239375-09 Copyright © Siemens AG 2012.

Industry Sector Ⓟ 12/2012 Technical data subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 Preface.........................................................................................................................................................5
2 Basic Menu...................................................................................................................................................9
2.1 Functionality..................................................................................................................................9
2.2 Working with the application........................................................................................................10
2.3 Configuration...............................................................................................................................10
2.3.1 Register of the Application...........................................................................................................10
2.3.2 Selection of the application with password check.......................................................................11
2.3.3 Application call via Menu bar > 'Program'...................................................................................11
3 Language transfer.......................................................................................................................................13
3.1 Overview......................................................................................................................................13
3.2 Concept.......................................................................................................................................13
3.3 Configuration...............................................................................................................................14
3.4 Engineering language..................................................................................................................14
4 Access authorization, Password.................................................................................................................17
4.1 General........................................................................................................................................17
4.2 User Query..................................................................................................................................17
4.3 Code Card Reader......................................................................................................................25
5 Data backup................................................................................................................................................27
5.1 Import/Export, Delete Archive files..............................................................................................27
5.2 Automatic delete function, if the hard disk is full..........................................................................27
5.3 Archive Manager.........................................................................................................................28
5.3.1 Functionality................................................................................................................................28
5.3.2 Working with the application........................................................................................................29
5.3.3 Archpath.txt.................................................................................................................................31
5.3.4 MultiClient functionality................................................................................................................35
6 Block transfer..............................................................................................................................................37
6.1 Functionality................................................................................................................................37
6.2 Client Area...................................................................................................................................37
6.4 Starting automatic block transfer at the command line prompt...................................................39
7 Synchronization..........................................................................................................................................41
7.1 Functionality................................................................................................................................41
7.2 Client Area...................................................................................................................................41
Administration
Function Manual, 11/2012, A5E00239375-09 3
Table of contents

7.3.1 Working with the application........................................................................................................42
7.3.2 Application call with parameter:...................................................................................................42
7.3.3 Call without parameter.................................................................................................................42
8 Scheduler....................................................................................................................................................47
8.1 General........................................................................................................................................47
8.2 Start of the Scheduler..................................................................................................................47
8.3 Configuration of the Scheduler....................................................................................................48
8.3.1 Scheduler Configuration..............................................................................................................48
8.3.1.1 Display Scheduler window...........................................................................................................48
8.3.1.2 Scheduler Cycle..........................................................................................................................48
8.3.2 Configure processes....................................................................................................................48
8.3.2.1 List of processes..........................................................................................................................48
8.3.2.2 Sections of applications...............................................................................................................48
8.3.2.3 Start types and parameters.........................................................................................................49
8.3.2.4 Configure Start time.....................................................................................................................49
8.3.2.5 Exit application............................................................................................................................50
9 Appendix.....................................................................................................................................................51
9.1 Trace Server Diagnostics............................................................................................................51
9.1.1 General........................................................................................................................................51
9.1.2 Procedure....................................................................................................................................51
9.1.3 Meaning of display elements.......................................................................................................51
9.1.3.1 Module selection list....................................................................................................................52
9.1.3.2 Main list.......................................................................................................................................52
9.1.3.3 Filter list.......................................................................................................................................52
9.1.3.4 Status line....................................................................................................................................52
9.2 Settings........................................................................................................................................53
9.2.1 Trace Server: Profile....................................................................................................................55
9.2.2 Trace Viewer (TRACEVWR.EXE)...............................................................................................56
Administration
4 Function Manual, 11/2012, A5E00239375-09
Preface 1
Purpose of the Manual
This manual describes the administrative tools for für BRAUMAT/SISTAR Cassic V6.0 and
gives you an overview of the following topics:
● BRAUMAT/SISTAR Classic V6.0 Basic Menu
● Access authorization and user administration
● Language transfer
● Data backup
● Block transfer
● Synchronization
● Scheduler
It helps you during installation and commissioning.
This manual is intended for those responsible for configuring, commissioning and servicing
automation systems.
Where is this manual valid?

This manual is valid for the software package BRAUMAT/SISTAR Classic V6.0.
The offered electronic manual is most largely identical with the contents of the on-line help.
Due to a technically necessary editorial deadline for the generation of electronic manuals
occasionally small deviations can occur compared to the on-line helps. The statements in the
on-line helps take precedence over those of the manual.
Place of this Documentation in the Information Environment

This manual forms part of the BRAUMAT/SISTAR Classic V6.0 documentation package. The
following schematic of the document architecture shows the individual manuals as well as their
thematic grouping within the entire program package
Administration
Preface
Document structure
'HVFULSWLRQ
RIWKH
,QVWDOODWLRQDQG
6\VWHP
&RQILJXUDWLRQ
$GPLQLVWUDWLRQ
&RPPXQLFDWLRQ
(QJLQHHULQJ 5HFLSHV\VWHP
ZLWK
EDVHGRQ
6
(3(FUHDWLRQ
%DWFKSURFHVVLQJ
'RVLQJDQG
:HLJKHUV
2SHUDWLRQ 2SHUDWLRQ
&RQWURORIEDWFKHV &RQWUROZLWK

EDVHGRQ6
%DWFKFXUYHV $SSOLFDWLRQVIRU

EDVHGRQ6
/RJJLQJ
0HVVDJHV
%XLOGLQJEORFN %XLOGLQJEORFN
OLEUDU\%DVLFV OLEUDU\5RXWH
&RQWURO
6HUYH :DWFK
%XLOGLQJEORFN 5RXWHV
GHVFULSWLRQ6
%XLOGLQJEORFN
GHVFULSWLRQ6 (QJLQHHULQJRI
WKH5RXWH&RQWURO
Administration
Preface
Further Support
If you have any technical questions, please get in touch with your Siemens representative or
agent responsible.
You will find your contact person at:
http://www.siemens.com/automation/partner (http://www.siemens.com/automation/partner)
You will find a guide to the technical documentation offered for the individual SIMATIC Products
and Systems here at:
http://siemens.de/simatic-tech-doku-portal (http://www.siemens.com/simatic-tech-doku-
portal)
The online catalog and order system can be found under:
http://mall.automation.siemens.com/ (http://mall.automation.siemens.com/)
Training Centers
Siemens offers a number of training courses to familiarize you with the SIMATIC S7 automation
system. Please contact your regional training center or our central training center in D 90026
Nuremberg, Germany for details:
Internet: http://www.sitrain.com (http://www.sitrain.com)
Technical Support
You can reach the Technical Support for all A&D products via the Web form for the Support
Request
http://siemens.de/automation/support-request (http://www.siemens.com/automation/support-
request)
Additional information about our Technical Support can be found on the Internet pages http://
siemens.com/automation/service (http://www.siemens.com/automation/service)
Service & Support on the Internet

In addition to our documentation, we offer our know-how online on the Internet at:
http://siemens.com/automation/service&support (http://www.siemens.com/automation/
service&support)
where you will find the following:
● The newsletter, which constantly provides you with up-to-date information on your products.
● The right documents via our Search function in Service & Support.
● A forum, where users and experts from all over the world exchange their experiences.
● Your local representative for Industry Automation and Drive Technology.
● Information on field service, repairs, spare parts and consulting.
Administration
Basic Menu 2
2.1 Functionality
The application 'Basic menu' is used for the overview and selection of all selectable
applications of the system.
The Client Area is divided into two areas:

1. Display of the Bitmap SYSTEM with the Version number or different Bitmaps
2. Display of the applications
Administration
Basic Menu
2.3 Configuration
● For the plant operation

● For the system operation (by activating the "Expanded‘‘ box)
Depending on the licensed System Version special non-enabled applications are displayed in
gray.
2.2 Working with the application

Working with the 'Basic menu' application includes the following activities:
Selection 'Basic Menu'

The selection of the application 'Basic Menu' is executed automatically after the system start.
Only 1 instance of the application can exist. Each activation of the application 'Basic Menu'
from other applications results in the first instance of the application being activated.
Selection of different applications

The selection of the applications from the basic menu can be executed in three different ways:
● Double-clicking on the text of the selected application
● Clicking on the application and pressing the input key
● Clicking on the application and selecting the menu items 'Program' 'Execute'
2.3 Configuration
2.3.1 Register of the Application

The structure of the 'Basic Menu' is defined in the '\\windcs\ \\Texte.?\menuv460.ini' file (?
represents the language number, e.g "Text.0" = German Texts).
The division into 3 register-user functions and on activation of the "Expanded" check box
additionally five register-system functions offers the following input possibilities:
Input Meaning
[Global] Global adjustment
Small=1,2,3 Register user page
Extended=4,5,6,7,8 Register System functions
Bitmap=logo.bmp Image in the basic menu
ExtendedName=Extended Name of the check box
[Chapter_1] Register
Name= Name of the Register
Desc= Description of the Register
Administration
Basic Menu
2.3 Configuration
Input Meaning
Bitmap= Displayed image of the register
Applications= Number of applications in the register
App1= List of individual applications
2.3.2 Selection of the application with password check

A password check can be carried out before calling an application. This is also configured in
the file menuv460.ini e.g. here the message archive should be called with a password level
255.
App3=message archive;passwchk.exe 255 List of individual applications

meldarch.exe
2.3.3 Application call via Menu bar > 'Program'

Menu bar > 'Program' This area of the menu is filled according to the file \\Windcs\\Texte.?
\Menuappl.ini
Administration
Language transfer 3
3.1 Overview
The system can be operated in different languages – independent of the Windows language
settings. By selecting the language in the ‘Main Menu’ or in the ‘PCU Server’ application and
a following a restart of Braumat/Sistar the corresponding language Dlls (subfolder …\windcs
\DLL.<language number>\*.dll) are loaded and when accessing plant text files by system
applications the corresponding subfolder (…\windcs\TEXTE.<language number>*.*) will be
selected.
3.2 Concept
The languages ‘German’, ‘English’ and ‘Spanish’ are installed in the basic delivery state. On
request any other languages can be created and delivered (only single-byte character sets
are possible). The language DLLs and text files should be stored in the corresponding
subfolders.
The system folder …\windcs\... contains the following subfolders for the Dynamic Link Libraries:
● …\DLL.0 Index 0 = German
● …\DLL.1 Index 1 = English
● …\DLL.2 Index 2 = Spanish
● …\DLL.10 Index 10 = English S88
● …\DLL.x Index x = any further languages
There is exactly 1 Dynamic Link Library for each system application in these subfolders. This
DLL contains the language-dependent resources (texts, dialogs, menus, icons, ...) of the
corresponding applications. These DLLs have the file name of the corresponding application
extended with "_".
Example: System applications 'Plant overview'
● \ WINDCS \ SYS \ seqctrl.exe
● \\WINDCS\DLL.0\seqctrl_.DLL German Resources
● \\WINDCS\DLL.1\seqctrl_.DLL English Resources
● \\WINDCS\DLL.2\seqctrl_.DLL Spanish Resources
● \\WINDCS\DLL.10\seqctrl_.DLL English - S88 Resources
● \\WINDCS\DLL.x \ seqctrl_.DLL any further foreign-language Resources
Furthermore, the DLL folders contain the COMLIB32.DLL file. This file includes language-
dependent resources which are used by all system applications and by the system library
WINDCS32.DLL. The WINDCS32.DLL file is in the folder …\windcs\SYS and exists only one
time. It includes only language-independent resources.
Administration
Language transfer
3.4 Engineering language
3.3 Configuration
The information as to which language is active is stored in the file …\windcs\SYS\SYS.INI.
This file is loaded in the data segment of the WINDCS32.DLL by starting the first Braumat/
Sistar application.
The languages must be announced to the system. The entry in the SYS.INI file looks as follows:
[Languages]
Numbers=0,1,<any further language numbers>
0=German
1=English
2=Spanish
10=English S88
:
<new Number>=<Language>
After restarting the system the user can select a new language via the Language Setting in
the Main Menu.
The language key is located in the following section:
[PC]
Language=<current language number>
Note
The engineering languages should be defined with the ‘SiteCfg’ Tool in the menu area > plant
settings. Further information is given in the ‘Installation & Configuration’ manual, in
subsections ‘Modifying factory settings’ as well as ‘PC definitions’.
Default Setting:
[PC]
LanguageEngineering=-1
Default adjustment = no changeover of the engineering language. The plant texts are located
in ‘…\windcs\PCU.nnn\texte\...’
Dynamic Engineering language setting

In this case, the engineering language is switched over with the system language according
to the following assignments in the AREA.ini file. The plant texts are located in ‘…\windcs
\PCU.nnn\texte.x\...’
Administration
Language transfer
[PC]
LanguageEngineering=x (x> -1); Default Engineering language, if
the following assignments are missing
LanguageEngineering0=0; Engineering language if system language
German is selected
English is selected
Spanish is selected
English S88 is selected
LanguageEngineeringx=y; free assignment …
Administration
Access authorization, Password 4
4.1 General
The system offers the possibility to have all operations and inputs subjected to a staggered
password protection. The protection is guaranteed by assignments of levels (2 to 255) for
defined users. The adjustment of level and announcement of the user is executed in the
application 'user administration'. After the query of the username and password before the
execution of a protected function, the corresponding user levels are compared with the filed
function levels. Only after a successful comparison is the requested operation or input possible.
With the system delivery only the username 'su' with password 'su' Level 1...255 is set as
default for the execution of all functions.
Level and username can be changed in any way by the application 'user administration', if the
level 200 (= System user) is available.
The system automatically requests the input of the password if the currently valid level is not
sufficient for the requested operation.
The input of the password is divided into the input of the username as well as the password.
The characters of the password are overwritten by the sign [*] and are therefore not visible.
The following user-staggering is useful. It is possible to enter several users under each user
group. The combination of the actions can also be adapted accordingly:
User Group Short Name Level Actions (Example) )

(Example.)
SUPERUSER Su 1-255 Execution of all functions permitted
OPERATORUSE Bed 1-100 Only selection of the user functions
R possible (left side in the menu). No
configuration, no system functions.
PROGRAMUSER Prog 1-200 Selection of the user and configuration
function. No system functions possible.
SPECIALUSER Spez <very special Only authorized for one or several very
Level or Level special function(s).
section>
In the basic delivery of the system there is only the super user (Name: 'su', Password: 'su').
All levels are set to 1, which means no password query is necessary. The levels are filed in
the SYS.INI file under:
[Levels]
<Level-Data name > = <1-255>
4.2 User Query

The system automatically requests that the username is entered (and where applicable the
password) if the currently valid level is insufficient for the requested operation. The characters
Administration
Access authorization, Password
4.2 User Query
of the password are overwritten by the sign [*] and are therefore not visible. The input of
username and password must be in this sequence. After that, the requested operation is
possible.
After the correct input of username (and password if required) a new password can be entered
for this user or the current password can be changed with the ‘New password’ button.
Only letters and digits are permitted. The input is closed with return.
The input must be repeated again for confirming the new password. The input is also closed
with return. If both password inputs are identical, the new password is valid.
If there are different inputs for the new password, the following note box 'password' will appear.
Therefore the password is not valid.
Users and passwords are managed in the "User Management" program. This program is
started in the Basic Menu -> Administration Tab -> User Management.
Create new user/Change user definition

Another dialog is opened via the command button 'Define' password in which the user, which
has already been defined, is listed. Via the command button 'New' a new user with the name
and the corresponding level section is entered. The check box 'Password' is grayed out with
a new input, i.e. the new user must enter a unique password. Only if an available user is
Administration
4.2 User Query
selected via the check box 'Change' can the user be requested to select a new password when
the 'Password' check box is deselected.
● The maximum user name length is 19 characters
● The maximum password length is 9 characters
Reset the password/Logout

The password can be reset by means of the following methods, which are independent of one
another:
● Automatic password reset
When this option is enabled, the password is automatically reset when the application is
ended.
● Password reset time > 0 min.
A time in minutes is defined with this setting. After this time has expired, all currently valid
password inputs are reset, regardless of active applications. Afterwards, the time is
restarted automatically. If the time value "0" is entered, the method is inactive.
● Manually by the user
The user has the possibility of resetting the password at any time by means of the 'Main
menu' application. Manually resetting the password is always possible, independent of the
automatic methods.
Enter password
If the ‘password’ window shows a star in the ''password" line for the relevant user, the user
has already entered a password. If the star is missing, a password must be selected.
The password is queried in an application which is provided with a password level. If the new
user intends to implement changes, he must enter his password one time via the command
button 'New Password'. After a security query the password is active.
Administration
4.2 User Query
Adjust program level
Via the command button program level → 'Define' the dialog is opened in which each application
or function can be assigned a level.
Note
Changes in level assignments become active only after restarting the Braumat system on the
according IOS.
The following table contains all function keywords with their brief description and the default
level assignments.
Program Function Description Level

BALIEDIT.EXE Bali_Chgpa Batch/Order System 1
● Change parameters
● Abort batch
● Insert batches
BALIEDIT.EXE Bali_Newor Batch/Order System - Enter order 1
BALIEDIT.EXE Bali_Proj Batch/Order System - Configuration 1
BALIEDIT.EXE Bali_Relba Batch/Order System - Change status 1
BALIEDIT.EXE Batch_PIL_Chg Batch/Order System - Changing batch process 1
input lists
LZSYS.EXE BEDIEN Process images - opening files, closing 1
BRAUMAT/SISTAR with LZSYS as shell
BIKO.EXE BIKO Image design - Application call 1
Administration
4.2 User Query

ANALOG/DIGITAL/ Commissioning Commissioning access 1
CTRL3/ICM3.OCX ICM3 – Simulation feedback/extended parameters
CTRL – Parameter/Unit (Tab. General, Parameter)
Digital – Simulation/Parameter
Analog – Parameter
DBEDIT.EXE DBEDIT DB Editor – Value change 1
ENTITYDEF.EXE EntityExplorer Entity explorer access 1
ICM3.OCX EntityOperator ICM - Entity Edit TAB operator 1
SeqCtrl,Unit_Ctrl.oc EOPAbort EOP Abort 1
x
SeqCtrl,Unit_Ctrl.oc EOPHold EOP Hold 1
x
SeqCtrl,Unit_Ctrl.oc EOPPause EOP Pause 1
x
SeqCtrl,Unit_Ctrl.oc EOPStart EOP Start 1
x
SeqCtrl,Unit_Ctrl.oc EOPStop EOP Stop 1
x
ESG.EXE ESG ICM - Application User access 1
ICM3.OCX ICMOperator ICM3 – User access (Manual-Auto, On-Off) 1
SeqCtrl,Unit_Ctrl.oc KETTE Plant overview/Unit_Ctrl.ocx - Inputs (old) 1
x
SeqCtrl,Unit_Ctrl.oc Kette_Hal Plant overview/Unit_Ctrl.ocx - Inputs/Stop 1
x
SeqCtrl,Unit_Ctrl.oc Kette_KPO Plant overview/Unit_Ctrl.ocx - Edit plant/unit 1
x
SeqCtrl,Unit_Ctrl.oc Kette_Scr Plant overview/Unit_Ctrl.ocx - Inputs/Step 1
x
SeqCtrl,Unit_Ctrl.oc Kette_Sta Plant overview/Unit_Ctrl.ocx - Inputs/Start 1
x
SeqCtrl,Unit_Ctrl.oc Kette_Sto Plant overview/Unit_Ctrl.ocx - Inputs/Cancel 1
x
SeqCtrl,Unit_Ctrl.oc KETTE_SW Plant overview/Unit_Ctrl.ocx - Setpoint inputs (old) 1
x
EditRec,ControlRec, Kette_Sw1 Plant overview/EditRec/Unit_Ctrl.ocx - Setpoints 1
SeqCtrl,Unit_Ctrl.oc 1-5
x
x
x
x
Administration
4.2 User Query

SeqCtrl,Unit_Ctrl.oc 21-...
x
SeqCtrl,Unit_Ctrl.oc Kette_Wei Plant overview/Unit_Ctrl.ocx- Sequence enabled 1
x
SeqCtrl,Unit_Ctrl.oc Kette_Zua Plant overview/Unit_Ctrl.ocx - Aux/user bit Off 1
x
SeqCtrl,Unit_Ctrl.oc Kette_Zue Plant overview/Unit_Ctrl.ocx - Aux/user bit On 1
x
KURVEIN.EXE Kurvein Curve Entry - Save 1
ARCHEDIT.EXE, Kurven_Bea Trend visualization. - Editing trends 1
KURVEN.EXE
SEQCTRL.EXE LeaveInterState Leave Intermediate State of EOP manually 1
WARTDAT.EXE Maint Maintenance data - Acknowledge and reset order 1
WARTDAT.EXE Maint_P Maintenance data - Parameter input and setpoint 1
ANALOG/CTRL3/ Maintenance Maintenance access 1
ICM3.OCX ICM3 – Parameter, Note text
CTRL3 – Parameter, Note text
DIGITAL – Note text
ANALOG – Simulation, Note text
EDITREC.EXE Mat_Ass Recipe system – Material stock/Settings/PCU 1
Download/Enable storage location
EDITREC.EXE Mat_Man Recipe system - Material management 1
EDITREC.EXE Mat_SetActSt Recipe system - Setting current material stock (for 1
installation or test purposes)
ARCH_MAN.EXE, Meldarch Message archive - Delete archive 1
MELDARCH.EXE
NEWMENU.EXE Menu_E Basic menu - Close application 1
NEWMENU.EXE Menu_M Basic menu - Move 1
NEWMENU.EXE Menu_P Basic menu – Windows Explorer access 1
EDITREC.EXE MR_Status_Chang Recipe system - Changing status of the master 1
e recipe
CTRL3.OCX Operator CTRL3 – User access (Manual-Auto, Internal- 1
External)
SEQCTRL.EXE OpReqAck Plant Overview - Operator acknowledgement 1
PARAM.EXE Param Parameter assignment - SW changes 1
PARATXT.EXE Paratxt Text Parameterization - Edit/Save 1
PCU_SERV.EXE PcuServ PCU server - General functions (old) 1
PCU_SERV.EXE PcuServ_Dbl PCU server - without menu bar 1
PCU_SERV.EXE PcuServ_End PCU server - End 1
PCU_SERV.EXE PcuServ_Ini PCU server - Edit INI files 1
PCU_SERV.EXE PcuServ_Kop PCU server - Coupling 1
PCU_SERV.EXE PcuServ_Opt PCU server - Options 1
PCU_SERV.EXE PcuServ_Smm PCU server - Mini/Size/Move 1
PCU_SERV.EXE PcuServ_Win PCU server - Restart Windows 1
Administration
4.2 User Query

QUEUING.EXE QueuingExplorer Queuing explorer access. 1
RCS_ONLINE.EXE, RCS_L1 RCS Online: Manual Stop 1
ROUTECON.EXE
RCS_ONLINE.EXE RCS_L2 RCS Online: Request, Start, Pause, Acknowledge 1
RCS_ONLINE.EXE RCS_L3 RCS Online: Route properties, configuration 1
EDITREC.EXE Rec_Cl Recipe system - Edit components list 1
EDITREC.EXE Rec_Head Recipe system - Recipe header 1
EDITREC.EXE Rec_Main Recipe system - Edit master recipe 1
EDITREC.EXE Rec_New Recipe system - Create new recipes 1
EDITREC.EXE Rec_Proj Recipe system – EOP definition, DFM definition, 1
equipment configuration, weigher definition in
storage locations
EDITREC.EXE Rec_Struct Recipe system – Change recipe structure 1
REGLER.EXE Regler_P Controller operation - Parameter input 1
REGLER.EXE Regler_T Controller operation - value input, key operation 1
EDITREC.EXE Rezepte Recipe system – Save Recipe 1
CONTROLREC.EX Rezepte_on Recipe Editor - Online editing 1
E, RECCONTR.EXE
CONTROLREC.EX Rezepte_sw Recipe Editor – change Setpoint Definition 1
E,
RECCONTR.EXE,
EDITREC.EXE
EDITREC.EXE,CON Rezepte_SWx Recipe system - Substitution or scaling of recipe 1
TROLREC.EXE setpoints
EDITREC.EXE RP_Status_Chang Recipe system - Changing status of recipe 1
e procedures
SITECFG.EXE SiteCfgSave Area.ini: Saving with SiteCfg.exe 255
SONDWERT.EXE Sondwt_N Special values - Edit Note text 1
SONDWERT.EXE Sondwt_p Special values - Parameter assignment 1
SONDWERT.EXE Sondwt_w Special values - Value input 1
SRP_NEU.EXE Srproted Step protocols - Delete 1
STATUS.EXE Status Status.exe - Application call 1
STEUERN.EXE Steuern Forcing – Value change 1
CONFIG.EXE Sysini_I System Settings - Save 1
USERMAN.EXE Sysini_P User Manager - Password/Level 1
NEWMENU.EXE, Sysini_S Basic menu, PCU Server Language/IOS settings 1
PCU_SERV.EXE
TRACEVWR.EXE TRACESVR Trace server operation 1
TRANSBST.EXE Transbst Block transfer – Start of block transmission 1
TRENDMAN.EXE Trendman Trend Manager - Close application 1
ZLSYNCHRONIZER ZLSynchronizer ZLSynchronizer - edit 1
.EXE
Further information on password functions of specific Braumat Controls (OCX):
Administration
4.2 User Query
UnitCtrl.ocx: KETTE_STA=1 Start sequencer/unit and quit rest

bit
" KETTE_STO=1 Stop sequencer/unit
" KETTE_SCR=1 Continue sequencer with next
step/Select step
" KETTE_WEI=1 Enable sequencer/unit
" KETTE_HAL=1 Hold sequencer/unit
" KETTE_ZUE=1 Aux/User bit On/Off
KETTE_ZUA=1
" KETTE=1 Pass synchronization/alternative
" KETTE_SW1=1 Set value 1 to 5
" EOPStart=1 Recipe operation by S88
" EOPHold=1 Recipe operation by S88
" EOPStop=1 Recipe operation by S88
" EOPPause=1 Recipe operation by S88
" EOPAbort=1 Recipe operation by S88
CTrl3.ocx: Operator=1 Auto/Manual
" Internal/External
" On/Off
" Open/Close
" Unit Sampling time
" Dead band
" Maintenance=1 STWE
" W Set value
" Y Control value
" YU/YO Control value limit
" Note text
" Commissioning=1 KP Controller gain
" TN adjusting factor (I-section)
" TV adjusting factor (D-section)
" Modify
" Unit
" REV Reversed mode
" XTR X-Tracking
" XN follow-up value
Analog.ocx: Maintenance=1 Simulation w/o check box
‘change’
" Y/X (according to Input or Output)
" +, - , ++, ---
" Commissioning=1 Check box 'Change’
" All other selections
Digital.ocx: Commissioning=1 All selections
Administration
4.3 Code Card Reader
UnitCtrl.ocx: KETTE_STA=1 Start sequencer/unit and quit rest

bit
ICM.ocx: no password Read maintenance data
" ICMOperator=1 Status
" Auto
" Manual
" On
" Off
" Maintenance=1 Reset
" Extended tab
" Maintenance tab ‘Parameter’
" Maintenance tab parameter/write
" Maintenance tab ‘Reset’
" Maintenance tab ‘Quit’
" Parameter tab, left page 'times’
" Commissioning=1 Parameter tab, right page
'extended’
" Improvement=1 Extended tab ‘Entity Port’
4.3 Code Card Reader

It is also possible to use the keyboard with magnet card reader as an option instead of entering
the password.
As long as there is a valid magnet card in the reading device, the password is not queried.
However, if the card is removed, no operation will be possible!
The following has to be adjusted after the keyboards are connected:
● Adjustments in SYS.INI:
[PC]
CODE32.DLL=CDCARD32.DLL
The operation levels are adjusted as usual.
● If a card is inserted which has not been entered in the internal card list, this number will be
entered in the CODES.INI file temporarily under:
[Info]
CardID=<Card number>
● This number can be copied as a real card input and supplied with levels accordingly
(Example):
[Users]
97121010000082409604=<Name>,<Min.Level>,<Max.Level>
From now on the card level is considered when the card is inserted.
Administration
Data backup 5
5.1 Import/Export, Delete Archive files
For the import/export of e.g. the archive files, an application 'archive manager' is in the system.
Here the project engineer can define their individual archive structures and sections in order
to realize definite file movements. Furthermore, some applications already have these features
incorporated for their specific archives.
For both possibilities so-called export disk drives should be defined (see system adjustments,
input in SYS.INI ). There should be a network connection to these disk drives or they are disk
drives of external data media (e.g. floppy disks). These are entered in files SYS.INI under:
● [ExportDrive]
Drives=<Drive disk identifier>, <Drive disk identifier>...
.
5.2 Automatic delete function, if the hard disk is full

The system records archive data (messages, step protocols, curves...) continuously and files
them on an adjusted mass storage device with a corresponding configuration. If this is e.g. the
local hard disk, it is not desirable that it overruns due to the permanent archive file recording
(messages, step protocol, curves,...).
An automatic delete function for the system archive files has been introduced for this reason.
It is/can be preset/configured in the file DISKMAN.INI. The following adjustments are possible:
● Time intervals to check the rest of the memory capacity, message display and delete:
[Repeat]
Rep_Normal=<Value in seconds for a normal test>
Rep_Limit1=<Value in seconds after the limiting value 1 is reached>
Rep_Limit2=<Value in seconds after the limiting value 2 is reached >
Rep_Msg=<Value in seconds for the corresponding message repetition>
Time=<Value in seconds for deleting periods>
Files=<Amount of files that are deleted in a cycle>
● Memory location – limiting values
[Spacelimit]
Limit1=<Low limit for the first message>
Limit2=<Low limit for the second message and start deleting>
Limit3=<Memory location upper limit up to the one to which it is deleted>
Administration
Data backup
5.3 Archive Manager
● Delete priority
[Priority]
;Delete sequence for archive types (0=trend, 1=free prot., 2=step prot., 3=messages,
4=complist, 5=temp/tmp)
Sequence=<Sequence of the deleting archive type >
● Maximum age of the archive files
[Timelimit]
Type0=<Maximum age in days with curve archives>
Type1=<Maximum age in days with free protocols>
Type2=<Maximum age in days with step protocols>
Type3=<Maximum age in days with messages>
Type4=<Maximum age in days with components list>
Type5=<Maximum age in days with Temp/Tmp directories>
Furthermore, it should be considered that the trace files which are created by activating trace
functions are deleted or the trace connections are deactivated any time.
Writing down system internals is necessary for the analysis of special fault performance or for
a better problem analysis (e.g. can be activated for the PCU Server in the PCU_SERV.INI
file).
The created ASCII trace files are in general located in the TEMP/TMP folder and can be deleted
without grounds for concern.
5.3 Archive Manager
5.3.1 Functionality
The application 'Archive Manager' is used for the administration of archive files.
These are created continuously during operation and filed on the hard disk of the IOS. Filed
are e.g. messages, free protocols, step protocols, curves, etc.
The archive types to be administrated by the Archive Manager can be freely configured. The
application allows the swapping out of archive files to export disk drives, their deletion or re-
import to the system disk in a convenient and time-saving manner.
The application is started under Basic menu -> Administration Tab -> Archive Manager.
The Client Area includes a list box "Selected Archive files“. There the currently selected archive
files are displayed completely with their total path. The list box is used exclusively to control
the selection.
The status line displays the user-defined disk capacity of the system disk drive and of a
selectable export disk drive.
Administration
Data backup
5.3 Archive Manager
5.3.2 Working with the application
Menu item Program:

Usage according to the usual SISTAR applications.
Administration
Data backup
5.3 Archive Manager
Menu item functions:

This item covers application-specific functions.
● "Selection" or 1.) Click Icon
A dialog box for selection of the archive type and the disk drive appears. With the button
"Previous selection" the last selection can be called again. After you have selected, continue
with "OK". Then a new dialog box is opened for any further selections according to archive-
specific indications.
With "OK“ it will branched out to the next dialog box, with "All" all files can be selected in
the current path.
The last dialog box is used for the selection of the requested files. It includes two list boxes:
"Available Archive files" and "Selected Archive files“. With the buttons "-->" or "<--" the
corresponding files which are marked can be transferred into the opposite list box. The
buttons ">>" and "<<" displace all included files in the different list box. The corresponding
file can also be moved by a double-click.
With "OK" the file selection is ended and the dialog box is closed.
The selected files appear with their complete path in the list box "Selected Archive files" of
the Client Area.
● "Export" or 2.) Click Icon
Export the selected archive files to an export disk drive. A dialog box appears for the choice
of destination disk drive. Afterwards the selected disk drive must be confirmed again in a
message box. During the export procedure a progress bar informs about the status of the
activity. After the export the list box is emptied in the field of activity.
● "Import" or 3.) Click Icon
Import the selected archive files on the archive-specific system disk drive. The selection
should be confirmed in a message box.
It should be considered:
As system disk drive with the corresponding path the application uses the indications
entered in the SYS.INI for the corresponding archive type. During the import procedure a
progress bar informs about the the progress. After the import the list box is emptied in the
field of activity.
● "Delete" or 4.) Click Icon
Delete the selected archive files. First there is a password query. Afterwards the selection
should be confirmed again. During the deleting procedure a progress bar informs about the
status of the activity. After deleting the list box is emptied in the section of activity.
Note
● The import is only possible from the export disk drives. Destination disk drive is
automatically in the system disk drive of the corresponding archive type which is
indicated by the SYS.INI.
● The export is only possible to export disk drives.
Menu item 'Options':

Under this item there are the usual switches in the SISTAR applications for unhiding and hiding
symbol bars, status lines and function keys.
Furthermore, the application 'archive manager' makes a menu item 'display' available with
which the disk drive should be selected whose free capacity should be displayed in the status
line.
Administration
Data backup
5.3 Archive Manager
After having clicked, a dialog appears in which all export disk drives are available for selection.
The display can also be deactivated by the selection "none".
5.3.3 Archpath.txt
With the function 'selection' various archive files can be selected. The dialog-controlled
selection refers to the search criteria and path description which is stored in the text file
ARCHPATH.TXT.
The path/file names stored in the text file are supplemented successively by the user
selections. The selection is made in a list box which presents the found files to the user
according to the list inputs or wildcard characters.
After a successful selection of the archive files the complete paths with file names are viewed
in the list box "Selected Archive files“ in the Client Area of the application.
The text file ARCHPATH.TXT is located in the ..Windcs\SYS folder.
Configuration:
In the file ARCHPATH.TXT a dedicated section must be entered for each archive type, as
described below. At the beginning of the text file the following section must be indicated one
time.
[ANZ]
Number = <Number> Amount of entered archive types
In the following the syntax for the configuration of a search path is listed for one archive type:
[TAB<Nr>] Number of the Archive type

Name = <Archive name> Archive name
PathDat = <Path/File name with Data file with complete path indication
wildcard character> and possible wildcard characters.
List<List-Nr> = <Name Listbox> ● List No:
Number of wildcard character
block
● Name List box:
List box headline, which is output
by selection of the corresponding
wildcard character.
If there is no input available, no
selection list box is displayed and
branched out to the next selection.
The next selection (List No.) starts
with the next wildcard character
block.
Administration
Data backup
5.3 Archive Manager
[TAB<Nr>] Number of the Archive type

From<List-Nr> = <Char number> character number from which the
selection starts
If it should not be searched from the
first question mark, the corresponding
character number should be entered.
To<List-Nr> = <Char number> character number, from which the
selection starts
If it should not be searched to the last
question mark, the corresponding
character number should be entered.
Ref<List-Nr> = <Reference to List No.> Reference to the list input which has
already been executed.
If there is no list input, the same input
is executed as for referenced list no.
If there is a list and ref input for a
number, the wildcard character block
is filled starting from the left. The next
step is to select the rest of the signs in
a list box, whereby the list input should
be used in connection with From/To.
References to several list inputs are
possible. The numbers should be
separated by ‘/’. The wildcard
character block is filled consecutively
starting from the left with the reference
indications.
Sec = <End> If secondary files should be selected
with the same paths and names at the
same time, but with a different
extension, the secondary extension
can be entered here.
Typ = <File type> File type according to SYS.INI, e.g.
0=Curves
1=Fr.Prot
2=Write out step protocol
3=Messages
In the following table the standard configuration at system delivery is displayed by means of
the ‘…\windcs\sys\Archpath.txt’ file: This may be configured at project-specific level.
Administration
Data backup
5.3 Archive Manager
Section Path/File structure

[ANZ] 13 Archive definitions to follow
Number = 13
[TAB1] …\windcs\FRPROT folder
;Name = Freies Protokoll: Empfangs-Daten FRJA_?? → subfolder year 2-chars
Name = Free protocol: Receive data (00=2000)
PathDat = \FRPROT\FRJA_??\REZ_???\FE_??_??.DBF
REZ_??? → subfolder Recipe type 3-
List1 = year
chars
List2 = recipe type
Ref3 = 1 FE_??_??.DBF → FE file for Year/
List4 = month Month in format <yy_mm>
Type = 1
;Name = Freies Protokoll: Hand-Daten FRJA_?? → subfolder year 2-chars
Name = Free protocol: Manual data (00=2000)
PathDat = ..\FRPROT\FRJA_??\REZ_???\FH_??_??.DBF
REZ_??? > subfolder Recipe type 3-
List1 = year
chars
List2 = recipe type
Ref3 = 1 FH_??_??.DBF → FH file for Year/
Type = 1
;Name = Freies Protokoll: Sende-Daten FRJA_?? → subfolder year 2-chars
Name = Free protocol: Send data (00=2000)
PathDat = ..\FRPROT\FRJA_??\REZ_???\FS_??_??.DBF
List1 = year
chars
List2 = recipe type
Ref3 = 1 FS_??_??.DBF → FS file for Year/
Type = 1
[TAB4] …\windcs\SRPROT folder
;Name = Schrittprotokoll Typ 5 SRJA_?? → subfolder year 2-chars
Name = Step - protocol: Type 5 (00=2000)
PathDat = ..\SRPROT\SRJA_??\REZ_???\ANR?????
\S???????.DBF
chars
List1 = year
List2 = recipe type ANR????? → subfolder order no. –
List3 = block range (e.g. ANR00100 = Anr.00000 ..
List4 = Order no. 00100, etc.)
From4 = 3 S???????.DBF → file for order no. in
To4 = 7 format <yynnnnn>
Ref4 = 1
Type = 2
[TAB5] …\windcs\MELD folder
;Name = Meldungen ME_??_?? → subfolder Year/Month in
Name = Message format <yy_mm>
PathDat = ..\MELD\ME_??_??\MA??????.TXT
MA??????.TXT → file per day in format
List1 = year
<yymmdd>
List2 = month
List3 = day
From3 = 5
To3 = 6
Ref3 = 1/2
Type = 3
Administration
Data backup
5.3 Archive Manager

[TAB6] …\windcs\TREND folder
;Name = Kurven DATA.??? → subfolder measuring
Name = Trend value No. range
PathDat = ..\TREND\DATA.???\KW????\????T???.H
KW???? → subfolder calendar week in
List1 = block
format <wwyy>
List2 = week/year
Ref3 = 2 ????T???.H → Header files in format
List4 = No. <wwyy>T<meas.value.no>
Sec = S ????T???.S → Data files
Type = 0
[TAB7] …\windcs\ TREND folder
;Name = Kurven-Übersicht DATA.??? → subfolder measuring
Name = Trend - overview value No. range
PathDat = ..\TREND\DATA.???\BA??T???.H
BA??T???.H → Batch curves header
List1 = block
files in format <yy>T<meas.value.no>
List2 = year
List3 = No.
Type = 0
[TAB8] …\windcs\RECIPE\COMPLIST folder
;Name = Komponentenliste clja_?? → subfolder year 2-chars
Name = Complist - directory (00=2000)
PathDat = .\recipe\complist\clja_??\rez_???\anr?????
\CI_?????.DBF
chars
List1 = year
List2 = recipe - type ANR????? → subfolder order no.
List3 = order - no. CI_?????.DBF → complist for batch
List4 = batch - no.
Type = 4
[TAB9] …<user-temp-lw>\TEMP folder
Name = Temp - dir.
PathDat = ..\TEMP\????????.???
List1 = name
List2 = type
Type = 5
[TAB10] …\windcs\TMP folder
Name = Tmp - dir
PathDat = ..\TMP\????????.???
List1 = name
List2 = type
Type = 5
[TAB11] …windcs\LOGGING\GlobLog folder
Name = GlobLog Gl_?? → subfolder year 2-chars
PathDat = ..\Logging\GlobLog\Gl_??\GL??????.dbf (00=2000)
List1 = year
GL??????.dbf → Global log file per day
List2 = month
in format <yymmdd>
List3 = day
From3 = 5
To3 = 6
Ref3 = 1/2
Type = 3
Administration
Data backup
5.3 Archive Manager

[TAB12] …windcs\LOGGING\UNITHIST folder
Name = UnitHist UH_?? → subfolder year 2-chars
PathDat = ..\Logging\UnitHist\Uh_??\UH??????.dbf (00=2000)
List1 = year
UH??????.dbf → Unit history log file
List2 = month
per day in format <yymmdd>
List3 = day
From3 = 5
To3 = 6
Ref3 = 1/2
Type = 3
[TAB13] …windcs\LOGGING\USERLOG folder
Name = UserLog UL_?? → subfolder year 2-chars
PathDat = ..\Logging\Userlog\Ul_??\UL??????.dbf (00=2000)
List1 = year
UL??????.dbf → User log file per day
List2 = month
in format <yymmdd>
List3 = day
From3 = 5
To3 = 6
Ref3 = 1/2
Type = 3
5.3.4 MultiClient functionality

If the application is started on a client, the target directory on the export drive will consist of
the IOS name and the archive file. This means you can save the archives of several servers
on one export drive.
Table 5-1 Example:
start on source path path on export drive

Server <IOS01> C:\windcs\... A:\windcs\...
Client <IOS21> \\IOS01\C\windcs\... A:\IOS01\c\windcs\...
Administration
Block transfer 6
6.1 Functionality
The application 'Recipe/Block transfer' has the following functionality:
● Transfer of PCU blocks from PCU-RAM to the hard disk of the IOS.
● Transfer of PCU blocks from the hard disk of the IOS to the PCU-RAM.
While processing the same file simultaneously by several users (IOSs) the consistency of the
data will be guaranteed by attaining validity for the last saved file.
The application is started under Basic menu -> Administration Tab -> Block transfer.
6.2 Client Area

The Client Area is divided into two areas:
right: Buttons for using the functions: Save, load, process blocks
left: Listing the transfer blocks
Column 1: Area
Column 2: Block
Column 3: Block number

Working with the application 'Block transfer' includes the following activities:
Create new transfer list

After selecting the menu item New in the menu File or clicking the icon New a new transfer
list will be filed in the toolbar.
Open transfer list

After selecting the function Open in the menu File or after clicking the icon OPEN in the
toolbar a transfer list can be opened. A modal dialog box for the selection of drives, directories,
file name and file format will be displayed.
The files are in the directory: \ WINDCS \ TRANS
Block transfer:
The files for the block transfer have the format "*.trs".
Administration
Block transfer
File transfer list

After selecting the function Save in the menu File or after clicking the icon SAVE in the
toolbar the current transfer list will be filed.
To save the transfer list under a different name use the Save as... function in the menu File.
A modal dialog box for the selection of drives, directories, file name and file format will be
displayed.
The data files are filed in the directory \ WINDCS \ TRANS.
Block transfer:
The files for the Block transfer have the format "*.trs".
Edit transfer list

After selecting the function Process in the menu Functions, after clicking the button Process
in the Client Area or after activating the function key F5 the transfer list can be edited. A modal
dialog box will be displayed.
Single recipes/blocks can be deleted from the transfer list with Delete, with Add recipes/blocks
can be added or with the function Delete all recipes/blocks can be deleted from the Recipe/
Block list. When you assign numbers, you can define individual recipes/blocks, or an area (x
to y), or you can use wildcards "*" to select all available recipes/blocks.
Load blocks
After selecting the function Load in the menu Functions, after activating the function key F4 or
after clicking the button IOS->PCU in the Client Area a dialog box will be displayed if no transfer
list is opened. After the input of Area and Block and activating OK the transfer will start. If a
transfer list is opened the block transfer starts immediately and without any feedback. The
currently transferred block is displayed.
Save blocks
After selecting the function Save in the menu Functions, after activating the function key F3
or after clicking the button PCU->IOS in the Client Area a dialog box will be displayed if no
transfer list is opened. After the input of Area and Block and activating OK the transfer will
start. If a transfer list is opened the block transfer starts immediately and without any
feedback. The block that is transferred currently is displayed.
Options -> Settings

You can customize the following settings:
● Report -> always generate log file
Generates the ASCII format log file "Report.txt" in the .\WINDCS\TRANS folder. An existing
file will be overwritten.
● Report -> Print automatically
The generated log file is output on the default printer
Administration
Block transfer
6.4 Starting automatic block transfer at the command line prompt
● Error handling -> Blocks not found

When this function is enabled, all non-existent blocks will be logged. Otherwise, the log
indicates all transferred blocks.
● Error handling -> Cancel transfer
The transfer of data is automatically canceled if a block is not found in the list.

The program "Transbst.exe" is suitable for generating automatic backups of the PCU blocks.
The user may configure a periodic call of this program in "Prosched.exe" (see chapter
Scheduler (Page 47)), in order to start this cyclic block transfer.
Calling "Transbst"
Command Function
Transbst /u:upload "transbst.exe" executes the commands in "windcs/trans/upload.trs".
The application window of "transbst.exe" is visible during the
execution of the program.
Transbst /u:upload /s "transbst.exe" executes the commands in "windcs/trans/upload.trs".
The application window of "transbst.exe" is hidden during the
execution of the program.
Administration
Block transfer
Example:
The sample configuration and the corresponding INI files below describe the syntax:
● We want to set up a cyclic function for the automatic transfer of data every 30 minutes.
""Transbst.exe" should fetch all the blocks from PCU14,16 (FB,FC,OB,DB,SDB) and
PCU4,8 (FB,FX,OB,DB,DX,SB,PB) at intervals of 30 minutes. These PCUs require the file
"windcs\trans\upload.trs", which must have been configured accordingly in the application
(see above)
● Prosched.ini
[Global]
Processes=TransBst1,TransBst2
[TransBst1]
Application=d:\windcs\sys\transbst.exe /u:upload
;HOURLY,DAILY,WEEKLY
Type=HOURLY
;to be started each hour at xxh:15m:00s, Daily, hourly or weekly
ReqTime=00:15
[TransBst2]
Application=d:\windcs\sys\transbst.exe /u:upload
;HOURLY,DAILY,WEEKLY
Type=HOURLY
;to be started each hour at xxh:45m:00s, Daily, hourly or weekly
ReqTime=00:45
● Transbst.ini
[Options]
;Break transmission when an error occurs
BreakOnErr=0
;i.e. the transfer is not canceled if the block is not found
Result:
"ProSched.exe" starts the cyclic transfer of the blocks at intervals of 30 minutes. The function
generates the block folders with the current block files in windcs\pcu.xxx. The ProSched
window indicates the start and the time of the start of "transbst.exe".
Further switches the user can set for calling the program "Transbst.exe":
● /U:<file name> .... Upload with Config file <file name>
● /D:<file name> .... Download with Config file <file name>
● /S ….Program execution with hidden window
Administration
Synchronization 7
7.1 Functionality
The application synchronizes the files and folder sub-trees within any group of network shared
drives. In this way the latest version of a file is used as the source.
The application is used in three steps:
● Write file definitions (File 'synchro.def')
● Compare files (File 'synchrox.tmp')
● Copy files (File 'synchrox.err')
The program is started under Main menu -> Administration Tab -> Synchronization.
7.2 Client Area

As the synchronization works automatically, this application has no main window with a Client
Area. Only the dialog boxes are displayed for the display of the synchronization sequence.
Administration
Synchronization
7.3.1 Working with the application

Working with the application 'Synchronization' includes the following activities:
7.3.2 Application call with parameter:
Automatically start: /a
If the application is started with the parameter '/a', all functions are carried out fully
automatically.
There is no query!
All non-existent files or obsolete files are copied without any queries!
Run with definition file: /def

After the parameter the file name of the definition file (with extension) stands behind a blank.
The file will be searched in the directory ‘windcs\etc’
Delete the file ‘notsync.ini: /u

With this parameter at the end of the synchronization the file ‘notsync.ini’ will be deleted in all
SYS.INI paths Deleting the file will re-enable a path, which was disabled with path monitoring.
See: Installation and Configuration → Path monitoring
7.3.3 Call without parameter

After having called the application it is queried once again whether the synchronization should
be carried out.
If this box is answered with 'Yes', all files are compared. The result is filed in the 'c:\tmp
\synchrox.tmp' file (x can accept the value 0 - 4 ; the file with the latest date is the result of the
last synchronization run).
If faults arise with copying, they will be stored in the 'tmp\synchrox.err' files ("tmp“=Windows
Set-Variable; x has the same value as the corresponding file 'synchrox.tmp').
Example of a line of 'synchrox.err':
"c:\windcs\pcu.001\param.pcu can't copied to e:"
Administration
Synchronization
Call via input in 'sys.ini'

The application can be executed automatically with the start of the system. The following input
must be in the file '..\sys\sys.ini' :
● [PC]
● Autostart=synchro.exe
The input is not necessary if the OS works as Recipe Server. A synchronization occurs with
every start of the Recipe Server.
File selection
Only files in the following folders are copied:
Path and files Search depths*) Disk drives**)

1. pcu.*\*.* 1 PCU
2. pcu.*\db\db.* 8 PCU
3. pcu.*\dx\dx.* 8 PCU
4. pcu.*\fb\fb.* 8 PCU
5. pcu.*\fx\fx.* 8 PCU
6. pcu.*\ob\ob.* 8 PCU
7. pcu.*\pb\bp.* 8 PCU
8. pcu.*\sb\sp.* 8 PCU
9. pcu.*\regler\*.* 8 PCU
10. pcu.*\texte.*\*.* 8 PCU
11. pcu.*\notetxt.*\*.* 8 PCU
12. pcu.*\rezept\*.* 3 RECIPE
13. pcu.*\rezept\re*.*\re*.dbf 8 RECIPE
14. bilder\*.* 8 PROJ
15 symbole\*.bmp 8 PROJ
16 etc\*.* 8 PROJ
17 texte.*\*.* 8 PROJ
18 notetxt.*\*.* 8 PROJ
*) Search depth: Amount of subfolders starting with the system path
**) Disk drives: the disk drives that are in the file 'sys.ini' ([Paths]) are browsed with the corresponding
input.
The definition of which files are synchronized is filed in the file 'c:\tmp\synchro.def' . This file
is created new with each program run.
'synchrox.tmp' file
In this file all different files which have been found with synchronization are listed.
Example:
*** Line: 1 Path: pcu.*\ Depth: 1
Administration
Synchronization
j:\winbrau PCU.001 NAME.TXT older c:\windcs j:\winbrau PCU.001

PARAM.OLD does_not_exist c:\windcs
Structure:
Comment lines start with '***'.
● Any further lines have the structure:
<Destination disk> <drive path> <file name> <relation> <source disk drive>
● <Relations> can be:
"older" File which exists but is obsolete
"does not exist" There is no file on the destination drive
Inputs in the file '..\sys\sys.ini'

The disk drives that are synchronized to each other are defined in the file '..\sys\sys.ini'.
Under the section [PATHS] disk drives can be indicated for different functions for which the
synchronization should be carried out.
[PATHS]
PROJ=c:\windcs ;\\server1\c\windcs Type: 0
BATCH=c:\windcs;\\server1\c\windcs Type: 1
STEP=c:\windcs Type: 2
MSG=c:\windcs ;\\IOS03\c\windcs Type: 3
RECIPE=c:\windcs;\\server1\c\windcs Type: 4
PCU=c:\windcs;\\server1\c\windcs Type: 5
SILO=c:\windcs;\\server1\c\windcs Type: 6
Files only in the system paths Type: -1
Configuration of the file '..\etc\synchro.def'

The application 'Synchronization' only considers files below the system folder. Which files
should be synchronized can be defined via the file 'synchro.def'.
In this file up to 100 file definitions can be configured. Each definition consists of four parts:
● Path indication
'Wildcards' are allowed as is usual for MS-DOS.
● Type indication
Reference to configuration of the disk drive in the file 'sys.ini'.
● File indication
'Wildcards' are allowed as it is usual for MS-DOS.
● Search depth
Indication of the amount of subfolders which should be browsed, a maximum of 8.
Administration
Synchronization
Example:
[DEF000] Continuous number starting with 0 up to a maximum of 99.
Gaps are not allowed, three-digit number with leading zeros.
Path=pcu.* All paths which start with 'pcu.' .

Type=5 Disk drive type 'PCU' (see file 'sys.ini')
Files=*.* All files
Deep=1 Only within the first subfolder
● In order to prevent the overwriting of an edited 'synchro.def' with the next synchronization,
the following input must be carried out in the file '..\sys\synchro.ini':
[APP]
WriteDefFile = 0
Administration
Scheduler 8
8.1 General
In BRAUMAT/SISTAR Classic V6.0 a Scheduler Program is integrated.
The Scheduler has the functions:
● hourly, daily or weekly start of applications
● Monitoring of applications and restart, if necessary.
8.2 Start of the Scheduler

The Scheduler can be started
● via the basic menu,
● via the Autostart group of Windows,
● manually
● from the PCU Server.
The following key should be set in the PCU_SERV.INI
– [Pcu_serv]
– ....
– ;Start and Check for running of Process Scheduler "ProSched.exe"
– RunProcessScheduler=1
The Start type depends on which applications should be started and monitored with the
Scheduler.
The name of the application is prosched.exe and it is located in the BRAUMAT/SISTAR Classic
V6.0 system directory.
Note
When the scheduler is started, the configured start conditions are checked immediately and
the applications are started accordingly. In case of the start types 'daily' and 'hourly'
PROSCHED.EXE determines whether the previous start did not happen within the configured
time period and tries to make up for this. In case of start type 'weekly' an application is started
only if the requested day of week matches the actual day.
Administration
Scheduler
8.3 Configuration of the Scheduler
The Scheduler will be configured via the file prosched.ini in the system directory.
8.3.1 Scheduler Configuration
8.3.1.1 Display Scheduler window
Key: [Config]
Input: ShowWindow=0
8.3.1.2 Scheduler Cycle

The cycle for examining and starting applications can be configured. The value is indicated in
seconds.
Key: [Config]
Input: CycleTime=30
8.3.2 Configure processes
8.3.2.1 List of processes
Key: [Global]
Input: Processes=XXProc
A list of processes can be entered here. The inputs should be separated by comma. The name
allocated in the list need not conform with the starting applications.
One more section should be made in the file prosched.ini for each of the processes. The key
name of the section should conform explicitly with the processes names in the process list.
(Example: [XXProc])
8.3.2.2 Sections of applications
Key: [xxProc]
Input: Application=
Administration
Scheduler
The input can be made with path indication and application parameters. If no path is indicated
the application will be searched according to Windows Standard.
8.3.2.3 Start types and parameters
Input: Type=HOURLY, DAILY, WEEKLY
Allows the hourly, daily (defined minute of the day) or weekly (defined day of the week) start
of the application. For further definitions see 'Configuring Start time' below.
Input: Type=PERMANENT
The inputs for day and time are not relevant for this type but should be defined as "Weekday=0"
and "Reqtime=00:00".
8.3.2.4 Configure Start time
Type WEEKLY
Input: WeekDay=6
This input is only relevant for the Start type weekly. The week day will be indicated. Sunday
has the value 0, Monday the value 1 and Saturday the value 6. The inputs for hour and minute
are not relevant for the WEEKLY type but should be defined as 'Reqtime=00:00'. The app. is
started as soon as the correct weekday has been reached (starting at 00:00 hours) and the
day of the last start is not the actual day.
Type DAILY
Input: ReqTime=00:10
With the input the requested start time is configured. The time is indicated in hour:minute. The
app. is started as soon as the correct time has been reached and the day of the last start is
not the actual day.
Type HOURLY
Input: ReqTime=00:10
For the Start type 'hourly' the hour value is not relevant but should be defined in the range of
0-23. The app. is started as soon as the correct minute has been reached and the day/hour
of the last start does not match the actual time.
Administration
Scheduler
8.3.2.5 Exit application
Entry: ShutDown=1
You can set the switch to determine whether or not the started application is exited at the end
of the scheduler.
Administration
Appendix 9
9.1 Trace Server Diagnostics
9.1.1 General
The Trace server installed with BRAUMAT/SISTAR Classic V6.0 is not intended for use by
the operators, but rather as a special tool for purposes of detailed diagnostics to be carried
out by experts, e.g. commissioning personnel. Although the displayed information is complex,
it can be used for diagnostics as well as to quickly detect the cause of an error through the
Hotline. With some practice you can gain valuable information for the commissioning phase,
which is why the following chapter briefly explains this tool.
The Trace Server application always works locally rather than through the network. To run
diagnostics the application must therefore always be started on the processor, which contains
the application to be scanned.
9.1.2 Procedure
● Start the trace server via ...\windcs\sys\tracesvr.exe
● Maximize the window after the first startup to make it easier to manage.
– In the selection field choose one of the applications on which you would like to run the
diagnostics. The Trace Server will only display currently active applications, i.e.
applications currently stored in the main memory and registered with the Trace Server.
– Define the scope of messages to be displayed (diagnostics, information, warnings,
errors)
9.1.3 Meaning of display elements
Menu item Notes

PIN needle If selected, the Trace Server will always appear as the top application (topmost)
Trace Recording of events ("tracing") ON/OFF
Scroll Automatic scroll ON/OFF Switching on the "Scroll" function will ensure that the
latest events always appear at the bottom of the screen moving older events up.
File Recording of events in a file ON/OFF (Hotline, system control centers and
developers often ask for such a file to be forwarded to them in packed format ...)
Clear Delete export list
All Off Reset all module event types assigned, i.e.: stop logging
Administration
Appendix
9.1 Trace Server Diagnostics
Menu item Notes

[Combobox] Displays all modules that can deliver Trace outputs. You can select them
individually and use the following four buttons to assign the event types to be
monitored.
The first entry in the Combo box
<tracesvr [xxxx]> - <ALL [yyyy]>
allows you to address all modules at the same time
Diagnostics, Infos, Event types to be monitored
Warnings, Errors Note
Diagnostics levels 3 and 4 should not occur in normal operation (warnings, errors)
9.1.3.1 Module selection list

Displays the following information
Left: Name of application (EXE), as it appears in Task manager, including its process ID
Right: Name of module within the application
For example, if you have started up the "Plant overview" application (internally: seqctrl.exe),
the selection list will display all modules and libraries that are related to it and can be found in
the memory. You will see that "SEQCTRL" will load several other modules. You can configure
their monitoring individually. This is optional. If you are equally interested in all events of a
main module (here: SEQCTRL), you can use the sub-entry with the same name as the main
module (here: SEQCTRL [1824] – SEQCTRL).
9.1.3.2 Main list

A list of incoming Trace messages will be displayed in the top part of the main window.
9.1.3.3 Filter list

If the settings contain an entry for the filter list, a sub-list will appear in the lower part of the
main window. It contains filtered lines from the main list. This will allow you to detect rare Trace
messages immediately.
Click on a line in the filter list to automatically jump to the corresponding line in the main list.
9.1.3.4 Status line
Entry (left to right) Meaning

55 / 10000 Current/maximum number of
possible lines
44[0000] Bookmarked line [Event types
each ON/OFF: 1/0]
Administration
Appendix
9.2 Settings
Entry (left to right) Meaning

File: C:\WINDCS\tmp\TS021119.txt (max:0) Trace file currently in use
If you are saving in a file, this will
be the file the Support Service will
ask you to send to them in packed
format ...
Profile: USER Currently active profile (see
below)
IOS 1 19.11.02 09:56:54 (Superordinate information)
9.2 Settings
The setting options described in the following chapter provide the tool with flexibility in relation
to filter, bookmarking and trigger options. For example, you can highlight messages with a
particular string in color to make them easier to distinguish from other messages or even start
the process of a defined application.
You can open the configuration dialog by double-clicking or via the context menu in the
message window.
Administration
Appendix
9.2 Settings
Element 'General' section

Start / Close with PCU Server TraceSvr starts/stops automatically
Max. Lines Max. number of lines for display
Del Lines Number of lines to be deleted, when Max. Lines is reached
File Dir Path for saving Trace files. A new file is created for each day.
Administration
Appendix
9.2 Settings
Element 'General' section

ZIP-Format ZIP compression option during writing process.
Max. History Max. number of held Trace files. Older Trace files are deleted
automatically. If 0 is preset, no Trace files will be deleted.
Note: Depending on the filter settings, Trace files can become very
large if not ZIP compressed (1GB per day)!
Element 'Filter' section

Include sub strings If a message contains the string, the line will be recorded.
Exclude sub strings If a message contains the string, the line will be discarded.
Filter list If a message contains the string, the line will be displayed in a sub-
window.
Element 'Highlight/Bookmark/Trigger’ section
Highlight sub strings If a message contains the strings 'Telegram' or 'PCU', the line will
be highlighted in color.
Bookmark In addition to 'Highlight', 'Bookmark' will also make it easier to find
particular items.
Trigger sub strings If a message contains the string, the following options will be carried
out.
Stop Scroll Trigger: Switch off 'Scroll' to ensure that the message remains
visible.
Stop Trace Trigger: Switch off Trace
Stop File Trigger: Switch off writing to file
Execute Trigger: Execute specified action, e.g. send message to another
processor via batch.
Once Carry out 'Execute action' only for the first trigger
Test Carry out 'Execute action' immediately for test purposes
All Filter/Highlight/Trigger strings:

● Several strings may be entered separated by a semicolon.
● Case sensitive!
Element Selected Message

Currently selected Trace entry to be copied and inserted as filter
text.
9.2.1 Trace Server: Profile

You can save all settings for modules and their events, as well as your chosen filters in a
"Profile" and load this profile when required. Right-clicking will guide you to the appropriate
menu (position is irrelevant). All menu entries are largely self-explanatory.
Administration
Appendix
9.2 Settings
9.2.2 Trace Viewer (TRACEVWR.EXE)

This tool is very similar to the Trace server described above. The only difference is that it cannot
perform Trace recordings, but only load recorded Trace files. Accordingly, the above-
mentioned buttons in relation to recording options (Trace, Scroll, All Off, Diagnostics, Infos,
Warnings, Errors) are deactivated.
To ensure efficient browsing of trace files, the start and end time for the required messages
can be specified when opening the tool.
Element 'File' section

Total size Size of the entire Trace file
Total time Timeframe for all included Trace entries
Select time Timeframe for required Trace entries You can also enter a partial
string
File Type The Trace Viewer can also display message archives and old PCU
Server Traces. The type must be right for these details to be
displayed in the right format. However, usually it will be determined
automatically on the basis of the file name. If this fails, e.g. because
the file name was changed, it can be entered manually.
Element Change Filter Settings
If this option is selected, a filter dialog will appear even before the
Trace lines are imported.
Note
You can branch off to the Trace Viewer by using the context menu in the Trace Server. The
current Trace file (if it has been saved before) will load automatically and will be displayed
with the last valid filter settings.
Administration

BRAUMAT-SISTAR Classic Administration (Function Manual)

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BRAUMAT-SISTAR Classic Administration (Function Manual)

Transféré par

Droits d'auteur :

Formats disponibles

Preface 1

BRAUMAT/SISTAR Classic V6.0 SP2

Siemens AG A5E00239375-09 Copyright © Siemens AG 2012.

7.3 Working with the application........................................................................................................42

Where is this manual valid?

Place of this Documentation in the Information Environment

Service & Support on the Internet

The Client Area is divided into two areas:

● For the plant operation

2.2 Working with the application

Selection 'Basic Menu'

Selection of different applications

2.3.1 Register of the Application

2.3.2 Selection of the application with password check

App3=message archive;passwchk.exe 255 List of individual applications

2.3.3 Application call via Menu bar > 'Program'

3.4 Engineering language

Dynamic Engineering language setting

User Group Short Name Level Actions (Example) )

4.2 User Query

Create new user/Change user definition

Reset the password/Logout

Adjust program level

Program Function Description Level

Program Function Description Level

Program Function Description Level

Program Function Description Level

Further information on password functions of specific Braumat Controls (OCX):

UnitCtrl.ocx: KETTE_STA=1 Start sequencer/unit and quit rest

UnitCtrl.ocx: KETTE_STA=1 Start sequencer/unit and quit rest

4.3 Code Card Reader

5.2 Automatic delete function, if the hard disk is full

5.3 Archive Manager

5.3.2 Working with the application

Menu item Program:

Menu item functions:

Menu item 'Options':

[TAB<Nr>] Number of the Archive type

[TAB<Nr>] Number of the Archive type

Section Path/File structure

Section Path/File structure

Section Path/File structure

5.3.4 MultiClient functionality

Table 5-1 Example:

start on source path path on export drive

6.2 Client Area

6.3 Working with the application

Create new transfer list

Open transfer list

File transfer list

Edit transfer list

Options -> Settings

● Error handling -> Blocks not found

6.4 Starting automatic block transfer at the command line prompt

7.2 Client Area

7.3 Working with the application

7.3.1 Working with the application

7.3.2 Application call with parameter:

Run with definition file: /def

Delete the file ‘notsync.ini: /u

7.3.3 Call without parameter

Call via input in 'sys.ini'

Path and files Search depths*) Disk drives**)

j:\winbrau PCU.001 NAME.TXT older c:\windcs j:\winbrau PCU.001