14 Logging e

Preface, Content
System logs
1
Free definable logs
SIMATIC 2
Creating free protocols based on
Stepping logs 3
Automation system Step logging
4
BRAUMAT/SISTARClassic V5.3
Logging of user operations
Logging 5
What to do on errors?
Manual 6
This manual is part of the documentation

package with the order number:
6FD7680-0PH03
Edition 11/2007
A5E00239388-04
Safety Guidelines
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring to property damage only have no safety alert symbol. The notices shown below are
graded according to the degree of danger.
Danger
! indicates that death or severe personal injury will result if proper precautions are not taken.
Warning
! indicates that death or severe personal injury may result if proper precautions are not taken.
Caution
! with a safety alert symbol indicates that minor personal injury can result if proper precautions are not
taken.
Caution
without a safety alert symbol indicates that property damage can result if proper precautions are not
taken.
Attention
indicates that an unintended result or situation can occur if the corresponding notice is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning and
operation of a device/system may only be performed by qualified personnel. Within the context of the safety
notices in this documentation qualified persons are defined as persons who are authorized to commission,
ground and label devices, systems and circuits in accordance with established safety practices and standards.
Prescribed Usage
Note the following:
Warning
! This device and its components may only be used for the applications described in the catalog or the
technical description, and only in connection with devices or components from other manufacturers
which have been approved or recommended by Siemens.
Correct, reliable operation of the product requires proper transport, storage, positioning and assembly
as well as careful operation and maintenance.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG.
The remaining trademarks in this publication may be trademarks whose use by third parties for their own
purposes could violate the rights of the owner.
Copyright Siemens AG 2007 All rights reserved Disclaimer of Liability

The distribution and duplication of this document or the utilization We have reviewed the contents of this publication to ensure
and transmission of its contents are not permitted without express consistency with the hardware and software described. Since
written permission. Offenders will be liable for damages. All rights, variance cannot be precluded entirely, we cannot guarantee full
including rights created by patent grant or registration of a utility consistency. However, the information in this publication is reviewed
model or design, are reserved regularly and any necessary corrections are included in subsequent
editions.
Siemens AG
Automation and Drives
Postfach 4848, D- 90327 Nuernberg, Germany ©Siemens AG 2007
Technical data subject to change.
Siemens Aktiengesellschaft A5E00239388-04
Preface
Purpose of the Manual
This manual describes the logging with BRAUMAT/SISTAR Classic V5.3 and gives you an
overview of the following topics:
¾ system logs
¾ step logs
¾ free definable logs
¾ create free definable logs based on stepping logs
¾ changes log
This manual is intended for those responsible for configuring, commissioning and servicing
automation systems.
Required Basic Knowledge
You require a general knowledge in the field of automation engineering to be able to

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

from Version V5.3 SP2.
The offered electronic manual is most largely identical with the contents of the on-line help.
Due to a technically necessary editorial deadline for the generation of electronic manuals
occasionally smaller deviations can give up opposite the on-line helps.
The statements in the on-line helps are primary to those of the manual.
Place of this Documentation in the Information Environment
This manual forms part of the BRAUMAT/SISTAR Classic V5.3 documentation package.
The following schematic of the document architecture show the individual manuals as well
as their thematic grouping within the entire program package
BRAUMAT/SISTAR Classic V5.3 iii

Logging
A5E00239388-04
Document Structure
Description of the
System Installation and
Configuration
Administration
Communication
Engineering Recipe System

'based on S7'
EPE-creation
Batch-
processing
Dosing and Serve & Watch

Weigher 'based on S7'
Operation &
Control batches
Application for
Batch curves 'based on S7'
Logging Message
Building block Building block

library : library: Route
Basics Control
Building block Serve & Watch

description S7 Routes
Building block
description S5 Engineering of the
Route Control
iv BRAUMAT/SISTAR Classic V5.3

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

Logging
A5E00239388-04
Technical Support
You can reach the Technical Support for all A&D products
• Via the Web formula for the Support Request
http://www.siemens.com/automation/support-request
• Phone: + 49 180 5050 222
• Fax: + 49 180 5050 223
Additional information about our Technical Support can be found on the Internet pages
http://www.siemens.com/automation/service
Service & Support on the Internet

In addition to our documentation, we offer our Know-how online on the internet at:
http://www.siemens.com/automation/service&support
where you will find the following:
• The newsletter, which constantly provides you with up-to-date information on your
products.
• The right documents via our Search function in Service & Support.
• A forum, where users and experts from all over the world exchange their experiences.
• Your local representative for Automation & Drives.
• Information on field service, repairs, spare parts and more under "Services".
vi BRAUMAT/SISTAR Classic V5.3

Logging
A5E00239388-04
Content
1 System logs 1-1
1.1 General ...................................................................................................1-1
1.2 Recipe log ...............................................................................................1-1
1.3 Stepping log ............................................................................................1-2
1.4 Parameterization log ...............................................................................1-3
1.5 Order log .................................................................................................1-3
1.6 Message archive log ...............................................................................1-3
1.7 Curve archive log ....................................................................................1-3
1.8 Curve input log........................................................................................1-4
1.9 Maintenance log......................................................................................1-4
1.10 Report footer ...........................................................................................1-4
1.11 Printer......................................................................................................1-5
2 Free definable logs 2-1
2.1 PCU S5 vs. PCU S7 ...............................................................................2-1
2.1.1 Different addresses and parameters ..........................................2-1
2.1.2 Different functionality ..................................................................2-2
2.2 Parameterization in the plc .....................................................................2-3
2.2.1 Telegram structure (plc Æ IOS) and sending.............................2-3
2.3 Required blocks within the plc`s .............................................................2-4
2.3.1 instance data blocks DB<FREE DEF. LOG) ..............................2-4
2.3.2 FB<FREE DEF. LOG > ..............................................................2-4
2.3.3 DB<temp. buffer> .......................................................................2-4
2.4 Parameterization of the FB<FREE DEF. LOG> .....................................2-4
2.5 Examples for logging batch data ............................................................2-8
2.6 Error messages and return values........................................................2-12
2.6.1 Error messages ........................................................................2-12
2.7 Parameterization in the IOS..................................................................2-14
2.7.1 Archive configuration (Def-File) 'receive data'..........................2-14
2.7.2 Description file syntax...............................................................2-14
2.8 Examples ..............................................................................................2-17
2.8.1 Engineering in the plc ...............................................................2-17
2.8.2 Engineering in the IOS .............................................................2-17
2.9 Files and folders....................................................................................2-20
2.9.1 Standard - Configuration (monthly - archives)..........................2-20
2.9.2 Structure of a yearly archive.....................................................2-20
2.9.3 Order/Batch Archive – Structure ..............................................2-20
2.10 Engineering of the search path .............................................................2-22
2.10.1 Examples from PROTDIDA.TXT (in state of delivery) ...........2-23
2.11 Copy archive .........................................................................................2-26
2.11.1 Structure of a DEF file ............................................................2-26
2.11.2 User data description..............................................................2-26
2.11.3 Example of copying data ........................................................2-27
2.11.4 Copy archive folder.................................................................2-27
2.11.5 Programming the copy archive...............................................2-27
2.12 "Free Protocols" application for visualization and evaluation ...............2-29
2.12.1 Installation...............................................................................2-29
2.12.2 Working with the application...................................................2-30
2.13 Summary...............................................................................................2-33
3 Creating free protocols based on Stepping logs 3-1
BRAUMAT/SISTAR Classic V5.3 vii
Logging
A5E00239388-04
3.1 General................................................................................................... 3-1
3.2 Filter criteria............................................................................................ 3-1
3.3 Installation .............................................................................................. 3-1
3.4 Necessary files ....................................................................................... 3-2
3.4.1 Structure of the filter table GENFRPR.DBF ............................... 3-2
3.4.2 Assignment table PCU/Unit to recipe type number ................... 3-4
3.5 Diagnostic feature................................................................................... 3-5
3.6 Examples................................................................................................ 3-8
3.7 Picture showing the interaction ............................................................ 3-10
4 Step logging 4-1
4.1 Overview................................................................................................. 4-1
4.2 'Step logging' program............................................................................ 4-1
4.2.1 Functionality ............................................................................... 4-1
4.2.2 Working with the program .......................................................... 4-2
5 Logging of user operations 5-1
5.1 Overview................................................................................................. 5-1
5.2 client functionality ................................................................................... 5-3
5.3 Server functionality ................................................................................. 5-3
5.3.1 Configuration of the unit history ................................................. 5-4
5.3.2 Configuration of the server function ........................................... 5-4
5.4 Which changes are recorded ? .............................................................. 5-6
5.5 Structure of the files................................................................................ 5-8
5.5.1 Columns of the log files.............................................................. 5-8
5.5.2 Columns of the units history....................................................... 5-9
5.6 Application ‘Change archive’ .................................................................. 5-9
5.6.1 Selection .................................................................................... 5-9
5.6.2 Selection of columns ................................................................ 5-10
5.6.3 Printing ..................................................................................... 5-11
5.7 Logging the last most significant recipe modifications ......................... 5-11
6 What to do on errors? 6-1
6.1 General................................................................................................... 6-1
viii BRAUMAT/SISTAR Classic V5.3

Logging
A5E00239388-04
System logs
1 System logs
1.1 General
The process control system supports system logs, where the following ones are included in
the system delivery:
¾ Recipe log
¾ Stepping log
¾ Parameterization log
¾ Order system log
¾ Message archive log
¾ Curve archive log
¾ Curve input log
¾ Maintenance log
¾ Changes log
1.2 Recipe log

In the "Recipe editor" program, you can select the recipe elements and their layout for
output to the printer.
Recipe overview window:
Outputs the master recipe list

Master recipe window
After you have selected and enabled a master recipe, you can output the following lists to
the printer:
¾ Process parameters list
¾ Process input list
Recipe procedure window
After you have opened the recipe procedure, you can output the following information to the
printer:
¾ The recipe procedure diagram with optiosn for selecting:
- the current size
- the complete recipe procedure on one page
- Poster print
BRAUMAT/SISTAR Classic V5.3 1-1
Logging
A5E00239388-04
System logs
¾ RUP lists with options for selecting

- the current recipe unit procedure
- all RUPs of the recipe procedure
1.3 Stepping log

A stepping log is put out onto the printer.
You can do the printing:
¾ triggered by a unit operation (from plc)
¾ through the user directly
Print-out triggered by a unit operation:
In order to initiate the automatic print-out of the stepping log at the end of a technological
sequence (after the last unit operation), the flag M 101.2 must be set to 1 within this last unit
operation.
Print-out through the user:
The user can start printing out a stepping log after selecting (application ‘stepping log’):
¾ year
¾ recipe type
¾ order number
¾ batch number
¾ unit
The selected stepping log is shown on the screen and via 'file, print' the user has two
possibilities:
¾ print log for the selected unit only
¾ print log for all units
Note:
The stepping logs are stored on a IOS (server) only if the datagram type 5 is configured for
FIFOs related to this IOS.
Via the application 'parameterization, FIFO’, the stepping log can be dis- or enabled.
In addition the user can enable or disable the logging of a certain step (basic operation) by
setting the flag M 102.5 to 1 (disable) or 0 (enable). These unit operations do not appear in
no stepping log.
1-2 BRAUMAT/SISTAR Classic V5.3

Logging
A5E00239388-04
System logs
1.4 Parameterization log

The parameterization (a setting) is logged on the printer.
application ‘parameterization‘:
In the application 'parameterization' a record is opened via the selection of the plc and the
object class. This record set is shown on the display. With 'file, printing' the user can select,
what to print:
¾ print all data sets (records)
¾ current record
¾ range ‚record from ... to ...’
application ‘text parameterization’:
Within the application 'text parameterization' we have two types of text lists:
¾ global text lists (plc independent)
¾ plc related text lists
After selecting ‚global' or a plc related text file, it is shown on the screen. Via ‘file, print’ a
dialog appears where two kinds of printouts can be selected::
¾ current file (means whole list)
¾ current range
1.5 Order log

After calling the application ‘order system’ and selecting the order list or the batch list it can
be printed out via ‘file, print’. A dialog appears where the user can select between three
types of log prints:
¾ current view
¾ table on one page
¾ entire table
1.6 Message archive log

In the application 'message archive' the user can open the log of a certain day. Via
‘selection’ a filter can be applied.
Via 'function, print' the current view is printed out.
1.7 Curve archive log

Via the application 'PI-curves' the user can select one of three archive types:
¾ short term archive
¾ batch archive
¾ weekly archive
The curve chosen from an archive and displayed at the screen can be printed out about 'file,
printing'.

Logging
A5E00239388-04
System logs
1.8 Curve input log

After selecting a curve via
¾ group number and
¾ curve number
the curve is shown on the screen and can via 'file, print table' to be logged on the printer.
1.9 Maintenance log

In the application 'maintenance data' the group is selected. Via ‘file, print’ a dialog appears
where the user can select some printing options:
page content
(Actual value, set point value, indication IW>SW, finished yes/no, short text, long text)
filter
(no filter, pending jobs, done jobs)
Records
(all, range from ... to ...)
1.10 Report footer

For all possible report printouts footer files exist containing plant-dependent textstrings.
These can be modified via the application 'text parameterization', global texts.
Note:
Another possibilty is the modification via a shareware text editor like ‘Ultra Edit’. In this case
the identical textstrings for ‘customer’ and ‘plant’ may be replaced commonly for all files with
one ‘Search/Replace in files’ command.
Global footer definition files in folders ‘…\windcs\texte.x’:
File Description
ARCH_FRM Footer for printing curve archives
BALIFRM Footer for printing order system
BRGRFRM Footer for printing recipe procedures
BRLIFRM Footer for printing of RUP lists
DATACONN_FRM Footer for printing graphical source views
KURVFRM Footer for printing input curves
MAINTFRM Footer for printing maintenance data
MELDFRM1 Footer for printing message logs
PARAMFRM Footer for printing of parameterization data records
PTXTFRM Footer for printing of text parameterization data
RECCLFRM Footer for printing the process input list of recipes
RECIOFRM Footer for printing the process input list of one batch job
RECMAFRM Footer for printing process parameters
RECOVFRM Footer for printing recipe overviews
SRPROTFR Footer for printing stepping logs

Logging
A5E00239388-04
System logs
1.11 Printer
One printer can be installed per IOS according to the operating system WINDOWS NT.

Logging
A5E00239388-04
Free definable logs
2 Free definable logs
2.1 PCU S5 vs. PCU S7

The following table shows the functionality and addressing of the two plc types. The
descriptions below always refer to the addresses in the most left column
‘address/parameter’.
2.1.1 Different addresses and parameters

Parameters S5 block parameters S7 block parameters
FB<Free def. logs> FB 80 FB 580
DB<Free def. logs > DB 186 DB 580
DB<temp. buffer> DB 17* DB 581
Calling range 1 Writing data at the call FB80 Writing data at the call FB580
from OB1 from OB1
Calling range 2 Writing data at the call FB80 Writing data at the call FB580
from OB10 from OB3x
system blocks for example DB225, DB100, for example DB725, DB600,
DB221 DB721 and so on
Starting DW using indirect DW130 DBW148
parameterization
Error code DB186, starting at DW40 DB581, starting at DBW12
Parameter
sub datagram number TTNR iPartTeleNr;
DB186, DW130, KF DB580.DBW148, INT
Batch number CHNR; iBatch;
Order number ATNR iOrder;
Recipe number RPNR iRecipe;
Recipe type RTNR iRecType;
Identification for OB WHETHER not used as the FB580
DB186, DW135, KF recognizes itself by what OB it
has been called

Logging
A5E00239388-04
Free definable logs
Identification for block transfer ( W-NR iDataDest;

and/or target data word) DB186, DW136, KF DB580.DBW158, INT
0 - 4 possible 1 - 5 possible
Calling type ART iFunction;
ANA ANA iANA;
Floating-point number DD rRealInput;
DB186, DD139, KG DB580.DBD164, REAL
Data block TYNR iDBNr;
Data word ( and/or start date DWNR iStartDW;
word at block transfer) DB186, DW142, KF DB580.DBW170, INT
Return value VKE 0/1 BoRetVal
DB186 DW40 DB581 DBW12
2.1.2 Different functionality

Functionality Versions with Versions with
Simatic S5 Simatic S7
Calling type ART = 29, 30 and 31: not existing as a S7 does not
loading of S-flags know any S-flags; the definition
range for flags is MB0 ... MB
2047
if the FB580 with a parameter
value 'iFunction' is called
between 1 and 11, the DW 1 up
to 5 is selectable via the
parameter 'iDataDest'
iFunction == 12 (Date) also the
day of the week is coded: 1 =
sunday

Logging
A5E00239388-04
Free definable logs
2.2 Parameterization in the plc
2.2.1 Telegram structure (plc Æ IOS) and sending

The FB<Free def. log> assembles a telegram being sent to the servers which contains the
following information:
Telegram- DB<Fr.Prot.> DB<Fr.Prot.> DB

structure Calling range 1 Calling range 2 <temp.-buffer>
S5 / S7 S5 / S7 S5 / S7
Telegram length - / DBW 50 - / DBW 100 - / DBW 300
Tele. plc-no. DW1 / DBW 52 DW21 / DBW 102 DW50 / DBW 302
type
Year Month DW2 / DBW 54 DW22 / DBW 104 DW51 / DBW 304
Day Hour DW3 / DBW 56 DW23 / DBW 106 DW52 / DBW 306
Minute Second DW4 / DBW 58 DW24 / DBW 108 DW53 / DBW 308
Milliseconds - / DBW 60 - / DBW 110 - / DBW 310
Recipe Recipe DW5 / DBW 62 DW25 / DBW 112 DW54 / DBW 312
year type
recipe number DW6 / DBW 64 DW26 / DBW 114 DW55 / DBW 314
order number DW7 / DBW 66 DW27 / DBW 116 DW56 / DBW 316
batch number DW8 / DBW 68 DW28 / DBW 118 DW57 / DBW 318
sub data gram DW9 / DBW 70 DW29 / DBW 120 DW58 / DBW 320
number
user data 1 DW10 / DBW 72 DW30 / DBW 122 DW59 / DBW 322
Depending on the call to the FB<FREE DEF. LOG > the telegram is assembled and stored
to the calling ranges 1 or 2 according to calling type. At the end of the block the
corresponding user data is transferred into the temp. buffer. After at most 5 user data words
are collected, all data is written into a FIFO through a call to the FB<FREE DEF. LOG>
(where type = 0) and sent to the server (IOS). Data gram type 6 has to be configured before
for this FIFO.
The parameters shown in gray back color in the table above are updated by the system
when a datagram is sent and must not be modified by the user.
On the hard disk of a IOS a dBASE file is created after arrival of the telegram. Depending on
the date and the recipe type the server (PROT_006.DLL) creates the folder and file name.
According to the order and batch number one record is created.
The definition file (FEPR_<Rezepttypnr.>.DEF) provides the structure of the dBASE files
and where the user data is written to (offset within the record). Data set elements
corresponding sub data gram number are written, all other ones remain unconsidered.

Logging
A5E00239388-04
Free definable logs
2.3 Required blocks within the plc`s
2.3.1 instance data blocks DB<FREE DEF. LOG)

