LENZE E94AMSE0034 E94AMSE0034 E94AMSE0034 E94AMSE0034 E94AMSE0034 E94AMSE0034

With the attribute KNOW_HOW_PROTECT a know-how protection mechanism for
blocks of type OB, FB and FC can be activated.
Instance data blocks cannot be protected manually since they depend on the
know-how protection of the assigned FB. This means that the instance data block
of a password-protected FB also contains a know-how protection. This does not
depend on whether the instance data block has been explicitly created or
generated by a block call. In TIA Portal are also global data blocks allowed. ARRAY-data blocks could not be
protected with know-how protection.
Limitations
Blocks with a block protection cannot be further processed in STEP 7 (without
correct password). Nor are testing and commissioning functions such as “Monitor
blocks” or “Stops” possible. Only the interfaces of the block remain visible.
The following actions can be carried out with a protected block:
? copy and delete
? call the protected block
? online/offline comparison
? load
S7 Block Privacy
S7 Block Privacy is a STEP 7 expansion pack from V5.5 onwards for protecting
functions and function blocks.
When using S7 Block Privacy, the following must be observed:
? S7 Block Privacy is operated via the context menus.
? Blocks once protected can only be unprotected with the correct password and
according to the enclosed recompilation information. Therefore it is
recommended to keep the password in a safe place and/or make copies of the
unprotected blocks.
? Protected blocks can only be loaded to 400 CPUs from version 6.0 onwards,
on 300 CPUs only from version 3.2.
? If there are sources in the project, the protected blocks can be restored by
means of the sources by compilation. The sources can be completely removed
from the S7 Block Privacy.
Note Further information for setting the block protection with the S7 Block Privacy can
be found in the FAQ “How can the improved blBlocks in STEP7 V5.x can be protected by adding a block attribute. The code word
KNOW_HOW_PROTECT is indicated during programming of the block in the
source.
The block protection can only be revoked with the STL source. If the STL sources
are no longer available to the program or the project, the protection for the blocks
cannot be removed.
It is recommended to use S7-Block Privacy instead as an improved know-how
protection mechanism.
Note Further information on setting up the block protection can be found in the
KNOW_HOW_PROTECT FAQ “How can a block prIn the TIA Portal, the block protection is set via the context menu by indicating a
password.
The following must be observed:
? In the comparison between the offline and the online version of know-howprotected
blocks, only the data that are not protected will be compared.
? No type of a know-how-protected block can be created in the library. If such a
block is added to a library, the new copying template also contains the knowhow
protection. There, you need the correct password of the know-howprotected
block for using the copies.
If a know-how-protected block is to be used in a library without disclosing the
password, the following items have to be observed for programming these
blocks:
– During compilation all the code and data blocks called must be known. So
it is not possible to make any indirect calls.
– For programming the blocks, the use of PLC variables and global data
blocks should be avoided.
Note Further information can be found in the STEP 7 (TIA Portal) online help at:
? Set up know-how protection for blocks