Technical data

Creating STL Source Files
13.2 Rules for Programming in STL Source Files
Programming with STEP 7
284 Manual, 05/2010, A5E02789666-01
Block Properties and Block Order
When entering block properties, you should observe the input sequence shown in the following
table:
Order Keyword / Property Meaning Example
1. [KNOW_HOW_PROTECT] Block protection; a block compiled with
this option does not allow its code
section to be viewed. The interface for
the block can be viewed, but it cannot
be changed.
KNOW_HOW_PROTECT
2. [AUTHOR:] Name of author: company name,
department name, or other name
(max. 8 characters without blanks)
AUTHOR : Siemens, but no
keyword
3. [FAMILY:] Name of block family: for example,
controllers
(max. 8 characters without blanks)
FAMILY : controllers, but no
keyword
4. [NAME:] Block name (max. 8 characters) NAME : PID, but no
keyword
5. [VERSION: int1 . int2] Version number of block
(both numbers between 0 and 15,
meaning 0.0 to 15.15)
VERSION : 3.10
6. [CODE_VERSION1] ID whether a function block can have
multiple instances declared or not. If
you want to declare multiple instances,
the function block should not have this
property
CODE_VERSION1
7. [UNLINKED] for DBs only Data blocks with the UNLINKED
property are only stored in the load
memory. They take up no space in the
working memory and are not linked to
the program. They cannot be accessed
with MC7 commands. The contents of
such a DB can be transferred to the
working memory only with SFC 20
BLKMOV (S7-300. S7-400) or SFC 83
READ_DBL (S7-300C).
8. [NON_RETAIN] This option is only effective if the CPU
supports the Retain property of DBs. A
data block with the "Non-Retain"
property is not stored in retentive
memory in such a CPU (for example
CPU 317 V2.1) and is therefore reset to
the load values at each power cycle
and after every change from STOP to
RUN.
9. READ_ONLY] only for DBs! Write protection for data blocks; its data
can only be read and not changed.
FAMILY= Examples
VERSION= 3.10
READ_ONLY