This block is the instance data block of the FB<FREE DEF. LOG>. It is used in its original
release version.
2.3.2 FB<FREE DEF. LOG >

Collecting and temporary storaging of batch data
The FB<FREE DEF. LOG> is the most import part for collecting batch data in the plc. It
must be called by the user within procedures.
The FB is used transferring the batch data from the users program to the PI-system.
Furthermore the user can end currently active batch archives and initiate a datagram to the
server. Which actions the FB is supposed to carry out, is given via a parameter list.
The FB does the storing of a datagram into the FIFO, too.
2.3.3 DB<temp. buffer>

Up to 5 user data words are stored temporarily here, before they are moved to the FIFO and
sent to the server via FB<FREE DEF. LOG> by calling it with (Aufruf-Art / type= 0).
2.4 Parameterization of the FB<FREE DEF. LOG>

Important:
Many of the calling methods shown below are useful only if we use a complete system since
system blocks are called inside: (refer to ‘system blocks‘)
Using indirect parameterization ( calling type = -1) the parameters are fetched from the
instance DB<FREE DEF. LOG>.
The following table indicates the available range of the parameters. Below the parameter
names the corresponding DW-Nr of the instance DB<FREE DEF. LOG> is given.
Parameter list of the FB<FREE DEF. LOG>:
Parameter Description
sub sub data gram number
data gram -4: The corresponding record with order number / batch number is reset
number (texts are overwritten with blanks, numbers set to 0).
S5: -3: The corresponding record with order number / batch number is transferred
TTNR into the corresponding copy archive (same recipe type).
S7: iPartTeleNr -2: end of a batch, only the sub data gram number the telegram is used.
-1: only the time of the datagram is read by the IOS.
0: all data of the telegram is read and written into the database record
1 - n: sub datagram number; writing posiion within the dBASE file depends on
the corresponding definition file (*.DEF).

Logging
A5E00239388-04
Free definable logs
batch number Identification for origin of the parameters or batch number

< 0: The indicated value corresponds to the sequence number, recipe number,
recipe type, order number and batch number of this unit is used.
= 0: recipe number, recipe type, order number and batch number of the current
unit is used.
> 0: recipe number, recipe type, order number and batch number are given as
input parameters of the function call (iBatch, iOrder, iRecipe, iRecType).
order number order number
Direct order number information
recipe number recipe number
Direct information recipe number
recipe type recipe type
Direct recipe model information
Identification of Identification of the OB (only important for SIMATIC S5)
OB = 1: Call from OB1
<> 1: Call from OB10
Identification Identification for block transfer and/or destination data word:
for block -1: If iFunction equals 7 the whole block of 5 data words is copied into the
transfer telegram.
No.: Into this destination data word within the telegram the determined value is
transferred.
calling type INT: Function of the FB<FREE DEF. LOG>
Type, origin and destination of the data to be sent is given by this parameter. The
next table describes this parameter in detail.
ANA According to the type (Art), ANA is interpreted as value or index of a DFM. With
'calling type’ = 9, ANA is interpreted as a value and is moved into the destination
address given by the parameter 'identification for block transfer'. With 'calling type'
= 1 or 'calling type' = 2, 'ANA' is used as index of a DFM.
floating point Floating point number
number Direct input of a real value, used with 'calling type’= 11
(not reasonably for dBASE archives, therefore do not used normally)
data block data block
'calling type’= 7:
The word addresses the block number where the data is read.
data word data word and/or starting offset for block transfer
and/or starting 'calling type' = 7:
address for Number (address) of the data word from which the value is supposed to be read.
block transfer
'calling type' = 7 and 'identification for block transfer' = -1:
address (offset) where 5 data words are supposed to be read.
methods for calling the FB<FREE DEF. LOG> :
calling type Description

= -1: Indirect parameterization; Parameters are located at DB<FREE DEF. LOG> at
address ‘starting-DW’
= 0: Setting the ‘end’ flag of a datagram. The data is moved into the FIFO and sent to
one or more server.

Logging
A5E00239388-04
Free definable logs
= 1: Reading the actual value (double-word) of the DFM-module with the index
(number) given by ‘ANA’:
001 ... 255 : DFM-group 0
257 ... 511 : DFM-group 1
513 ... 767 : DFM-group 2
769...1023 : DFM-group 3
The parameter 'identification for block transfer' indicates the offset (start address)
DW (1...5) within a telegram.
= 2: Reading the set point value (Double-word).
please refer to 'calling type' = 1.
= 3: Reading the actual value (double-word) of a DFM-module of the corresponding
unit with the relative number (1...13) given by the identifier 'ANA'. The parameter
'identification for block transfer' provides the offset of the DW (1...5) within the
telegram.
= 4: Reading of the set point value (double-word).
please refer to 'calling type' = 3.
= 5: not used
= 6: Reading the actual value of the block MESS addressed by the identifier 'ANA'. The
parameter 'identification for block transfer' addresses the offset of a DW (1...5)
within the telegram.
= 7: Loading a word from a DB. For Block number and DW number (address) see
parameter 'data block' and 'data word'. The parameter 'identification for block
transfer' addresses the beginning (DW) within the telegram.
= 8: not used.
= 9: Loading a word from identifier 'ANA'.
Here 'ANA' is not interpreted as a DFM number (index), but as a user defined
value. The parameter 'identification for block transfer' addresses the offest DW
= 10: not used
= 11: Loading a double-word addressed by the identifier 'floating-point number'. The
parameter 'identification for block transfer' indicates the address (offset) DW (1...5)
(not reasonably for dBASE archives, therefore don’t use)
= 12: Loading the data of the real-time clock of the plc S7-400;
Format: month, day, day of the week (1 = sunday), year;
the dates are always located in the 1st and 2nd DBW in the telegram.
= 13: Loading the time from the real-time clock of the plc S7-400; Format: minute, hour,
0, second;
the dates are always located in the 1st and 2nd DBW in the telegram.
= 14 - 19: not used
= 20 Loading an input byte addressed by the identifier 'ANA'.
= 21 Loading an input word addressed by the identifier 'ANA'.
= 22 Loading an input double word addressed by the identifier 'ANA'.
= 23 Loading an output byte addressed by the identifier 'ANA'.
= 24 Loading an output word addressed by the identifier 'ANA'.
= 25 Loading an output double word addressed by the identifier 'ANA'.
= 26 Loading a flag byte addressed by the identifier 'ANA'.
= 27 Loading a flag word addressed by the identifier 'ANA'.
= 28 Loading a flag double word addressed by the identifier 'ANA'.

Logging
A5E00239388-04
Free definable logs
= 32 Loading a time value (BCD, time base and value) addressed by the identifier
'ANA'.
= 33 Loading a counter value (BCD) addressed by the identifier 'ANA'.
= 34 - 98: not used
= 99 Initialization of the temporary entry (DB<FREE DEF. LOG>) and the temp. buffer
(DB<FREE DEF. LOG>) with zero.

Logging
A5E00239388-04
Free definable logs
2.5 Examples for logging batch data

The following examples are exclusively for programming under SIMATIC S7.
The calls of the FB are made from within the procedures. The call can directly or
symbolically. In the table the direct call is given, the symbolic call is as follows:
Call "FREE_PROT_FB", "FREE_PROT".
Call FB 580 function 7
In this example, five data words of DB300, i.e. DBW10, DBW12, DBW14, DBW16 and
DBW18 are copied to DB580 for datagram element 1.
Parameter interface values description

: U M x.y; the block can be called only directly
: BEB; Call...(S7); SPA...(S5)
: Call FB 580, DB580; Taking over the date for batch start
iPartTeleNr := 1
iBatch := 0 Batch dates are taken from current record
iOrder := 0
iRecipe := 0
iRecTyp := 0
iDataDest := -1 transfer block of 5 data word
iFunction := 7 iFunction = 7, that is load block data word block with
time
iANA := 0 all other identifiers are ignored
rRealInput := 0.000000e+00
iDBNr := 300 Date is located in DB300, format: (year, month, day,
hour, minute, second)
iStartDW := 10 Date is located at DBW10,12 and 14
boRetVal :=M a.b Error return value;
0: no error
1: Error
In this example, the DFM process value of DFM4 is copied from DFM group 0 to user data 3
and 4 of DB580.
DFM 0/ 4 process value DB580
DB736 DBW366 and DBW367 DBW126 and 128 or DBW326 and 328
: U M x.y;
: BEB;
: Call FB 580, DB580; Tyke over malt quantity from DFM groats flowmeter
iPartTeleNr := 1
iBatch := 0 Batch data is taken from current record
iOrder := 0
iRecipe := 0
iRecTyp := 0
Logging
A5E00239388-04
Free definable logs
iDataDest := 3 the target data words in the telegram are located at

address 3..DW and 4.DW
iFunction := 1 iFunction = 1, that is read the actual value (double-
word !) from the DFM-module addressed by the
parameter 'ANA'
iANA := 4 Take actual value from DFM-Nr 4
rRealInput := 0.000000e+00 all other identifiers are ignored
iDBNr := 0
iStartDW := 0
0: no error;
1: Error
In this example, the DFM setpoint of DFM3 is copied from DFM group 0 to user data 1 and 2
of DB580.
DFM 0/ 3 setpoint DB580
DB736 DBW342 and DBW344 DBW122 and 124 or DBW322 und 324
Parameter interface values Description

: U M x.y;
: BEB;
: Call FB 580, DB580; Malt quantity from unit groats load
iPartTeleNr := 1
iBatch := 0 Batch data is taken from current record
iOrder := 0
iRecipe := 0
iRecTyp := 0
iDataDest := 1 the target data words within the telegram are at
address 1.DW and 2.DW
iFunction := 4 iFunction = 4, that is loading the set point value
(double-word !) from the TA (unit)-module with the
relative number addressed by the parameter 'ANA'
iANA := 3 Read the set point value from the DFM-module which
is addressed within the unit as the 3rd DFM-module
rRealInput := 0.000000e+00 all other identifiers are ignored
iDBNr := 0
iStartDW := 0
0: no error;
1: Error

Logging
A5E00239388-04
Free definable logs
In this example, the value (2) of parameter ANA is copied to user data 1 of DB580.
Parameter ANA DB580
2 DBW122 or DBW322

: U M x.y;
: BEB;
: Call FB 580, DB580; Taking the number of the WPF (Würzepfanne / wort
settler) used for heating
IPartTeleNr := 1
IBatch := 0 Batch data is taken from the current record
IOrder := 0
IRecipe := 0
IRecTyp := 0
IDataDest := 1 the target data word in the telegram is the 1.DW
IFunction := 9 iFunction = 9, load a value from the parameter 'ANA'
IANA := 2 Value to be loaded
RRealInput := 0.000000e+00 all other identifiers are ignored
IDBNr := 0
IStartDW := 0
BoRetVal :=M a.b Error returned value;
0: no error;
1: Error
In this example, the five data words DBW10, DBW12, DBW14, DBW16 and DBW18are
copied from DB100 to datagram element 1.

: U M x.y;
: BEB;
: Call FB 580, DB580; read data block from DB
iPartTeleNr := 1
iBatch := 12345
iOrder := 12
iRecipe := 1
iRecTyp := 1
iDataDest := -1 Transferring data word block
iFunction := 7 iFunction = 7, that is copy a block of 5 data words
into the telegram
iANA := 0
rRealInput := 0.000000e+00

Logging
A5E00239388-04
Free definable logs
iDBNr := 100 from DB100

iStartDW := 10 from DBW 10 to DBW 18
(Caution: S7 is byte oriented !)
boRetVal :=M a.b Error returned value;
0: no error;
1: Error
In this example, datagram element 1 is transmitted as datagram 6. The data to be sent must
be available in DB580 prior to the call. The folder and file names are based on the year, the
month and the recipe type.

: U M x.y;
: BEB;
: Call FB 580, DB580; Sending data block to the server
IPartTeleNr := 1
IBatch := 0
IOrder := 0
IRecipe := 0
IRecTyp := 0
IDataDest := 0
IFunction := iFunction = 0, set ‘end’ flag for the batch
IANA := 0
IRealInput := 0.000000e+00
IDBNr := 0
IStartDW := 0
0: no error;
1: Error

Logging
A5E00239388-04
Free definable logs
2.6 Error messages and return values
2.6.1 Error messages

In order to easier locate the fault localization with the parameterization of the identifiers, the
FB<FREE DEF. LOG> returns the last error of DB<FREE DEF. LOG>.
Error codes working with a SIMATIC S5
The error code is returned by the FB80 via DB186, DW40. Additional information is returned
via AKKU1 and AKKU2.
Error code declaration

FE01 DB not available
FE02 Common error (please refer to error code AKKU2)
FE03 DB too short
Error code AKKU2 and/or DB186, DW40:
1 'CHNR' exceeds the number of units available
2 called with 'CHNR' = 0,
Æ not called from a running procedure
3 DFM-Nr exceeds number of DFMs
4 Mess-Nr exceeds number of MESS
5 FIFO occupied
6 'W-NR' out of of the valid range
7 'CHNR' > 0 not allowed (invalid)
8 DFM-Nr not allowed (invalid)
Return parameter of the declaration

FB<FREE DEF. LOG>
0: no error occurred
1: an error occurred, explained in detail in DB186, DW40
Error code working with a SIMATIC S7
The error code consists of 2 bytes in a hexadecimal format. The calling type indicates the
first byte, the second byte is a continuous number within calling type (sub type).
Error code DB581.DBW12:
Error with error code. declaration
calling type= xy
(DBB13,
(DBB12, hexadecimal)
hexadecimal)
01 or 07 01 DB not available or too short
Xy 02
FF 03 no data exists in the data words
1 to 5
FF 04 Error writing data into FIFO

Logging
A5E00239388-04
Free definable logs
01, 03, 06, 07, 09 or 11 05 the temp. buffer is full; Data

with calling type= 0
00 10 'iBatch' exceeds number of

units
03 21 'iBatch' > 0 is invalid with calling
type = 3 or = 4
01 30 DFM-Nr exceeds number of
DFMs
06 40 Mess-Nr exceeds the number
of MESS
03 50 Error at recipe data block: too
few steps
03 51 'ANA' exceeds number of DFM
in the unit
03 52 'ANA' out of the valid range or
'ANA' <= 0
Xy 60
Xy 70
Xy 80
01, 03, 06, 07, 09 or 11 90 'Identification for block transfer'
out of the valid range:
'Identification for block transfer'
>5
01, 03, 06, 07, 09 or 11 91 'Identification for block transfer'
<= 0
01, 03 or 11 92 'Identification for block transfer'
== 5
Return parameter ‘boRetVal‘ of the FB<FREE DEF. LOG>
Return parameter of the declaration

FB<FREE DEF. LOG>
BoRetVal 0: no error occurred
1: an error which is specified in the DB581.DBW12 in
detail (see above)

Logging
A5E00239388-04
Free definable logs
2.7 Parameterization in the IOS
2.7.1 Archive configuration (Def-File) 'receive data'

Within definition (DEF) files the structure of the archive (dBASE) files is defined. When
opening a file (free def. log) the first time and/or when receiving the first message, the
system creates a dBASE file based on the given structure of this DEF file. The following is a
sample of such a file.
Unrestricted listing/received datum configuration / telegram model 6

0 Offset: fix
121 record length: must be modified
1 AUFTR_NR CINT 5 order no.
6 CHARG_NR CINT 5 batch no.
11 SZ_JAHR CINT 2 batch start time (year)
13 SZ_MONAT CINT 2 batch start time (month)
15 SZ_TAG CINT 2 batch start time (day)
17 SZ_STUNDE CINT 2 batch start time (hour)
19 SZ_MINUTE CINT 2 batch start time (minute)
21 SZ_SEKUNDE CINT 2 batch start time (second)
23 REZ_TYP CHAR 16 recipe type
39 RECIPE CHAR 16 recipe name
55 TEILTELNR CINT 6 sub datagram number
61 DATEN1 CINT 7.2 [1,1,1,1] PCU1,Teilt.1,DW1
68 DATEN2 CINT 12.2 [1,1,2,2] PCU1,Teilt.1,DW2/3
80 DATEN3 CINT 6 [2,2,1,1] PCU2,Teilt.2,DW1
86 DATEN4 CINT 11 [2,2,2,2] PCU2,Teilt.2,DW2/3
97 TEXTE5 CHAR 16 [1,3,3,1,"mult.txt] PCU1,Teilt.3,DW3,Textl.
113 TEXTE6 CHAR 8 [1,3,3,1,"dfm0.txt] PCU1,Teilt.3,DW3,Textl.
Up to line 'TEILTELNR' the structure is fix for all use cases, however, except for the order
number and batch number the other parameters are optional. The lines below ‘TEILTELNR’
are optional, too, but can be configured in many different ways. Allowed are 16 bit, 32 bit
values as well as texts from text lists. The corresponding address within the telegram
received from the plc is given in the right most column (normally comment column).
2.7.2 Description file syntax

The description file must be built up as follows:
Description file
Offset
record
length
offset of element name data type element size comment or
element [.decimal points] description of user data
The configuration of the DEF file is to be interpreted as follows:

Offset:
The Offset defines the number of the bytes at the beginning of the (dBASE) file that does not
contain any user data (header data), but they are necessary for the file organization. These
header data contains the dBASE file size, number of records and record structure.
Logging
A5E00239388-04
Free definable logs
In case of using `Free def. logs’ this value may equal 0, as during evaluation of the
telegrams this offset is computed.
Record length:
The record length is the record size in bytes. Normally it is the sum of all elements (4th
column of DEF file). As it is allowed to leave some elements in the DEF file, this record
length parameter can be higher than this byte sum.
data element structure:
Every line describes the structure of one element as follows:

element offset:
This value gives a (relative) offset within the record, where the data of this element is stored
(start with byte address 0).
element name:
This is the symbolic name of the element, contains at most 10 characters whereas the first
must start with a character. This name becomes later the column name within a dBASE file.
Data type:
As only ASCII characters are allowed within a dBASE file, there is only a subset of all
possible data types for DEF files allowed to be used:
type description
CHAR: Character string
CINT: Number as a character string,
is printed / displayed later with right justification
element item, decimal point position:
Number of the characters and/or bytes of a element.

The minimum size is:
¾ 6 if the number has the range of a data word and no decimal places
¾ 7 if the number has the range of a data word and decimal places
¾ 11 if the number has the range of a data double word and no decimal places
¾ 12 if the number has the range of a data double word and decimal places
Either it is a single number (X) or the number is followed by a decimal point and another
number (X.Y) indicating the number of decimal spaces.
Rule: 1 <= Y <= (element size(X) - 3).
Comment:
at most 39 characters comment or user data description

User datum description:
Additional information within squared brackets [ ... ].

Every telegram from a plc contains the following information:
¾ plc number
¾ sub data gram number

Logging
A5E00239388-04
Free definable logs
Based on this two parameters and together with the additional information given in squared
brackets the system takes certains data out of the data gram an assigns it to specific
elements (lines in DEF file), and therefore of course to the dBASE file record.
Every data gram contains up to 5 data words (10 bytes) of user data. As a record may
contain more than 5 words normally, several data grams have to be sent. Using sub data
gram numbers provides the possibility to the separate a record and assign it to several (sub)
data grams.
According to the element number the system extracts the value(s) from the data gram(s). If
byond the number of decimal spaces the name of a file has been specified, the system uses
it as a index within the text file to retrieve a text line.
The syntax of the squared brackets [ ... ] is as follows:
[plc number, sub data gram number, element number, data size in words]
or for text files:
[plc number, sub data gram number, element number, 1, “file name”]
Meaning of the different elements:
Element Description
plc number Number of the plc, whose telegram contains a value that is supposed to be
extracted (valid range: 1 - <number of plc’s of system>).
sub data gram Number of the (sub) telegram, which a value is supposed to be taken from
number (valid range: 1 - <number of sub data grams>).
element number Number of the user data element within the data gram, whose value is
supposed to be taken (valid range: 0 ... 4).
data size in words number of user data elements, that are supposed to be read as a value. valid
range:
= 1 for data words
= 2 for data double words
= 1 if a text file name is specified
= 3 if a data / time identifier is specified (‘DT’ or ‘DT1’)
additions-/ ‘+’ the newly received value is added to the old value or
subtraktions ‘-‘ the newly received value is substracted from the old value
flag (optional) or The newly received value is the value taken from the telegram currently
handled.
Text file name: The value in element number corresponds with the text number in the text
(optional) file. if 'RecipeMode=GLOBAL' in SYS.INI, the textfile is read from Folder
WINDCS\TEXTE.X\ …otherwise from Folder WINDCS\PCU.xxx\TEXTE\
Note: Umlauts in text files
To ensure correct processing of Umlauts, parameter Konv=1 must be set in
[KonvChar] of "DB.ini"
date/time: (optional) if the element size 1 is specified and in addition ‘DT’ or ‘DT1’, than the first 3
words (user data) of the data gram is interpreted as a date/time in long or
short format.
DT Æ for example "10.01.1995 12:55:00"
DT1 Æ for example "10.01.1995 12:55"

Logging
A5E00239388-04
Free definable logs
2.8 Examples
2.8.1 Engineering in the plc

In the plc up to 5 words can be assembled by calling the FB580 up to five times, whereas
the same sub data gram number has to be specified.
Which values are handed over is specified by the parameters ‚DataDest, ‚function’, and
‚Ana' etc. The last call to FB580 uses ‘function = 0’, this triggers sending the data gram to
the IOS.
Per recipe type / order / batch number combination more than one sub data gram can be
sent. All sub data grams with the same order / batch number combination are stored into the
same dBASE file record, where the recipe type defines the location (folder name) of the
dBASE file and the order and batch number indicates the record within this dBASE file.
2.8.2 Engineering in the IOS

In the directory ‚FrProt' a DEF file must be configured for every recipe type used for free def.
logs. If recipe type independent data should be logged via free def. logs a ‘dummy’ recipe
type has to be used.
In the file ‘\windcs\FrProt\FEPR_xxx.def’ (recipe type xxx) both the data send via FB580 as
well as the data sent via and copied from stepping logs is defined.
The only difference is the configuration of ‘square brackets information’ for the use with
FB580.
The file has at the beginning a fixed structure. For every definition line a element offset has
to be entered. The offset of the next element is the offset added to the size (depends on the
data type) of its predecessor.
Note: The overall length (line 2 of the DEF file) has to be re-adjusted.
2.8.2.1 General definitions

Common parts are always:
¾ element offset
¾ element name = name of the column within the dBASE File
¾ data type
¾ length of the data type and
¾ user data description or
¾ comment (max. 39 characters)
example:
0 Free Protokoll/Empf.Daten-Struktur / Telegr.Typ 6

120
1 AUFTR_NR CINT 5 order number
6 CHARG_NR CINT 5 batch number
11 SZ_JAHR CINT 2 year
13 SZ_MONAT CINT 2 month
15 SZ_TAG CINT 2 day
17 SZ_STUNDE CINT 2 hour
19 SZ_MINUTE CINT 2 minute
21 SZ_SEKUNDE CINT 2 second
23 REZ_TYP CHAR 16 recipe type
39 RECIPE CHAR 16 recipe name
55 TEILTEL CINT 5 sub datagram number
60 E_DATEN1 CINT 7.4 [3,1,1,1] PCU1,Tt.1,DW1

Logging
A5E00239388-04
Free definable logs
67 E_DATEN2 CINT 12.9 [3,1,2,2] PCU1,Tt.2,DW2/3

79 E_DATEN3 CINT 6 [3,1,1,1] PCU1,Tt.1,DW1
85 E_DATEN4 CINT 11 [3,1,2,2] PCU1,Tt.2,DW2/3
96 E_TEXTE5 CHAR 16 [3,1,4,1,"TXT1.TXT] PCU1,Tt.3,DW3,Textliste
112 E_TEXTE6 CHAR 8 [3,1,5,1,"TXT2.TXT] PCU1,Tt.3,DW3,Textliste
2.8.2.2 Placing of numbers & texts
Plc-datagram record in database file

\FRPROT\FRJA_94\REZ_001\FE_09_94.DBF
Type=6 PCU=1 Auft_nr Char_nr ... Weight Flow Text Amo
volume unt
year=94 month=9 ..... ...
day=3 Hours=12 ..... ...
Minute=1 seconds=0 ..... ...
year = 03 recipe 13000 124 ... 12.78 70.330 cell 12 / 10
type=01: tank 3
order.no. = 13000
batch no. = 124 sub set of the according DEF-fileFEPR_001.DEF
sub- =3 . .
datagramn
o.
DW 0 = 1278 . .
DW 1 = 0x0001 55 Weight CINT 7.2 [1,3,0,1]
DW 2 = 0x12BA 62 Flow volume CINT12.3 [1,3,1,2]
DW 3 =3 74 Text CHAR 16 [1,3,3,1,“Anlag.txt“]
DW 4 = 10 90 Display CINT 6 [1,3,4,1,“+“]
.sub set of the text file "Anlag.txt"

Line 2: cell 12 / tank 2
Line 3: cell 12 / tank 3
¾ The value 1278 sent via sub data gram 3 (1st user data) is logged at byte offset 55
into the dBASE record.
¾ 55 the beginning of the data type within the definition. This offset starts at 0 and is
incremented.
¾ The next definition begins at 62 as at 55 a data type of size 7 (bytes) is specified.
¾ ‘Weight’ is the column name of the record in the dBASE file.
Remark: Don’t use special characters, e. g. "ß" as in ‘Durchfluß’.
¾ The CINT 7.2 value is supposed to be stored as a number with a maximum of 7
characters (comma included) and 2 decimal places.
¾ [1,3,0,1] describes where the data is located within the data gram. [plc number, sub
data gram number, offset of the first user data word, number of data words].
Additional information is possible, as some other examples show (‘Textliste’, ‚Add’
‚Subtract' etc.).
Annotation: The assignment of a datagram to the DEF file is related to the recipe type.

Logging
A5E00239388-04
Free definable logs
2.8.2.3 Configuration of ‘date & time’ logging

Plc datagram record in database file
\FRPROT\FRJA_94\REZ_001\FE_09_94.DBF
type=6 plc=1 order_nr batch_nr ... Datum1 Datum2
Year=94 Month=9 ..... ...
Day=3 Hour=12 ..... ...
Minute=1 second=0 ..... ...
year = 03 Recipe 13000 124 ... 10.01.1995 12:55 10.01.1995 12:55:04
type=1
:
Order number. = 13000
Batch number = 124 sub set of the DEF file FEPR_001.DEF
sub data gram =4 . .
number
DW 0 = 95,01 . .
DW 1 = 10,12 96 Datum1 CHAR 16 [1,4,0,3,"DT1"]
DW 2 = 55,04 112 Datum2 CHAR 19 [1,4,0,3,"DT"]
DW 3 =
DW 4 =

Logging
A5E00239388-04
Free definable logs
2.9 Files and folders

Here the directory structure of the received data is described (DEF file).
2.9.1 Standard - Configuration (monthly - archives)

The ‘Free def. log’ records are recorded into the corresponding files automatically by the
system after receiving a data gram. According to the data and the recipe type the file name
is created, if the file doesn’t exist, it will be created ‘on the fly’.
The syntax of the folder and the file name is as follows:
‘..\FRPROT\FRJA_<year>\REZ_<recipe type>\FE_<year>_<month>.DBF
According to the order and batch number a single record is created in the dBASE file (both
are used as a key). Every time another data gram is received, the system first searches a
matching data set and the data is written or rewritten. All other data is not recognized or if
not described within a predessesing data gram untouched.
Thus these two information are unambiguous and are evaluated as search keys. Each time,
when a telegram comes with exactly these numbers of the PCU's, first of all, the fitting
record is searched from the file and entered the corresponding user datum and/or
overwritten. All other components are maintained and/or. if still not through an ancestor -
message section weights, unconsidered.
With sub data gram number –1 the system creates the data set (record) together with
header data and the time/date stamp only. Otherwise it is created when receiving the first
data gram of a sequence of (sub) data grams.
2.9.2 Structure of a yearly archive

It is possible to store data independent of the year and/or month. In this case enter the
following into the configuration file ‘PROT_006.INI’ for example
[REZ_001]
month=00
year=00.
The syntax of the file name results in:
FE_<year>_<month>.DBF (for example FE_00_00.DBF)
2.9.3 Order/Batch Archive – Structure

In this variant the path \ file – structure looks as follows
..\FRPROT\FRJA_<year>\REZ_<Recipetype>\ANR O-No-5chars>\FE_<Batch.No-
5chars>.DBF.
A separate folder is created for each Order number block as well as a sepreate dbf file for
each Batch number block. The block range may be defined individually and is set to 50 per
default (see below).
For activating and configuring this model the following switches should be set in file
„PROT_006.INI“:
[GLOBAL]
;Global for all recipetypes. New path-systematic on/off (order-
batch-sorting/month-year-sorting).
New_Path=1
;Global for all recipetypes. It means, how much files get in one
path, dependent on orderno.. (Only for new path-systematic.)

Logging
A5E00239388-04
Free definable logs
Block_Order=50
;Global for all recipetypes. It means, how much datasets get in one
file, dependent on batchno.. (Only for new path-systematic.)
Block_Batch=50
This model may be defined for the individual recipe types as well, by setting the same
switches in the corresponding Areas [Rez_xxx].

Logging
A5E00239388-04
Free definable logs
2.10 Engineering of the search path

With the ‘archive-selection’ menue function of the MS Access database ‘PI_CHA32.MDB’
(description in capter ‘"Free Protocols" application for visualization and evaluation’) the user
can access different archives.
The dialog based selection is based on the search criteria and path syntax given in file
‘PROTDIDA.TXT’. The selection is done via list boxes, which are filled according to the list
configurations and wild card characters (*).
After a successful selection of the history file the complete path with file name is stored into
the file ‘TEMP\PROTDIDA.DAT’. The text file ‘PROTDIDA.TXT’ is located at the directory ‘...
windcs\SYS\’.
The next table shows the syntax of a search path for a data archive:
PROTDIDA.TXT
[TAB]<N0> number of the log
Name = <log name> name of the log
Note:
The average text length should not exceed 32
characters, because name elements may
otherwise be truncated.
PathDat = <path / file name with wild folder and file name
cards> (wild card characters are allowed)
List<List-Nr> = <listbox name> caption of the listbox if the wild card characters
are selected.
If no entry is available, the list box is skipped
and the next list box is shown.
The next list box (List-Nr) begins with the next
wild card character block.
From<List-Nr> = <char.number > Character number from which is Selected.
Otherwise to the character from the first
question mark is supposed to be searched, the
corresponding character number is brought
here.
To<List-Nr> = <char. number> Character number from which is Selected.
If there should not be searched for the last
occurence of a character, up to the last question
mark, a character has to be selected here.
Def<List-Nr> = <default value> If no entry exists, the default value is used for
the folder and file name.
Ref<List-Nr> = <Referenz on List-Nr> Reference to already existing entry.
If no entry exists, the same entry is done as at
the referenced list entry.
DEF = <Name DEF-File> DEF file corresponding to the log type
type = <Filetyp> File type according to sys.ini, for example.
–1 = System
1 = Free def. logs
2 = Stepping log

Logging
A5E00239388-04
Free definable logs
2.10.1 Examples from PROTDIDA.TXT (in state of delivery)

[TAB1]
Name = Freies Protokoll: Empfangs-Daten
PathDat = \FRPROT\FRJA_??\REZ_???\FE_??_??.DBF
List1 = Jahr
List2 = Rezepttyp
Ref3 = 1
List4 = Monat
DEF = \frprot\fepr_def.def
Typ = 1
[TAB2]
Name = Freies Protokoll: Hand-Daten
PathDat = \FRPROT\FRJA_??\REZ_???\FH_??_??.DBF
List1 = Jahr
List2 = Rezepttyp
Ref3 = 1
List4 = Monat
DEF = \frprot\fhpr_def.def
Typ = 1
[TAB3]
Name = Freies Protokoll: Sende-Daten
PathDat = \FRPROT\FRJA_??\REZ_???\FS_??_??.DBF
List1 = Jahr
List2 = Rezepttyp
Ref3 = 1
List4 = Monat
DEF = \frprot\fspr_def.def
Typ = 1
[TAB4]
Name = Freies Protokoll: Kopier-Daten
PathDat = \FRPROT\FRJA_??\REZ_???\FK_??_??.DBF
List1 = Jahr
List2 = Rezepttyp
Ref3 = 1
List4 = Monat
DEF = \frprot\fkpr_def.def
Typ = 1

Logging
A5E00239388-04
Free definable logs
[TAB5]
Name = Fr.Prot.: Empfangs-Daten/Neu
PathDat = \FRPROT\FRJA_??\REZ_???\ANR?????\FE_?????.DBF
List1 = Jahr
List2 = Rezepttyp
List3 = Auftr.Nr.-Block
List4 = Chargen.Nr.-Block
DEF = \frprot\fepr_def.def
Typ = 1
[TAB6]
Name = Fr.Prot.: Hand-Daten/Neu
PathDat = \FRPROT\FRJA_??\REZ_???\ANR?????\FH_?????.DBF
List1 = Jahr
List2 = Rezepttyp
DEF = \frprot\fhpr_def.def
Typ = 1
[TAB7]
Name = Fr.Prot.: Sende-Daten/Neu
PathDat = \FRPROT\FRJA_??\REZ_???\ANR?????\FS_?????.DBF
List1 = Jahr
List2 = Rezepttyp
DEF = \frprot\fspr_def.def
Typ = 1
[TAB8]
Name = Fr.Prot.: Kopier-Daten/Neu
PathDat = \FRPROT\FRJA_??\REZ_???\ANR?????\FK_?????.DBF
List1 = Jahr
List2 = Rezepttyp
DEF = \frprot\fkpr_def.def
Typ = 1
[TAB9]

Logging
A5E00239388-04
Free definable logs
Name = Freies Schrittprotokoll

PathDat = \SRPROT\???????.DBF
List1 = Archiv
DEF = \SRPROT\sr_frpr.def
Typ = 2
;[TAB10]
;Name = Schrittprotokoll Typ 5
;PathDat = \SRPROT\SRJA_??\REZ_???\ANR?????\S???????.DBF
;List1 = Jahr
;List2 = Rezepttyp
;List4 = Auftragsnummer
;From4 = 3
;To4 = 7
;DEF = \sys\srpdbf.def
;Typ = 2

Logging
A5E00239388-04
Free definable logs
2.11 Copy archive

Here the structure of folders for ‘copy archives’ is described (DEF file).
Via sub data gram number –3 copying a data archive can be triggered by plc. Dependent on
the recipe type, the order and the batch number, parts of the (original) ‘receive data archive’
are copied into a new one. A DEF file exists which describes the structure.
Free def. log / copy data structure / telegram type 6
0 Offset: always 0
44 Record length: must be modified
1 AUFTR_NR CINT 5 ["AUFTR_NR"]
6 CHARG_NR CINT 5 ["CHARG_NR"]
11 D1 CINT 7.2 ["DATEN1"]
18 D2 CINT 12.2 ["DATEN2"]
30 D3 CINT 6 ["DATEN3"]
36 T6 CHAR 8 ["TEXTE6"]
Note:
This function can only be used, if the switch:

[prot_cpu]
Akt=1
is set in the file prot_006.ini and the function is released with that.
2.11.1 Structure of a DEF file

See chapter 2.7.2, "Description file syntax"
2.11.2 User data description

In this description the element name of the corresponding element of the receive archive is
defined. Therefore the name is searched for within the original file and the corresponding
record (data) copied to the target file.
The description has following syntax:

["element name"]

Logging
A5E00239388-04
Free definable logs
2.11.3 Example of copying data

sub data gram from Datasets in archive file:
plc \FRPROT\FRJA_94\REZ_001\FE_09_94.DBF
type=6 PCU=1 Auft_nr. Char_nr .. Weight Flow Text amo
. volume unt
year=94 month=9 ..... ..
.
day=3 hours=12 ..... ..
.
minute=1 Seconds=0 ..... ..
.
year = 03 Recipe 13000 124 .. 12.78 70.330 cell 12 / tank 3 10
type=01 .
order no. = 13000
batch no. = 124 Extract from the DEF file: FKPR_001.DEF
datagram = -3 5 AUFT CINT 5 [“Auft_nr“]
subset
DW 0 irrelev. 6 CHA CINT 5 [“Char_nr“]
DW 1 irrelev. 10 T_1 CHAR 8 [“Text“]
DW 2 irrelev. 18 D_1 CINT [“Durchfluß“]
12.3
DW 3 irrelev. 30 G_7 CINT [“Gewicht“]
7.2
DW 4 irrelev.
Datasets in archive file:

\FRPROT\FRJA_94\REZ_001\FK_09_94.DBF
ORDER CHA T_1 D_1 G_7
.... .... .... .... ....
13000 124 cell 12 70.330 12.78
2.11.4 Copy archive folder

The ‘Free def. log’ copy data sets are copied automatically to the destination by the system
after receiving a data gram type –3. Dependent on the recipe type, the order and the batch
number, the record is first searched within the source files. If the files do not exist, they will
be created. The syntax is as follows:
‘..\FRPROT\FRJA_<year>\REZ_<recipe type>\FK_<year>_<month>.DBF’
Every record within this (destination or copied) archive is a subset of the receive archive.
The keys are again the order and batch number.
2.11.5 Programming the copy archive

We suggest the following sequence for calling FB580 for datagram 6:
Call of FB580 with iFunction=99 deletes data in the buffer

Logging
A5E00239388-04
Free definable logs
Call of FB580 with iFunction=7 enters the datagram subset

Call of FB580 with iFunction=0 sends datagram 6
Note:
If an error occurs when data are written to the archive, you can perform a diagnosis by
means of the "Tracesvr.exe" program. The cause of error is in most cases found in a faulty
*.def file.

Logging
A5E00239388-04
Free definable logs
2.12 "Free Protocols" application for visualization and

evaluation
2.12.1 Installation
The MS Access application "PI_CHA32.MDB" (Access 2000 Database format) supplied with
the software package can be used for the evaluation and visualization of *.dbf archive files
stored on the hard disk drive, and to print these data. This file is copied to the new
‘…\windcs\Access32’ folder by the Braumat Setup.
The MS Access Runtime Kit required for opening the MDB file (for users who do not have
the full version of MS Access), is found on the BRAUMAT/SISTAR Classic V5.3 Toolset CD
and must be installed seperately after running the Braumat Setup. Call the MSI setup file:
‘...\sis_sys.53\SISTAR.530_V0503xxxx\MicrosoftMS_AccessRuntime_Office_2003\Accessrt
.msi’.
If an earlier version of Access Runtime (before Access 2000) is installed on your PC, it
should be unistalled first.
If the application should be selectable from the menue, then the appropriate entry in file
‘menuv460.ini’ (in folders ‘texte.0’, ‘texte.1’ and ‘texte.10’ each) have to be integrated, as
explained by the following example:
Example:
[Chapter_3]
Name=Process archive
Desc=Trend view; Step and free protocols; mesages
Bitmap=mnu_archiv.bmp
Applications=6
App1=Trends;kurven.exe
App2=Step logs; srpneu.exe
App3=Free protocols;c:\Program Files\Microsoft
Office\Office11\msaccess.exe /runtime
d:\windcs\access32\pi_cha32.mdb
App4=Message archive; meldarch.exe
App5=Delta logging;proview.exe
App6=Maintenance data;wartdat.exe
Note:
In versions before BRAUMAT/SISTAR Classic V5.3 SP2 an earlier MS-Access Runtime

version was used which had to be copied (together with the database file) to folder
‘…\windcs\Access32.V70. In case of a software update this folder is not changed for
compatibility reasons and a new version of ‘PI_CHA32.MDB’ is installed as described
above. So it is recommended to change the entry in ‘menuv460.ini’ manually after the SW-
update (when using the ‘Free Protocols’ application) while adapting the MS-Access program
folder to the real attitude.

Logging
A5E00239388-04
Free definable logs
2.12.2 Working with the application

2.12.2.1 Functionality and Call
The Free Protocols application is used to select a data archive and to activate diverse
tables, queries and reports referring to the relevant data archive. To create data archive
tables, call the "Select archive" menu command.
Note:
The toolbar is assigned the standard MS Access functions. The "F1" shortcut key opens the
context-sensitive Help in the full version of MS Access. This version is not included with the
BRAUMAT/SISTAR Classic V5.3 CD package for reasons of Copyright. However, the user
can provide and implement MS Access.
Starting the program
The application is started from the Main menu Æ Register Tab ‘Process archives’ Æ
application ‘Free Protocols’
2.12.2.2 Client area

The main functions of the client area are
¾ Display of forms, tables and reports
¾ Display of the archive file, including the complete path in the toolbar
¾ Display of the type, month, year and recipe type in the status bar
2.12.2.3 Working with the application

Working with the Free protocols application comprises the following tasks:
Selecting a data archive
With menue item Functions Æ Select archive the following dialog box is shown for
selecting the required archive.
You can select the required protocol variant and archive file from the data found according
to the search criteria configured in PROTDIDA.TXT (picture shows the default configuration
at system delivery).
Start by selecting the protocol type from the "Selection" list box. In the next step, the
program generates a dialog, also using the wildcard characters stored in the search path,
until all data of the archive file and the full path name is entered.
Confirm the search item selected in the list box with OK or double-click.
Logging
A5E00239388-04
Free definable logs
By clicking NEW in the "Archive selection" dialog box, you can directly type in the path in an
input box, instead of selecting it in the selection list box. The function generates an archive
file which does not yet contain any data, according to user specifications.
The file PROTDIDA.TXT is stored in the Braumat system directory SYS. For further
information, please refer to chapter 2.10.
Note:
Protcol variants with the ‘…/New’ extension refer to the Order – Batch folder structure (see
chapter 2.9.3).
Opening the database table
Menu -> Functions -> Open table

Opening a table (example: “Freies Protokoll”)
Select the Functions menu, and then select the Archive table command to open the data
records of the archive in continuous (table) format.
(must have been configured by the user)
Opening a form (example: „Formular: Freies Protokoll“)
Select the Functions menu, and then select the Archive form command to open the data
fields of a record in a standard form.
Opening a report (example: „Bericht Freies Protokoll“)
Select the Functions menu, and then select the Archive report command to open the data
records of the archive in a report format.
Zoom function
The print preview shows only a section of the report, depending on the page format. You
can always open the print preview window to obtain a more detailed view of the printed file.
You can zoom the print preview in and out by double-clicking any area of the report with the
mouse pointer which changes to a magnifying glass form.
Print
Menu: File Æ Print

Standard elements of the archive database
The elements described below are available for all applications. The user can preset all
further dataset elements of the archive.
AUFTR_NR Order number
CHARG_NR Batch number
SZ_JAHR Start time: year
SZ_MONAT Start time: month
SZ_TAG Start time: day
SZ_STUNDE Start time: hour
SZ_MINUTE Start time: minute
SZ_SEKUNDE Start time: second
REZ_TYP Name of the recipe type
REZEPT Name of the recipe

Logging
A5E00239388-04
Free definable logs
TEILTELNR Datagram subset no.
The structure of the archive database is determined individually for each log type in a DEF
file (e.g.: FEPRDBF.DEF ffor the log type "Received data"). For information on how to
configure the DEF file, please refer to the configuration manual (see chapter 2.7 )

Logging
A5E00239388-04
Free definable logs
2.13 Summary
Note the following points for working with Free Protocols:
¾ Datagram 6 must be enabled in a FIFO
¾ The definition files must be created in "windcs\frprot" (see section 2.7).
Fepr_xxx.def xxx = recipe type (range = 1 to 255)
You can copy and edit the fepr_def.def template file.
¾ The data of datagrams type 6 in the controls must be programmed by calling
FB<Free Protocols> in DB<Free Protocols>. (see section 2.4)
S7 controller FB 580/DB580 with iFunction > 0 e.g. 7
S5 controller FB 80/DB80 with type > 0 e.g.. 7
After you have entered a maximum of five values, transfer these data in a datagram
subset (see item 5), and then continue with the data for the next datagram subset.
¾ In the controls, the datagrams type 06 must be initialized for each datagram subset
by calling the FB<Free Protocols> (see section 2.4)
S7 controller FB 580 with iFunction=0
S5 controller FB 80 with type=0
¾ These datagrams are generating Dbase files in
Windcs\frprot\frja_YY\rez_XXX\fe_MM_YY.dbf:
YY = year set in the datagram
XXX = recipe type set in the datagram
MM = month set in the datagram
¾ In order to view the archived datagrams by menas of the Free Protocols application,
the according DEF file must be defined in "windcs\sys\protdida.txt"

Logging
A5E00239388-04
Creating free protocols based on Stepping logs
3 Creating free protocols based

on Stepping logs
3.1 General
As a lot of information is already included in stepping logs, a selection can be applied via a
filter table to additionally select and store a subset from them as 'Free def. Log data' instead
of sending the same information twice (via stepping and via free def. logs).
3.2 Filter criteria

Following parameters of a step telegram can be used as a filter criterion:
¾ plc number
¾ unit number
¾ unit operation number = step number
¾ recipe number
This would normally allow filtering GOPs of all recipes, but what if we want to get the data of
exactly one GOP ?
The user can apply a filter ID which is provided as set point value (DFM) of a GOP (step).
This filter ID is also configured within the filter table.
3.3 Installation
To install and enable the functionality "Free def. logs by stepping logs’, you must do the
following:
¾ Copy files (see below)
¾ Modify ini file switch in ..\windcs\sys\SRPROT5.INI file
[SR_FRPT]
ForwardDGrams = 1/0
¾ Create the filter table
¾ Create the assignment table PCU/TA to recipe type number

Logging
A5E00239388-04
3.4 Necessary files

The following files have to be copied into their folders:
¾ GENFRPR.DBF to windcs\frprot\
¾ GENFRPR.DEF to windcs\frprot\
¾ GENFRPR.MDB to windcs\frprot\
¾ GENFRPR.LDB to windcs\frprot\
GENFRPR.MDB and GENFRPR.LDB are not a ‘must have’ but they offer a convenient input
mask (MS-Access) for the ‘filter table’ and the ‘assignment table’.
3.4.1 Structure of the filter table GENFRPR.DBF

Type Field name Field type Description Min. Max. DEF-
value value file
F PCUNR * Numeric PCU-number 1 255 CINT 5
F TEILANLNR * Numeric Unit number in the step 1 64 CINT 3
telegram
F GOPNR * Numeric GOP-number 1 32.767 CINT 5
F REZEPTNR * Numeric basic recipe number 1 32.767 CINT 5
(A recipe number
matches recipe number in
the step telegram exactly)
F SCHRITTNR * Numeric Step number for the 1 32767 CINT 5
distinction of GOPs with
identical GOP-numbers
F FILTER_ID * Numeric ID, if GOP that 1 "__int32 CINT 10
DFM employed x.y "
F FILTERDFM * Numeric DFM x.y, (= x*256 + y) 0 1.023 CINT 5
for example DFM3.255 =
1.023
Only relevant, if FilterID
was defined and doesn’t
equal 0
Q PARAM_TYP Numeric Type of parameter: 0 3 CINT 5
0 = actual value
1 = required value
2 = acceleration time of
the GOP
3 = end time of the GOP
Q PARAM Numeric Only relevant, when 0 13 CINT 3
_IDX PARAMTYPE=Ist-
/Sollwert
0 step operating time =
1..13=Parameternummer
(Required value 1..13)
Z DATEN_TYP Numeric 0 = Int16 (5 characters) 0 3 CINT 6
1 = Int32 (10 characters)
2 = text (Value is
interpreted as an index,
see below: parameter
"TEXT FILE")
3 = time, format
"dd.mm.yyyy hh:mm:ss",
4 = time, format

Logging
A5E00239388-04
"dd.mm.yyyy hh:mm"
3 and 4, when start-up or
end time
PARAMTYPE = GOP
5 time =, format
"hhhh:mm:ss"
6 time =, format
"hhhh:mm"
5 and 6 when
PARAM_IDX = 0 (Step
operating time) and
PARAMTYPE = 0/1
(setpoint-/Actual value)
Z SPALTENAM Character Field name (Name of the --- --- CHAR 9
string column) of the parameter
in the db-File, "CIS day
name" describes unique a
column of the above table
Z TEXTDATEI Character Text file name without --- --- CHAR 9
string TXT extension
Only available, when text
DATA_TYPE =, is ignored
else
Legend:
¾ F Filtering criteria (Conditions for the storage of a value from a telegram)

* If criteria = 0 then not relevant, if <> 0 the relevant and active filter
¾ Q Specifications of the source (What is supposed to be stored ?)
¾ Z Target information (Where should the information be stored to?)
Note:
¾ The step number is not evaluated currently, as it is not included in a step data gram
in the current version of BRAUMAT/SISTAR Classic V5.3 – therefore it cannot be
used as filter criteria at the moment !
¾ A line within the filter table describes always only one data item from a step
telegram. If for example several DFMs setpoint and/or actual values of the same
GOP are supposed to be stored, several lines must be configured within the table.
¾ The Filter-DFM, means the number of the DFM is only necessary, if a Filter-ID was
indicated (Filter-ID > 0), otherwise both values are ignored.
¾ plc-number (PCU_NR), GOP-number (GOP_NR), recipe type (RTYP_NR) and
recipe number (=recipe number, GR_NR) are ignored if they are 0. If they are larger
than 0, they are used as a filter criterion.
¾ The type of parameter (PARAMTYPE) and parameter index (PARAM_IDX) indicate
which data element is supposed to be stored from the step telegram.
¾ The parameter index is only relevant if the type of the parameter indicates an actual
or set point value to be stored.
¾ The parameter table type (TABLETYPE) and column name (COLNAME) of the filter
table indicate, where the value from the step telegram is supposed to be stored to.
The data type (DATATYPE) indicates in which format the value is stored. If the data
type "text" is specified, also the parameter "text file name" (TEXTFILE) has to be
configured. The value from the step telegram is taken as an index within the given
text file. The character string from the text file is stored in the dBASE files of the
Free def. log and not the value itself.

Logging
A5E00239388-04
¾ The table type (TABLETYP) corresponds to the file FEPR_<tabletype

number>.DEF, which describes the strcuture of the files of the Free def. log, for
example FE_<order number>.DBF.
¾ The column name (COLNAME) is the name of the column in one of the files of the
Free def. logs, this name appears also in the description file (FEPR_<table
type>.DEF). If a column name is specified, that does not exist in the description file,
then a warning message (WARNING) is stored into the trace file (see chapter
"Diagnosis")
¾ A specified file name (TEXTFILE)that does not exist in the text directory
(windcs\texte.y\ and/or windcs\pcu.xxx\texte.y\), then a warning message
(WARNING) is stored into the trace file (see chapter "Diagnosis")
¾ If a configured value exceeds the valid range for one of the parameters, then an
error trace (ERROR) is stored into the trace file (see chapter "Diagnosis")
¾ There are also still some "specific data types":
Action INT16 INT32 Description

--- DT_INT16 (0) DT_INT32 (1) New value = value
from telegram
Addition DT_INT16_ADD DT_INT32_ADD New value = value old
(65.536) (65.537) man value + from
telegram
Subtraction DT_INT16_SUB DT_INT32_SUB New value = value old
(131.072) (131.073) man - value from
telegram
Table1 : Data types - Addition and subtraction with old values
¾ Old value: Value from dBASE file (Value which is read from record)
¾ New value: Value for dBASE file (Value which is written in record)
¾ Value from telegram: Value from the step telegram
3.4.2 Assignment table PCU/Unit to recipe type number

Normally, data from Free Def. Logs is stored in DBF files based on Recipetype numbers
from Sistar. The layout of each DBF file is defined in the according DEF file
windcs\frprot\fepr_<recipetypenumber>.def
But another ‚view’ exists in association with CIS, where recipe types ‘span’ several units.
Here another table is used for assigning the PCUs/Units to recipe types. The DBF formed
table has the path/filename ‘windcs\frprot\pcutacis.dbf’.
Perhaps the term ‘Recipe type number’ should be omitted in association with CIS.
Now the tables are handled as follows:
¾ If the stepping protocol message has a PCU/Unit combination which is not
contained in the table, then the recipe type number is used directly for selecting the
destination DBF file
¾ If the received PCU/Unit combination is contained in the table, then the recipe type
number is not used directly but the associated recipe type number from
‚pcutacis.dbf’ is used for selecting the destination DBF file

Logging
A5E00239388-04
3.5 Diagnostic feature

To diagnose purposes it is useful, to trace individual or all parameters from the step
telegram if the desired data does not appear in the Free def. logs Output file. In the most
cases it is an engineering error (filter table).
To the enable the trace functions, please set the following keys in the file
\WINDCS\SYS\PROT_006.INI.
These keys are valid for step telegrams,
¾ arriving in the IOS (and are recorded),
¾ that should be stored (Telegram is relevant according to filter table) but where no
data has been written to the dBASE file of the Free def. logs.
The keys, that start with the prefix "DG_" are independent of each other. They can be used
to trace individual parameter from a step telegram.
[GenFrPr]
;0 = Tracing disabled; 1 = Tracing enabled
TraceToFile=0
;default trace file name if other trace file name couldn't be
generated, see key TraceToFile
TraceFileName=c:\tmp\genfrpr.txt
;Tracing of messages during check, whether a datagram is important
(data from step data gram should be saved as free protocol data), 0
= Tracing disabled; 1 = Tracing enabled
TraceFilterMsg=0
;0 = tracing disabled, 1 = Tracing enabled; tracing of all software
exceptions in module GenFrPr.C
ExceptLoggingOn=0
;0 = Don't display; 1= Display a message box if an internal software
exception occurs in module GenFrPr.c
ExceptShowMsgBox=0
;trace file name where information will be stored, if an internal
software exception occurs in module GenFrPr.c
ExceptFileName=c:\tmp\FrPrExc.txt
;0 = Tracing disabled; 1 = Tracing enabled; Tracing of time stamps
during evaluation of step datagram
TraceTimeStamp=0
;0 = Don't fill dynamically, 1=Fill dynamically Filtertable with
recipe type number, based on recipe type number of step datagram
FillFilterTableDynamic=0
;1=Trace step data gram if it isn't relevant, 0=don't trace it
TraceIfNotFound=0
;1=Trace step data gram type, 0=don't trace it
DG_Typ=0
;1=Trace plc nr of data gram, 0=don't trace it
DG_PCU=0
;1=Trace data gram time stamp, 0=don't trace it
Logging
A5E00239388-04
DG_TelTime=0
;1=Trace path year param of step data gram, 0=don't trace it
DG_PathYear=0
;1=Trace recipe type of step data gram, 0=don't trace it
DG_RezTyp=0
;1=Trace recipe number of step data gram, 0=don't trace it
DG_RezNr=0
;1=Trace order number of step data gram, 0=don't trace it
DG_AuftragsNr=0
;1=Trace batch number of step data gram, 0=don't trace it
DG_ChargeNr=0
;1=Trace unit number of step data gram, 0=don't trace it
DG_TeilanlNr=0
;1=Trace data set length of step data gram, 0=don't trace it
DG_DSLen=0
;1=Trace start time of step, 0=don't trace it
DG_StartTime=0
;1=Trace end time, 0=don't trace it
DG_EndTime=0
;1=Trace GOP number, 0=don't trace it
DG_GOPNr=0
;1=Trace set point time (Sollzeit) of step data gram, 0=don't trace
it
DG_SollZeit=0
;1=Trace (Istzeit) of step data gram, 0=don't trace it
DG_IstZeit=0
;1=Trace number, set point and actual value dfm's of step data gram,
0=don't trace it
DG_DFM=0
;Path for trace files, name will be generated automatically, e.g.
c:\tmp\genfrpr_xxxxxxxx.txt
TraceFilePath=c:\tmp
;max file size for each trace file
TraceSplitSize=65536
;or'd bits,1=norm.msg,2=wrns,4=err,8=err level2,16=fatal
errors,32=filter,64=filter warnings,128=filter errors,256=function
begin,512=fct end,1024=err def file,2048=dmp tbl,4096=lock
line,8192=info
TraceCat=29
In the log file the following appears (depending on which keys have been set to 1):
-----------------------------------------------------
DGram isn't relevant, additional information follows...
cTyp = 5
cPCUNr = 99
Logging
A5E00239388-04
telTime = 94.09.21 21:45:30

nPathYear = 0
nRezTyp = 1
nRezNr = 1
nAuftNr = 4352
nChargNr = 40960
nTeilanlNr = 10
lDSLen = 77
StartTime = 03.03.1998 12:17:12
EndTime = 03.03.1998 12:27:12
nGOPNr = 1
SollZeit =??.??.???? ??:??:?? (-171510507) // the Time/date stamp could not be evaluated
IstZeit =??.??.???? ??:??:?? (-282621618)
ANZ-DFM= 13
NR = 1 SOLL = 1 IS = 2
NR = 2 SOLL = 1 IS = -1
NR = 3 SOLL = 4567 IS = -4567
NR = 4 SOLL = -2147483648 IS = -2147483648
NR = 221 SOLL = 1234567890 IS = -1234567890
NR = 276 SOLL = 1234567890 IS = -1234567890
NR = 331 SOLL = 1234567890 IS = -1234567890
NR = 386 SOLL = 1234567890 IS = -1234567890
NR = 441 SOLL = 1234567890 IS = -1234567890
NR = 496 SOLL = 1234567890 IS = -1234567890
NR = 551 SOLL = 1234567890 IS = -1234567890
NR = 606 SOLL = 1234567890 IS = -1234567890
NR = 661 SOLL = 1234567890 IS = -1234567890
--------------------------------------------------------
Telegram is not relevant and is skipped by ForwardSchrittDGram

Logging
A5E00239388-04
3.6 Examples
Limits
There are four cases:

Case Procedure Control recipe Description
1 GOP 1 GOP 1 Only different GOPs that are not
GOP 2 GOP 2 multiplied (Master recipe without
Weighing-GOPs, old recipe system
GOP 3 GOP 3 version 2.13)
2 GOP 1 GOP 1 A GOP is used several times within
GOP 2 GOP 2 the recipe. Distinction through Filter-
DFM and Filter-ID.
GOP 1 GOP 1
3 GOP 1 GOP 1 Only different GOPs are used in the
GOP 2 GOP 2 control recipe, but a GOP is
multiplied, however, for example
GOP 3 GOP 2 Weighing-GOPs, as it is possible in
GOP 2 the new recipe system (version 3).
GOP 3
4 GOP 1 GOP 1 A recipe procedure contains several
GOP 2 GOP 2 GOP with the same number,
therefore also the control recipe has
GOP 3 GOP 2 these multiple GOPs.
GOP 2 GOP 2 In addition one GOP is multiplie as in
GOP 3 case 2 (Æ most complex case)
GOP 2
The cases 1 and 2 are currently covered by the functionality described here. In case 3 and
4, the multiplied GOP's can not be distinguished since in the recipe procedure only one
GOP exists.
Via the step number these GOP's can not be distinguished since the step number is not
part of the step telegram.
Even via the mechanism of the Filter-DFMs and the Filter-ID this GOP's can be
distinguished!
Saving the start time of a specific GOP which appears only once in all sequences of a plc
type column name Entry Example Comments

necessary ?
F PCU_NR Yes 3
F UNIT_NR Yes 30
F GOP_NR Yes 199
F GR_NR Yes 1.000
F FILTER_ID No 0 Because GOP appears only once in all
sequences
F FILTER_DFM No 0 Because Filter-ID is not used
Q PARAMTYPE Yes 2 start time of the GOP
Q PARAM_IDX No 0 Because PARAMTYPE is neither 0 nor 1
(Actual or setpoint value)
Z DATA_TYPE Yes 3 time
Z COLNAME Yes "start time" Always necessary
Z TEXT FILE No "" not used,
Logging
A5E00239388-04
because start time is not reasonable as

an index in a text file
Saving the end time of a specific GOP, that appears in several sequences (of the same
plc!) (filter DFM is DFM 3.255)
Type column name Entry Example Comments

nece
ssary
?
F PCU_NR Yes 3
F UNIT_NR Yes 30
F GOP_NR Yes 199
F GR_NR Yes 1000
F FILTER_ID Yes 10.000 Because GOP appears several times in
all sequences.
F FILTER_DFM Yes 1.023 The GOP is taken, which uses this
FILTER_DFM, all other GOP's with the
same GOP-number must not use this
FILTER_DFM
Æ 3.255 =
3*256 + 255 = 1.023
Q PARAMTYPE Yes 3 end time of the GOP
Q PARAM_IDX No 0 Because PARAMTYPE is neither 0 nor 1
(Actual or setpoint value)
Z DATA_TYPE Yes 3 time
Z COLNAME Yes "Finish at" Always necessary
because finish at is not reasonable as an
index in a text file
Saving the actual value of the fourth DFMs (DFM number = 2.44) of a GOP which appears
only once in the sequences of the plc
Type column name Entry Example Comments

nece
ssary
?
F PCU_NR Yes 3
F UNIT_NR Yes 30
F GOP_NR Yes 199
F GR_NR Yes 1000
F FILTER_ID No 0 Because GOP appears only once in all
sequences
F FILTER_DFM No 0 Because Filter-ID is not used
Q PARAMTYPE Yes 0 Actual value of a DFM of a GOP
Q PARAM_IDX Yes 4 4th DFM
Z DATA_TYPE Yes 1 32-bit-value

Logging
A5E00239388-04
Z COLNAME Yes "DFM4" Always necessary

because actual value is not taken as an
index in a text file
3.7 Picture showing the interaction
stepping protocol
handler GENFRPR.DBF /
filter table DEF
(SRPROT5.DLL)
filter table
description
of a
filter criteria,
datagrams type 5 table of the
source,
"free protocols"
destination
FEPR_<TableType
call check, whether
handler for datagrams Nr>.DEF
datagram is relevant
yes/no
data set size of data set

write dat set and memory
create a get
'free protocol' record text by index
WINDCS/TEXT.0/
xxx.TXT
WINDCS/FRPROT/
FRJA_97/REZ_001/
FE_00_09.DBF

Logging
A5E00239388-04
Step logging
4 Step logging
4.1 Overview
The setpoint and actual values of the process (units), quantities, temperatures and so on
and information about the executed unit operations are stored in files chronologically. The
storing of the data is done after a step change has finished.
The data are stored into dBASE files. The order and batch number are unique keys to the
stored batch data.
The batch data can be printed at any time or deleted. A complete batch print-out can be
activated also about the PCU. M101.2 (SRDR) must be set for this purpose via the flag
M102.3 (GSTO) in the last unit operation of a batch. Step logging program
4.2 'Step logging' program
4.2.1 Functionality
The Step logging program is used to view and print Stepp log files.
Client area
The client area can be split into these sections:

¾ - Header for the description of the various EOP elements
¾ - Area for the visualization of basic operations
¾ - Notepad
Column 1 : Key no.
Continuous numbering of the various basic operation positions
Column 2 : EOP
Shows the number of the technical operation
Column 3 : Name
EOP text that descxribes the technical operation
Column 4 : Date
Spalte 5 : Time-of-day
Column 6: Time
Column 7 dwonward: Setpoint 1 ... Setpoint 13
Logging
A5E00239388-04
Step logging
4.2.2 Working with the program

Your work with the Step logging program comprises the following tasks:
Selecting the step log file
Select File -> Open, then press F2 or click the OPEN FILE button to open the Select step
log file dialog box.
Options available:
- Year
- Recipe type
- Order number
- Batch number
- Unit
Start by selecting the year, the order number and the recipe type. Double-click the required
batch number to open the unit selection under Unit / PCU (area).
Confirm your selection with OK.
Printing step log files
Select File -> Print, then press F4 or click the PRINT FILE toolbar button to open a dialog
box for setting up the following functions:
Print:
- Log file of the selected unit
- All unit log files
Deleting step log files
Select File -> Delete, or double-click the DELETE FILE toolbar button to delete logs
from the hard disk drive. Select the log files to be deleted in the dialog box.
Order in which you select log files you want to delete:
- Year
- Recipe type
- Order number
- Bathc number
Access to the Delete log files menu can be password protected.
Input of comments
Select Options -> Comment, or press F10 to open the comment file for the current batch
number.

Logging
A5E00239388-04
5 Logging of user operations
5.1 Overview
The system is logging operator activities on process as well as changes in parameterization
and the recipes. The changes are structured like messages and stored in dBASE files.
This function covers.
¾ local logging of changes on a client and/or on a server
¾ Recording of a unit history
¾ Joining several local files into one ‘global’ file
¾ Apply batch relation to changes
Unit history
The history is recorded from the unit data image. The following changes are logged:
¾ Unit starts (leaving step 0 and going to a step unequal to 0; start and allocation)
¾ Unit terminates (goes from step not equal to 0 into the step 0; end and de-allocation)
¾ Unit changes its operation mode (automatic or manual)
¾ the fault indicator of the unit changes its status
¾ the running condition of the unit changes its status

Logging
A5E00239388-04
Client PC client PC
local logging function local logging function

(userlog.dll) (userlog.dll)
local log files local log files

...windcs\logging\userlog\... ...windcs\logging\userlog\...
recipe server
PCU-Server
recipe control
batch control
S7 channel
batch start
unit image
combining logs
(globlog.dll)
unit history
...windcs\logging\unithist\... offline data block image global log files
...windcs\logging\globlog\...
The changes are stored on every client temporarily. On every AREA server a service is
running, which combines the clients changes referred to this AREA and applies the batch
relation (if possible). The offline data blocks are used to get the batch information.

Logging
A5E00239388-04
5.2 client functionality

client application
user
(e.g. unit overview)
Client Applikation
(Beispiel: Anlagenübersicht)
stem
to
log on
w
en rite
the sy
try
local logging functionality

(userlog.dll)
da writ
ta e
se
t
local log files
All applications of BRAUMAT/SISTAR Classic V5.3 store changes done on a client via a
function (userlog.dll) into files of the system folder. The user currently logged in and the local
time of the client IOS is added to the log file.
Enable user logging on a client
File: windcs\sys\logging.ini
[Global]
EnableUserLogging=1
5.3 Server functionality

unit
batch combining files combined
historiy
reference (globlog.dll) data sets
(unithist.dll)
global log files

allocation
changes
e
ref unit
nc
ere
PMS
interface
unit history data offline data block image
On the server a service is running which combines the changes for that AREA done on the
clients. On the server also the unit history dll runs. For all changes related to objects with a
unit reference (ICMs, regulators...) the batch information is added. For that, the unit
assignments are read from the offline data blocks. If objects are assigned to units in a
dynamic way, it is not possible yet, to get the correct batch reference.

Logging
A5E00239388-04
Note!
It is the users responsibility to keep the offline data blocks up-to-date.
5.3.1 Configuration of the unit history

To get the reference from the changes to a batch, a history of the unit allocation must be
recorded. The batch data is recorded for every start and termination of a unit.
Enable logging of the unit history
File: windcs\sys\Logging.ini
[Global]
EnableUnitHistory=1
Location of the files
The files are stored in the folder '…\windcs\logging\unithist\...'. Subdirectories are created
per year (..\UH_YY). Within a ‘year’ directory a file is created per day (UHYYMMDD.dbf).
Example: ‘..\windcs\logging\unithist\UH_02\UH021221.dbf’
5.3.2 Configuration of the server function

For proper server function, the AREA assignments and access pathes for all IOS stations
have to be configured completely in the ‘SiteCfg.exe’ tool.
The change logging service must be configured on the recipe server. For that the ‘mini port’
file 'globlog.dll' must be entered in the ports list of the recipe server coupling mode.
Example file: ‘…\windcs\sys\pcu_serv.ini’
[&Rezeptserver]
Ports=ta.dll,s7.dll,recctrl.dll,balidata.dll,cas.dll,globlog.dll,cli
ent.dll
According to configuration the section name and port list can be different
Note: The client.dll should be configured as the last port
Cycle-time for the combination of the changes
File: ‘...\windcs\sys\logging.ini’
[GlobLog]
CycleTime=10
Deactivation of the globlog.dll
The server function can be disabled via a key, which is read also at runtime - a restart of the
pcu-server is not necessary.
File: ‘…windcs\sys\logging.ini’
[Global]
EnableGlobalLogging=0
Note:
The change log service is running only when the ‘Recipe-Server’ mode is activated on the
Server-IOS. Consequently only the active server on a redundant server pair runs that
service.

Logging
A5E00239388-04
Data storage
The user log and unit history files are combined to a global file called ‘globlog.dbf’ – which is
stored into the folder ‘…\windcs\logging\globlog\GL_YY\...’ with the file name
GLYYMMDD.dbf.
Redundancy
On a redundant system the data is copied to the standby machines by the active server. The
necessary path specificationsfor are read from the area.ini.

Logging
A5E00239388-04
5.4 Which changes are recorded ?

Changes to parameterization
Changes to data records of the block-classes (old- and new values each) via the
parametrization application ‘param.exe’ are recorded. However, this concerns the ‘Online
mode’ of parameterization only.
Note on text parameterization
The changes on the text parameterization are not logged.

Runtime process images/faceplates
In the faceplates of the runtime process images ‘LzSys.exe’ all parameter or value changes
of the linked valiable tags or block classes are logged with old- and new values each.
Particularly the following controls are concerned:
¾ Analog.ocx/Analog2.ocx
¾ Controller.ocx
¾ Digital.ocx
¾ ICM.ocx
¾ UnitCtrl.ocx
¾ SmartUnit.ocx
Recipes
The following changes on a recipe are logged:

(*) are not available in this release
¾ Status change
Recipe procedure
¾ Changes to ROPs
TUE
¾ Changes at the setpoints
Value
EditNr. (replacement, scaling etc.)
State
¾ Changes of the recipe structure
Deleting a ROP
insertion of a ROP
Deleting of a SW
insertion of a SW
RP type (Simple,(*)Free candidates, (*)XStreaming, tracks)
Deleting of a TRP
insertion of a TRP
¾ Unit recipe procedure (TRP) (RUP)
Name of the TRP
change of position
TRP deleted
TRP inserted
(*)unit class of the TRP
(*)Type of the candidates (Reference, automatic, manual)
Deleting candidates
Insert candidates

Logging
A5E00239388-04
¾ Track - recipe procedure (RP)

Change of the reference line
Reference line virtual / not virtual
Number of the reference lines
Deletion of a parallel line
Insertion of a parallel line
¾ Master recipe (GR)(MR)
Note: Changes are logged only in MR states not equal to ‘In work’
Name of the MR
Full name
Nominal batch size
RP-assignment
PIL-configuration: insert a input material
PIL-configuration: delete a input material
PIL-configuration: set quantity of input material
PIL-configuration: dosing group
PPL-configuration: number of process parameter
PPL-configuration: value of the process parameter
PPL-configuration: scaling of the process parameter
¾ Recipe procedure (RP)
Name
Recipe category
minimum, maximum, nominal batch size
Cycle time
Start unit
Start plc
creation date and "creator"
date of change and user name
¾ DFM definition
Change of the definition
¾ Technical operation (TOP)(EOP) – definition
Type (weighing, standard, etc.)
unit assignment
Number of the set points
setpoint values
editability of the set points
TOP – Name

Logging
A5E00239388-04
5.5 Structure of the files
5.5.1 Columns of the log files

The columns of the local and global change files are identical. At the local definition the last
column 'AddCounter' is left.
Column Type Comment

Time_GMT INT 11 Date and time according to
GMT
Date_Time TEXT 20 Date and time according to the
current IOS configuration
Log_Type INT 3 type of the entry
Usr TEXT 20 User who did the change
IOS TEXT 16 Name of the IOS
IOS_No INT 5 IOS number, on which the
changes were made
PCU TEXT 16 Name of the plc
PCU_No INT 5 Number of the plc
Block_Typ INT 3 block type
Block_No INT 5 Block number
DW_No INT 5 Data word
Bit_No INT 5 Bit number
Unit TEXT 16 Name of the unit assigned to
the object
UnitNo INT 5 Number of the unit assigned to
the object
Modules TEXT 12 Name of the module which was
modified
Object TEXT 16 Name of the object which was
modified
ObjectNo INT 5 Number of the object
Attributes TEXT 16 Attributes, that was modified
RecType TEXT 16 Name of the recipe type
RecTypeNo INT 5 Number of the recipe type
BatchYear INT 5 Year, when the batch was
created
OrderNo INT 5 Order number of the batch
BatchNo INT 5 Batch number
OldValue TEXT32 old value
NewValue TEXT32 new value
Text TEXT64 Additional information about the
changes
AddCounter INT 5 number to make identical
entries unique

Logging
A5E00239388-04
5.5.2 Columns of the units history

Column Type Comment
Time_GMT INT 11 Date and time according to
GMT
Date_Time TEXT 20 Date and time according to the
current IOS configuration
PCU_No INT 5 Number of the plc
Unit_No INT 5 Number of the unit assigned to
the object
UnitState TEXT 8 Status of the unit as a
hexadecimal number
Step_No INT 5 Step number
Rtype_No INT 5 Number of the recipe type
Rec_No INT 5 Number of the recipe
BatchYear INT 5 Year, when the batch was
created
Order_No INT 5 Order number of the batch
Batch_No INT 5 Batch number
5.6 Application ‘Change archive’

The recorded changes can be viewed with the ‘change archive’ application (proview.exe).
The application makes it possible to view the changes of a day.
The figure above the following changes are visible:

¾ Taking the sequencer 'malt intake' to '+' (set NotSeqHeld to 1)
¾ Afterwards the sequencer is parameterized with the order number 47, the batch
number 11, the recipe category 1 and the recipe number 1
¾ The last action is starting the sequencer (NewStep is set to 1)
5.6.1 Selection
The day of the changes is selected via 'open day archive'.

Logging
A5E00239388-04
¾ button ‘Reload’
Via this button the currently selected day archive is reloaded and the field ‘last
actualization’ is set.
¾ Filter
A filter can be applied to one column at a time, where ‘Only whole words’ or ‘Match
case’ may be selected.
¾ Selection ‘Set filter'
The filter becomes effective.
¾ Selection 'Show all'
The filter is disabled and all changes of the day are now listed.
5.6.2 Selection of columns

About the dialog 'column selection' the visible or printed columns can be chosen.

Logging
A5E00239388-04
5.6.3 Printing
The selected columns can be printed on the standard printer.
About the menu item 'printer setup' a different printer can be selected.
5.7 Logging the last most significant recipe

modifications
In addition to the entries in the "userlog" and "globlog" files, Braumat/SISTAR writes all
changes assigned highest priority to the master recips header file when it saves a recipe
procedure, provided the logging function is enabled. This entry consists of the modified text
and of the ID.
In the Manufacturing Execution System (MES), an entry is made in the MES coupling table
when the data are saved, and the entry is downloaded to the master system.
Of several changes to the recipe system made in a session between two archiving
operations, only the changes with highest priority are saved. The priorities of the changes
categories are found in the table. Existing entries are overwritten by the new data (LMSM
Logging: Last Most Significant Modification).
Modification Priority ID
RP production enables status is Maximum 32767
set or reset
RP type modified 70
TRP deleted 60
New TRP added 50
TRP deleted 40
New RUP added 30
Recipe updateed 20

Logging
A5E00239388-04
Setpoint modified Minimum 10

Logging
A5E00239388-04
What to do on errors?
6 What to do on errors?
6.1 General
No. Error Fixing / cause

1 A local change file is created, Check the file 'area.ini':
but the global file is not created, the paths to the client machines
or the entries are missing. must be specified and must be
accessible from the server
(shares).
2 Column 'user' is empty A user name is written to the
file only if the user access
security is used and enabled on
the system and a user is
logged onto
BRAUMAT/SISTAR Classic
V5.3.

Logging
A5E00239388-04

14 Logging e

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

14 Logging e

Uploaded by

Copyright:

Available Formats

Preface, Content

This manual is part of the documentation

Copyright Siemens AG 2007 All rights reserved Disclaimer of Liability

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

This manual is valid for the software package BRAUMAT/SISTARClassic

BRAUMAT/SISTAR Classic V5.3 iii

Engineering Recipe System

Dosing and Serve & Watch

Building block Building block

Building block Serve & Watch

iv BRAUMAT/SISTAR Classic V5.3

BRAUMAT/SISTAR Classic V5.3 v

Service & Support on the Internet

vi BRAUMAT/SISTAR Classic V5.3

viii BRAUMAT/SISTAR Classic V5.3

1.2 Recipe log

Outputs the master recipe list

¾ RUP lists with options for selecting

1.3 Stepping log

Print-out triggered by a unit operation:

Print-out through the user:

1-2 BRAUMAT/SISTAR Classic V5.3

1.4 Parameterization log

1.5 Order log

1.6 Message archive log

1.7 Curve archive log

BRAUMAT/SISTAR Classic V5.3 1-3

1.8 Curve input log

1.9 Maintenance log

1.10 Report footer

1-4 BRAUMAT/SISTAR Classic V5.3

BRAUMAT/SISTAR Classic V5.3 1-5

2 Free definable logs

2.1 PCU S5 vs. PCU S7

2.1.1 Different addresses and parameters

BRAUMAT/SISTAR Classic V5.3 2-1

Identification for block transfer ( W-NR iDataDest;

2.1.2 Different functionality

2-2 BRAUMAT/SISTAR Classic V5.3

2.2 Parameterization in the plc

2.2.1 Telegram structure (plc Æ IOS) and sending

Telegram- DB<Fr.Prot.> DB<Fr.Prot.> DB

BRAUMAT/SISTAR Classic V5.3 2-3

2.3 Required blocks within the plc`s

2.3.1 instance data blocks DB<FREE DEF. LOG)

2.3.2 FB<FREE DEF. LOG >

2.3.3 DB<temp. buffer>

2.4 Parameterization of the FB<FREE DEF. LOG>

2-4 BRAUMAT/SISTAR Classic V5.3

batch number Identification for origin of the parameters or batch number

methods for calling the FB<FREE DEF. LOG> :

calling type Description

BRAUMAT/SISTAR Classic V5.3 2-5

2-6 BRAUMAT/SISTAR Classic V5.3

BRAUMAT/SISTAR Classic V5.3 2-7

2.5 Examples for logging batch data

Call "FREE_PROT_FB", "FREE_PROT".

Call FB 580 function 7

Parameter interface values description

Call FB 580 function 1

iDataDest := 3 the target data words in the telegram are located at

Call FB 580 function 4

Parameter interface values Description

BRAUMAT/SISTAR Classic V5.3 2-9